I've had this conversation:
We need to increase our velocity! Has the customer told us yet what they would like us to build?
this post was submitted on 19 Jul 2023
1180 points (99.0% liked)
Programmer Humor
33619 readers
9 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
Unfortunately I can't have that chat ever. I'm the one (in most of my career, not now) responsible for telling my folks what the customer wants, and not in a sales way.
You can fix it later, but that doesn't mean you're going to.
Nothing's more permanent than a temporary solution.
Technical debt goes brrrrrrrrr
They can't fire you if you're the only one who can fix your shit...
Oh, they can, they will just force some other poor programmer to read your code and figure it out. A profoundly miserable process, but someone is willing to do it.
my heart goes out to the poor soul who tries to make sense of my code
Later there will be other projects, other fires.
I’ve seen a “temporary fix” serve as a core element of a service stack for a company with annual revenue in the hundreds of millions for like at least 5 years.
mmmm spaghetti code
"Boss, most of the bricks we have are broken in pieces. We can't build the wall per specifications."
"We have a deadline, get it done however possible by the end of the day today."
This applies to lift-and-shift migrations too. “We need to migrate this now, let’s fix it as a next phase”, then it never gets fixed; instead of taking the opportunity to fix stuff as you build on a clean slate.
You have a problem with agile methodology, you have a problem with me, and I suggest you let that one marinate.
there’s a special place in heaven for kanban lovers that’s what i always say
To be faiiiiiir, it’s is the easiests of the ways of workins.
To be faaaaaaiiiiirrr...
To be faaaaaaaiiiiiiiiir 🎵
Why?
I loved agile as an analyst, we used to use waterfall and you'd hear about incorrect designs months later, or not at all, where in agile you can work out the details with the programmers and get both nearer the business requirements, and better designs
Also I absolutely love the job of scrum master which had no equivalent in waterfall
I love waterfall as an developer, I’m using agile now and we have incomplete, conflicting designs every sprint, or spills which affect our metrics, where in waterfall you can workout all the details and have full vision of product and better design with less reworks.
Not to mock you. My point is that methodology is not import when team consists from responsible professionals
I think a lot of it dependent on management. If you have a good product manager, software architect (or whatever) who can have things solidly designed before sending it to development, agile works great. But if the people writing the cards suck at their job, well then the project isn't going to go well.
But then bad management is going to suck no matter what methodology is used.
You're right on. We have some good expertise left over from our previous methodology which was both waterfall and siloed so bad feature documents don't cause too much problem, but once our expertise retires (and we're not makeing new experts as the silos were removed) the features will need to great to get decent products
And bad management is the biggest thing to make a job miserable
I don't take it as mocking or anything, I know that some devs in my team preferred waterfall. I'm just saying there are aspects of agile I really enjoy
Waterfall makes higher quality software in many circumstances. It's optimised for quality.
Agile is optimised for speed explicitly at the expense of quality. Whatever methodology you can only pick two between development speed, cost, and quality
There are some instances in which waterfall is not only entirely appropriate, but also the best possible choice in terms of work organization.
There are some instances in which agile is the best fit. Likewise kanban.
Different domains have different optimal workflows.
My conversation with the moronic MBAs that lead my org today. Who cares about doing impactful work when we can just do useless busy work that makes the nontechnical morons happy.
"We're just using old, time tested frameworks. They worked fine in the past, they'll still work today for sure!"
About the pic itself, laying bricks like that can't be structurally sound... am I right?
No conflict is for the weak.
💪
That's actually a nice CSS.
Is there some reason that wall won't work fine?
should work fine if there is no load on it , this seems deliberate for the look
Ah the well known technical debt
The trick is to get some else to shit the 🧱 when it hits the fan.
with lease?