The Orphaned ID Bug from My First Job (And What It Taught Me About Being a Junior Dev)
The article discusses a junior developer's experience with a bug in a corporate learning management system. The developer faced challenges in debugging due to a lack of context and support from senior team members. Ultimately, the developer was let go for relying on AI tools, despite having made several contributions during their short tenure.
- ▪The bug involved orphaned IDs in a corporate LMS, affecting training assignments.
- ▪The junior developer was not provided with essential information to debug the issue effectively.
- ▪The developer was fired after one month for using AI tools, despite having made multiple contributions.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3610693) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Bradley Matera Posted on Apr 28 • Edited on Apr 29 The Orphaned ID Bug from My First Job (And What It Taught Me About Being a Junior Dev) #jquery #php #ajax #webdev The Junior Dev Trials (10 Part Series) 1 Job hunting is poopie 2 The Orphaned ID Bug from My First Job (And What It Taught Me About Being a Junior Dev) ... 6 more parts... 3 Companies Say There Are No Good Juniors. They Mean They Stopped Training Them" 4 AI Did Not Make Junior Developers Risky. Unreviewed Work Did.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV Community.
Discussion
0 commentsMore from DEV Community
