News for hackers. Stuff that matters.
Re:The non-linearity of productivity by dasmoth on Saturday July 22, 2017 @10:34AM (#14827413)
Agreed. And I'm increasingly tending to think that the stuck-thinking-about-the-tricky-stuff phase is the part of the game I find most satisfying.

A lot of textbook management techniques seem hellbent on trying to force steady productivity instead of punctuated equilibrium. Not the recipe for a satisfying environment.

Re:The non-linearity of productivity by GuiA on Saturday July 22, 2017 @11:00AM (#14827521)
I once had a manager ask me to email him a progress report every day; and every hour or two, he'd make a point of interrupting me to ask me "so how's <current_task> going?"

Sounds like something straight of office space, but that was my life for a while. Least productive job I've ever had because of that (well, and the myriad other little toxic/passive aggressive behaviors he had).

He had a Stanford MBA too, which convinced me of how useless MBAs must be. Because if you make it through one of the top programs in "business administration" in the world and still manage like that, you might as well have an MD from Harvard and still believe bloodletting is a viable treatment for illnesses.

Re:The non-linearity of productivity by dasmoth on Saturday July 22, 2017 @11:50AM (#14827756)
I once had a manager ask me to email him a progress report every day;

This seems to have become very nearly normalised in the guise of daily stand ups. Some would argue it's less intrusive if it's for "the team" rather than for an individual manager, but I'm not convinced myself.

and every hour or two, he'd make a point of interrupting me to ask me "so how's <current_task> going?"

Similarly, in environments where tasks are getting broken down into tickets that are only expected to take a few hours, there's a similar level of oversight (although hopefully a bit less disruptive than hourly shoulder-taps, I agree).

Re:The non-linearity of productivity by everyone on Saturday July 22, 2017 @12:34PM (#14827961)
I worked for a startup that grew up around me. We started without any project managers and such and they got introduced as the team grew and grew. I would just make tasks like "figure out how to do X", "look into this framework Y", "write a really good SO post for the bug we came across in library Z" . Worked fine, tho the PM for my project was sound.
Re:The non-linearity of productivity by wry_discontent on Saturday July 22, 2017 @06:38PM (#14829822)
I'm at the first job I've ever had that didn't do daily standups and it's liberating. I've never been more productive at work.

Maybe once a week my manager comes by and asks me how something is going. I give him a high level sketch and a time estimate. He goes along on his way after that.

Re:The non-linearity of productivity by ww520 on Saturday July 22, 2017 @12:00PM (#14827809)
He's treating you like a cog in a manufacturing plant, which he can "optimize" at will. MBA programs often teach people that. He doesn't understanding creative work or thinking heavy work "appear" to be non-working but it's essential.
Re:The non-linearity of productivity by erikpukinskis on Saturday July 29, 2017 @01:27AM (#14879654)
Why does asking how someone is doing mean you're a cog, or that you're in trouble if you're still doing research?

Part of what a supervisor does is track progress across a whole team so they can keep other parts of the group appraised.

Another important job is helping people make tradeoffs between perfect and done as the situation on the ground changes.

Both of those require asking "how's it going?"

Re:The non-linearity of productivity by ww520 on Monday July 31, 2017 @09:53PM (#14897334)
> I once had a manager ask me to email him a progress report every day; and every hour or two, he'd make a point of interrupting me to ask me "so how's <current_task> going?"

Asking a developer's status progress everyday or every hour? That shows the manager has absolutely no clue how development works. Period. Developers don't need a manager to "help" them make tradeoff on a daily basis. Developers need managers to back the fuck off to let them alone to concentrate on the mentally taxing work at hand.

Re:The non-linearity of productivity by teyc on Saturday July 22, 2017 @05:55PM (#14829616)
Here are some possible explanation for the behaviour. There might be other urgent fires burning for the past week and he is getting nervous and trying to figure out whether he needs to reschedule. He also has to manage up and set expectations when the whole project is going to be done. He might be concerned you are gold plating an otherwise simple task. He might think you are stuck and trying to figure things out on your own. You could help him by letting him have a sense of where you are, and whether there is something more pressing that he needs to talk about. Perhaps he has access to people/equipment/money that can accelerate your work.
Re:The non-linearity of productivity by bojan on Saturday July 22, 2017 @07:12PM (#14829946)
The manager in question, were he a good one, should also be able to clearly and timely communicate if any or all of these things apply.
Re:The non-linearity of productivity by eru on Saturday July 22, 2017 @01:10PM (#14828150)
I guess the MBA is there to facilitate your professional development, not to make you more productive.

And what you have to do in order to look good to your manager or manager's manager's manager is different than what you have to do to be productive. Your boss was perhaps just doing the former?

Re:The non-linearity of productivity by heymijo on Saturday July 22, 2017 @11:36AM (#14827683)
"A lot of textbook management techniques..."

Can you unpack this? Would like to hear more.

Re:The non-linearity of productivity by lordnacho on Saturday July 22, 2017 @12:33PM (#14827957)
I have "management" in my degree title, from a world famous uni. Basically a good taste of an MBA, since an MBA there is a year.

Very little of a management course is about how you treat people. If anything, you are left with Taylorism and the lingering question of how it relates to knowledge workers. Because Taylor was basically measuring factory workers' performance, whose contribution is to do some repeated action over and over. If that sounds like treating someone like a robot, it's because it is.

This is not to say nobody has thought about this. HBR will run an article now and again about HR issues. But there's nothing especially compelling where you'd be able to find a root cause, find a specific solution, and implement it. If it was, management wouldn't be magic, it would be engineering. And the practitioners would not be paid enormous sums for doing the impossible, they'd be paid moderately well for being ordinarily competent.

Most of the things on the course are really not that different from reading the FT regularly. So-and-so company found their product wasn't appealing to young people, so they tried X and it was a massive success. Doesn't tell you what to do if you were to run this firm, but after you've read a few you'll think you know. Case studies are a case study in post-hoc fallacy.

Then there's a bunch of supposedly advanced financial stuff, which if you're an engineer you'll laugh at. Ratios, really? Interest rates? If you do a proper finance course there will be real things to learn (stoch calc doesn't show up much in engineering), but not in the business school.

And there's a few useful things, too, like the history of capitalism, but nothing that develops a proper intuition or method for a field of problems like engineering does.

Re:The non-linearity of productivity by heymijo on Saturday July 22, 2017 @05:24PM (#14829466)
This just, kind of blows my mind. What is management if not people? I mean Drucker's very definition of management is the idea of organizing a group of people to drive towards a common aim where you learn how to make each individuals' strengths effective and their weaknesses irrelevant.

Deming was adamant that psychology had to be a pillar of management. Why? Because people!

I'm curious then, who were the authorities/what were the theories (if any I guess) that were used for your management degree?

- Also, why am I talking about Drucker and Deming? Because if I drew a family tree, I could trace at least some aspect of nearly any management idea today back to them (lots of amalgams out there these days). There is one big caveat though, lots of management practices today have neo-Taylorism embedded into them that most people are unaware of.

Re:The non-linearity of productivity by lordnacho on Saturday July 22, 2017 @07:24PM (#14830009)
> I'm curious then, who were the authorities/what were the theories (if any I guess) that were used for your management degree?

It felt like a very sporadic hodge podge of names. Porter's five forces, tech cycle, a load of case studies.

That's looking back a decade later, so maybe I'm missing something.

But it all seemed very vague. I remember thinking how on earth did Porter get his name on a "theory" when really that's just common sense? A company is going to tend to have customers, suppliers, entrants, and substitutes, and internal rivalry. I mean why would you think otherwise? Also, creating those categories is no guarantee that you're not going to miss out something.

If anything I've learned more about management from reading agile type stuff like Scrum, because those kinds of things are usually grounded in experience from a specific industry, with specific pain points and specific solutions.

Re:The non-linearity of productivity by thaumasiotes on Saturday July 22, 2017 @08:35PM (#14830241)
> I remember thinking how on earth did Porter get his name on a "theory" when really that's just common sense?

This is how I've always felt about "De Morgan's Laws". There are two, and they state:

1. If it is not the case that two things are both true, then at least one of those things is false.

2. If it is not the case that either of two things is true, then both of those things are false.

(Actually, they are logical equivalences, so they also apply in the other order -- "1b. If at least one of two things is false, then it is not the case that both things are true.")

I'm pretty sure both of those "laws" were known well before the nineteenth century.

Re:The non-linearity of productivity by dasmoth on Saturday July 22, 2017 @01:09PM (#14828136)
Thanks.

Ultimately, I think I was referring to the Taylorist aspect.

There's also a philosophy that I've seen labelled as "teamism" and which seems to form the basis of methodologies like Scrum. I'm not sure teamism is quite the same thing as Taylorism -- but it shares the same distrust for individuals working on problems without near-constant oversight.

Re:The non-linearity of productivity by crdoconnor on Saturday July 22, 2017 @02:09PM (#14828473)
Scrum has elements of Taylorism: team members are treated as interchangeable cogs to be assigned units of work and it has a crappy "productivity" measure built in (velocity).
Re:The non-linearity of productivity by epalmer on Saturday July 22, 2017 @05:22PM (#14829451)
I don't measure velocity in the scrum team I coach. And people's skills are not interchangeable but we do want most of the team member to be able to perform the easy stuff. A front end developer is not interchangeable with a backend developer. Having a task card about thinking through a design is always welcome. We use standup to have face to face conversations.
Re:The non-linearity of productivity by eru on Saturday July 22, 2017 @01:12PM (#14828158)
> And the practitioners would not be paid enormous sums for doing the impossible, they'd be paid moderately well for being ordinarily competent.

That's an awesome description of where we should move management to, hopefully. (Same for programming, marketing etc.)

Re:The non-linearity of productivity by dasmoth on Saturday July 22, 2017 @11:44AM (#14827723)
"Textbook" was possibly more a nervous tic than a statement of fact -- I've not read a lot of management textbooks...

However, whenever I see generalist managers at work, there always seems to be massive emphasis on schedule risk and at least in organisation I've been in, the proposed mitigation is always regular status meetings (and perhaps other forms of check-in as well).

This seems to have been almost entirely normalised in the software world, particularly anywhere that's gone down the agile pathway: fine-grained tickets in an issue tracker (or possibly cards on the wall -- but haven't ever seen that one in action) and a daily standup with an explicit goal of making sure nobody is "spinning their wheels".

Re:The non-linearity of productivity by heymijo on Saturday July 22, 2017 @05:18PM (#14829435)
Thanks for the explanation. I've got a working theory: most people, even managers, even lauded ones, don't know much about "textbook" management. They mostly manage how they were managed, some picking up a few things here or there.

It's recursive.

I've worked in businesses, started and scaled my own, and have also been a teacher (k-12). We all go to school for at least 13 years and internalize what "teaching" is. Most teachers' classrooms end up looking like ones they experienced even if the "textbook" lays out massively different ideas. It's the same problem as management.*

We all also work, and internalize some conception of "management." Thus, most manage they way they were managed.

Throughout my career I've worked with over a hundred different organizations. I can read about many more in the news and case studies. I see very little in practice that aligns with hardly any of the big ideas in management that I've learned from the likes of Drucker and Deming.

*It has not gone unnoticed that education is our first experience with management. Often it has Taylorist, Theory X, command and control roots. In contrast, the great teachers I see have a lot in common with great managers and management theory (see Drucker, Deming).

Re:The non-linearity of productivity by sverige on Saturday July 22, 2017 @02:43PM (#14828651)
> However, whenever I see generalist managers at work, there always seems to be massive emphasis on schedule risk and at least in organisation I've been in, the proposed mitigation is always regular status meetings (and perhaps other forms of check-in as well).

I think the reason for that behavior is because they don't want to be caught unawares when some deadline is missed. In other words, one of the metrics they are measured on is meeting deadlines, which of course pushes schedule risk to the top of the pile. There's merit to that, but that has to be balanced with the quality of the product.

The blind spot for such managers is that constant check-ins and updates on progress too frequently interrupt the flow of people who need time to think things through. Adding pressure at the wrong point can possibly ruin the quality of the final product.

Re:The non-linearity of productivity by ScottBurson on Saturday July 22, 2017 @05:08PM (#14829386)
I have a completely different way of mitigating schedule risk: find the most difficult, unpredictable subproblem and do that first. I guess it's not quite fair to say that I've never seen a manager pick up on this idea, but it still doesn't seem to have become their first-choice strategy.
Re:The non-linearity of productivity by mikhailfranco on Wednesday July 26, 2017 @06:19AM (#14854959)
An experienced architect will always do this. Often the most risky subproblem is the one that is least understood (unknown unknowns), which needs to be investigated, even if it turns out not to be a great risk. In agile-speak this is called 'spike solution'. Also see lean architecture methods, such as:

- 'Just Enough Software Architecture', by George Fairbanks.

- 'Risk and Cost Driven Architecture', by Eltjo Poort.

Re:The non-linearity of productivity by eru on Saturday July 22, 2017 @01:13PM (#14828165)
One problem is that 'agile' has been taken over by management types.