Honestly, the problem I encounter most with junior devs is that no one taught them to use the scientific method when trying to troubleshoot issues. Seems like everyone wants the answer to be handed to them on a platter and that just ain’t the way it goes.
this post was submitted on 16 Sep 2025
88 points (92.3% liked)
memes
17477 readers
1954 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
Honestly, that the problem with most people in most departments. No one learned the scientific method. Engineering, product, marketing. So many just panic and throw shit at the wall with how an understanding of how to isolate a variable.
YES EXACTLY! Learning how to set up a good test and a good control and then having the willpower to execute that and come to a conclusion… I swear that’s what will keep me employed into old age.
Iterative development is really good. Isolate and change a thing, see what behavior it does. See if user is happy. Push. Repeat.
Kind of felt like that last week. Our web-UI would automatically reload when you switched tabs, clearing out what the user had entered into a form. I started debugging, but the build times of our web-UI have been abysmal, making it extremely tedious to sprinkle log statements over the code for narrowing down what triggers the reload.
So, I decided to fix the build times first. The solution wasn't complex, basically just pull out a module into a separate library to benefit from incremental compilation, but with all the import changes and some additional restructuring, it still ended up being around 2000 lines of code changed.
Then I went back to debugging the reload problem, looked at it for 10 minutes, maybe rebuilt 3 times or so, and then made a lucky guess where I just changed one word for another and that fixed it. 🫠
Legend
real chad dev fix: -2 lines