Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How I learned to code in my 30s

medium.com

Post reply on HN
Print view View original

71–80 of 208 posts

Re: How I learned to code in my 30s

#71

Post by ice109 »

jarsin wrote: post #57
ice109 wrote: post #38

Earlier quoted context omitted.

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.

I honestly have never worked with anyone in software like that. I think you are a lot more rare than you know at least when it comes to software dev. But I do know other industries are filled with smart people that hate it and somehow stuck with it only for the money. For example attorneys...

coincidentally enough i considered law school before i considered my ms in cs :)

Re: How I learned to code in my 30s

#72

Post by bricestacey »

soneca wrote: 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.

Re: How I learned to code in my 30s

#73

Post by nstj »

brandonmenc wrote: post #65

When computers were invented, a lot of the people involved were already adults - plenty in their 40s and above. Before home computers, you didn't get to use a computer until your 20s. Therefore, the first few waves of programmers included a lot of "already olds." This is always overlooked as evidence that older people can learn to program.

This is a terrific observation - really should be the top voted comment.

Re: How I learned to code in my 30s

#74

Post by bradcrispin »

soneca wrote: 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…

I think you have accomplished the hardest part. Action is now your reward. :)

Re: How I learned to code in my 30s

#75

Post by bradcrispin »

ronilan wrote: post #39
bradcrispin wrote: post #32

I once said that "I realize nothing I do in engineering will ever end up on the front page of Hacker News." Feels like a once-in-a-lifetime moment. Thank you

Been there at the top once upon a time. "We create our own demons."

I couldn't agree more. I had a few paragraphs on impostor syndrome that I edited down to "doubt" but I hope it was implied, you must ignore impostor syndrome. There are always going to be people doing Mount Olympus code and that is great! These are the people we can learn from. I get to build things people use and I love it.

Re: How I learned to code in my 30s

#76

Post by anarazel »

bitcrusher wrote: post #34
koolba wrote: post #29

Earlier quoted context omitted.

That's the distinction of coding vs CS. Building CRUD apps using existing frameworks is coding. Building said frameworks and the rest of the software that powers those CRUD apps takes more. I don't mean to rag on simple projects or coding either. It's just as noble as any other profession. But to say that a random Rails or Node developer could write something like Postgres is laughable. It's not the degree that makes…

I don't mean to belittle you either, but this is hogwash. Of course a Rails or Node developer wouldn't be able to write Postgres without ramp-up time... Maybe what you're saying is that the ramp-up time would be LONGER for someone starting from Rails or Node only knowledge to being an infrastructure developer? Any highly sophisticated application ( Postgres, LLVM, etc ) requires some advanced levels of domain knowled…

> Any highly sophisticated application ( Postgres, LLVM, etc ) requires some advanced levels of domain knowledge but they aren't impenetrable fortresses of skill that no mere mortals can access.

Indeed. I think too many problems in our industry are seen as unapproachable. There's a lot of people working on postgres, me included, who did not have any sort of deep background in databases before. You start working on smaller things (I started making int -> text conversion faster), review other people's patches, start to develop new features, ... Gradually that gives you a more and more knowledge in database architecture. And you read a few good papers here and there.

Obviously that approach doesn't really lend itself to writing something like postgres from scratch - but realistically that's not something you're going to do on your own anyway. And if you do start a new project you don't set out to do something absolutely complete, but build it iteratively. With more domain knowledge, you're more likely to get the architecture halfway right initially, but in either case you're going to have to redesign and redesign and redesign.

Re: How I learned to code in my 30s

#77

Post by tuananh »

xxSparkleSxx wrote: post #67
tuananh wrote: post #25

Earlier quoted context omitted.

I find CS knowledge useful only when you tackle hard problems. Only then, CS and mathematics knowledge will come to play. You don't need a CS degree to make a website.

I don't even think it's that necessary to solve hard problems, at least in most fields. You can do a lot with general coding knowledge, however, I've found the CS fundamentals to be most useful for optimization.

it depends on what do we define as "hard problems"

Re: How I learned to code in my 30s

#78

Post by inimino »

jamestimmins wrote: post #64
jordache wrote: post #56

Is a full stack person still realistic with today's web technologies? I mean to build up expert level skillset, you'd have to really dedicate your self into learning the particularities of not just languages but also their runtime environments. Unless you have no life, and only sleep, eat, code, or super intelligent, being able to absorb and stay current with everything..... Other than that, I just don't see the full…

The value of being a full stack dev is not to be an expert in everything, as you're right that isn't really feasible. The value comes from being able to do a good job at each piece, so that you can take an entire project from concept to completion. Most full stack folks naturally develop areas of strength and focus within that, either frontend or backend, but still benefit from the fullstack context and mindset. That…

It is absolutely feasible.

Re: How I learned to code in my 30s

#79

Post by bradcrispin »

colmvp wrote: post #52

> Immersion means 100% focus. If possible, no friends, no drinking, no TV, just reading and writing code. If you take five minutes off to read the news, be aware you are breaking the mental state of immersion. Stay focused, be patient, your mind will adapt. Eliminate all distractions, of which you may find doubt to be the loudest. Immersion is the difference between success and failure. Certainly, I think Deep Work r…

I agree that for rapid learning, focus and repetition are essential. I don't think you have to quit your job in order to change careers into coding, but for me it took a very full year of effort.

Re: How I learned to code in my 30s

#80

Post by paul7986 »

At 31 I took my savings for my house, quit my robotic customer service job and started a startup. I worked on my 1st startup for three years and along the way taught myself front end development and design. Which I now do for a living.

I say startup and if it fails like 80 to 90% due you gained an in-demand skill that you can use to make a nice living.

Post reply on HN