 |
| “Mistakes, rewrites, late nights, firefights, and deadlines.” (comment) | ||
| recommended by 1 user | 2016 | stray on: Ask HN: What makes a Senior Dev | developer careers | original thread | | ||
| stray on Mar 23, 2016 | on: Ask HN: What makes a Senior Dev | view on HN | ||
| One user recommended this comment. What they said: |
|
misframer Sep 29, 2016 | on: Ask HN: When are you considered a “senior” programmer? | context
I really liked this comment by @stray [0] from a similar Ask HN from a few months ago. That thread was titled "Ask HN: What makes a Senior Dev". |
Mistakes, rewrites, late nights, firefights, and deadlines.
Core dumps, memory leaks, hardware faults, and plain bad luck.
Big O, data flow, always learning -- or out you go.
Manager metrics, schedules hectic, methodology hegelian dialectic.
Taking the heat, feature creep, open office, uncomfortable seat.
Holy wars, revolving doors, carpal tunnel, all you can take? There's always more.
Fucking suits, random reboots, and the ever present "thousand language stare".
Oh yeah, pressure -- lots of pressure. And time, time, time.
Metric shitloads of time.
Time, man. You gotta do your fucking time.