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.

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.

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.

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?

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.

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.

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.

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. 🚀💻

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.

Reflecting back on my previous post regarding quitting my job without an offer . Today the final email from system came : my resignation is accepted, my lwd is 7th dec and portal no longer shows the with draw button. The small spark with potential to burn the world did burn it , so her we are.

3 people were supposed to be part of this seperation : my current manager, the avp (person who hired me, was sr manager back then) and HR. HR was on leave for 2 days and all my emails went into auto reply from her, and when she came back, she approved the resignation without any discussion.
my manager(EL), who is the primary cause of me taking this step, tried talking to me. I can't say its because of u, so I simply said WLB, I need work from home. She tried to bring facts : why wfh? you are doing fine in hybrid ? you are getting 6h work every day? your joining letter said all days working from office?
I didn't entertain those points. The meeting ended in 5 mins.

Next day I emailed again regarding my status and she was the person who texted me saying such emails are not acceptable, go to portal and initiate seperation. she shared the steps and as i was about to press the button, I got a call from the avp

I tried the excuse approach bit he was able to see through it (he was showing disappointment). his talking style is charming, so I eventually opened up to him. the call lasted 30 mins, it made me think and today morning I was thinking of alternatives and discussing with him on chat, ittle to my knowledge that my manager has already approved the resignation. fine, I guess.

But here is the main story: WHY DO I WANT TO RESIGN? why would I ask a 3 day office company to gove me wfh and write here that even this is a lie. WHAT IS THE REAL REASON? here are the points , most of which i told the avp in some way as well:

1. The most frank reason is disrespect. I have been in this org for 2.9 years and was one of the first 4 members to join. today we are a 20 people team, one of the 1st 4 came as product manager and is now senior pm, 2nd came in as SSE and is now EL (SSE-> Module Lead -> Engineering Lead). 3rd came as SSE and is now ML . I came as software engineer and is still a software engineer . I even helped hiring a guy with 2 yrs less experience than me and in 10 months he got a sneior position but not me

2. The obvious area of disrespect is when I try to put my point, but my points are not considered but rather needs to be approved by those peole who hold a title. I am a laughing stock among juniors

3. Even after doing flwaless work for years and not getting an ounce of respect, my smallest mistakes are openly highlighted and humiliated. There was once a prod bug that was caught during sanity but for that, I was shouted upon by this EL at 1140pm in night in a 3 person call of EL,an intern and me. this same lady joined 10 days before me and did nothing but politics and talkings to get a position where she is humiliating me

4. These people suck at management and end up making us feel like slaves. one mistake (from anyone) and we get called out in meetings, chats . Our estimates are questioned and negotiated because the "senior" thinks it can be done in lesser time .

5. New rules are enforced everyday , making everything a dev's job . unit test cases? developer will do . uat testing? developer should do. prod testing? dev's job after getting prod numbers whitelisted. war room testing of modules? dev's job . let other teams know of changes? dev job. making a list of all tasks,all estimates and hourly time spent by a dev in a sprint? dev's job. What is the responsibility of qa team and EL?

6. in past 2 years I added 500+ commits, worked on 450+ small to large tasks and almost 99% of app's features are known to me. but in first year I broke my left arm and took a month wfh. In 2nd year i got stage 3 cancer and took 2 months sabbatical. all this made my contributions z my efforts as 0 and I never got any appreciation once.

----

With all these issues, what else could i have done apart from putting papers? How much can I figjt the useless fights? I am not the loudest nor the most cunning person in thsoe rooms. And these 2 seems common attributes of both of those SSEs who got good leadership positions.

I am sorry I couldn't be a better fighter. I am tired of fighting : my life, my situation and now the fight to proove my worth in the only space that i am passionate and proud

So my non-tech manager has started doing all the estimates for us developers on features upon high management request to save time, because of course rushing all the estimates for the work to be done in the next 6 months is the best process in software engineering.

All the estimates are based on previous work. Sometimes it will be accurate, but most of the time it is absolutely not.

So I get a task estimated to 3 weeks but I planned for 5. Just fit it in 3 weeks.

I planned for 2 weeks but the original estimate is 5. Just fit it in 5.

What kind of crap is that lol? What is the point of us estimating work if management knows apparently better than us how to design systems?

You guys got any similarly shitty project management system?