Live data from Hacker News

A 37-year-old wanting to learn computer science

initcoder.com

11–20 of 190 posts

Re: A 37-year-old wanting to learn computer science

#11
post #9

Stop writing about how you're going to do this, and just do it. Everything you need is available online. Writing blog posts like this is a form of procrastination, and distracts from your stated goal.

Blogging about your work can be great, and they haven't actually stalled out yet so you're being too cynical.

Re: A 37-year-old wanting to learn computer science

#13
Good luck.

I'd recommend finding a MOOC course that covers some of the fundamentals of computer science to make sure you have a really solid grasp of the fundamentals - the whys and how's etc. Data structures, algorithms, networking, databases, design paradigms (so Object orientated Vs functional Vs whatever), testing etc. If they use multiple programming languages in different classes then all the better as I think learning more than one makes it easier to grasp the principles at a more theoretical/abstract level and not just how language foo does it and you'll find your favourite language(s) eventually in your own time so don't give up if the class is in a language you don't know/like.

It's tempting to use AI - I'd recommend you think of it as a knowledgeable friend who you can ask questions - is there a better way to do this/what alternatives are there? What does this function do? Why does this code do this and not that etc etc. You won't learn if it just implements for you, but as a learning companion you can bounce ideas off of or help you out of a rut etc it is great.

It is tempting to concentrate on like a React Bootcamp or whatever to get "practical skills" to start going off and building things, but I think that is like the difference of being the person who is paid to only assemble flat pack furniture following instructions vs the person who is paid to design the flat pack furniture and all the smart little fittings and how it all goes together and will it be strong enough and fit in the box and meet the price point and look like what the designer wanted it to look like and so on.

Finally, don't worry about writing "bad code" or bugs. We all do it from time to time and no one is perfect.

Re: A 37-year-old wanting to learn computer science

#14
post #9

Stop writing about how you're going to do this, and just do it. Everything you need is available online. Writing blog posts like this is a form of procrastination, and distracts from your stated goal.

> I designed this website on my own as well while reading the book Refactoring UI [2]. This took me almost 4 months.

They have built something and they have used that something to shape a plan for achieving their goal. "Stated goal" and "just do it," are mutually consistent with "writing blog posts like this..."

Re: A 37-year-old wanting to learn computer science

#15
In a good economy, one year is more than enough time to get a job (considering most bootcamps are 12 weeks, and I know a lot of bootcamp graduates who are employed as developers.) Learning on the job can be beneficial as you usually have others to learn with, and learning is contextualized.

Good luck with it!

Re: A 37-year-old wanting to learn computer science

#16
In some sense blog posts like this shouldn't even need to exist, or the doubt you can read between the lines. At 37 you're a decade and a half into adult life, you probably got like 50 years left or who knows how much with what the future will bring.

That people who haven't even reached middle age yet are already mindful of ageism when it comes to reinventing themselves is just crazy. There's something messed up in our culture around age. It's one thing I enjoyed about chess growing up. Chess clubs are one of the places where you genuinely meet people at every age and skill level and they don't feel like they need to justify it.

Re: A 37-year-old wanting to learn computer science

#20
> My lovely wife ([…] who believes I have adult ADHD) is supportive of my journey, and has no qualms becoming the only breadwinner of the family.

Some advice for the OP:

1. Don’t give up working. IMO, a job provides structure to the ADHD and keeps you moving forward instead of spinning your wheels. Change job? Sure. Work 25 hours/week? Sure. Not 0 though.

2. Before you start on the projects, spend some time learning how to design programs. I like HtDP.org but it’s kind of oriented to a class setting.

3. OSSU could be the project of a lifetime. Beware getting sucked in there. That said, some of the courses referenced are excellent. Knowing ALL of them is a lot.

4. Have an exit plan if you are not working. When will you work again? Some bad scenarios are less horrible if you are ready to jump back into the workforce.

Post reply on HN