Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "micromanagement"
That's it. I fucking quit.
Over a month of unpaid work, developing your stupid course, only to get a high-quality outline rejected because "it's not what we wanted" again.
First outline, fuckers ask to do something with a Raspberry Pi and Yocto. Fine, but no Yocto as I don't know anything about it and the coworker doesn't even have a Raspberry Pi to flash the images on. Micromanagement guy (god I hate that word) agrees, fine no Yocto then. So no Yocto it is.
2 weeks later... Course outline is finished. Review stage.. rejected. Needs moar Yocto.
Fine... I'll include Yocto. Coworker was put off the course, I'm exclusively on it now. Time to do it well and get my feet wet with Yocto.
2 weeks later... Course outline is finished and looks pretty good. Review stage.. rejected. Needs less Raspberry Pi. Do it without the Raspberry Pi.
An embedded systems course whose core component is that fucking Raspberry Pi. Omit it they said. WHAT?!!
"Oh yeah but there's this other course that's selling like hot pockets, we can just redo that in videos. Make it more like that course."
You.. you can't be for real, can you? If students want to take that course... What makes you think that they wouldn't just pick.. *that damn course* then?
"But hey" micromanager said, "don't loose hope and confidence, I'm here🤪"
🤪. That describes your level of competence pretty well, you stinking piece of apeshit.
Go back to your micromanaging, at least you don't completely fucking suck at that.
2 times rejected because YOU fucking company's board can't describe your desires in a course properly. You know what, I think I'm starting to understand why web devs keep on complaining about indecisive clients now. Because you know company's board, you seem a lot like those clients from hell. Eat shit.
The Micromanagement God. The guy would come to the office 64 times a day, go behind my desk, stare at the monitors for a while and ask what am I working on.
He would sometimes ask for explanation of how something works because he never saw it before and then give me advice on how to use that thing he never saw before.2
I was hired by a company where a senior / dev lead recommended and interviewed me. He said to me that he was tired of broken processes, false promises to customers, micromanagement, pressure, etc. and told me that together we would improve these things. Few weeks later things didn't get any better and I told him that from what I had witnessed, he wasn't making things any better by saying in meetings that this and that would be easy to implement and would only take few minutes - that he was raising unrealistic expectations on the business side, which was clearly one of the reason the business had these high unrealistic expectations and caused all this pressure and micromanagement. He took this the wrong way, quit and hasn't spoken to me or his colleagues since. I didn't at all mean this in a bad way, because I highly respect and look up to him where he's one of the nicest guys and one of the best programmers I've ever met. Was I in the wrong here? What should have I done differently?15
CEO of previous job, only reachable by email, coming to the office twice a week at best, business trips at no notice, answers every third email, addressing the dev team:
"You need to plan better. A lot of the delays and bugs are due to poor communication and unaddressed issues."
I don't miss that job.2
Do developers have to get everything approved from the product manager. Even the name of a function and explain why you chose to pass something as a parameter? Isn't this micromanagement?19
We had a support Trello board set up. Slack with automated messages. Jira integration. Translation service integration. And a meeting. All clarifying that it's not okay for other company members to barge in and make requests or ask questions which would interrupt our work flow.
One day, the fucking boss does this to me. My headphones were on too. And he pulled this shit, asking me questions about translations on the web app. There is a ticket for it. We have a slack for it. We have an entire platform to handle everything related to translations.
My biggest issue was that he's the boss, the CEO, of the company. You're supposed to be leading by example. Cut the micromanagement shit and back off.7
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?"1
Terrible week. Micromanagement killing all progress. The only positive note this week is that we got a new scent of soap.
Thank the gods I like citrus...4
Many years ago I had a job as web developer at a small promotions company. The owners loved micromanaging their 7 employees, down to the minute. Work started at 9am, if you were even 1 minute late, you were deducted 1 point. (Even if the weather was bad) Once you were at 10 points, you were disciplined by being given an unpaid vacation day. (Thanks for the day off!). At 12 points, you were fired.
It only took me about 8 months before getting my day off. Somehow I was able to time it perfectly to a job interview at a large company.
Luckily I got the job, and purposely was late the next two days so when they told me I was fired I could tell them I already got a new job (thanks to their 10 pt rule) and I'm out anyway.
At the new job, I'd often drive home and nap on my lunch hour. No one would notice if I came back an hour and a half later.
The owners of the 1st company divorced a few years ago. The husband and I have actually kept in contact over the years. He's a cool guy when you don't work for him. He invited me to a Green Day concert over the summer. Probably makes the above story a little less cool, but at the moment, I was burning bridges!1
So I have a fucking groupmate for our degree project and he's been constantly bugging on my neck asking me to do things. The problem with him is that he constantly reminds me of the things that I should be doing and he seems like he wants the thing to be done all himself. Basically, he doesn't trust me that I could deliver whatever he asks me to do. He keeps on micromanaging me from time to time and he seems like he wants to control my life altogether! Fuck this.
Oh and another, whenever he asks for opinion, whatever you say doesn't even fucking matter. He dismisses it immediately anyway and goes with whatever he thinks.
Seriously, fuck this!!! I can't keep calm and I need to constantly check on my posture! (Forgot the right term...) Uhhhh halp6
Put me under pressure and I’ll produce the best code I’ve ever written.
Put me under a microscope and I won’t produce jack shit 😂😬6
Is it weird that I avoid forced socializing in my office? On mondays in the mornings we have a breakfast where essentially people gather (its a small gathering with 3 founders 1 cto and 3 employees), they have some pastries and juice.
And then they are talking about some bullshit for one hour.
For me personally monday mornings are for coffee and contemplation. I dont want to listen how boring their weekend was and try to impress them with my boring weekend. All that interaction feels so fake shallow and politically correct.
Dont get me wrong I care about my colleagues and what goes on in their life, but this forced monday morning and forced friday afternoon 1 hour gatherings are sooo draining and useless for me. I feel that only couple people are actually open during them and others are never sharing about their life, so esentially that gathering becomes an interrogation of 2-3ppl and topic revolves about them.
Gosh its draining. Gonna “be late” tomorrow again bcs I dont care. I would rather come in and go straight to work.
Having a beer after working means 100 times for me than that shallow and pretentious forced socializing that these guys are pushing so hard. Almost feels like micromanagement on personal level.5
The CEO at my previous company used to schedule two meetings, spanning 1-2 hours, per week. He would also schedule several smaller meetings throughout. A real micromanagement type.
CEO: "Why aren't you going to meet the deadline?"
Also note, we were a three-man team and were not consulted about a possible deadline.
Best boss is my current boss(es). They don’t breathe down my neck, no micromanagement, and basically let me outsource anything I don’t want to do or don’t know how to do. I work 100% remote on my own schedule (except for a few core hours) and every time I ask if they have any problems with my work or feedback for my improvement they say they couldn’t be happier. If I make a mistake, they don’t rake me over the coals and they just let me handle the problem.
I’ve been waiting over 20 years for a job like this one. Why can’t it be this way for everyone?3
Sooooo our department boss (the CTO) just announced his resignation, handing over his responsibilities to the lapdog of the CEO (who is very fickle on process micromanagement). Seeing as our offshore team was the CTO's idea, we're kinda expecting retrenchment to hit us in a few months once said lapdog starts throwing out our (soon-to-be-former) CTO's initiatives and projects for her own...
Quite frankly, I wish we'd get redundated now instead of later. I'm starting to hate my job (an increase from before, when I simply began to dislike it) because of my team lead's incompetence (she can't even attend a meeting without hijacking it for some other unrelated topic/issue) and lack of transparency (she never shares everything, keeps a lot of critical knowledge to herself). You can smell her lack of trust from miles away.
Anyways, yeah, I'd like to get retrenched/redundated please. I could use the money, honestly.
My boss (who's in a different country) just joined our internal Skype group where most of our daily information is spread. She honestly thinks we work faster when she's asking questions about progression on stories via Skype.
Why doesn't some managers trust developers? >.<5
Been lurking for a while and has been refreshing to see I'm not alone in some of 'interesting' issues I face day-to-day!
I am in a situation where I am a technical lead, but any architecture changes need approval by the MD, any software (free, obviously paid for is understandable!) needs signoff before installing, even if it's to see what it's all about! Essentially anything I should be responsible (no matter how minute) needs signoff before I can even attempt anything.
This is my first time that I am in a role of this level, but it seems like I am responsible for a lot but don't have much control over what I can do about it, is this normal? To me it just seems there is no trust in my judgement, which is not justified considering I'm only just being put into the role!6
I keep seeing two philosophies bash heads at work.
1. "Hey, use these tools according to idioms and best practices for that tool. We worked hard getting this to work predictably, and it depends on you doing things consistently."
2. "Go pound sand, I want to do what makes sense for the project. To hell with your nazi conventions."
They're both right, and they're both idiots.
#1 is right because precedents exist for a reason. People did a bunch of stuff with their tools and got things to behave reasonably well, showing mastery over a stack. There could also be actual legal- and infosec- related reasons to following a protocol for changes, and ignoring those precedents invites disaster.
#1 is an idiot because there's a fine line between enforcing consistency and micromanagement. If the idioms they confuse with architecture are making it harder for other people to work, then they need to back off and let context, not ego guide the conversation. Good architecture should enable and encourage people to change the software in radical ways.
#2 is right because Context. Is. King. No project should shape around a tool. Tools should simply and objectively obey their users through good and bad use alike in service of the project. A culture that would oblige you to change for the sake of a tool is not an engineering-driven culture, it's a culture driven by self-anointed thought leaders who learned everything they know about software from Medium.com and Smashing Magazine. To enforce idioms and consistency blindly is turn the best practices found so far into the status quo that prevents change.
#2 is an idiot because there's a baby in the bathwater, which is some of that context they so treasure. By getting defensive with #1, they forget that the more they change, the more the team has to re-learn to adapt. The worst case is the cowboy that rewrites the implementation from scratch, causing QA to re-do ALL WORK and causing engineers to drop everything for one person's way of doing things.
The compromise is hard, but here's what I think it entails:
- Context really is king, but frame your changes in terms understood by how the team already thinks about the project; and
- Make those changes work independent of the tech stack on which they sit.
Doing this requires a solid understanding of, well, SOLID, and lots of patience dealing with ego and red tape.
This may seem obvious to you, but I'm so tired of watching the arguments at work about this degrade software quality and the end-user's experience.1
Boss just repositioned the security camera we use to watch the front door right behind me, with perfect view of me and my monitor.....micro manage much....1
I see managers micromanage by having a junior developer to track the things people are doing. Micromanagement is truly a trickle down issue. They learn it from their managers and so on.1
The customer wants to drop Agile in favor of their in-house development methodology. They just sent an e-mail describing it...
I think my team needs a room decorated with cotton flowers and small huts to get into the right mindset.1
Every day, the SM likes to come by the dev table and ask what our updates are (stalking jira + dev slack channel is apparently too boring).
He comes by every 2 hours.
Each time asking about how close I am to finishing not only the current feature but the other stories I have to work on too.
The other stores are not in progress, what makes you think I was working on them in the background of what I'm currently working on?
Doesn't help that we somehow keep adding stories mid sprint,
How to deal with micromanagment?
I just lose it when the team leader checks on issues on a hourly base, And dont get me started on the scrum master who checks the sprint status twice a day.
I can't quit this work but I'm losing mind here.
H-O-W T-H-E F-U-C-K do i deal with this idiotism??5
Instead of doing work let's all just have a meeting then email about the work just so the managers can look like they're doing something. Loving the micro management.
I am reading third book
“The Cult of Fog Island” and now I am 100% sure that shitting on employees and micromanagement are forms of cult and sect.
People who do it are narcissistic dumb fucks just wanting to lick CEO or their own ass and get prize for what they didn’t do.
Well fuck them I hope they burn in hell.