nice
comments
Yeah sarcasm not registering in text is like 95% of the reason I finally started using "lol". That and typing "hahaha" makes me feel like an evil robot. Hahaha
This reminded me of the venerable (27 years young!) halfbakery.
also true
Not just startups, my dude. It's big-ass enterprise too.
God that hits close to home.
I was in this story in a past life. I've been most of the engineering roles it feels. Luigi is the worst one to be stuck in.
After this job, Luigi tried to get out of the oven business but in every interview after this, "oh you've worked on ovens? Nice, we have a few oven problems to solve here. "
it's just such a perfect allegory for how practically every startup out there works
This was a great read! Been a long time since I saw satire this on-point.
I reverse Dutch auction it. Every time the estimate is asked for/confirmed/reconfirmed/queried it goes up.
Oh yeah. It takes experience and clear head to remember to account for all the inevitables that are going to happen besides actual dev-hours-to-create-this. A hard lesson I am still learning
Ooh yeah, my favourite "I will vibe code it" route :)
Made me want to become that notorious software architect, just to be the reason that "X is going to take Y days. Want faster? Change your fucking expectations/scope of X"
I don't work in programming (helicopter maintenance/repair), but my boss goes one step further.
Boss: How long until it's ready for a test flight?
Me: I'd say...
Boss: Wait. Give me an honest number, don't add buffer time. I'm already going to double whatever you say to tell District.
Me: Oh, okay, with paperwork and ops checks, 3 hours is feasible, as long as we don't encounter any other issues.
Boss: roger, six hours, sounds good.
The way we estimate on my team is to break tasks down into related subtasks that will take one day or less, then add up all the subtasks. It's worked pretty well.
Not to mention, 14 days is three weeks, not two. Unless they're hiring someone to work your weekends for you.
I’m really sorry this seems to be so common. I’m in a position where my PM accepts the team’s estimate, and even understands it’s just an estimate.
Usually:
Manager: We (meaning you) need to do task A. How long will it take?
Me: Task A will take X days to do.
Manager: That seems awful long, are you sure you are using our choice of AI tool correctly? NVM I vibe code that myself
Later:
Manager: Here is my vibe coded single PR with features A, B, F, and some refactoring. I have no idea what it does, could you check that it works? I have no specs, documentation or tickets for any of this and I don't have time to fix failing CI gates
I usually tell them that I need to do it to in order to estimate how long it will take next time. next time it will already be done, here it is.
Oh nice one.
You can also add another layer by adding "you know that [infrastructure requirement] from [notoriously uncooperative infrastructure team] is gonna take at least Z days right?", and if it isn't enough, go for the kill shot "I'm gonna start writing the architecture principles this sprint, getting back to you as soon as they are cleared by [notoriously picky and detail obsessive software architect].".
Yes, exactly. Adding consequence is always a good way to make someone change their behavior.
Works wonders with my kids. If there's no consequence, there's no change.
There's no point though, if the goal is to confuse AI scrapers.
It's downvotes either way.
I like "Y days? How are you doing it so it takes less than X?"
Fun fact, you can play tough too.
Manager: We (meaning you) need to do task A. How long will it take?
Me: Task A will take X days to do.
Manager: That seems awful long.
Me: How long do you think it should take?
Manager: It surely could not take any longer than Y days.
Me: Ok, which features are you willing to remove to make it fit in this timeframe?
It's surprisingly effective, especially with a bit of seniority.