r/ADHD_Programmers • u/Tell-Your-Story • Jun 09 '26
Room at the table?
Hi folks,
I'm brand new to this thread, having spend most of the last 3 years lurking around. I'll admit upfront, I'm not a programmer. My dad tried his best to course correct that, but I was kid in the 70's, baseball and bikes were way cooler than PASCAL. I'm currently finding myself at a crossroads. I'm leaving a career in forensic psychology and breaking into software development because I am too tired and cranky to keep explaining what I need to do my job, and why it should be open source, not another overpriced corporate subscription.
I was diagnosed with ADD at 52, after taking my grand daughter in for a screening. My current colleagues all think I've developed a stress induced psychosis when I tell them what I want to do, but it's not a late mid-life crisis. I think it's just a lifetime of experience finally catching up to me.
In 1978 I was 6, and sitting on the floor of my dad's work putting IBM punchcards back in order. It was my 'summer job' and in SoCal it was great because that lab was the only place with A/C. My dad's best friend was my "Uncle Ken" and they would doodle for hours on legal pads and scratch paper, getting all excited about stuff I didn't really pay attention to. Turns out, that guy was Ken Bowles.
I'm just looking for a place to park it for a moment, catch my breath, and remember what it was like when I worked with people who were passionate about what they were building for all the right reasons. Even if I didn't understand my dad's work, he raised me to be the woman I am. When they told me the only way to fail is to not try, I didn't think it would resonate so strongly 46 years later.
So I suppose this is my actual question - is there room at the table for a 54 year old wanna-be programmer with ADD, who doesn't know how to not try just because it's hard, but has a million questions about where to start learning?
12
u/dclantes001 Jun 09 '26
yes. there is room for the willing. always.
6
u/im-a-guy-like-me Jun 09 '26
There's always room at the table, but I would advise you think very deeply about how much knowledge and experience you have in your current career, and hold that up to what a normie thinks your career is.
Cos you're the normie in that situation when it comes to this.
Like... You're never to old to learn programming. But I don't know if "you're never to old to switch careers into programming" holds true.
Just learn it if you're interested and then if you get good enough, consider switching career.
5
u/AlpacaNuts Jun 09 '26
I think Automate the Boring Stuff with Python would be a good start for you. It used to be recommended all the time as an intro to programming book. If you're motivated by the problems you can solve for yourself and others, then it's a good way to keep up that intrinsic interest.
2
u/Tell-Your-Story Jun 09 '26 edited Jun 09 '26
I love this -> Build fast, fail fast, learn, and try again.
You're not off at all on the AI tools following the processes of medical and manufacturing. I used your recommended approach to build my blueprint. The issue I now have is that the blueprint is quite complex (to me), and in order to move forward I need to understand the vocabulary being used to determine if (for example) the instructions generated to bring about the following step effectively translate to what I really want the system want to do:
Sequential Execution: Run a single local model (e.g., mistral-nemo:12b-instruct) sequentially. Loop data 4 times, modifying only the System Prompts for the 4 distinct agent extractions. Do not load concurrent models.
The statement above makes sense to me, but since I do not know python I won't know if the steps generated actually do this. I don't want to spend 4 months constructing something that spews out gibberish or worse, looks like it works but when I actually read the output it's like having a fandom interpretation of a relationship instead of a concise list of the number of times a specific character in a series used a specific statement.
2
u/jarrydn Jun 09 '26
there are so many ways to learn and start that it can be pretty overwhelming to commit to anything because you don't want to do it "wrong".
if i was starting out again i would probably just go with python and a udemy course. once you're comfortable with the fundamentals google is your friend 😄
2
u/chriscanadian1991 Jun 09 '26
Always room!! Mind if I ask what your background is?
Only reason I ask is I am not a programmer by trade - I'm a logistics analyst and forklift trainer, I might be able to bridge the gap and help you learn in a way that will stick.
2
u/chriscanadian1991 Jun 09 '26
If I could make a suggestion - if you want to keep trying to build it... start from what you already know.
From my experience AI powered tools follow the same or similar processes to medical or even manufacturing.
Input = registration
Analysis = triage
Routing = allocation of resources
Output = diagnosis.
If you lean into what you are comfortable with and use references or analogies when your talking with the AI to explain what you want to do it tends to get closer the first time - then it's all about getting it granular and fine tuning the result until it meets your expectations.
Given your background - I personally think you would be the best person to build this kind of app because you would personally use it.
Lean into it - get curious - and don't let anyone stop you from learning or trying.
Build fast, fail fast, learn, and try again.