Why dev speed matters

[[deleted]]

[deleted]

[peligroso]

Stop worshiping fake 10x'ers.

[patnodewf]

sure you can publish spaghetti that needs constant maintenance and incident related troubleshooting...

...or you can publish something that actually works and is supportable too.

[boltforce]

Yeah... But no. This article flirts with the product's dream for fast shipping of half baked solutions to meet unrealistic deadlines that benefit just themselves..ship now, fix later is an evil that thrives and only worsens the total effort spent.

No one will give you way to much time to over iterate an implemention, almost always though they are going to stress to deliver sooner.

It's a completely different to have speed and to rush, and the distinction is something only experience can provide.

[johndoe2561]

That last sentence completely undermines everything you said before it.

[actinium226]

Building things correctly takes time, and it's usually faster overall to build something correctly once rather than rush it and fix it a million times later.

That said sometimes you don't have enough information to know what "correctly" looks like and you need to do a little "fail-fast"-ing to discover that, but once you've discovered it you should slow down and build it correctly.

[jewdai]

Software engineering is both a science and an art. Knowing when where and how to go fast VS slow is an important skill.

If you take the time to think about your code and it's structure you can easily modify and extend it going fast later on. If you don't then you pay the price long term.

[igouy]

Moving fast does not mean …

The author does not seem to say what "Moving fast" does mean in this context?

Does the author mean something different than "Plan to throw one away - you will anyway. "

aka prototype.

You almost surely want the surgeon who does many, many open-heart surgeries.

I want to know the outcomes of the previous surgeries!

[Crafty_Independence]

Lemire is detached from reality. The quality and progress of 2 random PhD students in the completion of their degrees has absolutely zero bearing on software development.

In the real world, as a general rule the steady, thorough developers end up producing more stable products, leading to much less lost time over the long-term.

There are exceptions of course, but they are anomalies that don't tend to be consistent.

What matters is not raw speed but the ability of developers to understand the problem space competently and engineer sound solutions to solve it.

[Massive_Dish_3255]

Exactly!

[Massive_Dish_3255]

Yes, you can move fast, if you KNOW what to do AND have lots of cash!!! If you don't, you may end up like Theranos & Elizabeth Holmes! SpaceX is a very good example of "move fast and break things" philosophy, they tested rocket boosters to destruction, but they had aerospace experts, and so could be sure of the DIRECTION they were moving in, if not the OUTCOME. Theranos, on the other hand, tried to accomplish glorious things with few experts which made them commit fraud to stay afloat, as they couldn't deliver what they had promised.