Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "strategy"
Be more passive
I always get involved in everything, at every company. Not to further my career through ass-kissing and overperforming.
I regularly piss off people. When C-level has a discussion about strategy, I'm usually ahead of them, ask too many questions, criticize every detail they've missed, cause frustration by making them look incompetent.
Can't help it, when I see retards destroy a great product I have to intervene.
Some people appreciate it. I often defend both devs and end users, when others don't dare speak up.
But fuck it, I'm getting older. I'm gonna coast a bit more. Sit back, relax.
If a product manager doesn't prepare enough tasks — that's cool, I still have a Factorio savegame to work on.
If another team designs an incredibly stupid feature — they'll discover the issues eventually by themselves. Maybe I'll warn once, just to be nice.
*Pours another chocolate milk*
Also gonna spend at least 4h/d with my daughter. She's a better human than most of my coworkers, and the work we do using her Legos is honestly more important for humanity than the Jira backlog.20
what a garbage day. i've spent almost the whole day merging shit and the rest was meetings (also talking about how i merge shit).
dear fucked up branching strategy, when I look at the torn beauty of your mutated stream graph that carries the taint of corruption, depictions of feculent gnarlmaws come to my mind:
"These disgusting trees ring with the sorrowful tolling of entropic chimes, belch clouds of daemonic spores, and shed rot-wet blossom to carpet the maggot-churned earth beneath their boughs. The few stunted branches that grow from it feature dismal bells, tentacles and more pustulent boils."6
Maybe this is naive, but I feel if an application/feature is strategically important to a company, at least two developers should always be assigned to support it routinely. This great resignation is no joke, and I’m getting tired of being the last man standing here. I’m too old for this shit.8
My biggest challenge is not telling the people who wrote code I get to maintain that it is a big pile of shit. My fear is I will forget I wrote said code and proceed to complain about said code. Then someone will point it out that I wrote said code. So it is kind of a self preservation strategy.
Also, in meetings, when my boss calls something a "piece of software", I have to refrain from giggling.4
Idea: management strategy diversification experiment.
Basically we fund a company that has exactly the same fucking business model that we have, but a radically different management strategy. If it works, we know our culture needs some meddling.
New strategy to combat managers:
If you claim we can't afford the additional time for the tests that come with the feature, I won't build the feature.
If you claim we can't afford the additional time for the proper API versioning that comes with the feature, I won't build the feature.
And finally, if the internationalized texts, designs, and image assets are not complete when it comes time for development, I won't build the feature.
It's time to rise and stand against the "You're an engineer! do it all!" notions. I'm not a designer. I'm not a translator. I'm not a by-hand manual customer tester. And I'm certainly not going to take any more of your shit.2
My brother works in fintech sector. He had created an Options strategy after months of hard work and deployed the strategy in production via CI/CD.
However, the strategy didn't deploy automatically on Monday and few trades didn't happen leading to loss. His boss came down firing at him as to why strategy was not deployed.
Turns out the IT team had changed the password on Friday evening as per their routine password updates.1