Live data from Hacker News

How I learned to code in my 30s

medium.com

111–120 of 208 posts

Re: How I learned to code in my 30s

#111

Earlier quoted context omitted.

That unit of measurement should be dubbed the Pruteanu As in: " How many Pruteanus until I'll be proficient in ML if I have zero understanding of the subject"

So shall it be! 1 Pruteanus (1 Prt) is measured as the amount of learning from a 1m high stack of any books given. obv /s

[deleted]

Re: How I learned to code in my 30s

#112
post #38
post #4

What i always tell people if you find yourself naturally drawn to it then you will eventually find some level of success. If your in for just the money then you will not stick with it and it probably won't happen. Same is true for just about most things in life. This guy found he was naturally drawn to it. End of story.

people say this a lot but it's pretty hollow. if you're smart enough you can do it even if you don't like it. anecdotally I'm a fairly good dev (full stack, know several languages, several projects under my belt) and I hate it. the day I move from technical to management will be the greatest day of my life.

A manager tries to create reliable processes using flaky components with zero test coverage and lying metrics, I don't envy their job.

Btw, it irks me that you don't capitalize the first letter of your sentences but still properly capitalize "I".

Re: How I learned to code in my 30s

#113
post #13

This is generally a decent article about the balancing non-technical skills, and exerting effort in learning. I found it noteworthy that the "hook" in the title is that the person started in (gasp) their 30s. Why should that be noteworthy? Why wouldn't someone start coding in their 30s, 40s or 50s? Now it is true that starting a new profession late in life may not always make sense because, presumably, you have to li…

Yeah, I think the relevant part is "getting into software/tech in 30s", not learning to code per se which should be non-newsworthy at least through one's 50s. Then again, I changed careers into software in my 30s (had just turned 30 when I left aerospace), though I had coded in some capacity my entire life. Newsworthy?

s/50/90/

Re: How I learned to code in my 30s

#114
post #33

Earlier quoted context omitted.

on the topic of book learning, is there some generally considered principal choice when it comes to learning Haskell? There seem to be some competing ones with widely varying opinion.

There are indeed a lot of competing ones. Highly recommended: • CIS 194 @ UPenn, https://www.seas.upenn.edu/~cis194/fall16/ • Haskell Programming from first principles, http://haskellbook.com/ • Real World Haskell, http://book.realworldhaskell.org/

RWH is great up to Chapter 4 at which point the wheels come off. LYAH is much better.

Re: How I learned to code in my 30s

#115
I've been programming for 13 years. I started when I was 14 years old and studied software engineering at university. These days, when I take on well-paid contract work, sometimes I find myself working alongside people who only started learning to code at around 25 and never went to university.

It's upsetting for me to think of all the fun I missed out on in my early life because I was learning programming and pushing myself through university and it turns out that it doesn't even get me a higher pay check in the end.

These days, nobody cares that I'm proficient in all of ActionScript 2 , ActionScript 3, C/C++, C#, Java, Python, AVR studio (microcontroller programming), MySQL, Postgres, MongoDB, RethinkDB, PHP, Zend, Kohana, CakePHP, HTML, CSS, Docker, Kubernetes, AWS, JavaScript, Node.js, Backbone, CanJS, Angular 1, Angular 2, Polymer, React, Artificial Neural Networks, decision trees, evolutionary computation, times/space complexity, ADTs, 3D shaders programming with OpenGL, 3D transformations with matrices, image processing... I can't even list them all. I could wipe out 95% of these skills from my memory and get paid the same.

It only gives me extra flexibility... Which it turns out I don't need because I only really need two of these languages (C/C++ and JavaScript) and a couple of databases.

Re: How I learned to code in my 30s

#116

Reading that makes me glad to be a network engineer. Ethernet, BGP, and OSPF don't change all that much. I am all for learning the latest Python, NetMiko, NAPALM stuff for network automation. This article reads like masochism.

mother earth is pregnant for the third time...

Re: How I learned to code in my 30s

#117

I've been programming for 13 years. I started when I was 14 years old and studied software engineering at university. These days, when I take on well-paid contract work, sometimes I find myself working alongside people who only started learning to code at around 25 and never went to university. It's upsetting for me to think of all the fun I missed out on in my early life because I was learning programming and pushin…

Yes but you can use your advantages. It's only about finding the right opportunity.

Re: How I learned to code in my 30s

#118

I've been programming for 13 years. I started when I was 14 years old and studied software engineering at university. These days, when I take on well-paid contract work, sometimes I find myself working alongside people who only started learning to code at around 25 and never went to university. It's upsetting for me to think of all the fun I missed out on in my early life because I was learning programming and pushin…

A lot has changed in the past 5 years or so. Anecdotally, 5 years ago I'd bet that 90% of programmers either had a CS background or something very similar (ECE or Comp. Eng.).

Today, I think that number is down to 50% or maybe even less. So many of my friends who went to excellent schools but had degrees in Biology, Biotech, Physics, and even some social degrees (including a pianist) now are full-time programmers.

I agree with your sentiment though; if you don't need a CS degree to get a CS job, then maybe try something else during college. Take programming courses at your local coding bootcamp.

Re: How I learned to code in my 30s

#119

I've been programming for 13 years. I started when I was 14 years old and studied software engineering at university. These days, when I take on well-paid contract work, sometimes I find myself working alongside people who only started learning to code at around 25 and never went to university. It's upsetting for me to think of all the fun I missed out on in my early life because I was learning programming and pushin…

So you did learn programming, because you wanted a great paycheck 13 years later? Lol, that's just stupid. I advised everyone from my circle to stay away from programming unless they fell in love with it. It's pointless to be a programmer if you don't have it in your heart.

However, if you did enjoy, then there is nothing to be upset about, I mean you are doing what you love right? If its all about your paycheck you could try finding another employer, but not everything in this life should go around money, there are more important things, find people who could appreciate you and your values, be happy what you do and maybe the money will come later.

Re: How I learned to code in my 30s

#120
post #42

I started to learn to code last November at 37yo. About 30 hours a week for two months I finished the Front End Certificate from freeCodeCamp (highly recommend the site for starters). Then I decided it was better to build my own projects with the tech I wanted to learn (mostly React) using official documentation and tutorials. This is what I accomplished in around 3 months: www.rodrigo-pontes.glitch.me Then I started…

It looks like you've learned a lot, but a lot of people are going to criticize you based off your design skills. Frankly, it's ugly so you're automatically not going to be doing any product work. If you could clean up your demos to look more acceptable to the modern day reviewer, I think you would have better presented yourself.

It's better than my first website.
Post reply on HN