Most developers have never seen a successful project
-
Most software professionals have never seen a successful software development project, continuous delivery evangelist Dave Farley said, and have “built careers on doing the wrong thing”.
All this time, we've been living a lie?
I once worked on a big project that was going great until the evangelists showed up (and said we were doing it all wrong.)
-
Most software professionals have never seen a successful software development project, continuous delivery evangelist Dave Farley said, and have “built careers on doing the wrong thing”.
All this time, we've been living a lie?
I've seen big fails and big wins, and I reckon my "batting average" at this stage would be a 10:1 value to cost ratio - I'm pretty sure that's way above the bar for most careers (with the possible exception of teaching).
-
And in almost all cases, I can point the finger at management for being the cause of the failure. I'm not joking. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
I'm not sure if I'd like to blame management for badly written code... :~ Although I do have a manager who also writes code :laugh: Seriously though, I know some baaaad programmers...
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
And in almost all cases, I can point the finger at management for being the cause of the failure. I'm not joking. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
-
Most software professionals have never seen a successful software development project, continuous delivery evangelist Dave Farley said, and have “built careers on doing the wrong thing”.
All this time, we've been living a lie?
I've worked on some successful projects, and a lot of train wrecks. It really comes down to how it's managed. A couple of projects were successful is spite of management (dumb luck), and others were doomed from the start.
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." -- Marcus Brigstocke, British Comedian
-
Most software professionals have never seen a successful software development project, continuous delivery evangelist Dave Farley said, and have “built careers on doing the wrong thing”.
All this time, we've been living a lie?
Kent Sharkey wrote:
have “built careers on doing following the wrong thing manager”.
FTFY
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
I'm not sure if I'd like to blame management for badly written code... :~ Although I do have a manager who also writes code :laugh: Seriously though, I know some baaaad programmers...
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
They do exist, yes. But a bad programmer is not so dangerous for a project as a bad manager
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
They do exist, yes. But a bad programmer is not so dangerous for a project as a bad manager
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
Depends on the project. In the starting phase, yes, a manager can make it or break it. But when a project is successful and gets bigger bad code tends to slow the project down and ultimately make the client lose trust in the product. I've worked on relatively small projects where you fixed X and Y stopped working. Additionally, each fix cost you hours of looking through code, fitting in a solution that is far from optimal, and debugging everything to see if everything still works. In the end it cost the company too much money and we stopped the project.
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Most software professionals have never seen a successful software development project, continuous delivery evangelist Dave Farley said, and have “built careers on doing the wrong thing”.
All this time, we've been living a lie?
Hence why I'm not a developer but an engineer. If your "manager" writes code, run, run as far and fast as you can.
-
Most software professionals have never seen a successful software development project, continuous delivery evangelist Dave Farley said, and have “built careers on doing the wrong thing”.
All this time, we've been living a lie?
This quote from the article is especially interesting: "We have a situation where taking an entirely ad hoc approach to software arguably leads to more successful outcomes than traditional approaches." Does this mean no management is better than poor management? Could you argue that no development is better than poor development? Perhaps...
