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.

I tried to enter the field at 35. I couldn’t get an interview with a CS degree. I did everything right. Good GPA. Portfolio. Professional resume help. Sent applications for two years and heard nothing. Now I’m 45 with nothing to show for it. All those late nights studying coding interview questions and I never got a chance to try.

The success stories you hear are people with friends or family members who get them through the door. Unless you know someone like this, give up now and don’t waste your time.

Looking back what has helped me a lot is being surrounded by more experienced engineers that were good at teaching (those are quite rare I discovered later). Other than that, read a lot of code, write a lot of code, and keep reflecting on what areas to further develop. Be kind to yourself, this space is huge and no one’s is an expert in all of it. Burn out is real, especially when struggling alone for too long. One thing that has helped me as well is to realise everything in software engineering has been made by humans. None of it is actually ‘unknown magic’, just keep digging deeper to find out how the thing you’re struggling with works on a more fundamental level. The LLM age has made this so much easier.

I’ve started to see this myself. I’m certain it’s ageism.

To the OP, if you’re passionate about it, don’t let anyone/thing stand in your way.

- the Python courses got me up-to-speed on the basics of that language: https://ocw.mit.edu/courses/6-0001-introduction-to-computer-... and https://ocw.mit.edu/courses/6-100l-introduction-to-cs-and-pr...

- Structure and Interpretation of Computer Programs served as a disciplined review of a book which I wasn't patient enough to do the exercises of when I first read it: https://ocw.mit.edu/courses/6-001-structure-and-interpretati...

- Mathematics for Computer Science helped make up for my spotty math: https://ocw.mit.edu/courses/6-042j-mathematics-for-computer-...

I've also found the recent book:

https://www.goodreads.com/book/show/39996759-a-philosophy-of...

very helpful (first reading I did one chapter at a time, re-writing my current project applying the principles of that chapter) --- interesting video overview at:

https://www.youtube.com/watch?v=bmSAYlu0NcY

If one is fortunate, there are videos on specific subjects/algorithms which one needs, e.g.,

https://www.youtube.com/watch?v=jvPPXbo87ds

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.

We turn away the latter more and more these days. In the past, hiring a junior software engineer meant you were probably getting an enthusiast of some sort, the kind of person who had their own side projects and crazy ideas they worked on for fun, and would stay up late into the night just coding. But now with the surging supply of new computer science grads, there’s a lot of people that just want to log in, crush tickets, and go home. And AI is making it worse. They have no love for the science, just a steady paycheck. But the truth is that in this industry, if you really want to push the boundaries of what is possible, love is an important ingredient. And not just for your company, but for yourself.

Learning CS means starting with the math, particularly for folks long out of school (the famous quote, "Computer science is no more about computers than astronomy is about telescopes"). If that doesn't sound fun then you probably just want to spend your time with coding tutorials instead. CS is... a science. Software is engineering.

>I am mindful of the ageist tendencies in the tech industry [...]

These two claims seem at odds to me. If you're not aiming at getting a job, why does it matter to you what the tendencies of the tech industry are?

However, it was a hard road, and I travelled it when conditions for developers were much better. Along the way, I made some missteps, and followed the wrong path a few times out of sheer lack of industry experience. I had to make the kinds of mistakes you usually make at 22, but at that age everyone you know is also going through the same experience so it feels like everyone is going through it together. It’s a lonelier road when everyone you know is hitting senior/executive/management/ownership level and you’re back trying to figure out how to find your footing on the first rungs of the ladder. I didn’t love the work I used to do, but I was becoming respected when I left it and would have done quite well, so for _years_ I had the constant nagging doubt that I had made the wrong choice and that maybe the grass wasn’t greener after all.

That’s my experience. If you wanted advice (which you can ignore a la “wear sunscreen”), I’d tell you to keep your current job while you work on your passion projects. Try to get involved with dev meetups. You want to see if you want to become one of those people, and you want to see if the stuff you’re doing gets any kind of traction. Meetups will help you figure out how to sound like a developer, which can be more important than it should be. You will have to fit in with developers to get past interviews if you’re looking for a job.

Whatever you decide to do, best of luck. I hope it all works out for you!

I started programming when I was five years old, so I kind of fit the "whiz kid" profile that everybody thought all programmers would be back in the 80s. But one of the things I've noticed, is that unlike the situation, say, in Boston, where it was easy to find other former "whiz kids", when I attend tech meetups near my current city what I find is that almost all of them started programming in mid-adulthood, say mid-thirties to forties. Many of them even went to the same boot camp. But the joy and wonder they experience mirrors what I experienced at age five, poking at my Crazy Eddie's-issued VIC-20. I am utterly delighted by this discovery, as it lends further credence to the idea in my head that programming is something deeply satisfying to the human soul.

Find a job at a company, any job you qualify for, that has an IT department where you want to work. Make friends in the IT department and see if you can get the manager there to offer you an entry-level position once you learn what you need to know to do the job. Being a good employee in one department can take you a long way if you want to transfer to another.

Additionally, give yourself a deadline. Do not leave it open-ended; it's too easy to meander and get nowhere. It's also unfair to your wife to carry the load indefinitely. Plan out your journey before you quit your current job and stick to it.

FYI, programing as a job is no where nearly the same as programming as a hobby. The job is full of pressure to get things done and you write code you may have little interest in.

Good luck!

There is lot to unpack from the comment threads below and I will be doing that in the coming days. As recommended by several of you, I have also added an RSS feed on my blog to help you follow my journey.

Thanks!

That tells me that you have had some fairly good matriculated schooling. I have been doing heavy-duty software engineering for decades, and am not qualified to teach math, science, or, surprisingly, computers, to primary students.

"Computer Science" isn't really "programming." It's the theory behind things, not just implementation. I don't consider myself to be a "computer scientist," although I know a lot of the stuff they do. My focus has always been on deliverables. In some cases, that's more valuable for getting paid, in other cases (like in academia, or the R&D sections of companies), maybe not so much.

I'm 63, and still learn new stuff every day. I choose to concentrate on deliverables, as opposed to theory, but that's me.

I would suggest that if you want to be at the pointy end, then it's not really about delivering product. That's not always using the latest $BUZZWORD technology, or giving up, when it gets annoying and boring. For me, I find great satisfaction, in delivering end-user product.

For many others, here, they are far more interested in developing theoretical lattices and engines; which is extremely valuable. We need all types, to advance the craft. You also get to play with the best toys.

I would suggest thinking about what the end goal is, then focusing the learning on that.

That said, I know someone who started learning programming around 43. They enrolled in a local government-sponsored technical program that partnered with companies to offer internships. They trained hard, took an internship, and worked their way in — even though it took them over 3 years before they saw any meaningful income.

Now, about five years later, they’re doing well: they’ve earned several certifications, built a strong cv, and landed work at a company with a big name. On paper, they look impressive — even compared to me, and I’ve been programming since I was 13 and working professionally since 17.

But here's the thing: that path takes grit. They didn’t save much during those early years and had to stick it out for a long time before things clicked. Unless you’ve got real motivation and curiosity driving you, it might be a frustrating ride. If you do have that passion, though — go for it. Just do it with eyes open, and don’t expect shortcuts. this guy was passionate about money and he was always crap on interviews but he went through the internship route and now he's doing fine. I started at 13 but I didn't start making six figures until I was 20.

Remember: Even Hodor could not clear an interview these days, despite being perfectly aligned to his job role, but he got hired long-term via practical execution. and well, spoiler alert- his fate is pretty much every programmer's fate. To be eaten alive by.... LLMs?

To be honest, what I hear in the paragraphs that follow is less a description of yourself than the pronouncement that you are capable, curious, and driven to learn more, that you're excited and motivated by the breadth and depth of tech -- that there's so much to learn and so much to study and you want to know all of it. That's a wonderful starting point, but it also sounds as though you are or will be prone to a kind of paralysis.

You have a list of projects you want to work on. This is good. Study will give you a foundation (personally, I found DS&A, once I approached it methodically and patiently, by far the funnest part of learning programming and CS, so projects aren't the only way), but building will give you something to put on top of it, figuratively speaking.

Just keep on mind that you're probably not going to build these things from first principles, so you're probably not going to learn operating systems, networking, or programming languages. Rather, your going to develop skill in specific tools rely onthose technologies. That's fine. But if you really do want to dig very specifically into the subjects and technologies themselves, then you needto be aware that building the products or projects you've described isn't going to give you the progress you seem to want.

If you really do want to know networking, don't build a website; implement, I don't know, telnet or tcp/ip from scratch after reading the spec. If you really want to know operating systems, build one. If you want to understand programming languages, DS&A, and algorithmic analysis, familiarize yourself with some instruction sets; learn discrete math; learn what lambda calcus is and how it's used.

> Adult ADHD

I have severe ADHD. I could not survive in the tech world without treatment and medication. YMMV, but you should get treatment if you haven't already. Last time I checked, there was essentially no empirical evidence supporting the coping strategies so many people advocate. Medication is the one, and the only, proven treatment for the condition.

Sure you need the general sense for architecture which comes from experience, but it is not a long list. Learning about computer hardware and assembly from scratch is what made it all come together for me. Algorithmic complexity, data structures, development tools were all a mystery and "just things to memorize" until I learned about logic gates, developed transistors from those logic gates to get memory circuits, developed binary full adders, a bus, a basic cpu with a few registers and a program pointer and actually programmed it with its own instruction set. All you really need for this is pen and paper. Then move on to multicore, multiprocess, scheduling, then move to simd and graphics hardware. If you have several months to dedicate, I'd say go for that.

That's a recipe for soul-crushing long-term unemployment.

TBH journeyman computer work today is plumbing with tools that go stale fast, or perhaps making tools to do the same thing better with less.

By contrast, medicine is now the biggest employer, largely because it's difficult to automate that kind of personal touch, and b/c in the US the population is aging. While being a provider involves training & certification, there are a number of provider-adjacent jobs in logistics and related counseling (e.g., genetic counselors, IT) where you can use your people and explaining skills. All of medicine now is highly technical, so there's plenty to learn, and that knowledge is much more interesting and relevant than CS or programming.

https://www.instagram.com/arcadenest_games/

I find my age to be great period to learn new skills. It is never too late.

So it can be done! However, I had already been working as a tech (not programming though, more networks and sales tech support) for years, so it’s not like I had to learn what a CPU is.

2. Math, Tensors (you'll get why later) and Matrix Transformations, and all that sin cos tan stuff

3. Ben Eater-ish stuff on YT because it's 2025 and Computer Science is about to (you are ADHD, so anything from 2 days to 7 years) change without anybody noticing ... think AIs having a preference for certain voltage drops and materials ... ... ...

4. the while 37-year-old part is irrelevant because, again, it's 2025, and pretty much any PhD can be caught up with within 10000 hours aka 3-4 years ...

5. you should start a reddit thread where people suggest stuff you SHOULD do instead of CS and thinking in general and some rich guy should hire some people to remind you of all those suggestions multiple times a day

It is for academics, those looking to differentiate themselves from the other 2000 CS equipped applicants for a job, those wanting interviews answering useless data structure and algorithm questions, and those writing applications in the domains of the computer and data sciences, and computing infrastructure.

Most software is outside of this, though that might surprise many HNs who assume that is the only type of software there is. Well maybe they will cough up “crud apps” if pushed.

Just learn to program and learn the applicable standard libraries associated with a programming language. Stop overthinking it. An 8 year old can do it - you can too.

Good luck with it!

More than anything, what a self-starter community-taught coder needs is motivation, curiosity, and access to resources. It does not matter where you begin, so long as you have enough stuff to take the next step.

OP, as you've said so yourself, the places you can go are vast! And it's no small thing to have already made working things! Now is the time to play, discover what you like and don't like, start projects and abandon them, go down rabbit holes, get stuck and frustrated, to over-romanticize, to become bored, to feel like an imposter, to become jaded but then to be inspired again, and to experience the magic of making.

I wish you luck and thank you for sharing. I'm excited to learn from you!

I noticed this line at the end of the article about the things you would like to build: “Education apps that leverage learning theories, community learning and game design to make learning more inspiring and accessible for students”

That’s a perfect description of mathacademy.

You can get one of these ideas _done_ at a basic level, including learning time, in about four months.

Start with Laravel, use Livewire, and use Laracasts as a starting point.

You got this!

I'd encourage you to find a local user group in your area. You need a few people that can help you avoid dead ends of which there are many when you are starting from a blank state. In general there are going to be a couple of people that enjoy helping people learn. I've run a local user group for a quarter century and I always have gone out of my way to help newcomers.

My experience is that it is far easier than asking questions online. There are people for whatever reason love to criticize folks asking beginner questions. I have never understood that behavior but it serves to discourage people. I've experienced it myself when trying to learn something new and it is counterproductive.

We are similar in a few ways. I love to build things and I also spent the early part of my career as a mathematics / computer science teacher (mostly web development...HMTL, CSS, JS). After teaching for six years, I transitioned into business (marketing) and now I'm employed as a website manager where my understanding of high level coding concepts allows me to communicate with our development team, but I'm not actually writing the code (though in most simple situations, I probably could).

To satisfy my need to build things and write code, I work on small, side projects. I recently built a near pixel perfect clone of Frogger with Pygame to better understand game design best practices and leverage ChatGPT for the first time (though, to be clear, none of the code was written by ChatGPT).

My advice to you would be as follows...

1. Try to have a narrow focus so you aren't overwhelmed. Don't go into this with a "I'm going to learn EVERYTHING!" attitude. Have a specific focus.

2. There are a lot of fundamental "best practices" that need to be automatic. Build lots of smaller projects and doing so with a language like Python (so you aren't also wrestling with the idiosyncrasies of the language) is a good approach.

3. Of course continue working. If you aren't planning to be a professional software developer, is there another choice?

4. Use AI, but NOT to write your code. Rather, use AI to critique your work bearing in mind the responses you get aren't always perfect. And sometimes you won't realize that until a month or two later and that's ok.

5. Find others with similar aspirations to partner with so you can hold each other accountable. Going on such a journey alone has always doomed me. With life, family, work, etc, I've never been able to sustain my enthusiasm.

6. Writing some crappy, novice coded little nothing project thing is infinitely better than writing nothing. Movement is critical. Just keep coding. There will be good days and bad days, but don't stop moving.

Feel free to reach out if you want to chat about my experience. As I said, I see a number of parallels. Best of luck!

As a UX designer, I've worked with developers for a long time, so I've picked up knowledge along the way. I've read some books and merged some PRs at work but nothing that would qualify me as a developer.

What am I'm having a lot fun with right now though is building with LLMs. If I have an idea, I'll just throw it into Replit or Claude Code to see what it comes up with and then decide if I want to pursue it further.

My 2 cents: learn by building. Start working down your list of ideas and dig deeper into questions and topics that come up. Will probably keep things more interesting than slogging through a course.

One advantage you have over senior developers is that senior developers need to be generalists, you have the opportunity to go deep. It is entirely conceivable you could learn Postgres, JavaScript, or Python better than someone who has been programming in those languages daily for over a decade simply because they have a lot of other things to worry about. They can't read the manual cover to cover, no time. You can. Being a deep specialist in a technology has a lot of value.

If you find a programming community you love, start going to conferences as soon as possible. There are often financial opportunities available for new developers.

This is not going to happen overnight. In most cases to get proficient you can expect that working 3 hours a day, 3 days per week, it will take you about 3 years to reach a point where you might be employable -- although you will probably find you need to put in more time than that. But you can reach a point where it is enjoyable before then.

Good luck.

[1]: https://dabeaz.com/advprog.html

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.

Jimi Hendrix never learned to read music. He did not know how to 'construct a chord'. He had no music theory training. He just made music, and learned what he needed along the way to make the music he wanted. He did this from scratch in less than 12 years (ages 15 to 27).

TL;DR: computer science and 'building things' are two different things. Let your urge to build things and your interests guide what and how you learn, not academic traditions.

Okay, any other questions? ;o)

Also while I would not start a project in C understanding the memory model and how to implement basic data structures in it is s.th. every programmer should know IMHO.

The answer actually is, maybe, depending on what you want to do.

You’d certainly want to understand and have a strong intuition for physics, but knowing how to solve a differential equation isn’t going to necessarily make you a better mechanic. Understanding the concepts of what you’re solving might, but the raw technical calculus skill will most likely not

I’m not saying this to discourage you, simply throwing it out there for you to keep in mind as you embark on your journey. A lot of the coding that happens day to day is SV is more akin to a mechanic working in the ship than a physicist in the laboratory (or in front of the chalkboard) and I guess it’s just my way of saying to stay vigilant that what you’re studying will enable you to achieve your goals.

Only you know them and you very well may need extra physics for the type of work you want to do - definitely not saying that’s not possible

A lot of people in the valley make people feel like if they don’t have a cs degree they aren’t real coders and shouldn’t be allowed within 50 miles of contributing code. Just so you know this is bullshit :)

I’ve come across all types of devs - from high school drop outs to egghead Phds and I’ve seen awesome and terrible work from both camps

I've been meaning to do a write-up or something, but there's never a right time. I'd write more, but I'm at a festival r/n. Hit me up if you want some (hopefully useful tips).

My whole life I’ve known I was an engineer. However, for a great chunk of the early years I couldn’t express that and did really badly at school.

I just learnt at my own pace and eventually worked as an electronics engineer in the broadcast industry. Then quit that and moved into sw dev.

One piece of advice is to just build stuff, fail and learn.

Good luck

Edit: and algorithms

Writing blog posts like this is a form of procrastination, and distracts from your stated goal.

From your objectives, I don’t think you want to learn computer science, you want to learn how to be a full stack software developer.

Learning certain aspects of computer science may certainly help you, but it’s by no means a prerequisite - and won’t help you to actually build things.

Learn the things you aim towards by doing and reading domain specific knowledge.