Ask HN: Late-bloomer engineers, when and how did you discover programming?
11–20 of 44 posts
Re: Ask HN: Late-bloomer engineers, when and how did you discover programming?
#12I quickly realized being surrounded by amazingly smart people with passion for programming is way more beneficial than my masters. I stopped my masters, and started on a never-ending quest of computer science self education.
Every day, 1-2 hours after work, every weekend, 3-6 hours, I spend time on Coursera, EdX, math texbooks... Learning compilers, networking, iOS apps, JS, Java... whatever you give me, I'll learn.
7 years later, I have an "architect" in my title, my salary rose more than 3x. Still probably underpaid, but the pace of learning and opportunities I get far outweigh the salary (e.g. got certifications and trainings worth hundreds of thousands of dollars at this point).
I am also finishing a CS undergrad for fun in the evenings, but my resolve on that is waning. I can do the same for free on my own, minus the degree. I do like the math classes, which are far more rigorous than I'd be on my own. Other than that, it's been kind of meh.
Re: Ask HN: Late-bloomer engineers, when and how did you discover programming?
#13I was hitting snags trying to do analysis with excel and couldn’t vlookup or pivot on a table with a million rows. A friend mentioned in passing that python would make this pretty simple.
I started there and tried to solve problems I was facing with code instead of excel.
Fast forward a year or two having built a few projects on the side, quit my job and started selling software I built from scratch.
I found having a project to work on that solved problems I faced made the learning effort so much easier. I struggled early on trying to solve fizz buzz-type problems because I couldn’t see them solving problems I faced day to day.
I don’t code much anymore but having that arrow in my quiver changed my career trajectory significantly. I recommend learning as soon as possible!
Re: Ask HN: Late-bloomer engineers, when and how did you discover programming?
#14Re: Ask HN: Late-bloomer engineers, when and how did you discover programming?
#15At 26 I was studying criminal justice, then I had some health issues which would affect the physical aspect of the job, so I switched to CS. I used to think I was stupid because when I tried HTML everything seemed so hard and took long. Then in my CS program, while still dealing with health concerns I did exceptionally well in almost every course, always top of class and I learned that it is easier for me than others.
Before graduation I had job lined up. I am making decent money in non-tech but interviewed in quite a few companies and got offers, they never matched the amount I worked from home though, so I did not make the jump. I also realized I'm a pretty good self-learner and now read books and do online classes non-stop.
Re: Ask HN: Late-bloomer engineers, when and how did you discover programming?
#16Re: Ask HN: Late-bloomer engineers, when and how did you discover programming?
#17I didn't know what I wanted to do when I graduated high school. I just wanted to work. I tried community college but sorry burnt out. I tried business, welding, and IT. I passed a few classes, others I just quit attending. I had no goals or direction and super depressed I couldn't even get a job that made more than $11/hour. I worked probably 15 jobs total in my life by 21. In hindsight looking at it I think this mostly had to do with me wanting to be a priest but people talking me out of it. I struggled with religion ultimately just recanting allowing for myself to rebuild my purpose as a weird way of putting it.
I then got an assiciates degree in business and started working at a bank. From there I worked for a few years building up skills and experience. I got really good with Excel and realized a lot of what I was doing with the functions was very similar to programming. So the logic part and substituting variables was super easy for me to comprehend.
The thing I really appreciate about going back to school now is I know what's what. I know what matters and what doesn't. I had a fully laid out plan and understanding of the way in which I'd achieve my goal. It's so weird that the whole Corona issue didn't even put a dent in how I planned things out. I think it actually helped even get an internship. I'm still very green in terms of skill though. But I enjoy learning it because it's a skill. It's not like hypothetical nonsense they teach you in business classes.
Re: Ask HN: Late-bloomer engineers, when and how did you discover programming?
#18Re: Ask HN: Late-bloomer engineers, when and how did you discover programming?
#19And then in my late 20s I'm stuck with a program tearing through my customer records, overwriting values with empty fields and apparently at random. I was able to pull the script from the created username id that did the overwrites, and ultimately derive the flaw as being a 'match first instance by name' with no other restrictions (including overwrite protections in place for other end users, and ignoring things like same names in different states or intentional duplicates for regulatory or industry purposes).
So something didn't feel right that I was able to unravel what this script did wrong yet not be able to program it. When I found out how much the contractor made to write that sloppy POS, it was a career given.
How many fields can you say you doubled your salary with a job hop, really?
Re: Ask HN: Late-bloomer engineers, when and how did you discover programming?
#20I decided if I was going to make the switch I needed to learn something new. Having 2 years of Go experience puts me on a better position in the market. I can't compete with the guy/girl who's been writing Java for 13 years but I have SOME unique skills as a Go developer. That was my strategy at least.
Even though I wished I had started earlier, being a late bloomer has helped because;
1. I have better processes for learning concepts than I did when I was young, and so I can progress quickly.
2. I have a broader perspective. Seeing things from the business/customer side for so long stops me from building elaborate complex solutions for inconsequential problems that won't make it to production.