4 ms·

Efficiency Is Not Our Goal

7 points by pixelcort 13y ago

vishaldpatel 13y ago
Your argument would be much helped by actual anecdotes.
jared314 13y ago
I think I understand what this is trying to say, but I believe the problem lies more in each person's narrow scope of control, not some blind drive towards efficiency or ignorance of total throughput.
cbsmith 13y ago
Spoken like someone who has never had to operationally support hundreds of slightly different applications for a decade...
- fournm 13y ago
  Yeah. I understand the sentiment on some level, but when you find 10+ broken implementations of the same thing in a large codebase because every team decided to do it slightly differently you start to really, really appreciate those meetings for a change. Not to mention the (usually) resulting inconsistencies in how it works which can really annoy users.
losethos 13y ago
Liberals think standards of living can be increased by redistribution. Each year so many goods and services are produced. More goods and services do not materialize when you move money around. You must boost productivity. Be careful -- work is very unpleasant when you apply the thumbscrews for more efficiency. Many nations live lazily. God says... C:\TAD\Text\PARADISE.TXT iscipline and faith engaged, Your military obedience, to dissolve Allegiance to the acknowledged Power supreme? And thou, sly hypocrite, who now wouldst seem Patron of liberty, who more than thou Once fawned, and cringed, and servilely adored Heaven's awful Monarch? wherefore, but in hope To dispossess him, and thyself to reign? But mark what I arreed thee now, Avant; Fly neither whence thou fledst! If from this hour Within these hallowed limits thou appear, Back to the infernal pit I drag thee
userulluipeste 13y ago
"they probably could have shipped three more features in the time they spent blocked waiting on agreement" - because what we do is a race against time of volume shipping products crammed with features before everything else! This, is the kind of cowboy-developer I am trying to stay away from. (Here I am making a difference in terms between the general "programmer" and the "developer" which for me is not usually involved in later maintenance, testing and other kind of "boring" tasks that the work might require. That kind that only develops and tags it "done" jumping on something else.) This talk is focused on efficiency on development, deliberately ignoring the need for a system of development's checks and balances for other dependent tasks. I am sure that "We’ve all hated those jobs." and prefer a job where we'd be able to externalize the mess.

7 points by pixelcort 13y ago

Your argument would be much helped by actual anecdotes.

I think I understand what this is trying to say, but I believe the problem lies more in each person's narrow scope of control, not some blind drive towards efficiency or ignorance of total throughput.

cbsmith 13y ago

Spoken like someone who has never had to operationally support hundreds of slightly different applications for a decade...

fournm 13y ago
Yeah. I understand the sentiment on some level, but when you find 10+ broken implementations of the same thing in a large codebase because every team decided to do it slightly differently you start to really, really appreciate those meetings for a change. Not to mention the (usually) resulting inconsistencies in how it works which can really annoy users.

losethos 13y ago

Liberals think standards of living can be increased by redistribution. Each year so many goods and services are produced. More goods and services do not materialize when you move money around. You must boost productivity. Be careful -- work is very unpleasant when you apply the thumbscrews for more efficiency. Many nations live lazily. God says... C:\TAD\Text\PARADISE.TXT iscipline and faith engaged, Your military obedience, to dissolve Allegiance to the acknowledged Power supreme? And thou, sly hypocrite, who now wouldst seem Patron of liberty, who more than thou Once fawned, and cringed, and servilely adored Heaven's awful Monarch? wherefore, but in hope To dispossess him, and thyself to reign? But mark what I arreed thee now, Avant; Fly neither whence thou fledst! If from this hour Within these hallowed limits thou appear, Back to the infernal pit I drag thee

userulluipeste 13y ago

"they probably could have shipped three more features in the time they spent blocked waiting on agreement" - because what we do is a race against time of volume shipping products crammed with features before everything else! This, is the kind of cowboy-developer I am trying to stay away from. (Here I am making a difference in terms between the general "programmer" and the "developer" which for me is not usually involved in later maintenance, testing and other kind of "boring" tasks that the work might require. That kind that only develops and tags it "done" jumping on something else.) This talk is focused on efficiency on development, deliberately ignoring the need for a system of development's checks and balances for other dependent tasks. I am sure that "We’ve all hated those jobs." and prefer a job where we'd be able to externalize the mess.