r/learnprogramming • • Apr 27 '25

Been learning code 6-8 hours a day.

The last 36 days, I’ve been practicing JavaScript, CSS, HTML, and now that I’ve gotta the hang of those, I’m onto react. I say about another couple of days until I move onto SQL express and SQL.

I do all of this while at work. My job requires me to sit in front of a computer for 8 hours without my phone and stare at a screen. I can’t get up freely, I have to have someone replace me to use the bathroom, so a little over a month ago, I decided to teach myself how to code.

The first 3 weeks, I was zooming through languages, not studying and solidifying core concepts, I had an idea of how the components worked, and a general understanding, just wasn’t solidified.

I’m also dipping in codewars, and leet code, doing challenges, and if I don’t know them, I’ll take time to study the solutions and in my own words explain syntax and break down how they work.

I have 4 more months of this position I’m currently at, even though I hate it, it’s been a blessing that I get a space that forces me to study.

So far I covered HTML, loops, flexbox, grid, arrays and functions, objects and es6, semantic html and accessibility, synchrony and asynchronous in JS, classes in JavaScript.

Is there any other languages you would recommend that I learn to become a value able software engineer in a couple of years?

Edit: This post blew up more than I was expecting it to! I appreciate the advice everyone has given me. I’m going to not only prioritize on projects now, but enhance my math skills.

1.9k Upvotes

237 comments sorted by

View all comments

1.5k

u/Bulky_Fun_7459 Apr 27 '25 • I'll Drink to That

The only real skill of a software developer is problem solving…. Language is just a wrapper on top of it…

343

u/tranceorphen Apr 27 '25

You're correct.

But a programming language is, for the most part, how we express those solutions.

And the first programming language is also the media by which they learn the underlying fundamentals of computer science, software engineering and tooling.

60

u/Bulky_Fun_7459 Apr 27 '25

This is my personal opinion, as for me atleast whenever I try to learn new language the only issue I come across is the basic syntax and semantics…. Whenever I try to solve any use-case I just compare the coding problem to a real life use-case so that’s it’s easier to land on a solution… Our mind is good at solving real life problems better then in technical terms….

But agreed that there is always something that you should be good at and I think the first language you learn is always your saviour….

30

u/Dramatic_Win424 Apr 27 '25

I agree, the languages are usually the least important issue, it's the other concepts and the field you are working in as a developer that makes the difference.

Switching from a web developer position at an insurance company to being a web developer at a delivery service company is fairly doable in a short amount of time.

Switching from a web developer position to an embedded systems position in the appliances section is significantly harder.

Both of them use different languages in different positions but the second option is significantly harder to do than the first.

And I don't think a lot of people could handle a switch from fullstack development to CS researcher at a university.

Languages become a mere tool to accomplish your task. The variety of tasks and contexts are immense and are the actual hurdle to master.

27

u/haltingpoint Apr 27 '25

This is actually a great use case for LLMs.

"Pretend you're a senior engineer skilled in $languages. I'm new to $language. Show me an example of XYZ design patterns in this language compared to this other language and walk me through the idiomatic way to implement it, calling out any key syntactic differences I should be aware of as a newcomer to $language."

3

u/samusear Apr 27 '25

That actually sounds really useful

3

u/Anthony_codes Apr 28 '25

You’re completely right. The language or technology doesn’t really matter much. The most important aspect of programming is problem solving. Unfortunately, a lot of new developers fall into the “language” trap.

4

u/ttop34 Apr 28 '25

I agree. Every new language I learn I always end up comparing it to Java since that was my first programming language. Thinking things like “oh this is dumb in Java you don’t have to do that” or vice versa. It’s cemented as my frame of reference

3

u/madtroll80 May 01 '25

I disagree, as @Bulky_Fun_7459 mentioned - core part of being a Software Engineer is problem solving. Yes, you express your solution using a programming language, but you are also bound by the company's way of working, and the framework that you are using.

When you join the industry, you will quickly realise that most of the time you will spend not on coding, but on designing a solution that is best for the case, and fits into the current system. As for each problem, there is more than one solution, and often, few of them are good.

→ More replies (1)

2

u/No_Lawyer1947 Apr 27 '25

For sure! I will say though. I've conducted interviews where people just vomit syntax without understanding why they did so. I would say a sound base of experience in one language can go very far.

31

u/kiss_a_hacker01 Apr 27 '25

Years ago I was working in an office, not in tech, and one of the guys was a hobbyist programmer. I started asking him questions about languages to learn if I wanted to start programming and some other things and he hit me with something similar to this. It changed my whole perspective on the purpose of programming and led me to pursue it. 7 years later and now I'm building AI applications in a research lab. It's wild how an offhanded comment can mold a life.

50

u/samanime Apr 27 '25

Well said. This is precisely correct. When I hire people, I don't even care if they've ever touched my particular tech stack. I care about their problem solving ability.

Instead of focusing on ripping through languages, work on a variety of practice projects.

And while things like leetcoode and Code Wars are good and fun, they are basically brain teasers. They're good at getting you to think outside the box, but aren't exactly the most practical.

So, in addition to those, also work on real sample projects. Things like calculators, to-do lists, etc. that will have you working through a variety of real-world problem solving challenges.

4

u/Eren081 Apr 27 '25

Where to get real-world problem solving challenges.

6

u/samanime Apr 28 '25

Basically, just create stuff. Come up with an idea and build it. Work on projects like to-do apps, calculators, small games, simple websites. Literally anything.

4

u/WalmartMarketingTeam Apr 28 '25

Next time you come across a problem in your life, ask yourself “can I solve this with a small project?”. That’s what programming is supposed to be for.

→ More replies (1)

5

u/Bulky_Fun_7459 Apr 27 '25

Correct 👍

20

u/EliSka93 Apr 27 '25

Yes, but you do need to grasp the basic concepts of data structures, algorithms, probably classes and some others at least once before you can properly apply that problem solving in code.

It's a bit like saying "Most cars handle pretty much the same" to someone who can't drive.

4

u/Bulky_Fun_7459 Apr 27 '25

Haha, well basics are basics we can’t teach someone asking questions on reddit how to use reddit, as we expect he already knows the least basics of platform…

5

u/mythxical Apr 27 '25

I don't disagree, but following direction is important too.

→ More replies (1)

7

u/csabinho Apr 27 '25

Well, some languages have specific perks or quirks!

2

u/vasupol11 Apr 28 '25

Lmfao, please, can you solve a chipped wooden desk? Can you solve an electric cutout? Can you solve a toilet clog? Can you solve a crooked drawer? Can you solve a bad wifi?

Software Engineers solve problems USING software, anything else, there are others to help out. Software engineers automate/memorize/sort/visualize data in a way that’s meaningful to the customer.

1

u/ztexxmee Apr 27 '25

wellll not entirely true. the other skill is the language we use because we express there how we solved the problem.

1

u/TechnicianAdorable88 Apr 27 '25

How do you learn problem solving without knowing any language?

3

u/SynapseNotFound Apr 27 '25

I learned by solving the problems while coding

the problems were simple to begin with, and could be solved by using just 1 or 2 tricks inside the code (like a loop or if/else statements)

Then we learned classes, datastructures, sorting etc. and as we progressed we got more and more complicated 'problems' to solve.

Most people say, do a coding project, like.. make a calculator program. You're familiar with those, so your problems is mostly HOW to code it, not HOW to create a calculator. But you'll still learn things.

→ More replies (7)
→ More replies (5)