That's why I prefer working on small teams and without agile. I currently work for a government office where I am the only actual coder there besides the interns, and my bosses are pretty well versed in tech stuff and even some programming so they tend to leave me mainly to do what I need to do and only care about the results. And if I can't produce the results they want they'll understand why I can't do it and try to find a workaround with me that still fits the scope of what we need. Meetings are also rare, although I honestly kinda shit myself when I have to present stuff to the mayor or some secretary.
How I manage my programmers: Hey, here is a task; I estimate it will take about four days. Let me know if I am wrong, and don't hesitate to drop in if you're having trouble. I have tried multiple management styles and this is by far the best.
@@koresalivaI see no problem with the way they are doing it. They do ask "let me know if I'm wrong". It is definitely so much better than managers asking you for an estimate and then bargaining on whatever you say. Not sure how bargaining to bring down an estimate will make things any better.
@@koresaliva No, I tried that, but it's not good. I am an experienced developer, and for tasks that I understand, it's best use of resources to have 1 person estimating. For more complex, I have agile meetings. I have had bad experiences with developers when they give me time estimates since it's too tempting to overestimate. Plus, if I am wrong, I will take the blame; if I underestimate the task, I am clear that I am to blame.
When companies downsize they always wonder why they still aren’t making profit. That’s because when they look for inefficient people to fire, they never look at themselves…
So relatable in nursing/medicine, too. For all the documentation the actual patient time is reduced. We should have a channel where we show the reality of all these different jobs and fields- what they are, and what they aren’t
When I first got agile training, I was in a team that did waterfall with good manager. Wasted days in training about scrum masters and agile manifesto and all I could think about was, "this is all just how a good team functions under a good management. Under bad management this is going to suck".
I do general IT and networking... And yet it's pretty much the same. With the added things of doing something critical; server migration, network outage, AD changes. And you MUST drop everything to refill the printer cartridges or paper because "the best sales person evehr" printer isn't working.
Hey at least you get efforts for it. In my ofc pm allocates efforts as if we don't do agile, but expects all the work products and documentation for agile.
I hate that part. Sometimes I try to make a game out of it when it happens. I'll set a timer and say, "Ok what is the small improvement I can make to the code during the 30 min gap?"
And? Is it your company? Programmers that are too dedicated to their passion are the bane of everyone else. This is a job for me. I'll do what is asked and that is it