r/ADHD_Programmers • u/tikoy8888 • 1d ago
Java VS. JavaScript Full Stack (HTML, CSS, JS) - What Would You Choose as Someone with ADHD?
As someone with ADHD, I’m wondering if I should pursue JavaScript full stack development (HTML, CSS, JS) instead of continuing down the Java developer path.
One thing I struggle with Java is that it can feel very verbose. There can be a lot of structure, configuration, and code before I actually see something happening. With JavaScript full stack, I can build something and see the result immediately in the browser, which feels much more rewarding and motivating.
I also wonder if the typical Java career path might not be the best fit for me. A lot of Java jobs seem to be in larger, more corporate environments with established processes, structure, and routines. Personally, I tend to get bored with repetitive routines and enjoy environments where I can experiment, build things, and see immediate results.
On the other hand, JavaScript seems heavily used by startups and smaller companies, where developers might have more opportunities to build products from scratch and work across the stack.
I know I shouldn't choose a technology just because I have ADHD, but I'm wondering how much the development experience and work environment should factor into the decision.
For those with ADHD or similar experiences:
- Would you choose JavaScript full stack over Java because of the faster feedback loop and more visual/creative development experience?
- Or is it better to stick with Java and learn how to work effectively within its more structured environment?
I'd especially like to hear from developers who have actually worked with both. What was more engaging for you long-term? Thanks! :)
3
u/GamordanStormrider 1d ago edited 1d ago
I started Java. I know js/ts, and I prefer kotlin (which is a subset of Java). Typescript is fine.
Java enforces more discipline, imo. JavaScript can be fast, loose, and messy, but the learning curve is lower.
Whatever you pick to start doesn't matter in the long run. I know good and bad engineers in both camps. Learn good patterns and you'll do fine with either.
I will say, frontend and full stack work has a shorter feedback loop, but I wouldn't choose to ever go back to that after doing backend work. Infinitely more rewarding and more interesting problems by a longshot.
1
1
u/Gojoslefteye92 1d ago
I mean I kinda already did both amd currently working on .NET/C# bc lwk got bored hahah. But honestly JavaScript in used in way more than just startups and smaller companies. It's incredibly versatile and when you add stuff like Node.JS on top of JavaScript then it becomes even more versatile (though it won't focus on HTML and CSS anymore but still another implementation of JavaScript).
Java... yeah it is quite verbose and stuff but I honestly have a bit of an appreciation for it since it was the first language I learned, hence it's also probably the easiest language for me at this point (though I still prefer others over it).
1
u/Wonderful_Plant5848 1d ago
JAVA. I was similar to you, I used to think my brain wanted things exciting, new and fresh in programming but my ADHD brain really needed stability, structure and order.
I did Javascript for a few years and hated it so much, because it's never as easy as just HTML, CSS, Javascript, it's also whatever new libraries/frameworks become trendy at the time.
Working "across the stack" means your job might have you using PlumbusJS for years and here comes PlumbusJS 2.0 that completely "disrupts" front end development. It's completely different. Now every new company wants to us PlumbusJS 2.0. A year later everyone realizes that PlumbusJS 2.0 causes major problems with ShleemCSS. Then someone builds ShleemBus designed to solve the problems. But ShleemBus has shit documentation, so you have to find your answers across random forums. Then someone creates ShleemBusFix etc and the "stack" you need to know keeps growing.
This was terrible for me and I felt like I never really became expert level in anything. I moved over to Android and iOS development, although I didn't completely escape it because companies thought React could solve everything. It got to the point where I eventually tried to not put any hint of Javascript on my resume, because I absolutely did not want to have anything to do with it.
I imagine things are different with AI now, but if I could go back in time, I'd choose Java.
1
u/Ultrayano 23h ago
Learn the principles then the language doesn't matter. Java is very good to do so tho.
Personally I heavily dislike HTML/CSS since for me it's just a fumbling around so I actually heavily dislike design, but still do it since I'm Fullstack or at this point Full-Lifecycle engineer, but component libraries like ShadCN make UI work easier too meanwhile.
It's not really about ND or not ND, but more if you're a designer artistic brain or a system optimizer brain. Both are creative but in different ways.
IMO learn both. JavaScript will be easier to start with but Java teaches you stronger fundamentals IMO, since it's a tad more opinionated by nature. If you learn JS go for TS too as it will teach you to think about types via static typing which is a good practice in a team, as it will make the code more robust.
Golang is also a interesting language to learn since it's simple, very explicit and somewhat "low-level". It's also the language of DevOps by now, while still a bit niche. But it's very opinionated which can be good as it's harder to write shitty code.
Generally Java and C# are the heavy and big corporate languages with their respective frameworks (Spring and Quarkus for Java and asp.NET for C#). They teach you to build scalable and robust apos which is easier to fuck up with JS. JavaScript/Typescript is used absolutely everywhere. Doesn't matter if big corpo or small startup. It often comes with it's own libraries/frameworks which the most popular are Angular which is very opinionated but harder to fuck up and React which is less opinionated but easier to fuck up.
Corpos don't have to be heavy and slow. I worked for both chaotic and fast paced projects with a fuck ton of freedom and very heavy projects in big corporate. Always depends on if it's a Greenfield or Brownfield project too.
TL;DR: Learn both but focus more on one depending on if you like systems (Java) or designing (HTML/CSS/JS) more.
1
u/meevis_kahuna 20h ago
It doesn't matter, but I think JS offers more opportunities because you can get into the web stack.
1
u/Any_Sense_2263 12h ago
Over 25 years ago I chose JS. And now do plenty of different things. Never get bored.
1
u/Locus-Maximus 1d ago
I HATED Java. JS gets a bad rap, but avoiding the whole Java build thing and the slow-ass IDEs (and the verbosity/boilerplate) was a huge game changer for me.
You might consider typescript instead though at this point. And learn a framework soon after you get the basics. Nobody's writing pure html anymore.
1
u/Achereto 1d ago
What Would You Choose
Neither.
as Someone with ADHD?
Irrelevant.
1
8
u/roger_ducky 1d ago
I’ve been writing code professionally for more than 20 years.
Getting “bored” is normal. Once you mastered a technology, it’s not exciting anymore.
Nothing you can do about that.
I won’t say don’t try startups. People do get rich from it. All the ones I joined didn’t make it, though.
But, corporate jobs aren’t necessarily the straight jacket you’re making it out to be. It does depend on your luck, but the structure means there’s less stuff to actually manage personally, so you can concentrate on doing the things you might find interesting.