Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "boooo"
-
The morons at work state the obvious like it’s a goddamn epiphany, and get cheered or publicly rebuked based entirely on their standing within company politics.
“While writing code, think of performance. Performance is everyone’s job, and it doesn’t take much effort to write much more performant code.”
> Premature optimization! BOOO! You should be ashamed! Move fast and break things OR ELSE.
“Security isn’t profit driven, but allows us to retain customers and therefore profit. Everyone should be security conscious and work with the security team *before* releases”
> BOOOO! Do your job! Don’t tell devs how to do theirs!
“Being reactive is good, but we should focus more on recovering from outages faster!”
> YAAAY! GENIUS!
ffs.8 -
Done it once or twice when finishing up a feature for a presentation/delivery the next day.
I'm leaning on the side of Not Worth It because I'd rather not be sleep deprived and dumb in brainy brain when interacting with the client and demoing my other stuff.
I guess it's usually when my perfectionism flares up that I'm likely to do stuff like that.
Will consider an all-nighter if it's reeeally necessary but there's few scenarios I can imagine where that is warranted. Maybe when working on a very serious security flaw or something of that nature. Most stuff can wait a couple of days...
Edit: goddamn I guess I committed the sin of not really answering the question. There's no story here. Boooo. Permission to hate myself, captain?