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
nerd-chan136612dgod i hate people like that
platypus525612dMe: Why does this function accept 14 arguments?
ShitDev: Because I was able to remove five that weren’t used in the body...
For management, I often use buildings as a metaphor for code.
"Yes, this code works. The developer who made this created a beautiful gazebo, it looks truly amazing. But your land is a swamp, and there's zero foundation support under your new little garden structure"
"Well, that means that you can sit in your gazebo on a starry night with a glass of wine and everything will be fine. At least for a while. But it might break at a critical moment. Like when you plan a party for all your friends. Scalability is important, also for your reputation!"
"Yeah but we won't have that many visitors for a while"
"It also means that if you want a new feature, like a couch or a BBQ, it might be too heavy"
"So what are you saying?"
"That until you let us do some foundation repair, we should basically consider the gazebo off-limits, except for essential visits. No more new features, no big parties, no promises to visitors."
PepeTheFrog59511dAside from the actual rant topic, those arbitrary delivery milestones always crack me up, as mentioned in the shitDev last reply. I could straight put a bullshit description in a ticket and estimate it to 20 story points, now implement it and make it work. I could also link it to a requirement as well as say what is the acceptance criteria. It still does not mean what I did was actually useful.
The real question: how do you measure. that work being done goes towards the right direction? I swear nobody wants to answer it.
natesymer17411dThe problem is that mfers think code happens quickly and magically, and some idiots realize they can hide their ineptitude by quickly (and sloppily) doing things.
This job makes me want to scream sometimes. It's not the code, it's the asinine business culture and its unrealistic expectations of smart/skilled people.
Reminds me of a legacy app I’m working on at the moment it sucks. But “it works”. The team didn’t even do any CI testing at all haha that’s the tip of the iceberg.