Just want to recommend the DevRant stress ball. I wasn't quite sure how to use it (it doesn't come with instructions) but since stuffing mine down the PM's throat my stress level has reduced dramatically.

Attack is the best defence! I read my emails in the morning and figure out whether there's some action for me. When I go and get my second coffee, I drop by the PM's office and have a short chat with him.

Where I am in the projects, whether there's stuff from other tasks or unexpected actions, how long that might take, whether schedules are still OK, whether I need him to take care of some customer communication, these things. Usually less than 5 minutes.

The kicker is that he mostly doesn't interrupt me because I instead interrupt him - unless he is highly busy, in which case he just says "sorry, later", same as I would do.

It's a win-win because I can schedule the interruptions while he enjoys that he doesn't have to ask around.

PM used his wife's data in testing against legacy data.
Discovered she had different social number before they met.
Apparently she was also a he.....

Might be a interesting evening for him.

Here's a true story about a "fight" between me and my project manager...

I've been working as a Frontend developer for nearly two years, managed to acquire a decent amount of knowledge, in some cases well above the rest of my coworkers, and one day I got into a bit of a disagreement with my project manager.

Basically he wanted me to copy/paste some feature from another project (needless to say, that... "thing" has more bugs than an ant farm), and against his orders I started doing that feature from scratch, to build a solid foundation from the very start.
I had a lengthy deadline to deliver that feature, they were expecting me to take some time to fix some of the bugs as well, but my idea was to make it bug-free from the moment the feature was released. Both my method and the one I should be copying worked the exact same, but mine was superior in every way, had no bugs, was scalable and upgradeable with little effort, there was no reason not to accept it.

We use scrum as our work methodology, so we have daily meetings. In one of those, the project manager asked me how was the progress on that new feature, and I told him I was just polishing up the code and integrating it with the rest of the project, to make sure everything was working properly. I still had a full day left before the deadline set for that feature, and I was expecting to take about half an hour to finish up a couple lines of code and test everything, no issues so far...

But then he exploded, and demanded to know why wasn't I copying the code from the other project, to which I answered "because this way things will work better".
Right after he said that the feature was working on the other project, copying and pasting it should take a few minutes to do and maybe a couple of extra hours to fix any issues that might have appeared...
The problem here is, the other project was made by trainees, I honestly can't navigate through 3 pages without bumping into an average of 2 errors per page, I was placed into this new project because they know I do quality code, and they wanted this project to be properly made, unlike the previous one, so I was baffled when he said that he preferred me to copy code instead of doing "good" code...
My next reply was "just because something has been made and is working that doesn't mean that it has been properly made nor will work as it should, I could save a few hours copying code (except I wouldn't save any, it would take me more time to adapt the code than to do it from scratch) but then I'll be wasting weeks of work because of new bugs that will be reported over time, because trust me, they will appear... "

I told him this in a very calm manner, but everybody in the meeting room paused and started staring at me, not many dare challenge that specific project manager, and I had just done that...
After a few seconds of silence the PM finally said... "look, if you manage to finish your task inside the set deadline I'll forget we ever had this conversation, but I'll leave a note on my book, just in case..."

I finished that task in about 30 mins, as expected, still had 7 hours till deadline, and I completely forgot about that feature until now because it has never given any issues whatsoever, and is now being used for other projects as well.

It was one of my proudest/rage inducing moments in this project, and honestly, I think I have hit my PM with a very big white glove because some weeks after this event the CEO himself came to the whole team to congratulate us on the outstanding work being made so far, in a project that acted against the PM's orders 90% of the time.

Client: We want an application such that our users can view the 3D rendering of the building we are constructing for them
PM: That's quite easy, we'll get it done
Client: Oh, and the output should be a PDF document, such that they can view the 3D rendering on a PDF reader on the go
PM: That's not a problem, it'll be done

--Right back at the office--
PM: Hey guys, this is our new project....(rants on)
Lead Dev: (in a world of indescribable world) You mean you agreed to that? That's impossible
PM: Just get it done

I wish non coding PM's asked their devs before agreeing to some alien like features

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

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

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

Ha, this is so true...

Yo, is this devrant or spamspace???

Like, do you even fucking work, mates? Are you a dev? How doesn't a fucking legacy code piss you off on a daily basis? What are all the ways you want to respond to your customer's/PM's abuse? Does your lead dev even know jackshit?

Where did all your quality rants go? Why do you all sound like second graders writing essays for school? Have some passion for your job, and hatred for the incompetence for others!

Now, go produce some quality rants! Funny ones too! Bonus points if it's angry-funny.

Project manager: I haven't seen an automated email go out in a while.

Me: ok let me check. Can you provide me a previous email for reference?

Project manager: no
*Itterate 3 times*
Me: ok, does this template resemble the email you're missing?
PM: no
*End itteration*
PM after 3rd attempt to identify the email they're missing: comes into my office and tells me he's not even going to answer my emails anymore cause I can't find his missing email.

Me: finally nails down the email he's *missing* and there's nothing wrong with it.

PM: doesn't believe me.

I fucking hate bad PM's. Asshole can't be bothered to provide usefull information to save his life then questions everything I tell him and thinks I'm the idiot when it takes me 3x as long to fix/find something.

There are three things in my workflow that I don't like:

1. Feature requests appearing out of thin air.

It's common to be handled work at 2pm that needs to be deployed by the end of day. Usually it's bug fixes, and that's ok I guess, but sometimes it's brand new features. How the fuck am I supposed to do a good job in such a short time? I don't even have time to wrap my head around the details and I'm expected to implement it, test it, make sure it doesn't break anything and make it pass through code review? With still time to deploy and make sure it's ok? In a few hours? I'm not fucking superman!

2. Not being asked about estimates.

Everything is handed to me with a fixed deadline, usually pulled off my PM's ass, who has no frontend experience. "You have two weeks to make this website." "You must have this done this by tomorrow morning." The result, of course, is rushed code that was barely tested (by hand, no time for unit or integration tests).

3. Being the last part of the product development process.

Being the last part means that our deadlines are the most strict. If we don't meet the deadline, the client will be pissed. The thing is, the design part is usually the one that exceeds its time (because clients keep asking for changes). So when the project lands on our desks it's already delayed and we have to rush it.

This all sounds too much like bad planning to me. I guess it's the result of not doing scrum. There are no sprints, no planning meetings, only weekly status update meetings. Are your jobs similar? Is it just usual "agency work"?

I'm so tired of the constant pressure and having to rush my work. Oh, and the worst part is we don't have time for anything else. We're still stuck with webpack 2 because we never have time to update it ffs.

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

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

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

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

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

Let me tell you the story of how a feature request no one asked for got put in an early grave:

PM walks into weekly meeting with a single use case that one user called in about, despite never having this issue during the past year and a half that our app has been in production. PM's boss (genuinely one of the best people i have ever worked with) happens to sit in this particular meeting for no reason other than he felt like he should once in a while.

PM brings up use case and wants to devote 3 weeks' development time and another 3 weeks to test RIGHT NOW while other projects are already in motion. PM's boss speaks up with this: "Listen if this guy is really this upset, we can just tell him to build his own service. All the other end users have no problems with this, so it's not worth spending the resources on, i don't think."

And that is how i went from "this is bullshit" to "i love you" in the span of 20 minutes.

I wish people (pm's) would understand that sometimes it's easier to code something from scratch than to use an existing app that someone found on the internet and has very bad documentation and zero mentions in SO which you have to heavily modify to fit you needs...
And on a not so unrelated note, as Douglas Adams used to say... I love deadlines... I love the whooshing sound that they make as they fly by....

My plan to become rich:

1. Create a library / framework that's really just an easy wrapper for other libraries.

2. Write a bunch of books / courses online teaching this "new" library

3. Market it to overpowered but impressionable PM's who'd fall for anything with the word "inovative" in it

!rant
With all the people around here ranting about their PM's, I'm really curious to see how a PMRant app would look like. What are they complaining about?
Devs that listen to music all day long and never want to be disturbed?
Engineers who talk in long, incomprehensible words?
...TDD taking too long?

PM doesn't understand why we need to make a cross platform application for clients, when we only use Windows.

TGIF

So I have this massive fight with a PM, yelling at eachother for 5 min. Once out of our system we sorted it out, no hard feelings

I wish we had more pm's like him

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

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

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

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

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

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.

husband relays to me his boss laughing when a client made a ridiculous demand and flat out tells him no and all I can think is I wish my boss and pm's were that bold and cool. bullshit.

PM's? Like private messages? No idea, still haven't figured it out. There's still idiots from technical chats sliding in, often with a question that belongs in the very same chat they came from. My Telegram name has now literally "(No PM!)" in it, and a bio that says in all caps "DON'T FUCKING PM ME", yet there are STILL people that don't get it. September never ended, did it?

... Oh. Project managers.

>Be active on telegram
>Be a part of Android ROM building chat
>Sees a noob begging for free server to build ROMs
>Everybody thinks he's a troll and ignores
>Dude PM's me for a free server
>I tell him that admins have free server so PM them
>Dude PM's literally every admin of that chat
>Dude gets gbanned instantly lolol

Am I evil ?

As a dev, I think nothing have made me better prepared or equipped for explaining technical issues and functionality to PMs and board members than having kids and explaining things on their level.

I just found out today , that my pm had mistakenly committed the email id and password of his account(which he probably used for testing) in the public repo in github.
Although he subsequently removed it, I can see it in commit history.

The point is.....
I don't kinda like him...
Any mean ideas....?

how am i supposed to fix anything if they change the priorities on my tickets every 10 sec, like PM's change them, 2 min later MD over rules them and changes them again, so 5 min later PM's change them again because something urgent came up, but then another client starts ringing my MD so that client is suddenly priority

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARG

I give up

Best team experience?

Well, first I'd like to mention that after some more experience in the field since, I realize that this company had some pretty terrible management infrastructure...

Nonetheless, I think my best team experience had to have been during my first programming job because my project manager... WAS A FREAKING DEVELOPER! It wasn't his job to be a developer obviously, but we were a small team essentially developing waterfall style, and he had to pick up the slack now and then for certain issues. The man was a genius and everyone appreciated him because you could talk to him about anything dev related and he would get it. The rest of my team was also very chill too, so it was all in all just a fun experience, stressful as it may have been at times.

I have not since had such a diversified project manager 😟 but then again, not the PM's job to touch code...

I swear to God, Days i feel stupid i Look at my PM's code changes and laugh.

What kind of Fuck Tard creates an api call just to return JSON(true)

And to top it off I pulled the latest after his poisonous stench was added and gave me a broken build!

Serious! D ass clown put in a variable with the same name twice, does this buck not build before he commits?

Im starting to believe that this is a hidden camera show where they pulled a fucking mental patient out fking looney toon land and gave him a PM job in a tech company!

Lots of people seem to have awful PM's, so I just thought I'd express appreciation for my PM (who I found out last week goes to my church, which was cool). He regularly asks questions about how our system works so that he can be constructive in directions instead of acting like he knows what's up. Woo Tim! Ok feel free to go back to negativity time

PM's latest modification on my code:
deleted log
deleted my name from author comment

Know what really grinds my gears? The fact that at many companies, PM's and QA people aren't required or expected to have even a basic level of knowledge, making communication pretty unpleasant. Even having a grasp of relevant vocabulary would make things so much easier.

Combine this with the bedside manner of a barn-raised sociopath, an ignorance of human and technical capabilities in general, and we have several good reasons to stay at home "sick". What the hell do I keep getting myself into?

All i want to do is write code. Give me time, space, and stop bothering me so often and I can fix the shitty outsourced code. I can do it, really. I can write a ton of resdesign docs and improve so much shit. But I can't do ANY OF IT BECAUSE THESE FUCKS ARE ALWAYS PAWNING OFF WORK ONTO ME AND REFUSING TO LET ME GET MY HANDS DIRTY.

Stop asking me to email people. Stop asking me to update documentation that isn't for my features. Stop bothering me. Stop. Fucking. Bothering. Me. All. The. Goddamn. Damn.

Stop it stop it stop it fucking stop. I don't care about the PM's dumbfuck braindead statements and always wanting to pick a fight with me. I don't care that x environment is down. I don't care that your shitty overseas programmers can't tell their own ass from their head. I do care that I have the skills to fix it if you would give me the fucking time and space.

Instead of having me do all the mundane tasks that your shitty ape programmers could do overseas, let me have some fucking room to breath and I can fix this shitty fuck of a project and Maybe I can save it before it collapses on itself you dumb fucks

Holy shit im pissy today

Happy new year from Denmark.

Hope your year will be full of great projects with success and without terrible PM's

Fuck it, fucking fuck it.

Consulting company, been here for 2 years, had some decent projects (surprise, only those that me and my coworker started from scratch), but OMG the fuck ton amount of bizarre code I've seen is just mindblowing.

Everytime I start on a project, spend days improductive because the stack won't fucking work.

We use some frameworks, but the creators of the projects said fuck it, why would we follow the framework guidelines if I can create a supersmart way that nobody fucking understands way of doing things. I mean, It will look smarter and so nobody else can touch this shitty code.

I hate that the most praised developer is the guy that created most of this shit, and his nº 1 skill is moving Jira tickets to the correct state, tracking time (PM's love this, I hate it) and blocking my fucking merge requests because I left an extra blank line, dangling comma or whatever the fuck else, he's like a human linter.

Dude, the code is a piece of shit, my dangling comma is not going to be the problem! And if you really care that much, setup a linter or something.

Fuck this, I'm quitting this week.

Am I the only one who is working on a different project every day? And they're not small projects. All medium sized e-commerce sites (Magento 1&2) with tons of custom made functionality.

Soooo counter productive...

For some reason our PM's think it's the most efficient way to do it this way, even though we said numerous times it causes the opposite result. Having to switch to a different project every day and constantly picking up where you left a week ago is so frustrating...

The worst of Agile and Sc(r)um: All those people knowing the right way(™) to do it. Endless discussion about useless tooling: the proper use of the custom workflow in Jira, on when and how to create sub tickets. The hour-less meta-discussions on what should be discussed where and when (what's subject of the backlog refinement, retro, etc), the roles: the PO's, what he should do, cannot, the PM's. Who is allowed to pull a ticket to the sprint or not. How many reviewers need to acknowledge a pull request. To and fro. Pointless, but fought with heart and blood, full of sound and fury, signifying nothing.

And everywhere I hear: "In my previous company, we did Scrum like.. and it worked perfectly!"

Some of you might remember my rants on Mr. Gitmaster, with whom I thought I'd made my peace. Guess what? He's now a team member and turning into Mr. Agile - a more severe reincarnation! As our company starts flogging that dead horse of Agility, he seems to feel strong tailwind. Our team lead would constantly cut his monologues, but he's now on holiday, so we have no escape from the never ending: "In my previous company..."

If it was so great, why didn't you stay?

We are not allowed to pull a ticket to the sprint unless every team member is notified? I don't fucking care. If our software fails on customer's machines and I can fix it, I will do if there is a ticket, if it's in the sprint or not. Screw Scrum, if it is getting in the way of it. You can waste your hours discussing horseshit, I want to sit at my desk, deep in the test-compile loop and ship some fucking code.

my boss some months ago: so there is this new project, and we're planning to slowly fade in and gradually increase the time you guys work on this project

new pm last week: welcome to the project, you're now 100% allocated to the new project, that's your highest prio now
me: ...what about the other projects? they might have questions xD
pm: don't worry about that, dealing with that is not your job

my boss this week: yeah no, the other releases are most important for our company. the new project needs to be subordinated and has lower prio, at least lower prio than critical and highly prioritized bugs.
me: so.... who decides which items from which projects i shall prioritize higher than the new project and how much time i shall spend on them?
my boss: it is your job to talk to people, give them estimates and tell them how many items you can work on, so they can decide which items they pick

so basically i'm having the feeling that i need to manage myself here. it will be fun to attend the new project daily standups and tell the new pm all the time that i couldn't do anything because i had no time. anyone else with this experience? is this normal? actually i liked our new pm's attitude "dealing with that is not your job". i should have known it was too good to be true ^^'

Our PM's reminder.

I genuinely hate when people come up to my desk with our app up on there screen and just shove their screen in my face.... yes use your words buddy you can do it.

just got off work,... ANOTHER DAY SPEND TRYING TO FIGURE SOMEONE ELSES PROD ISSUE....

Doesn't help when my PM's like did you figure it out yet, did you figure it out yet?

Why am I cleaning up other people's shit....

Too many projects, too little time and didn't get a raise. So I now work on projects that people I like ask me to. Ignoring the other pm's while looking for a better job.

My main area of focus is consistent therapy from working with PM's.

In other news, I work on the frontend design and development of internal web applications, good times.

Kinda !rant, but still..
Most professional devs have or have had PM's/KAM's. I've had quite a few,, most I've really liked.. Now I have an issue thought, I like one a little too much,, correction there's no little about it, I fucking love her.. We do spend some time together outside of work as well, and she's become a very close personal friend.. She's really easy to work with and really good at her job, so we make a shitty working situation livable together.

But; of course, I want more, but not ruin anything,, And most of all not make her working situation uncomfortable.. I'm pretty sure she don't see me the same way..

Question: has this ever happened to anyone else? How did it turn out?

Yes, I realize the irony of asking relationship advice from the stereotypically least social group of all..

Oh, and to top it off,, my other closest friend, also works with us, and they know each other from before.. So it's kinda hard to talk to her about it..

I swear this is the PM's first time experiencing a scenario where you fix a bug and two more pop up.

"ThIs ShOuLd Be SuPeR sImPlE, gUyS"

My parents don't understand, my brother and sister in law are PM's

Time blocking my calendar with busy items so I can limit the amount of meetings PM's can invite me to. Works well and helps me stay of task.

!rant I'm lucky to work with 2 of the best back-enders in my career. We were royally pushed/screwed over today due to PM's last minute demands for a phone app that they were demoing to 1000's at a conference. Guess what, certain elements broke. But the guys jumped in to get the API fixed. It's a bit much being the only phone dev on the team but with such strong backend support, it makes it a pleasure to come into work. You know who you guys are. Thank you. Remember a little support makes all the difference in the workplace.

If PM's ruled the world nothing would ever get done.

That moment when product team ask to revert back to the old version of app after 3 weeks of development because of pm's miss communications.

// long rant sorry

A few jobs ago I had a meeting that was scheduled for 15 mins. It was not going to be a bad meeting. I was looking at the people that were invited a few dev's, few pm's, and this one guy (Fuck!!). This one guy we will call him R.

So R is a pm but not just any pm he is the pm that will keep asking why like a 5 year old trying to understand how a car works. To top it off he loved to debate in the work place anything and everything. How something worked or why something was the way it is.

So this one meeting was about a project that I had started on my own and turned in to this huge project. I was super excited it was one of those project that you are excited to work on and love to add new things to it. The meeting was to talk about how it was going to be used and what customers sites this was going to be added to in the coming weeks. 15 mins not bad.

Well the meeting comes we finished in about 10 mins I was trying to get out of the room before R started. Well I waited a little a little to long and sure enough he asked the question. "What about this drop down?". Instantly I thought "FUCK!!! Here we go." Now I don't remember what his exact question was about said drop down but it ended extending the meeting by another 30 mins with me almost cussing him out and walking away.

There was a heated debate about this thing and R continuing to ask questions and want to debate this. I was only saved by the lead dev and lead pm say that they think that this is something that could be talked about at a later date. Lucky for me I was leaving the company in the following weeks.

Upper management has a huge meeting and decides NOT to merge in buggy or incomplete or untested code just because it's the due date (you know, quality over quantity? And an attempt to cut back PM's unrealistic expectations)
2 sprints later: "So we're going to go ahead with the merge. Yes, we know the feature isn't complete, but we promised blah blah blah"
So much for that <.<;;

Argument in the office today when the designers went rogue, ignoring the PM's agreed plan with the client and started mock-ups for what they thought would look better. Boiled down to "No. Just stop that and do what I asked, you're wasting your time." vs "No, we're doing this. I'm a designer, I know this will look better."

Anyone else had issues with designers trying to take charge?

Ok, new to Twitter . Kinda liked it, followed some good techies , but i am quite confused in using it.. can someone help?
1) how to edit your tweet? Like if you did a typo or just need to change some text
2)when i visit it after a few hours( say 4 ) it shows 'incase you missed' , i press it and it will take me somwhere down. What's the meaning of that? All the messages above that message are of last 4 hours?Am i supposed to swipe up or down?
3) WHY THE FUCK AM I SEEING EXTREMELY STUPID 'PROMOTED' TWEETS HAVING MY PM'S RANTING AND OTHER POLITICAL TALKS WHEN CLEARLY AM A DEV WHO HAS FOLLOWED THE GOOD, TECH PAGES? How to just unsee those?somebody please lend a good ML algorithm to this weirdly naïve site called Twitter .
4)any good tech pages to follow?(general tech related news or datasciences)

Thank-you

I set up this Internet of Things Raspberry PI station to monitor the PM's but they did not think it was funny.

*New defect*

Designs are confusing and use bad practises. Multiple buttons achieving the same task. The dev team, the BA's, PM's can't understand the current flow.

*Defect closed*

"Design happy with current implementation"

Putting up with PM's...

Any of you guys that also faces existential crisis every sprint deadline? Not being able to fullfill PM's expectations is horrible.

As lead dev of a team, should I be writing estimation docs (more like novels) for new projects? I'm even told it should be at least n pages like back in frickin' high school.

Am I in the wrong for thinking it should be the PM's job to communicate with us devs and then write these useless docs to present to stakeholders, and he's just making me do his job while he's doing whatever else at home?

This is a genuine question. Am I being a lazy dick here?

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.