5 ms·
> Some product manager/project manager/engineering manager already broke things up into user stories. Those user stories were further broken down into tasks. Th
by crazygringo 14y ago
> Some product manager/project manager/engineering manager already broke things up into user stories. Those user stories were further broken down into tasks. The tasks were then evenly divided amongst all the engineers. Each engineer didn’t have much of a say in it. Some might call this slave work. It was the most unproductive time of my life.
This is one of the central dilemmas. To some people, it sucks -- they'd rather be programming rockstars, solving big problems in a way that's interesting to them.
But in most of the real world, when you've got various stakeholders, a big project, lots of programmers whose work needs to be coordinated, with standards, and you can't get bogged down in n-to-n communication, this is just how it often has to be. Face it, most work in this world is "slave work", if that's how you want to call it (although I think that sounds rather insulting, when you think about how an unfulfilling office job you're free to quit is a million times better than actual slave work).
And part of being a professional and mature programmer is realizing that, look, that's life. Sometimes you will get a job with a big say in how things are done, be super-independent, and it will be amazing. And sometimes you'll look back five years later and realize how it was a great learning experience for you, but you over-engineered it in a language or with a library that nobody could use afterwards, the whole system was replaced a year later, and you effectively wasted a lot of time and money of the company's.
But at the same time, sometimes you do need rockstar programmers, who are talented enough to be given free reign, and they'll produce amazing results, as long as you don't micromanage them, or even barely manage them at all. Different projets are different. And different employees are different, too.
- sherm8n 14y agoBut this is also hacker news -- where people don't settle on normal work. They're bold enough seek out only meaningful work. Either by starting their own company or joining one where they can make a huge impact without the typical fluff.
- onemorepassword 14y agoThat doesn't mean they don't need structure in their daily work. If it wasn't for those kind of people, those who are neither entrepreneurs nor risk-averse worker drones, start-ups wouldn't be able to get any development staff because "less meaningful" usually pays better.
- sherm8n 14y agoAre you arguing that all developers at start-ups can't think for themselves?
- kamakazizuru 14y agothats a bit broad - define meaningful work? - why is it more meaningful to go work at say a YC funded startup - than it is to go work for a larger corporation working in the same space? Lets face it - most startups dont make a huge "impact" - on anything other than the pockets of investors and founders - and that too in a small percentage of the successful cases that get overly romanticized!
- elbear 14y agoHe didn't define meaningful, because it's subjective and unique individual, so it might well be working for a larger corporation. His point was that the attitude around HN is to look for meaningful work as opposed to work that just pays the bills.
- kamakazizuru 14y agowhy cant "just pay the bills" be meaningful? - for more than 70% of the world thats very meaningful. Its also flawed to assume that everyone on HN is someone sitting in the valley with a bunch of job offers.
- elbear 14y agoYou wouldn't call it "just paying the bills" if it was meaningful. Meaningful in this context means something that you would do for free. At least, that's how I define it. That's not to say that 70% of the world's struggle is meaningless. It means survival. Also, you don't have to be in the valley to wish for meaningful work. I'm not and I do look for work that I enjoy doing.
- sherm8n 14y agoI have many friends who are working just to pay the bills. And they hate their jobs. Most people actually dislike their job in some way.
- kamakazizuru 14y ago
- eksith 14y agoThe key problem here is "lots of programmers". Even on a big project, there should only ever be "enough programmers", just enough to get the job done under budget (hopefully) and on time. It's easy to put the burden on the programmer to carry on soldier! But a lot of the burden of productivity is often on the managers themselves. Mangement needs to manage, not cause strife and yet that's what some do. Erik Lukas seems like a guy who's had his act together from very early on and whether he read up or not, he knew how to manage his people. That's a key skill. There's also been a complete cultural overhaul in the community. Programemrs have been spoiled, for better for worse, and maybe we're expecting too much. Jeremy Morgan wrote a post last year that really illustrates this. Well worth a read : http://www.jeremymorgan.com/blog/programming/the-programmers-before-us-were-better/ http://www.jeremymorgan.com/blog/programming/the-programmers...
- sherm8n 14y agoI don't think programmers are spoiled at all. They just know there exists a huge market of opportunities for them. Why shouldn't they benefit from this and find the best possible working situation that would make them happy?
- _aaa_ 14y ago"...Knowing how to actually write code will someday be as rare as those who know how to use a slide rule now..." Well, maybe then they will start paying actual real money.
- sherm8n 14y agoAsk cobol programmers how much they make.
- jeffgorder 14y agoThe key word is coordination. Unfortunately to some it means making a list and making sure every one knows what to do. Here's the goal, here's what you need to do, "make it so." In reality, coordination takes place in the face of constant change. Goals are critical, but purpose and trust are primary. When we know WHY we're doing work, and we trust the people we're working with, then coordination becomes two explicit acts. It is distribution of responsibility as widely as possible, and assignment of the right authority to carry out the responsibility. If you trust the people you're coordinating with, then what and how they meet their responsibility doesn't matter. You can rely on their individual creativity/talent. When change happens, everyone has enough authority to adjust to the change in their own area of responsibility. If you don't know WHY and you don't trust the people you're coordinating with, then slave-labour tactics and task lists will be required, which means the effort is very likely to fail anyway.
- sherm8n 14y agoI'm glad you brought this up. Trust is a big thing in the workplace. Take cross-department coordination for example. You're supposed to trust that another department will deliver what they promised so your project can succeed. I've been in situations where the manager did not trust the other department to deliver. So it was required that we implement our own solution "just in case".