I really hate working on work that require constant reporting and decision making: I don't understand how people are olay with work like that. let me present 2 cases : for context we are working on a complete ui revamp of our app.

case 1 Screen A ui revamp.
task : change screen A ui as per new figma
me : evaluates, give estimates, make new screen by changing ui wherever applicable , adding logics for new screen wherever applicable , and removing old logics whichever not mentioned in figma. finishes a task in standard timelines
Engg lead : NO!! WHAT HAVE YOU DONE! WHY DIDN'T YOU ADDED THE OLD CHANGES/MENTIONED THEM TO ME! YOU ARE THE WORST DEV IN THE HISTORY OF MANKIND

case 2 : Screen B ui revamp
new eng trainee
- starts on screen
- ask doubts on how to make new ui box 1 on day 1
- ask doubts on how to make new ui box 2 on day 2
...
- ask doubt on whether to keep feature 1 form old ui on day 11
- aks the logic for showing box 3 on day 15
...
Engg Lead : UwU MY SWEET SUMMER CHILD. YOU ARE THE POWERHOUSE OF NEXT GEN. HERE TAKE THIS QUARTERLY AWARD AND THE KEY TO MY ****

wtf? i mean yeah i should ask questions if 9/10 changes are covered in the ticket and 1 festure is missed, but if you are asking for 2 changes and not putting 10 changes, why would i bother asking about the other 8? Its like asking for an apple from a farmer and then scolding him for not coming up with "5 sacks of green diced and cutted and packed in platic containers ready to be shipped" when he comes back with a single apple in hand. ASK FOR THE CORRECT THING!!

Happy Monday fellas. I'm gonna be pretty grumpy tomorrow morning because:

- Tonight's TO-DO list is writing unit tests and getting past a blocker to my project which I have been avoiding. Unit tests cause depression.
- After a recent bout of depression, I started smoking more weed than I was comfortable with and tonight starts my temporary sobriety. Withdrawal from THC causes more depression.

Wish me some God damned luck bros.

The next pirate bay is just "the internet without stupid age verification", I'm calling it now.

When everything works, but nothing feels right.

You ever hit that weird stretch where all your code compiles, all your tests pass… but somehow, everything still feels off?

No fires to put out, no angry PMs breathing down your neck — and yet, the motivation just isn’t there. You stare at the screen, pretend to refactor, maybe rename a few variables, and then just… stare again.

It’s like the calm after a sprint, except the calm feels more like quicksand.

Not burnout. Not boredom. Just... blank.

Sure, I'll just find the error in this very intelligible stack

(it's just HALF of the stack)

I spent the past two days running headlong into obstacle after obstacle after obstacle. I found solutions and workarounds for all of them, including for some obscure odd behaviors in Rails, and got everything working — at least as much as is possible.

At the end of it all, the proposed architecture is fundamentally flawed. It amounts to “we want to have our cake and eat it, too.” So I’ll need to argue with management and try to convince them to let me redesign this broken sewage system. I doubt it’ll go well.

I’m tired, boss.

For the people who work in the office, is there some music in the office or is the majority wearing a headset?

You can be jealous, it's fine.

Been at interview today for some mobile banking app. Female interviewer describes the process: tech scrrwning for their company, then tech interview for client company, then coding challengde than hiring manager offer. I said I am not doing that, I cannot pass those, my brain freezes at those challenges. I can offer pair programing up to two hours with their programmer. Interview ended quickly amd I am glad I stood up against that nonsense.

lol the UI has a new background and some color updates, but features that users requested last year and myself and my team have been working on for the past 6 months (and can generate millions of revenue for the business) get pushed back in the deployment pipeline.

these people are fucking retards.

I regret persuing Software Engineering as a career.

I am not sure how to grow. I graduated in 2020, been doing mobile(Android) development for last 5 years and after 2 switches, am stuck in a typical micromanaging toxic company with an average package and this is sucking the life out of me.

I don't feel excited about my domain. Earlier I had this twinkle in my eyes everyday I wake up, wanting to tackle the next big challange, explore the next unexplored area in tech. But now am in crisis

Firstly My domain(Android) itself is challenging. continuously evolving and people wanting to move to shiny stuff instead of what works. Wasn't technology the tool to fix problems? Why is it inventing problems?

2ndly when and where is one supposed to "live life"? i wake up at 6.30, leave for office at 7.30, reach office at 9.30, leave from office at 6 and reach home at 8.30 .

take 1 hour of dinner 1 hour of freshen up, and 6 hrs of sleep and poof! almost whole day is gone! why am i spending 20+ hours in a routine that isn't giving me any happiness?

I can't go to gym , I can't goto park to walk, I can't read a book, I can't make some side business/hobby, I can't play some ps game or go hang out with friends/family. is this normal?

Either am at an illusion that :
1. there are some companies that allow one to achieve all this with their remote work or
2. there are professions/business which allow this or
3. there are government job employees who love like this.

or everyone is doomed like me and we are all looking to die at early 50s. I sometimes think even a farmer is not that in pressure as us.

Lastly the work pressure to proof oneself every damn minute and the office politics. I just want to get out of this rat race

The latest and greatest bullshit at the workplace: when you're asked to be an 'ambassador'. This really just translates to: 'take on more work for free'.

Whenever management approaches you with 'honorable extra role', immediately ask how it's compensated and definitely don't do it for no extra benefits (a raise should be default).

Don't fall into the trap.

Ooooof. So I was booked off sick by my doctor not too long ago for a week and when I got back, I seem to have been removed as project lead with zero communication about this.

Talk about a fucking professional sabotage situation...

Glad I'm leaving as soon as I get a job offer.

Crocheted a hand puppet. Just because.

Plot twist: @dfox disabled comments to let us catch a break from @jestdotty’s ramblings under every single post.

How is MSSQL so popular? "Oh yeah, sometimes you have to use dynamic SQL because the compiler doesn't correctly detect the impact of DDL commands and rejects working code" god fucking what? Why does the compiler infer the future structure of tables after a DDL command if it can't do so reliably? In my world, if it becomes public knowledge that a compiler incorrectly infers something, the maintainer scrambles to remove the inference instead.

I also find it surreal that I have to disengage versioning on a table in order to be able to modify the version history. Like surely, there should be a mechanism to temporarily skip the hooks other than ALTERing the table into a regular unversioned database table and then ALTERing it back, rebuilding the versioning infrastructure from scratch. SQL is awful and MSSQL is doubly awful.

We have a bug.

I fixed it, then I said it was a super tricky bug, a race condition in the library code, and that I had to put on an issue and wait for their answer.

Boom, day off.

God I'm a genius.

Am I in a toxic work environment or not?

1. I suggested implementing some code guidelines for our team so we can all work the same way. Lead architect sends me a DM telling me to stop talking about it until after projectX is done because it might stress out other devs. Friday he talks about how important it is to use standardised tools and ways of doing things.
2. Spent a week working on a bug fix and they said solution is good, but then invalidated all of my work by DM-ing me saying it's unusable because i worked on wrong branch and he quickly fixed it over the weekend and I should just copy his (inefficient) code.
3. I ask him a basic question of what version the backend software is using and he doesn't even respond. I ask another team member who quickly helps me check. it would have taken 1 fucking integer to answer that question. i wanted to learn the backend stack, but not so much anymore.
4. Lead doesn't respond to project management software ticket mentions.
5. Lead randomly makes hotfixes to the QA server without prior notice so the backend randomly goes down at times during work hours and then my local copy of the front end stops working for no reason at all when I am trying to focus on bug fixes
6. UX/UI designer's screen designs look completely different than the actual app, so I spent weeks implementing a feature looking like his nice designs, then having to change it again, taking another week.
7. Generally poor comms
8. Leadership mentioned jobs are safe, then 2 months later retrenched a bunch of people.
9. People getting sick all of the time.
10. Nobody gives a shit about technical debt

What‘s the purpose of separating your code into "independent" modules if each module contains everything anyways?

dev communities can be the most toxic as well as the most welcoming at the same time.

just depends on what your timing is. You can get a bunch of links to help debug your issue or you can get told to "kill yourself".

You never know.

I meant to upload this Reddit post from r/TrueOffMyChest as an image, but apparently that feature is broken. So I transcribed it. This rant writes itself. It's absolutely discrimination and by consent of the state. This, plus age and viewpoint discrimination, is why I own and operate my own business. I refuse to be beholden to HR assclowns trying to virtue signal their way into their next promotion.

"So I did an experiment, I work in CS and decided to test what the gender bias is. So I took my CV And changed the name to a female name. I'd send it out with my real name, then a few days later (or few days before) with a female name.

Out of 100, my applications with a male name got 7 responses for interview.

Out of 100, my applications with a female name got 45 responses to interview

The female resume was 650% more likely to get a callback. And the resumes were identical.

So then I thought 'what about someone looking for working class jobs?' So I decided to focus on restaurants-servers, hosting, etc. Made a fake resume, and responded to craigslist ads with both male and female names. Sometimes the male went first, sometimes the female went first.

Out of 100, my applications with a male name got 10 responses to interview

Out of 100, my applications with a female name got 87 responses to interview

The female resume got 870% more responses."

Friday afternoon.
Boss: “Can we push this small fix before the weekend? It’s just a button color.”
Me: “Sure, what could possibly go wrong?”

Fast forward 20 minutes:

Whole CSS is missing
Login page is blank
Server panicked so hard it restarted itself
I’m now "that guy" who deploys on Friday

Moral of the story:
No fix is truly “small” on a Friday. :(

Still alive. Wrist’s been hurting lately so I’ve had to stop crocheting 😭

But I got into paint by numbers!

I noticed an increased usage of the word unalive, such as in "to un-alive someone" on youtube, spoken in the videos and written in the comments.

I suppose this is to avoid the word kill?

So we are at the stage of changing the language just to avoid using a bad word on a platform of hypersensitive woke snowflakes who will cancel you for saying a specific word regardless of the context it’s been used in?

Please tell me I‘m wrong. 😒

Monday - delivered feature1. Manager demands starting to work on new feature2. I start working on feature2.

Thursday - in late evening manager provides feedback from testing feature1 for which internal testing starts Monday.

Friday. I start investigating. Everything is fucking broken. Backend contract broken from BE side, UI broken by another team member's PR from FE side. Missing configuration from FE side that was not documented anywhere.

I start working on issues from my side, inform relevant parties and coordinate that they would make fixes on their side (ofc after getting a lot of pushback trying them to force me to write workarounds to work with their broken implementations)

My manager during the day: what was the reason for us being blocked now?

Me: broken BE, broken FE by another team member, missing undocumented configs. Too late (and incomplete) testing feedback. Having to switch to feature2 priorities before finishing everything with feature1. Basically all things out of my scope.

My manager: so just to clarify we are blocked from internal testing because YOU missed this? Why it wasnt caught sooner?

Me: due to 5 same reasons that I listed before, I can list more but would prefer focusing on getting things working today

Manager: Ok, as WE discussed let's focus on getting things working and discuss about improving this processes in the future.

Seriously it fucking sucks working in this bank as a mobile developer.

We are responsible for basically everything.

From scoping out work according to business requirements, documenting stuff, to creating/maintaining BE contracts and constantly double triple checking everyone else's work across the chain.

Actual mobile implementation or proper testing is like the last priority in this case. And yet we are the ones that take all the blame if we fail to meet arbitrary deadline.

Fucking hell. Im gonna start documenting all decisions of this retarded manager, I'm not gonna allow him to throw me under the bus due to failures caused by his own shitty decisions

In my company I now have 3 browsers.

Chrome for company stuff that only works in Chrome.

Safari for company stuff that only works in Edge or Safari.

And Firefox for actual work.

🤡

Management has reviewed DevOps which is already being shown to customers and wants to introduce a code coverage metric to show customers how good the code is. Code coverage now has to be 80% or higher across the board, it's been decided by management, and there is no discussion on this topic. The front-end presentation layer has minimal business logic and most of the code that exists is generated objects to shift data to the backend (which in turn mostly shifts it to a 3rd party API that does a lot of the business logic). I now have to write thousands of pointless tests while also being 85% billable to the client.
I think code coverage can be used as a tool, but should not be used as a metric to promote the product.
I suggested an automated e2e test might be better placed to prove that things are working, but have been told we're not going in that direction.
I'm close to writing a code coverage test that uses reflection to touch all of the code, catch all exceptions, and return a positive result.

They started measuring deleted and added lines of code as a metric for productivity at my company. I have heard it's been done in other companies among friends... WHO THE FUCK IS PUSHING FOR THIS!?
Like WHY EVEN DO THAT USELESS SHIT???

I work with a team of morons where they just keep overriding my code and business sending us mails saying this requirement hasn't been implemented so please done.

Those morons are just getting on my nerves

Your tasks are going slowly, let's have a meeting about it