If doctors were treated like web developers!

My last internship. When acquiring a new project and having to give an estimate the boss/sales guy always went to the programming team first to ask them what the estimate was and then communicated that back to the client(s).

Asked him why he does that because many companies don't:

Well, the programmers are going to write the software so why the hell would *I* be the one who gives the fucking estimates?

Yes that was a good boss.

toxic workplace; leaving

I haven't wanted to write this rant. I haven't even wanted to talk to anyone (save my gf, ofc). I've just been silently fuming.

I wrote a much longer rant going into far too much detail, but none of that is relevant, so I deleted it and wrote this shorter (believe it or not) version instead. And then added in more details because details.

------

On Tuesday, as every Tuesday, I had a conference call with the rest of the company. For various, mostly stupid reasons, the boss yelled at and insulted me for twenty minutes straight in front of everyone, telling me how i'm disorganized, forgetful, how can't manage my time, can't manage myself let alone others, how I don't have my priorities straight, etc. He told the sales team to get off the call, and then proceeded to yell and chew at me for another twenty minutes in front of the frontend contractor about basically the same things. The call was 53 minutes, and he spent 40 minutes of it telling me how terrible I've been. No exaggeration, no spin. The issues? I didn't respond to an email (it got lost in my ever-filling inbox), and I didn't push a very minor update last week (untested and straight to prod, ofc). (Side note: he's yelled at me for ~15 minutes before for being horribly disorganized and unable to keep up on Trello -- because I had a single card in the wrong column. One card, out of 60+ over two boards. Never mind that most have time estimates, project tags, details, linked to cards on his boards, columns for project/qa/released, labels for deferred, released to / rejected from qa, finished, in production, are ordered by priority, .... Yep. I'm totes disorganized.)

Anyway, I spent most of conference call writing "Go fuck yourself," "Choke on a cat and die asshole," "Shit code, low pay, and broken promises. what a prize position," etc. or flipping him off under the camera on our conference-turn-video-call (switched due to connection issues, because ofc video is more stable than audio-only in his mind).

I'm just.
so, so done.

I did nothing the rest of the day on Tuesday, and basically just played games on Wednesday. I did one small ticket -- a cert replacement since that was to expire the next day -- but the rest was just playing CrossCode. (fun game, fyi; totally recommend.)

Today? It's 3:30pm and I can't be bothered to do anything. I have an "urgent" project to finish by Monday, literally "to give [random third party sales guy] a small win". Total actual wording. I was to drop all other tasks (even the expiring cert lol) and give this guy his small win. fucking whatever. But the project deals with decent code -- it's a minor extension to the first project I did for the company (see my much earlier rants), back when I was actually applying myself and learning something (everything) new, enjoying myself, and architecting+writing my own code. So I might actually do the project, but It's been two days and I haven't even opened single file yet.

But yeah. This place is total and complete shit. Dealing with the asshole reminds me of dealing with my parents while growing up, and that's a subject I don't want to broach -- far too many toxic memories.

So, I'm quitting as soon as I find something new.
and with luck, this will be before assface hires my replacement-to-be, and who will hopefully quit as soon as s/he sees the abysmal codebase. With even more luck, the asshole king himself will get to watch his company die due to horrible mismanagement. (though ofc he'll never attribute it to himself. whatever.)

I just never want to see or think about him again.
(nor this fetid landfill of a codebase. bleh.)

With luck, this will be one of my last rants about this toxic waste dump and its king of the pile.
Fourty fucking minutes, what the fuck.

When the PM gives you the project estimates...

PM asks for an estimate on a bug fix, I say 2 hours, he puts down 4 hours, I finish it in 10 mins. Today was a good day :)

My boss asked me to do estimates for some tasks.

I did it.

He told me that was too much time.

I told him that those were the estimates taking into account the experience of the team.

He told me the estimates were independent of that.

I asked if an estimate, for the same tasks, for a team of interns should be the same as for a team of seniors.

"Of course they are the same!"

Funny thing is that he even says he supports scrum...

Manager: I need estimates for your sprint tasks

Me: I've never done any of this before, my estimates have no context and are effectively worthless

Manager: don't worry it's just for the Jira board.

Me: OK *gives estimates*

End of sprint comes...

Manager: Why isn't task X done?

Me: *sigh*

I don't miss my old job :)

The rule of pi: When giving estimates, multiply your estimate by 3,14.

My company does estimates in two ways.

1. Sales person just throws a number out there, always short, and we panic code to make it happen before the client decides twice as long isn't worth it.

OR

2. The devs are told to give an estimate before having a chance to find out all the requirements, THEN ARE TOLD THEY ESTIMATED TOO HIGH AND TO LOWER THE NUMBER!

FUCK THE ESTIMATING!!! GIVE US TIME AND ACCEPT OUR ESTIMATES!! SALES PEOPLE DONT HAVE TO STAY UP IF WE NEED TO CRAM!!

fellow from the team was asked to do the estimate by manager - he said 2 weeks

then manager asked what if we add one more developer - he said, again 2 weeks and maybe add day or two

I was asked same question without knowing that they already asked fellow from the team same question - I said around two weeks, maybe day or two more! XD

as manager was confused and not satisfied with the estimates, goes to our team leader with the same questions - team leader said - 2 and half weeks and if you add one more dev to it, 3 weeks minimum

we didn't know that all of us were asked as manager did that behind our backs, in the end manager learned lesson in greed as we got to stick to team leaders estimate!

also that was very rude of underestimating someone's ability, same manager did had personal bias and frequently mocked us, for example when we said that that we will implement ML for cropping images at the right place (ie. crop part of the image where the face is) on the backend. Response was something like: 'You guys will do the ML? Are you shitting me? You're not /insert FANG company/!'

best team win ever!

second best team win ever is when whole team left the company in matter of weeks

Double your estimates.

Experience that made me feel like a dev badass?

Users requested the ability to 'send' information from one application to another. Couple of our senior devs started out saying it would be impossible (there is no way to pass objects across a machine's memory boundary), then entertained the idea of utilizing the various messaging frameworks such as Microsoft's ServiceBus and RabbitMQ, but came up with a plan to use 2 WebAPI services (one messenger, one receiver) along with a homegrown messaging API (the clients would 'poll' the services looking for message) because ServiceBus, RabbitMQ, etc might not be able to scale to our needs. Their initial estimates were about 6 months development for the two services, hardware requirement for two servers, MSSQL server licenses, and padded an additional 6 months for client modifications. Very...very proud of their detailed planning.

I thought ...hmmm...I've done memory maps and created simple TCP/IP hosts that could send messages back and forth between other apps (non-UI), WPF couldn't be that much different.

In an afternoon, I came up with this (see attached), and showed the boss. Guess which solution we're going with.

The two devs are still kinda pissed at me. One still likes say as I walk in the room "our hero returns"....frack him.

Hey PMs!

Fuck you!

Estimates are NOT... I repeat..they are NOT the FUCKING DEADLINES.

If you are asking for an estimate then remember, in your absolutely fucking small fucknugget brain, that it can FUCKING CHANGE!

The last thing you wanna do is grill the dev by asking them to explain in details why the change instead of trusting them. Specially when you don't understand a thing of the technology.

- Dev on whom you are shitting you asshole!

Three months down the line and I'm finally ready to admit that my first completion estimate of "this afternoon" may have been slightly overambitious

QA: Please Look at this Defect.
Me: Okay not a problem!
QA: Thanks
Me: <Starts to look at Defect>
QA: 2 mins later. Do you have an ETA on when it will be fixed?
Me: Not yet, I'm still looking at it.
QA: Do you know what time it can be fixed? I have a deadline.
Me: I don't know what's wrong yet, I can't tell you when it will be fixed if I don't know what's wrong.
QA: Okay. Update Me.
Me: Opens Dev Rant.

Dev: this will take around three sprints to complete.

Product owner: weeelllll I think you can manage it in one..

At the data restaurant:
Chef: Our freezer is broken and our pots and pans are rusty. We need to refactor our kitchen.
Manager: Bring me a detailed plan on why we need each equipment, what can we do with each, three price estimates for each item from different vendors, a business case for the technical activities required and an extremely detailed timeline. Oh, and do not stop doing your job while doing all this paperwork.
Chef: ...
Boss: ...

Some time later a customer gets to the restaurant.
Waiter: This VIP wants a burguer.
Boss: Go make the burger!
Chef: Our frying pan is rusty and we do not have most of the ingredients. I told you we need to refactor our kitchen. And that I cannot work while doing that mountain of paperwork you wanted!
Boss: Let's do it like this, fix the tech mumbo jumbo just enough to make this VIP's burguer. Then we can talk about the rest.

The chef then runs to the grocery store and back and prepares to make a health hazard hurried burguer with a rusty pan.
Waiter: We got six more clients waiting.
Boss: They are hungry! Stop whatever useless nonsense you were doing and cook their requests!
Cook: Stop cooking the order of the client who got here first?
Boss: The others are urgent!
Cook: This one had said so as well, but fine. What do they want?
Waiter: Two more burgers, a new kind of modern gaseous dessert, two whole chickens and an eleven seat sofa.
Chef: Why would they even ask for a sofa?!? We are a restaurant!
Boss: They don't care about your Linux techno bullshit! They just want their orders!
Cook: Their orders make no sense!
Boss: You know nothing about the client's needs!
Cook: ...
Boss: ...

That is how I feel every time I have to deal with a boss who can't tell a PostgreSQL database from a robots.txt file.
Or everytime someone assumes we have a pristine SQL table with every single column imaginable.
Or that a couple hundred terabytes of cold storage data must be scanned entirely in a fraction of a second on a shoestring budget.
Or that years of never stored historical data can be retrieved from the limbo.
Or when I'm told that refactoring has no ROI.
Fuck data stack cluelessness.
Fuck clients that lack of basic logical skills.

You know you're a programmer when your phone estimates your bedtime as 1:22am

Come on:
You can't trust estimates that two month ago me said!
He was young, foolish and full of hope.

*project manager + designer are showing new designs*

PM: so, can we get some estimates?

Devs (literally all of us): do we have a mockup for this interaction?

Designer: no.

Devs: What about that one?

Designer: not yet.

Devs: What happens when you click here? Hover there? How does this look if I select that option + this option at the same time? Does it make sense that a user can select *this* option with *that* option? They're kind of mutually exclusive.

PM: Well...

BTW: code freeze is in two weeks...

I fucking hate giving estimates.

My teams current process is:

1) Asked by product to create “T-Shirt size” estimates, also known as a WAG (wild ass guess). The process is the mental equivalent of throwing darts while blindfolded, after being spun around in a circle and pointed in the wrong direction.

2) Product make firm commitments to upper management based off these. Ensuring them that all these features will make it out in Q2.

3) 4 days before Q2 starts, product ask engineering to figure out the real estimates based off no concrete information what so ever.

4) 4 Weeks into Q2, product provide the missing information.

5) Engineering inform product that the estimates are out by a factor of 1.5 - 3 times the original estimates.

6) Product sends angry email to upper management that through not fault of product, engineering are unable to meet the deadlines.

7) Everyone shout and complain until 1 week before Q3, then see point 1.

Following this process, you and your team can be just as delightful as me.

That’s the practiseSafeHex guarantee!

Microsoft estimates now available in macOS

I was at my last job for 13 years when they outsourced my job to India. They kept me on as a liaison - they said they needed a BS detector to make sure the hosting company was not inflating their estimates. 6 most boring months of my professional career.

As I was getting my resume together to start looking, a former coworker called. She was now an application dev manager and was putting together a post integration team. One interview later, I was hired. It was perfect timing.

"How long will it take us to build X?"

"How long is a piece of string?"

Very similar indeed. Time estimates are insanely hard even with all the cards on the table, be sure to lay them all out before asking.

- Premature optimization is bad and wastes your time
- You need to see the big picture
- Always add extra hours to your estimates
- Test your feature like a QA engineer; look for the edge cases

I just told my biggest client that they have to start changing things or they will need to find a different company to work with.

I'm hired to program what they want. They are suppossed to do all the concepting, functional designs, QA, testing.

So they tell me to program feature x, not realising that this interact with feature y. And then complain about the change in feature y. Make me do a lot of extra work and then complain that my estimates are way off.

So I told them they also need to hire my company for the software design and QA and prefferable testing because I'm done getting blamed.

Find a place where management is able to handle some criticism.

I personally think Agile/Scrum is holy, and I don't mean "yeah we kind of do our own version of it", no, fucking do it by the book. The PM shouldn't assign estimates. Developers shouldn't receive bugfix requests from anyone other than the scrum master. The CTO can't be your scrum master... etc.

If a company can't answer the question "What were the points of feedback during the last retrospective(s), and how are those points being picked up?" -- Don't work there.

Many other things are optional in my opinion. I could work at a company without QA, without fruit baskets, table tennis, without Friday drinks. I could even live without git & continuous integration, just emailing patches to a patch integrator. I don't care.

But maintaining a safe bubble of serenity and sanity for devs to do their work in, that is an absolute must.

Also, option to WFH as much as wanted. Offices are nice for social bonding, but they kill productivity for me.

Rant about devRant.

I hate to see two types of posts:

1. “Haha, i added a WordPress existing theme and charged customer XXXX EUR”, “Idiot customer, I had cross platform app and I charged for each platform”, “lol, they wanted to negotiate the payment, I connected to backdoor and shutdown down their servers”
2. “Why does customer not trust our estimates?” “I told him he does not need to worry about this comparability”, “they are asking about security of the hardened server, are they nuts?

First you treat customers dishonestly and then expect them to trust you and rely on your expertise. Before you constantly complain about the customers - look at yourself guys.

When rough estimates become hard deadlines... 👌

Boss: "How much time do you get this bug fixed?"
Me: "Give me 20 minutes"
*4 hours later*
Me: "fixed is in the repository"
Boss: "You're getting to much time to do your assignments"
Me: *Damn it*

I suck doing estimates 😥

Not a deadline but I once worked for a company that regularly asked for “accurate estimates” which I found hilariously oxymoronic

Why is it that people that can't program always seem to think they know how long it should take you?

In my last job they required us to turn on a task timer for every little thing. Remembering to do that, and to turn it off, was a royal pain. First I had to look up which task it is, start the timer, stop the timer, find the next task and repeat, then flip back to the first task. Lots of open browser tabs within tab groups to keep track of it all. And if I came up short or went over on budget, there was a “conversation” with management to account for discrepancies. Then I had to go by memory and try to reconstruct the “missing time” accurately enough to be convincing.

Now that I’m freelancing, I try to keep up the habit because it does have merit for tracking estimates and actuals, but now it’s just me to answer to for discrepancies and I can fudge the numbers as I see fit. The time records did, however, save my bacon in a recent dispute.

I've decided that whenever a non technical person be it a client or a non technical PM tells me it's easy or tells me it'll take only x hours, I'm going to tell them to either do it themselves, or let me do my estimate calculation. You don't fucking understand one line of what I do yet you can magically calculate the amount of time I'll take on the task? No fucking thank you sir.

Me: Right, its Monday, time for a fresh start. Things have been unbearable, but i've nowhere else to go just yet. I gotta just dig deep, ignore everything bad and just get it done, It's all about positivity right? Lets just ignore the little things and keep moving.

*My morning so far, 2 hours in*

Remote dev: (timezone 5 hours earlier than me) Hey so whats the plan for this quarter?

Me: ... I posted a big detailed plan in the group chat on Friday night so you wouldn't be delayed ... but anyway, lets just move on. I need you to work on A, B and C. A is just copying what Android has already done, for B one of the backend guys working next to you is doing this, he'll be able to help you. C is all documented in the ticket.

Remote dev: cool thanks.

Local dev: So I was just chatting with remote dev ... yeah he told me he has no idea what he's suppose to do.

Me: ..... Ok i'll book a video call with him in the morning. Can't do it right now.

==========

Remote dev: Hey i'm helping the BE team do some testing. I found a bug in Android. Homepage says theres no trips. But Offers screen says there is.

Me: Ok so just to confirm, The "available" offers screen has offers to accept, but the white notification on the homepage saying "You have X offers to accept" is not showing up?

Remote dev: Correct!

*debugging for 5 mins*

Remote dev: actually no, the "accepted" offers tab has offers, but the homepage says there are no upcoming offers to work on.

Me: ..... ok, thats very different ... but sure, let me have a look.

Me: Right so the BE are ... again ... sending down expired offers. Looks like the accepted tab isn't catching it and the homepage is.

Remote dev: Right i'll open a ticket for Android.

Me: ... and BE team.

Remote dev: why?

Me: ... because they once again have timezone issues. This keeps causing issues in random places. BE need to fix this everywhere.

Remote dev: right, i'll chat to them and see if they can fix it.

==========

Product: So this ticket xxxxx is clear right?

Me: eh, kind of, so you want us to add feature X to user type A?

Product: correct.

Me: right but I don't see anywhere talking about the time it will take to build the screen for feature X

Product: What do you mean the screen?

Me: ... well, feature X is only accessible on screen Y ... we would have to change screen Y to support user type A ... you know ... so they can ... use the feature

Product: .... hhhhmmm .... i suppose you are right. Well we can't just add screen Y, we'll have to add W and Z, it won't make sense without them.

Me: ... ok sure, but our estimates put us over for this quarter. I don't think we can just add in 3 screens.

Product: No this is a must have.

Me: Ok so we'll have to drop something else.

Product: hhhmmm, don't think we can ... let me get back to you.

==========

Backend team invited me to a meeting at 6am my time on Friday.

==========

... 2 hours into Monday ... there must be vodka around here somewhere

This big multi-million consulting company hired me as freelance. They did it in a hurry, because "the project already started, it is a very important client (a bank) and we need your expertise by YESTERDAY".

In the first THREE WEEKS I had meetings with their own project managers, their client's project managers, techies, sales people. No one was able to tell me what do I have to do, but:

1 - they asked me for very detailed estimates plus a release plan
2 - f**k your estimates, we need this BY JANUARY 16th

HAVE YOU JUST TRIED TO BARGAIN ON MY ESTIMATE?!

I really hate when people try to bargain on my estimates. It's done when I say so. I really think it through before I tell you the deadline, so GO FUCK YOURSELF PLEASE AND SHUT THE FUCK UP. NEVER EVER BARGAIN ON THAT AGAIN.

If you do, it will take one week longer for every time you try it.

For some reason my manager freaked out after her non developer husband told her that each of the web pages for our main service would take months to build. Shit man its just static content with some animations here and there. It is a total of 15 pages and this dude estimated that I (as in yours truly) would only be able to do 2 per month. Bato stfu. Stick to banking (hopefully your time estimates don't suck ass there) and let me woo your woman with my frontend godspeed.

So what did I do?

Simple, asked her to show me one of the design models she already created on photoshop. Saved that thing to my computer and coded it at home. In 2 hours (It was originally one but my dumbass gor tab trigger happy with rm rf autocomplete so I had to do it again...fking dumb) and showed it to her this morning.

Eat a dick dude. The woman is already going apeshit over all the other shit we have to do plus working on her masters and attentind 100+ pointless meetings a day whilst still being able to be the best fucking manager I've ever had. I really don't need her freaking the fuck out over your dumbfuck estimates. Why in the wholy fucking world she listened to your dumbass is beyond me, probably stress made her freak out.

Its cool b.....I got it under control.

Fucking chill woman damn.

**drops mic

Coworker: since the last data update this query kinda returns 108k records, so we gotta optimize it.
Me: The api must return a massive json by now.
C: Yeah we gotta overhaul that api.
Me: How big do you think that json response is? I'd say 300Kb
C: I guess 1.2Mb
C: *downloads json response*
Filesize: 298Kb
Me: Hell yeah!
PM: Now start giving estimates this accurate!
Me: 😅😂

There are three things in my workflow that I don't like:

1. Feature requests appearing out of thin air.

It's common to be handled work at 2pm that needs to be deployed by the end of day. Usually it's bug fixes, and that's ok I guess, but sometimes it's brand new features. How the fuck am I supposed to do a good job in such a short time? I don't even have time to wrap my head around the details and I'm expected to implement it, test it, make sure it doesn't break anything and make it pass through code review? With still time to deploy and make sure it's ok? In a few hours? I'm not fucking superman!

2. Not being asked about estimates.

Everything is handed to me with a fixed deadline, usually pulled off my PM's ass, who has no frontend experience. "You have two weeks to make this website." "You must have this done this by tomorrow morning." The result, of course, is rushed code that was barely tested (by hand, no time for unit or integration tests).

3. Being the last part of the product development process.

Being the last part means that our deadlines are the most strict. If we don't meet the deadline, the client will be pissed. The thing is, the design part is usually the one that exceeds its time (because clients keep asking for changes). So when the project lands on our desks it's already delayed and we have to rush it.

This all sounds too much like bad planning to me. I guess it's the result of not doing scrum. There are no sprints, no planning meetings, only weekly status update meetings. Are your jobs similar? Is it just usual "agency work"?

I'm so tired of the constant pressure and having to rush my work. Oh, and the worst part is we don't have time for anything else. We're still stuck with webpack 2 because we never have time to update it ffs.

Manager: what is the estimations for this task A nd B?

Me: Task A: 3 months for 1 guys, and task B: 2 Months

Manager: ok, u can have a fresher, and finish task A, and u urself can pick task B, u can train him and bring him up to pace...

Me: (trying to recalibrate my estimations)...

Manager: oh and u have 3 weeks to deliver production ready scalable quality code with junits, documentation and testing done...

Me: then why the fuck did u bother for the estimates?

Manager: oh that is just for the process complaince...I don't want any trouble in audit...

Worst part of being a Dev when someone else prepare estimates for your tasks.

Everyone's crying about big bad companies using innocent graduates by offering them a few non-paid internships. But when it comes to mgmt manipulating devs into non-paid overtime by questioning their estimates, noone sees a problem.

For fuck's sake, you are the devs, YOU and ONLY YOU can do tech estimates, not the mgmt. You are nothing close to a developer if you allow them to manipulate you like that. Just a dummy coder at best. A puppet with no backbone. An amoeba. You are DISGUSTING and a disgrace to developers' proffession.

Start acting proffessionally for once!!

-Boss instructs me to always set high estimates
-Asks in how many days will i finish X
-I think 3, but adding 1 extra day for each random problem i tell him one week
-He says thats way too long, make it 3 days
-Shit happens and i can barely finish it in one week
-My boss:

Boss: this is different from the old console I don't like it

Me: but this has been approved by product management and the team already made estimates and committed to the feature

Boss: Well this needs to change, our existing users will not like it

Me: This is far from agile to be honest, and the change came from user feedback analysis

Boss: You are not doing your work *swears and curses* this is against the team direction!

Me: then why was this committed on this sprint? All I did was facilitate the needs of the team to proceed development.

Boss: *runs out office and starts calling other bosses to boss around*

Runs in 5 minutes later, saying we are not allowed to destroy a feature with enhancements like this.

Me: *Infinite facepalm*

Coworker: We you have to estimate these tasks.
Me (thinking): This task should take one day, but I'll add 4 hours in case something unexpected happens again.
* Estimates 12h
Coworker: Alright, the tasks for this sprint have been selected. Please start to work on them.
Me: * Starts working on certain task
* Sees time available for task
2d 4h (=20h)
* Writes coworker
Dude, that much time is overkill for that task!
Coworker: Yeah, the client said something similar.
Me: Then why did you estimate it that high?
Coworker: 🤷‍♂️
Me: Ok, what am I gonna do with all that extra time? 😑
Coworker: 🤷‍♂️

Thanks mate.
Around 4 hours in and almost done. What should I do with that extra time?

Task in question: Add a mutually exclusive field to a database table, add it to the form, test it and update the docs.

Enjoy the unrelated, clickbait cat

Asking a developer for an estimate is like asking a doctor how long it will take to perform an appendectomy.

Making that estimate a hard date is like telling the doctor, "We need this finished in 45min, no matter what... NO MATTER WHAT!"

asked for estimates

said tomorrow

pm said she needs it by today

why asked me then?

Our company maneuvered themselves into a classic technical debt situation with a project of a second team of devs.

They then left, signing a maintenance contract and now barely work on the project for exorbitant amounts of money.

Of course management got the idea to hand off the project to the first team, i.e. our team, even though we are not experts in that field and not familiar with the tech stack.

So after some time they have asked for estimates on when we think we are able to implement new features for the project and whom we need to hire to do so. They estimates returned are in the magnitude of years, even with specialists and reality is currently hitting management hard.

Code is undocumented, there are several databases, several frontends and (sometimes) interfaces between these which are all heavily woven into one another. A build is impossible, because only the previous devs had a working setup on their machines, as over time packages were not updated and they just added local changes to keep going. A lot of shit does not conform to any practices, it's just, "ohh yeah, you have to go into that file and delete that line and then in that other file change that hardcoded credential". A core platform is end of life and can be broken completely by one of the many frameworks it uses. In short, all knowledge is stowed away in the head of those devs and the codebase is a technical-debt-ridden pile of garbage.

Frankly I am not even sure whom I am more mad at. Management has fucked up hard. They let people go until "they reached a critical mass" of crucial employees. Only they were at critical mass when they started making the jobs for team 2 unappealing and did not realize that - because how could they, they are not qualified to judge who is crucial.

However the dev team behaved also like shitbags. They managed the whole project for years now and they a) actively excluded other devs from their project even though it was required by management, b) left the codebase in a catastrophic state and mentioned, "well we were always stuffed with work, there was no time for maintenance and documentation".

Hey assholes. You were the managers on that project. Upper management has no qualification to understand technical debt. They kept asking for features and you kept saying yes and hastily slapped them into the codebase, instead of giving proper time estimates which account for code quality, tests, reviews and documentation.

In the end team #2 was treated badly, so I kinda get their side. But up until the management change, which is relatively recent, they had a fantastic management who absolutely had let them take the time to account for quality when delivering features - and yet the code base looks like a river of diarrhea.

Frankly, fuck those guys.

Our management and our PM remain great and the team is amazing. A couple of days a week we are now looking at this horrible mess of a codebase and try to decide of whom to hire in order to help make it any less broken. At least it seems management accepted this reality, because they now have hired personnel qualified to understand technical details and because we did a technical analysis to provide those details.

Let's see how this whole thing goes.

I hate doing estimates, but I had to adapt. Since I work remotely and under contract, I'm used to track my time and estimate by hours.

I did a lot of mistakes before, which means I worked for free to wrap up fixed price projects.

Today, the method that is working best for me is:
1) positive estimate
2) most likely estimate
3) worst case estimate
Sum up and divide by 3.
I do this for every task.
Also, for Web projects, I like to divide tasks in categories like: HTML / CSS, UX, programming, testing.

Client project manager calls me up one day

PM: hey can you make some precise estimates on some items for a project you’re not working on? It should be easy. It’s very similar to the project you ARE working on and it’s only a handful of user stories, mostly front end stuff. We´ll need this to be done by tomorrow night.

Me: um, I guess if it’s just a few simple items. ok

PM: great! I’ll let you know when you get access to the backlog.

Me: sounds good

Link to project is sent to me. Backlog contains over 20 user stories, most of which are backend related. And it doesn’t have much to do with my current project.

I contact PM: this isn’t exactly what you announced when I had you on the phone. If you want precise estimates with a minimum of design, this could take up to a week. I could however proceed to some ballpark estimates (poker planning) for starters if you need this quickly for your roadmap.

PM: no I need PRECISE estimates down to the hour for each item.

Me: ok then, it’ll take up to a week.

PM: 🤬🤬🤬. You told me it could be done in a day. I’m coming to realize your word can’t really be trusted.

Me: 🤦🏻‍♂️

For fuck's sake man! I know you are an inexperienced junior dev/student but estimating 3 months at 6 hours /day for slightly modifying some C# code is just ridiculous.

I may have never touched anything .NET before but the modification required just 3 fucking lines and I did it in a day. In three months I would have finished the whole fucking project.

PS: VS2017 (RC) was quite lovely.

"How much time would it take you to implement $some_feature ?"

DAMN IT, I hate being asked for estimates on friday. Reminds me that I have to work again on monday.

A new producer started to pick up where the previous guy had rage quit. He looked at our sprint plan and announced it.

"According to this schedule, by these estimates, to hit our goal we have to somehow all work 27 hours a day, 7 days a week, for the next month."

"How long will this take?"

"Are you familiar with probability distributions?"

Estimates? You guys got asked for estimates? I just got my deadline set, no questions asked.

When i worked for a large, international bank (whose name rhymes with shitty), I always had to use the following formula to estimate projects.

1. Take estimate of actual work
2. Multiply by 2 to cover project manager status reports
3. Multiply by 4 to cover time spent in useless meetings.
4. Multiply by 2 to cover user support and bug fix tasks.
5. Multiply by 2 to cover my team lead tasks.
6. Multiply by 3 to cover useless paperwork and obtaining idiotic necessary approvals to do anything
7. Finally, multiply by 3.14159 to cover all the other stupid shit that the idiots that run that company come up with.

It's only a slight exaggeration. Tasks that required less than a day of actual coding would routinely require two weeks to accomplish and get implemented.

Give me your estimates.

Producer: "We need this new feature by next Wednesday's release. Enter estimates into the task, ok?"

Me: ಠ_ಠ

hint for the estimate: by next Wednesday

There was a sales manager who was raked with overseeing me and another dev finish a last minute request project. He said at one point to the other dev that he was mad at developers because we understood something that he would never understand.

This same manager would often sit in on estimation meetings and constantly say that we were estimating too high and needed to come up with faster solutions. When we would offer him with caveats of possible technical debt or unintended side-effects/performance issues, he'd want us to go with that solution. He would then complain that we were always wanting to work on technical debt and that our application was slow. He would also ask for very high level estimates for large, unscoped features/apps without any meaningful level of detail, then hold us to the high-level estimated date even after revealing additional features previously unmentioned.

We learned to never compromise on the right solution and to push back hard on dates without proper scoping. They didn't learn, so I and most of the good devs left.

If the project goes overbudget it's because you fucking gave away the custom made software for too fucking cheap.

Not because of the amount of hours building this piece of shit site which btw I was never consulted on the estimates and not even mentioned about the 2 different designs for the same fucking site or even how it needed to be architected.

As a contractor you depend on your time, not on a fixed salary. No perks, nor fucking swag.

My advice is if the company thinks that working remotely is a perk, then fucking run away.

I can't stop myself from thinking like a computer when I'm sick.

The OS that runs my body is kinda fucked up right now. It was very vulnerable and now it got infected by viral executables sent out by an agent which happens to be on same work network that I'm connected to. Well, it executed and populated feelings of infatuation and crush in my heart drive. ( pun intended )

As a precaution, I patched the vulnerabilities by masking response of my Emotions API.

To further secure my system, I'll be executing memory intensive tasks that will also put my hardware to it's limits. According to my estimates, this will stall further execution of this infection and eventually kill them while rewarding me with upgraded hardware.

I’ve been interviewing with a startup for a Frontend Engineer role. In the interview they said they didn’t have a designer, that their founder and other devs do the design work. I thought “ok so they are still putting something together and don’t care much if the UI is crappy”, and still proceeded with it. I do the take-home test, it took a lot more than the 1-2 hours they said it should take (these estimates never seem realistic), I thought I did a pretty good job and send it back to them. I then got an email back from one of the founders, they really liked the code and my approach, but the UX was not good enough. He asked if I would be willing to iterate on it if given some direction? The direction: design your own version of our product. I refused. I thought this was a developer position, not a designer position.

Overwhelmed by a shitty codebase? Use the boy scout rule and leave the code you're editing a little better than you found it.

Worked wonders for me when I realized I could spend literal months refactoring and desperately needed a systematic approach.

Little by little that rotting house of cards will turn into something okay. It's a nice feeling looking back after a couple of months and see what you've done to make things better.

Also, make sure to remember the cost of wrestling with hurried legacy solutions in your estimates as well. Just adjust the level of bluntness depending on your work environment: admitting that things can/need to be improved can be unpleasant for some to hear even though it's true.

Again I ended working for a company where people love to pride themselves because they're 'agile'.
Basically they bought A JIRA license, that's all.

The CTO decides the estimates privately.
He assign the stories.
No idea what's a retrospective.
The sprint ends whenever he wants.
No CI.
New stories continuosly added to the active sprint.

That's the risk of agile, unchecked power.

Why am I so fucking bad with estimates? I am literally 20 hours over on this one thing because it’s so goddamn annoying to deal with.

Being able to make dev time estimates that aren't off by whole weeks.

I am calling this a premonition rant, of more rants to come.
I have a feeling in my bones.
We have a newly acquired fat cat customer with bucks to blow who we have done some digital work for already and swag bag of marketing perkiness.
I will call the CEO of this whale "The Porcupine"
The Porcupine has a business degree and industry experience, nothing to do with websites or applications.
It claims to be a visual perfectionist yet never delivers an overall coherent review.
It likes to fixate on minor brand style differences in websites and apps we have built.
The Porcupine seems to be always busy with policy and legal and other things rather than participating in their own projects.
Procrastination on feedback or reviews until the day before release is common.
Many overtime hours worked, not a sliver of thanks. The haughty attitude indicative of somebody who thinks web development is like desktop publishing.

"It's just code" in response to a crash production server change they were warned was a risk that borked all of our responsive templates and took 3 hours to fix.
Their entire brand is shades of pea green, grey and lime. No serif fonts because they are suck. Arial and Helvetica are boss.
One of my devs missed a CSS style on privacy policy hyperlink text that went times new roman and I had various account directors and our CEO on phone telling me how embarrassing it was for us to let this happen.
Anyway. They pay on time and the cost estimates for all the upcoming work are juicy.
We have shitloads going on for an upcoming hard date conference and everything is already compressing.
Therefore I can already smell doom and feel those porcupine quill getting closer to my ass as I beg their AD today if we have any feedback on the 10 or so project reviews yet?
Nope.

Fuck my company. Let the technology people work with technology.

I work at a small company who constantly brings in people who are absolutely useless. The project manager requires me to take items out of azure Dev-ops into an excel because he will not take the time to understand how a board works. The business analyst hands bullshit requirements in formats which no one but him can understand under the pretense that the Devs and architect can ask him when they feel like it. The CEO wants a power-point which again the technical teams have to prepare for him because the project manager or BA will not have time for it. However they make sure to gut the estimates handed over by the Dev team and introduce unfeasible deadlines.

Meanwhile the client has zero problems as the work still somehow gets done due to people in the Dev team overextending. Goddam leeches wasting mine and my teams time doing bullshit.

I am a senior Android dev, and I have an old colleague (iOS senior dev). We work on the same project, but in every estimation session he pushes a lot on the lower side: he estimates 4h a task that normally takes 6h or 8h, and the reason is that he has no social life. Right after work he starts working again from home (I can see all his commits), he also works almost entire weekends. I would say he works as average 12/13 h per day.
I don t want to work extra time (unpayed).
About him, it is his life, so I don t care...but at the same time this makes me pressure. I care a lot about quality of code, and I don t want to sacrifice it just for catching up. Most of the people in the team know that he works a lot extra time.

How would you handle this?

I usually work in a two person team on a hybrid application we are developing, using AngularJS and node.

This normally works okay, because he handles the back end (he's been on the project since January last year, I joined in August as a placement student), and I handle the front end.

However, due to Christmas holidays and such, he's ended up taking an entire month off, and won't be back until the end of January.

I've dabbled in back end before, some routes and that for SQL queries, but nothing serious.

Last Tuesday our core service for the application that needs to be updated in real time broke and pissed off the API provider because we were hammering them with requests.

My first day on back end and this happened. I didn't really know what to do, and had to call my teammate to ask what to do. I essentially just restarted things, and left them as is, until I could find a solution.

From there, I had to mock the operation of the service (which is a complex enough beast) to figure out the problem, and find a fix. Our app more or less hinges on this service, so if it messes up, it's the end times.
All of this while flying on what I've interpreted because the guy that's on holidays was the only guy that knows more about this project than I do.

To make things worse, the clients are being very particular because they're waiting on investments and don't have money to pay our company. So, if they're paying for 5 days work, they're going to put in 5 days of project development. The problem is that their interpretation of 5 days of project development has not changed from when there were two people on this project.

There are 40 tickets in this sprint (ends Friday) and 35 of them are assigned to me. Granted, not all of those take a day to do, but estimates don't mean anything, I guess.

Ganbarimasu.

Why do business and systems analyst even project managers try to give estimates for how long development should and will take? I hate how people who don't code and do any real work try totell me how long it would take me.

Hardest thing about software development to me is estimation of time needed to complete. There should be an algorithm that knows to estimate better than me, shouldn't it? Like google maps navigation knows precisely in advance when I will arrive somewhere taking a car or a train, perhaps they could do my development estimates for me?

I have just started working in this industry, and so annoyed by the fact that managers are insensitive to the efforts put in by the developers.
1. They ask for estimates, and sometimes consider it to be the hard line for everything and then they make you feel guilty if you are not able to live up to them.

-- I am not asking to be always lenient but they need to understand that this is problem solving and one might not be able to gage the problem at first sight. A problem might have several sub problems or a solution to one issue might raise compatibility issues with other which were tough to foresee .

2. Why do they always want an instant response to their email or query, a developer being online isn't just there to answer your damn obvious and sometimes stupid questions which can be understood just be glancing at the logs once.

-- How annoying would it be if the manager himself is being poked every other minute for trivial things. Does he have the same patience with his/her developers?

3. In tough times the manager easily delegates the responsibility to the developer and instead of standing by his/her side, interrogates them as if we have done some crime.

-- Wasn't this approved by you. Weren't you the one who had these stupid demands before and didn't let me do things the correct or optimized way. I am not saying I am always right, but you can be atleast open for feedback or discussion.

Why are you the first to take credit for the success and yet hold us responsible for any mishaps.

It's sad to see that some of these people have been tech developers.
I can go on ranting for many more things.
I am not saying all those people out there are like this. But trust me many are.

Note: I am not seasoned as you guys out there. I may even be biased by my own experiences. But this is in complete contrast to what I was expecting when I graduated from college and was excited to finally learn by working.

In "Sprint Planning", the team is supposed to come up with stories, break those down into tasks, estimate those tasks as a team, then let devs choose what tasks they want to work on based on the stories pulled into that particular sprint.

Instead, our manager creates the stories. He assigns the stories to each developer and then has that developer announce his theoretical tasks (without any research on feature's or project's requirements!) in front of the entire team. So, when I say, "I think it will take me 6 hours to implement this feature", he says, "6 hours? I think it will take 3." and then types the estimate as 3. I have so much rage when that happens. Then we continue to sit in the room for 2.5 hours where we go through this long data entry mess of him typing out tasks and second guessing estimates. There is no team deliberation or collaboration, its whatever the manager says.

While there are many issues I take with this approach, my pet peeve would be the second guessing of the estimates. It would make sense for teams members to second guess estimates as long as they are the same teammates who have the ability and possibility to take on the tasks themselves.

But I disagree with a manager seconding guessing an implementation feature that "I" definitely have to do alone, and they do not possess the immediate knowledge to implement it themselves.

Always double your level of effort estimates to any management over what it's really going to take. Always.

Asked to make high level estimates for something that has no scope.

Manager keeps asking to trim down the estimates. o.o

Where is this economic + social collapse that was promised?

%@&$4727;&2@@(&@&

Sweet talker but Incompetent colleague/team lead has given estimate of 350 story points (1point =1day) i.e more than an year and half, for one module to refactor. Worthless manager seriously considered to proceed with these estimates and ready to accept proposal.
When presented these numbers/estimates with wider audience, one senior engineer reminded everyone that module was developed few years back, in <2 months by 3 engineers.
Shame shame!

Manager: These estimates are wrong
Me: Why?
M: These shouldn't take too long
Me: Well you asked me to make those while I was busy with the mess design did.
Jr frontend: Manager is right. They shouldn't take too long.

*me knowing jr doesn't know the system nor coding standards*

Jr: I'll fix mine to get a more accurate estimation. Do you want me to do yours?

* Me thinking f*ck no*
Me: Just do yours.

M: Ok. Then we are settled.

He just wanted me to fit a 10 week project into 6 weeks while I carry the Jr and was complaining I didnt do it well.

Fml

PM wrote a really high-level requirement doc and asked me about estimates.

Me: Well, functionality-wise it will take 4-5 days provided the design is ready.

PM: Our designers are really full on schedule; Just do it! Expand your creativity. I believe in your taste of UX

Me: Listen, the implemented design will take much more time to change if we go back and forth. It's better to revise on the designer's screen.

PM: Oh don't be so modest! I trust you already. Just focus on the functionality, get it done first. For the design we'll talk about it later. Move fast and break things!

Me: ..Sigh. This is gonna end up badly.

I hate arbitrary deadlines.
Cocksuckers just pull them out of thin air and force me to give estimates about tasks that are impossible to give an estimate on.
(Spoiler: The tasks are the problem and need to be split and analyzed)

Project managers never ask Chuck Norris for estimations…ever.

Alright y’all what’s the longest minute:

Microwave minute
Google drive upload 1 minute remaining
Windows copying less than 1 minute remaining
MacOS update screen 1 minute remaining

Client: Can you give me an estimate of how long this change will take?

Me: (meets with other devs for a good estimate, around 2.5 weeks, and gives to client)

Client: Great. Oh by the way we have a one week deadline.

"Scientists discover the world that exists; engineers create the world that never was"

I've come to love this quote. We, the engineers, are shaping the world. We have the tools, knowhow and expertise to move mountains.

I said it before years ago and I'll say it again: all the other roles are meant to assist us, not the other way around. We don't work for managers, sales dept., bosses. They can't do shit without us. Why do we need them? To buy us toys, to sell our creations and suggest us how to shape our creations to make a better sell.

Quit slaving if you feel you are a professional. Quit bending over to sales' and mgmt nonsense timelines and demands. Hear them out, consider their concerns and give them YOUR estimates and approaches.

WE are the power of creation. THEY work for us. Not the other way around.

Does not apply to juniors. They are still learning their way around

Most pissed off I've ever been at work when was I attending some development meeting about the "slow progress we were making", in which the boss (same one giving us shit for being slow) came up with several new good ideas that he wanted implemented ASAP. Same thing he'd been doing all year; fucking up our plans and adding a metric shitton of feature creep. I tried to give realistic estimates for how long it would take to implement, and casually mentioned that working on this would also push back the other stuff on our plate, but he snapped at me and accused me of being a "negative influence" and "sabotaging the project", and went on in a long rant about how we didn't take the work seriously enough and that we didn't put in enough effort.

I was a hair's breadth away from flying over the table and strangling him with his keyboard cable, and the only thing that kept me in check was the tiny amount of steam I vented by snapping the pen I was holding in two. We'd been working overtime every day for months to try to meet his insane demands and accomodate him by doing all the changes and additions he wanted done, and I found his tirade - mainly targeted at me - highly unfair.

Somehow I managed to exercise restraint, and I'm not sure if he even realized what happened.

Don't complete the task within estimates : You're slow.
Complete it before estimates: Your estimates suck!

Welcome to Whose Sprint Is It Anyway, where the estimates are made up and the story points don’t matter!

estimates you say? deadlines i say!

Luckily I don't work at a place like this anymore, but I sure hate it when a company touts that they are an effective company who has implemented agile "the right way", then when they describe their process in detail, it is almost exactly the opposite of what agile is supposed to be.

I've worked for a couple places that just couldn't get their head around the fact that one of the reasons agile exists is because estimating software is hard, and only after doing agile the real right way for an extended period of time can a company expect to have realistic estimates. The business can't go a week without hard deadlines.

You'd think that after doing this for 8 years I would've gotten better at estimates...

When you have no work all week long because you finish 3x as fast as the estimates. You ask for more work, and due to "red tape" you can't even work on the back log.

Time to sit and look busy :).

Sadly, this is too common for me... I want to be buried in code and tasks! Not sit and twiddle my thumbs.

I hate giving estimates, especially for projects when you hardly know the codebase. But yet everybody expects you to deliver everything and everything on time.
Just get off my back maybe then I can actually finish something.

Thank you for listening. <3

I once went to a client to get a brief for a website (the twat can't be bothered to write it, so he gets me to do it). I wrote all the details down and fired as many questions as I could. When I got back I wrote up the notes into a brief and sent it back to check before I costed it. He said it was spot on, so I sent an estimate. A few days later he must have shown it to another director, they both call me on speaker phone. Them: Will it do this, will it do that? Me: "It" doesn't exist, if you want to add some requirements then write or extend the brief and I will re-cost it.
They ignored that and rang a little later. Them: We have been discussing it, will it do .... and will it do.... Me: I repeated what I had said earlier, but my tone of voice had changed to reflect my annoyance. I never heard from these pathetic twats again. Moral: I always do background checks on a company, as well as accounts and financials check it's good to tap in to your network of colleagues, designers, freelancers. It can set the alarm bells going long before you commit any time.

Lesson Learned: Don't ever be so ambitious that you are no longer realistic about your abilities. I remember when I started out, I would give unbelievably short TTC estimates for medium/hard tasks that would undoubtedly take some time.

We basically don't unit test at work. I write some tests for my code and honest to God people complain I'm wasting time saying a test bed and manual tests are good enough. We don't write test beds for about half of our production code and rely on integration tests for the rest. We only test release builds which have been symbol stripped, I get handed a crash report with no stack trace that I'm unable to reproduce and expected to stay late to fix it for some arbitrary internal deadline.

I've since moved to R&D where basically I'm left to do my own thing so it's better.

We don't project manage. Project leads take time estimates and double them so management might cut them some slack. This doesn't matter because management made up time estimates before the project started. Last project I was on had a timeline of 3 months and took a year.

We have released broken products. Not that any of the above really matters, our software products have made about 50k revenue in 2 years. There are 6 people on software. Fortunately hardware has made about 3 mill. That said our hardware customers are getting frustrated with us as we keep fucking up, shipping broken products and missing deadlines.

I've been working there about a year and a half and will be looking for a job at the end of the current project.

I joined devRant about when I was most pissed off with my job, my rant frequency has definitely gone down since I moved over to R&D.

Business: how long would this pile of vague tasks that are not fully defined, and whose requirements we don't even know, take to finish?

Man I am tired of my company's dogshit software release process.

We have to commit to fucking estimates for 6 months (2 quarters), SQA shadowing dev by 2 weeks, and freaking estimates and work done at the end are not even close. And then we call it a minor release. These shitty estimates are based on requirements that basically say "we want feature x, plz make it work". It's some fucked up agilefall garbage that does not work for shit.

We rush like motherfuckers during the final weeks because estimates are bullshit but we are still expected to be done with every story points which somehow are days instead of other better metrics.

I swear this fucking bullshit has been designed by the board so they could plan their money entries based on the software release.

The only reason this company actually still holds itself up is because the engineers are good at their job.

Go fuck yourself high management.

I was recently hired as a fullstack developer internally in another team

While interviewing the manager specifically mentioned angular in the skill sets but *surprised* the codebase is in angular js

The previous ui guy didn't bother to upgrade to further versions and basically managed by adding band-aid fixes and patches to new requirements

Now the manager wants me to revamp the ui asap because it looks like something from early 2010s , i explain to him that I know angular ( previous projects was in angular 12 ) and this is in angular js which is totally different

To revamp it would basically mean rewrite

Manager thinks I'm cooking up excuses to avoid work or stretch my estimates ...

SWAG - Scientific Wild Ass Guess

Lost count of the no of times I have been asked for SWAGs by EOD.

I just got an email from the project manager:

"Hi Team,
Please make sure to review the 7/12 sprint requests for (x project). Please add your estimates even if the requirements are ambiguous. Thank you."

Ideas:

1. Scrape github

2. Attach feature size estimate (an abstract scale) as examples across many projects.

3. Use this as prompt/finetunning data.

4. Train and prompt on project descriptions relative to feature size and number of contributors/changes in the changelog.

5. Package and release a model that takes descriptions of ideas and generates reasonable estimates of time and manpower.

6. Optional, sell as an estimate service to corporate and make money introducing some sanity to the world for a change.

Logging work in Jira, because it goes against the whole ethos of trusting people to get the work done when they have to log exactly how much time they spent on each individual story. It also doesnt account for pair programming. so 2 people log the same time and it looks like the story took twice as long. I’ll stop now because I’m precariously close to opening the “time based estimates” can of worms and thats for another rant.

Almost..

I am a web developer and assigned in a project as Infrastructure Engineer AND Penetration Tester because no one is available. I survived that hellish experience, i learned clustering and other advance stuff on my own, studying even late at night, no training..just youtube videos. PM (who is currently has little to no involvement in this stage) has very little appreciation in what im doing(research, server estimates, diagramming, documentation, planning)

Does anyone else question their career in programming from time to time?

I've been around this line of work for almost 7 years now and I still get these doubts once or twice a year.
Be it unreasonable deadlines, horrible people that I'm forced to work with or just outright incompetence.

My latest occurence of doubt was when getting assigned a task that initially didn't seem like a big deal, but it turned out to be months and months of custom work instead of going along with the standard components and design guidelines.

This was somehow missed in the estimate phase and once I got assigned to it a hard deadline was already set, to top it off the features was non-negotiable.

These kind of things really makes me feel helpless and really depressed. My work is all I have, and I don't really know what I would do if I'd change career path today.

There are a couple:

A system that updates user accounts to connect them into our wifi system by parsing thousands of processing files written in Clojure. The project was short lived and mainly experimental, It has complete test cases and the jar generated from it is still purring silently on the main application. It was used to replace an $85k vendor application that made no fucking sense. The code has not been touched in 2 years and the jar is still there. The dba mentioned the solution to the vendor, the vendor tried buying it from me, but being that it belongs to the institution nothing was touched, still, it got the VP's attention that I can make programs that would be bought for that level, it caught his attention even more when I showed him the codebase and he recognized a Lisp variant (he is old, and was back in the day a Fortran and Cobol developer)

A small Python categorical ML program that determines certain attributes of user generated data and effectively places them on the proper categories on the main DB. The program generates estimates of the users and the predictions have a 95% correctness rate. The DBA still needs to double check the generated results before doing the db updates. I don't remember how I coded it because I was mostly drunk when I experiment on the scenario. It also got the attention of the VP and director since the web tech manager was apparently doing crazy ML shit that they were not expecting me to do, it made them paranoid that I would eventually leave for a ML role somewhere, still here, but I want more moneys!!

A program that generates PDF documentation from user data, written in Go, Python and Perl (yes Perl) I even got shit from the lead developer since I used languages outside of their current scope of work. Dude had no option but to follow along with it :P since I am his boss

Many more. I am normally proud of my work code. But my biggest moment is my current ntural language processing unit that I am trying to code for my home, but I don't have enough power to build it with my computers, currently, my AI is too stupid, but sometimes it does reply back to my commands and does the things I ask it to do (simple things, opening a browser, search for a song etc) but 7 times out of ten it wont work :P

Wtf does it even make sense to ask devs to do estimates for the spike, planning and the implementation of a big feature containing other features which nobody has any idea how long it will take to do and what are the dependencies and to try to fit it in the next quarter release?

Agile my ass.

Whatever the fuck is 'absolutely accurate estimates'.

Why the hell does every manager I end up with think estimates are a reasonable thing to expect?!

I might have just git-committed the cardinal developer sin: not multiplying estimates by 3. Torvalds help me!

So a php app I developed a few months ago when I was first starting as a dev needs an upgrade. Pretty simple since I've known about said upgrade for a while, but the feature was never needed until today.

Told my boss it would take a day or two of refactoring and additions for it to work.

How screwed am I?

Asking for a precise or accurate estimate is asking me to predict the future, which is essentially asking me to lie to your face.

And I'm a terrible liar. Please don't make me lie.

#noestimates

I fucking hate doing estimates. It stresses me out. I just did it, for a requirement about migration. I'm on my way to a fight now with the PO, because "the estimated time is too long". There was an agreement that deliverables were not to have extensive documentation and unit testing will only cover 30% of each use case (I know, stfu), but that's gone so I have to do the whole thing. I estimated 160 hours coding time, 40% of that for docs and 50 for testing. I'm standing by it.

All that stuff aside, what bothers me the most about estimates is that there's lazy motherfuckers who say shit like "I can have their RESTful ws in 2 days, but I said a month, because fuck it" and generate a win-win situation for them and their company, because the client - practically everytime - will just argue for the task to be completed in barely 10% less of the estimated time, accept the proposal and be happy waiting, the developer will fucking dawdle and the company will be paid for more hours than it deserves. Ugh.

Fuck estimates.

PM: You developers are like craftsmen, you're so unreliable in your time estimates, I do not know why I bother asking you.

Looking up, thinking if you gave me time to investigate the issue before forcing me to give an estimate... *smile and wave*

Good PM you sod off !!

my boss some months ago: so there is this new project, and we're planning to slowly fade in and gradually increase the time you guys work on this project

new pm last week: welcome to the project, you're now 100% allocated to the new project, that's your highest prio now
me: ...what about the other projects? they might have questions xD
pm: don't worry about that, dealing with that is not your job

my boss this week: yeah no, the other releases are most important for our company. the new project needs to be subordinated and has lower prio, at least lower prio than critical and highly prioritized bugs.
me: so.... who decides which items from which projects i shall prioritize higher than the new project and how much time i shall spend on them?
my boss: it is your job to talk to people, give them estimates and tell them how many items you can work on, so they can decide which items they pick

so basically i'm having the feeling that i need to manage myself here. it will be fun to attend the new project daily standups and tell the new pm all the time that i couldn't do anything because i had no time. anyone else with this experience? is this normal? actually i liked our new pm's attitude "dealing with that is not your job". i should have known it was too good to be true ^^'

Told my client last october that I would not be doing a migration.

Two weeks ago they wanted me to do the migration and I told them I will do my best to create estimates but that it was the first time.

Gave them a resonable estimate to migrate the content.

And last meeting they cut the time by 70% to meet the budget.

Fuck the budget, can't pay then you don't get the shiny new toy.

I'm a contractor, not a fucking employee. So all the extra hours are on me.

Going to give them a piece of my mind today.

If I lose this client, i don't give a fuck.

Wish me luck. Looks like the feature I am developing is going to be late because QA doesn't feel like following the estimates we agreed on. We already identified that development was going to be the longest part of this whole effort and that QA was going to be relatively easy, but but no. Because this is the day we have to be "code complete", they don't want to test a relatively simple feature. In fact we had to talk them into even starting testing on it today. Even though regression day is Monday and they are basically going to be done testing their last ticket this morning. Like what the fuck were they going to do for the next 7-8 hours? They don't write any documentation. There are no reports to do. There are no meetings. Did they just want a virtual day off?

Edit: they are literally playing with people's careers here. This is not the first time I have had something delayed by QA even though they agreed that it was simple to test and it was delivered with enough time to fucking test. Then I get in trouble because of late delivery.

Client: “We need a very simple app where waiters speak orders, and it prints automatically. No typing.”

Also client:

Speech-to-text with noise

Identify table, dish, modifiers

Group orders per table

Add more orders later

Dual printer output

CSV reports

Budget? Less than a round of beers at the bar.

So tired of clients wasting time with "features or changes we absolutely have to have" but after researching planning and estimates "it's just not in the budget right now"

"Hey I know we're doing Agile but, just real fast for some paperwork, I just need a quick estimate, nothing complicated, of the LOC to convert our decades-old millions-of-LOC project from 32-bit to 64-bit, just real fast like whatever you can come up with in 30 minutes"

Estimates...? What estimates?

... You mean deadlines?

Don't even say your initial time estimate/guess out loud. It will probably become your deadline, and you probably assumed that most things would take a reasonable amout of time.

Bonus: Try to get onto projects that you think you can get interested in. Once on a project try to keep interested in it's success.

Lol so we had a meeting where basically the entire dev team got shat on for everything always taking too long... Now, I know a .lot of us suck at estimates but if it's all the time then do you think maybe we're not getting the best quality info to wok from?

Then they revised the WFH policy to 3 days a week in office. AND got pissy about the hours.

so I ask you all what are you hours?

!dev

When your retirement estimates says no matter what, you'll be earning more than you do now when you retire...

It's been 3 busy weeks. Had so much to rant about, but I could lurk at best.

We had 2 big features coming to 2 different projects. I told my boss it's take 3 weeks for the one I was working on. The guy working on the other one, said he only needed 1 for his. Guess who got labeled as negative, worrying too much over nothing, and so forth? Especially since a "much more complex" feature would take just 1 week!

Whatever. Fast forward to this week. I was done by tuesday, including testing of both features and deployment. By wednesday, I had even a good looking documentation. Everything was ready. EXCEPT. The 2 features have to go live together, due to various reasons. Guess who ia still a ling way from completing his task? Gueas who asked to postpone his deadline by 2 weeks? Guess who's gonna have to work on weekends for no extra pay?

Guess what? I know how to give an eatimate, and I rather be "negative" and schedule 1 or 2 extra days to be prepared for hiccups and what not rather than having to waste my free time for nothing.

FFS.

Rant one of monday!!

Monday stand up meeting....

Reviewing jira tasks
Front end:" well, I dont think that is a priority but IM NOT TEST DRIVEN DEVELOPER SO...."

Jira task? Local env for testing in minikubes.

Ahhh the cool startup isssss sooooo cool he takes decisions about that, model the app or even estimates the deadlines of the product (the product not jira tickets)

Isnt it cool? Why not give that power to juniors? Why not tell them they dont need to learn and junior is just something they label to pay cheap for them?

For the guys familiar with 3D printing.

Does your slicer also give you time estimates that are completely off? I'm printing something that would take 10 hours according my slicer. Started it at around 10 AM and its 1AM now and still printing. Halfway during the print I increased the printing speed to 150% because it was way to slow.

Is it just me or are the estimates completely off at each print and the longer the print takes the less useful the estimates are.

Any advice?

Moved from a gambling company to a government body. Got to say I'm less stressed about estimates now but more worried about standards here.

Stress and career development < No Stress and less career development.

Ask me in a few months.

Only if estimates were not a thing 😪

The Coding Apocalypse: A Dev's Rant

June 14, 2024

Okay, gather ’round, fellow code warriors, because it’s time for a good ol' developer rant. If you're reading this, chances are you’ve already faced the dragon that is modern software development, and you’re somehow still using "Agile" as a life preserver while the ship is sinking. So let's dive into the chaos that our world has become.

Here’s the thing: We’re living in a paradox where every other day there's a shiny new framework promising to be the “ultimate solution” while ignoring that it's just recoil from the last big mess. I mean, can we talk about JavaScript for a second? I’m pretty sure if you stand still long enough, a new JavaScript framework will spontaneously generate from the void. Do we really need another one?

And don’t get me started on Sprint Planning. It’s like playing Tetris with stones while blindfolded, hoping that all the blocks land perfectly. Spoiler: They don’t. The product manager’s eyes glaze over as they nod approvingly to your estimates, secretly extending deadlines in their minds. The 'flexible' deadlines then become rigid, unattainable goals, and who gets the heat? The devs, of course.

Also, can we address the insanity of microservices? Sure, splitting a monolith into microservices sounds fun—until you’re drowning in API calls and Docker containers. Debugging a distributed system is like trying to untangle a pair of headphones made of spaghetti.

Oh, and if one more person asks if we’re "leveraging AI" and "blockchain technology" for our simple CRUD app, I might lose it. Sometimes, folks, the wheel doesn’t need reinventing. It just needs a little grease.

Finally, remote work. Blessing and curse. Sure, I enjoy the freedom of working in my PJs, but the endless Zoom calls are killing my soul. Breakout rooms? More like breakdown rooms. The Slack notifications? Let’s just say my sound settings have a hair trigger on mute these days.

So here’s to us, the devs. The ones who stare into the abyss of JIRA tickets and laugh in the face of mounting tech debt. May your coffee be strong, your code refactored, and your deployments ever in your favor.

End rant. Back to the trenches. 🚀💻

At my company we have a rule that ticket estimates can only be pointed using numbers from the fibonacci series. So 4 point tickets are not allowed!

We’re also discouraged from giving an estimate larger than 5, and told that tickets need to be broken down into smaller tickets if we think it’s more than a 5.

Also, ticket estimates must include the full amount of time for dev, QA, AND deploy. Given how hard it is to work with our tech stack, few tasks actually fit.

All of this may sound fine in principle, but in practice it’s extremely frustrating. I’ve protested a few times but I’ve been told I’m outvoted and nobody wants to reconsider the decision that was made sometime in the distant past. I was also told that “most other companies do it this way”, so therefore we have to as well.

This is the first company I’ve ever worked at which had this stupid rule. Is it this way at your company? Is this a NorCal tech company thing? I’ve worked at several companies outside of the SV bubble, and never encountered this.

Don't you just love it when there is no formal spec. you get a few mspaint slides and told a delivery date, scope and slides are changed by management weekly, not necessarily informing you of it. Then when your failing, deadlines pass you by you still have no clear spec 2 weeks before release, partial backend because core business devs are busy doing support on the legacy systems. No frontend cause it's been changed, redesigned and you've been forced to change frameworks and technology so many times due to corporate policy and legacy systems with another dev group holding your balls with what they allow you to do and use. Id complain but at least we've been told to be agile. This is my life now, we lost all hope and stopped caring. And management wonders why the deadlines and estimates are all off.

TL;DR - an entire emulation of a closed source CMS to develop a theme

The longer version:

We are using a cms that is closed source, and we only have access to frontend files alongside twig files. The CMS is custom built but many aspects are in a very rudimentary state, for example it is nearly impossible to develop locally, we have to use an integrated text editor to code stuff.

So out of frustration, and for my development needs, I decided I would make an emulation based on Symfony 4. Also because my PM was pressing me to optimise our site. I wrote some custom JS to handle everything smoothly, a semi-sass framework and well-structured twig files.

I was also supposed to work with our graphic designer, but she didn't get any alloted time from our pm to work on it...

Now PM asks me to write a specifications document in order to make another company build the new version

I mean wtf, I'm so bored, I can actually enjoy my day by coding, and no, I'm just there to write the specs.

When I told PM I am currently building the new version, she's like "but we didn't validate anything", when she explicitly said I had a green Go to code it a few months back

Instead I have to make prezies and convert them back to PowerPoint because we have computer-illiterate people in the company who aren't flexible to understand simple tools.

Let's hope it won't get useless by Friday (I have a presentation to give, alongside my estimates and project management presentation)

Im bad at estimates so I created a Formula to calculate it:
Number of identities in database * 2 * pi / amount of free coffee in liters * expected uichanges from customer / (7 /rainy days in the week)
It is pretty rough but it gets the job done most of the time

Have you ever felt that you did such a piss poor job that you don’t even want to charge the client for it?

My manager needs accurate estimate

Estimating a rather simple looking project without a thorough examination of the client's code.
It turned out to be the worst kind of crap a human brain could produce. The project we estimated for 2 months is going to last 6... And if we decided to rewrite it the day we were to estimate it, it would be done in 6 weeks

Each day, I read the vast swath of ticket hell hole that is our JIRA.

I read tickets that are written by people with not just 0, but an undefined understanding of technology...

I read tickets that are technically impossible due to this 0 understanding...

And finally, I laugh in bitterness seeing the time estimates stack up to months and months worth of work for which the managers expect to be done in 2-3 weeks 😂

I've received new instructions at work and I would like to know your opinion. We are two at work, my boss and I..

From now on, projects are estimated, we own the responsability of delivering our tasks to the date each individual. We will work with estimates + error margin of 30%, meaning we do the estimate and add 30% to the hours. We also set a deadline date, ideally a week or two later - this date will be given to clients. If we have not met our estimates including the error margin, we do overtime. We have to own each task our selves, and personally take the responsability for our assignments.

when a web agency contacts an other web agency to outsource between 10% and 100% of the work (asking for estimates), and that web agency then asks you how complex it would be...
and you're the only programmer in the story...
and you're a freelancer.

I have a dream that one day the sales people will consult with a developer on time and effort estimates before making ridiculous promises to the client.

Product was not thrilled with our estimates we gave them for the next phase of our project. So they got the veep to give us 2 new team members - a new hire and an existing senior - in hopes that it will allow us to finish a lot sooner.

Because 9 women can make a baby in a month, right? Gods forbid we consider removing anything from the scope of this phase. Mind you, there's still another phase planned after this one before we even release the product.

I've just heard from the business person that we are giving high estimates on the projects delivery time out of spite. Are you fucking kidding me. All of that just because they wrote Hello World and they think they now better how much time it will take.

Not more accurately tracking my hours worked with estimates, then wondering why I feel like I've worked so hard for seemingly so little monetary gain.

How the fuck do you accurately estimate development time , testing time , fixes time ?

When your MBA boss bases new bonus on his own estimates of features...

Rarest of the rare moments when my client actually said to me that perhaps I was being little bit too optimistic about the estimates I had given for few tasks on the sprint and that I should probably put in more time just to be on the safer side. How often does that happen?

I hate quotes/estimates so damn much

Quote too high and we don't win the work
Quote too low and I screw myself/other devs over

And then there's the fact that most initial quotes for an entire project are based off nothing but a few marketing slides from the potential client; we do re-estimate after winning the work and nailing down what the client actually wants, but obviously it can't be too far from the initial quote

And then there are other people on the company (not devs, obviously) who like to casually expand the scope without checking how much time it'll add

Moments when you give wrong estimate and then have to sit up all night.
Fuck estimates. I will never get them right.

Been a team lead for a few years now but it seems that my job now seems to be chasing team members for estimates and deadlines 😡

Clicked "Reader View" on a Jira card in Firefox. Firefox displays a JSON object which it estimates is going to take me 17-20 minutes to read.
Go home, Firefox, you're drunk.

Last year my boss decided to outsource a project I did the year before to another company.

Now he wants my opinion on why this company estimates 10h to do an upgrade on a API interface I did on that project.

Like I remember details on what I did two years ago. And like I have any idea how this company is rigged to handle the project.

When your manager estimates your tasks for you.. :(

Having to give time estimates for custom projects involving functionality unlike anything you've done before - FUCK OFF. How is that possible?!

What's the point of doing estimates per quarter if you are gonna change the estimates to projects that are being worked on to match the release date?

Also doing estimates per quarter before doing investigations on the requirements is a fucking shit way to do estimates. Arguably doing it per quarter is also trash.

We are not doing hardware design for fuck sake, we work on software, you bunch of retards.

I suck at making estimates on my tasks. I recently estimated a task for 2 weaks but finished it in 12 hours...

Commit to management with "accurate" estimates...

ALWAYS multiple estimates by 2!!!

Idealistic vs. realistic sprint planning:

Idealistic:
p1: "Can you tell us why you think this user story deserves 9 workdays?"
p2: "Of course. We are using framework xyz for part ABC of component y, so if we were to adopt changes in this, we would need to do new test planning and adjust accordingly. The complexity is of linear time and so -"
p1: "Interesting. I had not thought about that. Let us discuss more"

Realistic:
p1: "Ok so, how long?"
p2: "um, 9 days"
p1: "k"
p2: "k"
p1: "and you?"
p2: "yeah 4 for this 2 for this 1 for this, rest is ok"
p1: "aight, meeting concluded gg"

The idealistic one can happen if there's team trust, but usually there's team dysfunction which causes for team silence and brewing of product issues later on. If only reality weren't this sad.

Working in an Agile manner provides numerous ways to lessen or eliminate dependence on estimates. #NoEstimates

Right now. I'm expected to train a guy in maintaining 3 different apps before the end of August. The manager wanted a complete plan for the whole process, with time estimates on everything. Then we put together a whole plan with a spreadsheet for the schedule and she wonders if we are "going overboard". If you expect this guy to be able to fix any issue by the end of this, theres no such thing as overboard. Get your head out of your ass. Meanwhile she is supposed to be finding a new project for me but I fully expect her to come back and say they need me to stay "just a bit longer". I cant wait for that meeting...

* vacation + flight mode

* being VERY clear thay each interaction with you will significantly prolong your delivery time, hence next time your estimates will be artificially increased to compensate for such disturbances [think like 2days to change a button color instead of 20 minutes]

When Email and Time-sheet is everything in the workplace....
They literally don't care about your work or about successfully deploying project, if you don't have it in timesheet then you did nothing.

They want me to work on totally new things and expect to get the results within week and when I mention this is new and I can't even give estimates, they want that to be in an Email. Like WTF!! you even know this is fucking new thing that only I'm working on, there's no one to help me.

And I'm here learning,studying so I can solve these out of scope requirements with best practices.

And in the meantime they also want me to work one few other things .__.

Fuuuuuuuck!!
CR estimates:
Part 1: 2h including testing
Part 2: 2h-2days-maybe never (small changes on horrifically fucked up project noone understands with tons of tech debt)

Managed to pull off the part two in one day.. //yay me?!

Additional day to unfuckup git fuckups (including but not limited to master head not compiling because a smartass included *.cs in .gitignore file which he also pushed..don't ask, I have no clue why..) which was a huuuge deal for me as I usually use only local repo and had no idea how to tackle this.. coworker helped out.. seems I was on the right way, but git push branchy was acting up & said I had to login & ofc I had no clue what the pass was set to (first setup was more than 2yrs ago)..so new key, new pass.. all good.. yay!

Back to the original story/rant: Now I'm stuck with writing jira explanation why it was done this way & not the way customer suggested. They offered only vague description anyways which would require me to do a hacky messy thing, ew.. + it most probably would require major data modifications after deployment to even make it work..

Anyhow, this expanation is also easy peasy in english..
BUT...
I must write it in my native tongue.. o.O FML! Spent almost 40mins on one paragraph..

Sooo.. if anyone will petition to ban non english in IT, I'm all for it!!

Estimates.. First, part of the team makes "high-level" estimates which are based on informal, incomplete, still-evolving specs and an unstable back-end. The project people report the estimates to the client and elevate the status of these inaccurate estimates to that of commitments.

Then, before the "sprint", we review our initial estimates *ahum commitments* in greater (technical) detail. Because there are still a lot of unknowns, we tend to estimate more buffer here (back-end is often not ready, always ping-pong between project people and dev-team about unclear specs, more work than originally expected, and often late modifications to the original spec).

When an estimate becomes more than 50% extra time at the "refinement", we are told: "sorry, we gotta do it in less" and when it doesn't work out, we're kindly asked to spend part of our weekend catching up at 100% pay rate (legally it's 150-200%).

FUCK THIS SHIT

*quotes used abundantly because these terms belong to "agile/scrum" terminology but we're only pretending

Currently having very funny project lead, who gives on the spot estimates for 9 years old very pathetic quality code having Android app in security domain. Memory leaks, bad practices, typos, CVEs etc. you name it we have it in our source of the app.

Since 5-6 sprints of our project, almost 50% of user stories were incomplete due to under estimations.

Basically everyone in management were almost sleeping since last 7-8 years about code quality & now suddenly when new Dev & QA team is here they wanted us to fix everything ASAP.

Most humourous thing is product owner is aware about importance of unit test cases, but don't want to allocate user stories for that at the time of sprint planning as code is almost freezed according to him for current release.

Actually, since last release he had done the same thing for each sprint, around 18 months were passed still he hadn't spared single day for unit testing.

Recently app crash issue was found in version upgrade scenario as QAs were much tired by testing hundreds of basic trivial test cases manually & server side testing too, so they can't do actual needful testing & which is tougher to automate for Dev.

Recently when team's old Macbook Pros got expired higher management has allocated Intel Mac minis by saying that few people of organization are misusing Macbooks. So for just few people everyone has to suffer now as there is no flexibility in frequent changing between WFH & WFO. 1 out of those Mac minis faced overheating & in repair since 6 months.

Out of 4 Devs & 3 QAs, all 3 QAs & 2 Devs had left gradually.

I think it's time to say goodbye 😔

How do you guys explain to your CEO, PM, boss [whatever] that you cannot give them accurate time estimates for debugging? 😅

If something i made has a bug, and uses external libraries, not even debugging my code (more like, how i used / implemented something has a problem), i obviously have to first of all check what the hell is wrong ! I dont just make bugs for fun and happen to know exactly what is the problem and therefore the solution ...

How on earth are you supposed to deliver a precise estimate of assignments, when your client wants the assignments estimated in parts, but youre not able to split it into parts because its a chain of assignments, that cant be split, like if one Thing succeeds then its possible to move on to next part? So many unknowns because you have to set time aside for unknown code behavior.. Sigh..

So we got jira tickets, estimates and hour logging, but bosses are still asking to give them a detailled weekly report on tasks...

I asked if it would be possible to autogenerate these reports from JIRA instead of doing all of it by hand. Should not be too difficult, yeah?

I got told no, takes too much time to implement and nobody updates their tickets anyways.

For real? I'll create a script in a few hours that does all of it, but you don't want to give me admin rights, you chuckle fucks! Also, make people accountable for not attempting to use tools properly instead of creating additional soulcrushing processes.

Like all those bullshit meeting updates on the same topic that never seem to go forward taking up half my mornings each day.

I work with clowns doing fuck all, all day long.

Our client supposedly managed our Jira board yesterday in preparation for the release to live.

It was a mess. We have two people on this project - so our effective maximum workload is 10 days worth of tickets.

The current sprint plus the next have over 60 tickets in them, with the other "light" sprints having about 15 days worth in them.

I know you shouldn't get caught up over estimates too much, but they're in place for a reason.

The client really needs a reality check, and to be reasonable. When looking from a macro perspective he loses sight of all reason and scope, trying to grossly overfill what the two of us can handle.

A junior and student placement dev can only do so much.

I guess time will tell how realistic 16th April is..

wait,
if there are 3.4 Billions FaceBook fake users, that means than there are also at least 3.4 Billions fake email accounts around. Jeez.

And the spam traffic estimates are at 260Billions email per day or 260B/3.4B=76 emails sent by each fake email accounts per day. Much less as probably fake email accounts are more.

So, only 76 spam emails sent per account per day. I think there is still room for a big improvement

I'm about to start as junior programmer. I'm taking a course which includes Scrum, where the teacher said '99.9 % of IT uses agile'.

That can't be right, right?!?

Or am I just being pessimistic? Can I get some estimates from the pro world, i.e. you?

All our estimated are too high because we build everything from scratch every time, but we can't white label anything because we have to always be billable and a customer won't pay extra for white labeling just so the next customer gets it cheaper.

I fucking hate being put on the spot. I'm trying my best over here to learn and improve but I don't know my entire project by memory and how every single little thing works, and it makes me feel like shit constantly having to say "I don't know" when asked about task estimates and work difficulty

Now I've made myself look like an incompetent moron because it's stressful and the one thing I was left in charge of I screwed up

Christ man since when did programming become a social management activity?

I spent last week trying to figure out estimates about how much time we'll spend in this quarter's project - like, 3 days on the schema, 4 days on the API, 5 days on the GUI etc. Why does management think that each part of the project is separate? Oh I forgot, they're management. I wonder how much work I could've done if management wasn't so obsessed in knowing metadata about the project instead of doing the project itself 🤔

Got a change request today. The client had written two lines.

The first line(specs): we would another installation type something like "blabla"(an existing installation type).

The second line just ask for an time estimate...

They same client have been known to use mspaint as the visual aid of how they want things to look, and it looks ugly.

My reply for the CR: The time needed to complete the task is 5 hours + whatever amount of hours I find suitable.