home.social

#simonwardley — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #simonwardley, aggregated by home.social.

  1. @jasongorman The diagram is BDUF.

    What’s missing?

    The feedback loop from step 5 to step 2.

    As you mention, the user/customer.

    As #simonwardley points out, we don’t really have software engineering. Engineering involves studying and correcting errors in understanding, models, and actions.

    I started in the days of BDUF. And that which is old is new again. The only thing that changed is the name of the steps.

    We have failed to learn, anything.

    Well, we can now fail faster. Automated GIGO.

  2. @jasongorman The diagram is BDUF.

    What’s missing?

    The feedback loop from step 5 to step 2.

    As you mention, the user/customer.

    As #simonwardley points out, we don’t really have software engineering. Engineering involves studying and correcting errors in understanding, models, and actions.

    I started in the days of BDUF. And that which is old is new again. The only thing that changed is the name of the steps.

    We have failed to learn, anything.

    Well, we can now fail faster. Automated GIGO.

  3. @jasongorman The diagram is BDUF.

    What’s missing?

    The feedback loop from step 5 to step 2.

    As you mention, the user/customer.

    As points out, we don’t really have software engineering. Engineering involves studying and correcting errors in understanding, models, and actions.

    I started in the days of BDUF. And that which is old is new again. The only thing that changed is the name of the steps.

    We have failed to learn, anything.

    Well, we can now fail faster. Automated GIGO.

  4. @jasongorman The diagram is BDUF.

    What’s missing?

    The feedback loop from step 5 to step 2.

    As you mention, the user/customer.

    As #simonwardley points out, we don’t really have software engineering. Engineering involves studying and correcting errors in understanding, models, and actions.

    I started in the days of BDUF. And that which is old is new again. The only thing that changed is the name of the steps.

    We have failed to learn, anything.

    Well, we can now fail faster. Automated GIGO.

  5. @jasongorman The diagram is BDUF.

    What’s missing?

    The feedback loop from step 5 to step 2.

    As you mention, the user/customer.

    As #simonwardley points out, we don’t really have software engineering. Engineering involves studying and correcting errors in understanding, models, and actions.

    I started in the days of BDUF. And that which is old is new again. The only thing that changed is the name of the steps.

    We have failed to learn, anything.

    Well, we can now fail faster. Automated GIGO.

  6. “engineering is not writing code. It is understanding the system, the failure modes, the blast radius."

    Alas, most software engineering today is not engineering at all, it's a craft. The issue with vibe coding is that we haven't yet developed the practices to safely manage this, they are still co-evolving and will do so for many years. Until that time vibe coding is mostly driven by belief and faith but then software "engineering" was broken anyway, relying on reading hundreds of thousands of lines of code in order to understand something was never sustainable.

    And this is one of most pressing problems in software, we are literally going from craft to faith i.e. I lack the ability to do this, so I'll trust the machine to do it for me. It might be time we actually turned software into an engineering discipline.”

    #simonwardley on LinkedIn

  7. “engineering is not writing code. It is understanding the system, the failure modes, the blast radius."

    Alas, most software engineering today is not engineering at all, it's a craft. The issue with vibe coding is that we haven't yet developed the practices to safely manage this, they are still co-evolving and will do so for many years. Until that time vibe coding is mostly driven by belief and faith but then software "engineering" was broken anyway, relying on reading hundreds of thousands of lines of code in order to understand something was never sustainable.

    And this is one of most pressing problems in software, we are literally going from craft to faith i.e. I lack the ability to do this, so I'll trust the machine to do it for me. It might be time we actually turned software into an engineering discipline.”

    #simonwardley on LinkedIn

  8. “engineering is not writing code. It is understanding the system, the failure modes, the blast radius."

    Alas, most software engineering today is not engineering at all, it's a craft. The issue with vibe coding is that we haven't yet developed the practices to safely manage this, they are still co-evolving and will do so for many years. Until that time vibe coding is mostly driven by belief and faith but then software "engineering" was broken anyway, relying on reading hundreds of thousands of lines of code in order to understand something was never sustainable.

    And this is one of most pressing problems in software, we are literally going from craft to faith i.e. I lack the ability to do this, so I'll trust the machine to do it for me. It might be time we actually turned software into an engineering discipline.”

    on LinkedIn

  9. “engineering is not writing code. It is understanding the system, the failure modes, the blast radius."

    Alas, most software engineering today is not engineering at all, it's a craft. The issue with vibe coding is that we haven't yet developed the practices to safely manage this, they are still co-evolving and will do so for many years. Until that time vibe coding is mostly driven by belief and faith but then software "engineering" was broken anyway, relying on reading hundreds of thousands of lines of code in order to understand something was never sustainable.

    And this is one of most pressing problems in software, we are literally going from craft to faith i.e. I lack the ability to do this, so I'll trust the machine to do it for me. It might be time we actually turned software into an engineering discipline.”

    #simonwardley on LinkedIn

  10. “engineering is not writing code. It is understanding the system, the failure modes, the blast radius."

    Alas, most software engineering today is not engineering at all, it's a craft. The issue with vibe coding is that we haven't yet developed the practices to safely manage this, they are still co-evolving and will do so for many years. Until that time vibe coding is mostly driven by belief and faith but then software "engineering" was broken anyway, relying on reading hundreds of thousands of lines of code in order to understand something was never sustainable.

    And this is one of most pressing problems in software, we are literally going from craft to faith i.e. I lack the ability to do this, so I'll trust the machine to do it for me. It might be time we actually turned software into an engineering discipline.”

    #simonwardley on LinkedIn

  11. The iSAQB was sponsor of the "Agile meets Architecture 2025" conference in Berlin, where experts from around the world gathered to share their insights. 💡

    We had the privilege of conducting a fascinating interview with Simon Wardley, inventor of Wardley Mapping, in which we discussed the powerful potential and possible pitfalls of integrating AI into company processes. 🤩

    Watch the full interview here! 👉 youtu.be/Ulo0YlRLrJs

    #iSAQB #AgileMeetsArchitecture #AI #SimonWardley #WardleyMapping

  12. The iSAQB was sponsor of the "Agile meets Architecture 2025" conference in Berlin, where experts from around the world gathered to share their insights. 💡

    We had the privilege of conducting a fascinating interview with Simon Wardley, inventor of Wardley Mapping, in which we discussed the powerful potential and possible pitfalls of integrating AI into company processes. 🤩

    Watch the full interview here! 👉 youtu.be/Ulo0YlRLrJs

    #iSAQB #AgileMeetsArchitecture #AI #SimonWardley #WardleyMapping

  13. The iSAQB was sponsor of the "Agile meets Architecture 2025" conference in Berlin, where experts from around the world gathered to share their insights. 💡

    We had the privilege of conducting a fascinating interview with Simon Wardley, inventor of Wardley Mapping, in which we discussed the powerful potential and possible pitfalls of integrating AI into company processes. 🤩

    Watch the full interview here! 👉 youtu.be/Ulo0YlRLrJs

    #iSAQB #AgileMeetsArchitecture #AI #SimonWardley #WardleyMapping

  14. AI and the New Theocracies

    linkedin.com/pulse/ai-new-theo

    "There is far too much AI doom for my liking. However, there is one issue that does concern me. It is not about machines but about people. It is almost never mentioned and mainly arises from attempts to solve the above risks. The thing that gives me concern is the rise of a new Theocracy." -- #SimonWardley

    #gen_AI #OpenAI #chatGPT

  15. AI and the New Theocracies

    linkedin.com/pulse/ai-new-theo

    "There is far too much AI doom for my liking. However, there is one issue that does concern me. It is not about machines but about people. It is almost never mentioned and mainly arises from attempts to solve the above risks. The thing that gives me concern is the rise of a new Theocracy." -- #SimonWardley

    #gen_AI #OpenAI #chatGPT

  16. AI and the New Theocracies

    linkedin.com/pulse/ai-new-theo

    "There is far too much AI doom for my liking. However, there is one issue that does concern me. It is not about machines but about people. It is almost never mentioned and mainly arises from attempts to solve the above risks. The thing that gives me concern is the rise of a new Theocracy." -- #SimonWardley

    #gen_AI #OpenAI #chatGPT

  17. AI and the New Theocracies

    linkedin.com/pulse/ai-new-theo

    "There is far too much AI doom for my liking. However, there is one issue that does concern me. It is not about machines but about people. It is almost never mentioned and mainly arises from attempts to solve the above risks. The thing that gives me concern is the rise of a new Theocracy." -- #SimonWardley

    #gen_AI #OpenAI #chatGPT

  18. AI and the New Theocracies

    linkedin.com/pulse/ai-new-theo

    "There is far too much AI doom for my liking. However, there is one issue that does concern me. It is not about machines but about people. It is almost never mentioned and mainly arises from attempts to solve the above risks. The thing that gives me concern is the rise of a new Theocracy." -- #SimonWardley

    #gen_AI #OpenAI #chatGPT