
7 Things Senior Developers Do That Juniors Think Are 'Lazy'
My senior colleague closes his laptop at 5 PM sharp. Every single day. When I was three months into my first job, I thought he just didn't care about the work. I'd be sitting there at 7 PM, eyes burning, fixing a bug I introduced at 4:30 PM because I was too stubborn to step away. Meanwhile this guy was already home cooking dinner or whatever. Six months in, I started paying attention. Not just to the leaving-at-5 thing, but to everything else. The way he'd stare at a whiteboard for an hour before touching his keyboard. The way he'd kill features that took us weeks to spec out. The way he'd say "I don't know" in meetings like it was completely normal. It messed with my head. I thought senior developers were supposed to be the ones who knew everything and worked the longest hours. Turns out, almost everything I believed about being a "great" developer was backwards. So here's what I've been noticing. Seven things that looked lazy from where I was sitting. I was wrong about every single
Continue reading on Dev.to
Opens in a new tab


![[MM’s] Boot Notes — The Day Zero Blueprint — Operations from localhost to production without panic](/_next/image?url=https%3A%2F%2Fcdn-images-1.medium.com%2Fmax%2F1433%2F1*cD3LWDy_XXNTdZ_8GYh6AA.png&w=1200&q=75)

