home.social

#failfast — Public Fediverse posts

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

fetched live
  1. What Is a Product Manager Actually Responsible For? Maya Brooks on Building Systems for Team Success

    A veteran interim CPO explains how leading 13+ product teams on short timelines shaped his people-first approach to product management.

    tpgblog.com/2026/06/26/what-is

  2. What Is a Product Manager Actually Responsible For? Maya Brooks on Building Systems for Team Success

    A veteran interim CPO explains how leading 13+ product teams on short timelines shaped his people-first approach to product management.

    tpgblog.com/2026/06/26/what-is

  3. Jenna Gaudio’s Sprint Planning Process at Vydia

    A veteran interim CPO explains how leading 13+ product teams on short timelines shaped his people-first approach to product management.

    tpgblog.com/2026/06/11/jenna-g

  4. Jenna Gaudio’s Sprint Planning Process at Vydia

    A veteran interim CPO explains how leading 13+ product teams on short timelines shaped his people-first approach to product management.

    tpgblog.com/2026/06/11/jenna-g

  5. Why Companies Benefit from Recognizing Failure Early and Redirecting Resources

    📰 Original title: Perseverance doesn't always pay off for companies – sometimes it's better to 'fail fast'

    🤖 IA: It's not clickbait ✅
    👥 Usuarios: It's not clickbait ✅

    View full AI summary: killbait.com/en/why-companies-

    #business #failfast #businessstrategy #decisionmaking

  6. Why Companies Benefit from Recognizing Failure Early and Redirecting Resources

    📰 Original title: Perseverance doesn't always pay off for companies – sometimes it's better to 'fail fast'

    🤖 IA: It's not clickbait ✅
    👥 Usuarios: It's not clickbait ✅

    View full AI summary: killbait.com/en/why-companies-

    #business #failfast #businessstrategy #decisionmaking

  7. Post-OOP Imperative Functional Java.
    Model the process. Not the domain.

    Most Java code still asks the wrong question:
    "What is this domain object?"
    But production systems fail, scale, and burn because of processes, not nouns.

    If your system is a sequence of irreversible steps, model it as a sequence,
    not as interacting objects pretending to be immortal.

    This follows ideas from Railway-Oriented Programming (ROP):
    errors and decisions are values, not control-flow side effects.

    Modeling the process means you can read this top to bottom
    and understand exactly what happens.
    No debugger. No IDE magic. No tribal knowledge.

    Control flow is explicit.
    You see the execution order.
    Nothing hides in constructors, annotations, or overrides.

    Failure is a first-class concept.
    Once it fails or decides early, nothing else runs.
    No exception archaeology.

    Processes > Objects.
    Real systems are workflows where refactoring is safe.

    Steps are reordered, removed, or replaced
    without collapsing a class hierarchy.
    Testing is trivial, small stepwise context — even for an AI.

    Feed input. Assert final result.
    No mocking five layers of indirection.

    GraalVM / native-friendly.
    No reflection rituals.
    The compiler smiles.

    Objects are great for long-lived entities.
    User actions, payments, rules, and failures are short-lived processes.

    I model what happens,
    not what pretends to exist forever.

    Influenced by:
    Railway-Oriented Programming,
    Functional Core / Imperative Shell,
    Workflow / Saga patterns,
    Command pipelines,
    Unix philosophy,
    and value-oriented libraries like Vanilla-DI.

    Don't be stuck in axioms.

    #PostOOP
    #ImperativeFunctional
    #ProcessOverObjects
    #ModelTheProcess
    #WorkflowFirst
    #RailwayOrientedProgramming
    #FunctionalCore
    #ImperativeShell
    #CommandPipeline
    #ExplicitControlFlow
    #ValueOrientedDesign
    #ProcessModeling
    #FailFast
    #NoExceptionArchaeology
    #ComposableSystems
    #NativeFriendly
    #GraalVM
    #NoReflection
    #DeterministicCode
    #RefactorSafe
    #SagaPattern
    #UnixPhilosophy
    #VanillaDI
    #ModernJava
    #ArchitectureMatters

  8. Post-OOP Imperative Functional Java.
    Model the process. Not the domain.

    Most Java code still asks the wrong question:
    "What is this domain object?"
    But production systems fail, scale, and burn because of processes, not nouns.

    If your system is a sequence of irreversible steps, model it as a sequence,
    not as interacting objects pretending to be immortal.

    This follows ideas from Railway-Oriented Programming (ROP):
    errors and decisions are values, not control-flow side effects.

    Modeling the process means you can read this top to bottom
    and understand exactly what happens.
    No debugger. No IDE magic. No tribal knowledge.

    Control flow is explicit.
    You see the execution order.
    Nothing hides in constructors, annotations, or overrides.

    Failure is a first-class concept.
    Once it fails or decides early, nothing else runs.
    No exception archaeology.

    Processes > Objects.
    Real systems are workflows where refactoring is safe.

    Steps are reordered, removed, or replaced
    without collapsing a class hierarchy.
    Testing is trivial, small stepwise context — even for an AI.

    Feed input. Assert final result.
    No mocking five layers of indirection.

    GraalVM / native-friendly.
    No reflection rituals.
    The compiler smiles.

    Objects are great for long-lived entities.
    User actions, payments, rules, and failures are short-lived processes.

    I model what happens,
    not what pretends to exist forever.

    Influenced by:
    Railway-Oriented Programming,
    Functional Core / Imperative Shell,
    Workflow / Saga patterns,
    Command pipelines,
    Unix philosophy,
    and value-oriented libraries like Vanilla-DI.

    Don't be stuck in axioms.

    #PostOOP
    #ImperativeFunctional
    #ProcessOverObjects
    #ModelTheProcess
    #WorkflowFirst
    #RailwayOrientedProgramming
    #FunctionalCore
    #ImperativeShell
    #CommandPipeline
    #ExplicitControlFlow
    #ValueOrientedDesign
    #ProcessModeling
    #FailFast
    #NoExceptionArchaeology
    #ComposableSystems
    #NativeFriendly
    #GraalVM
    #NoReflection
    #DeterministicCode
    #RefactorSafe
    #SagaPattern
    #UnixPhilosophy
    #VanillaDI
    #ModernJava
    #ArchitectureMatters

  9. Wenn du gerade erst mit dem Programmieren in Java startest, wirst du relativ schnell über einen Begriff stolpern: "Fail Fast". Klingt erstmal nach einem fancy Buzzword, steckt aber etwas sehr Handfestes dahinter: Der Code soll möglichst früh, möglichst klar und möglichst laut kaputtgehen, wenn

    magicmarcy.de/fail-fast-statt-

    #Fail #Exception #Java #Vorbedingungen #IllegalArgumentException #FailFast #Programming

  10. Wenn du gerade erst mit dem Programmieren in Java startest, wirst du relativ schnell über einen Begriff stolpern: "Fail Fast". Klingt erstmal nach einem fancy Buzzword, steckt aber etwas sehr Handfestes dahinter: Der Code soll möglichst früh, möglichst klar und möglichst laut kaputtgehen, wenn

    magicmarcy.de/fail-fast-statt-

    #Fail #Exception #Java #Vorbedingungen #IllegalArgumentException #FailFast #Programming

  11. @nobsagile

    Ich glaube, da gibt es ein kulturell unterschiedliches Verständnis von "scheitern". In manchen Kulturen ist es eine Schmach, die man auf jeden Fall vermeiden muss. In anderen ist es der Beweis, dass man den Mut hatte, es zu versuchen.

    Ist es nicht sinnvoller, darauf hin zu arbeiten, dass die erste Kategorie sich der zweiten annähert?

    #Agile #Mindset #FailFast #LearnFast #Produktentwicklung

  12. @nobsagile

    Ich glaube, da gibt es ein kulturell unterschiedliches Verständnis von "scheitern". In manchen Kulturen ist es eine Schmach, die man auf jeden Fall vermeiden muss. In anderen ist es der Beweis, dass man den Mut hatte, es zu versuchen.

    Ist es nicht sinnvoller, darauf hin zu arbeiten, dass die erste Kategorie sich der zweiten annähert?

    #Agile #Mindset #FailFast #LearnFast #Produktentwicklung

  13. Hört ihr auch ständig dieses "Fail Fast"-Mantra? Ich halte das für grundlegend falsch und sogar schädlich.

    Das Problem ist das Wort "Scheitern". Es suggeriert ein binäres Ergebnis, dabei geht es nicht um Erfolg oder Misserfolg.

    Es geht darum, Hypothesen zu testen, z.B. "Verbessert dieses Feature das Leben unserer Nutzer?". Jede Antwort darauf ist ein Fortschritt, kein Scheitern.

    Ein Thread 🧵 👇

    (1/3)

    #Agile #Mindset #FailFast #LearnFast #Produktentwicklung

  14. Hört ihr auch ständig dieses "Fail Fast"-Mantra? Ich halte das für grundlegend falsch und sogar schädlich.

    Das Problem ist das Wort "Scheitern". Es suggeriert ein binäres Ergebnis, dabei geht es nicht um Erfolg oder Misserfolg.

    Es geht darum, Hypothesen zu testen, z.B. "Verbessert dieses Feature das Leben unserer Nutzer?". Jede Antwort darauf ist ein Fortschritt, kein Scheitern.

    Ein Thread 🧵 👇

    (1/3)

    #Agile #Mindset #FailFast #LearnFast #Produktentwicklung

  15. Oh, joy! 🤦‍♂️ Yet another command-line tool that lets you #retry that command you *already* know is going to fail. Because obviously, the solution to bad code is to make it fail faster! 🚀 Why fix bugs when you can just keep smashing your head against the keyboard with style? 🧨
    github.com/MaxBondABE/attempt #commandline #tools #badcode #failfast #codinghumor #developerlife #HackerNews #ngated

  16. Oh, joy! 🤦‍♂️ Yet another command-line tool that lets you #retry that command you *already* know is going to fail. Because obviously, the solution to bad code is to make it fail faster! 🚀 Why fix bugs when you can just keep smashing your head against the keyboard with style? 🧨
    github.com/MaxBondABE/attempt #commandline #tools #badcode #failfast #codinghumor #developerlife #HackerNews #ngated

  17. Die Grundidee bleibt faszinierend:
    Eine agentische KI, die ihre eigene Codebasis kennt, strukturiert vorgeht, Rückmeldungen aus der Code-Ausführung einbezieht und dadurch komplexen Code Schritt für Schritt erzeugt.

    Nur leider:
    Am Ende läuft’s nicht.
    Und die KI wirkt mit jedem Schritt ein kleines bisschen dümmer.

    #AgenticAI #CodeGeneration #AIDev #FailFast #PromptJourney #DeveloperReality

  18. Die Grundidee bleibt faszinierend:
    Eine agentische KI, die ihre eigene Codebasis kennt, strukturiert vorgeht, Rückmeldungen aus der Code-Ausführung einbezieht und dadurch komplexen Code Schritt für Schritt erzeugt.

    Nur leider:
    Am Ende läuft’s nicht.
    Und die KI wirkt mit jedem Schritt ein kleines bisschen dümmer.

    #AgenticAI #CodeGeneration #AIDev #FailFast #PromptJourney #DeveloperReality

  19. A strange usage of this new ai llm world. I as an individual can dabble quickly into a new domain and am suddenly faced with issues that people face deep in domain as basic grunt work is automated and i can then make a judgement call if i want to keep exploring this domain or not.

    #failfast

  20. A strange usage of this new ai llm world. I as an individual can dabble quickly into a new domain and am suddenly faced with issues that people face deep in domain as basic grunt work is automated and i can then make a judgement call if i want to keep exploring this domain or not.

    #failfast

  21. 🗣️ Zitat der Woche: „Fail fast, learn faster.“

    🟢 Hilfreich, wenn Mut und Chance zum Ausprobieren da sind.
    🔴 Riskant, wenn nur das Scheitern bleibt – ohne echte Lernschleife.
    🧠 Reflexionsfragen:
    • Was genau lernen wir – und wie sichern wir es fürs Team?
    • Planen wir unsere Experimente wirklich bewusst?

    #FailFast #Lernen #Experimente #Agile #Teamkultur

  22. 🗣️ Zitat der Woche: „Fail fast, learn faster.“

    🟢 Hilfreich, wenn Mut und Chance zum Ausprobieren da sind.
    🔴 Riskant, wenn nur das Scheitern bleibt – ohne echte Lernschleife.
    🧠 Reflexionsfragen:
    • Was genau lernen wir – und wie sichern wir es fürs Team?
    • Planen wir unsere Experimente wirklich bewusst?

    #FailFast #Lernen #Experimente #Agile #Teamkultur

  23. Infomatics is dead! Long live information (ontology)!

    Progress necessitates a commitment to falsifying even one's own beliefs. Never let it be said I'm not willing to falsify mine... here's proof, a detailed succession of my failures: qnfo.org/releases/2025/Lineage

    Tl;dr: There's still something worth exploring further, which gives birth to Information Ontology (IO).

    Also, #AI is superior for rapid prototyping and active falsification #failfast #openscience #research

  24. "Hey, #DeptofDefense, if you drop your investigation(s) into why I am so willfully-compromised, I can send a Crew Dragon spacecraft up to the ISS, um, tomorrow! I never liked #NASA's precautions anyway. #FailFast, as they, err, #Boeing says!" - #LeonSkum. space.com/space-exploration/hu

  25. #Zeitumstellung funktioniert super, besonders mit Kindern 😬

    Schafft das mal wieder ab langsam, bitte. #FailFast

  26. #Zeitumstellung funktioniert super, besonders mit Kindern 😬

    Schafft das mal wieder ab langsam, bitte. #FailFast

  27. Passwort darf nur eingeschränkt Sonderzeichen enthalten? Mir fallen dazu kaum Gründe ein, außer das PW wird unverschlüsselt und nicht gehashed in der Datenbank gespeichert... #failFast #opssec

  28. Passwort darf nur eingeschränkt Sonderzeichen enthalten? Mir fallen dazu kaum Gründe ein, außer das PW wird unverschlüsselt und nicht gehashed in der Datenbank gespeichert... #failFast #opssec

  29. Embrace failure as a powerful source of wisdom. [This website showcases](failure.museum/) various fails along with brief, insightful information. Explore notable examples like #Blockbuster and #NewCoke to learn valuable lessons from mistakes.
    #Fail_is_not_a_failure
    #FailFast

  30. The “fast” part of #FailFast matters. A 6 month failure is not fast. “Fast” means at least fast enough that the pain of failure is acceptable.

  31. The “fast” part of #FailFast matters. A 6 month failure is not fast. “Fast” means at least fast enough that the pain of failure is acceptable.

  32. @jerry

    Since we recently we recently had 2+ hours of downtime, I will allow it. /s

    TBH, I would do the downtime because if there is a problem, you will be able to fallback quickly.

    You want to failfast.

    If you try the migration path, there could be an undetected ptoblem ocuuring that is not discovered quickly, and the remediation could end up being a bigger mess than 2 hours of downtime.

    I am old skool, this is how I would do it.

    #FailFast #DBA

  33. @jerry

    Since we recently we recently had 2+ hours of downtime, I will allow it. /s

    TBH, I would do the downtime because if there is a problem, you will be able to fallback quickly.

    You want to failfast.

    If you try the migration path, there could be an undetected ptoblem ocuuring that is not discovered quickly, and the remediation could end up being a bigger mess than 2 hours of downtime.

    I am old skool, this is how I would do it.

    #FailFast #DBA

  34. “The subtlety of it is pretty insidious. Like some kind of distributed long con, played out over and over, in the midst of so many millions of other simultaneous ones.”

    @amatecha on VC (Venture Capital)

    #VC #VentureCapital #SiliconValley #BigTech #BugWeb #startups #exponentialGrowth #failFast #exits #surveillanceCapitalism #peopleFarming

  35. “The subtlety of it is pretty insidious. Like some kind of distributed long con, played out over and over, in the midst of so many millions of other simultaneous ones.”

    @amatecha on VC (Venture Capital)

    #VC #VentureCapital #SiliconValley #BigTech #BugWeb #startups #exponentialGrowth #failFast #exits #surveillanceCapitalism #peopleFarming

  36. Fully agree with this - small - #failfast experiments are key in my experience.

  37. Fully agree with this - small - #failfast experiments are key in my experience.

  38. 81 Years Ago: A date that will live in... #infamy. (1st draft of Roosevelt's #PearlHarbor address didn't say that.)

    #iterate #failfast

  39. 81 Years Ago: A date that will live in... #infamy. (1st draft of Roosevelt's #PearlHarbor address didn't say that.)

    #iterate #failfast