Live data from Hacker News

I self-learned to code at 30

kaapi.team

41–50 of 150 posts

Re: I self-learned to code at 30

#41

This part stood out to me: > Every weekday - 1 hour post work > Every weekend - 4 hours on Saturday and Sunday each > Done over 4.5 months, so total = 234 hours As an almost-40-year-old that has minor coding experience (but wants to do / learn more) I find that time is the component that's the most difficult to overcome. I have a wife, a 5 year old, a house... all of which require time. Getting 4 hours _per day_ on a…

100% Agree

Re: I self-learned to code at 30

#42
Not at 30, but I started to self-learn at 27. The key difference for me was that a) it was on the job so I had access to computers (the job wasn't related to coding) and b) I didn't have any family commitments so I could do as much reading/practice/coding as I wanted. Many Saturdays and Sundays were spent at the Unix prompt.

However, I wasn't driven by the desire for my own business or career growth etc (nothing wrong with being driven by those - I do like money very much). The driving force that kept me going was that I absolutely loved programming. It is probably the one enduring thing that I never outgrew. I guess that is why many many years later, I'm still coding. And I still love it.

Re: I self-learned to code at 30

#43
post #7

I have a slightly cynical view about this sort of thing, and assume that most might have some counter-arguments for why my cynicism is misguided. I get that the point of the post is to encourage others, but proclaiming to have "learned how to code" feels misleading because there is no real finish line for it. This is an open-ended skill, there is no such thing as being done with it, same with most other skills. Maybe…

Knowing how to code means you're able to go from an idea to working implementation in a reasonable amount of time.

Re: I self-learned to code at 30

#44

This part stood out to me: > Every weekday - 1 hour post work > Every weekend - 4 hours on Saturday and Sunday each > Done over 4.5 months, so total = 234 hours As an almost-40-year-old that has minor coding experience (but wants to do / learn more) I find that time is the component that's the most difficult to overcome. I have a wife, a 5 year old, a house... all of which require time. Getting 4 hours _per day_ on a…

This is important. With a busy family life, you will never find 4-8 hours regularly to sit down and study solidly.

What you're quite likely to have is half an hour every day, and if you do some study for a short amount of time daily, the hours will very quickly add up

Re: I self-learned to code at 30

#45

My experience with learning how to code, is just find some good guide, follow it TO BUILD A REAL USABLE PRODUCT. Learning by making a real usable product is the most important part here, other kinds of learning didn't work for me. P/S: This is different from learning by project. Project mostly is for fun, not a real usable product.

I like this nice list for finding those sorts of tutorials https://github.com/tuvtran/project-based-learning

Re: I self-learned to code at 30

#46

I suspect that most of what is coding (ie, logic) is pretty intuitive, and only obfuscated by environmental factors like learning syntax, obscure jargon, and especially learning to execute code in your head. However, it's been a long time since I learned to code myself and my own learning experience is lost to the mists of time, so I'd really love to hear from people who are either learning right now or have recently…

I learned about 8 years ago and I think the first, hardest part is grasping the fundamentals - firstly data structures and algorithms. Things like visualizing the storage of data types in variables and using them later. Things like when you create a variable you create an empty box and assigning something to that variable is like putting the variable in the box. A tool to be able to visualize what an array of tuples…

Honestly if I were advising someone, with apologies to Dijkstra, I'd tell them not to worry about the CS side of things until they could make programs. Way easier to approach that stuff as someone who already is comfortable with programming basics.

Re: I self-learned to code at 30

#48

I started at 37 and got my first full time job a couple of months after I turned 38. I was a lawyer and hated it - now I love going to work every day. But it wasn't easy. I was working full time in a demanding profession and I'm married with two kids under 5 years old. So basically I spent every free moment I had working on learning HTML/CSS/JavaScript. If my kids were asleep, I was coding. I basically had to burn th…

It's good to see someone on the same path. I was a corporate lawyer for a couple years before dedicating all my time to learning programming. I got really excited with it and got back to university to get a compsci degree. I'm on my second year and I still love every minute I spend learning algorithms and other technologies.

Re: I self-learned to code at 30

#49

One thing I've noticed as a self-taught programmer is that concepts get really, really fancy names for simple things and it kinda acts as a barrier. That said one of the hardest part s of programming on a team so far has been making names that make sense, so, some sympathy there.

I see you've likely met Dependency Injection, the fancy name for "pass the dependency as a parameter"

Re: I self-learned to code at 30

#50

I started at 37 and got my first full time job a couple of months after I turned 38. I was a lawyer and hated it - now I love going to work every day. But it wasn't easy. I was working full time in a demanding profession and I'm married with two kids under 5 years old. So basically I spent every free moment I had working on learning HTML/CSS/JavaScript. If my kids were asleep, I was coding. I basically had to burn th…

> My only regret is that I didn't do this 10 years earlier.

It's not a bad thing to have a professional career before programming. I'd imagine that you'll have developed some non-technical skills that some developers lack, to be blunt about it.

Post reply on HN