Le monday morning after a commit on sunday evening...

PM: BLAAAH!!!! Your commit broke the site, nothing is working!!!!!!
Me: What? All of tests passed (coverage 95%), no issues were found.
PM: NOO!!!! Site is broken, we can't use it no more!!!
Me: Ok, what's the problem?
PM: I've tried to enter -10021 into this field on that page and it gived me an error.
Me: Ok? So, that single page is broken?
PM: No, whole site!!!! This is important
Me: Sure... Let me take a look

* PM tried to enter a negative value into an unsigned field that I've mutated yesterday after checking LIVE database if there was no records with negative value. Reason: we've hit an int limit and there was no chance that the value would be negative. Validation? Well, yes.... Except that page was added by him this morning without even checking everything else *

Me: Here, this is the issue, *gives explanation*
PM: Well.... You shouldn't do this. This is unacceptable. You must never leave int fields without negative values. Didn't they teach you in school that integers can be negative?!
Me: What? *consufed as hell*
PM: *More morale... blah blah blah....* Revert it back!
Me: Ok but if anything else breaks, copy of this slack conversation will be kept.
PM: Don't care! Fix it!
Me: * Reverts the fix, saves chat copy * - Done.
PM: Great.

* 5 wild minutes later *
PM: BLAAAH!!!! Site is down, service is not working, what have you done?
Me: Reverted the change needed for it to work. Todays schedule is full with other important tasks. * pastes a screenshot as a proof that he asked me to do this *
PM: FIX IT NOW! Apply your fix.
Me: You're the PM. - Done.
PM: Great, now I'll fix my code. You should be more careful next time.
Me: * YOU DENSE MATHA...KER * Sure.

How's your morning going? :)

Great phrase from my PM (sarcasm):
"Don't waste time with maintainable code, we have a lot of bugs to solve"

My dad called me up at 11:30 PM telling me that his computer wasn't booting. I drive over to see what was going on. I notice immediately that the motherboard light is a solid amber light.

Me: "The motherboard is amber, that means it's failing to POST".

Dad: "How soon can we fix it? I need to run my Ebay business."

Me: "A week probably. You have a laptop that works can you use that?"

Dad: "It doesn't work great with Windows, it's not a very powerful compu"

Me: "You're going to use Linux dad. Welcome to Linux."

I want Gordon Ramsey to start a IT program in the same fashion as Hotel Hell and Kitchen Nightmares

He'll sit at a desk with a laptop, examining code as if he's eating food, venting frustrations and screaming insults out loud

Then he'll have a talk with the team and see how they work on a day

After that he'll go into the freezer (server room) and scream at mold and cockroaches

Then comes the intervention where we discover that the PM is still grieving about the death of his original programming language and the team loves him but thinks he should move on

The next day the development studio is modernised and has a candy bar, tennis table and everyone is forced to use linux on their new macbooks

Then we experience a good day where everything is great and velocity is through the roof

Then Gordon leaves and everything is shit again

** Makes a design for a landing page, in a Single-page format. My designs are usually clean and "aerated" (breathing, uncluttered). **

** Pm comes in **
Me: Oh hey! I've finished my mockups
PM: Ah nice, let's see... ** comes to my screen **
---

PM: Not bad, but can you remove this spacing, this spacing, and this one and this one... oh and that one too?

** corrects them as she says, everything starts looking cluttered and I dislike it **

PM: Great! Can you export them in pdf?
Me: Sure.

** PM goes away **

** Proceeds to re-make the mockups more "breathing" with an evil smirk **

I'm drunk and I'll probably regret this, but here's a drunken rank of things I've learned as an engineer for the past 10 years.

The best way I've advanced my career is by changing companies.

Technology stacks don't really matter because there are like 15 basic patterns of software engineering in my field that apply. I work in data so it's not going to be the same as webdev or embedded. But all fields have about 10-20 core principles and the tech stack is just trying to make those things easier, so don't fret overit.

There's a reason why people recommend job hunting. If I'm unsatisfied at a job, it's probably time to move on.

I've made some good, lifelong friends at companies I've worked with. I don't need to make that a requirement of every place I work. I've been perfectly happy working at places where I didn't form friendships with my coworkers and I've been unhappy at places where I made some great friends.

I've learned to be honest with my manager. Not too honest, but honest enough where I can be authentic at work. What's the worse that can happen? He fire me? I'll just pick up a new job in 2 weeks.

If I'm awaken at 2am from being on-call for more than once per quarter, then something is seriously wrong and I will either fix it or quit.

pour another glass

Qualities of a good manager share a lot of qualities of a good engineer.

When I first started, I was enamored with technology and programming and computer science. I'm over it.

Good code is code that can be understood by a junior engineer. Great code can be understood by a first year CS freshman. The best code is no code at all.

The most underrated skill to learn as an engineer is how to document. Fuck, someone please teach me how to write good documentation. Seriously, if there's any recommendations, I'd seriously pay for a course (like probably a lot of money, maybe 1k for a course if it guaranteed that I could write good docs.)

Related to above, writing good proposals for changes is a great skill.

Almost every holy war out there (vim vs emacs, mac vs linux, whatever) doesn't matter... except one. See below.

The older I get, the more I appreciate dynamic languages. Fuck, I said it. Fight me.

If I ever find myself thinking I'm the smartest person in the room, it's time to leave.

I don't know why full stack webdevs are paid so poorly. No really, they should be paid like half a mil a year just base salary. Fuck they have to understand both front end AND back end AND how different browsers work AND networking AND databases AND caching AND differences between web and mobile AND omg what the fuck there's another framework out there that companies want to use? Seriously, why are webdevs paid so little.

We should hire more interns, they're awesome. Those energetic little fucks with their ideas. Even better when they can question or criticize something. I love interns.

sip

Don't meet your heroes. I paid 5k to take a course by one of my heroes. He's a brilliant man, but at the end of it I realized that he's making it up as he goes along like the rest of us.

Tech stack matters. OK I just said tech stack doesn't matter, but hear me out. If you hear Python dev vs C++ dev, you think very different things, right? That's because certain tools are really good at certain jobs. If you're not sure what you want to do, just do Java. It's a shitty programming language that's good at almost everything.

The greatest programming language ever is lisp. I should learn lisp.

For beginners, the most lucrative programming language to learn is SQL. Fuck all other languages. If you know SQL and nothing else, you can make bank. Payroll specialtist? Maybe 50k. Payroll specialist who knows SQL? 90k. Average joe with organizational skills at big corp? $40k. Average joe with organization skills AND sql? Call yourself a PM and earn $150k.

Tests are important but TDD is a damn cult.

Cushy government jobs are not what they are cracked up to be, at least for early to mid-career engineers. Sure, $120k + bennies + pension sound great, but you'll be selling your soul to work on esoteric proprietary technology. Much respect to government workers but seriously there's a reason why the median age for engineers at those places is 50+. Advice does not apply to government contractors.

Third party recruiters are leeches. However, if you find a good one, seriously develop a good relationship with them. They can help bootstrap your career. How do you know if you have a good one? If they've been a third party recruiter for more than 3 years, they're probably bad. The good ones typically become recruiters are large companies.

Options are worthless or can make you a millionaire. They're probably worthless unless the headcount of engineering is more than 100. Then maybe they are worth something within this decade.

Work from home is the tits. But lack of whiteboarding sucks.

pm: our client wants a proprietary pdf compression app.
me: Okay gimme 3 days and some sample PDFs.
pm: they won't supply any sample PDFs because they contain confidential information.
me: okay fine, I'll download some from the interwebs.

** 3 days later **

me: here is the pdf compression app. all done and works with all of about 100 PDFs we tested with.
pm: okay great I'll have the client take a look.

** half and hour later **

pm: the client said that the compression app errors out.
me: okay I'll go look at the server logs to see what's up.

** 10 seconds later **

me: what the shit is a "foxit phantompdf" file.
pm: it's the proprietary pdf format that they are using.
me: oh joy. I'll go try to find some sample files and see if I can fix it.

** 1 hour later, no sample files found **

pm: got anything?
me: *sobs obnoxiously*

Team: Finishes SudoCode.

PM: Great, now let’s convert our sudo code to python.

Team: SudoCode.py

Welcome back to practiseSafeHex's new life as a manager.

Episode 2: Why automate when you can spend all day doing it by hand

This is a particularly special episode for me, as these problems are taking up so much of my time with non-sensical bullshit, that i'm delayed with everything else. Some badly require tooling or new products. Some are just unnecessary processes or annoyances that should not need to be handled by another human. So lets jump right in, in no particular order:

- Jira ... nuff said? not quite because somehow some blue moon, planets aligning, act of god style set of circumstances lined up to allow this team to somehow make Jira worse. On one hand we have a gigantic Jira project containing 7 separate sub teams, a million different labels / epics and 4.2 million possible assignees, all making sure the loading page takes as long as possible to open. But the new country we've added support for in the app gets a separate project. So we have product, backend, mobile, design, management etc on one, and mobile-country2 on another. This delightfully means a lot of duplication and copy pasting from one to the other, for literally no reason what so ever.

- Everything on Jira is found through a label. Every time something happens, a new one is created. So I need to check for "iOS", "Android", "iOS-country2", "Android-country2", "mobile-<feature>", "mobile-<feature>-issues", "mobile-<feature>-prod-issues", "mobile-<feature>-existing-issues" and "<project>-July31" ... why July31? Because some fucking moron decided to do a round of testing, and tag all the issues with the current date (despite the fact Jira does that anyway), which somehow still gets used from time to time because nobody pays attention to what they are doing. This means creating and modifying filters on a daily basis ... after spending time trying to figure out what its not in the first one.

- One of my favourite morning rituals I like to call "Jira dumpster diving". This involves me removing all the filters and reading all the tickets. Why would I do such a thing? oh remember the 9000 labels I mentioned earlier? right well its very likely that they actually won't use any of them ... or the wrong ones ... or assign to the wrong person, so I have to go find them and fix them. If I don't, i'll get yelled at, because clearly it's my fault.

- Moving on from Jira. As some of you might have seen in your companies, if you use things like TestFlight, HockeyApp, AppCenter, BuddyBuild etc. that when you release a new app version for testing, each version comes with an automated change-log, listing ticket numbers addressed ...... yeah we don't do that. No we use this shitty service, which is effectively an FTP server and a webpage, that only allows you to host the new versions. Sending out those emails is all manual ... distribution groups?? ... whats that?

- Moving back to Jira. Can't even automate the changelog with a script, because I can't even make sense of the tickets, in order to translate that to a script.

- Moving on from Jira. Me and one of the remote testers play this great game I like to call "tag team ticketing". It's so much fun. Right heres how to play, you'll need a QA and a PM.

*QA creates a ticket, and puts nothing of any use inside it, and assigns to the PM.
*PM fires it back asking for clarification.
*QA adds in what he feels is clarification (hes wrong) and assigns it back to the PM.
*PM sends detailed instructions, with examples as to what is needed and assigns it back.
*QA adds 1 of the 3 things required and assigns it back.
*PM assigns it back saying the one thing added is from the wrong day, and reminds him about the other 2 items.
*QA adds some random piece of unrelated info to the ticket instead, forgetting about the 3 things and assigns it back.

and you just continue doing this for the whole dev / release cycle hahaha. Oh you guys have no idea how much fun it is, seriously give it a go, you'll thank me later ... or kill yourselves, each to their own.

- Moving back to Jira. I decided to take an action of creating a new project for my team (the mobile team) and set it up the way we want and just ignore everything going on around us. Use proper automation, and a kanban board. Maybe only give product a slack bot interface that won't allow them to create a ticket without what we need etc. Spent 25 minutes looking for the "create new project" button before finding the link which says I need to open a ticket with support and wait ... 5 ... fucking ... long ... painful ... unnecessary ... business days.

... Heres hoping my head continues to not have a bullet hole in it by then.

Id love to talk more, but those filters ain't gonna fix themselves. So we'll have to leave it here for today. Tune in again for another episode soon.

And remember to always practiseSafeHex

rant? rant!

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

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

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

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

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

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

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

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

So, basically i am getting desperate, and i'm also angry... and want to cry, and i feel a failure.
My biggest error in this story is "believing"

First of all, I'm a starting entrepreneur as freelancer, started of 6 months ago, back then it all seemed bright, i had my first customer, they believed me, got a second assignment for that same customer, fulfilled the task in brilliance, and was ready to move on to a bigger customer base. Here's where shit goes wrong.

Working with another office that outsources people to various (goverment) contractors, Had a meeting with them, we would cooperate very soon. This was january.

PM: "We've got a gov Dept as a customer that wants to do project XYZ and starting in february, requirements are yadiyadiyadi, you up for it?
Me:"Sure, send me the specs, and timeframe and i'll apply with my offer)"
Project is about a bit backup system migration, lots of fancy shmancy tech used, 2 datacenters setup... a big project that can take up several months...
- sends offer- received an acceptance on the offer

PM " Great, we'll start end of february"
Me: "Ok, end of february is a go then, looking forward to cooperate"

FF to near end of february, receive msg from PM: "Project XYZ delayed until half if march"
Me: "Okay... what is the delay?"
PM:"Govt bureaucracy"
Me " Ok, let's keep in touch"

Near Half of March
PM " Project delayed again".
Me: " Okay... what's the reason?"
PM: "they have decided to take a different approach, and want 3 datacenters now"
Me: "That will change the offer i made for you, can you send me the specs?"
PM: "No, because they havent decided on the techs used, expect end of march"
Me: "Okay...but once you got the specs,s end them to me"

End of March
Pm: " Hy NeatNerdPrime, we still havent got any specs yet... they still forgot to make the shopping list"
Me: "(-_-) ... I thought they already had that covered"
PM:" No, new Govt budget cuts and lots of changes, basically, they still don't know what they really want. But we're just -delayed- , not -cancelled-"
Me: "Okay... i hope we get started soon"
PM: "expect launch beginning of april"
I was not really satisfied with this explanation.... but ok

Beginning of april, at april's folls day
PM "Project delayed again"
Me: " This is a joke right?"
PM: "Sadly, no, they delayed the project since they don't really know what they actually want, we are trying to give them the proposed solution... but they still need approval, and still need to set up shopping list"
Me:"when do we start then?"
PM: " I was told 17th of april'
Me:" I really hope it gets through, i had to decline some proposals for work for months due to this, this ain't funny"
PM: "I know, i'll make up for it"

15th of april...
PM " Project delayed again"
Me right now almost losing my shit
"why this time??? I thought you said 17th of april real launch!"
PM: "they fired their PM, need to hire a new one, delayed until May/June"
Me: "I've set aside some other assignments just because you said you were going to launch at those dates... This is really pushing my limits, can you give me SOME assurances?"
PM: "5th of june would be official go" Me: " Okay, i'm noting 5th of june in my agenda, let's get this through!"

And now i get a message...stating that the date of 5th of june , is for another project, at the same goct dept, but totally different project

WHAT THE FUCKING SHIT I'VE SPENT MONTHS WAITING FOR A PROJECT THAT WAS PRACTICALLY ALL SET AND GO AND EVERY SINGLE FUCKING TIME IT GETS DELAYED, EVERY FUCKING TIME I THINK "you know, i cannot accept these offers since that Govt project will start soon, i cannot do 2 assignments at once especially when they require me to work at govt office at the capital..." AND EVERY FUCKING TIME IT GETS DELAYED!!!

I feel at a loss now..... i've done i think the most horrible thing you can do as a independent and that's not accepting another assignment just because there was a concrete promise for a govt contract...

Almost dried up, nothing much left, had to do some spending because of a move to another apartment... I'm feeling really down, and angry...and down, but mostly angry, for not accepting those offers in the meantime...

A real interaction I just had...

Team Member: "Can you handle this ticket for a bug fix?"

Me: "Whats the problem?"

TM: "We aren't exactly sure..."

Me: "Ok, so can you show it to me?"

TM: "We can't get it to happen again, and when it does the machine freezes and we can't debug it..."

Me: "So, if I find a fix then how do we test to make sure it worked?"

TM: "I'm not sure..."

Then today,

Product Manager: "How's that bug fix going?"

Me: "Well, let's see. The problem still hasn't been defined. I have never been able to recreate the issue. I have a hacky fix in a PR..."

PM: "Great, so we can deploy today?!?"

Me: "No, because we have no way to reproduce or test this issue at all..."

PM: "Do you think your fix will work?"

Me: "Honestly, no. If you're asking for my opinion then you can have it. IMO this is NOT a bug fix but a change to how the system operates altogether. This system was built by someone who didn't know what they are doing. We have done our best with it but it is a house of cards. And now the solution is to replace a card at the bottom layer. It is likely that no matter what fix we do (even when we can fucking test it) that it will topple the house of cards..."

PM: ~Looking at me in disbelief~

Me: "If you ask me for my honest professional opinion then you will get it. Keep that in the future if that honest response was outside what you expected."

PM: "I will do that, thanks for your assessment"

Where do we go from here? God only knows.

Praise Joe Pesci

!rant.
I've worked for about two months at my (first) job. Its amazing.
We create audio/video software for the products we make.

There are 9 programmers besides me, I'm the only junior. And I'm still learning my way around the code, but they still value my input.

We only do stand ups for 5-10 min, like it should.

One if my colleagues helps me often when I have questions, so I've nicknamed him ducky.

My pm is awesome, he's great at coding and a great manager.

When we work overtime, the department pays for delivery food and drinks.

And we've already gone on 2 trips with the department, mountain biking and a BBQ.

I love my job and I hope that I'll soon be good enough to ask less questions.

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

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

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

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

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

My PM: I don't like when you get up and help out other colleagues with their problems on their computer. You're not at their service.
Me: okay, I'll refrain from doing so.

The next day, I arrive 5 minutes before 8, I get myself a coffee, talk with a few colleagues, and:
PM: Hey, can you please come and help me review this email?
Me: ** fuck it, I still have 2 minutes ** Yeah I'm coming
PM: Now please.
Me: ...

Also my PM, 5 minutes later: Hey I don't manage to print my document, can you help me?
Me: ...

10 minutes later, I get a call:
PM: did you call XY about ZX?
Me: Yep, sent you a mail about it 2 minutes ago
PM: Really? I don't see it
Me: I sent it.
PM: Can you send it again?
Me: ...

Later that day:
PM: Hey, what are you up to?
Me: Well, I'm working on our improved websi-
PM: Can you please create a new campaign on Mailchimp? We're all under water here and a bit of cooperation from you would be great
Me: ** huh? ** erm, ok?
PM: Do it now
Me: Yeah yeah, don't worry. ** click ** here, done. Now, where was I...

----- PM on holidays

Other colleague from another department: Hey Phlisg! I have a small problem on our platform, can you help me?
Me: ** writes a script to help her out **
Her: awesome, thank you!!
Her own PM, 5 minutes later: Hey! Thank you very much for your help, it helps us out a real lot, very much appreciated :)

I lost my smile at work since the beginning of the year, but that little help I gave my colleague just gave my smile back to me :D

Ahhhhh devrant... long time no see.

I just need to get something off my heart. The past two years, I worked for the same ISP in Germany, but now as a devops engineer. Well, popo hit the fan really quick lately..

First a good friend, team lead for one of five areas in Germany, quit his job. He was one of the nicest persons I knew, and he believed that all that five areas should work together and share dev resources. Thats why I work mostly in other areas as developer.

Shortly after, his deputy quit as well. I heard that this specific area, the management were a bunch of dicks, but wow!

A short while later, I learnd the hard truth, why those two good friends quit, and that brings me to this story. In a meeting I readied myself up to present my new plattform - a social room - to management. I got a lot of positive feedback from others and we thaught managment would approve of the project. But nope. "We can buy from external, we dont need to program ourselfs. In fact lets stop spending money on internal programming, we should outsource everything!"

I was baffeld... Wtf did i just witness? My team lead didn't say anything, and afterwards I didn't dare to question it, but I told most of my close dev friends and we all realizied, that the rumors were true... We will be shifting into project managment.

At this point, I realized that I wasnt having it, and made a linkedIn account, not because I wanted to switch jobs, but because, meh you never know.

One week ago, one of my bestest buddies said he will quit and join his team lead that left eariler this year, I was heartbroken. Me and our other buddy are devestated, because now we have to do everything he had done. Management didn't listen as we told them that nobody can maintain his code. I have so many projects, I can bearly keep up with them. Now I got a lead role for creating the server infrastucture for a huge project my buddy was working on. Only as specialist and not PM, but his Team Lead thinks I am replacing him!

Last week I got a message on LinkedIn, a consulting firm reached out to me to aquire me as a new consultant or devops engineer. They look great, only less vacation (26 instead of 30 days), 40h shifts instead of 38h and only slightly more base payment. I currently receive about 53.000€ a year, the new firm only grants up to 60.000€ a year for anyone. Otherwise, they look great.

With all my buddies quitting around me, work getting more while time developing decreasing, I don't know what the right thing to do is... There is no way I can get a payment increase in my current position. I always say "my workplace is save, but my work isnt". I don't want to do project managment.

Today I have a meeting with my team lead, she is really nice btw. This is an annual meeting where we discuss my future in the company etc. Shortly after, I have a meeting with the new firm to discuss a bunch of questions I have.

I dont know what to do...

Edit: I missed you, devrant

Conversations I've genuinely had at work:

Me: "Do you want some advice understanding that function?"
Dev: "Yeah, please!"
Me: "Get a plastic bag and some super glue..."

Dev: "I think I'm seeing the light at the end of the tunnel!"
Me: "It's just the train of mental bitchslaps coming in the other direction."
... Some time later
Dev:"You were right... "

Dev: "If the system is so unstable, how does it keep working?"
Me: "Do you see any goats in the office?"
Dev: "Uhm no... Why would there be goats?"
Me: "There aren't, now, we ran out."
Dev: "The hell are you talking about?"
Me: "We just sacrifice our own blood to Cthulhu these days, it's cleaner and we didn't have to pay to have all the goats blood and waste matter to be cleaned up. That and it was needlessly cruel to the poor goats and that is why there is no goats and despite conventional logic the app continues to work."

Dev: "So what language is the web app written in?"
Me: "You need to understand I inherited this project, I had nothing to do with it's spawning..."
Dev: "OK, that sounds ominous... How bad is it?"
Me: "Java..."
Dev: "..."

Dev: "So what's it like working on this project? What should I expect?"
Me: "You'll call your grandmother during your lunch break just to know there's a world beyond this project. You'll go home, nose bleeding and you are gonna sit in the shower and rock back and forth, holding yourself and feeling like you're suffering imposter syndrome. You'll question why you joined this team and it'll get inside your head til it's all you think about..."
Dev: "Damn man, why are you still on it?"
Me: "Stockholm syndrome, it's too late for me..."

PM: "You're such a dark person, we're not gonna find you hanging from the lights one day are we?"
Me: "Impossible, we use those industrial fluorescent strip lights, there's no cord to hang from."
PM: "That really wasn't the comforting answer I was looking for."

Head of department: "So I need to apologize, you were never meant to be left on your to manage the product on your own, it's something someone way more senior should have been doing and we reassigned him. It wasn't professional of us, it wasn't fair of us, we're sorry. Truth be told,we're impressed you've not gone mad."
Me: "I think I have. Wibble."

A card goes round work for a sick member of staff I've never met.
Me: "How would you describe her condition?"
Dev: "She said that she 'survived' the surgery."
Me: "Yeah, I'm not great at being appropriate but even I think writing 'glad to hear that you are not dead' in a get well soon card isn't the done thing."

today a coworker came to me. he had some ideas on a program i made for him (he had the thoughts i did the programming).
he is really thankful for this program as it helps him a lot with his daily work.
we talked about an hour: he told me what he wishes and i explained him what i can do with my abilities.

after this talk i had like 8 to 10 changes to make - more or less big.

from 10 am to 2 pm i managed to work off 5 points, built the release and did the update on his pc.

been a long time seeing someone so happy :)

that was a great feeling. now i get some beer. cheers guys

PM: I spoke with x client, they really like x feature and want to continue.
Me: great, I'll let the team know.
PM: Yeah, I told your team already.
Me: Oh. What did they say?
PM: They all told me to tell you first, so you can tell them.
Me: 😏

Once, I overheard a conversation between my former PM and a client during a phone call.

Client: I will send the final draft of the project by Thursday.

PM: That's great to hear!

Client: When can I expect the updates to review the changes after the draft is sent? I need to present it at a meeting this weekend.

PM: It should be ready by Friday without fail!

Client: Excellent! Thank you. I will be expecting it.

PM: Sure, goodbye.

(After the call, PM joined the team.)

PM: So, team, the client for Project-A will be sending us a new draft for review and updates. They are putting a lot of pressure on us and need it to be ready by Friday at the latest. We need to treat this with a sense of urgency.

(After hearing this, we felt compelled to respond.)

Me: There's no way they would expect us to deliver an unseen draft within a day. Both the backend and Figma team members were forced to work last weekend, on Saturday, because you mentioned that Project B was behind schedule and the client needed an update by Monday. We simply can't continue working like this.

Backend guy 2: I also worked last Sunday on Project B.

Me: We overheard you telling the client that they should expect an update by Friday. It seems like you're the one directly putting the team under pressure, even though we still have three ongoing projects with tight deadlines.

(The office fell into an uncomfortable silence.)
(PM left the office without saying a word.)

Later on, I heard that he contacted the client to reschedule the expected time of arrival (ETA) after receiving the draft.

colleague in a planning meeting: so now it's Easter, which in Germany is public holidays on friday and monday
PM: i as a manager would find it great if there weren't any public holidays

yeah not surprised, but thank fuck you're not the one to decide that... some people are trying to have a life^^

this happens way too often in our company

PM: did you made that change I requested?
me: yeah, its on the live server now, why?
PM: I cant see it...
me: *wtf, I specially forced the JS to reload to eliminate problems with cache* could you send me a screenshot?
PM: *sends screenshot*
me: I dont get it... I can see the changes in my browser *dev feeling intensifies* ... refresh the site and try again
PM: oh... suddenly its there, ...anyway, thanks! it looks great!
me: *facepalm*

turns out our managers just dont refresh websites, they want changes to take place immediately

[Little perspective: For the last 7 months I'm working in a certain project.]
[The project is full of unimaginative, non-creative devs with 0 initiative and poor technical background.]
[And they're almost all from one country which you all can figure out.]
[But I'm not going to mention it here because I don't want to come up as a racist]
[So there's US (Europeans) and THEM. 3 of US and about 10 of THEM. And we're doing 90% of all the heavy lifting]
---
Yesterday
---
D (Dev from THEM): Hi S, I have a problem with my task
Me: (sighing) Ok let's have a call
* on the call with D we were checking some stuff loosely related to task *
* code wouldn't get invoked at all for some reason *
* suddenly I realize that even if the code would invoke, D's probably doing everything wrong in it anyway *
Me (thinking): I need to double check something.
Me: I can't help you now, I'll get back to you later.
* call ended *
---
Me: Hey J, I need your help, I need to clarify the work package in my mind, because I am no longer sure.
J (my European TL): Ok, fire away.
* call started *
Me: Is it true that [blahblahblah] and so D's task depends on me completing first my task, or am I losing my mind?
J: That is correct.
Me: Well she's trying to do this in [that] way, which is completely wrong.
J: You see, that's how it is in this project, you do refinements with them, split these work packages to tasks, mention specifically what depends on what and what order should things be taken in, and in some cases all tasks from given user stories should be done by one person entirely... But they do it their way anyway, assign different people to different interdependent tasks, and these people don't even understand the big picture and they try to do the things the way they think they understand them.
Me: It's a fire in a brothel.
J: Yup.
Me: I fucking love this project.
J: (smiling silently)
* call ended *
---
Me: Ok D, you can't do your task because it's dependant on my task.
D: Oh... so what do I do?
Me: I don't know, do something else until I do my task.
---
A (THEIR TL) (Oh, did I forget to mention that there are 2 TLs in this project? THEY have their own. And there are 2 PMs as well.)
A: Hey S, I need to talk
Me: (sighing, getting distracted from work again) Ok let's have a call
* call started *
A: S, we need this entire work package done by Friday EOD.
Me: I can't promise, especially since there are several people working on its several tasks.
A: D's working on hers for 3 days already, and she's stuck. We want you to take over.
Me: (sighing, thinking "great"): Ok.
* call ended *
---
Me: Hey D, A instructed me to take over your task. This is actually going to be easier since you'd have to wait for mine after all.
D: Oh, ok.
---
* I switched the Assigned Person on D's task to myself on Azure *
---
This morning, email from D.
"Hey, I completed my task and it's on [this] branch, what do I do now?"

........................................
Me, hesitating between 2 ways to reply:
(and take note there are people in CC: A, J, P - the last one is THEIR PM)
1) "Hi, Unfortunately you'd still have to wait for my changes because your task is dependent on my task - the column to be changed is in the table that I am introducing and it's not merged to develop branch yet. By the way I already did your task locally, as I was instructed to do it, I'm wrapping things up now."
(y'know: the response which is kind, professional, understanding; without a slight bit of impatience)
2) WHAT FUCKING PART OF "DON'T DO THIS I WILL FUCKING DO IT MYSELF GO HOME JUST GO HOME" YOU DON'T FUCKING UNDERSTAND

Past few weeks, I have started to work late night and sleep whole day. I go to office at around 7pm and returns back next day 8-9am. I found it super productive.
But, my manager wasn't happy about it and now, she shifted daily scrum at 1 PM and emailed me to make sure I attend it daily.
Now, I have to fix my sleeping cycle... Nights are so great to work. Silent and nobody around.
Now, from tomorrow, I got a new challenge everyday to make it to scrum daily.

>On a call with Manager
>he's showing off some code
>oh cool he's finally assigning me some real work

PM: So yeah, just wanted to have you on a call to show you how easy it was to fix this.

Me: ... Oh... OK.

PM: yeah so this was completely broken. The last guy that was working on this didn't do a great job. Like seriously, what is this? Amateur hour? Hahaha

Me:... Haha... Yeah, right... 🫠

PM: anyways I figured I would go ahead and do this because it would take me 10 minutes to figure out. It would probably would have taken you 3 hours or something to figure out.

Me: ok... <why tf am on this call other than for you to shit on my skills?>

PM: anyways just wanted to walk you through what I did and show you how easy it was to fix.

Me: ok.

Other PM: We must fix the database performance issues now.

Me: We can't. We're still only halfway on the dependency chain to tackle this and honestly, even if the dependency chain would be fulfilled, I'd leave at least 2 weeks monitoring the production after the changes were rolled out before we further poke around.

Other PM: This is taking far too long. And whaddya mean by dependency chain? Why was I not informed about this?

Me: *sigh* like in every meeting in the last weeks: the dependency chain are the current open blockers before we can proceed with the database changes. We've talked about this _at length_... Especially why these blockers exist.

Other PM: No, we need to start now. I've _examined_ at the blockers or "dependency chain" as you call it.

(Examined.... He opened on his currently streaming laptop, which was connected to the active beamer, the mentioned ticket with a detailed blocker ... And quickly scrolled. Yeeah. Warmonger...).

Me: I'm very tired of discussing this. But since you are already presenting us the ticket, read out the referenced meeting notes... We explained it in great detail.

Other PM: Why? This is just a waste of time!!!!!!!

--
Yes. This happened. Other PM was my nemesis.
In this meeting were 2 PMs (Him, Me)… I think 5 - 7 devs... And we were sitting in this meeting since 2 hours at least. Everyone was angry...

After this "manifesto of intelligence"… I simply left the room, followed by a few devs.

And yes. Other PM did this on a regular basis....

At a certain client, was asked to help them with an "intermediary" solution to stopgap a license renewal on their HR recruiting system.

This is something I was very familiar with, so no big. Did some requirements gathering, told them we could knock it out in 6 weeks.

We start the project, no problems, everything is fine until about 2.5 weeks in. At this point, someone demands that we engage with the testing team early. It grates a little as this client had the typical Indian outsourcing mega-corp pointey-clickey shit show "testing" (automation? Did you mean '10 additional testers?') you get at companies who put business people in charge of technology, but I couldn't really argue with it.

So we're progressing along and the project manager decides now is a great time to bugger the fuck off to India for 3 months, so she's totally gone. This is the point it goes off the rails. Without a PM to control the scope, the "lead tester," we'll call her Shrilldesi, proceeds to sit in a room and start trying to control the design of the system. Rather than testing anything in the specification, she just looked at the existing full HRIS recruiting system they were using and starts submitting bugs for missing features. The fuckwit serfs they'd assigned from HR to oversee this process just allowed it to happen totally losing focus on the fact this was an interim solution to hold them over for 6 months and avoid a contract renewal.

I get real passive aggressive at this point and refuse to deliver anything outside the original scope. We negotiate and end up with about 150% scope bloat and a now untenable timeline that we delivered about 2 weeks late, but in the end that absolute whore made my life a living hell for the duration of the project. She then got the recognition at the project release for her "excellent work," no mention of the people who actually did the work.

Tl;Dr people suck and if you value your sanity, you'll avoid companies that say things like, "we're not in the technology business" as an excuse to have shitty, ignorant staff.

If living and working in the UK wasn't hard enough as is for a student. This now happens and has, pretty much, screwed everything over.
Promoted lies, PM stepping down, value of pound dropping.
All going great! ☺️🔫

As a developer, I constantly feel like I'm lagging behind.

Long rant incoming.

Whenever I join a new company or team, I always feel like I'm the worst developer there. No matter how much studying I do, it never seems to be enough.

Feeling inadequate is nothing new for me, I've been struggling with a severe inferiority complex for most of my life. But starting a career as a developer launched that shit into overdrive.

About 10 years ago, I started my college education as a developer. At first things were fine, I felt equal to my peers. It lasted about a day or two, until I saw a guy working on a website in notepad. Nothing too special of course, but back then as a guy whose scripting experience did not go much farther than modifying some .ini files, it blew my mind. It went downhill from there.

What followed were several stressful, yet strangely enjoyable, years in college where I constantly felt like I was lagging behind, even though my grades were acceptable. On top of college stress, I had a number of setbacks, including the fallout of divorcing parents, childhood pets, family and friends dying, little to no money coming in and my mother being in a coma for a few weeks. She's fine now, thankfully.

Through hard work, a bit of luck, and a girlfriend who helped me to study, I managed to graduate college in 2012 and found a starter job as an Asp.Net developer.
My knowledge on the topic was limited, but it was a good learning experience, I had a good mentor and some great colleagues. To teach myself, I launched a programming tutorial channel. All in all, life was good. I had a steady income, a relationship that was already going for a few years, some good friends and I was learning a lot.

Then, 3 months in, I got diagnosed with cancer.

This ruined pretty much everything I had built up so far. I spend the next 6 months in a hospital, going through very rough chemo.

When I got back to working again, my previous Asp.Net position had been (understandably) given to another colleague. While I was grateful to the company that I could come back after such a long absence, the only position available was that of a junior database manager. Not something I studied for and not something I wanted to do each day neither.

Because I was grateful for the company's support, I kept working there for another 12 - 18 months. It didn't go well. The number of times I was able to do C# jobs can be counted on both hands, while new hires got the assignments, I regularly begged my PM for.

On top of that, the stress and anxiety that going through cancer brings comes AFTER the treatment. During the treatment, the only important things were surviving and spending my potentially last days as best as I could. Those months working was spent mostly living in fear and having to come to terms with the fact that my own body tried to kill me. It caused me severe anger issues which in time cost me my relationship and some friendships.

Keeping up to date was hard in these times. I was not honing my developer skills and studying was not something I'd regularly do. 'Why spend all this time working if tomorrow the cancer might come back?'

After much soul-searching, I quit that job and pursued a career in consultancy. At first things went well. There was not a lot to do so I could do a lot of self-study. A month went by like that. Then another. Then about 4 months into the new job, still no work was there to be done. My motivation quickly dwindled.

To recuperate the costs, the company had me do shit jobs which had little to nothing to do with coding like creating labels or writing blogs. Zero coding experience required. Although I was getting a lot of self-study done, my amount of field experience remained pretty much zip.

My prayers asking for work must have been heard because suddenly the sales department started finding clients for me. Unfortunately, as salespeople do, they looked only at my theoretical years of experience, most of which were spent in a hospital or not doing .Net related tasks.
Ka-ching. Here's a developer with four years of experience. Have fun.

Those jobs never went well. My lack of experience was always an issue, no matter how many times I told the salespeople not to exaggerate my experience. In the end, I ended up resigning there too.

After all the issues a consultancy job brings, I went out to find a job I actually wanted to do. I found a .Net job in an area little traffic. I even warned them during my intake that my experience was limited, and I did my very best every day that I worked here.

It didn't help. I still feel like the worst developer on the team, even superseded by someone who took photography in college. Now on Monday, they want me to come in earlier for a talk.

Should I just quit being a developer? I really want to make this work, but it seems like every turn I take, every choice I make, stuff just won't improve. Any suggestions on how I can get out of this psychological hell?

Worst exp. on a collab/group project?

Had a few, here is one.

Worked with a dev team (of two devs) in Norway to begin collaboration on providing a portal into our system (placing orders, retrieving customer info, inventory control, etc)

They spoke very good English, but motivation was the problem. Start the day around 10:00AM...take a two hour lunch...ended the day at, if I was lucky, 4:00PM (relative to Norway time). Response time to questions took days, sometimes weeks. We used Skype, which helped, but everything was "Yea...I'll do that tomorrow...waiting on X....I have a wedding to go to, so I'll finish my part next week."

I didn't care so much, I had other projects to do, but the stakeholders pounded me almost everyday demanding a progress report (why aren't you done yet...etc..etc.)
The badgering got so bad I told the project owner (a VP) if he wanted this project done by the end of the year, the company would have to fly me to Norway so I personally push things along.
When real money was on the line, he decided patience was warranted.

A 3 month project turned into 9, and during a phone meeting with the CEO in December
O: "Thanks guys, this project is going great. We'll talk again in February. Bye."
PM: "Whoa...what! February!"
<sounding puzzled>
O: "Um..yes? It's Christmas time. Don't you Americans take off for Christmas?"
PM: "Yes, but not until Christmas. Its only December 12th. Your taking the whole month of December and January for Christmas?"
O:"Yes, of course. You Americans work too hard. You should come over here and see how we celebrate. Takes about a month so we can ease back into the flow of things."
<Jack is the VP>
PM: "Jack wanted this project completed by the end of the year, that is what everyone agreed to."
O:"Yes, I suppose, but my plane is waiting on me. Not to worry, everything will be fine."
<ceo hangs up>
PM: "Oh shit..oh shit..oh shit. What are you going to do!?"
Me: "Me!?..not a darn thing. Better go talk with Jeff."
<Jeff is the VP>
J: "This is unacceptable. You promised this project would only take a few months. I told you there would be consequences for not meeting the deadline."
PM:"But..but...its not our fault."
J: "I don't care about fault. I care about responsibility. I've never had to fire anyone for not meeting a deadline, but .."
Me: "Jeff, they are in Norway and no one is working this project for the next two months. You've known for months about them dragging their asses on this project. We're ready to go. Services have been tested and deployed. Accounting has all the payment routing ready. Only piece missing is theirs."
J: "Oh. OK. Great job guys. I guess we'll delay this project until February."
<leave the office>
PM: "Holy shit I'm glad you were there. I thought I was fired."
Me: "Yea, and that prick would have done it not giving a crap that it's Christmas."
<fast forward to Feb>
O: "Our service provider fell through, so I'm hosting with another company. You guys know PHP? Perl? I don't know what they called it, but it sounded so cool I bought the company."
PM: "You bought what? Are we still working with Z and B?"
O:"Yea, sort of. How's your German? New guy only speaks German."
PM: "Um, uh... no one here speaks German"
O:"Not to worry, I speak German, French, and Italian. I'll be your translator."
PM: "What? French and Italian?"
O: "On my trip to France I connected with a importer who then got me in touch with international shipper in Italy. I flew over there and met a couple really smart guys than can help us out. My new guy only speaks German, J only speaks French, and R speaks Italian, Russian, and a little English. Not to worry, I'm full time on this project. You have my full attention."

We believe the CEO has/had some serious mental issues, including some ADD. He bailed within the first month (took another vacation to Sweden to do some fishing) and left me using Google Translate to coordinate the project. Luckily, by the end, the Norwegian company hired a contractor from England who spoke German and hobbled together the final integration.

Did I ever say I love my PM? He's fucking awesome.

In the summer I got an internship at this company and the PM had plans to turn me into a permanent employee, junior position I assume. I told him I'd need a month after school started to see how things went with school and the job at the same time. In the end I decided I couldn't work full-time because I don't have time for it. Also, I want to explore a bit the CS field and see if there's anything else I like (quantum computing and low level programming are at the top of my list), so I decided I won't be renewing my contract as an intern either.

Last week I went into a call with my PM to tell him about all of this and I did not expect the response I got. He actually thinks I'm doing right and supported me in my decision to learn other things. I didn't expect this kind of response at all and it made me feel much, much better (I was pretty nervous to tell him). He also told me that if I want to work on something else in order to learn I just have to ask (I currently do web dev).

But that's not all. He gives us, developers, space to work and doesn't micromanage us. He has technical understanding, doesn't force deadlines on us and understands that sometimes things take longer than expected. He is just great and I'm kind of sad I'll be leaving this job because he's awesome and (from what I read here on devrant) that seems to be pretty rare.

Anyways, that's it, no anger or anything today, I just wanted to say I like my PM very much.

Client project manager calls me up one day

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

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

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

Me: sounds good

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

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

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

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

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

Me: 🤦🏻‍♂️

meeting with PM, 1:1
me: well, to be honest, i think there is also some room for improvement concerning communication in our meetings. the discussion culture in our meetings could be more open.
PM: what do you mean? i don't know what you're talking about.
me: well, i feel sometimes that in meetings, you overly challenge what colleagues suggest. on the other hand, it's really hard to argue against what you are saying. what you say is often like engraved into stone and it is hard to argue against that, but the next day you might have changed your mind again and then things are different, but engraved into stone again.
PM: hmm. can you give me some more concrete example?
me: well... (gives some examples) it's just that it would be nice if you would listen more to what people say in meetings and try to understand what they actually mean or want to say, instead of saying "nah, that's not how we do it" or "no, that's wrong"... just.. well, have more trust in our skills, try to find out what people mean before you discard what you think they said... a bit more of appreciation and openness.
PM: oh, i can tell you, i'm the MOST open manager in this whole company.
me: ...
PM: but anyway, i will think about it.
me: well... okay. also i see there are some challenges within our team concerning intercultural communication. i mean, communication between Germans and Indians is in general a bit problematic in our company, and maybe it is a good idea to have some workshop together concerning intercultural competences... i think we could benefit from that. (what i actually meant is, these problems exist, but currently i see them more on his side or between him and Indian colleagues, because e.g. he tends to harshly criticize people in daily standups, and if we "direct" Germans already feel affronted by his behavior, how must Indian guys feel about it? in fact, 2 Indian devs already left the project. also communication doesn't really work well, in a way that there's often a great mismatch between his expectations and what Indian devs actually think they have to do)
PM: i can tell you, i really understand our Indian colleagues, i really know how to work with them. also, their working style has greatly improved since project start. (which doesn't feel quite right after he totally ripped apart the work of one guy in the last sprint review meeting)

of course, that's not the whole conversation, but it's kind of a symptomatic example for the whole situation...

it was 12am when we are ready to launch our new web design which requires a lot of hardwork and routing processes. my team lead was the one who pushes the button to production using "cap production deploy" command. everyone in the room (including PM) was like counting down like launching a rocket to space. the feeling is great knowing that everyone was sleepy at that time. im glad it went smooth and everyone congratulates each other.

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

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

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

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

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

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

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

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

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

Frankly, fuck those guys.

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

Let's see how this whole thing goes.

Meetings... They say coding is 70% thinking and well.. I find meetings to be a great place to think about what am currently working on. I go in with a sketch book and sketch away. I always figure out whatever is bugging me by the end of the meeting. After all the PM will send a summary of whatever I may have missed during the meeting

Do you have a ‘Drama Queen’ on your team?
This happened last week.
DK = Drama Queen
DK: “OMG..the link to the document isn’t working! All I get is page not found. I’m supposed to update the notes for this project…and now I can’t! What the _bleep_ and I supposed to do now?!...I don’t understand how …”
This goes on for it seems 5 minutes.
Me: “Hold on...someone probably accidently mistyped the file name or something. I’m sure the document is still there.”
DK: “Well, I’ll never find it. Our intranet is a mess. I’m going to have to tell the PM that the project is delayed now and there is nothing I can do about it because our intranet is such a mess.”
Me: “Maybe, but why don’t you open up the file and see where the reference is?”
DK: “Oh, _bleep_ no…it is HTML…I don’t know anything about HTML. If the company expects me to know HTML, I’m going to have to tell the PM the project is delayed until I take all the courses on W3-Schools.”
Me: “Um…you’ve been developing as long as I have and you have a couple of blogs. You know what an anchor tag is. I don’t think you have to take all those W3 courses. It’s an anchor tag with a wrong HREF, pretty easy to find and fix”
DK: “Umm…I know *my* blog…not this intranet mess. Did you take all the courses on W3-Schools? Do you understand all the latest web html standards?”
Me: “No, but I don’t think W3 has anything to do the problem. Pretty sure I can figure it out.”
DK: “ha ha…’figuring it out’. I have to know every detail on how the intranet works. What about the javascript? Those intranet html files probably have javascript. I can’t make any changes until I know I won’t break anything. _bleep_! Now I have to learn javascript! This C# project will never get done. The PM is going to be _bleep_issed! Great..and I’ll probably have to work weekends to catch up!”
While he is ranting…I open up the html file, locate the misspelling, fix it, save it..
Me: “Hey..it’s fixed. Looks like Karl accidently added a space in the file name. No big deal.”
DK:”What!!! How did you…uh…I don’t understand…how did you know what the file name was? What if you changed something that broke the page? How did you know it was the correct file? I would not change anything unless I understood every detail. You’re gonna’ get fired.”
Me: “Well, it’s done. Move on.”

First day back. I am a junior Dev a year and a half of work.
I get in after Christmas break and find people standing around my desk turns out all senior staff (except CEO and PM who are both non-technical ) are away and an email. Basically saying it's up to me for the next week to manage people.

FU&£&# what the heck I don't have a clue what I am doing and I can't mange if I could I would be a manager pays better. So I designate to people took me an hour to figure out what people can actually get on with. Then PM wants a break down of the plan. Then meeting with CEO over the importance of these projects and told 'politely' shortest deadline to date most work, get it done the company depends on these projects if you don't well it would be the end of you.

Get back to my desk people need work I should be getting on with to do theirs but I have been busy in silly meetings and litrually every 5 mins get nagged 'have I done it yet'. But as I am about done they discover what they should have been working on is doable without my work. I don't shake but at one point today I was shaking so much with nerves I couldn't type. Had a very short lunch and stayed on late sorting people problems out. (Thankfully the even more junior people are nice and 1 did help me at one point today I'm so great full for the help)

I'm a junior no training in the technologies I work with not even before starting the job. £3 million+ worth of projects and possible future client resting on my shoulders... (Thankfully the real project lead and senior members are back next week although won't be long left till deadline) Wtf ...
Anyone got a job going I want out!

So, I'm the only iOS developer in the company working on this stupid app which is never going to succeed because the client idea is just plain stupid. Anyway, 6 months developing this crap, countless iterations, trillions of so-called retard "features", and now that we are almost there to go into production my PM decides it's a great moment to document every aspect of what was done and asks me to do it. Now I have 3 documents to write and around 80 bugs to review before Friday. Stupid me for thinking he didn't waste 6 months doing absolutely nothing while I was working 12 hrs a day to meet deadlines.

I'm so sick of dumb project managers, they want "updates" but then they reply with "I didn't understand any of that but it sounds like it's going well"

I literally have a PM who does it all the time, at this point I could talk to him in another language, and he'd just say "Great, sounds like its going well" then proceed to ask for updated a couple hours later *hardfacdpalm*

New PM thinks it's a great idea to start micromanaging my team's (private) repo names. Can't wait to hear his opinions on our class and variable names! 😭

So ok here it is, as asked in the comments.

Setting: customer (huge electronics chain) wants a huge migration from custom software to SAP erp, hybris commere for b2b and ... azure cloud
Timeframe: ~10 months….

My colleague and me had the glorious task to make the evaluation result of the B2B approval process (like you can only buy up till € 1000, then someone has to approve) available in the cart view, not just the end of the checkout. Well I though, easy, we have the results, just put them in the cart … hmm :-\
The whole thing is that the the storefront - called accelerator (although it should rather be called decelerator) is a 10-year old (looking) buggy interface, that promises to the customers, that it solves all their problems and just needs some minor customization. Fact is, it’s an abomination, which makes us spend 2 months in every project to „ripp it apart“ and fix/repair/rebuild major functionality (which changes every 6 months because of „updates“.

After a week of reading the scarce (aka non-existing) docs and decompiling and debugging hybris code, we found out (besides dozends of bugs) that this is not going to be easy. The domain model is fucked up - both CartModel and OrderModel extend AbstractOrderModel. Though we only need functionality that is in the AbstractOrderModel, the hybris guys decided (for an unknown reason) to use OrderModel in every single fucking method (about 30 nested calls ….). So what shall we do, we don’t have an order yet, only a cart. Fuck lets fake an order, push it through use the results and dismiss the order … good idea!? BAD IDEA (don’t ask …). So after a week or two we changed our strategy: create duplicate interface for nearly all (spring) services with changed method signatures that override the hybris beans and allow to use CartModels (which is possible, because within the super methods, they actually „cast" it to AbstractOrderModel *facepalm*).
After about 2 months (2 people full time) we have a working „prototype“. It works with the default-sample-accelerator data. Unfortunately the customer wanted to have it’s own dateset in the system (what a shock). Well you guess it … everything collapsed. The way the customer wanted to "have it working“ was just incompatible with the way hybris wants it (yeah yeah SAP, hybris is sooo customizable …). Well we basically had to rewrite everything again.
Just in case your wondering … the requirements were clear in the beginning (stick to the standard! [configuration/functinonality]). Well, then the customer found out that this is shit … and well …

So some months later, next big thing. I was appointed technical sublead (is that a word)/sub pm for the topics‚delivery service‘ (cart, delivery time calculation, u name it) and customerregistration - a reward for my great work with the b2b approval process???

Customer's office: 20+ people, mostly SAP related, a few c# guys, and drumrole .... the main (external) overall superhero ‚im the greates and ur shit‘ architect.
Aberage age 45+, me - the ‚hybris guy’ (he really just called me that all the time), age 32.
He powerpoints his „ tables" and other weird out of this world stuff on the wall, talks and talks. Everyone is in awe (or fear?). Everything he says is just bullshit and I see it in the eyes of the others. Finally the hybris guy interrups him, as he explains the overall architecture (which is just wrong) and points out how it should be (according to my docs which very more up to date. From now on he didn't just "not like" me anymore. (good first day)
I remember the looks of the other guys - they were releaved that someone pointed that out - saved the weeks of useless work ...

Instead of talking the customer's tongue he just spoke gibberish SAP … arg (common in SAP land as I had to learn the hard way).
Outcome of about (useless) 5 meetings later: we are going to blow out data from informatica to sap to azure to datahub to hybris ... hmpf needless to say its fucking super slow.
But who cares, I‘ll get my own rest endpoint that‘ll do all I need.

First try: error 500, 2. try: 20 seconds later, error message in html, content type json, a few days later the c# guy manages to deliver a kinda working still slow service, only the results are wrong, customer blames the hybris team, hmm we r just using their fucking results ...
The sap guys (customer service) just don't seem to be able to activate/configure the OOTB odata service, so I was told)
Several email rounds, meetings later, about 2 months, still no working hybris integration (all my emails with detailed checklists for every participent and deadlines were unanswered/ignored or answered with unrelated stuff). Customer pissed at us (god knows why, I tried, I really did!). So I decide to fly up there to handle it all by myself

Project manager, who i've complained in the past is neglecting critical things that he doesn't want to do, decided today to cancel our weekly planning meeting, to have the below conversation with me 1:1. Its very long, but anyone who has the will to get through it ... please tell me it's not just me. I'm so bewildered and angry.

Side note: His solution to the planning meeting not taking place ... to just not have one and asked everyone to figure it out themselves offline, with no guidance on priorities.

Conversation:

PM: I need to talk to you about some of phrasing you use during collaboration. It's coming across slightly offensive, or angry or something like that.

Me: ok, can you give me an example?

PM: The ticket I opened yesterday, where you closed it with a comment something along the lines of "as discussed several times before, this is an issue with library X, can't be fixed until Y ...".

"As discussed several times" comes across aggressive.

Me: Ok, fair enough, I get quite frustrated when we are under a crunch, working long hours, and I have to keep debugging or responding to the same tickets over and over. I mean, like we do need to solve this problem, I don't think its fair that we just keep ignoring this.

PM: See this is the problem, you never told me.

Me: ... told you what?

PM: That this is a known issue and not to test it.

Me: ..... i'm sorry ..... I did, that was the comment, this is the 4th ticket i've closed about it.

PM: Right but when you sent me this app, you never said "don't test this".

Me: But I told you that, the last 3 times that it won't be in until feature X, which you know is next month.

PM: No, you need to tell me on each internal release what not to test.

Me: But we release multiple times per week internally. Do you really need me to write a big list of "still broken, still broken, still broken, still broken"?

PM: Yes, how else will I know?

Me: This is documented, the last QA contractor we had work for us, wrote a lot of this down. Its in other tickets that are still open, or notes on test cases etc. You were tagged in all of these too. Can you not read those? and not test them unless I say I've fixed them?

PM: No, i'm only filling for QA until we hire a full time. Thats QA's job to read those and maintain those documents.

Me: So you want me to document for you every single release, whats already documented in a different place?

PM: ok we'll come back to this. Speaking of hiring QA. You left a comment on the excel spreadsheet questioning my decision, publicly, thats not ok.

Me: When I asked why my top pick was rejected?

PM: Yes. Its great that you are involved in this, but I have to work closely with this person and I said no, is that not enough?

Me: Well you asked me to participate, reviewing resumes's and interviewing people. And I also have to work extremely close with this person.

PM: Are you doubting my ability to interview or filter people?

Me: ..... well a little bit yeah. You asked me to interview your top pick after you interviewed her and thought she was great. She was very under qualified. And the second resume you picked was missing 50% of the requirements we asked for ... given those two didn't go well, I do think its fair to ask why my top pick was rejected? ... even just to know the reason?

PM: Could you not have asked publicly? face to face?

Me: you tagged me on a google sheet, asking me to review a resume, and rather than tag you back on 2 rows below ... you want me to wait 4 days to ask you at our next face to face? (which you just cancelled for this meeting)

PM: That would have been more appropriate

Me: ..... i'm sorry, i don't want to be rude but thats ridiculous and very nit pick-y. You asked my opinion on one row, I asked yours on another. To say theres anything wrong with that is ridiculous

PM: Well we are going to call another team meeting and discuss all this face to face then, because this isn't working. We need to jump to this other call now, lets leave it here.

The company considers the project manager I work with to be the best. After working with him, I consider him to be everything that is wrong with project management.

This PM injects himself into everything and has a way of completely over-complicating the smallest of things. I will give an example:

We needed to receive around 1000 rows of data from our vendor, process each row, and host an endpoint with the data in json. This was a pretty simple task until the PM got involved and over complicated the shit out of it. He asks me what file format I need to receive the data. I say it doesnt really matter, if the vendor has the data in Excel, I can use that. After an hour long conversation about his concerns using Excel he decides CSV is better. I tell him not a problem for me, CSV works just as good. The PM then has multiple conversations with the Vendor about the specific format he wants it in. Everything seems good. The he calls me and asks how am I going to host the JSON endpoints. I tell him because its static data, I was probably going to simply convert each record into its own file and use `nginx`. He is concerned about how I would process each record into its own file. I then suggest I could use a database that stores the data and have an API endpoint that will retrieve and convert into JSON. He is concerned about the complexities of adding a database and unnecessary overhead of re-processing records every time someone hits the endpoint. No decision is made and two hours are wasted. Next day he tells me he figured out a solution, we should process each record into its own JSON file and host with `nginx`. Literally the first thing I said. I tell him great, I will do that.

Fast forward a few days and its time to receive the payload of 1000 records from the Vendor. I receive the file open it up. While they sent it in CSV format the headers and column order are different. I quietly without telling the PM, adjust my code to fit what I received, ran my unit test to make sure it processed correctly, and outputted each record into its own json file. Job is now done and the project manager gets credit for getting everything to work on the first try.

This is absolutely ridiculous, the PM has an absurd 120 hours to this task! Because of all the meetings, constant interruptions, and changing of his mind, I have 35 hours to this task. In reality the actual time I spent writing code was probably 2-3 hours and all the rest was dealing with this PM's meetings and questions and indecisiveness. From a higher level, he appears to be a great PM because of all the hours he logs but in reality he takes the easiest of tasks and turns them into a nightmare. This project could have easily been worked out between me and vendor in a 30 min conversation but this PM makes it his business to insert himself into everything. And then he has the nerve to complain that he is so overwhelmed with all the stuff going on. It drives me crazy because this inefficacy and unwanted help makes everything he touches turn into a logistical nightmare but yet he is viewed as one of the companies top Project Managers.

them: welcome new project members, this is our CI/CD pipeline which is completely different from the rest of the company, there won't be any great knowledge transfer, we just expect you to be able to know and use everything. but also, we expect you to work on your tasks and don't waste any time.
me: okay, so my tasks aren't going as fast as expected, because I need to invest some learning so i can set up my project correctly.
later: some help would be nice, i'm stuck right now
coworker: *helps me to fix my problems, which were partly due to misconfigured build servers* i know it's a lot, and unfortunately, for this topic sources on the web aren't so good. i can really recommend this book, this will give a deeper understanding of the topic.
me: okay, yeah i mean, tbh, i'll read the book if the project invests some time for me so i can learn everything that's required, but this won't happen. also, some initial workshop on the topic or anything would have been nice.
coworker: well, i mean, i am a software developer. for me, it is normal that i learn all that stuff in my free time. and i think that's what the PM expects from us.
me: okay, that's fine for you, i mean, if i'm interested in a topic, i will invest my private time. but in this case, PM would just expect me to do unpaid labor, to gain knowledge and skills that i can use in this specific project. i'm not willing to do that.
coworker: ...
me: ...

it's not that i don't want to learn. the thing is that there isn't any energy left by the end of the day. i'm actually trying to find some work life balance, because i don't feel balanced right now, haven't felt since i started this job.
also, this is only one of several projects i'm working on. it's like they expect me this project has top priority in my life. if it wasn't so annoying on different levels, maybe i'd have a more positive attitude towards it.

also, at the moment i find it fucking annoying that i have to invest so much time in this dev ops bullshit and this keeps me from doing my actual work.

if they are unhappy with my skills, either they can invest in my learning or kick me out. at this point, either is fine for me..

!rant

How I think the process for designing a hardware-driver is like

CEO: "Alright everyone, we have designed and created this great product, now let's write a driver for it!"

PM: "Great then! We just code for Windows, create an eye-catching UI but leave the actual at the worst possible case that could work!"

Dev: "B-But isn't there other OSes, like Linux and Android that people use on their computers too?"

PM: "Shut up! We are going to JUST support Windows and f*** no absolutely other OSes!

Dev: "But what if they are also developers, and want to control and use this great product by programming it themselves? We should make the driver open-source, or at least give them some APIs!"

PM: "Nonsense! They are only going to use this product on M$ Windows, and with the program we provide to them, even if it's crappy and crashes most of the time!"

Dev: "But-but..."

PM: "No buts! That's our final decision!"

And some other consumer devs are like, "F*** it, we just reverse-engineer the codes and write a new driver ourselves!"

:|

PM: We have a really exciting job for today.

Me: Great! What is it? Website? Emailer?

PM: Business card design and ad resizes!

FML #justwanttocode

Boss: How long will it take to finish the project?

Me: (Gives date for finishing dev and deployment.)

Boss: great, sound reasonable.

Me: ...

Boss: wait. Aren't you on vacation the two weeks after that.

Me: jup.

Boss: yeah we are not doing that again. Client can wait another two weeks.

Before someone says no Boss/PM is like that, he was/is a developer too so discussing deadlines and efforts is usually pretty relaxed since he knows our codebase and how long it takes to do things.

After reading some rants abut stupid project managers I remembered this situation that happened to me a decade ago.
One of the tasks was to move some html component to different place on the page. The whole page was a mix trs and tds and to achieve that I had to rewrite the whole page structure. I estimated around half a day to complete that task. It was my first job and I was not great back then, but still it was reasonable amount for this task.

Now lets introduce my PM : the guy was a complete tool. He was a former hardware store manager ( ͡° ͜ʖ ͡°) and had no idea what we were doing.
He started ranting how on earth such simple task can takes so much time. I started explaining myself, but he wasn't listening. Instead he started sharing his screen, he made a screenshot of the page, pasted it to the ms paint, cut the component, and moved it to desired place. Then he said : It took me like 10 sec to complete the task and I have no experience, maybe I will replace you?
I was speechless. I had no words and I just kept silence.
Then he said he would reassign this task to X, because he is competent.
X spend more then 4 hours and I heard no apologies.

My first gig straight out of uni was on a project where my role required fixing an FTP client to upload files from a clients machine to our server. It was a spreadsheet. VBA. An excel spreadsheet. FTP client. A spreadsheet.

Me: "why are we using VBA for this?"
PM (was a dev 10+ years ago and started the basics of this 'ftp client'): "VBA is great." *Stern face*

Brilliant

people with 8+ years of work from office experience, is 9-6 the only truth of work life? today in sprint planning, our manager suggested assigning 81 hours of tickets in a 2 week sprint and when a lot of us had 60-65 hours of work he was like "ehh it seems less . junior mgr , look into the softwares and create more tickets"

2 week sprint is 9 days +1 day for sprint planning + 2 sat Sunday 🥲 . additionally it takes me arohnd 2 hours to reach home so i try to get out by 5 pm and everyone starts staring at me. as am a bad example, i will probably be hearing from my manager in future about this.

need some tips on handling a stable work-office life. i am a covid graduate so i have seen a great wlb in work from home but its a true reality that for mext 30 years , the chances to work from home for more than 5 cumulative years is next to 0. so need a permanent office hack.

i don't think buttering boss's ass is a reliable solution . i just wanna be back at home by 7, do some workout, roam in car/watch series/work on hobby project (aka relaxing) eat and die on my bed for next day's horrific life

*Log in to work*

*Get a ticket to work on*

"Oh this seems like a simple fix. This should be done in a couple hours."

*Move the ticket to Completed status*

"Oh would you look at that. It's 9 PM and now I have to make dinner".

One of the great joys of being a dev.

Today started off great!

New 5TiB HDD... Check!

Formatted with zfs under LUKS, with a high level.of compression and dedup... Check!

Copying over roughly 4TiB of data, about 2 of which was scattered in small files... Coworker unplugged it from AC thinking it was his (they are sort of similar), when the process was almost complete.

Goddamit. zpool scrub.... 6 hours left. It's 9 pm over here, and I'm not a fan of leaving my stuff at work. Goddammit.

...I guess tomorrow is another day.

Best boss I've had was when I was collecting recycling materials as a truck driver.
The company mostly employs unliterated people that can't get a job anywhere else, so It has lots of dumb, jealous people who made his life miserable.
Still, he's so good with people that he could filter it all out and we had a great relationship even in such a poisonous environment.
He was really sad when he told me I wouldn't have my contract renewed. He allowed me to work from 5 am to 2 pm so I could finish my 12grade class (high school) at night and I fell asleep one day. The company does not renew contracts if you miss even one day. When people talked bad about each other he would just nod and do nothing or descalate the situations.

Well, I'm off to help my dad again :( he's the one who gave me the taste for DIY, but fuck his projects take so much time. Were repainting a motorhome :D

Business logic:

Meeting starts at 9:45 AM. They only really wanna talk about the features they have on the horizon and how innovative and distruptive and rich we'll be. We spend 10, maybe 15 minutes talking about UI and details of the feaure. The meeting ends a few minutes before 12, so that's 2 hours of lunch (I wanna respect the schedules we had pre-covid to keep that rhythm). I start working again at 2 PM, but 15 minutes later, I get called again by one of the managers to hear more about this new great new idea they have.

So I work about 7-9 hours a day. But HR and management want to spend 3 of those hours. Suggestion: we'd improve our productivity by about 35% if we cut those daily meetings.

I'm in my first internship, they gave me their only company owned product. They always made interns work on that, and it's something I really appreciate (I like when people give to others any possible chance of learning)... But apparently they made a mistake: for the first year they never reviewed interns' code. And now that software is huge and full of bugs.

After two weeks working on that I said to the tech leader and to the PM that we should spent a couple of months rewriting more than half of the code, and surprisingly they listened and agreed (the TL already knew that, and the PM is not a dev and he listened to the TL).

After two days of code rewriting ("refactor" is a too weak word) the boss calls me and orders to stop, telling me basically "I agree on this decision, but not now; let's first make it work and then we make it great!".
Okay I respect that, but what he didn't understand is that the two things are strictly related!

Result: last week we had a first official release (with some client's testers, so they were expecting a few bugs) and nothing was working, so me and the tl started a really hard rewriting work (that didn't finish) and managed to release a very bade made software that works by chance.

After easter we'll keep working on this, and I think at the end it will be great.

First working experience, in two months I learned a lot (not only about code/tech).

PM blindly puts user requests into JIRA as tasks to complete without thinking through their relevancy. Some of these are straight up not possible or don't make any damn sense. (╯°□°)╯︵ ┻━┻ just a constant reminder how great it will be when I leave here at the end of the month.

Our PM just send a mail to our team, that after testing the latest extension we made to the project, he could not find a single issue or bug (usually there are some minor UI problems or some edge case bugs we did not think about or know existed)
and what a incredibly great job we did, and he also forwarded the mail to all our managers up the hierarchy right under the CEO.
The appreciation is a nice change to the self-hatred I feel while coding

Debating on whether to quit my job.

Part of the reason it's hard for me to make a decision is there are a lot of good things about my job:

- almost all the projects we work on are blue sky; no technical debt anywhere
- great teammates; people help each other out and generally there's a good vibe
- reasonable boss; he's totally fine with me managing my own schedule, and since I get my work done, he basically never questions when and where I work
- about 1 hour of corporate meetings each week
- best healthcare I've ever had; basically everything is paid for
- 3 weeks PTO & all major US holidays
- free food; generally healthy office snacks and such

So why would I want to quit this environment?

- I hardly get to code anymore. About 2 years ago, I got asked if I would mind helping spec out projects. Since then, I've moved from writing code related to projects to helping my teammates understand the business situation so they can build the right thing.
- I'm in lots of meetings. So we have very few meetings for the company itself. We have a bunch of customer meetings, though. And progressively, I've getting pulled into meetings where there's really no reason for me to be there, aside from "we should have a technical person present."
- The sales people are getting tired of turning down clients that our product isn't targeted for. So they're progressively pushing to make products in those areas. Unfortunately, I'm the only one on the engineering team has any experience in that other tech stack. Also, the team really, really don't want to learn it because it's old tech that's on its way out.
- The PM group is continuously in shambles. Turnover there has averaged 100% annually for about 5 years. Honestly, IMO, it's because they're understaffed. However, there has been 0 real motion to fix this other than talk. This constant turnover has made it so that the engineering team has had to become the knowledge base for all clients.
- My manager has put me on the management track, but has been very slow to hand off anything. I'm the team supervisor, and I have been since the beginning of the year formally. When the supervisor quit last year, it basically became obvious to me that I was considered the informal supervisor after that. However, I can't hire or fire; I can't give a review; I don't have any budget; I can't authorize time off. So what do I do now? Oh, I'm the person that my boss comes to ask about my co-workers performance for the purpose of informing promotion/termination/pay increases. That's it. I'm a spy.

PM: That's a great idea. We'll look at implementing it.

... never implemented

I used to be at a company where it was kind of expected that you worked long days, which made it quite difficult to balance work and private life. It got so out of control that I was even called to work while I was on my holiday. At first I started with shutting off my phone after work hours, but the real solution I found was moving away from that company.

Pretty much everyone at my new company just stops working when the clock hits 4 or 5 pm unless there is something critical that needs to be done. Seeing that also discourages me (and everyone else) from working long days. We are also quite open about our workload so if anyone thinks they’re overwhelmed they can find a relevant person to talk to and eventually a solution is found. The salary isn’t incredible, but the work/life balance and the benefits I get are just way better than getting paid more and living to work.

I think a lot of people go for the high salaries, most of the time disregarding the other part of the equation. If the company has a meh work culture with low regard to employees’ work/life balance, there isn’t much the employee can do besides finding a place to work with better wlb. I’d pick a great work/life balance and peace of mind to a high salary any day.

Taking a class at my local university for fun where the point of the class is to build some kind of project for local companies. The teacher talks a lot about Wordpress and how great it is... He's not a dev, and has only worked as a business consultant/pm.... It's gonna be a long semester, but at least he's funny and has good choices in tv shows to include in his lectures.

Needed money for my company, not enough clients to support business on SaaS alone. Took on a 5k / month job building a platform that competes with my SaaS (more niche, less generic). Also sign up new client who that company's owner is part owner onto my current SaaS. Win / Win?

I do a lot of custom work to my platform to fulfill their needs, which is why I ran out of time for the 5k / mo project. I did these customization for free. Losing money to keep client, but also improving my system.

Work gets busy, I need to drop the 5k project. Client is upset I am working more on his other company (he is not majority owner). I return 1 month of funds to the owner and say I cannot continue.

Owner threatens to make other company that he is part owner stop working with my software if I do not complete project. Blacklisting...great. I agree to work with an overseas developer to do it and PM it for 3 months at least. Making nearly nothing from it (now 1k / month for PM), working nights to deal with India, losing sleep...

Other company suddenly folds due to conflict of egos with that SAME owner. Users drop from 16 to 1. I drop the project, no more strong arming me. Everything is a loss, all effort and money lost for nothing. Bad bet..however...

Owner becomes 100% owner of the other company, and of the software company. I transition him to PM his own project, he still uses my software because It doesn't, nor will it, ever do what the one he is building does. Also, partners from previous company break off and use my software again. New Client. #profit.

But holy hell was it stressful in the interim. People's business tactics are disgusting. Stay calm, play it neutral. Win. Sometimes you have to do what you don't want to do in order to succeed...at least for a little bit.

I was so scared that how he screwed his partners he would screw me over as well if I built one of the modules I have planned for my System, but haven't done yet.

If I did it for him first and then built my own (totally diff codebase) I really didn't want to run into any legal issues considering the schematics he has now are mine, but I didn't finish that part of the system for him. He is obivously highly competitive. Even though he wanted me to, and still does, want me to run his company for him.

Who knows, maybe in the future. To be CTO / COO of two SaaS CRM's in the same space may make sense. But I will never sell my software to him or partner with him. Too much drama. Avoid the drama. Be careful out there fellas.

If you are a creator, people will take advantage of you in every way imaginable. Read the fine print, read the people, document everything. Don't put yourself at risk.

Moved from A 10-day sprint to a 10-hour sprint.

Thank god we don't have hourly stand-ups.

During the course of my career I've stumbled on like 6-7 people I've worked with and it was really great. Every now and then we meet up and chat how it'd be great to form a team again and work on something (we're all in different companies atm).

Lately we've been mentioning that even more and are considering whether to start working on a product/find clients and form an agency/join some other company.

We have experience with both outsource and products. Our profiles range from development, design, marketing, UX, HR, PM.

Any road we take has pros and cons. We're least fit to start on a product because we'd need more profiles, have to figure out finance and would probably have to work alongside our current jobs.

I've been thinking of writing a joint letter when I hear a company is opening up an office in our city. When that happens, usually whole teams are formed and most of the profiles I mentioned are needed.

Do you think that's even possible? Is there another way we're overseeing? Have you heard of or attempted something similar?

Any advice is truly appreciated.

the more i think about the effort i've poured into various projects and products over the years, for clients or my own, and how little its payed overall... its quite depressing (people probably understimate, but i'm talking years upon years, not all at at time, but month spurts where i'd be done for the day at 7 PM or later) 12 hour days are easy to hit quickly when you are cranking out software

if you need an application requirement i've probably built it before, probably most of them twice

everyone tells me "it will pay off in the long run!" or "its great you have so much experience and built those different things!"

great to say, but i'm not getting payed for it / see no benefit from it

not fun to think about

and every place i go i know its gonna be filled with the workaday dev bros who are just there for the paycheck, have no passion, and who don't even know what TypeScript is (true story about that TypeScript one, i shit you not, occured only last year, and the guy is a frontend dev)

😩😩😩

where do i belong devrant?

What a long horrid weekend this has been.
So much overtime gathered though.

Started Friday 5am, went to Oslo to do some drone footage for one of our clients. Got back home at 11:30pm.
During the day I had also been doing some work for this other client we have, they were supposed to have project launch the 22nd, but called on Friday and said it has to be on the 15th instead.

I got a few hours of sleep, woke and worked all day till I passed out at my desk for a few hours, went to the office (on a sunday) to talk to the PM and CXO about the project (great help, they were my rubber ducks)

Good part, I get so many days off now

This one is easy, being forced to use visual studio! In fact I made one or two rants about it.

To top it off using NuGet as a pm was also not a great experience to say the least.

Luckily I was not alone and my team agreed and we rewrote the entire legacy code in Java... A much much better experience!

So that was my worst experience.. My best experience was that I started my first big non-school related project and I am super excited!!

i am i such a shitty situation. i have recently started to love my job as i find the work to be lesser and lesser stressful. i finish my tickets in 2-3 hours exch day, and i am almost free after 3 pm and officially free after 6.30 pm every day (kinda officially, as i have set an unavailable notice on my calendar for 6.30 to 8.30 and after that no one really is online).

i get time to go out, jog, play with my pets do home taks, and even study sometime.

everything is going great except 2 things: they are ending the remote work policy in 2022 and giving esops instead of appraisal/promotion :'( will have to either switch or go live in the city where my office is, which is the most expensive city in my country ( and maybe in top 10 most expensive in the world) + very unsafe. and its obvious that my boss won't be letting me code lying flat on a mattress with a bag of cheetos and in just boxers and flip-flops

A pm asked about a feature I was developing and I went on to show them what I got so far. Feature-wise almost finished, but it still needed to be polished and thoroughly tested, as such it wasn't merged yet. Weeks later - I couldn't finish it yet for unrelated reasons - there was great confusion about why the feature is not there as it had been billed to the customer already. So I gotta pull some sunshine out of my ass and bring it to the last release branch..

I've had my share of both good and bad coworkers.

My best memories are definitely from the late 90's, early 2k's. The team I was a part of back then really had the best attitude. I particularly remember one of them, who ended up being a PM. He was always joking around, nothing was ever too serious to make fun of. He was an old school punk, and it did show. Although he was always professional in meetings with customers and when it mattered. If I'm not totally mistaken, he started a punk band in his fifties, where noone knew how to play or sing. Great guy!

In my current job, all the good and nice people are either quitting or bullied out of the company. I miss them. Sigh.

Had our 3rd party vendor finally check their code into our github. Great.

Checking the recent commits, they only add changed .CSS files. Hmm..odd.

We use less so why did they update the compiled CSS file...? Did they forget to checkin the Less changes...?

Nope. Backend sitecore developer updated the bundled, minified CSS files and checked those in along with the fucking node_modules folder.

Didn't even know what LESS is.

The vendors PM swears the frontend developer did the changes. I don't know what's worse.

TL;DR: idiot 'team leader' does mindless merge to master. Precious time wasted in a high pressure deadline environment.

So, i work currently at one of Belgiums largest consulting company's at brussels airport, we are moving their analytics platform to the cloud.

We use puppet to manage the systems.

When i started i noticed immediately that their 'development workflow' is hardly to be named as such, because they simply change stuff directly on server , manual 'temporary' fixes everywhere, hardcoded stuff, non validated code... Basically the way one would develop in their garage, not in a consulting company as this one. But that is just the beginning.

A month ago i did a major effort to equalize all the discrepancies between the codebase and the server. Ensured entire codebase to be validated, syntax checked, parsed, tested... It works. A 'great codebase overhaul' commit was PR'ed to master and got merged.

Yesterday the team lead, i'll call him 'B-tard' from here on, has also 'equalized the discrepancies between codebase, server and the restnof the stale branches on the repo' . i was doing my other work on my branch so no fucks given. This is where i should have given some fucks.

Anyways, today. The day starts every day with merging the master branch into your working branh because you need the latest working codebase, right?

Wrong!
This fucking dipshit smug b-tard has done a mindless merge of the entire codebase, effectively removing ALL validated working code for provisioning servers. Control blocks, lookup functions, lambda's... Basically everything he did not understand.

At the same time the project is already way beyond the allotted budget in pkney and time, so there is a huge pressure to have a working 'production' environment TODAY!

THIS MOTHERFUCKING B-TARD JUST MADE THAT IMPOSSIBLE.

i'm loving this assignment, i'm loving the PM, the collegues, the environment, the location... everything. All but this fuckibg b-tard that somehow got his position by sucking dick or licking ass or both...

I wanna get out asap.

Oh... While typing this and arriving at the room of the office... It is locked, i have no key.

Fucking asshole!

Recruiter question: Recruiter X sets me up with an interview that went extremely well. The Interviewer ( who is also the project manager) says she would call the recruiter the same day and that I was pretty much a shoo-in for the spot. Recruiter calls b.c. a reference isn't answering and she wants another. I give another good one that I know will pick up. Fast forward almost 2 weeks and I still haven't gotten a response, even after reaching out to X via email and calls. Would it be unprofessional of me to contact the PM directly to inquire about the position? It was due to start monday, but we also got hit by hurricane matthew... not really sure how to procede. Any advice would be great.

PM: We need to add "Under Contract" banners dynamically to listings on xyz.com
Me: No problem
[ ... a few minutes later ... ]
Me: xyz.com has been updated. Check out the listings and let me know if anything is out of place.
PM: The updates you made look great! How does this scale (in the most basic sense of the word; i.e. in the viewport) on abc.com.
Me: ? òįÓ ? ... that's a completely different site ... why would it affect it if you didn't ask for it.

[CONCEITED RANT]
I'm frustrated than I'm better tha 99% programmers I ever worked with.

Yes, it might sound so conceited.
I Work mainly with C#/.NET Ecosystem as fullstack dev (so also sql, backend, frontend etc), but I'm also forced to use that abhorrent horror that is js and angular.
I write readable code, I write easy code that works and rarely, RARELY causes any problem, The only fancy stuff I do is using new language features that come up with new C# versions, that in latest version were mostly syntactic sugar to make code shorter/more readable/easier.

People I have ever worked with (lot of) mostly try to overdo, overengineer, overcomplicate code, subdivide into methods when not needed fragmenting code and putting tons of variables.

People only needed me to explain my code when the codebase was huge (200K+ lines mostly written by me) of big so they don't have to spend hours to understand what's going on, or, if the customer requested a new technology to explain such new technology so they don't have to study it (which is perfectly understandable). (for example it happened that I was forced to use Devexpress package because they wanted to port a huge application from .NET 4.5 to .NET 8 and rewriting the whole devexpress logic had a HUGE impact on costs so I explained thoroughly and supported during developement because they didn't knew devexpress).

I don't write genius code or clevel tricks and patterns. My code works, doesn't create memory leaks or slowness and mostly works when doing unit tests at first run. Of course I also put bugs and everything, but that's part of the process.

THe point is that other people makes unreadable code, and when they pass code around you hear rising chaos, people cursing "WTF this even means, why he put that here, what the heck this is even supposed to do", you got the drill. And this happens when I read everyone code too.

But it doesn't happens the opposite. My code is often readable because I do code triple backflips only on personal projects because I don't have to explain anyone and I can learn new things and new coding styles.

Instead, people want to impress at work, and this results in unintelligible, chaotic code, full of bugs and that people can't read. They want to mix in the coolest technologies because they feel their virtual penis growing to showoff that they are latest bleeding edge technology experts and all.

They want to experiment on business code at the expense of all the other poor devils who will have to manage it.

Heck, I even worked with a few Microsoft MVPs.
Those are deadly. They're superfast code throughput people that combine lot of stuff.
THen they leave at you the problems once they leave.

This MVP guy on a big project for paperworks digital acquisiton for a big company did this huge project I got called to work in, which consited in a backend and a frontend web portal, and pushed at all costs to put in the middle another CDN web project and another Identity Server project to both do Caching with the cdn "to make it faster" and identity server for SSO (Single sign on).

We had to deal with gruesome work to deal with browser poor caching management and when he left, the SSO server started to loop after authentication at random intervals and I had to solve that stuff he put in with days of debugging that nasty stuff he did.

People definitely can't code, except me.
They have this "first of the class syndrome" which goes to the extent that their skill allows them to and try to do code backflips when they can't even do code pushups, to put them in a physical exercise parallelism.

And most people is like this. They will deny and won't admit, they believe they're good at it, but in reality they aren't.

There is some genius out there that does revoluitionary code and maybe needs to do horrible code to do amazing stuff, and that's ok. And there is also few people like me, with which you can work and produce great stuff.

I found one colleague like this and we had a $800.000 (yes, 800k) project in .NET Technology, which consisted in the renewal of 56 webservices and 3 web portals and 2 Winforms applications for our country main railway transport system. We worked in 2 on it, with a PM from the railway company.

It was estimated 14 months of work and we took 11 and all was working wonders. We had ton of fun doing it because also their PM was a cool guy and we did an awesome project and codebase was a jewel. The difficult thing you couldn't grasp if you read the code is if you don't know how railway systems work and that's the only difficult thing.

Sight, there people is macking me sick of this job

So, while working on a story, I noticed something which the lead dev did that is now giving me problems.... and he's offline while in another building.
Ok, I'll just contact our PM to see how much is due today (visual happy path only or API call is needed too)...same state as lead dev.
Scrum master, the person who's in charge of contacting anyone... no flipping clue where she's at.

It's great being on such a small team!

ugh, company discussion on WhatsApp sucks. i want to take a leave from this new company i joinedbas i am bored the hell out

the company policy is that we got 16 pl 7 mandatory leaves and 8 emergency leaves. pretty good deal i guess. but as a new joiner, i am on probabtion for 6 months and I can't take either of those mandatory/paid leaves.

i was neck deep in work so could not get time to call my manager. plus had a 1 hour incredibly boring and frustrating call with another 50 yo tech lead from another team who was goin on an on like a 90 yo uncle with his wartime stories so could not think straight.

i sent my manager a "hey a***" at 7.08 pm on WhatsApp.

that's a great shoot oneself in the foot situation. i could not call because it's 7.08 pm, and don't wanna give an impression of a corporate non living dev who makes or supports making calls at odd hours. i also can't dele6 the message coz that would be more awkward

but i had went with the creepy hey text , and didn't wanna keep him waiting, so quickly add anothe message with the context : "i wanted to discuss a small leave related query, will call tomorrow"

another classic shoot oneself in the foot.

the probation guy wants to take leaves? he doesn't have any, what could he talk about it? oh right, i was gonna cheese him to give me an informal permission. but now i made it all formal.

noice :/

We need to go live by this month 10.

Yep, infra is ready in production. You can push the events and see the results right away.

PM: Wow, great. Setup staging we need to test it.

Me: FML, staging machines are smaller, can't even start the program.

So the project I have been working on for the past 5 months was finally released yesterday with only very minor problems, this stemmed from both programming side, and users entering data incorrectly.

It has been a rather hectic 5 months. I've had to deal with crap like:
- clients not knowing their own products
- a project manager that didn't document anything (or at least everything into a Google Slides document)
- me writing both requirements AND specifications (I'm a dev, not a PM)
- developers not following said specifications (then having to rewrite all their work)

But the worst thing I think would be the lack of vision from everyone. Everyone sees it as a "project" that should be get it over and done with rather a product that has great potential.

So with the project winding down, and only very few things left to fix/implement. Over these 5 months I learned a lot about domain driven design, Laravel's core, AWS, and just how terrible people are at their jobs. I imagine if I worked with people who gave a damn, or who actually had skills, I probably wouldn't have had such a difficult project.

Right now I'm less stressed but now feel rather exhausted from it all. What kind of things do you to help with the exhaustion and/or slow down of pace?

HOW to document business logic in code?

background:

I'm a frontend dev for admin system of our company. Often times I code things like: if user choose this product type and that settings then I show some other input field to input. I deal with mostly forms and show/hide UI for user. And after some time nor did user/PM/test or myself remember the logic of what should show or why something do not show.

So I want something to be able to let me write code and business logic along the way.(I'm not asking for API docs or function docs like JSDoc)

Great Thanks

Related topics:

And In terms of this, I would also like to build something to centralize PM's business DOC with developers API/dev Doc and also things like how to test for our test team and etc... basically a unified place to document everything, I think scenarios like these inside companies should exists so I would like to know how other company do this.