Earlier quoted context omitted.
Zed is for Zombie.
We're not using the Zed word.
Untitled topic
231–240 of 297 posts
Re: undefined
#232Re: undefined
#233Re: undefined
#234I've always felt project management should just be 1 person going to each programmer/designer on the team and saying "Hi, are you on schedule? Do you need me to clear any roadblocks or clarify any requirements for you? No? Good day to you, sir." That is effective project management. Anything else is just spinning your wheels.
Sharon knew what all good instinctive managers know:
The manager's function is not to make people work,
but to make it possible for people to work.
That actually comes after this anecdote: One snowy day, I dragged myself out of a sickbed to pull
together our shaky sys- tem for a user demo.
Sharon came in and found me propped up at the console.
She disappeared and came back a few minutes later with a
container of soup. After she'd poured it into me and buoyed
up my spirits, I asked her how she found time for such
things with all the management work she had to do. She gave
me her patented grin and said, Tom, this is management.Re: undefined
#235"The path of the righteous programmer is beset on all sides by the inequities of the clueless and the tyranny of evil project managers. Blessed is he, who in the name of achievement and solid technology, shepherds the users through the valley of ineptitude, for he is truly his customer's keeper and the finder of lost solutions. And I will strike down upon thee with great vengeance and furious anger those who would at…
This reminded me of the Tao of Programming that I first read in 1991: http://en.wikipedia.org/wiki/The_Tao_of_Programming
Re: undefined
#236Re: undefined
#237Re: undefined
#238"The path of the righteous programmer is beset on all sides by the inequities of the clueless and the tyranny of evil project managers. Blessed is he, who in the name of achievement and solid technology, shepherds the users through the valley of ineptitude, for he is truly his customer's keeper and the finder of lost solutions. And I will strike down upon thee with great vengeance and furious anger those who would at…
Re: undefined
#239Earlier quoted context omitted.
Nothing really scales. There is no process that will allow 100 hacks to make a Michelangelo, if you want a Michelangelo you're going to have to fucking hire him. If this bullshit really worked then corporate IT departments would be the envy of every startup out there. If your software is late/buggy/whatever the solution is rarely adding people / process. It's usually removing people / process. Process is what allows…
"the solution is rarely adding people / process. It's usually removing people / process" hell yeah.
Re: undefined
#240Earlier quoted context omitted.
I've struggled with how to respond to your comment. You seem to be taking the view that any project that requires more than 5-10 great programmers is inherently flawed. I think this is false. I've worked on very large software systems before, places that had around 1,000 developers spread throughout the organization. While there were a lot of mediocre, and truly some flat out bad developers, I guarantee you that 5-10…
What single project requires more than 5-10 programmers? Places with 1,000 developers spread throughout are working on hundreds of interacting projects. But, the communication and coordination isn't between all 1,000 developers.