Filed under

working with development

See all posts on posterous with this tag ยป

on budgets and schedules

Perhaps the main reason we were behind schedule and over budget was because budgets and schedules are based on previous experience with similar projects. We really didn't know how much it would cost to build or how long it would take.

Tom Kelly of Grumman on building the lunar module for the Apollo space project

Filed under  //  working with development  
Posted by Steve Johnson 

How do you feel about coworkers asking you questions?

The Engineering mind is back with another one. "How do you feel about coworkers asking you questions?"

He writes:

Yes, you're welcome to ask me whatever you like, but keep in mind that I will hate you. Forever.

For more on development productivity, see also http://www.paulgraham.com/makersschedule.html

It takes 20 minutes to begin concentrating yet the typical workplace has an interruption every 3 minutes. No wonder we can't seem to get any work done at work. My suggestion: the closed door policy. Whenever you need to think, close the door. And scowl--at anyone who isn't your boss--when someone bothers you anyway. Or do what so many others do: work at home when you need to think.

Don't be the guy that interrupts everyone when they're trying to get real work done.

Filed under  //  working with development  
Posted by Steve Johnson 

Touch Revolution's Android-powered microwave

Hailed one of the worst 10 new products at CES: 
Touch Revolution's Android-powered microwave 
Slide_4334_60933_large

Looks like someone was sitting in a room with too much time and not enough market data. 

I think it's likely we'll be seeing many Android-based bad ideas in the future. Android is a great embedded system but just because you can... Oh well, you know the rest. As we like to say, Development knows what can be built; product management knows what should be built.

Filed under  //  working with development  
Posted by Steve Johnson