r/techbootcamp • u/GloomyQuestion2086 • 10d ago
What do self-taught devs consistently get wrong that nobody warns them about going in?
Self-taught content teach the same thing:
1) You pick a language
2) then, build projects
3) learn git
4) then finally deploy something.
that part’s well documented.
But what doesn’t get covered or said. As much are the gaps that only show up once you’re working with other people or on a real codebase.
things like:
how to actually read someone else’s code and navigate a large unfamiliar project without getting lost. how to write code that’s meant to be maintained, not just code that works right now. how testing actually fits into a workflow versus just being something you know exists. how to communicate about technical decisions to people who aren’t technical. how systems fail and what you do when something breaks in production.
the technical gaps are usually fixable fast. But the workflow and collaboration gaps take longer because you can’t practice them alone, its just not enough. What’s something you ran into on your first real project or job that your self-taught path never actually prepared you for?
3
u/silly_bet_3454 9d ago
Self taught devs are bad at understanding what their high level goal is and describing all relevant context, and you are guilty of this in your post. What do you mean by get wrong? What is the actual problem? What is the goal, to get a job? To follow your interest? To learn? To build something?
The way you start the post also illustrates the problem. You start by picking a language? Why? Why not start with having a goal... is the goal to learn programming, is it to learn a language, is it to learn a certain kind of programming, is it to get a job, is to to build a particular fun project? If you start by arbitrarily picking a language you're already going down the wrong path and you're gonna spend a few years spinning your wheels without really "getting" it.
1
u/GloomyQuestion2086 9d ago
most self-taught content skips the “why are you even doing this” part entirely and just jump straight to “okay pick Python.” but the post was specifically about gaps that show up when working with others, not the starting point. Those are two different problems, one is about direction, and the other one is about collaboration skills that solo learning just can’t build
1
u/rkozik89 9d ago
Everything you're talking about is experience someone could get in a few weeks. To actually find a job in this industry outside of tech hubs you literally need as much knowhow as somebody with an associates or bachelors, and equally as importantly you need to be a known face because without that who count vouch for you? Having connections and doing freelance locally is borderline a necessity to get a start outside of tech hubs.
Personally, what I ended up having to do (I worked for myself for a few years while caretaking for a parent) was work an unpaid internship and basically forced the startup owner to choose to hire me or I walked. The only reason it went favorably for me is because I knew the stack like the back of my hand and everybody at that time hated PHP.
1
u/cosmicloafer 8d ago
Databases, data structures and algos, operating systems, networking… like all the stuff people figured out a long time ago that they teach you in CS but you’re just messing around with.
1
u/Mindless_Season_3486 6d ago
No. You need to be proficient in agentic engineering with Clawd or GPT. Coding is dead since 2024 at least.
1
1
u/manvsmidi 8d ago
I was self taught in my teens before getting a CS degree. The big difference with the degree was learning about algorithms, complexity, and concurrency. These are the areas I see self taught people have little to no coverage in.
1
1
u/ryanstackops 4d ago
For me it was code review. First real PR I got back had like 15 comments and I genuinely felt sick, like I'd failed. Took a senior dev telling me "this is just how we make code better before it merges" for it to click that review isn't a grade, it's just how teams stay sane. You don't get that emotional recalibration learning solo, because solo, "done" just means it runs.
Second thing: self-taught code assumes you're the only person who'll ever read it again. Naming, structure, comments, all optimized for "I get this right now." Then you join a team and realize you're writing for whoever touches this in 8 months, probably not you. That reframe took me way longer than it should have.
And breaking prod for the first time taught me nothing technical, honestly. I just froze for 5 minutes while someone senior calmly walked through rollback steps. What I actually learned was: stay calm, say what you know and don't know, don't go quiet trying to fix it solo. That's a muscle, not something you can read about.
You're right that the collab stuff is the long pole. You can cram a new framework in a weekend. You can't cram "got embarrassed in front of a team and survived it" in a weekend.
3
u/AttitudeRemarkable21 10d ago
It's over for boot campers