@sarahjeong.bsky.social

Yeeaaa... it's a different approach.

(Don't read this as a defence of Musk, he's a turd, but SpaceX has competent technical people below their chimpanzee-on-a-string PR person)

NASA's traditional approach was to basically achieve perfection of design and manufacturing before trying to launch anything. Look at every possible failure mode of every component, down to the tiniest screw or wire or bit of plastic. Keep redesigning parts until you eliminate all failure modes that you don't have triply-redundant backups for. Test the living snot out of everything on the ground, in the lab. Have massive technical and safety reviews to ensure nothing was missed, anywhere.

It worked about as well as anything could, but it was extremely slow, bureaucratic, and above all incredibly expensive. Tons of rework when issues were found meant having to go back 3 steps to change something, and then redo the massive amount of work that had been done since then to make sure no new failure modes were possible, etc.

SpaceX is doing things differently - #iterative design. You design, build, #integrate, and #test-to-failure as often as possible to learn where the weak spots are -- you then rapidly iterate when you find the problems. "Rapid Unscheduled Disassembly" is an expected part of the process - it's how you learn the limits of what you've built, where the problems are.

Neither one is "the right way". They both work.

#IterativeDevelopment

๐—ฃ๐—ฒ๐—ฟ๐—ณ๐—ฒ๐—ฐ๐˜๐—ถ๐—ผ๐—ป ๐—ถ๐˜€ ๐—ฎ ๐—บ๐—ถ๐—ฟ๐—ฎ๐—ด๐—ฒ.
๐—ฃ๐—ฟ๐—ผ๐—ด๐—ฟ๐—ฒ๐˜€๐˜€ ๐—ถ๐˜€ ๐—ฟ๐—ฒ๐—ฎ๐—น.

Waiting for the โ€œperfectโ€ solution often means not shipping at all.

โœ… Start small
โœ… Ship early
โœ… Learn from feedback
โœ… Improve over time

Done is better than perfect โ€”
As long as youโ€™re growing with each version.

โ€”โ€”โ€”
โž• Join My WhatsApp Channel: https://lnkd.in/g62_G8Gr
โ€”โ€”โ€”

#ProgressOverPerfection #IterativeDevelopment #ShipIt #BuildLearnImprove #EngineeringMindset

LinkedIn

This link will take you to a page thatโ€™s not on LinkedIn

๐Ÿ”„ ๐—œ๐˜๐—ฒ๐—ฟ๐—ฎ๐˜๐—ถ๐˜ƒ๐—ฒ ๐——๐—ฒ๐˜ƒ๐—ฒ๐—น๐—ผ๐—ฝ๐—บ๐—ฒ๐—ป๐˜ ๐—ณ๐—ผ๐—ฟ ๐—ฅ๐—ฎ๐—ฝ๐—ถ๐—ฑ ๐—œ๐—บ๐—ฝ๐—ฟ๐—ผ๐˜ƒ๐—ฒ๐—บ๐—ฒ๐—ป๐˜

Iterative development allows teams to roll out improvements quickly based on ongoing user feedback, creating a product that evolves and grows alongside its users.

#IterativeDevelopment, #RapidImprovement

If you adhere to discipline and consistency in this process, the likelihood of success significantly increases.

#ProductMarketFit #StartupSuccess #AgileMethodology #MarketingData #IterativeDevelopment

What is the difference between iterative and incremental development, as used in agile and scrum, and the benefits of both?

Watch the full video to find out why you should think of it like a pizza! ๐Ÿ• https://youtube.com/shorts/gJrbOCX3B1c?feature=share

#incrementaldevelopment #iterativedevelopment #scrum #agile

Incremental vs Iterative Development #short

YouTube
@com
If you know what you want, but refuse to tell the team, it is micromanagement. If you don't know what you want, and wait for the team to show you, it's called Customer Collaboration under Agile.
It's hard to do true customer collaboration: People don't like to make mistakes, customers are unhappy, devs are unhappy, but mistakes are part of being agile (or even of #IterativeDevelopment). So, we are adopting more forgivable vocabulary: e.g. bets and forecast over deliverable and estimates.

โ€ชโ€œRequirements Volatility Is The Core Problem Of Software Engineeringโ€, The Overflow (https://stackoverflow.blog/2020/02/20/requirements-volatility-is-the-core-problem-of-software-engineering/).โ€ฌ

โ€ชVia HN: https://news.ycombinator.com/item?id=22382536โ€ฌ

โ€ช#SoftwareEngineering #Agile #Requirements #IterativeDevelopmentโ€ฌ

Requirements volatility is the core problem of software engineering - Stack Overflow Blog

It's now been more than 50 years since the first IFIP Conference on Software Engineering, and in that time there have been many different software engineering methodologies, processes, and models proposed to help software developers achieve that predictable and cost-effective process. But 50 years later, we still seem to see the same kinds of problems we always have: late delivery, unsatisfactory results, and complete project failures.

Stack Overflow Blog