"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"

So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.

First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.

So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.

Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?

I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.

Did you run the code I gave you to do this update?

"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"

So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.

More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!

I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.

And this, my friends, is the part I will never forget.

"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."

You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!

"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."

I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.

So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.

You just cannot make this kind of stuff up.

The first time I realized I wasn't as good as I thought I was when I met the smartest dev I've ever known (to this day).

I was hired to manage his team but was just immediately floored by the sheer knowledge and skills this guy displayed.

I started to wonder why they hired outside of the team instead of promoting him when I found that he just didn't mesh well with others.

He was very blunt about everything he says. Especially when it comes to code reviews. Man, he did /not/ mince words. And, of course, everyone took this as him just being an asshole.

But being an expert asshole myself, I could tell he wasn't really trying to be one and he was just quirky. He was really good and I really liked hanging out with him. I learned A LOT of things.

Can you imagine coming into a lead position, with years of experience in the role backing your confidence and then be told that your code is bad and then, systematically, very precisely, and very clearly be told why? That shit is humbling.

But it was the good kind of humbling, you know? I really liked that I had someone who could actually teach me new things.

So we hung out a lot and later on I got to meet his daughter and wife who told me that he had slight autism which is why he talked the way he did. He simply doesn't know how to talk any other way.

I explained it to the rest of the team (after getting permission) and once they understood that they started to take his criticism more seriously. He also started to learn to be less harsh with his words.

We developed some really nice friendships and our team was becoming a little family.

Year and a half later I had to leave the company for personal reasons. But before I did I convinced our boss to get him to replace me. The team was behind him now and he easily handled it like a pro.

That was 5 years ago. I moved out of the city, moved back, and got a job at another company.

Four months ago, he called me up and said he had three reasons for us to meet up.

1. He was making me god father of his new baby boy
2. That they created a new position for him at the company; VP of Engineering
and
3. He wanted to hang out

So we did and turns out he had a 4th reason; He had a nice job offer for me.

I'm telling this story now because I wanted to remind everyone of the lesson that every mainstream anime tells us:

Never underestimate the power of friendship.

During a random school project.

Me: *Explains why team members idea is bad*

Team member: *Im going to do it like this anyways.*

Me: *add explaination of why idea is bad to git commit log.*

1 week later: some parts of the project dont work like they are suppost to.

Team member: *dude can you help me bla bla....(encounters issue i mentioned regarding his idea)*

Me: *no, i've already got too much on my plate. please, sort it out yourself....*

At the presentation

Teacher: *ask question about problem*

Team member: *tries to blame the problem on me....*

Me: *shows git commit log to teacher*

Me: *passing grade*

Team member: *failing grade*

Justice served.

I've learned that trying to jump into a project without properly understanding everything it will entail is bad.

I recently worked on a project that involved modernizing a legacy system and no one on the team (including me) fully understood how the legacy system worked. This led to us missing a lot of edge cases and attacking the project in a way that really wasn't beneficial overall.

If we had thought about the entire system beforehand and mapped out the legacy system, the project would've turned out much better.

So I have been temporarily assigned to new team .. moving from mainly backend.. to help the Web team ..

Me .: Aight guys .. what we working with ?
Team: MVC .net
Me: awesome ..
Team: but we have our own version of MVC .
Me : 🤔 your own MVC ?
Team: yeh we only buse controllers.. but no models at all ?
Me.: 😲 So where does the view gets its data from ?
Team : from Azure functions apps.
M: how ?
T: ( in very proud tone ) .. we use js to call all functions.
M: so why not just use HTML pages . Why MVC then !
T: coz MVC is modern architecture design.
M: but you not using it and all of calles to the functions are exposed publicly.
T: 🧐 THIS IS MODERN DESIGN !!
M: 🤪 My bad .. what the hell do I know ! I only been developing MVC applications for 7 years !!
Please tell me more about your " Modern Design "
🤮🤮🤮

My first job: The Mystery of The Powered-Down Server

I paid my way through college by working every-other-semester in the Cooperative-Education Program my school provided. My first job was with a small company (now defunct) which made some of the very first optical-storage robotic storage systems. I honestly forgot what I was "officially" hired for at first, but I quickly moved up into the kernel device-driver team and was quite happy there.

It was primarily a Solaris shop, with a smattering of IBM AIX RS/6000. It was one of these ill-fated RS/6000 machines which (by no fault of its own) plays a major role in this story.

One day, I came to work to find my team-leader in quite a tizzy -- cursing and ranting about our VAR selling us bad equipment; about how IBM just doesn't make good hardware like they did in the good old days; about how back when _he_ was in charge of buying equipment this wouldn't happen, and on and on and on.

Our primary AIX dev server was powered off when he arrived. He booted it up, checked logs and was running self-diagnostics, but absolutely nothing so far indicated why the machine had shut down. We blew a couple of hours trying to figure out what happened, to no avail. Eventually, with other deadlines looming, we just chalked it up be something we'll look into more later.

Several days went by, with the usual day-to-day comings and goings; no surprises.

Then, next week, it happened again.

My team-leader was LIVID. The same server was hard-down again when he came in; no explanation. He opened a ticket with IBM and put in a call to our VAR rep, demanding answers -- how could they sell us bad equipment -- why isn't there any indication of what's failing -- someone must come out here and fix this NOW, and on and on and on.

(As a quick aside, in case it's not clearly coming through between-the-lines, our team leader was always a little bit "over to top" for me. He was the kind of person who "got things done," and as long as you stayed on his good side, you could just watch the fireworks most days - but it became pretty exhausting sometimes).

Back our story -
An IBM CE comes out and does a full on-site hardware diagnostic -- tears the whole server down, runs through everything one part a time. Absolutely. Nothing. Wrong.

I recall, at some point of all this, making the comment "It's almost like someone just pulls the plug on it -- like the power just, poof, goes away."

My team-leader demands the CE replace the power supply, even though it appeared to be operating normally. He does, at our cost, of course.

Another weeks goes by and all is forgotten in the swamp of work we have to do.

Until one day, the next week... Yes, you guessed it... It happens again. The server is down. Heads are exploding (will at least one head we all know by now). With all the screaming going on, the entire office staff should have comped some Advil.

My team-leader demands the facilities team do a full diagnostic on the UPS system and assure we aren't getting drop-outs on the power system. They do the diagnostic. They also review the logs for the power/load distribution to the entire lab and office spaces. Nothing is amiss.

This would also be a good time draw the picture of where this server is -- this particular server is not in the actual server room, it's out in the office area. That's on purpose, since it is connected to a demo robotics cabinet we use for testing and POC work. And customer demos. This will date me, but these were the days when robotic storage was new and VERY exciting to watch...

So, this is basically a couple of big boxes out on the office floor, with power cables running into a special power-drop near the middle of the room. That information might seem superfluous now, but will come into play shortly in our story.

So, we still have no answer to what's causing the server problems, but we all have work to do, so we keep plugging away, hoping for the best.

The team leader is insisting the VAR swap in a new server.

One night, we (the device-driver team) are working late, burning the midnight oil, right there in the office, and we bear witness to something I will never forget.

The cleaning staff came in.

Anxious for a brief distraction from our marathon of debugging, we stopped to watch them set up and start cleaning the office for a bit.

Then, friends, I Am Not Making This Up(tm)... I watched one of the cleaning staff walk right over to that beautiful RS/6000 dev server, dwarfed in shadow beside that huge robotic disc enclosure... and yank the server power cable right out of the dedicated power drop. And plug in their vacuum cleaner. And vacuum the floor.

We each looked at one-another, slowly, in bewilderment... and then went home, after a brief discussion on the way out the door.

You see, our team-leader wasn't with us that night; so before we left, we all agreed to come in late the next day. Very late indeed.

!rant

New job (first CS job).

Day 1: Install Ubuntu
Day 2: Dev said "it was so cute when he asked if he could uninstall windows." Also, first pair programming with engineer of 12 years. First commit (he did all the work, I just tried keeping up."
Day 3: "Here, try this bug " nearly get there. Have to leave early. Team event (Group VR experience, was wicked fun with drinks afterwards. Turns out boss man is a total bad ass. Swam with sharks and giant Wales)
Day 4: Fix bug. Notice odd behaviour. Fix that too. (All on my own). Code review: "This, that but works and is good." Get asked if I want to go to customer to do A, B and C. Tell Boss I only know B. He said "Tell me what you need for A and C."

I'm so God damn happy.

Manager: Good news everyone, I made a big giant announcement this morning that the app upgrades will be released today!

Dev: They definitely won’t be, we need another 2 weeks minimum. I told you yesterday

Manager: Ok well I already made the announcement that today was the day so too bad for you.

Dev: Doesn’t change the state of things

Manager: 😡 This announcement is supposed to motivate you to work faster! You guys are making me look bad when you don’t support me like this!

Dev: Working as fast as we can, it’s a 2 person dev team for 4 separate applications so it’s quite a bit to get pushed through

Manager: Ok well then stay extra then, we have to get this out asap. Tell your spouses they are not going to be seeing much of you until this work is done. People are starting to ask questions!!!!!

Dev: Not my problem, it’s done when its done. I’m not staying extra.

Manager: !!

// *************

Might be blowing my cover a little but what are they going to do? Fire me? Good luck getting this out without me. They’ve tried to replace me in the past but the cheapest person they could find was 60k more expensive than me and still couldn’t keep up. Probably they’ll ship the work overseas and the code will die in a dumpster fire and cost them even more. Ah well, just another company that doesn’t deserve code.

One week, and it turned out to be worse than that.

I was put on a project for a COVID-19 program in America (The CARES Act). The financial team came to us on Monday morning and said they need to give away a couple thousand dollars.

No big deal. All they wanted was a single form that people could submit with some critical info. Didn't need a login/ registration flow or anything. You could have basically used Google Forms for this project.

The project landed in my lap just before lunch on Monday morning. I was a junior in a team with a senior and another junior on standby. It was going to go live the next Monday.

The scope of the project made it seem like the one week deadline wasn't too awful. We just had to send some high priority emails to get some prod servers and app keys and we were fine.

Now is the time where I pause the rant to express to you just how fine we were decidedly **not**: we were not fine.

Tuesday rolls around and what a bad Tuesday it was. It was the first of many requirement changes. There was going to need to be a review process. Instead of the team just reading submissions from the site, they needed accept and reject buttons. They needed a way to deny people for specific reasons. Meaning the employee dashboard just got a little more complicated.

Wednesday came around and yeah, we need a registration and login flow. Yikes.

Thursday came and the couple-thousand dollars turned into a tens of millions. The amount of users we expected just blew up.

Friday, and they needed a way for users to edit their submissions and re-submit if they were rejected. And we needed to send out emails for the status of their applications.

Every day, a new meeting. Every meeting, new requirements that were devastating given our timeframe.

We put in overtime. Came in on the weekend. And by Monday, we had a form that users could submit and a registration/ login flow. No reviewer dashboard. We figured we could take in user input on time and then finish the dashboard later.

Well, financial team has some qualms. They wanted a more complicated review process. They wanted roles; managers assign to assistants. Assistants review assigned items.

The deadline that we worked so hard on whizzed by without so much as a thought, much less the funeral it deserved.

Then, they wanted multiple people to review an application before it was final. Then, they needed different landing pages for a few more departments to be able to review different steps of the applications.

Ended up going live on Friday, close to a month after that faithful Monday which disrupted everything else I was working on, effective immediately.

I don't know why, but we always go live on a Friday for some reason. It must be some sort of conspiracy to force overtime out of our managers. I'm baffled.

But I worked support after the launch.

And there's a funny story about support too: we were asked to create a "submit an issue" form. Me and the other junior worked on it on a wednesday three weeks into the project. Finished it. And the next day it was scrapped and moved to another service we already had running. Poor management like that plagued the project and worked in tandem with the dynamic and ridiculous requirements to make this project hell.

Back to support.

Phone calls give me bad anxiety. But Friday, just before lunch, I was put on the support team. Sure, we have a department that makes calls and deal with users. But they can't be trained on this program: it didn't exist just a month ago, and three days ago it worked differently (the slippery requirements never stopped).

So all of Friday and then all of Saturday and all of Monday (...) I had extended panic attacks calling hundreds of people. And the team that was calling people was only two people. We had over 400 tickets in the first two days.

And fuck me, stupid me, for doing a good job. Because I was put on the call team for **another** COVID project afterwards. I knew nothing about this project. I have hated my job recently. But I'm a junior. What am I gonna say, no?

*deep breath*

Remain calm, don’t freak out, remain calm, don’t freak out.

*deep breath*

Ok, so my sort of new manager (had a slightly different manger-ish role on the team), has for the third time in as many months, just sent an email criticizing the dev team for our working from home-ness (which for the record has not been that bad, 2/3 or 3/3 have been in everyday for the past month)

In this same period, there has been late nights, weekends, successful releases, I’ve been invited to talk at a conference about my work (not a particularly big one, but still). Point is, everything is going well, very well in fact.

There has been no emails discussing our great work, thanking us for extra work, thanking us for picking up slack from other teams who are down a few people etc. no our major concern it seems is the “optics” of our team not being present in the open space.

Our contracts list flexible working hours, and his boss has frequently told us WFH is fine when things are too busy. But no he is complaining for us to get our hours in the office in line and make sure we are in the office more.

It’s been a particularly long and frustrating week, and I’m very tempted to inform him that if he is concerned about my chair and desk looking empty, that I can put them somewhere for him where they will always be occupied until a surgeon can remove them.

However, thanks to the deep breaths, I’ve managed to restrain myself long enough to run this past you all first and ask advice.

Please help,
Sincerely,
My sanity

Job offer:

"There is no hierarchy within this company."

Bullshit.

Given a group of people, a hierarchy will emerge. In any company, a hierarchy will emerge. Even within a team a hierarchy will emerge.

Some people like to butt heads, some people like to go with the flow. It's how you deal with these personalities that matters.

You can try to be as fancy you want and declare your hierarchy to be as flat as a pancake, yet the reality is: there will be one.

Certain people will be trusted more by other people. Certain people will have more power in the decision making process.

Can we please stop deluding ourselves that this is not the case?

And that is not necessarily a bad thing. It only becomes bad if the company culture sucks. Instead of platitudes in regards to the assumed absence of hierarchy, I would be more interested to know how a company deals with its hierarchy.

How is feedback handled? How do people argue? How are decisions made, challenged and implemented?

That's what I would find much more interesting.

Worst dev team failure I've experienced?

One of several.

Around 2012, a team of devs were tasked to convert a ASPX service to WCF that had one responsibility, returning product data (description, price, availability, etc...simple stuff)
No complex searching, just pass the ID, you get the response.

I was the original developer of the ASPX service, which API was an XML request and returned an XML response. The 'powers-that-be' decided anything XML was evil and had to be purged from the planet. If this thought bubble popped up over your head "Wait a sec...doesn't WCF transmit everything via SOAP, which is XML?", yes, but in their minds SOAP wasn't XML. That's not the worst WTF of this story.

The team, 3 developers, 2 DBAs, network administrators, several web developers, worked on the conversion for about 9 months using the Waterfall method (3~5 months was mostly in meetings and very basic prototyping) and using a test-first approach (their own flavor of TDD). The 'go live' day was to occur at 3:00AM and mandatory that nearly the entire department be on-sight (including the department VP) and available to help troubleshoot any system issues.

3:00AM - Teams start their deployments
3:05AM - Thousands and thousands of errors from all kinds of sources (web exceptions, database exceptions, server exceptions, etc), site goes down, teams roll everything back.

3:30AM - The primary developer remembered he made a last minute change to a stored procedure parameter that hadn't been pushed to production, which caused a side-affect across several layers of their stack.

4:00AM - The developer found his bug, but the manager decided it would be better if everyone went home and get a fresh look at the problem at 8:00AM (yes, he expected everyone to be back in the office at 8:00AM).

About a month later, the team scheduled another 3:00AM deployment (VP was present again), confident that introducing mocking into their testing pipeline would fix any database related errors.

3:00AM - Team starts their deployments.
3:30AM - No major errors, things seem to be going well. High fives, cheers..manager tells everyone to head home.
3:35AM - Site crashes, like white page, no response from the servers kind of crash. Resetting IIS on the servers works, but only for around 10 minutes or so.
4:00AM - Team rolls back, manager is clearly pissed at this point, "Nobody is going fucking home until we figure this out!!"
6:00AM - Diagnostics found the WCF client was causing the server to run out of resources, with a mix of clogging up server bandwidth, and a sprinkle of N+1 scaling problem. Manager lets everyone go home, but be back in the office at 8:00AM to develop a plan so this *never* happens again.

About 2 months later, a 'real' development+integration environment (previously, any+all integration tests were on the developer's machine) and the team scheduled a 6:00AM deployment, but at a much, much smaller scale with just the 3 development team members.

Why? Because the manager 'froze' changes to the ASPX service, the web team still needed various enhancements, so they bypassed the service (not using the ASPX service at all) and wrote their own SQL scripts that hit the database directly and utilized AppFabric/Velocity caching to allow the site to scale. There were only a couple client application using the ASPX service that needed to be converted, so deploying at 6:00AM gave everyone a couple of hours before users got into the office. Service deployed, worked like a champ.

A week later the VP schedules a celebration for the successful migration to WCF. Pizza, cake, the works. The 3 team members received awards (and a envelope, which probably equaled some $$$) and the entire team received a custom Benchmade pocket knife to remember this project's success. Myself and several others just stared at each other, not knowing what to say.

Later, my manager pulls several of us into a conference room
Me: "What the hell? This is one of the biggest failures I've been apart of. We got rewarded for thousands and thousands of dollars of wasted time."
<others expressed the same and expletive sediments>
Mgr: "I know..I know...but that's the story we have to stick with. If the company realizes what a fucking mess this is, we could all be fired."
Me: "What?!! All of us?!"
Mgr: "Well, shit rolls downhill. Dept-Mgr-John is ready to fire anyone he felt could make him look bad, which is why I pulled you guys in here. The other sheep out there will go along with anything he says and more than happy to throw you under the bus. Keep your head down until this blows over. Say nothing."

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.

Once we were going to present a web service to governmental firm. All is going well so far and my boss asks me to host the web application the day before the presentation.

I hosted it and all was good with demo production tests, but I had a bad feeling.

While it was running on our server, I also ran it locally with a reverse proxy just in case.

* Meeting starts *

* Ice broken and down to business *

"And now our developer will run the demo for you..."

* Run the demo from my laptop to double check --> 500 Internal Server Error *

Holy shit!!!

* Opens reverse proxy link on my laptop. Present demo during meeting. Demo works like a charm. *

Firm representative: "Great! Looking forward to go live."

*Our team walks out*

GM: "Good job guys"

ME:

Can I only pick one?

I don't hate a lack of skill by itself. Incompetence, in my book, refers to a lack of skill combined with being in a position of responsibility.

The junior/intern in my team writes pretty bad code, but that is OK. He asks questions, I give pointers and bounce back his PRs ten times in a row, and he keeps fixing things without complaints.

My boss however... still writes PHP as if he's living in the 90s. He doesn't visit scrum meetings because he "isn't a developer". He thinks of a new feature while pooping, writes it without telling anyone, and throws it into production without making a PR.

---- Startup RantLife ----

A senior developer joined the team, let's name him Bob, and this guy is really good no doubts about that.
He made suggestions, some improvements, but Bob is always waving his hands and says out loud that some part of the code base is really really bad.
I kept quiet until one day I had to pair with Bob to check a feature. Guess what happened, as usual, Bob clenched his fist and start pointing that this code is super ugly.
So let's check the history of changes and boom, Bob was the main writer.
That moment, I was completely silent, trying not to smile as Bob came up with an excuse, he never admits that he is wrong, now he needs a scapegoat and he starts blaming the process, the planning...
I believe that being humble and saying sorry is a quality that it requires time to develop.
So don't be like Bob, please :)

My team handles infrastructure deployment and automation in the cloud for our company, so we don't exactly develop applications ourselves, but we're responsible for building deployment pipelines, provisioning cloud resources, automating their deployments, etc.

I've ranted about this before, but it fits the weekly rant so I'll do it again.

Someone deployed an autoscaling application into our production AWS account, but they set the maximum instance count to 300. The account limit was less than that. So, of course, their application gets stuck and starts scaling out infinitely. Two hundred new servers spun up in an hour before hitting the limit and then throwing errors all over the place. They send me a ticket and I login to AWS to investigate. Not only have they broken their own application, but they've also made it impossible to deploy anything else into prod. Every other autoscaling group is now unable to scale out at all. We had to submit an emergency limit increase request to AWS, spent thousands of dollars on those stupidly-large instances, and yelled at the dev team responsible. Two weeks later, THEY INCREASED THE MAX COUNT TO 500 AND IT HAPPENED AGAIN!

And the whole thing happened because a database filled up the hard drive, so it would spin up a new server, whose hard drive would be full already and thus spin up a new server, and so on into infinity.

Thats probably the only WTF moment that resulted in me actually saying "WTF?!" out loud to the person responsible, but I've had others. One dev team had their code logging to a location they couldn't access, so we got daily requests for two weeks to download and email log files to them. Another dev team refused to believe their server was crashing due to their bad code even after we showed them the logs that demonstrated their application had a massive memory leak. Another team arbitrarily decided that they were going to deploy their code at 4 AM on a Saturday and they wanted a member of my team to be available in case something went wrong. We aren't 24/7 support. We aren't even weekend support. Or any support, technically. Another team told us we had one day to do three weeks' worth of work to deploy their application because they had set a hard deadline and then didn't tell us about it until the day before. We gave them a flat "No" for that request.

I could probably keep going, but you get the gist of it.

Man, we have a snake in our company.

This snake is responsible for terrible code. They oversee a offshore team, but hold them to no coding practices. They don't do code reviews or checks. They let them be lazy and get away with sloppy work every time.

And if you critize their team - they will defend them and get angry at you. You can't adress the problem because said snake is always around. He's in a senior position for giving our company cheap workers, doing years of damage to our product while the non-code savvy managers remain blissfully unaware of their product being ruined in the background.

This snake is the senior product office. He has a share in the company now. He is from the overshore team's country. That team now has their claws so dug into our companies roots and are just pumping lsd's into it constantly. Feels good untill you die from an overdose.

Here I am, the new junior software developer, trying to tear out the claws that have sunk into these roots. Im up against the snake. The snake hates me. I hate the snake. I am trying to open the eyes of the managers. They hate that. They want to silence me so I don't expose the awful, unprofessional level of work they do.

Well, that's too bad. I won't back down from this, snake.

It's disheartening to see a senior member of my team shitting on the code of less mature developers. Don't just say "this is unacceptable", elaborate, teach them. How are they going to action anything from that feedback?

Take the time to respond to their questions when they ask for clarification on what you're saying. Don't berate them.

Honestly some developers need to learn a thing or two about code etiquette.

There's no room for good cop / bad cop behaviour.

Manager: "Good Morning"

Employee: "Okay"

Manager: "You are fired. I deserve a proper reply"

Employee: "I have put my entire focus on solving the problem the team members have been skipping for months. Anyways I will go"

Manager: "My bad, I will fire the other employee"

So there is this girl who joined the company as a trainee.

The company developed a 1 year project to train 25 trainees and she joined saying that she already had some experience making websites. (remember this)

They started in the beginning of January and stayed for about 3 months just studying the platform (Salesforce) and receiving some classes from Senior Devs, on subjects like OOP basics, loops, conditions and features of the platform.

After this time they joined the teams, 2 joined my team, a guy with 32 years that worked 10 years in a bank and wanted to go for a IT job and the girl of 22.

We gave her a really small task, just to make a code to copy info from one field to the other on a list of objects.

After 3 days of saying she was working on it we asked her to show us the code, she had written the "code" directly in the class, VS Code was going crazy with errors. When we asked her "But where is the method?", she answered "What is a method?"

After it we had other experiences trying to teach her some things. The team was formed by me (mid level dev), another mid level dev, a senior and a architect (who was self taught and one of the best teachers I've ever seen).

We tried for about 3 months to teach her how to do basic stuff, like a for loop, and every time we learned that she was missing some "foundations" of this basic stuff, so we would come back and explain the foundation, and a couple times she needed to use this knowledge like a week later and didn't remember shit.

So after this the team talked with our leader that we wanted to let her go and focus on the other guy who was going really well and some other junior devs who had joined the team.

But the HR found out that she had sued her last company, we don't know the reason, but HR guys were afraid of firing her without a careful firing process.

So now we're stuck with her in the team, and everything we ask her to do need to be remade, not because the code is bad, but because it NEVER works

And after all this I still ask myself, how did she finish college? Every person that i know that studied CS or CS like courses had a lot of OOP or at least knew what a class and a method were supposed to be.

One of my previous managers would constantly make promises our team couldn't keep. "You want it in a week? Sure, we can finish it in a week! You want it tomorrow? Sure, we can do that!"

It got so bad that our team basically had to stage an intervention. At one of our standups, we flat-out told him that even if the entire team dropped all of our other tasks to focus on the one big project, we still would not be able to meet the deadline he'd promised the client.

And that fucker actually said, "Well, if you want to come in on the weekend to work some overtime, I don't mind." as if he was offering to do us a favor by "allowing" us to work more.

No overtime pay because we had salaries.

So glad I don't work for him any more. Of course, my next manager wasn't great either, it just took longer for us to figure it out because she wasn't nearly as blatant about it.

So I'm a entry level female Developer and I started a contract to hire position in July. Its my first job as a developer and I love almost everything about it. Except this..., there is a Senior Female Developer on my team who hates me and isn't shy about it. She goes for the throat man! She magnifies any mistake I make, hell she calls me out on things that people would consider positive. In sprint planning this week she got mad at me for pulling tasks from the backlog after finishing mine early. I've tried to do everything I could to make her like me. I patiently listen when she goes on and on about her damn cats, kids, sports, ah everything, and she is a non stop talker.

Her main problem with me, so she tells the head of engineering, is that I bug her too much. I almost laughed when I heard this was her main issue with me! Sure, I asked her the normal amount of newbie questions but it's not like I don't know how to read code or google! In fact I started avoiding talking to her about a month ago because she was so rude to me. Now getting hired on full time comes down to whether or not she can stand me still if I am working on another team. I'm so frustrated because it's impossible to prove my worth to this company with this crazy lady making me look bad. I have no problems with anyone else at work. In fact a lot of us have become good friends. No one understands why she hates me so much. It feels like middle school all over again.

On top of that there is an even newer hire who she is supposed to help bring on to the team, but because of her horrible management skills, I have become his defecto mentor for learning the project, as well as the technologies we use. The stress of being in an uncertain contract to hire position + tyrant coworker + helping the new guy + still learning and having my own work to do has been overwhelming! I don't know what to do other than hope that she doesn't try to sabotage me moving to a new team.

One team was delivering for 12 months.

... but definition of done not met. Code crap everywhere. Tests barely there and are total mess.

I inherited mess after previous lead engineer.

I exposed all the issues to the management in a straight way, no sugar coating.

... and now guess who's the bad guy for "complaining" instead of shut up and "making it work"?

P.s.
"Giving accurate report about situation" is seen as "complaining".

Micromanager: “@Root, you need to do <thing>! It’s important, and very unprofessional if you don’t. Bad things can happen if you don’t do the thing. You need to get into the habit of doing the thing.”

@Root: Already does the thing.
Micromanager’s boss: Doesn’t do the thing.
Micromanager: Doesn’t do the thing.
Team: Doesn’t do the thing.

Micromanager: “You need to work on your reputation, @Root!”

Hey Root. Here’s a new ticket for you. It involves lots of things you’ve never seen before, and the only person you can ask is out this week.

Hey Root. Why haven’t you been making good progress every day? Why didn’t you reach out to the guy on FTO? Clearly you can’t communicate. Give me detailed status updates twice a day at specific times, covering <exhaustive list of topics> so I know you’re working. What do you mean “no”!?

Hey Root. Stop working on that ticket, and work on this other ticket. It’s the same thing, but different. High-priority!

Hey Root. You asking questions about that ticket pissed off a legendary golden boy principal dev, and he said it’s a bad idea and that we should have assigned it to a different team, too — you know, the team who usually works on these areas. But we might still have you do it. Please work on the previous ticket that’s in the exact same area until we decide.

Hey Root. Why haven’t you gotten anything done?

Everyone but me in my team touches the screen. Everyone except for my one co-worker G, she mashes it like the screen is at fault for the code being bad.

Holy fucking shit! Coding by yourselves seem so much fucking more efficient than in a team. Fuck you team! I know you might say this makes me a bad programmer. But you know what fuck you too!

Colleague started a slack channel for our team, management wanted nothing to do with it. We used it to work and have a bit of fun.

Some push / drive came form somewhere and now all the managers are on it. Yesterday I was told my screenshot and "snarky comment" are not appropriate for the workplace and to delete my slack message.

My comment was a joke about about a new app the company has to use "to increase efficiency" that broke and wouldn't let me do what I needed. It wasn't offensive, demeaning, sexist to anyone or even contain any bad language.

How petty and childish to be monitoring a private channel making sure everything is positive. We all joked that from now on our meme's must be about how awesome the company is and how much time we are saving on a daily basis.

God forbid we're allowed to speak honestly and openly or have a bit of fun.

Man I really need to get this off my chest. So here goes.
I just finished 1 year in corporate after college. When I joined, the team I got was brilliant, more than what I thought I would get. About 6 months in, the project manager and lead dev left the company. Two replacements took their place, and life's been hell ever since.

The new PM decided it was his responsibility to be our spokesperson and started talking to our overseas manager (call her GM) on our behalf, even in the meetings where we were present, putting words in our mouth so that he's excellent and we get a bad rep.

1 month in, GM came to visit our location for a week. She was initially very friendly towards all of us. About halfway through the week, I realized that she had basically antagonized the entire old team members. Our responsibilities got redistributed and the work I was set to do was assigned to the new dev (call her NR).

Since then, I noticed GM started giving me the most difficult tasks and then criticizing my work extra hard, and the work NR was doing was praised no matter what. I didn't pay much attention to it at first, but lately the truth hit me hard. I found out a fault in NR's code and both PM and GM started saying that because I found it, it was my responsibility to fix it. I went through the buggy code for hours and fixed it. (NR didn't know how it worked, because she had it written by the lead dev and told everyone she wrote it).

I found out lately that NR and PM got the most hike, because they apparently "learnt" new tech (both of them got their work done by others and hogged the credit).They are the first in line to go onsite because they've been doing 'management work'. They'd complained to GM during her visit that we were not friendly towards them. And from that point on if anything went wrong, it would be my fault, because my component found it out (I should mention that my component mostly deals with the backend logic, so its pretty adept at finding code leaks).

What broke my patience is the fact that lately I worked my ass off to deliver some of the best code I'd written, but my GM said in front of the entire team that at this point "I'm just wasting money". She's been making a bad example out of me for some time, but this one took the cake. I had just delivered a promising result in a task in 1 week that couldn't be done by my PM in 4 weeks, and guess what? "It's not good enough". No thank you, no appreciation, nothing. Finally, I decided I'd had enough of it and started just doing tasks as I could. I'd do what they ask, but won't go above and beyond my way to make it perfect.

My PM realized this and then started pushing me harder. Two days back, I sent a mail to the team with GM in cc exposing a flaw in the code he had written, and no one bothered to reply (the issue was critical). When I asked him about it, he said "How can you expect me to reply so soon when it's already been told that when anything happens we should first resolve within the team and then add GM in the loop?" I realized it was indeed discussed, but the issue was extremely urgent, so I had asked everyone involved, and it portrayed him in a bad light. I could've fixed it, but I didn't because on the off chance if it broke something, they'd start telling me that I broke the tool, how its my fault and how its a critical issue I have to fix ASAP, etc. etc., you get the idea.

Can anyone give me some advice of how to deal with this kind of situation? I would have left but with this pandemic going on, market being scarce and the fact that I'm only experienced by 1 year, I don't think I qualify for a job switch just now.

*the Company closes a project and splits us in different teams*

Me: *tells the manager for half a year about feeling extremely bad in the new team which is mobbing me, caling the previous project "shit" (it was not, it simply didn't need to be alive anymore cause we found out cheap alternatives) and not letting me do anything*

Company(half a year later): *sends me into a new project* we don't get why you are underperforming lately.

Me: *full burnout after half a year of being treated as living shit* yeah. Wonder why.

Today I quit my job lol.

In my two previous stories I told you guys about a job offering I got, and after a few more incidents in my old job, I decided I take it.

No, this is not an april fools joke, though it felt quite bad to tell my team lead that I quit on april fools day.

Due to notice period I'll begin my new work at first of july this year, can't wait <3

The last 5 months have been tough.... My boss ( who was a close friend) quit and I become interim department head... Trying to run a team who didn't seem happy I'd taken the reigns.

At the same time my wife's ongoing battle with her anxiety had gotten worse and she really needed my help with everything possible at home..

In March I was confirmed as the HoD but I was still doing 3 to 4 days a week on client delivery, trying to support all presales activities, manage a team of 10 people, travel for work and support my family....😩

It really got to me and I was close to breaking... The worry of not replying to an email ASAP no matter what time of day would eat me up, working late every night... It got too much and I was running on fumes with my weekends just me completely wiped out and useless to the family. 😓

.....But.....

I had a escape last weekend to a 🍻 beer 🍻 festival with friends that I was considering not going too and just losing the money but the wife made me go...

And it broke me even more... So much that its somehow put the pieces back in the right order in my brain and snapped me out of my major rut!

Somehow, sitting with friends, making stupid jokes, drinking way too much and blocking out all the work crap gave my brain the hard reset it needed. 🤟

This week I've come back a different person ( wife's words) work is a breeze, exciting and encouraging.... 👊

I can't get enough of playing silly games with my kids all night

And couldn't feel any more positive about things if I tried.... Set that spark back for my wife too! 😏💏

So.... After that long rant 👀

Tl;Dr - work and life got too much... Close to giving up... Too much beer with good company gave me a hard reset and I feel like a new person.... 👍

Plus the team is now loving the new direction and strategy too 👔

Who says drinking is bad for you? 😂🍻

I'm a tech lead for a digital agency.

Digital agencies are universally known for being shite. Why? Because they typically push through sub-optimal code with very little testing over tiny deadlines for maximum profit. Maybe I've just had bad experiences but this is the 5th digital agency that I've worked at that does this bollocks.

I am currently sitting on a Teams call at 8:39pm because the fuckwit project/account managers are unable to face up to the big scary client and ask them terrifying questions like "Is this bug a blocker for the deployment?" or "We don't have enough time to fix/change these things, can we delay another day?". They just assume that A - We will work into the evening, and B - that all the issues are P1 and that we should all 'pull together' as 'team players' to get this done in time.

No, Me and my team have to work into the evening for seemingly free because these pricks can't do their jobs properly.

The funniest thing of all? When I speak to the CTO about overtime payment he tries to make me feel bad about "we don't typically pay for overtime..."

Fuck Everyone.

Time to find a new contract.

I've come to a conclusion today: Management are fucking with me. I know it sounds far fetched, but its the only thing that makes sense.

I was in a meeting today, discussing some bad emails back and forth. Part of my issue was the amount of time spent on useless meetings, or waiting around to give demos.

The meeting got cut short, so I could prepare a demo for a VP ... after an hour and a fucking half of waiting around ... theres no time to see my demo.

What the actual fuck, seriously .... seriously what the actual fuck. What if the name of mother fucking christ is going on with this team, that they call me into a mother fucking meeting to discuss the "developers attitude" only to go and cut it short ... so they can fucking waste my time ... for the second time in 3 mother fucking days.

Oh i'd rather fuck myself with a cactus than spend the rest of my days dealing with this utter bullshittery.

I worked on an amazing web app that tracked satellites and their failure rates. it was beautiful and worked fantastically. Me team worked like dogs to get it done three months. Our manager insisted it has to work perfectly for the demo and we delivered... We all got raises and everyone was happy, right? WRONG!

Demo day comes and management decides that they don't want to build the app because the customer pulled out. Sooo my manager then asked me why I wasted so much time building it when static images would have been fine. I lost my cool and yelled at my manager "YOU'RE THE ONE THAT TOLD ME TO GET A FULLY FUNCTIONAL SYSTEM WORKING!" Then I stormed out of the meeting.

It is still the coolest thing I ever built. Too bad it will never see the light of day.

fuuuck, I overslept today, and I have to introduce a new team nember today and I will be too late in office because of that.

OK so i take a shower, and brush my teeth and get my clothes on in under 5 minutes (which is actually very fast for me), run for my train, just made it into it, get to the next station where I have to switch trains, and then it hits me again: 8 minutes delay, OK that made it even more bad than it was vefore, because I will miss my train on the next station where I again have to switch.

I will now end up 45 minutes too late in the office, only because I overslept. I hate me

I had a huge epiphany on Friday... not all developers enjoy coding.

Discovered when they brought down 2 of our environments, well told them what was wrong with the changes in their code that caused the environments to break, gave them links directly to the file in the gitlab repo that needed to be updated, and...

They fucking went home. The change would’ve taken all of about 30-45 seconds to update and they fucking left.

This person’s team lead come storming in pissed off because her manager is furious about 2 environments going down and preventing everyone else from being able to deploy their changes.

We provide the exact same details to the team lead about what needs to be changed, and advise that her team member took off....

30 mins later, her manager is storming up to us (devops/sre) livid as hell.

Explain the situation for a third time... manager is like, why can’t you guys fix it?

Look here you dense motherfuckers, we can fix the code. We can be the plumbers that clean up your shit. But what value do you gain as a developer if you don’t understand how the systems work and you keep pushing shit in?

Made the changes, fixed the environments, done right? Wrong.

The original developer made more changes not knowing what would happen and thoroughly fucked the environments again.

This dumb-fucking dumpster fire of a dude then sends us a slack message. “It’s down again, can you fix it?”

Our manager steps in and tells us to send him a link to the logs and have him fix it himself!

Thank goodness we have a badass manager.

Send logs, send repo file links (again), and send line numbers in the logs to try and help just a bit more. Dude goes almost the whole day without fixing it, environments are down, other devs are pissed, we throw this dude to the wolves. His manager starts to head over and was about to talk with my team lead when our manager steps out of his office and tells him the in’s and out’s of the situation and that our job isn’t to play log parser/error fixer for the developers. This dude that’s breaking the environments needs to be the one to fix the issue and his team lead should be aware of the problems and should have been able to correct his errors before it ever came to us.

The amount of hand-holding we do is ridiculous.

(Disclaimer, this one guy making some mistakes doesn’t sound too bad, but this is actually a common occurrence for like 40% of all of our developers)

We literally have interns still in college running circles around some of our full time devs. I know I’m not a developer, but for anyone that’s new-ish to developing, when you see shit like that please don’t lose hope. Those ass-hats got into programming purely for a paycheck, not because of passion.

Stick with it and your greatness will know no bounds 👍

As for you craptastic dipstick lickers, FUCK YOU!!! Go back to school and learn how to give a damn.

This happened today...
Manager: how long this is going to take?
Dev: 3 months
M: cool! 3 weeks then
D: no.. This is quite complicated and most of us are unfamiliar with the topics. It'll take us 2 weeks just to get started
M: drop the unit tests then. Just get the features done in 3 weeks. We have customers waiting
D: that's a bad idea. We'll end up with unstable co..
M: oh we also need to complete documentation, release guide, and this [shitty feature no one care about]
D: but that is even more complex. We don't have enough ti..
M: just copy it from stackoverflow. It'll only take 5 minutes guys

Worst part? This guy is technically sound and understands our pain really well. He is just acting dumb and trying to put the blame on us when the higher management asks

Second worst part? The whole team keeps silent when I try to convince him somehow and starts ranting after he leaves the call

hmm let's see
>atheist propaganda during lunch time
>fascist propaganda during lunch time
>praising the rival of the football team boss supports
>suggesting we should drink alcohol in work hours
>teaching minecraft to boss' son
>talking bad about star wars VII even though boss liked it

Not really a recruiter but at interview at one place I was given a printed code example and told that there was 8 bugs and that I shield treat it like a code review.

I found 16 bugs and 4 bad practices and explained them all to the director of software engineering and team lead (that set the test), they agree that I was correct; the director turned to the team lead and said ... Are you are your a senior

I tried not to laugh lol

I try as hard as possible not to be judgemental towards incompetent colleagues, motivating myself with the knowledge that we were all incompetent at some point, and that people need a chance to learn, and that sometimes too much pressure will lead you to believe that they're bad. Or sometimes, people just aren't good at the stuff you want them to be good, and you just need to discover that niche where they will be very useful.

Mostly that goes well.
I've had the incompetent late bloomer who was a family man who started too late to dev, and wasn't really serious. A bit of harsh talk, some soul searching over a few beers, made him into a really valuable asset. Not the brightest rock, but reliable, steady-paced developer who earned his stay.
Then there was the girl who wasn't really good at coding, but saved our team from disaster many times by keeping things into account, and realizing what must be developed or tested at every step.

However, there are exceptions. I've worked with people who have been nothing but a menace, through their incompetence AND attitudes.

The most noteworthy example was an intern that we sought out, by talking to professors to point us to their best students. So we got that intern on board. He seemed strange at first. Kind of perfectionist. Talked serious, with an air of royalty, and always dressed sharply. He really gave the impression that one must be worthy to receive his blessing. The weirdest part was his handshake. It was as if he was touching an iron hand heated to 3000 degrees. It was over before you even knew it. Leaves you kinda offended. Especially when he always took a wet wipe after that and wiped his hands. Am I really that gross?
But that's fiiiine. I mean we're all different and weird in our own ways, right? So he's a germophobe, so fucking what? We just gotta find a way to work together, right?
WRONG.
As soon as he started (and remember, he's a paid intern, who barely knows how to code, and has zero industrial experience), he started questioning my architecture solutions, code implementations, etc. I don't mind discussion and criticism, which is why I welcomed his input. But it seemed like he wasn't willing to accept any arguments, so I started looking for excuses not to talk to him.
Meanwhile, the most productive team member we had, to whom you could just give and describe an idea, with architecture and stuff, well, and you'd see it implemented the next week, with only the most well placed questions asked, started going into fights with this intern for the same reasons I was avoiding him.
.....
And here's the kicker.
Get this:
This intern comes to me (I was the team lead), while that guy is not in the office, and with a straight face, dead serious, starts telling me that that guy was making stupid decisions and being a bad team member because he doesn't ... I quote him almost verbatim... "follow my indications". He said that I had to do something because he refused to work with him together.
I was stunned.
This good for nothing imagined superhuman, who was completely useless and an amazing annoyance to pretty much everyone in the team, came to me, telling me that the most capable and productive developer in the team is bad, because he doesn't follow his orders, and that I had to pick between the 2.

I couldn't believe what I had heard.
I had so much emotion in me right then. I was angry, but at the same time I could barely abstain from laughing.
I just told him calmly that he was wrong, and that I wouldn't mind if he never came back. I didn't see him for 5 years after that.

Anyway, later that week our team went for a dinner + beer, and the stories from all the team members started pouring in. They didn't want to talk him down either, but now that he was gone, it was a weight off, and everybody could tell their story.

What a fucking asshole.

So 5 years after I stumbled on him as he was entering a church. Still an arrogant bitch. Barely exchanged 10 polite words and I continued on my way as he was disinfecting his hands from my filthy handshake.

They've literally left me with nothing to do. I'm doing nothing. I can't be happy doing nothing.

To illustrate the chaos: Everyone on the team was trying to figure out some defect. No one knows what is going on in the code. It's unlike anything I've ever seen.

I found an API call with a misspelled endpoint. It was wrong since the code was written two months before. There's no way it ever worked. Obviously no one tested the code because they would have immediately seen that the call returned a 404 every time.

I fixed it. That was my only PR in about a month. It was literally one character.

The next week that PR got reverted. Apparently the app works better if the API call fails. No one said what goes wrong if the request is made, just that it "causes problems."

That's how bad it is. No one knows why anything does or doesn't work. People write code that doesn't work, never test it, and the application works better in some unspecified way if that code never gets executed.

The last straw for me was when an architect told us that if we want to improve our skills we need to learn how to read and debug stuff like this.

1) Not to be immodest, but I'm good at figuring out bad code.
2) Just because I can doesn't mean I want to do it all day instead of actually developing software
3) He trivialized the really important skill, not making a mess like this in the first place. If his idea of skill is to sling crap without tests at the wall and then debug it, how is he an architect?

I tried really hard but I can't keep a good attitude. I don't want to become toxic, but why would I consider working that way? I try my best to be good at this. Writing decent code means a lot to me. It should mean a lot to them. Their code is costing them hundreds of thousands of dollars. Maybe millions.

I can't write good code and add value if all I do is debug bad code.

So I'm out. I'm going to another project. Have a nice life.

Encouraged a friend to quit his current job. He is mentally unstable now because of his employer. His jerk employer harasses him and blames him stuff he didn't do. Blames him pre-existing bugs/bad features/bad codes from three years ago! He just got employed by that jerk employer two months ago. I know how my friend works because he was once my team leader for 19 months. He works harder and is one of the best devs I've ever met. He doesn't deserve a dickhead employer and that dickhead employer DOES NOT deserve a talented(skillful) software engineer like my friend. If anything happens to my friend, a lot of people will be hunting him down.

Background: I work at a small startup company in Canada who makes simple FAQ Chatbots for companies who waste a lot of resources on the same Customer questions over and over.

So we were making this one bot for a provincial government who wanted a bot for students to be able to ask questions regarding the upcoming election and how to vote, etc. and get the answers they were looking for. Since it's Canada and a government bot, it had to be in both English AND French.

These bots take some time to train (we use Wit.ai mostly) in english so it was a challenge to train it in French. However I am bilingual (not very strong in French but can manage) so I did my best and the bot didn't turn out too bad. (English was great, French was, Id say, "not terrible").

HOWEVER, now that it is done (The company loved it, even with the less than perfect french version). The sales team (who know nothing of the process of making/training these bots) is now telling companies we support "SEVERAL LANGUAGES" and are currently about to sign a contract with a company overseas that wants a bot done IN JAPANESE!!.

To make matters worse.. when we (the dev team) brought up that it would be EXTREMELY difficult to do this, their answer was ... "You did it in French so you can just do the same but in Japanese"

HOW DOES THAT EVEN MAKE SENSE.

Oh well, Rosetta Stone here I come, I guess it's time to learn Japanese.

sprint retros with PM are a fucking farce, it cannot possibly get any more grotesque.

they are held like this:
- in the meeting, PM asks each team member directly what they found good and bad
- only half of the team gives real negative feedback directed towards the PM or the process, because they are intimidated or just not that confrontative
- when they state a bad point, he explains them that their opinion is just wrong or they just need to learn more about the scrum process, in any case he didn't do anything wrong and he is always right
- when people stand up against this behavior, he bullshits his way out, e.g. using platitudes like "it's a learning process for the whole team", switching the topic, or solely repeating what he had just said, acting like everybody agreed on this topic, and then continue talking
- he writes down everything invisible for the team
- after the meeting he mostly remembers sending a mail to the team which "summarizes" the retro. it contains funny points like "good: living the agile approach" (something he must have obviously hallucinated during the meeting)
- for each bad point from team members, he adds a long explanation why this is wrong and he is doing everything right and it's the team's fault
- after that happens the second part of the retro, where colleagues from the team start arguing with him via mail that they don't feel understood or strongly disagree with his summary. of course he can parry all their criticism again, with his perfectly valid arguments, causing even longer debates
- repeated criticism of colleagues about poor retro quality and that we might want to use a retro tool, are also parried by him using arguments such as "obviously you still have to learn a lot about the scrum process, the agile manifesto states 'individuals and interactions over processes and tools', so using a tool won't improve our sprint retros" and "having anonymous feedback violates the principles of scrum"
- when people continue arguing with him, he writes them privately that they are not allowed to criticize or confront him.

i must say, there is one thing that i really like about PM's retro approach:
you get an excellent papertrail about our poor retro quality and how PM tries to enforce his idiocratic PM dictatorship on the team with his manipulative bullshit.

independently from each other, me and my colleague decided to send this papertrail to our boss, and he is veeeery interested.

so shit is hitting the fan, and the fan accelerates. stay tuned シ

Apparently some freaking man in my ex-team tried to learn Vim because he thought he could become more efficient but he spend more than two weeks trying it while delivering poor quality code with extra spaces, bad indentation and extra "wq" strings

Client asks for website and budget very low and wants a form with dB. Think WordPress site is a solution. Build site.
Deliver site.
Client's IT team unable to deploy on server. They blame me for bad "code".
I have to go to their office and help them deploy on local machine using WAMP.
2 days and 100s of calls later, website installed on test server. Works fine.
All is well

So finished a project for a client, the client signed a contract. He signed off that all milestones where reached. Text me that he was very pleased.
We give 30 days to pay. 8 days before the due date he asked for a meeting, telling us he wants to go another direction and he wants the source code to show the new development team he's going with to get a quote from them. I tell him that, that's fine he can have the source files once he pays for the product which was in the contract they signed mind you!! And this FUCKING DICK FART threats to sue, saying he's calling his lawyer, threatening me and my development partner with physical violence, and saying he's going to sue me personally not because me work was bad but because I refused to give him the product before he paid. I was calm we offered to meet his new dev team explain the code, and show them what they needed to see to give the clients a quote and they would not allow that, saying how now I'm not getting paid instead I'm getting sued and that he will publicly shame my startup company. Just complete bullshit, good thing I saved the original contract he wanted me to sign which had threats of physical violence I. His contract... Which in retrospect should have been a hint, but it was the highest paying contract we ever landed. Seems he never planned on paying. What's a guy to do?

After mass layoffs my team went from 10 engineers to 4 with no drop in expectations. This was a ridiculous ask, everyone was burnt out and could not keep up. For some reason the geniuses in management gave me a bad performance review despite me doing 2 to 3 full time workloads.

That day I put in applications and got an offer in less than a month from one of them. Put in my notice and suddenly it was surprised Pikachu face. Now they are down to 3 engineers and admitted it would be months before they had the revenue to even backfill my position.

Good riddance.

I just spent 2 hours helping a fellow Sr Dev format an “if block” in code. Then helped show them how to step through the code. This is what passes as a senior at my company? I no joke have stayed at this job for 6 more months than I wanted to out of pure pity for my team. I want to quit so bad, but the team is in such terrible shape and can’t hire anyone new that is willing to stay. All good people personally, but gosh this job is just brain dead and eats my weekends when I should be focusing on family. Back to helping through the 500 line if block. There are worse things in life, but this just feels terrible.

Debugging a system error with a good team of fellow developers/devops people is fun.

We had an issue on Friday where we were getting a pretty cryptic error in our error reporting system. A couple of developers and I got together with a couple of devops people and we worked it out well as a team and figured out a pretty complex issue in a reasonable amount of time with everyone playing a solid role.

Nobody tried to steal the show and everyone listened to each other's ideas on what the problem might be. Through and through a great debugging session and made me think about bad ones and good ones I've had in the past.

Well the clown strikes again,

How do u break production and a testing environment in one night?

One full month preping for same thing that revolves around one config file and assured us he was confident,

He wasn't
he managed to fuck it up so bad for the team d brass lost d plot,

I'm not one for condemning people but my God Dante's inferno woulda had an extra ring if he worked with this buck,

The stupidity has shattered my belief in sunshine and rainbows

Introduced a ‘new’ logging framework for our web site. Web team is testing the integration and I get an email saying the logging wasn’t working. Instead of sending me how she is searching the logs, she sends me a screen shot of the code (which is ass-backwards of how I documented the logging library, but that’s another rant). OK, she wrote 5 lines of code that should be one line, but OK, the error still should have logged fine. I search the logs, and sure enough, there they are. Errors logged just as they should.
So I email back (with screenshot of the search query and results) asking how she searched for the errors.
Hour later she responds ..”I don’t know.”
That’s it.
WTF do you mean “I don’t know”?…WTF…you are a –bleep-ing developer too! This is not the first –bleep-ing splunk query you’ve written!
OK..I’m calm..feeling better. Wouldn’t be so bad if she emailed just me with the question (I’m not a splunk query expert either, we can figure it out together), but she was sure to cc 3 of the PMs involved in the integration, my boss, and other team members to make it sound like the problem was my code.

This is something I'll never forget.

I'm a senior UI engineer. I was working at a digital agency at the time and got tasked with refactoring and improving an existing interface from a well known delivery company.

I open the code and what do I find? Indentation. But not in the normal sense. The indentation only went forward, randomly returning a bunch of tabs back in the middle of the file a few times, but never returning to its initial level after closing a tag or function, both on HTML and JS.

Let that sink in for a minute and try to imagine what it does to your editor with word wrapping (1 letter columns), and without (absurd horizontal scrolling).

Using Sublime at the time, ctrl+shift+P, reindent. Everything magically falls beautifully into place. Refactor the application, clean up the code, document it, package it and send it back (zip files as they didn't want to provide version control access, yay).

The next day, we get a very angry call from the client saying that their team is completely lost. I prove to the project manager that my code is up to scratch, running fine, no errors, tested, good performance. He returns to the client and proves that it's all correct (good PM with decent tech knowledge).

The client responds with "Yeah, the code is running, but our team uses tabs for version control and now we lost all versioning!".

Bear in mind this was in 2012, git was around for 7 years then, and SVN and Mercury much longer.

I then finally understood the randomness of the tabs. The code would go a bunch of tabs back when it went back to a previous version, everything above were additions or modifications that joined seamlessly with the previous version before, with no way to know when and so on.

I immediately told the PM that was absurd, he agreed, and told the client we wouldn't be reindenting everything back for them according to the original file.

All in all, it wasn't a bad experience due to a competent PM, but it left a bad taste in my mouth to know companies have teams that are that incompetent, and that no one thought to stop and say "hey, this may cause issues down the line".

i genuinely like programming. it's like solving logical puzzles for me, challenges on a smaller or bigger scale, and this is fun.
i always feel this when working on something on my own, i.e. a full stack project where i take care of everything.

but i'm so sick and tired of corporate software development.
i'm tired of scrum, all these scrum meetings, it feels like they are sucking my life energy away. if at least i had the feeling that i work in a team where everybody contributes, the team work is nice and also project management is aligned.
i'm tired of having too many different tasks in too many different areas or projects and never having the feeling to be able to really concentrate on one thing, to be able to do a job well enough so that i'm content with it.
i'm tired of this feeling that what i'm working on is not meaningful. the feeling that my team is not part of a bigger story where everyone contributes their part and where there is a sense of productive collaboration between teams. the feeling that mismanagement will result in a lot of money being burned, because of work being thrown away or becoming irrelevant, or because of miscommunication, making promises that can impossibly be delivered on.
this feeling that i cannot really improve or fix the ship we are sailing with, but rather being handed a bucket and being told to constantly remove the leaking water and put it back in the ocean, but always at multiple sites of the ship all at once.
i'm tired of being the only female dev and altogether feeling so different from the rest of the team, feeling that i do not belong there.

even though i need to make a living, i just can't imagine anymore to spend so much of my lifetime for something that makes me feel so bad...

how to become a true scum master:

- formulate jira tasks for your inferiors as vague as possible, best they don't make any sense

- before sprint start, ask the subhuman being to estimate storypoints, and if they say they can't really tell with this description and choose the highest estimate, say "okay, let's estimate it to one sprint length", so they can actually work on it within one sprint (which makes total sense)

- if the scum dares to question the content of the ticket and begs for more details, be like teflon and give no useful answer at all. if they continue asking for a meeting to discuss the ticket, tell them to have a meeting with a coworker about it (who also has no clue). don't be available for them because you have more important stuff to do.

- bully them during daily standups that they didn't create clear subtasks from this task and criticize them because you have no idea what they are doing. tell them they are having performance issues and suspect them to sit on their lazy asses all day.

- criticize the team in general for bad performance, bad item tracking and never say something nice, to make sure everybody loses even the last bit of intrinsic motivation for the project.

stay tuned to learn how to make yourself a skull throne out of those filthy dev smartasses ^.^

2nd day in new job. Random HR training blabbing about something (thanks God all remote so I just did things around house). Blabbing about diversity and other corporate brainwashing. Then she proceeds to say that if someone is introvert and doesn't like to interact with people then such person should look for work in some other company (wtf x1). Next in line her real life story how she yelled at her subordinates (wtf x2 who admits to mobbing xd ) but that's ok because she is choleric and people have to understand that different character types make their team better xD
I have a bad feelings about where this is going...

Interviewed at a pseudo-startup (not quite a startup, but later realized run and organized like one) where the VP of dev ops seemed eager to have me in. I sent him my code sample and he said he'd schedule an onsite. Weeks went by without a peep.

Being persistent, I kept emailing, figuring the environment still might be worth the apparent lack of interest... Eventually the dude told me he'd been away on "travel" and he didn't check his mail. He said come on by if I was still interested...

I went in and met with a couple people on the team, interviewed (I think) well and he said he'd be in touch. Another two weeks -- nothing. I emailed again, he said they hadn't reached a decision. By this time, I'd pretty much written it off. I never heard anything back. No good, no bad.

Moral of the story, don't waste your time on anyone who doesn't respect it enough to give you theirs.

doNotMessWithITTeamInAFuckingProject();

Last night me with my team have a discussion with my project team. Currently we have a project for our insurance client building a Learning Management System. The project condition already messed up since the first day i join a meeting. Because since its a consortium project with multiple company involved, one of company had a bad experience with another company. It happened few years back when both of company were somehow break up badly because miss communication (i heard this from one of my team).

Skip..skip... And then day to day like another stereotype IT projects when client and business analyst doing requirements gathering, the specs seems unclear and keep changing day by day even when I type this rant I'm sure it will change again.

Then something happened last night when my team leader force our business analyst to re index the use case number (imho) this is no need to be done, and i know the field conditions its so tough for all team members.

So many problems occured, actually this is a boring problem like lack of dev resource, lack of project management and all other stereotype IT projects had. Its sucks why this things is happening again.

Finally my fellow business analyst type a quite long message in our group and said that he maybe quit because its too tired and he felt that the leader only know about push push pushhhhhy fcking pussy, he never go to the client site and look what we've done and what we struggle so far.

I just don't know why, i know this guy earlier was an IT geek also, but when he leading a team he act like he never done IT project before, just know about pushing people without knowing what the context and sound to me like just rage push!

Damnit, i maybe quit also, you know we IT guy never affraid to quit anytime from the messed up condition like this. Even though we were at the bottom level in a project, but we hold the most main key for development.

Hope he (my leader) read this rant. And can realize what happened and fix this broken situation. I don't know what to say again, im in steady mode to quit anytime if something chaos happen nearly in the future.

doNotMessWithITTeamInAFuckingProject();

The other day a non-programmer colleague asked me:
"How do you know what to type in, like, did you write all of that?"
As I responded, he asked me another question; "but how do you know wuat to type".

I use to have those same thoughts years ago.

It occurred to me that through constant bugs, errors, bad (team) projects and failures that its become second nature, like breathing.

So, as an experienced developer to people just learning the craft and juniors. Don't give up on your collabs, don't be disheartened by group projects, don't be discouraged by your peers who seemingly try to make your life harder.

Take it as an experience to better yourself and teach them something.

These are the experiences that will make you a better developer.

Folks...

I think I need to get away from web development...

Honestly, no grudge held against web/mobile development itsef... But the projects, the teams, the workflows... It's always shitty af.

I'm fed up with the bad architecture, poor management decisions, unmaintained legacy code, broken windows, arrogant juniors, arrogant seniors, code smells left to rot, the freaking red door... Hell! The fucking "we don't have time for that" answer to testing... Damn!

Been there done that.

Feels like it's always the same crap and unfortunately, it's rare to start a professional project from scratch.

Fucking angular, broken piece of shit.
Fucking react (& RN) community modules, broken pieces of shit.
Fucking lazy-ass node developers.
Fucking ES and fucking garbage proposals submitted to the TC39.

I wish I could do Haskell / Rust / Clojure professionally... I could even enjoy Go with a good team... Anything but that huge pile of dogshit JS and its community of brainfucked so-called developers.

I remember a bad freelance experience.

It was a sophisticated mobile applications (many UI, many customization, many APIs to integrate with). since the client have many future freelance projects, I give him 3 weeks as estimation time, and one day per week I work on its place to evaluate the progress and sync our work.

I worked hard, the quality was excellent.. but he kept ask for "small" changes and "small" features.. at first it was OK, and I was planning to give him a good example to profit from his future projects.. but he toke advantage for that and the same app extended from 3 weeks to 2 months and more.. he barely added a little to the initial price..

So what I did? I uploaded the code to a private repository in Bitbucket, added him to the team.. I wrote few lines how to sign and publish the app.. aand disappeared.
his luck, I disappeared from the country, I immigrated to another country for best job opportunity.

[9:10]

CTO (works as a team lead): You here?
Me: Yes 👍
CTO: After doing X, Y and Z I broke X. That should not happen. You do understand, that this is not a good UX?
Me (asked CTO X amount of times to hire a a good designer, because I’m not): Well, we made the backend receive Y when X is triggered so B can be passed. I can tell the user to do Y in order to do Z.
CTO: NO, you will not. Do what I’ve said.

DUDE WTF? YOU FUCKING 🐎 I WILL BLOW YOU BRAINS WITH MY MORNING NAUSEA AND DIARRHOEA. FUCKING DIPSHIT ALLOWS HIS BAD MOOD AFFECT OTHER EMPLOYEES. HOW THE FUCK YOURE A CTO.

IM NOT GOING TO REWRITE THE CENTER PIECE OF OUR APPLICATION IN A DAY, WHICH TOOK US MONTHS TO MAKE. FUCK OFF

Monday, hurray 🥳

So apparently there was a prod issue all day today because some server app couldn't start up.

The error was caused by missing Params...

And seems everyone that got asked to look at it are pretty clueless.

I looked at the text msgs now cuz my phone wouldn't stop vibrating from notifs (yes it got that bad) and I'm thinking, of all the ppl you guys could've asked, no one reached out to me... Who well knows exactly it works, and how to fix it.

But the issue with the team is everyone works on everything but most people have no idea how the apps actually work...

Jack of all trades, master of none...

Anyways, sitting on the sidelines watching the chaos ain't too bad either....

Another case of "devs too stupid to poop" TM.

We had a funny discussion today.

Topic came up that a project using Lucene was incredibly slow.

Then came the yadda yadda of Java bad, Java sucks, Java bla Java blub in the gossip mill.

Both things irritated me, last thing was just the usual "I want to use new stuff cause I wanna be a cool jackass" trouble.

So. Today meeting. We did quick analysis by pair programming.

If I tell you that a whole team managed to review an PR, give it green light...

Despite the PR using the thread safe Lucene IndexWriter in a non-parallel fashion for large bulk inserts?

The whole problem screamed parallelization.

Yeah. If you ignore that scream and implement it in a sequential fashion, it is slow.

Congrats Jimmy, your retard level is off the charts.

Well, my company hired a total amateur who can't do anything right on his own without copying code from me or the internet and I have to pretend he's helping in any capacity because otherwise I'm a "bad team player" and "should communicate more".

Helped me get over impostor syndrome, at least.

Worst dev experience was when I was asked to "take a look at" a propriatery Windows app built by a now non-existent team at the company.

The code base resembled the quality of legacy code where about every hour I felt like I needed to vomit. But that wasn't even the worst part for me.

This was the first time I had to develop on Windows and was sent a separate dedicated laptop for this. Now I started to have a bad feeling about this because as far as I had known every single dev at the company used company Macs for development (including me for other projects). It turned out the Windows laptop was indeed configured for a non-dev team :)

Having liased with IT admins for a day I finally got my environment set up and hit install on the dependencies and in 10 minutes it got to less than 10%. The laptop was pretty powerful so I couldn't belive wtf was going on, fans were ramping. Checked task manager and the company Anti-Malware was hogging the whole CPU.

I was so mad that I managed to get the IT admins to completely disable it and then it was only the pain of working with shitty code on Windows which would have been more than enough from the start. Thankfully it only lasted a week.

I'm having an existential crisis with this client.

We are spending millions of $s every year to make sure the product's performance is perfect. We are testing various scenarios, fine-tuning PLABs: the environment, application, middleware, infra,... And then we provide our recommendations to the client: "To handle load of XX parallel users focusing on YY, yy and Zy APIs, use <THIS> configuration".

And what the client does?
- take our recommendations and measure the wind speed outside
- if speed is <20m/s and milk hasn't gone bad yet, add 2x more instances of API X
- otherwise add 3xX, 1xY and give more CPUs to Z
- split the setup in half and deploy in 2 completely separate load-balanced prod environments.
- <do other "tweaking">

- bomb our team with questions "why do we have slow RTs?", "why did the env crash?", "why do we have all those errors?", "why has this been overlooked in PLABs?!?"

If you're improvising despite our recommendations, wtf are we doing here???

One day I will crack. Hopefully, not sometime soon.

This begs for a rant... [too bad I can't post actual screenshots :/ ]

Me: He k8s team! We're having trouble with our k8s cluster. After scaling up and running h/c and Sanity tests environment was confirmed as Healthy and Stable. But once we'd started our load tests k8s cluster went out for a walk: most of the replicas got stoped and restarted and I cannot find in events' log WHY that happened. Could you please have a look?

k8s team [india]: Hello, thank you for reaching out to k8s support. We will check and let you know.

Me: Oh, you're welcome! I'll be just sitting here quietly and eagerly waiting for your reply. TIA! :slightly_smiling_face:

<5 minutes later>

k8s team India: Hi. Could you give me a list of replicas that were failing?

Me: I gave you a Grafana link with a timeframe filter. Look there -- almost all apps show instability at k8s layer. For instance APP_1 and APP_2 were OK. But APP_3, APP_4 and APP_5 were crashing all over the place

k8s team India: ok I will check.

<My shift has ended. k8s team works in different timezone. I've opened up Slack this morning>

k8s team India: HI. APP_1 and APP_2 are fine. I don't even see any errors from logs, no restarts. All response codes are 200.

Me: 🤦‍♂️ .... Man, isn't that what I've said? ... 🤦‍♂️

I am a senior a DevOps engineer who took the production stack down for ~10 minutes today because of a bad code commit. I could use some encouragement! It’s a fierce world of competitive engineers and I wonder why my company doesn’t replace me. The mistake was missed by two other peer reviews... but that doesn’t stop me from feeling this way.

Have you crashed prod? Did your team support you or tear you down?

A morbid realization (I am just wasting your time keep scrolling)

Unless someone takes a stand for the user, and their comfort and requirements, unless someone looks a client straight in the eye and says "no, I will not do that, and neither will my team" and denies them their request, nothing will change, good devs will keep losing their spark to save themselves frustration, good people will walk away and the tyranny that we face daily grows... unless someone stands up, someone who cannot be knocked down, or reprimanded and told they're wrong for fighting for what's right.. unless someone stands up for what is right and fair... nothing changes... and nothing ever will... poor programs, bad games and content, lower standards, frustrated users, annoyance that you don't matter as a user or a dev will never go away... unless someone says enough. But no one will, money is the boss, morality a liability, and people an abundant resource. This world is backwards, devs are carrying the blame and no one who is able, cares enough to say "that's enough!".

In order to reduce support costs, manager instructed his team to remove all logging/reporting of errors in the company’s CRM application.
Team’s support tickets went down 80%, manager received an award for his efforts, but mysteriously, DBA/support workload increased, bad/missing data,
increased support tickets in other areas of the business (shipping, etc. that relied on correct data from the CRM) and other side-affectual behavior.
Even after pointing this out this correlation, showing before/after code, no one believed the two were related and I was accused of not being a ‘team player’.
“You and the other teams need to learn from his example!”. As ‘punishment’ was I was moved to the team managing the CRM application.

Maybe not worst, but most frustrating. One of the systems I helped maintain at my first job had a few different bugs that caused bad data in the database. The "solution" to the problem was to write SQL queries to directly fix the production data. This would take one member of our team (it rotated weekly) about an hour every day to fix because there were literally dozens of these errors.

All the devs knew that we could identify the root cause and fix it in, probably, 3-4 days tops. Management would never approve the time because it would take longer to fix the root cause than it took to fix the data.

I worked at that company for 7 years. The bug was there when I came on, and it was there when I left.

I started working for a company something around 1-2 months ago, they said because I don't have any experience with their stack, my salary will be lower than other team members. I said there is no problem and started my work. My first task was refactoring codes that their experienced programmers have wrote. My second task was extracting data layer from views. (They use Laravel and MVC architecture and they get data directly in views, not controllers). So, by end of the month when I talked with my boss I said I should get more money because I was better than your experienced programmers. He refused my request so I said I will not work with your team anymore :)
Anyway, never accept a job if you know you deserve more money than what they say will give you.

P.S: Sorry for my bad English. English is not my native language

this was about office politics. for context, a lot of non tech people think they can borrow our time willy nilly and our boss agrees, so we're often pulled out of our tasks to do random shit.

these girls asked for my consultation on a simple problem, because another team wasn't fixing an issue for them and they said it wasn't possible. i said it was possible and simple to solve, i spoke to the other team, showed them how to do it and thought that was done. they kept asking me to produce proof that it was possible, excessively, like i had nothing to do.

that went on for a week, lots of back and forth, i was getting tired, so i told this girl fine, I'll do this stupid thing IF you send me an email making this a formal exchange, she says fine. the next day i find out they went after another guy in my team, who's much busier than i, and he stopped everything to coddle them.

i told him to be careful about that stuff, because he's setting himself up for this shit, he's making the rest of the team look bad and he's stopping his work to do something that was already done, because they couldn't bother to send an email. had a huge discussion about this, he was super condescending and overall, he was an asshole.

next time, I'll just send the girls his way

DevOps is a huge scam.

Whoever sold companies maintenance-free cloud is God-tier marketer, they would be able to sell fire extinguishers in hell.

First, the platform is constantly moving, keeping up with all the updates for Kubernetes/CNI/Ambassador/Calico/kube-proxy/wtf/foo/bar/etc requires a huge team constantly peddling the boat; and if not updating in time - eventually everything will suddenly break when AWS deprecates old Kubernetes version (1.23 in EKS has just 1 year and 2 months (!!!) of support) or whatever else. At least they don't deprecate services that often.

Second, all other tooling either suck, or expensive as a Boeing. DataDog/Splunk/NewRelic/Grafana? Data centers were built for the monthly prices of these tools not so long time ago. But, capex vs opex, what stupid software engineers knows (though, it's hilarious to be present on a meeting with an agenda "reduce cloud costs").

That's all really.

On the bright side, when the team is solid and really care about the product and build it in a cloud-first manner (with understanding of all the requirements, caveats and limitation) - it can be rock solid, stable and fast platform.

To bad it's incredibly easy to implement some impressively wrong architecture (much more easier than f'up single-server architecture).

No, you cannot ask us to move our tech meeting elsewhere because we're being "loud", for the same reason we don't ask you to leave the area because your non-work-related chatter is distracting us from our said meeting. It's the only video conferencing system in the joint, and it's not our fault you and your people sit nearby. How dare you go past us and complain to our boss as if we're nothing to you - just because you were recently promoted, don't act like you were never in the trenches with the rest of us. It's like you have no respect for us now that you've gone a step up the ladder. The next time you or your team members try to fuck with us like that over petty shit like this, we're going to bring the hammer down on your asses and burn every last vestige of self-worth you have by making sure you never get a moment's peace. It's bad enough you and your team suck each other off during our bi-weekly department meeting by patting yourselves on the back for doing what's supposed to be your fucking jobs - don't you dare try to drag us down to make yourselves look like fucking saints. That is where I cross the goddamn line.

> be me
> starts job at a new company
> team likes me, coworkers appreciate my skills
> bosses have plans for my future
> insomnia hits
> wakes up at noon
> 15 missed calls, 20 unread messages at the start of my second week, some from the client firm
> cuss-word.jpeg

Please tell me it's not that bad and I'm not the only one that gets bent over by poor sleeping habits :(

Time management tips one must follow to be successful:-

1. Remove distractions:- Phone, Whatsapp, Instagram, FB, etc. All away from you during work.

2. Remove clutters: Get rid of not required things.

3. Eliminate redundancy

4. Emulate others: (My favourite) If someone has spend time and done some work. Do not reinvent the same work done just replicate that work and continue from that point.

5. Share burden: Team work and depending on others is not bad.

6. Make work fun: Most important if you enjoy your work you will give your best.

- be any programmer hired to a job
- do some cool thing that helps the business
- gets labeled as a smart programmer and a helpful team member
- get questions and cries of help from everyone at the office
- get burnt out and refuse to help some people
- get labeled as lazy, bad at my job, and having a bad attitude
- gets shadow fired
- cycle repeats

It’s time to burn down the houses of every rich person - and I hope we actually fully commit this time :)

One of my clients got hacked.
FML. It was fucking bad passwords by a team member.

Google has now blacklisted the domain.

Removed the shady code, requested for review. Hope it recovers soon.

Any idea how long it takes for Google to remove the red warning page before you even enter the page ?

Junior engineer asking managers on Slack about prioritisation..

Junior eng: Hey managers, I have these tasks A & B lined up and some other type of work... Is it ok if I finish A by Weds and B by the end of week or should it be done sooner? Also, is the order fine or should I prio B first?

*silence for hours*

Random dev feeling bad for junior getting no response chips in: Hey, you are doing great, that order makes sense to me and let me know if you need any guidance or have questions!

Junior dev: Thaanks and will do!

*another hour goes by*

Manager: Hi team. I have asked other engineer X to do task B tomorrow.

what the fuck. at least answer the fucking question and say it needs to be done sooner. felt bad for poor junior here. :/

> Advice to new coders

Don't worry over picking language A or B.
Just pick A, use it for a month, then move on to B.
In a normal 3 year college degree you'll try multiple languages, some of which you'll never use again, and they'll each teach you something.

I had classes in Java, C, C++, C#, Prolog, Assembler, F#, JS.

Never used F# again and no one uses Prolog. But they were great for learning recursion and logic.

It's not like you take "a step down a bad path" if you pick a language you're never gonna use again.

You'll also learn new stuff on the job. We have one team that uses Go and one that uses Rust. None of the devs ever studied those languages. They were mostly former Java devs who leaned on the job.

Worked for a team where Scrum was thrust on it to fix/cover up bad management decisions.

Manager is really enthusiastic (to impress his new boss) and gets a bunch of colored post-it sticky notes for stories and shit. Team spends a bunch of time carefully writing stories & etc and arranging said notes on a white board. Come in the next day and 90% of them fell off due to condensation, or such such.

Left the group, with the rest of the senior dev staff, after the "15 minute" standup expanded a minimum of 1 hour each day... and the SM carefully writing down everything everyone said.

A co-dev gave me some career advice - "when the pilots are drunk, it's time to get off the plane."

My new favourite quote...

"I can't be the only one worried about the deadline"

By boss speakign ot my team who is expected to deliver 6-8 months worth of work in 5 weeks time...

Too bad he does not know he IS the only one worried, when you going to miss a deadline by that much when you never agreed to it in the first place, have not seen a single API and the scope is still actively changing and lets not forget we have no DevOps yet...
why the fuck would you worry...

After 9 weeks of waiting for my much delayed dell xps 15 i opened the box and it's fucking azerty ... While i clearly, CLEARY requested qwerty. I mentioned it 4 fucking times for the love of god make sure the keyboard is fucking QWERTY .. THEY GAVE ME AZERTY .. on top of that shittrain they also forgot to include​ my integrated fingerprint reader which i paid extra for.. man what a fucking shit company .. they might make half decent hardware but they piss all costumers of with their insanely bad braindead costumer service and sales team.

9 weeks of waiting , receiving the wrong configuration, probably again 5 more weeks of waiting.. man im starting to hate this shit company.

!rant

I promised myself I wouldnt cry but ... nah I wont.

So I got the job and today was my first day of work, well not precisely work but introduction to the cultuure of the place, signing tons of paper, I probably sold my soul but who cares?, and I met my team, so far everything seems cool, except tthat I will be using windows and wont be able to use any streaming websites or services (yt, spotify, deezer, etc) yes I know, there are ways around it, but come on guys I dont wanna start screwing my first week of work, anyway everything is cool, even the food is tasty there iis only one thing left, my workspace Im an extremely bad decorator so I need ur help, (and yes I know i have to have a duck and a devrant stressball) but apart from that guys and gals, any ideas? So far ive thought about a debugging body, a lava lamp and an extra monitor.

On my project the customer has re-signed into a contract several times when they have budget to continue work. The first time they got us to build the system was a huge success story because the team was assembled quickly and we did rapid development. Initialize repo to prod in 1.5 months. The customer asked for the same dev team. Strong dev team, a PM that doesn't take shit, and pure agile. Lets call her don't-take-shit PM.

When the customer re-signed the executive decided that she didn't like don't-take-shit PM. So the project manager gets replaced by play-by-the-rules PM who will comply with stupid requests and micromanagement. He isn't a bad PM but he tries to make everyone happy. The amount of management types executive installs on the project is massive, and development team is cut down in major ways. Customer and executive shit rolls down to the development team and we can't get anything done. The customer starts to lose faith because we can't get traction. They start demanding traditional waterfall/SDLC docs. Which causes more delay in the project.

So the executive decides that the PM can take a fall for it to save face for the company. She moves play-by-the-rules PM to another project. He starts handover to a new PM that has a history of being her pushover. The customer hadn't seen him yet so now we have push-over PM.

Play-by-the-rules PM is finally out of the project and instead of moving to a different account the company decides to "lay him off because there is no work". So basically they made him take the fall for the failure while promising reassignment, and instead let him go. This is so unfair..

Meeting with push-over PM yesterday and he shows us his plan. Identical to play-by-the-rules PM's plan that got him axed.We point that out and show him the docs that were made for it. His face clearly communicates "OH SHIT WHAT DID I SIGN UP FOR?"

Sat down with the Project Management team today to discuss a signage installation. This is how the conversation went...

Me: Right, so we need to get the hardware on-site asap so we can get this configured before it goes over to the production guys to have the facisa installed.
Them: That's fine we have plenty of time. Stop rushing things.
Me: Okay, so do we have the story board in place ready for development?
Them: Nope. Hasn't been done by the designer yet because he is in a bad mood.
Me: Okay so when does the client want this?
Them: 3 Weeks' time
Me: But it is atleast a week of dev time?
Them: Sure. But you can work late if needed...right?

This is a typical conversation between them and me. I'm the sole developer here. So done with today.

Ok Storytime.
Yesterday I applied for a summerjob as a Software/Webdeveloper at some companies. Today I got a call and they tell me I have the job. When I asked what kind of things I will have to do there the Recruiter didn't really know, so I accepted because fuck it.
Later I got told that somebody from the team will be calling me. So i ask that guy what I'm going to be doing and he tells me they have a old sharepoint application that they need to migrate to a new sharepoint version.

So I read up on sharepoint and find out about the languages ASP.NET supports aaaaaand it's about my least favorite language C#. (Well actually that would be Visual Basic but nevermind) We did some C# in school but I never got fond of it.
But hey learning something new ain't so bad or is it?

What are your thoughts on Sharepoint, ASP.NET and C#?

So, 9months ago my scrum master came to me and asked me to spearhead a "little" API... 2months work, no worries... I started the analysis and quickly discovered that that estimation was grossly understimated...

I convinced them that it was not 3 months but 4. I alerted to the design mistakes that were made, I pushed changes and made sure the entire project worked, was stable and the best it could be... 4 months passed, target proposition donne... Several change requests since then and we have been implementing braindead CR after CR for 5 months... Most CRs came from design issued I raised but we're ignored at the time just to come back and bite them on the ass...

Horrible design, bad documentation, amateur requirements analysis... However, delivered successfully with great acceptance...

What was my reward? They rearranged my team, removing virtually every good performer.

Never did I receive a "good work" or a "thank you"... I don't want one, I am just doing my job... However can you please not fuck me in the ass!? I now have 2 projects to spearhead at the same time and virtually no team... I can only handle so much!!!

Some good news? Ok, just announced I'm the project owner of a new project, that we will take advantage and make a 2 in one.... Great! Some more work for my lap! Thank you for the workload raise!... Ok, timewise? One month! And I still don't if that includes implementation....

TL DR; did my job, got fucked with more work...

Sorry for the vent, just wandering if I should try and not do my job...

Best:
Really getting into Rust. It has taught me so many things.
1. Null is evil
2. Sum types are amazing
3. Compiler can actually have good error output
4. Multi threading is actually really scary if you don't have a compiler to back you up

Worst:
I had to deal with SSIS. It has also taught me many things:
1. No matter how 'mature' a product is, it can be awful. Simply dump a random error code, the user can figure out what went wrong, no need for good error messages.
2. The modern concept of the database is crap. It's a gigantic global state that is used by everyone and owned by no one.
3. Don't use tools that aren't made to be used with version control.
4. Even when you tell your team that it's bad, you will be ignored.

When I started off working on this particular project under a new technical manager, I used to love working overtime because the work and the problem we were trying to solve was really interesting. My technical lead was also a really awesome dude and I was able to learn a lot of things under his guidance. A couple of times, I didn't even mind working on the weekends too in case we wanted to meet some strict deadlines. I wanted to make sure that my team's brand name does not get spoiled and we deliver on what we promise.

It was all good until all the management started taking our overtime and weekend work for granted. It took me some time to realize this. Now it almost became a part of standard expectations. It was getting irritating. Managers could see this uneasiness but chose to do nothing.

The work increased, so did the team and the communication channels. The newbies in the team now worked overtime and on weekends. And everybody started acting as if it was normal. That's when it stuck me that I am responsible for inculcating this unsustainable and life sucking culture in the team. I stopped working overtime and started questioning the set deadlines, often asking them to postpone things. Management got furious and changed their focus on the newbies who'd work overtime, often rewarding them to reinforce the behavior.

I tried undoing it, asking managers that the team will not work on weekends. There was friction and managers would agree but the old bad habited cultural spore would pop up tume and again and the team would go back to the regular overtime and working weekends thing. As more time passed, the managers would circumvent me and start talking to others in the team, giving them work and deadlines directly because I started to say 'No' when I felt the need to do so. I tried to protect some folks in the team who would not be able to speak up but were frustrated. I started caring less about the team's brand and more about colleagues who were suffering due to such unethical (and illegal?) practices being normalised in the team.

Trying again and again to get back to 'normal', I failed everytime. Unsure of how far I'll be able to go on with this without getting severly burnt in the process and seeing no respite, I decided to move on. I put in my resignation two weeks back and want to start a fresh in another company.

I feel I am responsible for bringing this into the team without realizing the repurcussions of my working overtime. Staying in the team for more than 3.5 years, I could actually feel how managers have no fucks about your personal life and work life balance (despite showing oh so much concern about the well being of my family) and would reward anyone who works as per their whims and fancies. I wish I never get to work for a management such as this.

Can't stand it when devs who never bother to do anything / don't pull their weight etc. suddenly come out with:

"Ooh I'm really feeling the imposter syndrome right now, I feel like everyone around me is just leagues ahead of me and I shouldn't be here"

...then wait for everyone to tell them how amazing they are, how they're a critical part of the team etc.

No mate, imposter syndrome is a thing, but so is being a genuine waste of everyone's time. I'm not talking about having bad days, I'm talking about your work output being practically zilch for the past half a year or so because you're "not too familiar with the framework", then going after this pity party approach. As a senior dev, it's kinda insulting to all the great junior and mid level devs who do a better job while being paid considerably less.

Unfortunately, I was causing the bad experience of the group project.
Had a 3D modelling class at university. I was totally overwhelmed and had no time to do anything for the project. I was too scared to face my team so I decided to just break the contact and didn't show up to the presentation.
I thought I would get a bad grade and that I will have to take the class the next year again.
But the worst part is, I got a better grade than the rest of the team because someone did the part, I was responsible for, so well.
I felt so bad for my behaviour, I cut my hair and shaved and hoped they won't recognize me at the university.
I'm sure there are or will be some rants about me this week -.-'

I want to share this story and need your advise.

When I was teaching exisiting team members about git and new iOS development ecosystem. I was changing the whole ios development practices and processes that time. One of my teammates wasn’t listening, when implementing the new ios development practices and standards, he actually screwed all of the projects.

He’s been with us for 2 years and he even don’t know how to use git. He forcefully push his changes without pulling our changes first. I was so angry that I reported him to my manager to address this matter. And then my manager told me, he is aware of my teammate’s incapabilities. He said he was planning to terminate him, and he is been thinking about it for 3 months.

When the judgement day came, we were in the meeting room. My manager told us the bad news that one of us will be terminated. During the meeting he said, “I am sorry, {my teammate’s name}. You will be out of the team due to {reason of termination}. {my name} reported to me that you dont meet the deadline, you are always late with 2 weekly sprint to your tickets”. As my manager keeps talking, my teammate look at me with his eyes so angry together with his girlfriend (her girlfriend is part of mobile team, but she is focused on UI/UX).

After my manager stops talking, her girlfriend started crying and said I was the one who should be terminated. Her reason was that I keep on giving difficult tasks to his boyfriend, that’s why he is always late to report. In my defense, those tasks are not difficult, most of his tasks is just changing the color of labels, changing layouts. If you are an iOS developer you know how easy it is to change font colors, changing the layouts using storyboards. Her girlfriend keeps on rambling that I should be the one needs to be terminated.

After few days, he left the team and surprisingly his girlfriend stayed and we never talk to each other except anything about work.

I am really pissed guys. Now my teammates think I am the bad guy asking my manager to terminate anyone in the team if I feel to. I feel very very not good in my work now. I can’t function what I used to. The termination of my teammate was already planned why am I should take the blame?

dear female devs / haecksen, how many other female devs do you have in your team?
if not so many, how do you feel about it?
and do you get a lot of sexist bullshit or not so much?

would be great to hear your experiences.

the female quota among our devs is < 3% 😅
most of the time i don't think about it and just do my job and it's fine, but sometimes i think, it's a bit weird. also, there is this fear that people might not have trust in my skills. it can be good and bad to be "special"... anyway, having more female rolemodels / mentors / colleagues to have technical discussions with would be awesome.

Half a year ago, I got fired in my job. The reason was the same always bullshit; we have very little clients, economy nowadays is terribly bad, our priorities are different now than when we hired you, etc.
The last week I spent there, I heard something about my poor performance and programming skills, and that pissed me off a lot. For six months I worked on a laravel web app for managing customers, tasks and invoices, a fucking CRM, but made specifically for that company just because they didn't know sugar, odoo, prime or whatever.
Parallel to the crappy CRM, I was told to patch some PrestaShop, WordPress and plain sites, and it was hard to communicate with customers, management ignored every email I sent, and all I was told to do was "do as they say".
The result was shit, obviously, and my work showed much less skill, knowledge and expertise than I really have.
After that, I spent a few months unemployed, studying and working as a waiter just to survive, because my contract didn't comply with unemployment office requirements for a pay.
Then I got this job, on an analytics company where guess what, I'm told to write a fucking laravel web app for managing customers, invoices and tasks. In the meantime, I design websites, and communication with customers is shit, and management ignores every single mail I send.
My salary is eight hundred putos euros again, and will contract is wet shit.
I know, maybe I am "not that good" to earn a 3000€+ salary and have a good team support.
But I'm not */that/* bad.

For those who have seen me ranting about ending up in a bad team.....

Few days back I was emotionally and mentally affected to a level I couldn't handle anymore. I spoke to my manager (our team got a new manager who is sensible and serious) and asked for team change and he said it was possible but he would need some time. 🙂

How do you guys/girls explain to potential new customers that you can perfectly work in a structured business environment and follow the rules, but also that you're assertive enough to oppose desicions being made based on bias, misunderstanding, fanboyism, or grave stupidity.

I just got informed from a freelance position that they would have hired me if it were not for my 'rebellious nature towards customers'

I don't oppose customers, i oppose stupidity unfounded.
Example from experience
> me working in a helodesk support position, all windows computer.
> new mgr comes into office, is a douche and complete mac fanboy
> wants all computers that are FINALLY working decent for some time in the entire department replaced with mac's... Back at 2010.
> whole team, even disliking microsoft themselves, are telling mgr that's a bad, dangerously dumb idea, expensive too, different OS, different software mgmt making, back then integration microsoft and apple was beyond diarhea... Several other issues the senior devs and admins pointed out

>mgr: 'but aple is soh much better, like a billion times better, hurrduurrrrr'
His decision passed somehow to the board..
> All stations from our customers get changed...we don't get a single machine to try out problems because overspending
> we are most of the time unable to help out customers because we still have pc's...
> mgr asks team why performance drops after 1 month
> we compared performance graph with his starting date of mgr, see clear drop after mgr's plan implemented...
> board stilll stands by mgr, gets praise for 'bold changes in the company', but appears to be some associate's son
> two main seniors leave after 15 years of employment, in three months, 80% of staff leaves.
> we canr fix the problems, we are not dev's , we get shit from all sides, i was still a junior in the industry so i worked as a slave inside that job.
> eventually get fired due to 'bad performance'
> mgr loses entire team... 'Hey why don't we outsource this dept to south africa, it's a lot cheaper! '

now that company is an it hellhouse where everyone get clinically depressed from sitting atbtheir station...
This is what i wish to oppose!

How to make that clear!

I got recognized!

I'm new here and was mostly learning, but my team pushed through some bad issues and I got recognized as well. Even for helping whatever little I could.

For all the rants of bad bosses and clients and work. Here's a happy one. :)

I'm in good company in this company.

How bad it feels when it work in a place where Agile and DevOps are mostly abused buzzwords.

Forced doing "scrum" with:
- half of the team providing endless daily reports instead of focusing on the 3 questions
- a scrum master that is barely reachable
- a product owner that would not even make a decision
- a sponsor that pushes us to go faster regardless of current technical debt (it's important to look good to other sponsors!)
- doing all possible scrum ceremonies with no value added
- not even estimating stories
- not even having accurate description in stories. Most of the time not even a description.
- half of the team not understanding agile and DevOps at all

Feels so good (not). Am I the one in that boat?? ⁉️

What's the point of doing scrum if implemented that badly?? 😠

(first post/rant on here)
So I recently started at a new company. I was kinda aware that the project I'm working on would be rather old school (to put it in a nice way :-)).

Part of my job is to 'industrialize' and update/clean up the existing code so there is less time spent on fixing bugs due to bad design.

One of the first things I had to do was to write a new interface to integrate with external software.

I already noticed some rather nasty habits, like prefixing every variable with m (don't know why), private fields for every property (all simple properties) and a whole lot of other stuff that either is obsolete or just bad practice.

Started writing clean code (simple classes with properties only, no m prefixing, making sure everything is single responsibility, unit tests, ...).

So I check in the code, don't hear much from it again besides the original dev/architect that started the project using my code to further work on that integration.

Now recently I started converting everything from TFVC to Git (which is the company standard but wasn't used by our team yet). And I quickly skimmed through my code to check if everything was there before pushing it to the remote repo.

To my surprise, all the code I had written was replaced by m prefixed private variables used in simple properties. BL classes were thrown in together, creating giant monstrosities that did everything. And last but not least, all unit tests were commented out.

Not sure what I got myself into ... but the facepalming has commenced.

Why most of the Indian developers code so bad? I face it very often, with my colleagues, with the freelancers we hire, even with our clients.

I am an Indian, and I feel so much disgusted (& sad as well) when a client tell us that they have a dedicated team to rework on the code which they outsource from India. If you visit a freelancing website you will see that the Indian developers have the least price, and they bid on literally anything even without understanding what they need to do. And finally when they get a job, they complete it, but with a fully f*cked up code and the worst architecture possible.

I have a lot of friends working in IT, and I personally know that they do not have any passion about programming. They just work for money, nothing else. I don't understand, why? My 7 years of IT career is probably not long enough to find a suitable answer for this 'why'.

First time I was screaming out of anger while looking at code.
I'm doing a group project in my university.
We are developing a indoor navigation Android app.
And a team mate of mine just merged this…

/*Method for help-feature.
Sets all the TouchEvents that are at least 400 ms long. This is made for all the relevant buttons or editTexts, which are seen on the mapView.
The case for mapView is needed because otherwise the other buttons, etc. wont work properly.*/

public void setButtonsForHelpDialog(){
View v = mapView;
switch (v.getId()) {
case R.id.mapview:
mapView.setOnTouchListener(…);
case R.id.buttonUp:
buttonOn.setOnTouchListener(…);
case R.id.buttonDown:
buttonDown.setOnTouchListener(…);
…
case R.id.description:
description.setOnTouchListener(…);
}}

The code is really aligned like this - no breaks. And it's even worse. There are if statements like if("constantly false var" == true). Which is highlighted by Android Studio.
This is done in a own class. The views are set via public member variables of this new class. The constant vars were added in the actual class holding the buttons and also stuff like this useless method
public void getDoStuff() {
doStuff()
}
And I could continue like this.

I never saw code this bad…
I can't even find words for it :/

TL;DR:
JuniorDev ignores every advice, writes bad code and complains about other people not working because he does not see their result because he looks at the wrong places.

Okay, so I am really fed up right now.
We have this Junior Dev, who is now with us for circa 8 months, so ca. a year less than me. Our first job for both of us.
He is mostly doing stuff nobody in the team cares about because he is doing his own projects.

But now there's a project where we need to work with him. He got a small part and did implement that. Then parts of the main project got changed and he included stuff which was not there anymore. It was like this for weeks until someone needed to tell him to fix it.
His code is a huge mess (confirmed by senior dev and all the other people working at the project).

Another colleague and me mostly did (mostly) pair programming the past 1-2 weeks because we were fixing and improving (adding functionality) libraries which we are going to use in the project. Furthermore we discussed the overall structure and each of us built some proof-of-concept applications to check if some techniques would work like we planned it.
So in short: We did a lot of preparation to have the project cleaner and faster done in the next few weeks/months and to have our code base updated for the future. Plus there were a few things about technical problems which we need to solve which was already done in that time.
Side note: All of this was done not in the repository of the main project but of side projects, test projects and libraries.

Now it seems that this idiot complained at another coworker (in our team but another project) that we were sitting there for 2 weeks, just talking and that we made no progress in the project as we did not really commit much to the repository.
Side note: My colleague and me are talking in another language when working together and nobody else joins, as we have the same mother tongue, but we switch to the team language as soon as somebody joins, so that other colleague did not even know what we were talking about the whole day.

So, we are nearly the same level experience wise (the other colleague I work with has just one year more professional experience than me) and his work is confirmed to be a mess, ugly and totally bad structured, also not documented. Whereas our code is, at least most of it, there is always space for improvement, clean, readable and re-useable (confirmed by senior and other team members as well).
And this idiot who could implement his (far smaller part) so fast because he does not care about structure or any style convention, pattern or anything complains about us not doing our work.

I just hope, that after this project, I don't have to work with him again soon.
He is also one of those people who think that they know everything because he studied computer science (as everybody in the team, by the way). So he listens to nothing anybody explains to him, not even the senior. You have to explain everything multiple times (which is fine in general) and at some points he just says that he understood, although you can clearly see that he didn't really understand but just wants to go on coding his stuff.
So you explain him stuff and also explain why something does not work or is not a good thing, he just says "yes, okay", changes something completely different and moves on like he used to.

How do you cope with something like this?

Recently was in a recruitment hackathon for leading technology company.
So, to test ppls networking, team building skill they grouped ppl into a team.
I was teamed up with noobs, and had very bad experience.
One guy in the team was arguing to use PHP for developing a web app.
Me : What PHP framework are u good at!?
He: what is framework !?
Me : like laravel etc..
He: no I meant we use plain PHP!

Me (mind voice) : go fuck yourself, I am bailing out , I Do not need the job

Me : It's ohk we only know NodeJs , so, gave a wierd smile

He was still arguing ,but I gave 0 f***
This is considered as a fight!?
Yeah not the worst though
Apparently the recruitment ppl liked him a lot in my team!

So I tell my coworker how ticking noises of clocks can annoy me really bad. It is an OCD thing where I will not notice a clock, then I notice the ticking and it annoys the hell out of me.

He leaves the room after a while after turning on a fucking youtube video with 11 hours of ticking clock.

I am like, "You fucker..."

Then another guy we work with comes into the office and pretends like he is wondering what the ticking noise is.

I said, "Yeah right, he sent you in here to ask about didn't he?!" He was like "maybe..."

Anyway, that must mean I am part of the team now. They are screwing with me. All in good fun.

This happened yesterday during 1-2-1 meeting

My dear teamleader telling me.

"You're just a stupid consultant"

Well, this 'stupid consultant' has had enough of your bullshit and will look for future endeavors elsewhere.

You are free to consider your options and make the bad decisions, dear team 'leader'.

Cry at the sheer amount of work 'your' project really entails and I will revel in your failure

I'm done with this guy.

Team leaders should be ousted if they fail their team members and the projects they are responsible for.

Program manager who handles scrum of scrums asked our scrum master to slow down. Our velocity and quality is making other teams look bad...
The problem is, no one from other team wants to learn anything from us on automation/cicd. They are good even though manual.

Not sure what to do. Biz is happy with us...

Bad managers, rude clients and annoying colleagues...

A lot of the stories here I read have at least any of the words listed above. My advice to most of you guys is: LEAVE.

And do it NOW.

The thing is, most of the stuff you're complaining about won't change. And you will be stuck there longer than you want to be and/or notice, trust me i've been there.

Especially the rude client part is where I've had lots of experience in, you have to search for a company which will abstract that layer for you. If you're on here most likely you're a developer and not everybody is a team lead. So why the F in hell are you even in conversations about budget and/or are you doing the most of the talking in the retrospective? If your project manager is ANY good he is doing that all for you.
There is so much to choose from (my experience in western countries) so please dont be stuck in a dead end job. Or start freelancing or whatever..

So do you have any co-workers or teammates who horde tasks and don't share knowledge? I hate those kind of people. Everytime I bring it in team's retrospective and that one asshole remains quite during the whole meeting, agrees to everything and continues to horde tasks again in the future. That affects the team performance and causes to form a single point of failure and recovery which is bad when working in a team. Share your experiences.

It would be great if CS students graduated and emoloyers could plug them in anywhere knowing that they can do their job without anymore training.

There for I think students sould have full on collaboration with high risk companies. Deadlines with serious consequences if they aren't met (i.e bad reviews on your profile). Computer science and programming really needs deep thought and concentration. Being able to work in a team to deal with issues as fast as possible.

These days you don't need to know a lot of theory to get started. Knowing it all helps, but being able to figure it out and then finding beter ways to slove the issues as you progress through becoming a master in your field really burns the knowledge and skill into your being.

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.

Issue in production. Multi billion dollar enterprise. Complex landscape. We sort of make things.

Turns out there is a single point of failure at a specific integration point. Kind of a lot stopped. When I reached out to the people knowing anything about it and I raised the issue that maybe we should make a slight change in how we do things they just brushed it off. Like it was nothing… 😬

No data was lost but everything was delayed for many hours. The _truth_ varied in different parts of the ecosystem causing potential wrong or suboptimal decisions to be taken.

When I asked why this LOS was not detected they told be they have no means of detecting it. 😬

I’m like, yeah, it’s 2023, we’re going to land on Mars and you can bet your ass we can detect it and you are just LAZY DEVELOPERS!

Anyway, I escalated (nicely) and they are now implementing a (more) resilient system and we’re helping the team detecting THEIR LOS in minutes instead of downstream services hours later (they are bad also but it’s not their fault!)

Stay safe!

Was on my first internship, told to analyse and prepare stuff for the Android dev to build an application for a big client. Did it before the end of the internship and team was satisfied with my job.

Because the Android dev had already lot of works on other stuff they let me start the development of the app.

The end of my internship is coming, the app is not finished but the team agreed that my work is not bad and that I should continue to work on it.

I finally get hired to finish the app, when we first publish it 95% of the code was mine and the boss started to stress because he let an intern (that became an employee) build the application from the ground. But the application got quickly its 4.5 stars on the playstore and more than 10.000 downloads.

I quit the job a few time after the publication of the app but I feel proud and happy that this team let me work on one of the biggest project they had as I was only an intern without any professional experience.

This is not "badass" but this is my first and best experience in the professional world !

I feel really bad for the guy I'm currently working with. I have until roughly the end of August to upskill him in every aspect of 3 different iOS apps because once I move to a new project he will be the entire maintenance team for those apps. Feel like he is getting shafted so badly. The whole process has been poorly managed. The managers don't care how well I train him as long as it doesn't take too many man-days. And they are expecting that they can still pull me back in to help if he gets stuck even after I've moved. Starting to feel like I'm being taken for granted. Can't wait to get off this horrible project.

I don't know what you did yesterday, but i did make my company throw away 2 months of progress.
It all started in the beginning, since that i've made numerous complaints about the workflow or code and how to improve it. I've been told off every time, and every time i either told the boss who agreed in the end or wrote code to prove myself. Everything was a hassle and my tasks weren't better.
Team lead: you'll do X now, please do that by making Y.
Me: but Y is insecure, we should do Z.
Team lead: please do Y
Later it turns out Y is impossible and we do Z in the end...
Team lead: please do W now
Me, a few days later: i've tried and their server doesn't give http cors headers, doing W in the browser is impossible
Team lead, a few days later: have you made progress on W?
Me: * tells again it's impossible and uploads code to prove it *
Team lead: * no response *

After that i had enough. Technically i still was assigned to do W, but i used my time to look over the application and list all the things wrong with it. We had everything, giant commits, commented out code, unnecessary packages, a new commit introduced packages that crashed npm install on non-macs, angularjs-packages even though we use angular, weird logic, a security bug, all css in one file even though you can use component-specific css files...

I sent that to my boss, telling him to let the backend-guys have a look at it too and we had a meeting about this. I couldn't attend but they agreed with me completely. They decided to throw away what we have already and to let one of the backend-guys supervise our team. I guess there will be another talk with the team lead, but time will tell.
It feels so good having hope to finally escape this hellish development cycle of badly defined task, bad communication and headache-inducing merges.

Does your team also tend to get stuck in the MVP Trap?

You ship a barebones version of a feature. Zero polish. That’ll be done later if it’s successful.

When the stats roll in it seems the feature got a lukewarm reception. A few users liked it, but it wasn’t a hit.

Next sprint starts and everyone asks if we should spend more time on it

The PM argues ”Why would we spend time polishing something no one uses?”

The designer argues ”Well of course no one used it, it looks like shit, we gotta spend some time polishing it!”

It becomes a chicken or the egg scenario.

Your product ends up with a bunch of half assed features. not bad enough to remove, not good enough to spend more time on.

I had to bite my tongue today when the MD and my colleague started to have a conversation about remote working "not working". It doesn't ******* work if you sit at your mom's kitchen table, cramped around "the team" while all using laptops without additional monitors.... yeah sure, my 3 monitors, large desk, peace and quiet and the ability to go to the bathroom without a security card "doesn't work" and is such a bad environment to get stuff done. ARGGGGG

Im now working as a fulltime dev for 3 years. I do programming since im 9 and now that I collected some experience, I have to to say, its horrible. Seriously. What the fuck is wrong with german internship companys? Letting me do 3 years of FUCKING CRYSTAL REPORTS. IN A DEVELOPMENT TEAM THAT CONSISTS OF A TEAM LEAD THAT ACTUALLY HAS TO LEARN SHIT LIKE PROPER OOP AND ASYNC/AWAIT FROM ME. THEY EVEN ASKED ME IF I CAN DROP OF MY HOBBY PROJECTS TO WORK ON SAMPLES THAT THEY CAN LEARN FROM! NO! FUCK! JUST BECAUSE THESE DOUCHBAGS ARE TOO LAZY TO FUCKING LEARN TECHNOLOGY THEY SHOULD BE PASSIONATE ABOUT IN THEIR FREE TIME, IM NOT MAKING IT MY JOB TO FREAKING SHOW THEM THAT HAVING A STATIC CLASS CONTAINING ALL MODELS EVER EXISTED IN THE APP IS A BAD THING! SERIOUSLY, THERES ONLY ONE INSTANCE OF EVERY MODEL WE HAVE! AND THEN THEY BLAME SQL SERVER FOR RACE CONDITIONS WHEN TRYING ASYNC!!!! WHAT THE FUCK!! AND STILL, IF I TELL THEM WHATS WRONG, IM AN IDIOT BECAUSE IM A JUNIOR! Please tell me that i didnt waste 10 years of my life dedicating to such bullshit. Will that change? Is it company specific?

My lead loves to over engineer crap and waste weeks building complicated solutions.

And then during retro when a team member has the stones to say we should've thought about it a little more or used the input of some other teammates, he shuts them down by saying that more input would've been bad for the design. I can see where he's coming from, but he always seems to have an excuse for us. Why can't he just be more transparent and clear with us? If he has a problem, just say it. That's what retros are for.

Oh and then he takes a shot at me saying that we shouldn't have built a UI in tandem with it. I didn't even recommend a UI for the thing. All I said was that if we ever have a UI, we should consider a database setup that assists both the server and UI. But nooo, he's stuck with this "server design" approach. Everything has to be built to make it easier for the server.

I still don't understand why anyone would have their server logic influence the design. Especially the database. I just seems too targeted. It just creates these nasty denormalized tables.

Ugh... Our team is getting dragged around by this arrogant and silly man.

For about 1.5 years on and off, we've been developing a system to rate tickets/requests sent to our team. We wrote it in Angular, and it turned into this feature-rich gorgeous application with custom-built graphical statistic tracking, in-app social networking capabilities, robust user profiles, etc.

Eventually, we no longer had time to work on it along with all the other applications we're developing. So we passed ownership of the app over to a couple of other developers on our team. You'd think that they'd just work off what we already built and keep the robust environment we created for them. But nope, instead of keeping everything we already built, they scrapped it all and started from scratch using React instead of Angular, and removed all of those robust features and turned the app into a shell of its former self. No more statistic tracking, no more social networking capabilities, no more fancy user profiles. Just a single page with a number representing how many "Good" tickets you've sent to us, and how many "Bad" tickets you've sent.

1.5 years and hundreds of hours worth of work, all gone and replaced with the most rudimentary basic React app ever.

I have been keeping this inside for long time and I need to rant it somewhere and hear your opinion.

So I'm working as a Team Lead Developer at a small company remotely based in Netherlands, I've been working there for about 8 years now and I am the only developer left, so the company basically consists of me and the owner of the company which is also the project manager.

As my role title says I am responsible for many things, I maintain multiple environments:
- Maintain Web Version of the App
- Maintain A Cordova app for Android, iOS and Windows
- Working with pure JavaScript (ES5..) and CSS
- Development and maintenance of Cordova Plugins for the project in Java/Swift
- Trying to keep things stable while trying very hard to transit ancient code to new standards
- Testing, Testing, Testing
- Keeping App Stable without a single Testing Unit (sadly yes..)
- Just pure JavaScript no framework apart from JQuery and Bootstrap for which I strongly insist to be removed and its being slowly done.

On the backend side I maintain:
- A Symfony project
- MySQL
- RabbitMQ
- AWS
- FCM
- Stripe/In-App Purchases
- Other things I can't disclose

I can't disclose the nature of the app but the app is quite rich in features and complex its limited to certain regions only but so far we have around 100K monthly users on all platforms, it involves too much work especially because I am the only developer there so when I am implementing some feature on one side I also have to think about the other side so I need to constantly switch between different languages and environments when working, not to mention I have to maintain a very old code and the Project Owner doesn't want to transit to some more modern technologies as that would be expensive.

The last raise I had was 3 years ago, and so far he hasn't invested in anything to improve my development process, as an example we have an iOS version of the app in Cordova which of course involves building , testing, working on both frontend and native side and etc., and I am working in a somewhat slow virtual machine of Monterey with just 16 GB of RAM which consumed days of my free time just to get it working and when I'm running it I need to close other apps, keep in mind I am working there for about 8 years.

The last time I needed to reconfigure my work computer and setup the virtual machine it costed me 4 days of small unpaid holiday I had taken for Christmas, just because he doesn't have the enough money to provide me with a decent MacBook laptop. I do get that its not a large company, but still I am the only developer there its not like he needs to keep paying 10 Developers.

Also:
- I don't get paid vacation
- I don't have paid holiday
- I don't have paid sick days
- My Monthly salary is 2000 euro GROSS (before taxes) which hourly translates to 12 Euro per hour
- I have to pay taxes by myself
- Working remotely has its own expenses: food, heating, electricity, internet and etc.
- There are few other technical stuff I am responsible of which I can't disclose in this post.

I don't know if I'm overacting and asking a lot, but summarizing everything the only expense he has regarding me is the 2000 euro he sends me on which of course he doesn't need to pay taxes as I'm doing that in my country.

Apart from that just in case I spend my free time in keeping myself updated with other tech which I would say I fairly experienced with like: Flutter/Dart, ES6, NodeJS, Express, GraphQL, MongoDB, WebSockets, ReactJS, React Native just to name few, some I know better than the other and still I feel like I don't get what I deserve.

What do you think, do I ask a lot or should I start searching for other job?

! related

So there is this girl in my office from different team. We only talked over emails couple of times. I never got courage to go and talk to her in person. Sometimes I found her looking at me (** i guess**), sometimes she catches me looking at her. Smiles gets exchanged and that's it.

Didn't see her for 2-3 days. Checked in portal, turns out she left company. I'm feeling super bad right now. I can't focus on anything since this afternoon. I know this is not the place to share it, but I don't have anywhere else to share this...

Faaaakkkkkkkkk
Faaaccccckkkkkkkkkkkkkk

I could've tried...

My shyness kills me more than anything else in this world.😞

I explained last week in great detail to a new team member of a dev team (yeah hire or fire part 2) why it is an extremely bad idea to do proactive error handling somewhere down in the stack...

Example
Controller -> Business/Application Logic -> Infrastructure Layer

(shortened)

Now in the infrastructure layer we have a cache that caches an http rest call to another service.

One should not implement retry or some other proactive error handling down in the cache / infra stack, instead propagate the error to the upper layer(s) like application / business logic.
Let them decide what's the course of action, so ...
1) no error is swallowed
2) no unintended side effects like latency spikes / hickups due to retries or similar techniques happens
3) one can actually understand what the services do - behaviour should either be configured explicitly or passed down as a programmed choice from the upper layer... Not randomly implemented in some services.

The explanation was long and I thought ... Well let's call the recruit like the Gremlin he is... Gizmo got the message.

Today Gizmo presented a new solution.

The solution was to log and swallow all exceptions and just return null everywhere.

Yay... Gizmo. You won the Oscar for bad choices TM.

Thx for not asking whether that brain fart made any sense and wasting 5 days with implementing the worst of it all.

Colleagues cannot seem to grasp that allowing a user to manually update a field via an Api, that only business process should update is a bad idea.

The entire team of around 10 'software developers' cannot grasp that just because the frontend website won't set it doesn't mean its secure. I have tried many times now...

Just an example honestly... Our project follows a concrete repository pattern using no interfaces or inheritance, returning anaemic domain models (they are just poco) that then get mapped into 'view models' (its an api). The domain models exist to map to 'view models' and have no methods on them. This is in response to my comments over the last 2 years about returning database models as domain transfer objects and blindly trusting all Posts of those models being a bad idea due to virtual fields in Ef.

Every comment on a pull request triggers hours of conversation about why we should make a change vs its already done so just leave it. Even if its a 5 minute change.

After 2 years the entire team still can't grasp restful design, or what the point is.

Just a tiny selection of constant incompetence that over the years has slowly warn me down to not really caring.

I can't really understand anymore if this is normal.

I'M A SENIOR DEVELOPER NOT A BUSINESS ANALYST...

IF YOU GIVE ME SOME CRAPPY LEGACY CODE THAT SOMEONE RANDOMLY DECIDED TO USE, THE ONLY WAY I CAN UNDERSTAND IT IS BY RUNNING IT AND REVERSE ENGINEERING THE "BUSINESS LOGIC".

ADD THAT WITH BAD INPUTS... THE ONLY THING YOUR DOING IS WASTING MY TIME..

JUST BURN THE WHOLE THING AND GIVE ME THE REQUIREMENTS OF WHAT YOU ACTUALLY WANT....

It feels like I've been fucking a pig all week...

Oh and now my team agrees and will look to get the actual requirements from the business...

This feels like a hallow victory.... As that was the first thing I told them to do....

This week I got a promotion after being a junior for a year. Boss said Im a medior now and my monthly salary raised with 400 euro per month

Feels good but what feels bad is that a coworker of mine which has been contracted recently without any development experience is still making 400 more a month..

The thing is that this "developer" wanted to become a Java developer, he has been given time during work to study Java and in the meanwhile join the team thats working on a saas product (my team, where im lead dev)

During the 3 months ive counted a maximum of 10 commits and i was done with him which conflicted in a very bad vibe at the office.

During a refinement I asked if everybody understood what needs to be done, no questions asked. Next day when i was working at a clients office on another project 9 am i git a Skype message "Can you tell me What to do? I have no idea" where I replied "you should have asked me yesterday, i am not going to help you unless u come up with a question that makes sense.. what have u tried urself?".. Well then he got mad and stopped doing what he was trying to do.

The next morning i talked with him and we agreed to have a 1hour session to talk him through the user story. When we were done, he said that he understood and was going to work on it.

Next day I check, no commits, so during stand up i confronted hmj with this and he admitted hes been lacking and wanted to talk with the boss and me after stand up.

Well he admitted things were going to fast to keep up for him because he is doing some sysadmin stuff aswell.. the plan of becoming a Java dev was now history and he left the team..

Now he is just doing some sysadmin stuff but its been 3 days that hes been saying today ill setup a tomcat on the servers and give you SSH acces to deploy your .war files, today I finally gained access but he couldnt figure out how to move the war to the webapps folder.. And i wasnt allowed to transfer it to there..

Not dev related
Worst Team work fail...
I was hired to a Steel werehouse to join a team of two...
One month latter I was working alone while my coworkers spent their time on the bathroom watching manga and playing rpgs on their android phones...
One year latter I was fired, got Hurt because of the heavy weight (Steel weights a lot) and because I was a temp they just fired me (toke me a year to recover)
Two months latter both my coworkers were fired.. Guess that without me the work didn't do itself...
Wish I knew back them they couldn't fire me while I was Hurt...
Oh and I didn't complain about my coworkers because I don't like to talk bad about others...
No matter.... Got a better job latter on and the company lost clients... So fuck you smart ass engineer....

As a person from low-paying country, how do I reconcile with the fact that for the same work, and the same 8 hours, I get 1/3 of what a person in Germany does? In my previous team (same company), one of my teammates was from Germany. The same team, the same work, but he happened to earn a lot more.

This bothers me a lot sometimes. I have seen people requesting to be transferred to another country, and being denied, presumably because of the salary difference. Then, the person leaves, and someone in Australia gets hired. So, rather than moving a veteran person of whom you know fits your company culture to a higher-paying country, you let him go and hire a newbie in an equally-expensive country? What the fuckity fuck?

And to my friends from high-paying countries, especially managers: you don't have to feel bad, but have some common decency. If you come to my country, do not say "oh gosh, everything here is so cheap," or "the dinner for the whole team costs less than buying my family of four a dinner back home." That's offensive as fuck. If that's the case, fucking give me a raise you cheap fuck!

Just needing somewhere to let some steam off

Tl;dr: perfectly fine commandline system is replaced by bad ui system because it has a ui.

For a while now we have had a development k8s cluster for the dev team. Using helm as composing framework everything worked perfectly via the console. Being able to quickly test new code to existing apps, and even deploy new (and even third party apps) on a simar-to-production system was a breeze.

Introducing Rancher

We are now required to commit every helm configuration change to a git repository and merge to master (master is used on dev and prod) before even being able to test the the configuration change, as the package is not created until after the merge is completed.

Rolling out new tags now also requires a VCS change as you have to point to the docker image version within a file.

As we now have this awesome new system, the ops didn't see a reason to give us access to kubectl. So the dev team is stuck with a ui, but this should give the dev team more flexibility and independence, and more people from the team can roll releases.

Back to reality: since the new system we have hogged more time from ops than we have done in a while, everyone needs to learn a new unintuitive tool, and the funny thing, only a few people can actually accept VCS changes as it impacts dev and prod. So the entire reason this was done, so it is reachable to more people, is out the window.

I proposed agile training to my company.
I choose a well known coach around here, with good references.

First 3 days were great. After a month he came back for another session and check progress.

This time, he literally fell asleep during the workshop. Several times. He would ask questions, sit down and quietly fall asleep while waiting for our answers.

We were astonished and embarrassed.

He apparently had a very hard working period and could not cope with traveling and working so much. He apologized some day afterwards and didn't charge us for the day.

He never came back. The team didn't take it very well and my reputation was compromised, as well as trust in the methodology I think.

I kept saying that everybody can have a bad day, but it was probably just to defend myself and my fucking stupid idea of changing the world.

A real fucking shame. Still I can't believe when I remember this.

When you get into good company but end up in bad team. Worst thing to happen. I want to quit. But as of now I don't have any option.

I am way too triggered. Any one tries messing with me anymore at work, I won't be able to stop myself. I am gonna shout....take out all my anger. To hell with you assholez! I don't care if you get me kicked out of team or job! I can't take it anymore. FUCKING IDIOTS!!!!!!

Managers at my jobs for the most part leave me be. Though I often have no clue whether I'm doing OK. I guess no news is good news right?

My worst experience isn't that bad. At one place, I was the only tester working on things coming from 20-30 devs. After about a year+, the company finally hired more testers, but it was still only 3 of us.

We were in the final stages of releasing a build to prod. It was going smoothly, or so we thought. At the last minute, I found a buried bug that was a showstopper.

A lot of hatred on me that day, that once it was fixed, and the release was finally deployed, I just shut off my laptop and left. I took all the blame because I was the one who found it rather than blaming the team as a whole for not finding it earlier. Oh well. Stuff happens.

Let's knock on wood that I don't run into worse higher up stories.

Manager: Last release was really bad, it was late, there was confusion and a lot of frustration on the team, we need to do better. Any suggestions?

Me: Have you tired not being shit?

Me: ... I feel it would help a lot.

Alright, server got hacked a week ago. Bad enough on its own but okay, perfect time to change the server infrastucture completely instead of doing it later this year. Since Saturday we are working on setting everything up (game server, apache, etc.pp.) while making sure to configure everything correctly to be safer this time.

We are finally at the point where we could go back online. And what happens? One team member _now_ (6 days after the hack) suggests that it might be a good idea to format the hacked server and configure just what we need to patch the clients with it.

Great fucking idea, why didn't you have that idea 5 days earlier?! There was more than enough time already to format the old server and configure it. Another day delay, yay. X_X

Aaah, ranting really helps in those situations. Oh and Hi, I'm new here. Nice place, I like it. ^_^

This post is kinda late. For those who haven't read my previous rants, a marketing coworker bragged about a feature that we hadn't yet finished. (I'm thinking that they perhaps did it to put extra pressure on the dev team 🤔.) Of course it backfired pretty bad, because this feature was a plug-in for another service, and even though the dev team was on time with the feature, the other service we were writing a plug-in for took _sooo_ long to approve of our code, and it made this marketing guy look so bad in front of these clients because the feature was a few weeks late.

A part of the new feature was that some of their data would be synced with this service. These customers were so important that we couldn't afford to disappoint them, and the solution was... *drumroll please* ... that this marketing guy would have to manually copy the customer's data from the service into our platform to make the customer think this feature is ready. Row by row. I'm hearing it takes about one hour of their day 🤣

I mean I'm good friends with the guy but... they kinda deserved it

I'm very bad at reading someones code. For example when someone on uni asks me to help him with code I just write it from scratch, I can't find the mistake or even understand thoughts of this person. I'm afraid that when I'm going to work in team I'll be useless. Can I even do something with this?

Worst Hackathon Experience ever!
Had been to SAP for a hackathon last year. Built a complete solution for our challenge. Due to no sleep and 48 hours of non stop coding, my team mate who was supposed to present our solution screwed it up in the last minute. Now we blame ourselves for losing because of our bad presentation.

- my (non-dev) supervisor at my job
- no documentation
- no source control
- people working in the same team with completely different programming/domain knowledge levels, but also very different ways of being
- bad within-project communication

Luckily not all of them are about my job. We do use source control.

In my study program the is this last big course everyone is looking forward to because it combines everything we've learned so far. It's a group project where you build a middle-scale-ish application using ask kind of project management like scrum & co.

We had a good idea and am enthusiastic team.

Well, long story short: our assigned teacher was just bad. He barely listened to our proposal, had no fucking idea who we were at the second meeting and he FUCKING FELL ASLEEP in the last meeting. No feedback. No comments on our progress. Nothing. We could've work with the cleaning lady, she probably would've more feedback for us!

Have you ever encountered a situation like this before?

You worked in a team, made many adjustments in the codebase, and all the changes you've made are the best practice (after some research or asking the community).

But the team leader decided to go with the "messy" version of the code and the team leader does adjust the principle of "bad code" in favour of your coworker, just because he/she is a friend of the team leader.

So, whatever you adjust or contribute is simply nullified but any adjustments made by your coworker are considered "new updates".

PR by my team leader:
"OH NO! This method is not inline. This will slow our program by 1 ns!!! Fix that immediately!!"
FYI
Our program computes stuff for dozen of minutes, because of his short sight and bad design from day 1...

My project manager decided to go full micromanager today. So members of the team have been emailing our manager and the PMs manager to explain why what he's doing is bad both for our deliverables and our moral

Our agile scrum team has finally shattered into two parts.
On the one hand we have front-end guys.
On the other hand we have backend- /dev-ops guys.

The FE guys don't care about the BE guys business.
They don't join pairworking and only noticing things that went bad, when a Backend guy has caused it.
Goodbye fullstack dev-ops team...

I really dislike that arrogant basterds.

Frontend Hobo-Bitches...!

tl;dr; A co-worker and I had an disagreement on our package structure. They went straight to our team lead instead of trying to solve this in our team and by that letting me do my job.

Do I overreact by assuming that this was malicious?

A co-worker asked me to do their code review today. There was nothing really wrong there, mainly something a bad generator created.

However at one point we had a disagreement about the naming structure of the packages. We both agreed to disagree, so I thought we could bring that up in the next daily, as it's something the team should agree on.

Shortly after that, they told me on Slack, that they relayed the matter to our team lead to get their opinion. Wtf.

My role in the team is that of a technical lead. Even though I like to discuss such topics in the team and not straight up dictate decisions.

By going directly to our team leader, they basically circumvented the whole team. This really rubs me wrong the way.

Maybe I'm just overreacting?

I work remotely from the rest of my team and I just came back from a 1 week vacation. Logged in this morning and no one else was online...

My first thought was WTF happened... did something blow up do bad they all gelot fired???

Turns out today is a holiday for them. So now I've a whole day of peace and quiet to figure out what the hell in supposed to be doing again.

---Startup Rant---

Being a senior developer doesn't grant the privilege to join a team and starting a drama out loud that everything is bad and you don't like it.

First, if everything is perfect there is no need to hire you.
Second, think about the value that you can bring to the team instead of making them feel bad, how can you prepare an improvement plan and start to learn the factors and reasons behind those decisions.

What's funny, it that the same guy after a couple of months starts introducing bad fixes and he says it's ok for the moment, it's not good but it's okayish, I wish I had a time machine for those developers!

Bad case of schadenfreude the biggest asshole on the dev team is having issues with his code merge! Someone merged 2 mins before him...lol. This is why you used the command line not the GUI!

So me and some colleagues joined a hackathon. We already agreed on our project architecture, UI design, and features to build and showcase. Halfway through development new features kept getting added without my inputs, I said to myself it's ok maybe they're just small insertions. But nope, they kept breaking my CSS and UI design and kept causing merge issues on our repo because, well, no one could seem to agree on the project scope. The last straw was, with a couple of hours left, someone went and added new screens and changed the application flow entirely, which entailed some rather nasty rework of my code to fix. Fuck that, I decided to just stop and let them sort the mess.

When it was our turn to present our project, the fucking cunts assumed I would do all the talking - even if they never sent over the slides they put together. Why the fuck am I going to present something drastically different from the initial, agreed-upon scope? I told them to do it themselves and I remained silent throughout the entire debacle.

Of course, we lost. But I wasn't surprised. The guys who presented kept on contradicting each other and were not unified in their vision. I'm never teaming up with them ever again. Fucking asshole douchebag fucks.

Almost everyone here has shared a story about their boss whether bad or good at some point in their time on devRant. Here's mine.

I started out in my current company around mid third year in college. I have been doing freelance for about six years which is why I think my boss hired me.

I couldn't be more thankful for these last 10 months in this company, every experience has been epic. Since my boss knows my future plans and how I hope to build my own company some day, my boss has been mentoring me ever since I've knew him.

Last week he even offered to take me along with him and certain other members of our team to the US to meet with a client of ours. (I have nothing to do with the client, he just offered the trip for the heck of it.)

I can't wait to see where my time with this company will lead me.

Why do game studios force social/multiplayer in single player games?
Single player sandbox? How about we make it a multiplayer co-op?
Just fine 1 on 1 brawl? Hey how about you find a team and tag team? No? Too bad fuck you, no points to you for a whole fucking season.

Ugh.

I'm a developer, member of the A-Team. Actually I'm the leader of the A-Team.

We are incredibly skilled. Our problem solving capabilities is amazing, almost 100 times more effective than the rest of people. We produce code 10 times faster and better than anybody else. We have THE knowledge.

We can save the company in case of emergency.

For that reason, it's of paramount importance to nurture and protect the A-Team.

- When there is a bug, A-Team will not correct it. Because, if A-Team is busy, and bad shit happens, the company could be destroyed and we couldn't help

- When there is some important features to develop with a deadline, A-Team will not participate: A-Team must stay alert and ready in case of emergency

- If huge catastrophe happens and long hours, night and weekend are needed to fix it, A-Team will not risk burning the A-Team because it's the only high skilled team we have. The company cannot afford to have an A-Team member exhausted, underpaid, unhappy leaving or sleepy. Therefore, the company will sacrifice other less important people.

A-Team is company biggest asset and must be protected in any kind of situations.
The company should also pay training for them in order to increase their skills and make them unreplaceable.

These are my conditions. I'm the leader of the A-Team. You can't afford to loose me.

I am surrounded by incompetent fucking idiots, from the team lead that does a half arsed job at coding and then wonders why nothing further down the chain works to whole component teams that seem to be lagging so far behind they don't even know what the current code base looks like.

And who's in the middle of it all running around fixing all the problems these fucktards create, why yes it's me.

I would leave to let it implode and see what they'd do but I already know, they'd leave it till I got back so I could fix it all for them.

Feel like going around with a rolled up news paper and whacking each of them on the back of the head while screaming "no, bad code monkey, bad, fix your own bugs"

I hate being the go to fix it guy sometimes.

Design team constantly needs help fixing bad commits and merges. (can't use git after using it for 3 years...) And boss wants to know why the ticket is falling behind.
After explaining I'm pretty much told that assisting other teammates is part of the job but I'm being paid to write code and need to stay late.... this is while I'm hitting a 10 hour workday already (skipping lunch). And btw, we aren't doing reviews this year because the business made some bad decisions recently and raises aren't in the budget.

Guys need your opinion. How bad of a thing is it if I change my job in just a year. Stuck in a toxic team. I’m a Class of 2020 undergrad, joined my current firm for the’brand’ but my experience and expectations have been polar opposites. I’m not able to put myself 100% behind to look for other jobs as I keep worrying that switching this early would hurt my profile long term.

Just wanted to hear what yall think.

So, I'm the engineering leader of a startup. This year, the company hired new directors and with that a new CPO. We've been using Google Workspace and have all our infrastructure on GCP. We never had any trouble with Google products. We also have Google SSO configured in almost every tool out there.

Yesterday, the new CPO, sent me a request to change "just some dns" on the domain. Those "just some dns" were Microsoft 365 mx, cname and text records.

I asked him if he was planning to switch to MS.

He answered: "yes! The team (a new team of marketing) wants to use PowerPoint and Teams".

I don't know you guys, but I hate MS products. They're just bad.

So, yes, it seems that now I'm gonna waste my time switching and configuring everything with MS just because they don't know other tools that are way better than any MS product!

I tried to convince him, this wasn't a good move, but it seems my opinion equals zero at this company.

I just hate this type of product managers that always wants to reinvent the wheel to let others see that they are doing something important when they're not.

Also hate when managers make decisions without ever consulting the people that will be affected by those decisions... But I guess that's how it works in this world...