When I worked for an online dating app, at one point we had the ridiculous idea to try to take a popular LinkedIn feature and convert it to a dating app feature in order to capitalize off of the success LinkedIn had with it.

The feature was LinkedIn endorsements. The idea was to allow the dating app users to get endorsements from people in their contacts lists on certain traits/features from a defined list (ex. Funny, smart, etc.). It wasn’t a terrible idea on the surface, but the way we planned to execute on it was insane and everyone knew it was going to fail. To avoid any controversy all of the endorsable terms were watered down to the point where no one would ever find using them/asking their friends for endorsements to be any fun. And the worst part was how we planned to get people to ask their friends for endorsements - management wanted us to build a contact list importer and just spam email contacts with “please endorse me” emails. The whole thing was ridiculous.

No one, including myself, wanted to build the feature/spam tool but management really wanted it so we had to build it. Like expected, it failed very quickly when it was clear no one cared about getting their real life friends to endorse them on some dating app, and the spam contacts took was ineffective and... spammy.

Computer Science is probably the only major where if you suck at it and end up dropping out, you're more likely to be a leader than someone who is good at it and sticks with it.

There were roughly 200 people in my freshman class majoring in CS, by my sophomore year that number had dropped to about 120. A lot of people dropped out because it was too damn difficult for them, and they switched to less technical majors like "Business Information Technology" or "Management Information Systems." Almost without exception, the people who dropped out are now managing teams of developers, they actually have programmers reporting to them. Seriously, WTF?

This isn't even the worst of it, there are people who majored in art history who are now "product managers," who take the word "manager" in their job title literally, they think they're above developers. Some of them will even profess with no small amount of pride that they "know nothing about technology." You can hear the pride in their voice when they say it, as if they're saying "I'm a lot of things, but at least I'm not a geek." Is there any other field of study where people boast with such pride that they know nothing about it? I mean, very few people will say "I know nothing about history" or "I know nothing about literature", and if they do say it, they'll say it with a bit of humility. When it comes to Computer Science though, knowing nothing about it is almost a badge of honor.

Rant the f**k over.

This week I quit the corporate life in favour of a much smaller company (60 people in total) and i never felt so good.

After 3 years in 2 big corporations, I began to hate coding mainly because of:
- internal political games. It's like living inside House of Cards everyday.
- management and non-tech people choosing tech stacks. Angular 4 + Bootstrap 4 alpha version + AG-Grid + IE11. Ohhh yeah. Not.
- overtime (even if it was paid double). I never did a single minute of OT for fixing something that I caused. I spent days fixing things caused by others and implementing promises that other people made.
- meetings. I spend 50-60% of the time in pointless meetings (I tracked them in certain time intervals) but the workload is same like I was working 8 hours / day.
- working in encapsulated environments without access to internet or with limited access to internet (no GitHub, no StackOverflow etc.)
- continuously changing work scope. Everyday the management wants something new introduced in the current sprint/release and nobody accepts that they have to remove other things from the scope in order to proper implement everything.
- designers that think they are working for Apple and are arguing with things like "but it's just a button! why does it take 2 days to implement?"
- 20 apps installed additionally on my phone (Citrix Receiver, RSA Token, Mobile@Work Suite etc.) just to be able to read my email
- working with outdated IDEs and tools because they have to approve every new version of a software.
- making tickets for anything. Do you want a glass of water? Open a ticket and ask for it.
- KPIs. KPIs everywhere. You don't deserve anything because the KPIs were not accomplished.

The bad part of the above things is that they affect your day-to-day personality even if you don't see it. You become more like a rock with almost 0 feelings and interests.

This is my first written "rant". If anyone is interested, I will post different situations that will explain a lot of the above aspects.

I hate ZenHub. For those who haven't heard of it, it's an agile project management solution that is hacked (and by hacked I mean really hacked) on top of Github.

It's touted as being convenient because you can have all your issues in Github and then look at them in epics and board format. Sounds awesome. Except it's not. For everything "convenient" it does, it severely lacks the most basic ticket management features that make any ticket management solution usable. Ex., you can't copy tickets. That's right - if you're creating 20 similar tickets, which I've needed to do in the past, you must create each one individually. New ticket -> add labels -> add assignee -> add title -> add description and then submit. 20 times.

ZenHub is so bad and so poorly conceived that many of those who use it have lost sight of project management reality and are blind to the 300 other PM products out there that are better.

True story: a couple of weeks ago people were celebrating because ZenHub added functionality to allow you to define what epic an issue belonged in while you were creating it. For those who aren't familiar with what that means, let me explain: before two weeks ago, when creating an issue in ZenHub, to fill out this "epic" field, you needed to first create the issue and then edit it to fill in the epic.

Let me break that down in devRant terms: it's the equivalent of not being able to add tags to a rant until you create it and then go back and edit it. Complete lunacy is the only way to describe it. And when they added the functionality two weeks ago allowing you to do it all in one step, people praised them!!!

Yeah, ZenHub sucks.

rant? rant!

I work for a company that develops a variety of software solutions for companies of varying sizes. The company has three people in charge, and small teams that each worked on a certain project. 9 months ago I joined the company as a junior developer, and coincidentally, we also started working on our biggest project so far - an online platform for buying groceries from a variety of vendors/merchants and having them be delivered to your doorstep on the same day (hadn't been done to this scale in Estonia yet). One of the people from management joined the team working on that. The company that ordered this is coincidentally being run by one of the richest men in Estonia. The platform included both the actual website for customers to use, a logistics system for routing between the merchants, the warehouse, and the customers, as well as a bunch of mobile apps for the couriers, warehouse personnel, etc. It was built on Node.js with Hapi (for the backend stuff), Angular 2 (for all the UIs, including the apps which are run through a WebView wrapper), and PostgreSQL (for the database). The deadline for the MVP we (read: the management) gave them, but we finished it in about 7 months in a team of five.

The hours were insane, from 10 AM to 10 PM if lucky. When we weren't lucky (which was half of the time, if not more), we had to work until anywhere from 12 PM to 3 AM, sometimes even the whole night. The weekends weren't any better, for the majority of the time we had to put in even more extra hours on the weekends. Luckily, we were paid extra for them, but the salary was no way near fair (the majority of the team earned about 1000€/mo after taxes in a country where junior developers usually earn 1500€/month). Also because of the short deadline given to us, we skipped all the important parts like writing tests, doing CI, code reviews, feature branching/PR's, etc. I tried pushing the team and the management to at least write tests and make feature branches/PRs, but the management always told me that there wasn't enough time to coordinate and work on all that, that we'll do that after launching the MVP, etc. We basically just wrote features, tested them by hand, and pushed into the "test" branch which would later get tested and merged into master.

During development, one of the other juniors managed to write the worst kind of Angular code you could imagine - enormous amounts of duplication, no reusable components (every view contained the everything used in the view, so popups and other parts that should logically be reusable were in every view separately), fuck - even the HTML was broken (the most memorable for me were the "table > tr > div > td" ones, but that's barely scratching the surface). He left a few months into the project, and we had to build upon his shit, ever so slightly trying to fix the shit he produced. This could have definitely been avoided if we did code reviews.

A month after launching the MVP for internal testing, the guy working on the logistics system had burned out and left the company (he's earning more than twice the salary he got here, happy for him, he is a great coder and an even better team player). This could have been avoided if this project had been planned better, but I can't really blame them, since it was the first project they had at this scale (even though they had given longer deadlines for projects way smaller than this).

After we finished and launched the MVP, the second guy from management joined, because he saw we needed extra help. Again I tried to push us into investing the time to write tests for the system (because at this point we had created an unstable cluster fuck of a codebase), but again to no avail. The same "no time, just test it manually for now, we'll do that later when we have time" bullshit from management.

Now, a few weeks ago, the third guy from management joined. He saw what a disaster our whole project was. Him joining was simply a blessing from the skies. He started off by writing migrations using sequelize. I talked to him about writing tests and everything, and he actually listened. He told me that I'm gonna be the one writing them, and also talked to the rest of management about it. I was overjoyed. I could actually hear the bitterness in the voices of the rest of management when they told me how to write the tests, what to test, etc. But I didn't give a flying rat's ass, I was hapi.

I was told to start off by writing a smoke test for the whole client flow using Puppeteer. I got even happier, since I was finally able to again learn new things (this stopped at about 4 or 5 months into the project).

I'm using jest as the framework and started writing the tests in TypeScript. Later I found a library called jest-extended, but it didn't have type defs, so I decided to write them and, for the first time in my life, contribute to the open source community.

Worst experience with higher ups:

The Office team at Microsoft suddenly woke up to the possibility of innovation from the grounds up. We were asked to come up with ideas. The best ideas were to be shortlisted by management.

That's what i had a problem with. People are generally bad at dertermining what will work. So instead of managenst shortlisting, everyone should have run cheap experiments with their ideas and we could then double down on the ones that showed promise. That's what is done at all internet companies. But the Office team's culture hadn't changed from the boxed software days.

I was asked to have faith in the judgement of management.

Well, Ballamer didn't let Office develop mobile apps for Android and Apple. When Nadella took over, he fixed that mistake. But because competitors had already gotten ahead, the Office team had to work on Saturdays for almost a year to ship it quickly. Meaning employees having to unnecessarily sacrifice their family time because of a strategic blunder by the highest management.

So excuse me if I don't have faith in the judgement of management.

Worst of 2020:

Seeing company get stuck in an organizational swamp. Devs tend to be reasonably good at working from home...

Management isn't. Meeting quality has gone down the drain, half of management thinks "if the boss can't see me why work at all?", the other half has constant calls with tiny working groups where nothing is final and everyone is left confused.

I'm convinced: Everything management is afraid of about allowing devs to work from home is based on projection of their own weaknesses.

They're not passionate enough to work without oversight. They might not be introverts, but extroverts are perfectly able to communicate poorly, especially when a few digital hurdles get in the way.

The average developer might actually be more attuned to the intricacies of emotionless text chats, and preventing disruptive elements in video calls.

Also, unless someone physically helps a manager to remove their head from their own ass once in a while, their "gut feelings" about the market and products are actually just amplified bias caused by their endless self-absorbed yelling into the echo chamber that is their stretched out rectum.

Holy motherfucking hell, have I seen some weird projects float by in 2020, pooped out by isolated product managers whose brain clearly has melted when they had to survive without office fruitbaskets and organizational post-it walls.

Yeah let's promote our international character, by giving away travels and hotel bookings, using pictures of happy hugging people in foreign countries... Great promo during a pandemic.

Or let's get "woke" and promote the "colored users" on our platforms, by training ML to categorize people by skin pigment (Apart from how illegal and ethically insane that is on multiple levels, about 85% of our users pick shit like anime characters and memes for their avatar).

Or how about we make a Microsoft Store app, even though the vast majority of our end users are students using cheap Android phones, older iPhones, Macbooks and Chromebooks.

😡

Anyway, now that I have dressed up my Christmas tree with some manager intestines...

Best of 2020:

I got to play through my Steam backlog, work on hobby projects, and watch a lot of YouTube.

All this pandemic insanity has convinced me all the more that I want to work way more in Rust, and publish way more on open source projects.

I became maintainer/collaborator on a bunch of semi-prominent libraries & frameworks, and while no community is perfect, I enjoy my laid-back coffee-fueled debugging on those packages much more than listening to another crack addicted cocksucker in a suit explain their half-assed A/B test idea to me at 9AM.

So, 2021 will be me half-assing through the spaghetti at my official fuckfest of a job so I can keep filling my bank account — and investing way more time and effort into stuff I find truly engaging, into projects with a heart and a soul.

Disclaimer: kinda non dev related. Just working to pay the bills right now.

The other day I ran for the train to work, don't want to be fucking late, right?

Arrived and this guy asked me this: (I have a sweating/transpiration problem but I'm fully aware of that)

"hey man, ever heard of fucking showers or deodorant?!"

Yes, I was sweating my ass off and you could smell me but I can't FUCKING help that.

It was very embarrassing and humiliating to get that kinda comment in front of like 30 people but I just swallowed it and went to work.

After the first break, a woman from management came to me and pulled me aside. A few people had complained about how that guy from before said some pretty humiliating stuff to me and she said that the guy received a warning and was told to fucking learn to treat people with respect, regardless of their (health) issues/appearance. I also got an apology and a sorry and if I could keep my eyes open for such behaviour in the future.

I'm very glad that she apologized although it wasn't her fault because I know I've got this health issue and I can't do anything about it yet but it can MOTHERFUCKING hurt when someone talks shit about me when I smell and I CAN'T FUCKING HELP IT BECAUSE THIS IS THE WAY MY BODY WORKS TOO BADLY.

I felt protected and safe about my issue for the first time in my life.

Thanks management!

Although I know it's nothing, the irony is real.

My room is connected to the power group together with 5 other people.

Watching a mass surveillance documentary.

Suddenly my power goes out, the rest stays on.

I know it must be a glitch in the newly installed power management system but damn the timing couldn't be better!

So I said I'd rant this yesterday but a long night of server management came in the way!

Yesterday @trogus mentioned in a comment that he thinks everyone deserves a place where they feel like home and this is that place for me along with some sub-places which derived from here.

So in this linux/foss chat yesterday I was trying to get into an IRC chatroom (all people there (or at least a lot) are also like minded on privacy/security). I don't want to use email signup if not absolutely neccesary (don't judge me, everyone there own thing) and I found out very late (after 20 minutes of instructions from a fellow devRanter) that this thing required email signup. I didn't wanna do that so I said that and started typing a whole essay of why I'd rather not do that and what my reasons are (privacy partly) but then the guy said: "haha you got it man".

For one second I forgot that I don't have to explain myself over there on stuff regarding privacy that a lot of people would find paranoid. Man, that feels like being home :).

I realize now I probably shouldn't have called out my manger's bullshit if I wanted to keep my job. We were told to work a Sunday and our PO called it a "Smack-a-thon."

I said, "No let's not use stupid names. Let's call things what they are. This is a management failure Sunday."

That was during new hire lunch, in front of my manager.

I worked the first Sunday. I refused to work the second one. I've also been refusing to work over 45 hours a week.

So I guess I could have seen it coming. My manager didn't even have the gums to do it himself. He had the HR lady do it, while I was working remote from home. She told me it wasn't a 9 to 5 shop and that people there are expected to work long hours (People on my team are working 80+ a week for several months).

I took the train in to get my stuff. No one was there. My computer already gone. Couldn't even say "Go fuck yourself to anybody."

So I feel better now. I haven't taken a day of since I started in February, so it's time for some vacation and an unemployment check.

It was a really terrible job, and terribly mismanaged. I'm glad I stood my ground and knew what I was worth. I wish my co-workers had done the same.

I should have tried to start a union.

I am a female manager at a small, mostly male company, and directly manage several people (all male). One of the six has worked for me for multiple years. Since he began his employment, I always felt he had a “crush” on me and kept my distance (as much as I could as his manager).

His crush has gotten increasingly more obsessive over the past year: constantly staring at me, using absurd reasons to contact me through email/messenger/texts, whether at work or evening/weekends, and getting extremely emotional/upset if I do not frequently talk with him or provide feedback for his every task. He never says anything inappropriate or makes any advances but is making me increasingly more uncomfortable.

My tendency to avoid the employee combined with my obvious annoyance with his increasingly absurd reasons to interact with me is reflecting poorly on my management skills — to the extent that my manager is questioning my abilities to manage.

I would absolutely love it if people would write their own stupid code instead of blindly mixing everyone else's mental diarrhea together and pouring the resulting mess into their bloody stupid IDE. At least then I could insult them properly. As it is, they're outsourcing their fucking stupidity to the lowest fucking bidder and then bragging about how quickly they get everything done. And management eats it up! No wonder everything is a slow, tangled, unmaintanable mess.

I can't fix much of anything because almost none of it is in my control. It's all autogenerated bullshit glued together with laziness and poor taste. "But Root, why is fixing this taking so long?" Gee, I wonder why. Maybe if someone had built it somewhere in realm of correctly the first time, it wouldn't have all fallen apart when someone looked at it the wrong way!

Seriously, there's no way this pile of stale fertilizer could have passed QA.

Last week my company fired 4 people (on top of 15 more over the past few months). This week they silently pushed a change to all of our machines that changed our wallpapers. The wallpaper was a picture of someone in upper management staring at you with wide eyes.

They claimed it was a joke or something but the office didn't see it that way. At best it was incredibly tone deaf and stupid, at worst it was a way to tell employees that they are always watching.

I have no idea how management could be that fucking out of touch.

I'm currently on my way to Japan on vacation.
This is how it went so far:
😁 - Arriving at airport early and excited
🤔 - Find out our flight is delayed. Oh well it might now be by a lot
😥 - Find out that it's 2 hours delayed and we will miss our next flight
😤 - Arrive at Frankfurt airport, and stands in line for 2 hours to the service desk
😡 - Arrive at service desk to get told that we have to go to a special service desk to get rebooked
🤬 - Get a ticket with our number in the queue. 125 people in front of us.
😴 - 4 and a half hour later, get get informed we will need to stay at a hotel for the night, and that we'll be flying at 6 pm the next day
😑 - Get to hotel and crashes (this is by 1 am now)
🤬 - Wakes up 6 hours later because we have a room right next to a construction site

Pro tips for Lufthansa and the imbeciles in their management and staff:
1. Inform people. You fucking knew the flight was this delayed, and you could actually have given people a choice at the beginning of their travel.
Now you had to put 100+ people in a hotel.

2. Bring food to people. Spending so much time in an airport leaves people very hungry. (Pssst, chocolate, candy and French potatoes are NOT food)

All in all, just fuck Lufthansa and their handling of this situation.

Fucking great start to the vacation. I'm already more exhausted than if I just went to work...

My old employer used to used a highly complex people management system, made up of around fifteen or so different tools and packages. Apparently this had been the case for decades, so in my spare time, I wrote an entirely bespoke, extensible HR web application that could be easily modified without changing the code. It even supported the weird spider web management structure.

I took it to my area manager, who pushed it up the chain. Apparently the country representative liked it a lot, so decided to bring me on board for an implementation and test case. Fast forward a few months, and people are singing praises. I get a huge promotion, with a sizeable pay bump to match.

Sadly, most of my country was sold out to another org, who decided pretty much straight off to make 90% of us redundant. Last I heard, though, my app is now in use in almost every operating country around the world. Not bad for something I wrote in my spare time.

I'm waiting for them to need modifications, because I never had time to complete the documentation...

"Attention micromanagers
If you don't trust your employees to
work from home, you've hired the
wrong people, or your management
style needs updating. Either way,
you're the problem."

Seen on linkedin today

Two thousand fucking eighteen people!!!!
Stop this non sense "get a plane" for a fucking meeting that could be a fucking video conference.

Wtf? Everyone here seems to be addicted to flying, specially upper management... And if we need a new switch to keep the network running? Oh, for that we have no money :)

Q: WHO THE FUCK USES EXCEL FOR PROJECT MANAGEMENT?
A: My Product Manager

Excel because she cant wrap her head around using Trello. WHAT THE FUCK!
Some people exist just to make things more difficult for everyone else. Fucking pain in the ass.
This person is one of the most incompetent one I have ever met.

I dont have enough words to express my rage right now.

Corporate joke

A woman in hot air balloon realized she is lost...

*She reduced altitude & shouted to a man below :-*
_"Excuse me, can you help me? I promised a friend to meet him an hour ago but I don't know where I am."_

*Man below replied :-*
_"You are in hot air balloon 30 feet above the ground. You are at 41 degree North latitude & 59 degree West longitude."_

*Lady :-* _"You must be an engineer."_

*Man :-* _"How do you know?"_

*Lady :-* _"Everything you told me is technically correct but useless & the fact is I'm still lost."_

*Engineer :-* _"You must be in Top Management."_

*Lady :-* _"Ya. How do you know?"_

*Engineer :-* _"You don't know where you are or where you're going, you have no technical knowledge._
_You made a promise, which you've no idea how to keep & you expect people beneath you to solve your problems..!

I am a tester by profession, But I love coding. Sadly my organisation doesn't allow people of my profile to install IDE/ Programming softwares... So I had to work with what I had... VBA, MS Office...

I started to work on few small Ideas, then I and a friend worked on a macro which automates a 5 year old manual process... It became a Hit ! It changed the whole process... My manager started to highlight it everywhere... Other manager started to come to us for helps....

So I learnt MS Excel Vba, then MS Access vba... started to become an expert...
Now the whole onshore and offshore management knows us by name....

This excitement made me explore other programming language band fell in love with Python and JavaScript...

Now I made a virtual bot for my manager....

That small project paved the whole way of my programming passion...

$work: Ey @Root, make this super simple thing.
$work: No, not like that.
$work: It also needs to do A, B, and C.
$work: No, not there. You should build it somewhere else, but I won't tell you where.
$work: You need to build out F and G, too.
$work: What do you mean you don't have the data? Just ask support drone #3. (who directs me to #2, and that one to #8 who doesn't know, and that one to #12 who won't answer)
$work: Why can't I do K, Y, or S? You should be able to infer these from the mind of whoever wrote the ticket by its wording, despite no mention of them whatsoever.
$work: Are you done yet? It's a super simple ask!

Our boss keeps mentioning that the company is good to people who put in long hours and work weekends. We're all salary and there's no extra money on the table; just references to bonuses.

I'm sure when I'm 75 and in hospital with pneumonia, the last thing going through my head will be, "Man, I wished I had worked more hours on that backend for the app for that fast food company that gives the world diabetes."

The company can't give me summer back. It can't give me a 30C day in the middle of the winter. Even asking employees to work long hours and on weekends constantly is a sign of poor management, poor planning and the inability to value people's individual time.

Today I visited a partnered company, best summarized as "our people are the best at what they do, although we haven't figured out what it is that we do".

It was fucking awful.

Halfway a presentation about "capitalization on the internet of things" which featured nothing about hardware or protocols at all, a guy stood up and started talking about improvements on ecdsa and schnorr encryption or something... for no apparent reason. Then followed a bunch of pretty slides about the sharing economy... after which the CEO concluded with some vague speech about decentralized management of assets in a globalist world or whatever...

It was like a bunch of pretty smart people all had been locked up in some kind of closet with mirrors on the inside for six months, discussed their best ideas with their own reflections, then immediately grouped up and convinced an investor to fund their startup.

Ugh, I have to wash my ears and eyes with bleach. My brain is flooded with pretentious bullshit buzz and over the top startup decadence.

Actually, I think this sums it up best: There was a framed oil painting of the CEO with his dogs in the conference room, and the bathroom had a large marble Charizard statue watching me pee.

So that coworker of mine who got promoted to manager keeps continuing on abusing her new power. She convinced upper management to implement a new policy where you would be disqualified from your monthly performance incentives if you take 2 total sick days a month. She says this is to reduce the number of sick days people take, which of course upper management loved hearing.

By the way, since she's a manager now, this particular policy doesn't affect her - it only applies to us in the trenches. She can still take as many sick days as she wants, since being a manager she can work from home.

Needless to say, save for a couple of suck-ups, she's lost a lot of friends and made a number of enemies in our department, particularly on our dev team.

I want to vomit everytime rich people in upper management says stupid shit like "working for money in this company is a sin. Work for higher reason"

Hello, if only I get paid as much as you earn just by talking random nonsense in every meeting, I would be glad sharing the same shit quote like that to other employees in the company.

Company wide ban on headphones at desks, because how can people be working if they're listening to music? Never felt so miserable in my life.

Fuck fuckitty fuck, with a side order of bollocks. May the senior management of this tight arsed tin pot cowboy outfit of a company all sleep soundly at their desks until Doomsday while the rest of us keep them in business. See, I'm not bitter...

Ask questions during interview.
Ask about trainings - it's usually a good sign when company offers training budget. Ask about specifics - sometimes it's a shared pluralsight account, and nothing else, which means that that had an idea and half assed it into existence.
Ask tech recruiter about overtime, a good sign is when they have no idea or say that it must be budgeted and scheduled - it means that it does not happen often.
Ask if it is possible to select and change projects, and how often it happens - if often, it may be bad low level management, or people learning new things and jumping between projects.
Also make sure to ask about rules for promotions and pay rises. Good company wił have a clear set of rules in place.
All of the above apply to mid to large companies.
For small company, i'm sure it will be different.

hey there, long time no rant.
remember that manipulative, sociopathic angry manchild turdface PM, the kind that gives you a never ending rant inspiration? the one that got immortalized in like 90% of my rants?

well... it's time for the final update.
i decided to leave the team some months ago. my boss reacted very cool and supportive and suggested topics i could work on instead. when i told my colleague, he decided to leave the team at the same day. we both also complained at HR and added some papertrails about PM's shenanigans.
shortly after, another guy from the team quit and left the company, and i know that it was 100% because of this PM.
so, there were 2 devs left from originally 6 in PM's team.
some other people in the environment of this PM quit, one of his subordinates and someone from a greater project in which the PM's project was embedded.
after some internal investigations and discussions, the PM's team was completely kicked out of this greater project, since after ~ a year, this team was neither able to deliver anything useful nor to define what it actually was what they wanted to provide. instead, they actively blocked the project, solution finding and cooperation between teams. and this is quite very much PM's fault.

the final move came this month when PM got fired. i think, management finally realized that he is a total fraud who has no clue about the whole matter (neither what devices we build nor about software development). or management. or leadership. and that all he can do is produce hot air and bullshit people for some time to make them believe he knows something.
not sure how long he'll still be around, but i'm happy when i don't have to see his face ever again. i'm just sorry for the next company he'll be moving to...

Manager: Messages not visible! bug ticket!!!!

Dev: oh fuck, there's an issue with our chat system, not good! _inspects ticket_ oh, it's just a display issue that actually is according to the previous spec, yawn...

Dev: please describe the bug better next time, I though we had a major outage, this is simply a small design issue...

Manager: ...

Dev: ...

I think I'm quitting soon guys. I literally do not get paid enough to deal with these incompetent idiots each day.

Meanwhile:

Management: forget your shitty salary, take one for the team, you get 3% of the shares in the company!!!!

Dev: what fucking shares, you haven't even converted to a corporation yet, THERE ARE NO SHARES

Management: ...

Dev: ...

Oh yeah and they called me at 6:30 PM today: "so i guess you are winding down for the day"

fuck outta here i haven't been working since 5 you fucks

jesus i swear some people need to screw their fucking head on straight, so far gone into the hUsTlE CuLtUrE they don't even know what reality is anymore

So a friend called me over to his newly opened company. He just started, along with two other partners, so 3 of them on the management structure. It started as a service-oriented company, not single-product based company. Strategically, over the course of 4 years, these two other bosses kicked my friend out. I followed. All the people in the company eventually followed. Now we are about to start selling our services to them for around double the fee. #justice

What an absolute fucking disaster of a day. Strap in, folks; it's time for a bumpy ride!

I got a whole hour of work done today. The first hour of my morning because I went to work a bit early. Then people started complaining about Jenkins jobs failing on that one Jenkins server our team has been wanting to decom for two years but management won't let us force people to move to new servers. It's a single server with over four thousand projects, some of which run massive data processing jobs that last DAYS. The server was originally set up by people who have since quit, of course, and left it behind for my team to adopt with zero documentation.

Anyway, the 500GB disk is 100% full. The memory (all 64GB of it) is fully consumed by stuck jobs. We can't track down large old files to delete because du chokes on the workspace folder with thousands of subfolders with no Ram to spare. We decide to basically take a hacksaw to it, deleting the workspace for every job not currently in progress. This of course fucked up some really poorly-designed pipelines that relied on workspaces persisting between jobs, so we had to deal with complaints about that as well.

So we get the Jenkins server up and running again just in time for AWS to have a major incident affecting EC2 instance provisioning in our primary region. People keep bugging me to fix it, I keep telling them that it's Amazon's problem to solve, they wait a few minutes and ask me to fix it again. Emails flying back and forth until that was done.

Lunch time already. But the fun isn't over yet!

I get back to my desk to find out that new hires or people who got new Mac laptops recently can't even install our toolchain, because management has started handing out M1 Macs without telling us and all our tools are compiled solely for x86_64. That took some troubleshooting to even figure out what the problem was because the only error people got from homebrew was that the formula was empty when it clearly wasn't.

After figuring out that problem (but not fully solving it yet), one team starts complaining to us about a Github problem because we manage the github org. Except it's not a github problem and I already knew this because they are a Problem Team that uses some technical authoring software with Git integration but they only have even the barest understanding of what Git actually does. Turns out it's a Git problem. An update for Git was pushed out recently that patches a big bad vulnerability and the way it was patched causes problems because they're using Git wrong (multiple users accessing the same local repo on a samba share). It's a huge vulnerability so my entire conversation with them went sort of like:

"Please don't."
"We have to."
"Fine, here's a workaround, this will allow arbitrary code execution by anyone with physical or virtual access to this computer that you have sitting in an unlocked office somewhere."
"How do I run a Git command I don't use Git."

So that dealt with, I start taking a look at our toolchain, trying to figure out if I can easily just cross-compile it to arm64 for the M1 macbooks or if it will be a more involved fix. And I find all kinds of horrendous shit left behind by the people who wrote the tools that, naturally, they left for us to adopt when they quit over a year ago. I'm talking entire functions in a tool used by hundreds of people that were put in as a joke, poorly documented functions I am still trying to puzzle out, and exactly zero comments in the code and abbreviated function names like "gars", "snh", and "jgajawwawstai".

While I'm looking into that, the person from our team who is responsible for incident communication finally gets the AWS EC2 provisioning issue reported to IT Operations, who sent out an alert to affected users that should have gone out hours earlier.

Meanwhile, according to the health dashboard in AWS, the issue had already been resolved three hours before the communication went out and the ticket remains open at this moment, as far as I know.

I started to get super pissed off to people saying you don’t need a college, masters degree to get an IT job. Instead go and gain practical knowledge, showing your practical certificates projects is much better than a having a degree that doesn’t prove if you can do the job or not.

Is a degree absolutely necessary to get a job? No, I agree on that. You can tear yourself apart to be known make projects loads of people contribute in GitHub spend maybe years on practicing and creating stuff for your portfolio..

But excuse me what do you think people do in college studying degrees? Are we getting it from the shop in the corner on a Saturday?

Respect people’s achievements and titles. Especially Masters degrees push you hard, make you sweat apart from loads of courses you work at least a year on a practical project, dissertation, thesis and only pass if it is your own opinion and findings. It is not like a multiple choice exam certificate or you study watch videos for few months and create a web page.

Don’t throw shit on people’s efforts and accomplishments without knowing how it is achieved just because you don’t have it.

Yes it is not necessary. Does it make you learn? Yes! Is it practical? Yes! Does it help you get a job? Hell yes! Why most companies look for degrees? Do you think they might know what it takes to get it and the skills and knowledge you gain?

Don’t come and say in IT degrees not worth it without even knowing how to draw UML. Without knowing IT management you go and be a leader later on, no clue on how to manage projects, people and soft skills sweeping the floor.

It doesn’t matter if you are a YouTube celebrity or a president. What does the title say? “Master” now go, respect and digest it! Don’t be a sour loser.

Ooh I am fierce today and not done yet

So I'm in the middle of the website migration that was made in Wordpress.

Just made a database dump and decided to take a look at it cause it looked really big for a site that only needs internal management. Found out they use contact form plugin which stores binary of attachments directly in database..

And people ask me why I hate Wordpress and so called Wordpress devs..

Why is it so important to some people to claim that "HTML and CSS are not programming languages"? I get it, you're a REAL programmer working with arrays, maybe tuples, objects and possibly direct memory management. Who the fuck has a right to call themselves a programmer for writing some brain dead markup or poorly designed selectors, right? Who fucking cares for semantic tags or nested selectors?

Just think for a few seconds about when you were taking your first baby steps to becoming the GOD ROCKING MEMORY HANDLER THAT WRITES _REAL_ CODE that you are today, and how good it felt to be able to create something that appeared on your screen. It felt pretty awesome, yeah?

Now imagine if someone much more experienced than you told you "You're not a real programmer, that is not real programming. You should see what I do, I do real programming".

I think you get it. Why spend your energy spreading bad vibes when you could spend it on something more productive. Like reading up on the new CSS4 specs ;)

My manager is an idiot and a complete asshole.

Knowing that I was working on a solution for an important problem, he sent an email to our customers saying that the problem cannot be solved, and the customers need to take care of it themselves. He sent this email the evening before I was supposed to present my solution to everybody.

It's not the first time something like this happens, but this stupid individual RESIGNED ONE MONTH AGO. He's in notice period right now, and nonetheless he keeps fucking people like he used to do. WHY THE FUCK MANAGEMENT DOES NOT BLOCK HIS EMAIL!?

This next one is dedicated to a couple of special people at my workplace:

- The person who uploaded internal-use-only code to a personal repository on GitHub

- The network team that has blocked any and all access to GitHub

- The obscured mass of management bureaucracy that makes it pretty much impossible for anyone at my level to make any sort of appeal

This one's for you:

*ahem*

WHY?!

It's sad. My teammates are resigning :( Damn management for not taking care of people that they already have. You hire new people with higher pay and let your existing people with lower pay teach them. I just feel like resigning too.

My friend told me stories about his colleague who's always against him.

One time, during their management meeting, that colleague suggested that they should have a suggestion box in the office.

So my friend proposed that they use Google forms. He presented how Google forms work and the majority got really impressed(except the colleague).

Naturally the colleague is against him, he said "this is not what I had in mind". He wanted to have an actual box and people write suggestions on paper and drop it in(suggesting the ancient way).

Every meeting, the colleague complains a lot, and my friend provides techy and convenient solutions.

Management and other senior leadership have been really shitty recently, I got showed up in a meeting in front of about 20 of my peers and people myself/them and treated like a fucking child.

So I took a week off, uploaded my CV and today, after about 30 calls with offers, I attended two interviews and got two amazing offers of employment!

More money, less responsibility, better career development, modern company and less stress!

I’m so happy and can’t wait to go into work on Monday morning and tell them all to FUCK OFF!

After completing my sprint and some lingering stuff in the backlog

Me: Hey, there's this tiny feature people have really requested, I'll go build it since I got nothing else to do at the moment. It'll only take like 1h

PO: Hmm ok. Don't work on that yet, we need to check with business people and agree on the user stories and bla bla bla

Me: Ok, well there's these bugs I can take care of then, I'll get them fixed, won't be long.

PO: Hmmm, we need to measure the impact first. Let me get back to you on that a bit later

Me: Meh, oh. I'll refactor this bad component meanwhile then.

PO: Have you created a story for that in JIRA? Create the story first and then we'll groom it and take it in when we've time

Me in my head: Dafuq! Im trying to work on your fucking project but you keep throwing all that business bueraucracy shit at me. What am I supposed to do then? Sip coffee in the kitchen and talk about the other fucking billion failed "new business opportunities" with my peers? Fuck this circle jerk of a billion management people all trying to make themselves important. Nothing. Ever. Gets. Fucking. Done!!!

Me: Ah right, I'll do that *proceeds to the water cooler*

When I learnt programming, sugar was still made out of salt and hence not used in coffee.

Also, we didn't have source level debuggers, only the "print" method. However, compiling was also slow. It was faster and more convenient to go through the program and execute the statements in one's head. This helped understanding what code is doing just by reading it. It also kept people from trial and error programming, something that some people fall for when they resort to single step debugging in order to understand what their own code is even doing.

Compiling was slow because computers in general were slow, like single digit MHz. That enforced programming efficient code. It's also why we learnt about big Oh notation already at school. Starting with manual resource management helped to get a feeling for what's going on under the hood.

Dear Atlassian Support,

In my life I had a lot of experiences...

But your software manages to replace all these experiences with a unique feeling of depression, hatred, anger... Only negative emotions.

Not once have I said anything good about your software - not once in > 5 years.

Whenever your chum bucket of mismanagement and misanthropy stops working, it's never the fault of the end user, the administrator or someone else.

It's entirely your fault.

Fucked up upgrades, lack of documentation, catastrophic handling of logging, lack of support of current database systems, lack of proper migration and clean up of plugins, ....

I could go on. But it's really just and endless tirade.

I wish I could stop management for even giving you money for the pile of poo you call software, but sadly they don't listen.

But there's hope on the horizon.

Thanks for making people go cloud only.

No one wants that.

It would mean entrusting that pile of poo to the craptastic hands of your irresponsible people.

No one really wants that.

Not even management who blindly paid the license fees all the times.

Thank you for your cloud only movement.

Maybe we can finally find an alternative and I can finally start a therapy for the PTSD I have thx to your software.

I know I am late to this but I have a happy story for this one.

My first dev job was awesome. Except for the pay. I had interviewed and taken the job based on the fact that I was done with my master's degree, but because of a paperwork snafu I wouldn't be receiving my degree until the spring. I was assured that if I provided proof of my degree when it was awarded I would get a pay rise in relation to my education. Well that was not to be. So this professionally and socially inept bitch I was working with was going to be ahead of me in her career because the people I worked for gave pay raises based on time served rather than ability and education.
So I started interviewing for other positions. Especially after government furloughs cut my pay by 20% for 11 weeks, causing me to max out my credit cards. All of my coworkers had my back. They went to the upper management and the higher ranking military people we worked for and explained the situation. They were my job references for my interviews. They got me a job that paid double what I was making. I still get the warm fuzzies thinking about it.
They were some of the sweetest people I had ever worked with. One of them gave my mom and brother a ride to the airport when I crashed my car. They bought me lunch when I was in dire straights. I really would have loved to stay but I couldn't afford it. That and winter in Utah fucking blows.

When I was still a noob programmer, I was working on a website for a big client. We had a demo coming up in big city. So we drove there several hours and went to their office. All the management board and shareholders and what not were there.

So we started the demo. Everything had worked perfect the night before. But on that day, we were right away greeted with some stupid PHP error right there on the first page. Had to fix it quickly so we could continue with the demo, so I logged into their production server with SSH and started fixing the code with vim. I was connected to the projector, so my horrid noob code with cringy joke comments was there for everyone in the room to see.

Eventually got it working, but I saw several people in the room facepalming hard. Can't ever forget the day. :D

I'm really happy today. I'm not sure why, my life is in ruins on many levels, but at work I'm having fun and getting a lot more responsibility now. I even get to lead a meeting on Monday and be part of the management of a project which means I'll have people reporting to me. I suspect it's a sneaky way to get me more invested in the company so I'll want to stay after my studies but I enjoy it regardless. I finally have enough I need to keep track of to warrant carrying a notebook around and it makes me really happy 😂Hope you're all having a great day too!

An important message:
PrOpErLy managing servers is HARD.

I get pissed off at customers with ZERO server knowledge who think they can manage their VPS. “Just get a control panel and a VPS” from some flashy provider that makes server management look way too easy.. Clicking around in their fancy control panel, until:

- they need help with their *self-managed* VPS;
- their email ends up in spam;
- they suffer from performance issues;
- they need to restore a backup;
- something breaks, because YES, things break

Way too little people are able to answer:

- when and how do you make backups?
- how do you monitor your servers and which services?
- how do you keep track of trend analysis?

Then I come by with necessary software. SNMP for trend analysis, Graphite for infrastructure health, Sensu for monitoring, Kibana, Ansible for configuration management..

Things that servers need but that customers have never even heard of.. because they can do everything in their control panel..

Until they come crying to me because it broke and they don’t even know how to get into SSH.

I think the ones to blame are VPS providers that tell the tale of how easy it is to install a control panel and never look at your server again.

Customers become responsible for something *business-critical*! Yet they don’t know how it works.

In the last project i worked in, the product owner wouldn't treat people as people but as resources.

The problem with that is you just look at people and their work in terms of a checklist and remain blind about real humans face.

She wouldn't understand the challenges of building something with an absolutely new stack which people needed to learn from scratch and put pieces together. She wouldn't be supportive of people trying out things and fail.

One fine day I told her that I was spending too much time on meetings and i should be excluding that time from available sprint timings.. she made me open my calendar in a screenshare session with all team members. Made me go through go through every meeting invite i had on calender and ordered which ones should i be attending from then and which ones i wont. That was insulting. It broke the trust.

I decided to not work with the project. Stopped putting my heart and soul into it and eventually got out of it in a month time.

Don't put your team into a position like this ever. You have to trust them with the problems they face and try to find a solution. Scrutinizing and micro management will always kill the team.

Hi guys!
That is my first...well, rant? No, not at all.

I found this community by accident. I was looking for something like this, but did not realize til now. I scrolled through some posts and it is awesome to read awesome stories and rants from awesome people.

I am a 21 year old SAP ABAP developer from Germany. I have finished my bachelor's degree (business informatics/business information management? German: Wirtschaftsinformatik) last August. I have always been interested in web development and teached myself some php basics when I was younger. I would love to do more things like that, but things have changed. There are lots of different frameworks, languages and stuff. It's complicated.

I am not sure if I have understood how this community works, but I am very excited to find out.

And, as I already mentioned, I am German. So please feel free to bash my shitty English. :D

TeamLeader: I need you to stop disagreeing with the decision of the management, the people in there are taking their decision for a reason.

IHateForALiving: When integration tests were failing, the management decided to comment out the ingration tests; god knows how many bugs slipped by.
When users had problems with the idiotic migration process the management designed, the management decided to remove down migrations; it took two weeks before the QA team started screaming, as all their machines were filled with garbage data.
I was writing type definitions for my code, you removed it. You effectively ensured the only person capable of working on that particular piece of code would be me.
I have been proposing for 8 months to make a unified scheduled jobs system, you all decided to create at least 5 different -and incompatible- implementations, at least 4 of them are total garbage with setTimeout, there's no way to ever unify them and God willing they never break, if they do there's NO WAY to find out even where tf they're hidden in the code.
Every time you were making one of those bad decision I was the only one warning you of the problems you were creating. The idiotic change of the day is going MongoDB+Angular: I can keep a low profile if you want, but when this blows up you can be damn well sure I'll handle my 2 weeks notice because there's no way on earth I'll be stuck with the aftermath of you lot taking technical decisions you are clearly unable to manage.

It doesn't feel good to be average at everything.

Life is depressing

I can't commit to anything hard enough to become the best.

Programming
Singing
Drawing
Story making
Sports

I'm just average.
I feel bad
I feel like I'm a waste of resources.

I'm tired of ranting.
This life is just tiring.
I don't have the patience

I'm average at commitments.
Time management

I see other people code and sing better than me and feel demotivated

I feel like jumping of a cliff cause no matter what I do, there's someone light years ahead of me.

I'm not even unique
Ultimately that's probably what I want.
To be irreplaceable.

I guess in this struggle to be relevant I'm gonna lose myself and if I do get there, I might not be as happy anyways.

So what's the point to all this

The best decision I ever made was moving from a big company to a very small one.

I used to work for a large international consulting firm in the model development team. Everything moved so slowly, there were huge amounts of pointless meetings and other time-sinks, we were surrounded by people who were being paid a lot of money but added little or no value, and the general atmosphere of the company was quite depressing. We spent more time having to make PowerPoint presentations for senior management trying to explain why you can't just hire 100 devs and have a product 100 times faster than we actually did developing a product.

I took a bit of a risk and moved to become the fourth person (and second developer) at a niche software producer to take over product innovation and lead product development. Immediately I felt so much happier and realised how much the previous company had worn me down. Everyone works hard and efficiently because your individual output is so much more important to the success of the company and the work you put in comes back to you financially without being syphoned by layers of valueless management levels or time-wasters.

Having responsibility, seeing the impact of your own work and being rewarded accordingly is so important for your sense of well-being. I urge you all to try it if you're stuck in a big company that's wearing you down. And if you're considering moving from a small company to a big one: don't.

Branch Manager without actual credentials (just a manager no real business decisions are made by him).

- Constantly is sick
- at home a lot doing „home office“ and not being responsive in company chat or emails
- is in home office 3-4 days a week while company policy clearly states one day a week
- watches YouTube a lot at work and calls out other people when they check their emails or quickly order something on amazon or maybe just listen to a podcast at work
- is a scrum master but rarely acts like it as in softens up rules as he sees fit
- backstabs employees in front of ceo when he actually entrusts them beforehand and says he is definitely in the employees side
- actually tried to physically intimidate me and another employee
- has no real technological background but chimes in on technical discussions and thinks it’s a new round of bullshit bingo
- does personal errands during work and books the time for it as work time
- claims people cheat on their time management entries and gets them warned and fired for it, while doing the exact thing himself
- knows he is trusted by the ceo but actually takes 0 interest in the future of the company
- tirades and gossips about other employees that just aren’t around at that moment
- is sexist at times
- very untrustworthy
- is responsible for a very toxic environment around the office

So that are his attributes - he got me warned and sacked because I supposedly committed fraud with my time management and caused the company financial harm - I had no projects or todos and was keeping myself busy with learning JS and python stuff instead of sitting around waiting for a ticket to come around.

Needless to say I’m glad I don’t see that guy any more. I’d break his jaw if I’d have to see him again.

THE FUCK WHY did the company which made the website I'm maintaining now ADD CUSTOM FACEBOOK LIKES AND TWITTER FOLLOWER WIDGETS - IN A SUBDIRECTORY OF THE THEME?

Guess what, you motherfuckers: One year after you made that damn page the Facebook API changed and your stinking widget is broken REQUIRING ME TO REWRITE MOST OF IT!

Also WHO THE FUCK LEFT HIS BRAIN ON HIS BEDSIDE TABLE the day he decided to HARDCODE ASSETS WITH AN http:// (no tls) URL? YES, browsers will block that shift if the website itself is delivered over tls, because it's a GAPING SECURITY HOLE!

People who sells websites that have user management and thus request authentication without AT LEAST OFFERING FUCKING STANDARD TLS SHOUD BE TARRED AND FEATHERED AND THEN PUT IN A PILLORY IN FRONT OF @ALEXDELARGE'S HOUSE!

Maybe I should be a bit more thankful - I mean I get payed to fix their incompetence. But what kind of doctor is thankful for the broken bones of his patient?

A woman in hot air balloon realized she is lost...

She reduced altitude & shouted to a man below: Excuse me, can you help me? I promised a friend to meet him an hour ago but I don't know where I am.

Man below replied: You are in hot air balloon 30 feet above the ground. You are at 41 degree North latitude & 59 degree West longitude.

Lady: You must be an engineer.

Man: How do you know?

Lady: Everything you told me is technically correct but useless & the fact is I'm still lost.

Engineer: You must be in Top Management.

Lady: Ya. How do you know?

Engineer: You don't know where you are or where you're going, you have no technical knowledge.
You made a promise, which you've no idea how to keep & you expect people beneath you to solve your problems..!!
😀😀😀😀😀😀😀

The 5 stages of project management:

1 - the Mission:
Receive a project

2 - the Vision:
Over confidence and optimistic time estimation. Tell people how quick you can finish it.

3 - the Climax:
Adding unnecessary features. Try to be innovative. Think different. Feeling like a Rockstar.

4 - the Bargain:
Does not aware deadline is not far away. Reverse all unnecessary or impractical moomshot features. A bit stressed

5 - the Embarrassment:
Unpredicted obstacles or incidents. Late delivery or fail. Feel like a loser.

Why management has such orgasmic attachment to numbers?

Example 1.
Mngr: split this into tasks
Me: done
Mngr: now estimate these tasks
Me: can't. Team is new and codebase is unknown. Any estimations would be subjected to huge error and I will not commit to anything if I'm not at least partially sure.
Mngr: but we need some timeline
Me: so give it yourself. I'm not doing it

Example 2.
Mngr: we need to measure how your knowledge sharing sessions impacts our organisation
Me: how?
Mngr: e.g. amount of bugs lessen in next quarter
Me: bugs can go up and down because of hundred other reasons. Also, knowledge sharing is just to inspire people, it's up to them if they keep educating and growing. Me sharing knowledge 1h per week, I can't guarantee they will understand and apply this new knowledge.
Mngr: but we need to measure it somehow, otherwise it is useless.
Me: <speechless facepalm frustrated>

Backstory: A few months ago, I wrote an inventory management web app for internal use by the sales team, logistics, and whoever else might need to use it.

Earlier this week: A few minutes before I usually leave, my phone rings. It's some dude I've never heard of. No idea what his function at the company is, still don't, probably never will, don't care. He's never used the app before, and says he's having problems. His cube's on my way out, so I swing by.

I'm not making this next part up. This dude is probably 60 years old, and he's using a very old looking gateway desktop (with the cow print logo thing on the chassis), running Windows XP (not a typo), using IE7.

I don't know what to say, so I just stare at the desktop, look at dude, laugh, and eventually explain that he's never going to be able to use the system via the web app until his rig is replaced.

What the fucking fuck is this. How could this have happened. How do our it people still fucking have jobs. Better question, how did this thing survive the y2k bug?

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.

Why management people thinks that a career path for any senior developer is to be a "leader" and be good in business side. Its like saying "hey you are a good programmer, let me take away that work you love to do and do stupid human resource management instead"

My last job before going freelance. It started as great startup, but as time passed and the company grew, it all went down the drain and turned into a pretty crappy culture.

Once one of the local "darling" startups, it's now widely known in the local community for low salaries and crazy employee churn.

Management sells this great "startup culture", but reality is wildly different. Not sure if the management believes in what the are selling, or if they know they are selling BS.

- The recurring motto of "Work smarter, not harder" is the biggest BS of them all. Recurring pressure to work unpaid overtime. Not overt, because that's illegal, but you face judgement if you don't comply, and you'll eventually see consequences like lack of raises, or being passed for promotions in favour of less competent people that are willing to comply.

- Expectation management is worse than non-existent. Worse, because they actually feed expectations they have no intention of delivering on. (I.e, career progression, salary bumps and so on)

- Management is (rightfully) proud of hiring talented people, but then treat almost everyone like they're stupid.

- Feedback is consistently ignored.

- Senior people leave. Replace them with cheap juniors. Promote the few juniors that stay for more than 12 months to middle-management positions and wonder where things went wrong.

- People who rock the boat about the bad culture or the shitty stunts that management occasionally pulls get pushed out.

- Get everyone working overtime for a week to setup a venue for a large event, abroad, while you have everyone in bunk rooms at the cheapest hostel you could find and you don't even cover all meal expenses. No staff hired to setup the venue, so this includes heavy lifting of all sorts. Fly them on the cheapest fares, ensuring nobody gets a direct flight and has a good few hours of layover. Fly them on the weekend, to make sure nobody is "wasting time" travelling during work hours. Then call this a team building.

This is a tech recruitment company that makes a big fuss about how tech recruitment is broken and toxic...
Also a company that wants to use ML and AI to match candidates to jobs and build a sophisticated product, and wanted a stronger "Engineering culture" not so long ago. Meanwhile:

- Engineering is shoved into the back seat. Major company and product decisions made without input from anyone on the engineering side of things, including the product roadmaps.

- Product lead is an inexperienced kid with zero tech background -> Promote him to also manage the developers as part of the product team while getting rid of your tech lead.

- Dev team is essentially seen by management as an assembly line for features. Dev salaries are now well below market average, and they wonder why it's hard to recruit good devs. (Again, this is a tech recruitment company)

While this wasn't technically a real client, it's still one of the most insane requests I've ever had.

I chose to specialize in software engineering for the last year and a half of my degree, which meant a lot of subjects were based around teamwork, proper engineering practises, accessibility, agile methods, basically a lot of stuff to get us ready to work in a proper corporate dev environment. One of our subjects was all about project management, and the semester-long coursework project (that was in lieu of a final exam) was to develop a real project for a real client. And, very very smartly, the professors set up a meeting with the clients so that the clients could tell us what they wanted with sixty-odd students providing enough questions. They basically wanted a management service for their day-center along with an app for the people there. One of the optional requirements was a text chat. Personally not something I'm super interested in doing but whatever, it's a group project, I'll do my part.

The actual development of the project was an absolute nightmare, but that's a story for another day. All I'll say is that seven juniors with zero experience in the framework we chose does not make a balanced dev team.

Anyway, like three months into the four-month project we've got a somewhat functional program, we just need to get the server side part running and are working our asses off (some more than others) when the client comes in and says that 'hey, nice app, nobody else has added the chat yet, but could you do voice recognition okay thanks?'.

Fucking.
Voice.
Recognition.

This was a fucking basic-ass management app with the most complicated task being 'make it look pretty' and 'hook up a DB to an API' and they want us to add voice recognition after sitting on their ass for three months??? The entire team collectively flipped its shit the second they were out of earshot. The client would not take no for an answer, the professor simply told us that they asked for it and it was up to us whether we delivered or not. Someone working on the frontend had the genius idea of 'just get them to use google voice recognition' so we added the how-to in the manual and ticked the requirement box.

What amazes me about all that is how the client probably had no idea that their new last-minute request was even a problem for us, let alone it being in a completely different ballpark in terms of implementing from scratch.

!dev rant about social media 🤡 s like this one.

I hate when people seek for a reason to bitch on social media. This tweet for example.

1) I went to a small high school (small compared to a lot) and we still had a personal management class and this was covered.
2) Who the fuck uses checks still.
3) It's addition and subtraction, not brain surgery.
4) if you actually cared, Google it. There's a shit ton of information on balancing a check book out there.
5) You're probably in debt due to a shitty lifestyle combined with terrible money management, but keep playing victim. It's never your fault.

But of course she doesn't care. It's another case of someone wanting a reason to bitch and moan on social media. Get a hobby you clown.

> raw http request injected in the model
> 400 lines long method, followed by three 300 lines long methods
> no autocomplete, no comments
> code called by the whole application, I mess up once there's at least 150 other components that might break
> no documentation, no tests
> pyramid of doom, 13 levels of indentation

Those are the same people getting all puffed up because the cat dared to sit on my shoulder during a call. Management focused on the real fucking problems, no doubt.

I just had a chat with the CEO (I'll call him John) of the company I work at. I was trying to get a real alignment on what I need to do to be a valuable resource to this company. They promoted me (without a raise in pay) to a different (management) role, and I do not know what I need to do to be the best in this role.

During the discussion, the CEO failed to provide any usable metrics, or a way to track those, except for phrases like "higher productivity" and "higher quality". How to track? No idea.

So, at this point, me being the idiot I am, wanted to make things explicit:
*Me: Okay, so what if I request for a 20% raise six months from now, what metrics will you look at to decide whether to give me the raise.

(My last raise was a big one, more than 100% or so, more than a year ago. That was a dev role, and I was paid 2 cents earlier, so the doubling to 4 cents wasn't really a big deal.)

John went on a long rant on how people just expect raises every year, inflation, etc. All good and fine.
But then he mentioned something strange.

*John: ...and you know, for the last three years, there has been a race to retain resources. During this race, many companies, including us, had to pay people WAY MORE THAN THEIR VALUE to retain them. These people are going to be the first to be fired during cost-cutting as they are the most expensive resources at the company without any proven value. These people should not expect raises to come soon, and if they do expect that, they need to prove the value themselves.

Now, I, being a simpleton, am wondering how is it fair for an organization to pay someone "more than their value" to retain them once so that they can just be fired two years later. How did the company decide the value of such employees to begin with?

And all this is ignoring the fact that in the company there are no metrics, no KPIs, and performance of a person is how much the CEO likes that guy. How TF the people who joined a year ago and never interacted with the CEO prove their worth?

Developers are building PowerPoints and configuring JIRA/Confluence/Laptops of Sales team, project managers are delegating management to developers and decision-making to the CEO, Technical architect is building requirements documents, Business Analyst is the same person as the QA team lead (and badly stretched), and the Release Manager is the Product Technical Admin that cannot write one sentence in English. And then we got 3.8 hours in meetings every DAY. Why TF are Dev Managers in "QA KPI Meeting"? Why are "developers" writing documentation on "How to create meeting notes at <company>"?
And, in this hell-storm, how does one really demonstrate one's value?

I finished my software development apprenticeship and aced the presentation about the software I built for the company.

I'm so happy that I no longer have to go to that workplace anymore.

Most people were toxic, rude, incompetent, slow, entitled, insulting, screaming and fake.
Most were uncommunicative.
Management was shit.
CEO was shit.
HR was nice.
But the rest of the devs were ok, kind and helpful.

Now I'm taking a big vacation to calm down from the years of torture before I can start working as a dev again.

That includes motorcycle driving, chilling with my gf and trying out NixOs (wanna see if it is really worth the hype)

I have previously mentioned my weird co-worker. He likes to come up behind people and shoulder surf, asking "whatcha up to, buddy?".

He also thinks he's a manager, which explains a lot I guess. I half expect him to walk around with an " Initech" mug saying "Yeah....if you could just have those TPS reports done by lunch, that would be greaaat".

YOU ARE NOT MANAGEMENT. YOU DO NOT KNOW WHAT I SPECIALIZE IN. GO FIX A PRINTER, GAH DAMMIT.

...and he mumbles.

I'm not perfect though, so I'm sure I have weird quirks about me.

“Like herding cats.” I’ve heard this out of the mouths of PMs and other management types. No shit that’s what it’s like because cats aren’t herd animals. It’s what happens when you put some of the smartest people in your company at the bottom of a hierarchy, and then have some doofus manage us that reads inspirational leadership blogposts all day.

We will undermine the shit out of your shit, and you won’t even know it’s happening.

We will make every single reprimand of yours into a joke while you’re not in the building. “Hey Joe, I’m pretty sure what you’re doing right now is spreading negativity. Don’t you know it’s contagious?”

We will game every single metric you try to use on us. We will game every single one of your leadership agendas.

When I think of these things, I laugh in my heart like Skeletor.

Mother fucking cunts should be shot into the sun...

It's worse enough when you have to deal with many things at once...

But how the fuck can 3 people from 3 different teams have the same bullshit idea to disturb a meeting and just start talking like it's the most normal thing.

YEAH. INTERRUPTING MEETING AND JUST BLABBERING ON AND ON...

Then fucking laughing how funny it is.

Upper management found it absolutely not funny.

Working from home prevented a mass murder today.

I honestly don’t know how my coworker has been a software engineer for 10+ years, doesn’t know and or understand a single Linux command, only works from windows... also doesn’t understand the concept of proper version control ... thinks zip folders is completely sufficient... AND doesn’t understand why someone would need to refactor something... says it works... I’m like you have a 2000 line function... yes it works, but it’s not testable nor reusable... he says he’s tested it (at his desk) ... and so what if it’s not reuseable... he’ll copy and paste and rewrite something for another project. “That’s what we are paid todo” .... HORSESHIT!!!

I don’t understand how the system hasn’t weeded people out like this.... and he blindly doesn’t want to take criticism, or learn.. saying his Years of experience proves he knows what he’s doing... bullshit

I’m just happy management is on my side.

At $work, I just learned that a daemon on prod makes an SFTP connection to the same domain every 0.5 to 10 seconds, all day long, every single day. That’s a minimum of 8,640 connections per day!

The senior developer responsible for it had the dev skills of a junior and the management skills of a puppet, but she’s a “disadvantaged minority” and is great at stealing credit and throwing people under the bus. Naturally, she has been given multiple promotions and a team to lead… which she fills exclusively with other Indians, all of them at her skill level or below. (I used to do their code reviews and security reviews.)

When I asked one of the fintech managers (a former dev) about the crazy number of SFTP connections, he said “[Her team] did that intentionally, as it didn’t used to be that way. They must have had a reason” and cut me off.

Okay then.
Not my garden, not my fertilizer.
Just another day weeding the fields in hell.

So now that Covid is apparently "gone", management wants us to come to the office to participate in daily team building events to hype up people to commute full time...
but still gotta finish those milestone deliveries while having too many meetings and deadlines.

Murphy is watching us from above with a shit-eating grin.

So, CS student here.
Gave TCS "national" level test.
Quoting from the question:
"if you have 3 bytes of memory, it can be used to represent 2^3=8 values in the memory"

This test is a waste of at least 30000+ human hours and these guys didn't even put 24 hours of effort to make sure questions are correct.
Fuck this fucking IT industry.
Fuck the people who designed this testing process.
Fuck the people who endorsed this process.
Fuck the management for passing it as a test.
The people who wrote the test question can go die in hell.
It's not my problem that their mothers fucked Neanderthals.

Uh! All I want is a job but ended up wasting 200+ hours of time.

I have arrived at a conclusion that most, if not all, people in management (managers, sr managers, directors, VPs, etc) are assholes.

And every single person who is hands on with their skill is gold of a human being.

I think, to be a manager, the basic criteria is to be an asshole. Fuckers ignore you, discourage you, belittle you in front of everyone, never help you, and make your life difficult as much as they can.

That totally ruins the productivity and moral of a person.

Welcome to Capitalism, Floyd.

And person who is hands on, knows and has fuck ton of more knowledge and wisdom needed to achieve something. They are very helpful and nice.

Just bagging a heavy pay check and making crappy decisions doesn't make you a good boss.

>work on multi million dollar company
>last year "we were doing fine" until we got told "well, turns out we didn't, no bonus this year"
>people leave
>You'll get a bonus next year for sure
>Company cuts expenses such as training budgets and freezes raises and promotions
>People still leave
>There are whole teams that are now left with 1-3 people, lol
>Turns out we will not get any bonuses this year either, except for "the high achievers", but they have not announced it yet
>high achievers include the evp of engineering who single handedly destroyed the company's DevOps department last year and an EM/engineer who is completely incompetent as both an engineer as well as a manager, so much so that the company has made him his own 1-person-department so that he doesn't have to work with other people
>Upper management keeps telling us everything is going fine and they suck each other's d**k

This is like watching a trainwreck in slow motion lmao.
I'll stay till they announce this year's bonuses to watch the shit show and then I'll leave

We've worked 5 months to decompose a complex and huge monolith into microservices, deployed in prod with zero defects. And finally moving to AWS, one by one.
How can i explain this work to bunch of 5 year olds? i.e. i've to present this to top level management with no tech knowledge.

I'm thinking of: Lets say a family of 6 people want to travel for 30 holidays to another country. A monolith can be equivalent to having everyone's luggage in huge bag, microservices can be packing luggage in sizable chunks acceptable by airlines.

I'm bad at explaining, can someone help with better example?

Senior management just had a covid opening up party, streamed it on YouTube in the middle of the office with not a single person wearing a mask or social distancing. Encouraging employees to come back to working in the offices.

I AM FUCKING DONE. IM DONE.

It hasn't been a week since one of our employees died and these were the same people who emailed the team asking to donate towards the bereaved family.

This isn't even a rant. It baffles me that narcissistic bullshit like this is legal. How can anyone be that fucking stupid? Just how. Explain this shit to me. Because these aren't total assholes. They're generally nice people outside of work. Why is it that anything touched by corporate greed gets corrupted to the point of inhumanity.

Nope.

I assigned a new task to an intern who has been with us for a month. He was supposed to prepare the testing environment and test the Geolocation API. When it works, then he can start integrating it with our platform and everything.

After a week, he emails me to say that he thinks the Geolocation API doesn't work. I was weirded out by that because a lot of people use it. We scheduled a meeting and asked him for a demo of his code to see what the error message is.

Him: *no Visual Studio, no code, nothing at all* So here it goes.

Me: ????

Him: *Goes to the API documentation, copies the base URL, pastes it to the browser and hits Enter* See? It says 404 not found.

Me: *literally facepalmed*

Now, he is working on sales management. We totally took him off every software developing projects.

Not quite a rant... more of a question.

So, I'm almost 40 years old. I have a lot of work experience in varying fields, much of it in low-level management.

Truth is I've ALWAYS wanted to be a programmer.

I recently got into a somewhat competitive training program
where I'm learning to write Java, and will subsequently learn Android development. It's fairly in-depth, so it will take 10 moths to complete. My ultimate goal it's to work as a mobile dev at a great company, making products people love. Ambitious, I know.

My question is: Am I a fool for attempting to get into this field at this age? I'm starting to panic a little. I'm not sure if I'm wasting my time, or if 40 is too old to be the "newbie".

Thoughts?

1. Manage my time better.
2. Find motivation to wake up and go to work.
3. Fake more smiles.
4. Kick ass hole (L)users in the throat when they piss me off...
5. Attend anger management.
6. Stop making shit lists.

In all honestly I need to dedicate more time to my personal clients and stop allowing my primary job’s frustration to drain my motivation to take care of their needs. It’s not fair to them that I chose the life I have. Find myself and attempt to love myself again. Create more time to focus on my health and goals. Surround myself with people that have goals and want to better their life. Find someone to share life with.

Then, with my luck; throw it all away and repeat these steps like a broken record.

If I ever start my own company, I'll build it on the basis of people not giving a single fuck about what others might think about them, especially management.

There will be no place for butthurt special snowflakes and predictable egoFucks! (credit to @MrJDev for that one)

Personally I am starting to think that any development tools, resources and sites should not be allowed to use marketing dribble.

It should go
-> Land on home page
-> Hi, we are a realtime database cloud host
-> no you cannot host it yourself
-> here is code to speak to our servers
-> here is the cost
->now take it or go.

Something like that, and not

We provide clients with the leading cloud and hosted data solutions that can scale vertically and horizontally on and offline data management keeping people connected and saving kittens.

Fuck you show me one kitten you saved? Lying pieces of shit that do not want to just say hey this is what we have , this is ours, it may not be much but it is what we believe in and if you would like to use it here is how , thank you now move the fuck along our server can't handle so many concurrent connections.

Getting serious about CISSP as I try getting into security and management.

Any tips for studying this? Anything to keep in mind when I get into leadership and need to not piss off the people smarter than I am?

Recently purchased a few edge AI devices at work, and management sent some people to box up and get rid of our dedicated GPUs, since we "just got new AI computers." Now futilely trying to explain to management that not all computers are exactly the same...

When I realized my job isn't to code, it is to hack for hacks.

As smart developers our job is to be accountable to non-technical product management types who care nothing for elegant system design or DRY code. They expect features get done fast and "technically complete." They use terms like "minimum viable product (MVP)" to imply we'll go back and improve things like refactoring and tech debt later.

They will not. Most likely they won't even be around. Producers and scrumlords have the highest turnover rate of any role on a team. By design they get bored or frustrated easily and are constantly looking for greener pastures. Many people in self-proclaimed "non-technical" roles like this never had the patience and attention span to learn a real vocation, and they've discovered a career path that doesn't require one.

These are our masters. As developers, we will answer to them forever and always.

Things I wish people had said at my first job (in light of lots of the people I see starting their first dev gig on here). Please add yours.

Congrats!
Take a breath, you will be fine.
If you get frustrated, take a moment to collect your thoughts.
Don't be afraid to say you don't know, you are not expected to know everything.
Your workday needs to end at a decent time. Don't overdo it or you will be useless for more of your hours.
Always take whatever length of time you think something will take and double it. If you think it will take 15 minutes, it'll probably take your 4 hours.
Concentrate on networking and personal relationships.
Pick the smartest people who have moved the most vertically and pay attention to what they say, they might know a lot.
When management makes an "unwise" or "crazy" decision, ask them why or what the context or motive is that made then arrive at that course of action. Some of them might surprise you in their bigger picture motives or dumbassedness.
Six sigma may be in your future, learn what it is.
Automate as much of your own job as possible.

Um, that's all I've got for now. Hopefully that's helpful to people just starting out. Feel free to add yours.

We use jira at my company. It's great for me, because no ticketing system's UI is worth a shit, but jira's API is excellent. But we're switching to a new system that is an absolute piece of garbage. Every page is 100% Javascript, so no source can ever be viewed, and the URL never changes to reflect what's onscreen. If you know a ticket number, no URL will ever get you straight to it. You have to navigate multiple slow-loading 25MB piles of Javascript to reach what you're seeking. And most damning of all: the new system has an API, but our highest management is withholding access to it, claiming it breeds laziness.

Is amazing the kind of shit you have to swallow when your management has regular meetings with really really super extremely good-looking sales people.

Never buy crappy, consumer-grade SSDs for use in production servers/RAIDs. This might sound obvious but at the company I used to work for, through a series of bad decisions by management and cheapness, we ended up with the cheapest consumer SSDs you can imagine powering all of our storage.

This turned into a nightmare spanning years of failed hard drives and a continues cycle of ridiculousness. Drive failed after a few days, gets taken out, sent back to manufacturer and then replaced with another equally crappy drive destined to fail within days/weeks.

Our ops people were going to the data center multiple times per week to replace failed drives. Lesson I learned: cheaping out on system-critical hardware and software can have long standing consequences and in the end usually doesn't end up actually saving money when you account for time employees have to spend dealing with issues that result from it.

I really hate the childish corporate culture at some tech companies. Today I received my Christmas "gift" from my employer. It was a branded chocolate bar and a sticker pack. The stickers were designed by our UX designers, and the stickers look like they are made for little toddlers at kindergarten. The stickers said things like "Make Friends!" and "To The Moon!". Jesus Christ, are we little kids? The average age of an employee at my company is around 30 years old, and those are the stickers you give us? Stickers are childish anyways, but it seems like 50% of my autistic colleagues seem to like putting those ugly things on their laptops to lick the boots of upper management.

The office itself literally looks like a kindergarten. There's LEGO artwork on the walls and the "Make Friends!" and "To The Moon!" nonsense and similar motivational bullshit is plastered on all the walls. Seriously, who ever thought it's a good idea to tell 30 year old adults to "make friends!". I already have my friends, I don't need to be friends with anyone at work, and I definitely don't need to be told to do so!

Even funnier than that is the fact that the whole "To The Moon!" bullshit is a phrase introduced by upper management to symbolize their effort and wish to make our company bigger and stronger by having a bigger market share. Basically it's the rich peeps from upper management telling us to work harder and make them more successful. Today I had a meeting in which they told me they wouldn't increase my salary because they have a tight budget this year because of the economic problems we're currently facing. But that doesn't stop them from childishly motivating us with bullshit like "To The Moon!" so they can become richer themselves, while the little people at the bottom of the pyramid need to work harder without extra pay.

The most annoying part of this is that many employees lick the boots of upper management and go along with all this bullshit. God I hate cringy childish corporate culture so much.

Our company is cheap, cheap as fuck. We have to use some third-party platforms and every year they choose something that is slightly cheaper than the other. (like a few $ per annual), they do not know that we have to refactor our code at the backend because the changes of the platform.

It doesn't end there, they even look for devs from third world countries to work for them remotely instead of hiring permanent staff (I understand it is cheaper because of currency difference and etc), but what about the training period or to let them become comfortable with the existing system, even when he/she is a genius... it takes time to be productive at work.

The worst part is they dont give a shit, they think devs can be replaced easily just like some construction workers carrying stuffs on site (no offence to them), management treating people like shit and doesn't care when they leave.

I recently started working on a 3 months old project, that was outsourced to two Indians genius. One of them left just before I arrived.

I had the chance to discover those guys were not using any version control system, just exchanging a zip file. I don’t even talk about the codebase, never seen such a mess …

Even better the project managers, were not using any IT program to follow the project advancement, but just Excel!!!

After a few days I realised that the remaining dev was not committing anything, the guy was always lying, (so many people died around him + some emergencies)

So, the guy got fired, but don’t worry management found new genius to save the project 🙂

Can someone tell me if outsourcing is really working?

That the most important thing in any project is to first make sure YOU have understood what the customer/management wants and that THEY have understood what you are going to do.

Seen so many projects (other people's and my own) go down the drain because people had false expectations.

Also, good management is enormously important for any medium-sized endeavour. I cannot count how often I have seen mediocre to bad middle management screw things up, and devs pull off overnighters and 60+hours work weeks for this super-important project that then goes to the bin because "it turned out to be not so important in the end, sorry."

My 5 cents about refactoring.

People often postpone it, making it harder down the line.

From my experience, it's better to just do it as you go. 5 min can otherwise become 30 min thing after a while, and combined with some other 5 min thing, this can become 2 hour thing after some time, for example.

Also good luck convincing management (especially bad one), that you need 2 weeks of refactoring. Doing tiny 5 min refactoring, no one will notice.

Project managers who distribute a task instruction like "add button on page x" into 20 ticket comments (each minimum 1000 chars), 1 pdf from the client, 2 unrelated tl;dr confluence pages, 3 lengthy bullshit management emails (at least 5 people in cc) and end up sending chat messages every hour...

The emphasis on "team" to the exclusion of the individual (thanks in no small part to Scrum) is destroying the software developer career. It's a pendulum. There are always team/company goals AND personal goals. However, these days, the rhetoric is ALL about the team: everybody on a team has the same title, get rid of people who don't conform to some "collaborative", "open space", "colocated" ideal, etc. OKRs are entirely about giving everybody the exact same goals. I remember sitting down with managers throughout my career to talk about where I want to be in a year. What skills I wanted to explore. There were no guarantees, but the generally accepted idea was that nurturing the employee helped retain the employee. Now, there is only the idea that every developer should have the same "T-shaped" skillset, that all team members are the same, that all teams are interchangeable, that all developers are nameless cogs. It is demoralizing. If I were to give any advice to those looking to enter the industry as a developer right now, it would be "Don't". Because you will be told that being a "hero" is a bad thing. In what other industry does management tell its producers that they don't want people to go "above and beyond", and that if they do, they won't get credit for it because the credit always belongs to everybody.

Management has been promising we'd leave .NET framework for 2 years now. Never fucking happens. A new ASP.NET project was just started last week and yup, OF COURSE, its .NET Framework 4.8.

I'd even be happy with one of the earlier .NET Core versions at this point for fucks sake. I have no clue why tech leads are so happy to create a brand new project on a deprecated framework version.

And yes, I have checked thoroughly. Our whole infrastructure works with .NET Core onward. People are just too lazy to learn new stuff.

Stuff like switching to .NET 6, actually doing unit testing, improving our CI/CD pipeline, refactoring problematic codebases, etc. -> all this stuff is the kind of things they promise me I can work on later whenever I'm so bogged down with work that I'm looking for a light at the end of the tunnel. All empty promises.

Ideally we should be on .NET 6 since its LTS and just stay on the LTS versions as the year goes on.

dev, ~boring

This is either a shower thought or a sober weed thought, not really sure which, but I've given some serious consideration to "team composition" and "working condition" as a facet of employment, particularly in regard to how they translate into hiring decisions and team composition.

I've put together a number of teams over the years, and in almost every case I've had to abide by an assemblage of pre-defined contexts that dictated the terms of the team working arrangement:

1. a team structure dictated to me
2. a working temporality scheme dictated to me
3. a geographic region in which I was allowed to hire
4. a headcount, position tuple I was required to abide by

I've come to regard these structures as weaknesses. It's a bit like the project management triangle in which you choose 1-2 from a list of inadequate options. Sometimes this is grounded in business reality, but more often than not it's because the people surrounding the decisions thrive on risk mitigation frameworks that become trickle down failure as they impose themselves on all aspects of the business regardless of compatibility.

At the moment, I'm in another startup that I have significantly more control over and again have found my partners discussing the imposition of structure and framework around how, where, why, who and what work people do before contact with any action. My mind is screaming at me to pull the cord, as much as I hate the expression. This stems from a single thought:

"Hierarchy and structure should arise from an understanding of a problem domain"

As engineers we develop processes based on logic; it's our job, it's what we do. Logic operates on data derived from from experiments, so in the absence of the real we perform thought experiments that attempt to reveal some fundamental fact we can use to make a determination.

In this instance we can ask ourselves the question, "what works?" The question can have a number contexts: people, effort required, time, pay, need, skills, regulation, schedule. These things in isolation all have a relative importance ( a weight ), and they can relatively expose limits of mutual exclusivity (pay > budget, skills < need, schedule < (people * time/effort)). The pre-imposed frameworks in that light are just generic attempts to abstract away those concerns based on pre-existing knowledge. There's a chance they're fine, and just generally misunderstood or misapplied; there's also a chance they're insufficient in the face of change.

Fictional entities like the "A Team," comprise a group of humans whose skills are mutually compatible, and achieve synergy by random chance. Since real life doesn't work on movie/comic book logic, it's easy to dismiss the seed of possibility there, that an organic structure can naturally evolve to function beyond its basic parts due to a natural compatibility that wasn't necessarily statistically quantifiable (par-entropic).

I'm definitely not proposing that, nor do I subscribe to the 10x ninja founders are ideal theory. Moreso, this line of reasoning leads me to the thought that team composition can be grown organically based on an acceptance of a few observed truths about shipping products:

1. demand is constant
2. skills can either be bought or developed
3. the requirement for skills grows linearly
4. hierarchy limits the potential for flexibility
5. a team's technically proficiency over time should lead to a non-linear relationship relationship between headcount and growth

Given that, I can devise a heuristic, organic framework for growing a team:

- Don't impose reporting structure before it has value (you don't have to flatten a hierarchy that doesn't exist)
- crush silos before they arise
- Identify needed skills based on objectives
- base salary projections on need, not available capital
- Hire to fill skills gap, be open to training since you have to pay for it either way
- Timelines should always account for skills gap and training efforts
- Assume churn will happen based on team dynamics
- Where someone is doesn't matter so long as it's legal. Time zones are only a problem if you make them one.
- Understand that the needs of a team are relative to a given project, so cookie cutter team composition and project management won't work in software
- Accept that failure is always a risk
- operate with the assumption that teams that are skilled, empowered and motivated are more likely to succeed.
- Culture fit is a per team thing, if the team hates each other they won't work well no matter how much time and money you throw at it

Last thing isn't derived from the train of thought, just things I feel are true:

- Training and headcount is an investment that grows linearly over time, but can have exponential value. Retain people, not services.
- "you build it, you run it" will result in happier customers, faster pivoting. Don't adopt an application maintenance strategy

/rant

Join a company 18 months into lockdown
Get frustrated at the lack of internal discussion
Raise issue with management
Get ignored
Go to Christmas party
Talk to people that have been dealing with this all through lockdown
Suggest steps to improve
Get bombarded with comments from people that are way more frustrated than me, have been dealing with this way longer
???
Profit

Was an aspiring 2nd grade student then, still a newbie in databases and stuff.

Managed to work with bossy motherfucker who didn't give a flying fuck about proper management, team culture, job roles and everything and treated people like shit.

The big boss wanted me to develop the ecommerce website that integrates with 1c (complete and utterly garbage buggy ass dbms with RUSSIAN SYNTAX, nuff said) and with its own crm to track every employee and even real time chat. He also wanted it to be a kind of online medical wikipedia. And he wanted me to take a professional photo of each and every fucking item for this website, somewhere around 5 thousand photos.

He offered me around 800 bucks for all that job. No, not monthly. He wanted me to do all that shit alone, for 800 bucks and expected it to be up and running in less than two months.

Gently told him to fuck off. Quit that job the same day.

Why are you expected to have people management skills as your experience grows? I don't want to deal with people, I just want to deal with my code 😢😫

The whole company [cult]ure bullshit has really gotten out of hand. When management sets new deadlines that only put stress on the devs then decide to have some cringe AF company bonding soirée in the middle of the work day who benefits from this? The rebranded HR platoon thinks all employees want to participate in basically mandatory chum-it-up gatherings. Don’t get me wrong I love to party and enjoy myself, but I go to work to do just that. Work. And when other departments whose main responsibility is setting up events for the technical staff, they never seem to consider these work loads or what other people actually want. It might seem all fun and dandy on the surface but when you hear tales of people talking in the closed offices about so-and-so because they aren’t reflecting the cultural values, it starts to seem very fucking problematic. Like why would anyone ever say anything when you would probably just get the boot for just being too different, even though all this sits on top of some guise of, “a diverse work environment”. All in all I hope this [cult]ure shit summers down sooner than later. And I’m in a right to work state, so transparency be damned.

I really dislike the company I work at.

I want to say hate, but there are parts that I adore (mostly the people I get to work with).

However, I dislike:
- The management
- The way engineers are treated
- Lack of responsibility for on QA for finding bugs, and it falling solely onto the engineers
- Sales circle jerk every All Hands meeting
- The amount of "ring-around-the-rosy" they played with me for a 10k raise (took 12+ months and not what I was looking for when I first asked)
- They lie

Just a shitty company overall. Interesting product depending on what team you're on, but overall I'd rather dye my hair green and become a talking broccoli stock.

I'll give you a few reasons to walk away from a dev's chair:

1. if you want your life to be simple and not challenging, if you just want to go with the flow - choose something else. Dev's life will definitely bring some challenges to your day (and sometimes night, and sometimes - your weekends). Especially if you feel you are a perfectionist, dev life could turn your life into a living hell if not handled with care.

2. If you like to see people smiling, if you love that feeling when you help someone and that someone has a better day thanks to you - choose something else. 1st line SD would probably do, but the further from technology you go - the more smiles (and human faces overall) you'll see.

3. If you prefer person-to-person interaction over to talking to machines - definitely don't be a dev. Go to management, administration or smth else, but development. >90% of the human interaction in this field is arguments and conflicts; ~8% are requests for assistance, and the remaining 2% are shared by saying "hi" to the office administrator and your (semi|)annual reviews with your manager. Not kidding.

4. If you have a personality where you find it difficult to stand your ground and not budge to the pressure/blame game/your managers asking you to stay in late. Like it or not, it happens quite often. Many devs have spoiled the management by budging to their requests/demands to stay for OT/unpaid OT to "fix the mess they have made". That's a blame game right there. And these people stay in and do what the slaves do - work for free because they are yelled at. And then management sees this technique work and (ab|)uses it on other devs. If you can say NO and stick to it, prolly wave with some printed paragraphs of labour law in front that manager's nose - it won't be a problem. But if your consciousness is too troubling - stay away from this field of engineering.

5. If you want to easily "disconnect" from work and go do something else - dev's career might be a problem. Yes, your computer might be shut down/hibernated/suspended after 5pm until 9m the next morning, but your brain will most likely keep trying to solve the problems you were facing. You'll prolly use your own computer to do some research, check some forums, docs, etc. - this is all your free time, this is all your family time donated to your manager (and to your personal knowledge base). Not to mention, all these things you learn will soon enough become obsolete, as new technologies will replace them. So if you'd like to easily "disconnect" after 5pm, doing that as a dev might be too challenging.

I decided I should finally relocate from Russia. As one of the people I value much once said, it’s not about grass being greener, it’s about grass being alive.

I’m not going to buy a property here. Instead, I do this all at the same time:

- fixing my health (eye surgery done, quit smoking half a year ago, quit sugar several months ago, now through dental care and an obesity treatment with newest novo-nordisk stuff and sports, so far so good)

- gaining some momentum (newsletter launched, articles and open source stuff are published on a regular basis, it all gonna assembly to make my new website and a v2.0 media presence)

- learning (hands-on management and a11y experience on my current job as a tech evangelist, also a11y courses, bleeding edge JavaScript and css)

- saving money. Fuck rouble, just converting everything into usd covers up all commissions and taxes and basically makes me money

I’m going to accomplish all this and finally relocate.

Being attached to my city is a bias and a mind game. I just need to leave.

Network, talk to people, and get yourself on the spot, document everything and make sure that you take action when others do not.

Kissing ass can take you far, but I ain't about that life, because sooner or later the fucker that promoted you because he liked his pp getting suckd by you will leave or get put in the spot. Or change alleagiances.

Your best bet is to be ANYTHING OTHER THAN A FUCKING NECKBEARD WITH AUTISM and be someone that people likes being around, I know it sounds hardcore, but people around you will ignore the things you don't know if you are a charismatic guy. Dress well, work out or find ways to improve yourself in ways that are noticeable, use human psychology to be fucking likeable.

Work hard, both on yourself and on your craft, study, get better, be social.

Stop being a twat because high chances are that the higher executives of your branch will not give a shit about your knowledge, but how good is to have you around. Join the circle, fuck your opinions about anything else, this is business, and business doesn't care about a lot of things. Don't cut throats, but make yourself a force to be reckoned with.

Source: Upper management, deals with VPs on a daily basis, knows that being a neckbeard will not take you anywhere.

Meetings. I don't know how management people get anything done, but the time I spend in meetings counts completely opposite, in terms of productivity.

Naaaaaaaaaaaaaaaarfffffffddddd

Motherfucking shitty depression kicks me around like a fucking wet teabag.

Shit doesn't get done

Motherfuckers are annoying me

And this constant whining....

Why can't we have new hardware....

Because it's fucking 'rona and you had a motherfucking frigging shitty ticket to clean the shit up so we don't need frigging fucking new hardware that takes ages to delivered

Now I have to give a seminar thx to some special guys showing up stoned on work law....

... Getting chewed out by management and tons of laughter was exactly the extra care package I needed… thx for the nice reminder that you are all shitbags.

I love my job and the team mates close me.

But the rest of the people seemingly nuked their brain and are really grinding their teeth down my emotional barriers.

Why is everyone seemingly obsessed with stupidity since Corona began...

<deep breath>

2 more days.

Remember, just 2 more days.

Weekend is near...

My boss does this management by neglect thing - he is hardly in the office and mostly communicates in slack. Today it got really vague and ambiguous.

So - when 4 people don't understand your slack message - the obvious conclusion is that you hired 4 morons...

!rant

More like a genersl question I guess. But how do you guys react to writing software that might make someone else get laid off? At work I developed an application that manages a lot of the inventories and yard management that had to be done by hand. While I was developing it, the manager that was giving me the details mentioned (jokingly) many times that if the software works as it was expected that they will not require certain people anymore. I shrugged it off as a joke since I could not imagine it being serious. Turns out, it was serious and some talks about company restructuring have taken place since I released the app into our servers. How the fuck am I supposed to feel? If someone loses their job because of something like this, how would someone go about NOT feeling guilty af?

I honestly maintain a positive opinion that almost (again read almost) all devs are not inherently evil. Those who are made do those autoplay vids were probably asked by management, the game devs at EA are forced to use Frostbite which isn’t suitable for everything, like RPGs, and Apple devs aren’t trying to maximise profits by limiting so much to the consumer world (e.g the bloody XCode license), but are forced in by this corporate model.

A lot of shit is given to devs and sometimes I think it’s undeserved. In their shoes most people would too go against their moral compass if it meant that they won’t lose their jobs. I’m sure when battlefront was in the works it wasn’t the devs that came up with that whole shitstorm model.

Why do I have to "grow" into a managerial role? I like doing what I am doing and would like to do it more. Anyone with some serious advice on how to stay relevant in software development with greying hair and without growing into people management?

Yesterday all management was sick or away on vacation or training.
All work continued as normal. Everyone is an adult and knows what to do.
Made me question if we actually need to have soooo many people in management positions.
Funny to think that they get paid more.
Ironically when a developer is sick, real money is lost and progress stops in a particular area.
🤔

I applied as a full-stack dev at a private company, they offered me the Project Manager role instead, I took the offer and after 1yr they gave me a choice to choose between staying as a Project Manager or switching to being a Software Engineer/System Analyst. I took the SoftEng position because project management isn’t my career choice for now.

Now people saying I not knowingly chose to be demoted. Is it a bad choice?

I fucking hate corporate environment. We have a weekly meeting in our tech department where a team is chosen at random to present the project they're working on, architecture and such. You know what? We have fucking documents, for both product scope and technical architecture. If you're interested in our work, go fucking read our docs. If you have a question, slack us or send us a fucking email. Why the fuck do I have to attend a 1-hour meeting every week for this bullshit. Oh and some dude from upper management has a brilliant idea: from today they decide to host 2 such meetings per week, 1 within the tech department, and another within the whole company. So we had to attend the same fucking meeting twice in 1 week!!! Fucking genius!
I'm so fucking tired of these meaningless meetings, but attendance is recommended because "this is how you reach staff level" as they told me. Fucking bullshit. I may try a few more years for the sake of financial stability, and then find a small shop where people just leave me the fuck alone with my codes.

In my previous company we developed a CRM web app for the company to use internally and it was in my humble opinion really easy to make sense of, but for some freaking we kept getting calls whenever someone got an error, and our default response was always to send us an email, then we will get back to you, as it was mostly stupid things they called about, for example, a customer might have to be status terminated, before you can click button A, button A would then be disabled and employees would call asking why. Apparently, people got annoyed by our response and went to the management, to get some guidelines as to when they could call the "development apartment" for help, so the management sends out some guidelines as to when they could call, write or whatever... The following was done without consulting us in any way ANY WAY AT ALL!... Because we all know management knows fucking best, and why bother asking the people that sit with it every day, and the way it was done was by saying:

If the background color on your error is red, it means the error is fatal and you can call the developers immediately, if its orange send an email and they will answer within 48 hours LIKE WTF... Seriously???. That was basically it, and honestly we had just been using colors, without much thought to it ofc red, was an error etc. But they we're not "OMG EVERYTHING IS BREAKING" alert, so we decided to use a couple of hours refactoring the color of the flash errors, and after that, we did not have many red alerts(None, yes none what so ever) We changed all the red ones to orange, and introduced some new colors. That worked for some time around 6 months or so, but then people obviously started calling again like, why even bother... So we created a simple service desk, blocked all incoming calls to our phones that were from regular employees, heard a lot of complaints about this from the employees, management was mad, we had so many meetings with those top paid management fuckers that know everything (way better than you and me), about how to handle this. As it took way too much of our time, that people couldn't bother trying simple things, or make some sense as to why a button is disabled etc. We ended up "winning", was allowed to block calls for some time, till the employees had learned to use a freaking simple service desk, it's not fucking rocket science Okay, stop being a pain in the ass... And it actually fucking worked! Most relaxing time after people got a hang of using the service desk instead of calling life was good after that... <3

We had today a meeting in management that ended in a discussion about prevention instead of crisis and risk management.

Or to make it bit simpler: prevention instead of treatment.

In IT / management / government, treatment is usually the way - you let the crisis happen, despite knowing it could have been prevented, and treat the damage / crisis.

Needless to say, the discussion escalated like usual.

It's funny how managers are able to put sentences like: "it's important to have quality assurance like prevention but staying within budget should be priority" (loosely translated from German, it's hard - sorry)...

You mean the budget that exploded and quadrupled in size because you dumb fuckers pay no attention to quality assurance? Or the additional cost of hardware, maintenance etc. to compensate for the fuckups regarding performance evaluation and regression testing?

"We cannot prevent everything nor anticipate everything, it's safer to deal with an estimated risk than with the unknown"...

"But we'd need to invest in ..., which reduces value"

I could give more details, but I think the point is clear... the discussion became quite heated and the longer it went on, the more I wanted to have an morphine drop with suicide option...

Why do people hate prevention so much?

Is the concept that hard to understand? You prevent things to not deal with crisis.

You invest to prevent loss.

It's just one of these weeks where the only happiness consists of tipping the delivery guy with 20 % plus and getting an honest smile.

:(

Why on Earth are people letting management tell them how to code? It is not their job to know how to do it. Much less to tell you how to do it.

Why the fuck are there people in power (management positions) who are a bunch of scumbags and have literally 0 amount of trust left in their bodies? What the fuck is up with that??? If y'all have freakin issues with your subordinates, and don't trust them that they can do their work, FUCKING 👏 TALK 👏 TO 👏 THEM 👏 STAYING IN YOUR PETTY PITY PITHOLE WONT FUCKING DO ANYTHING. YOU HAVE ALREADY ACCEPTED THEM IN YOUR COMPANY AND THERE IS AN ALREADY EXISTING TALENT/RESOURCE WAITING TO BE USED BUT YOURE NOT DOING ANYTHING TO SOLVE THE PROBLEM THEN IDK? IF YALL COULD JUST TALK TO THEM THAT WILL BE GREAT.

I used to think I was the kind of programmer that was good with people. That somehow I was special because I could get on with colleagues and make clients happy.

But fuck people. It’s so easy to be nice, just don’t be not nice. Don’t say rude things and be surprised when I’ve had enough.

For some reason my latest colleagues think it’s too confrontational to talk to each other and instead give management anonymous feedback on who they don’t get on with. Which obviously gets fed back to everyone immediately.

I’m done putting on a smile. Elegant code speaks for itself. I’m getting a PA to talk to people from now on because fuck this.

Remote work (for the software industry, at least) is PERFECT and I still haven't heard a single argument against it that could not be derived into one of the following explanations:
- the complainer is/has a terrible manager
- the complainer has a shitty house
- the complainer has a shitty family
- the complainer is a shitty person
Naturally I mean only real-adult healthy people who work in the software industry.

I will now list the complaints I have heard more often. All fit neatly in the categories above:
- "my family interrupts me a lot, require lots of attention and/or creates an environment I cannot work in" - in this case it is very irresponsible of the complainer to try and escape to an office. If the adults you live with cannot get by without you, how going to an office will help them? If you can't teach your children to behave, who will?

- "my house is noisy and/or uncomfortable" - move out! if you can go to the office, you can look for another place to live.

- "I need in person conversations to understand people / zoom meetings are a waste of time" - why? do you need the smell of other people to properly organize your thoughts? Yes, meetings are extra-shitty during the pandemic. But pandemics come and go and your terrible time management skills won't simply improve themselves. Learn to lead better meetings instead of blaming the medium.

- "I miss face-to-face interactions at work" - Those do not miss you. If you want to have personal conversations, do it *out of working hours* with consenting adults. If you want to have personal touch in work contexts, it is called "sexual harassment" and is a crime.

- "my employees / colleagues are not as effective without me breathing at their necks" - you are a terrible manager and leader if you can't inspire people in words only. Maybe even video.

My main point is, there is no argument against WFH. When people try to argue against it, they often actually mean "I don't like the pandemic". No shit. Life will be better after people stop dieing for breathing close to their friends and family. In the mean time, learn to organize your life instead of running away from it every day.

Have you ever been to love theatre? How many times? Have you ever seen a movie? How many?
Why so many more movies than live theatre? You think you would have liked the movies, and their price, more if it was live theatre? Would you have seen as many?
WFH is not perfect for everybody in the planet. But it sure is for the software industry.

I see a lot of rants on this platform complaining about their boss/management.

About how they don't understand how complicated the development can be of seemingly simple tasks or how they would prefer small estimations over realistic ones.

Is that really the standard in this field of work?
Am I just that lucky to find basically the ideal boss on my first try?

My boss really understands how difficult some tasks can be even if they don't initially seem like it. He listens to my ideas as if they are at least just as important as his own. He can almost think like a real developer and is prepared to give us all tools we could want to evolve.

It is a very small firm and I'm basically the only real developer on this project, but I would follow that man to the ends of the earth.

Can some people please clear my conscience and confirm there are still good managers in this field who really care about their project and their employees/colleagues?

Can someone explain to me why non-technical people even work in tech companies ??

I really don't want to sound like an asshole, but can you, for example, imagine that someone who doesn't even know what brick is would work on a construction site ?

Or can you imagine working in bike repair shop not knowing neither how to ride a bike nor how's bike is built ?

Sure, every company (especially large ones) needs bookkeepers/HRs/accountants etc. that don't need to know the inner workings of business.

Those people don't bother me, and they are necessary to keep the circus going.

I'm talking about all those middle management individuals.

All those "Project Managers" , "Business Analysts", "Directors' , "Principal Program Managers " etc etc ..

Such thing thing would be unthinkable in every other industry but somehow, in tech, anyone can work as long as they can throw a sufficient number of acronyms around.

Answering several emails per day from annoying customers.

Estimating expenditures of possible future projects for offers.

Calls from the management. Calls in general.

People coming into my room in the office (where I sit with 2 other programmers) just to have a call, because it's quieter in this room than in the rest of the office.

People who dont know shit about technology and dont know how much work is required to make a product are commenting on how software should be made. (Pure management background people not even senior level).
- PS. Im fine with management people with tech background.

The job wasn't bad. I started as an intern in a startup. The company did have its problems but the people were nice and I liked the job. But holy shit, I was insecure. I was constantly worrying if I was doing okay or not and even though nobody ever said anything even slightly negative. Since it was a startup, projects did fail and I usually felt guilty and blamed them on myself. Failures that I now understand did not have anything to do with me or my coding abilities and were mostly because of other issues (management, marketing, finances, etc). But all in all, I liked it and I improved a lot. Both technically and non-technically.

Previous department director. I loved working with the dude.

He had a no bullshit attitude and would always back up and defend his people, he would tell us that whenever he sticks his neck out for us we better be in the right because he would go full ballistic and did not wanted to make a fool of himself or the department. Dude was fucking amazing.

He was happy when I accepted the promotion but told me that he wanted me to shadow him to learn more about proper management techniques. It was a clear mentor trainee relationship, but he had 100% full trust in my ability and knowledge.

He retired about a year ago, got a new director, dude ain't thaaaat bad but he has a lot of cons, as a person I like the new boss, as a boss I am not convinced entirely since he has not been around for long, but it does feel that he does not listen, goes in one ear and out through the other kind of person.

Aaron, seriously. Stop wading into our team uninvited, coming in with your "superior experience", mouthing off about how we need to be doing everything differently because our current code makes no sense, making a few PRs that break everything, then complaining we're just incompetent and don't understand when everyone rejects them.

If there's one thing that hacks me off the most, it's people like this wading in uninvited, pretending they're being really helpful in coaching us in the "one true way" to do development, screwing everything up, then buggering off again while boasting to upper management that "thank goodness I got there when I did, or that team would be royally screwed."

People of devRant. I am in need of some advice.

So I joined this new firm around an year ago and ever since my team lead resigned, we have been managing it ourselves. Then a senior member suggested me that I could be a good fit as a team lead role. Now there are members in my team that are more experienced than I am but they either don't want to lead or are not good at it. I never had a formal leadership role before although I have driven projects. Higher management is open overlook my lack of experience but has also said that I may not find lot of technical growth as I am moving to a more administrative role. Any piece of advice on what I should do? I would love to have a leadership role but would it really affect my technical learning?

Story Time!

Tittle: About Larry.

Fun Game: Tell me if / when in this story you know the plot twist.

Setting: Years ago, non coding job.

I work with Larry a lot, Larry works remote. In technical terms Larry is senior to me and I escalate some technical issues that get assigned to Larry. I've never met Larry in person.

Larry can be hard to work with, but he's plenty good at his job and I don't mind his prickly side. Sometimes it takes telling Larry something a few times before it sinks it, but that's not a big deal. Sometimes it seems like Larry doesn't remember his cases entirely, but he has a lot of cases. Also Larry has good reason for how he works considering the land of scubs who usually escalate to him without any thought / effort.

Larry's escalation team is short staffed and they're trying to hire folks, but that's been like that forever.

So one day I get an email that Larry is going to be out of the office for a few weeks. Nothing unusual there.

My current case that I share with Larry sort of floats in limbo for a while. The customer is kinda slow to respond anyhow and there's nothing that I need Larry for.

Finally I get automated notice that my case has had a new escalation engineer. Laura. Laura is much more positive and happy compared to Larry. Understandably Laura isn't up to date on the case so we go back and forth with some emails and notes in the case.

The case is moving along just fine, we're making progress, but it's slow because of the customer's testing procedures. Then we hit a point where this customer's management pushes on sales for a solution (this customer's management is known for doing this rando like for no reason).

Down the management chain it goes and everyone wants a big conference call to get everyone up to date / discuss next steps (no big deal).

Now I really don't want to do this with Laura and throw her into the deep end with this customer, she doesn't have the background and I'd rather do this call with Larry & Me & Laura. Also according to the original email Larry is due back soon.

I start writing an email to Laura about "Let's try to schedule this for when Larry gets back."

Then I stop ... I don't really know why I stop but when it is a "political case" I want some buy in on next steps from management so I go talk to my manager.

-Plot Twist Incoming-

Long story short, my manager says:

"Laura IS Larry..."

O

M

G

I had no idea. Nobody told me, nobody told ANYBODY, (except a couple managers).

Back up a few months Larry apparently went to his managers and told them he was going to transition, surgery and all, in a few months.

Managers wondering how to address this went to HR and some new hire very young to be a manager HR manager drone logiced out in her bonkers head that "Well it shouldn't matter so don't tell anyone."

ARE YOU FUCKING KIDDING ME!!??

Thank god I didn't send that email...

I did send an email to Laura explaining that I had no idea and hoped I didn't say anything stupid. She was very nice about it and said it was all good.

After that incident made the management rounds (management was already fuming about being told not to tell anyone) things came to another critical point.

Laura was going to visit the company HQ. Laura had been there before, as Larry, everyone knew her as Larry... nobody (outside some managers) knew Laura was Larry either. With nobody knowing shit Laura was going to walk in and meet everyone ...

One manager at HQ finally rebelled and held a meeting to tell his people. He didn't want Laura walking in and someone confused, thinking it was a joke or something horrible happening.

HR found out and went ballistic. They were on a rampage about this other manager, they wanted to interview me about how I found out. I told HR to schedule their meeting through my manager (I knew they didn't want my manager to know they were sniffing around).

Finally the VP in our department called up the HR head and asked WTF was going on / kind of idiots they had over there (word has it legal and the CEO were on the call too).

HR had a change in leadership and then a couple weeks later there were department wide meetings on how to handle such situations and etc.

So sick of my pessimistic, paranoid supervisor. She's always accusing everyone of being spies and has opinions on everyone.... Complains abt management and everything under the sun.... But when management comes in the room... Quiet as a mouse, because in her words ,'I don't wanna fix anything'

THEN WHY THE FUCK ARE U COMPLAINING!?!?

U clearly see nothing wrong and that's why u don't wanna change it

Fucking hate people who endlessly complain

So new job started.
Just for context- old company was shit.
Promised the world but.
No benefits.
Terrible project management.
High pressure.
But green field interesting work (except by now it’s a few years in so it’s a ‘browning’ field but I was on it from the start).

New company first impressions..
Seems a fantastic company.
True to their word they have money for tools.
Making time for personal development.
Much bigger development community/department.
Seems like the term are under far less pressure so far at least.

But a MASSIVE amount of tech debt.
People seem to want to do the right thing and they’re making time to try and deal with it.
But one or two are very opinionated as to how to deal with it.

So this could go either way and only time will tell I guess.
Trying not to over analyse every little thing they say but I’m hyper sensitive to it at the minute while in the early days.

As always the real challenge in IT is the people not the tech. I count myself as part of the problem, sure I will form some opinions and sharing them too.

It may be shocking to you if you are involved in management but actually pressuring people to meet arbitrary deadlines is not an effective way to improve productivity

A PM who suck-up to a creative technologist. He comes up with ideas while me, the programmer, have to figure how to get it done.

PM expects me to explain how things can or cannot be done. I spent whole day drawing diagrams explaining things, while the creative technologist makes demand after demand.

For me, the worst project manager is one who doesn't take care of their people.

N The worst creative technologist, is one who won't go do their own fucking research and expect the developers to do it.

Both fuckers are management roles. Go figure..

I started getting more into the product management side of the business lately, which involved being invited to what feels like 80 meetings per week.

My schedule today consisted of 5:30 of meetings, three of which were a single API design kickoff…

I’m starting to get why people are so damn mad at meetings all the time. Should’ve been a fucking email chain

I would like to stop and genuinely thank the devs and anyone that contributed to NW.js for allowing users to work outside the sandbox. Fucking sandboxes these days make developing editors and tooling a bunch of bullshit hassle. I understand why, but it makes an entire class of software that much more difficult to develop.

And on a semirelated note, I decided to go with nw.js because unlike electron, I don't have to tell users "just install these two gigabytes of npm dependencies *from off the net after already downloading the main application*, dependencies that could break at any time at all for any reason."

Does anyone even bundle their dependencies any more or is this something only clinically insane people like myself do?

Because last I checked most users still don't know how to debug console autobarf when a single command goes awry due to something obscure like a version conflict between two brittle cogs in the organ grinder known as package management.

Edit: also, nw.js startup times and memory requirements are relatively sane compared to electron.

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.

I've always wanted to post a rant here whenever I get pissed about something at work mostly because of the management and the people I work with. It rarely happenes but if I encounter one, I start to post something and end up changing my mind about not posting it because I'm afraid I am not the only devranter on our team or even other teams that I work with and they might figure out that it was me ranting because of the details I include in the rant. So I try to calm down instead and try to find a way to handle the situation.

Damn I'm never getting my free stress ball here

Many "purists" love to piss on JavaScript and web development. And to an extent I can understand ostream’s frustration with these people.
It’s easy to criticize because yes: many web projects are indeed shit.

But I’d like to argue that the reason why so many of these projects are crappy is because of bad management:
- unrealistic deadlines
- no clear testing strategy
- or no testing at all because of deadlines
- no time allotted to catch up on technical debt
- etc.

This type of management is far more commonplace in web projects because things need to get delivered quickly and if they’re delivered with bugs, it’s no big deal as lives aren’t at stake.

I doubt this type of management is tolerated in projects where you’re working on software for welding machines (for example), where the stakes are that "you’re expected not to kill anyone" (to quote demolishun)

So in these types of projects, management can’t tolerate anything much below perfection and thus has to adapt by setting realistic deadlines that take into account the need for quality processes and thorough testing.

If this type of management was more common in web development, I can guarantee that web applications would be much more reliable and of better quality.
I can also guarantee that poorly managed non-web projects as outlined above would be just shitty as many web products.

My point being that’s it’s really DUMB to criticize fellow devs that work with web technologies on the basis that the state of websites/web apps is a mess. It just so happens that JS is the language of the web and that the web is where things are expected to be delivered quickly (and dirty … but we can fix it later mentality)
Stop acting like you’re the elite. I have no doubt you’re super smart and great at what you do. So be smart all the way and stop criticizing us poor webdevs that have to live with the sad state of affairs. ❤️

Something I wrote in my "how not to run a company" notebook:

Getting told you've now replaced the CTO as the person people ask for support (literally, he was recieving no questions), but you're not experienced enough to be promoted to senior.

I replied by telling them I was interviewing elsewhere.

Made me laugh. Is it really that hard for management to get that they should invest in talent?

Whatever works that you can get people to work with.

I can’t remember the number of times I’ve warned management against using fancy ass tools only to find out that there literally are no devs on the market who work with it outside fancy ass startups.

Reality is real for a reason.

One of the things that I like the most regarding Clojure(and most Lisps to be honest) is how "not for beginners" the ecosystem feels.
Don't get me wrong, setting up a project in lein with dependencies(both internal and external) is a cakewalk, installing lein or boot is a cakewalk. Setting environment consts and middleware etc etc is a cakewalk.
Its just that there are no blogs about convoluted and amateurish ways of doing things. Most presentations and articles are written by really experienced and talented individuals.

I dunno, its just a nice shift in community. Its nice to see people not fucking up Object Oriented programming in java or any of the other oop languages. Its nice not seeing people giving horrible advice regarding memory management in C or c++ and it is sure as shit nice to not see spaghetti php und js code.

And my productivity levels are off the charts man. Really liking this shit and I get to stay inside my JVM

I am 2 months in this job and I already hate it.
I love programming and building stuff and also the business side of things, even some meetings are ok if done efficiently.
This time its the coworkers. Nobody goes with the management decision to migrate the app. People intentionally deny help or at best dont care. Nothing is going forward.
I am a Junior but I am not just a warm body in the room. Still they really try to make me feel like I have to kiss some boots because of it. I really fucking hate this „family“ they call themselves.

How do you do? And how do you deal with a place you hate?

Joined a new startup as a remote dev, feeling a bit micromanaged. So this week I joined an established startup as a senior mobile dev where I work remotely.

Previous two devs got fired and two new guys got hired (me as a senior dev and another senior dev as a teamlead, also third senior dev will join next week).

Situation is that codebase is really crappy (they invested 4 years developing the android app which hasn't even been released yet). It seems that previous devs were piggybacking on old architecture and didn't bother to update anything, looking at their GIT output I could tell that they were working at 20-30% capacity and just accepting each other MR's usually with no comments meaning no actual code reviews. So codebase already is outdated and has lots of technical debt. Anyways, I like the challenges so a crappy codebase is not really a problem.

Problem is that management seems to be shitting bricks now and because they got burned by devs who treated this as a freelance gig (Im talking taking 8-10 weeks pto in a given year, lots of questionable sick leaves and skipping half of the meetings) now after management fired them it seems that they are changing their strategy into micro managament and want to roll this app out into production in the next 3 months or so lol. I started seeing redflags, for example:

1. Saw VP's slack announcement where he is urging devs to push code everyday. I'm a senior dev and I push code only when I'm ready and I have at least a proof of concept that's working. Not a big fan of pushing draft work daily that is in in progress and have to deal with nitpicky comments on stuff that is not ready yet. This was never a problem in 4-5 other jobs I worked in over the years.

2. Senior dev who's assigned as the teamlead on my team has been working for 1 month and I can already see that he hates the codebase, doesn't plan on coding too much himself and seems like he plans on just sitting in meetings and micromanaging me and other dev who will join soon. For example everyday he is asking me on how I am doing and I have to report this to him + in a separate daily meeting with him and product. Feels weird.

3. Same senior dev/teamlead had a child born yesterday. While his wife was in hospital the guy rushed home to join all work meetings and to work on the project. Even today he seems to be working. That screams to me like a major redflag, how will he be able to balance his teamlead position and his family life? Why management didn't tell him to just take a few days off? He told me himself he is a senior dev who helped other devs out, but never was in an actual lead position. I'm starting to doubt if he will be able to handle this properly and set proper boundaries so that management wouldn't impact mental health.

Right now this is only my 1st week. They didn't even have a proper backend documentation. Not a problem. I installed their iOS app which is released and intercepted the traffic so I know how backend works so I can implement it in android app now.

My point is that I'm not a child who needs hand holding. I already took on 2 tickets and gonna push an MR with fixes. This is my first week guys. In more corporate companies people sit 2 months just reading documentation and are not expected to be useful for first few months. All I want is for management to fuckoff and let me do my thing. I already join daily standup, respond to my teamlead daily and I ping people if I need something. I take on responsibility and I deliver.

How to handle this situation? I think maybe I came off as too humble in the interview or something, but basically I feel like I'm being treated like a junior or something. I think I need to deliver a few times and establish some firm boundaries here.

In all workplaces where I worked I was trusted and given freedom. I feel like if they continue treating me like a junior/mid workhorse who needs to be micromanaged I will just start interviewing for other places soon.

Is it highly likely that, those at high position of management are more greedy of money and posses less ethics and values, than those who actually build the company ie engineers ?

I had seen, it's always the top management who get away from mistakes/ issues but generally it's those who develop the company at core i.e. engineers again, are sidelined or considered responsible for the mistake, when management don't know a shit about anything, or sometimes engineers just follow what management says and management fucks their asses wide even if the management did something wrong.

Who do you think actually build companies/product. Engineers or management or marketers/sales people, who eats fat cheques ??

I remember from silicon valley, when hooli reverse engineered Richards idea and developed their own prototype named Nucleus. Pushed their engineers to beat pipe Piper and when their product turns out to be awfully terrible and extremely fucked like a burned dick with broken balls, they just fired their entire nucleus division

Funny how people freak out when I offer free stuff (in exchange for feedback) as I introduce myself as the CEO.
But when I tell them that I'm a developer, they all accept it without a single doubt.

Since I'm doing both, I can call myself whatever, but this just shows how little trust people have towards management of ANY company. So I can't really blame them.

CEOs, please stop being fucking greedy and do something that can change the life of at least one person in a positive way.

My vision for this startup is to produce as many opportunities for people so that they can feed their family and have a place to call home.

Edit: I've seen this one CEO buy an expensive car on company lease when he received an investment. Guess what his employee told me next. I fucking LOL'd.

Tools are made for various audiences. Git is the de-facto standard for version management, so it can be complicated because people will still learn it (they more or less have to). Editors aren't as standard and they are to be used from the minute you start learning, so they have to at least be usable without a course or a handbook. I prefer the first type of tool because to use something really good I don't mind reading a book. Programming languages can fall in either category; Python was meant to be used by laics and is therefore very simple, sacrificing a lot for the sake of simplicity. Rust isn't meant to be used by anyone who isn't trained, and it comes with a great book that explains all the most important gotchas. Haskell doesn't have an official book AFAIK, but it has the best wiki I've ever seen in a programming language.

Why is so hard to find engineers that actually care? It feels like the majority of people always want to do the bear minimum, no one wants to fix their shitty code even when it clearly violates the project or company standards. Everyone constantly comes up with shit about why they can't do things properly or how they'll fix it later and then get their mates to push their shit through review. The majority of lower management usually care equally as little so there's no point explaining the situation to them and the lack of care probably goes much higher. It seems like so many people go from job to job getting bump after bump in salary, which granted is absolutely fine and probably advised, but have nothing to show for it. Usually very little skills but alleged mountains of experience and a lazy piece of shit attitude. I hear all the time people saying you'll never change anything so why try and it feels like that most of the time but more because everyone keeps saying it. If everyone pulled their fingers out their arse, maybe we would stand a chance. I'm sure a lot of people on here have a real passion for computer science, whichever division you're in and love to learn and improve and reflect. What I really want to know is how you deal with people who are just taking their paycheck and enjoying the ride but don't actually care and how you discover these people as early on as possible to get shot of them.

Is it possible to have a midlife crisis at 27?
The "software biz" swallowed me up and except for money and a career I don't have anything.

Turned down multiple management positions because I dont wanna deal with other people, I just wanna be challenged while being let alone

I know I said this before but once again I'm thinking about buying a small house with lots of land.. get some cows, maybe chickens, work remotely and make my own life on my little property.

I work in a company, where prototypes become instantly a product... People are far from being an expert in the technologies we use (technologies which were chosen by management without any further research).

Timeframes are more than short, so there is no chance to learn what you need to know to be able to create something really maintainable and stable.

Guess what - that shit is going to be installed at the customer site, where neither we nor them know what to fucking do if something breaks ...

great

Micro-management people. Still working on that though.

35y/o and a child (well, 2 soon), experienced as an integration dev (not my dream job tho), scripted a lot as a devops engineer (bash, py).

My heart says "jump deeper into devops and/or py", but my imposter syndrome infested brain says it might be too late and that after 10 years in IT it's time to navigate more into management/architect role (mostly because I've seen a lot of people around me follow this path).

Thoughts?

No no no. That's it. Less than 2 years experience supposed to be leading a team of 12 soon to be 17 most of which have more experience than me! Been given sever admin responsibilities, training and managing 2 large frame works in addition to everything else I was doing before.

With the current set of projects we were given half the amount of time to do over twice the amount of work. Management seems to expect constant over time. And I keep being nagged by management to finish x,y,z. Every thing is high piority and I keep being asked to switch between tasks every hour or so nothing gets completed when this happens every time I make them aware this happens. The worse thing is that the CEO has a way of naming and shaming people who fall behind work infront of the entire company.

I have only been surviving thanks to a few saints in the team who just get on with the work without argument but now found out a bunch of these are moving to better companies!!!

I like helping people but with everything that is going on I can't find time to and I know at times I end up coming across inpatient with them that they don't deserve. But if you are part of a team please try and solve your issue yourself before asking others every half an hour there are too many of you and I need to get things done too.

And why is it so damn hot sitting at the desk sweating.

Ok I am prob on my meriod and being over the top grumpy. I want to find a new job but so tired in the evenings that I just want to collapse on my bed and do nothing. At end of writing this and feel a little better.

Rant!!!

Fuck!!!

Clowns!!!

And it is only Monday!!!!

Involved in a pretty large it project. Several years endevour. Global. Tens and tens of millions of dollar budget.

It is obvious for all that this waterfall approach will cause enormous pain. Pain and suffering.

Multiple consultant firms involved. Loads of management, leads and the likes. Several with no it background.

🙄

Yes. No real concept of a database or what not. I mean. It is an actual IT project.

Several leads. One of the managers have no idea what he is doing. None. One would guess he should have his shit together regarding NON-it stuff. But no. And they work with this full-time and can’t even setup a descent way of working in a sub-sub-sub-project.

Clowns.

One would imagine in a waterfall setup that things is…formal. But no. It’s just people doing their thing. Lots of words. Lots of words.

I think there are nice problems to solve at the end. When it is delivered and done. So I will plan to stay and learn as much as possible. But I have to do the clowns work. Which sucks so much I can’t believe. But there are so many people involved so I guess I can get away with it in one piece without too much effort.

I am not even going to write a single line of code. 😬

All is fine.

Fucking Monday.

Hm, missed a bit this pile of sociopaths here on devRant.

Last few weeks:

I repeat myself, this shouldn't be hard.

Working on it for 5 mins.

O h m y g o d.

Quite nothing the past weeks worked like intended, people and management have been a complete desaster and the weather is killing me.

Cheers.

Oh. And my request to get an benzo perfursor and a sexy manly nurse was denied by my team colleague handling hardware management.

-.- He said me being in a good mood is the last missing sign that the apocalypse is happening.

Yeah. Shit is burning everywhere. We're e.g. getting hardware delivered by a supplier who said that the request *was* canceled (after 3 months...) Two days phoning back and forth, they don't understand how it was possible but we can keep the hardware. Yay. Except that we completely redid the whole planning a week before. Naaaayy....

And now I will do the best I can: get drunk.

Cheers.

I started reading “The Phoenix Project” by Gene Kim. And in the first chapter itself two people from the IT department get fired, and the author is forced to takeover the CIO position. Damn, now I’m shook. Is Tech really that much under appreciated and management that much hostile ?

I was brought into my new position as part of an transformation of waterfall to agile methodology.

We are now running 4 while projects and need to restart the remaining 29 projects using agile principles. The business management type people love agile, but somehow the people inside the current waterfall practices doesn't.

They are afraid their silo work will either expand or not exist thus making it hard to transform the company. Also the company have been subjected to the dead sea effect.

Therfore, the project that is currently in the space of transformation is making my blood boil because people just ain't passionate enough about software.

Either you craft software, or, well you sit and suckle other's money. People suckling should please grow up and start venturing beyond there cozy 9 to 5 and transform to be a professional software doer rather than a BA, DEV, IT GUY.

YOU BASTARDS GET A SHITLOAD OF MONEY AND DON'T DESERVE IT FOR THE EFFORT YOU BRING.

It is your software, own it, be proud of it. Read up to make it better. And as always, the people debugging your code can be a violent psychopath

Don't love the environment where an idiot developer, who has perfected his people skills and Visio skills constantly impresses the management with good looking charts, albeit unintelligible, and the management adopts his stupid ideas every time.

Scrum is like low-management, similar to low-code.

With low-code, we say our programmers are not very good. So the less they program, the better. With low-management, we say that our managers are not capable of managing people, so the less they manage, the better.

This is more of a story than a rant, but it has some rant-ey elements, so whetever...

I work for a pretty big company. Several departments, teams, many different markets...so it's a big orchestration. The programming department (aprox. 5% of all employees) is the core of the whole company, because everybody else uses software we've written...(a bit off topic, the point is there are a lot of people)

So today, I got assigned with a side-project. The project spec arrives, and as I read through it, I start realizing that upper-management whats me to build an app to fire people instead for them. The app is supposed to track salary, connect with Trello (for departments that use it) to track finished tasks, track sick days, work attendence...a lot of stuff, and at the end, if the situation requires, spit out a person that is of least benefit to the company, to be fired...

Now from coding perspective, this will be very interesting and fun to build, but from a moral standpoint, I'm a bit woried...simply because, indirectly, I'm firing those people. Because, the way I tune the the app(specifically the algorithm that weighs the value of an employee to the company) will cause certain people to get fired...

So I'm woried I'm gonna have a small breakdown when the app goes live and I see someone saying goodbye to theie colegues of something similar...heck, the app might even spit out my name some day(I should probably add a tiny if statement somewhere in there :) )
What do you guys think about this, from a moral standpoint? Would you be okay with building something like this?

(Sorry for the long post :/ )

IT people stereotypes:

young gods = „I know that already for ages. Those senior folks are way too pessimistic and too theoretical.
Give me shell.. wait.. Call me h4ck0r g0d now because I use kali linux.“
("no, you did not learn anything")

senior slow-moes = „could you please retry your last sentence? I just opened my wordpad“
("triple-facepalm")

sales-Sebastian = „Sure we can do that. By intention our solution offers only graphQL access because our design goal is minimalism and simplicity“
(no, your solution is piece of sh*t).

Framework-Fred = „let’s stick to togaf. Please use these terms from the glossary of following data management framework. You can reach me via ITIL process xy“

Nearshore-Naan-Ganjid = „I can program in HTML“
("program")

Feel free to extend

Why can't people just do their fucking jobs? How hard is it to understand? Managers keep time, resources and risks in check and inform the developers. Developers develop and test the system. How the fuck do we have manager for agile, manager for program a manager for program b, risk mitigation manager, this shit manager that shit manager . For fucks sake with this much management we should be like fuckin bee nest and not an unorganized mess. In the end it turns out that literally there are more managers than developers just because they cannot fire an incapable idiot and they hire the next one. It is plain fucking simple - if you are not fit for the job get lost or make yourself fit. For fucks sake.

It really makes me wonder are there any well organized companies out there?

code reviewed a "senior" developers code (guy has been at the companyny since noah and his clay computer tablets), he replied with my comments against it stating he has more experience than i have and that i shouldnt do anything except just sign off the stuff to production, stuff goes to production and breaks a massive financial cluster fuck of a mess, who gets the blame for releasing the code to production ? Junior me !!! gotta love it when management needs scapegoats of FIFO people.

Today I talked to a cousin who works in Tata Consultancy Services (TCS) and he told me precisely why companies like Infosys, TCS and Wipro are moving towards ending WFH and mandating working from office.

He told me that post-COVID hires are treating these software jobs so casually, that they don't ask for leaves. They decide, on their own, when they want to take leave(s) without telling their team members.

They don't pick up phone calls when someone from upper management tries to reach out and they magically show up 3-4 days later. They don't value deadlines.

He told me that these companies do see the benefit of letting people work from home, but the new generation hires are creating a joke out of these positions and are taking blatant advantage of the situation. So they are forced to mandate working from office.

Some older woman in my building tried to cyberbully me. She found a back door because the building’s online message board emails everyone in the building and those emails have a link to email the author.

You bet I snitched on her to building management after she continued to email me after I had asked her to stop and told her that her email was offensive. I don’t tolerate people who make assumptions about my ethnicity and use that as a reason to send me demeaning messages.

And you bet I contacted the developers of the building’s message board about the backdoor. And of course they implied that I could have prevented this and sent me instructions. No, I could not have prevented this and those instructions they sent me would have never applied to my comment on the message board.

I highly recommend my colleagues to read this book quickly, quickly!

First, realize that trying to accurately estimate how much time something is going to take is akin to accurately predicting the future and that people who ask you to do it are stupid. Then realize that sales-oriented deadlines are the source of all that is evil. Then shift away from sales oriented software. Instead focus on selling existing features and new features on the roadmap have no deadlines, they're done when they're done. Then realize almost no workplace will let you truly do that because chasing the sale is all that matters despite the latest buzz word rhetoric. Then estimate enough buffer to give you a reasonable time to complete it without calling your abilities into question. Then finish it faster so you score points with management, but not every time because then they'll begin to expect it. Now you have leveled up in mind games, an unfortunate but necessary tool in the tool belt. Then hate on sales oriented software some more, rinse and repeat.