PUBLIC MARKS with search spend

The overall goal is to allow developers to worry less about application "plumbing" and to spend most of their time on adding value for the client by focusing on the business logic and developing a rich user experience.

The nature of corporations as they grow is to become glacial and bureaucratic because no one trusts anyone. You spend half the day reporting on what you do so execs higher up can keep an eye on you because they believe that some how, you're out to destroy the company. And probably, some number of employees are. Or at the very least, not working up to their potential. Here's an idea, do some careful hiring and recruiting, hire people who are excellent at their jobs AND have some moral fiber, and set them loose to do what you hired them for. No one gets hired to fill out status reports, but that's mostly what we all end up doing. So the good people leave for greener, entrepreneurial pastures, and the people happy about status reports stay, get promoted and the whole thing perpetuates itself until you have Yahoo, GM or any other number of glacial bureauracracies.

the only value of valleywag hides in the comments.

I know the argument: demand is so high, we don't have another choice. I reject this argument on the basis that most good programmers spend the majority of their time fixing problems created by terrible programmers.

ouch! Learned was is NNPP thus

During the cold and dark Berlin winter days, I spend a lot of time with my boys in their room. And as I look at the toys scattered on the floor, my mind inevitably wanders back to New York.

In our research, we found that the most effective teams were skilled in all five styles, choosing the style that best fit the needs and goals of a project. For example, they might concurrently be involved in deep research on a User-Focused project, while relying on their experience for a Genius designed project, and spend a little time whipping out some one-shot functionality whose results would be Unintended Design.

Since the teams are working with different styles all the time, does it matter? Our research says it does. The teams that produced the best experiences knew these styles well and how to quickly switch between them. They knew when they needed to go whole hog and pull out all the stops for a User-Focused style project, while also knowing when it was important to bang out a quick design, knowing the results would essentially be unintended. Those teams had a rich toolbox of techniques and a solid understanding on how and when to use them.

There is no silver bullet.

Dsplaced is an exploration of the human belonging - to a city, a country or even oneself. Through voluntary submissions, Displaced illuminates a universal palette of emotions that individuals often spend a lifetime trying to decipher. But most importantly, Dsplaced is an experiment in collective storytelling - and it is our fervent hope that you will become a part of this mosaic. The web is our chosen platform for this expression. We know no other way that will allow us to create a place that overtime will build itself into a rich tapestry of personal stories.

You have $100 engineering dollars to spend.

A new project – for every book I read, I’m going to spend no more than 30 minutes designing a new cover for it. I will stick to classics and avoid newer stuff.

The bigger point is that none of us are doing enough to challenge the assignment. Every day, I spend at least an hour of my time looking at my work and what I've chosen to do next and wonder, "is this big enough?"

how big can you think?