home.social

#softwarecraftsmanship — Public Fediverse posts

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

  1. AI agents can write code faster than you ever will. That doesn't mean you can stop thinking.

    New post on vibe coding, DDD, TDD, and why the craftsman isn't replaced — just gets leverage.

    fiatcode.dev/posts/vibe-coding

    #SoftwareCraftsmanship #TDD #DDD #VibeCoding

  2. Open Source erblüht weiterhin. Die jüngsten Lizenzänderungen und die sich entwickelnde Landschaft zeigen, wie wichtig Community-getriebene Projekte für Innovation sind. Doch wie können wir die Nachhaltigkeit dieser Modelle sichern und sicherstellen, dass die Vorteile allen zugutekommen? #OpenSource #SoftwareCraftsmanship #Community

  3. NewCrafts is taking a break and will be back in 2027.
    After 10+ years of sharpening software craft, we're pausing to reflect on what craft means in the age of AI agents. Lower revenue in 2025 and the dramatically changed landscape for software development both played a part in this decision.
    For our Paris community, in-person workshops continue. Looking for a conference in 2026? Consider DDD Europe in Antwerp this June.
    Full story: ncrafts.io
    #softwarecraftsmanship #NewCrafts

  4. NewCrafts is taking a break and will be back in 2027.
    After 10+ years of sharpening software craft, we're pausing to reflect on what craft means in the age of AI agents. Lower revenue in 2025 and the dramatically changed landscape for software development both played a part in this decision.
    For our Paris community, in-person workshops continue. Looking for a conference in 2026? Consider DDD Europe in Antwerp this June.
    Full story: ncrafts.io
    #softwarecraftsmanship #NewCrafts

  5. NewCrafts is taking a break and will be back in 2027.
    After 10+ years of sharpening software craft, we're pausing to reflect on what craft means in the age of AI agents. Lower revenue in 2025 and the dramatically changed landscape for software development both played a part in this decision.
    For our Paris community, in-person workshops continue. Looking for a conference in 2026? Consider DDD Europe in Antwerp this June.
    Full story: ncrafts.io
    #softwarecraftsmanship #NewCrafts

  6. NewCrafts is taking a break and will be back in 2027.
    After 10+ years of sharpening software craft, we're pausing to reflect on what craft means in the age of AI agents. Lower revenue in 2025 and the dramatically changed landscape for software development both played a part in this decision.
    For our Paris community, in-person workshops continue. Looking for a conference in 2026? Consider DDD Europe in Antwerp this June.
    Full story: ncrafts.io
    #softwarecraftsmanship #NewCrafts

  7. NewCrafts is taking a break and will be back in 2027.
    After 10+ years of sharpening software craft, we're pausing to reflect on what craft means in the age of AI agents. Lower revenue in 2025 and the dramatically changed landscape for software development both played a part in this decision.
    For our Paris community, in-person workshops continue. Looking for a conference in 2026? Consider DDD Europe in Antwerp this June.
    Full story: ncrafts.io
    #softwarecraftsmanship #NewCrafts

  8. Mal was Grundsätzliches jenseits von Meetings und Tickets: Woher kommt eigentlich die Idee vom "Programmierer als Handwerker"?

    @simulo hat diese Frage in den Raum gestellt und damit eine Diskussion über unsere professionelle Identität angestoßen.
    Eine willkommene Abwechslung zum Buzzword-Bingo.

    Der Anstoß: hci.social/users/simulo/status

    Seht ihr euch als Handwerker, Ingenieure oder Künstler? Und warum?

    3/4

    #SoftwareCraftsmanship #AgileMindset #Programmierung

  9. Mal was Grundsätzliches jenseits von Meetings und Tickets: Woher kommt eigentlich die Idee vom "Programmierer als Handwerker"?

    @simulo hat diese Frage in den Raum gestellt und damit eine Diskussion über unsere professionelle Identität angestoßen.
    Eine willkommene Abwechslung zum Buzzword-Bingo.

    Der Anstoß: hci.social/users/simulo/status

    Seht ihr euch als Handwerker, Ingenieure oder Künstler? Und warum?

    3/4

    #SoftwareCraftsmanship #AgileMindset #Programmierung

  10. Mal was Grundsätzliches jenseits von Meetings und Tickets: Woher kommt eigentlich die Idee vom "Programmierer als Handwerker"?

    @simulo hat diese Frage in den Raum gestellt und damit eine Diskussion über unsere professionelle Identität angestoßen.
    Eine willkommene Abwechslung zum Buzzword-Bingo.

    Der Anstoß: hci.social/users/simulo/status

    Seht ihr euch als Handwerker, Ingenieure oder Künstler? Und warum?

    3/4

    #SoftwareCraftsmanship #AgileMindset #Programmierung

  11. Mal was Grundsätzliches jenseits von Meetings und Tickets: Woher kommt eigentlich die Idee vom "Programmierer als Handwerker"?

    @simulo hat diese Frage in den Raum gestellt und damit eine Diskussion über unsere professionelle Identität angestoßen.
    Eine willkommene Abwechslung zum Buzzword-Bingo.

    Der Anstoß: hci.social/users/simulo/status

    Seht ihr euch als Handwerker, Ingenieure oder Künstler? Und warum?

    3/4

    #SoftwareCraftsmanship #AgileMindset #Programmierung

  12. Mal was Grundsätzliches jenseits von Meetings und Tickets: Woher kommt eigentlich die Idee vom "Programmierer als Handwerker"?

    @simulo hat diese Frage in den Raum gestellt und damit eine Diskussion über unsere professionelle Identität angestoßen.
    Eine willkommene Abwechslung zum Buzzword-Bingo.

    Der Anstoß: hci.social/users/simulo/status

    Seht ihr euch als Handwerker, Ingenieure oder Künstler? Und warum?

    3/4

    #SoftwareCraftsmanship #AgileMindset #Programmierung

  13. Nach Doku-Chaos ein Mini-Win! 💪 Hab ein Modul refactored: von 200 Zeilen Spaghetti auf 50 Zeilen cleanem Code. Lesbar, testbar – läuft! ✨ Das ist meine Meditation. Code, der Sinn ergibt, bessere Performance… unbezahlbar. Refactoring ist keine Zeitverschwendung, sondern die beste Investition. #changemymind

    Was war euer krassester Refactoring-Erfolg? 👇

    #vibecoder #refactoring #cleancode #softwarecraftsmanship #developer #coding #neucode

  14. Nach Doku-Chaos ein Mini-Win! 💪 Hab ein Modul refactored: von 200 Zeilen Spaghetti auf 50 Zeilen cleanem Code. Lesbar, testbar – läuft! ✨ Das ist meine Meditation. Code, der Sinn ergibt, bessere Performance… unbezahlbar. Refactoring ist keine Zeitverschwendung, sondern die beste Investition. #changemymind

    Was war euer krassester Refactoring-Erfolg? 👇

    #vibecoder #refactoring #cleancode #softwarecraftsmanship #developer #coding #neucode

  15. Nach Doku-Chaos ein Mini-Win! 💪 Hab ein Modul refactored: von 200 Zeilen Spaghetti auf 50 Zeilen cleanem Code. Lesbar, testbar – läuft! ✨ Das ist meine Meditation. Code, der Sinn ergibt, bessere Performance… unbezahlbar. Refactoring ist keine Zeitverschwendung, sondern die beste Investition. #changemymind

    Was war euer krassester Refactoring-Erfolg? 👇

    #vibecoder #refactoring #cleancode #softwarecraftsmanship #developer #coding #neucode

  16. Nach Doku-Chaos ein Mini-Win! 💪 Hab ein Modul refactored: von 200 Zeilen Spaghetti auf 50 Zeilen cleanem Code. Lesbar, testbar – läuft! ✨ Das ist meine Meditation. Code, der Sinn ergibt, bessere Performance… unbezahlbar. Refactoring ist keine Zeitverschwendung, sondern die beste Investition. #changemymind

    Was war euer krassester Refactoring-Erfolg? 👇

    #vibecoder #refactoring #cleancode #softwarecraftsmanship #developer #coding #neucode

  17. Nach Doku-Chaos ein Mini-Win! 💪 Hab ein Modul refactored: von 200 Zeilen Spaghetti auf 50 Zeilen cleanem Code. Lesbar, testbar – läuft! ✨ Das ist meine Meditation. Code, der Sinn ergibt, bessere Performance… unbezahlbar. Refactoring ist keine Zeitverschwendung, sondern die beste Investition. #changemymind

    Was war euer krassester Refactoring-Erfolg? 👇

    #vibecoder #refactoring #cleancode #softwarecraftsmanship #developer #coding #neucode

  18. Are you inadvertently making your code more complex than it needs to be? Join Kevlin Henney's workshop 'Code Simplification Masterclass' to explore the real cost of complexity in code, culture, and process. We'll tackle technical debt head-on and discover practical simplification strategies: ddd.academy/keeping-it-simple/ #CodeSimplicity #SoftwareCraftsmanship

  19. Are you inadvertently making your code more complex than it needs to be? Join Kevlin Henney's workshop 'Code Simplification Masterclass' to explore the real cost of complexity in code, culture, and process. We'll tackle technical debt head-on and discover practical simplification strategies: ddd.academy/keeping-it-simple/ #CodeSimplicity #SoftwareCraftsmanship

  20. Are you inadvertently making your code more complex than it needs to be? Join Kevlin Henney's workshop 'Code Simplification Masterclass' to explore the real cost of complexity in code, culture, and process. We'll tackle technical debt head-on and discover practical simplification strategies: ddd.academy/keeping-it-simple/ #CodeSimplicity #SoftwareCraftsmanship

  21. Are you inadvertently making your code more complex than it needs to be? Join Kevlin Henney's workshop 'Code Simplification Masterclass' to explore the real cost of complexity in code, culture, and process. We'll tackle technical debt head-on and discover practical simplification strategies: ddd.academy/keeping-it-simple/ #CodeSimplicity #SoftwareCraftsmanship

  22. Are you inadvertently making your code more complex than it needs to be? Join Kevlin Henney's workshop 'Code Simplification Masterclass' to explore the real cost of complexity in code, culture, and process. We'll tackle technical debt head-on and discover practical simplification strategies: ddd.academy/keeping-it-simple/ #CodeSimplicity #SoftwareCraftsmanship

  23. The art of programming is not knowing all the answers — it’s knowing how to ask the right questions, one bug at a time. 🔍💡 #SoftwareCraftsmanship #CodeWisdom #DevThoughts

  24. Are you inadvertently making your code more complex than it needs to be? Join Kevlin Henney's workshop 'Keeping it Simple' to explore the real cost of complexity in code, culture, and process. We'll tackle technical debt head-on and discover practical simplification strategies: buff.ly/5k4Q7wb #CodeSimplicity #SoftwareCraftsmanship

  25. Technical Excellence: Lost. Like Atlantis. But with more AI JavaScript.

    Once upon a time, engineers knew things. Not Googled things. Crafted things. We automated builds, wrote real tests, treated code like it could explode if mishandled, which it did, and we were proud when it didn't. It was elegant. Precise. Shameful if the customer found a bug. Now? It's fashionable to push broken features into production and call it MVP.

    Nowadays, we want to engineer. But we don't get the space for applying our knowledge. Every training is useless when you can't apply it.

    "Senior Developers" parade around with 10 years of experience by repeating the same year 10 times. They chant Clean Architecture but build everything in main(). They talk about TDD, then mock their way into oblivion. They don’t refactor, as it's not in the ticket. They don’t simplify, they just make it work. They wait for ticket assignments like robots awaiting firmware updates.
    Worse: nobody creates anymore. They consume tools. No one understands the layers. No one asks why.

    Agility? Without engineering excellence, it's just theatre. You can't move fast if you don't know how your engine works.

    Want to be agile? Build engineers who:
    * Understand architecture beyond drawing hexagons.
    * Write tests that assert behaviour, not just lines executed.
    * Know the cost of a dependency.
    * Automate not for fun, but for resilience.
    * Take responsibility before being told to.
    * Stop chasing tools & Start understanding systems.
    * Build things that work, not just compile.

    Technical excellence is not a luxury. It's the foundation. And without it, you're not building software. You're just decorating the Titanic.

    Agility without engineering is chaos in a hoodie.

    #TechnicalExcellence #SoftwareCraftsmanship #AgileNotFragile #DevRantWithLove #coding #programming #developing

  26. Are you inadvertently making your code more complex than it needs to be? Join Kevlin Henney's workshop 'Keeping it Simple' to explore the real cost of complexity in code, culture, and process. We'll tackle technical debt head-on and discover practical simplification strategies: buff.ly/3xrKM6z #CodeSimplicity #SoftwareCraftsmanship

  27. True Engineering Isn't about using tools.

    It's in the questions.

    Too often, I see "engineering" reduced to assembling frameworks like IKEA furniture, follow the docs, trust the tool, ship it. But real engineering begins where the documentation ends.

    Do you know what that smart-syntax language is doing under the hood?
    Do you know how your beloved build tool behaves when it comes to automations and generic CI/CD pipelines?
    Do you know what your "schema-less" database sacrifices when concurrency climbs?
    Do you know how many runtime hacks exist to make your "native" build work seamlessly?
    Do you know how your framework manages threads… or fails to?

    Many don't. And that's the problem.

    We've built castles on sand because the sand came with good tutorials. Engineering isn't about how much you can plug in. It's about how much you understand, especially the parts no one talks about.

    If you're not asking, "What isn’t being said?"
    You're not engineering. You're just believing and praying.
    AI is a perfect example of many people which hype it but don't understand it.
    You have incidents, bugs, complexity, legacy and need time for maintenance or migrations? Then you build your system wrong. Technology should help and not hinder us. We need to focus on simplicity, not on overengineering.

    #TrueEngineering #ThinkBeforeYouCode #SoftwareCraftsmanship #QuestionEverything #BeyondTheFramework #UnderstandTheTools #CodeWithPurpose #SimplicityFirst #CleanArchitecture #DevMindset #EngineeringNotAssembling #TechWithoutMyth #UnderTheHood #CI_CDReality #AutomationTruths #NoMoreMagic #AskTheRightQuestions #AIWithoutUnderstanding #OverengineeringKills #LegacyByDesign #BuildForSimplicity #MinimalistTech

  28. True Engineering Isn't about using tools.

    It's in the questions.

    Too often, I see "engineering" reduced to assembling frameworks like IKEA furniture, follow the docs, trust the tool, ship it. But real engineering begins where the documentation ends.

    Do you know what that smart-syntax language is doing under the hood?
    Do you know how your beloved build tool behaves when it comes to automations and generic CI/CD pipelines?
    Do you know what your "schema-less" database sacrifices when concurrency climbs?
    Do you know how many runtime hacks exist to make your "native" build work seamlessly?
    Do you know how your framework manages threads… or fails to?

    Many don't. And that's the problem.

    We've built castles on sand because the sand came with good tutorials. Engineering isn't about how much you can plug in. It's about how much you understand, especially the parts no one talks about.

    If you're not asking, "What isn’t being said?"
    You're not engineering. You're just believing and praying.
    AI is a perfect example of many people which hype it but don't understand it.
    You have incidents, bugs, complexity, legacy and need time for maintenance or migrations? Then you build your system wrong. Technology should help and not hinder us. We need to focus on simplicity, not on overengineering.

    #TrueEngineering #ThinkBeforeYouCode #SoftwareCraftsmanship #QuestionEverything #BeyondTheFramework #UnderstandTheTools #CodeWithPurpose #SimplicityFirst #CleanArchitecture #DevMindset #EngineeringNotAssembling #TechWithoutMyth #UnderTheHood #CI_CDReality #AutomationTruths #NoMoreMagic #AskTheRightQuestions #AIWithoutUnderstanding #OverengineeringKills #LegacyByDesign #BuildForSimplicity #MinimalistTech

  29. True Engineering Isn't about using tools.

    It's in the questions.

    Too often, I see "engineering" reduced to assembling frameworks like IKEA furniture, follow the docs, trust the tool, ship it. But real engineering begins where the documentation ends.

    Do you know what that smart-syntax language is doing under the hood?
    Do you know how your beloved build tool behaves when it comes to automations and generic CI/CD pipelines?
    Do you know what your "schema-less" database sacrifices when concurrency climbs?
    Do you know how many runtime hacks exist to make your "native" build work seamlessly?
    Do you know how your framework manages threads… or fails to?

    Many don't. And that's the problem.

    We've built castles on sand because the sand came with good tutorials. Engineering isn't about how much you can plug in. It's about how much you understand, especially the parts no one talks about.

    If you're not asking, "What isn’t being said?"
    You're not engineering. You're just believing and praying.
    AI is a perfect example of many people which hype it but don't understand it.
    You have incidents, bugs, complexity, legacy and need time for maintenance or migrations? Then you build your system wrong. Technology should help and not hinder us. We need to focus on simplicity, not on overengineering.

  30. True Engineering Isn't about using tools.

    It's in the questions.

    Too often, I see "engineering" reduced to assembling frameworks like IKEA furniture, follow the docs, trust the tool, ship it. But real engineering begins where the documentation ends.

    Do you know what that smart-syntax language is doing under the hood?
    Do you know how your beloved build tool behaves when it comes to automations and generic CI/CD pipelines?
    Do you know what your "schema-less" database sacrifices when concurrency climbs?
    Do you know how many runtime hacks exist to make your "native" build work seamlessly?
    Do you know how your framework manages threads… or fails to?

    Many don't. And that's the problem.

    We've built castles on sand because the sand came with good tutorials. Engineering isn't about how much you can plug in. It's about how much you understand, especially the parts no one talks about.

    If you're not asking, "What isn’t being said?"
    You're not engineering. You're just believing and praying.
    AI is a perfect example of many people which hype it but don't understand it.
    You have incidents, bugs, complexity, legacy and need time for maintenance or migrations? Then you build your system wrong. Technology should help and not hinder us. We need to focus on simplicity, not on overengineering.

    #TrueEngineering #ThinkBeforeYouCode #SoftwareCraftsmanship #QuestionEverything #BeyondTheFramework #UnderstandTheTools #CodeWithPurpose #SimplicityFirst #CleanArchitecture #DevMindset #EngineeringNotAssembling #TechWithoutMyth #UnderTheHood #CI_CDReality #AutomationTruths #NoMoreMagic #AskTheRightQuestions #AIWithoutUnderstanding #OverengineeringKills #LegacyByDesign #BuildForSimplicity #MinimalistTech

  31. True Engineering Isn't about using tools.

    It's in the questions.

    Too often, I see "engineering" reduced to assembling frameworks like IKEA furniture, follow the docs, trust the tool, ship it. But real engineering begins where the documentation ends.

    Do you know what that smart-syntax language is doing under the hood?
    Do you know how your beloved build tool behaves when it comes to automations and generic CI/CD pipelines?
    Do you know what your "schema-less" database sacrifices when concurrency climbs?
    Do you know how many runtime hacks exist to make your "native" build work seamlessly?
    Do you know how your framework manages threads… or fails to?

    Many don't. And that's the problem.

    We've built castles on sand because the sand came with good tutorials. Engineering isn't about how much you can plug in. It's about how much you understand, especially the parts no one talks about.

    If you're not asking, "What isn’t being said?"
    You're not engineering. You're just believing and praying.
    AI is a perfect example of many people which hype it but don't understand it.
    You have incidents, bugs, complexity, legacy and need time for maintenance or migrations? Then you build your system wrong. Technology should help and not hinder us. We need to focus on simplicity, not on overengineering.

    #TrueEngineering #ThinkBeforeYouCode #SoftwareCraftsmanship #QuestionEverything #BeyondTheFramework #UnderstandTheTools #CodeWithPurpose #SimplicityFirst #CleanArchitecture #DevMindset #EngineeringNotAssembling #TechWithoutMyth #UnderTheHood #CI_CDReality #AutomationTruths #NoMoreMagic #AskTheRightQuestions #AIWithoutUnderstanding #OverengineeringKills #LegacyByDesign #BuildForSimplicity #MinimalistTech

  32. This is brilliant advice. In times of "vibe coding" just… turn off AI agents for a bit and slowly, meticulously practice your chops with Katas: Take small, deliberate steps and great things will happen when you re-enable your AI assistant.

    youtu.be/ZW4AEKbHE28

    P.S. I do use AI tools (a lot!). But I don’t "vibe code," just like I never blindly copied and pasted code from Stack Overflow without understanding it.

    #CodeKata #TDD #LearnToCode #SoftwareCraftsmanship

  33. Are you inadvertently making your code more complex than it needs to be? Join Kevlin Henney's workshop 'Keeping it Simple' to explore the real cost of complexity in code, culture, and process. We'll tackle technical debt head-on and discover practical simplification strategies: buff.ly/4houjvO #CodeSimplicity #SoftwareCraftsmanship

  34. Are you inadvertently making your code more complex than it needs to be? Join Kevlin Henney's workshop 'Keeping it Simple' to explore the real cost of complexity in code, culture, and process. We'll tackle technical debt head-on and discover practical simplification strategies: buff.ly/4houjvO #CodeSimplicity #SoftwareCraftsmanship

  35. 🚀 Want to Grow Faster as a Developer? Improve Your Code Readability Today 🚀

    If you’ve ever opened an old piece of code and felt a wave of panic trying to understand what you were thinking, you’re not alone.

    #CodeReadability #DeveloperGrowth #SoftwareCraftsmanship #CleanCode #CSharp #CodeSimplicity #Dotnet #SoftwareDevelopment #TechEducation #LearnToCode #Programming @bot boost this

  36. 🤔 How did #Meta develop & launch the #ThreadsApp in just 5 months?

    Spoiler: They reused key parts of Instagram! Discover the inside story in this #CaseStudy!

    #InfoQ article by Zahan Malkani: bit.ly/3MbQDLa

    #SoftwareArchitecture #Threads #TechnicalDebt #reusecode #SoftwareCraftsmanship #SoftwareDevelopment #Agile

  37. Budapest calling! 🇭🇺 Dieses Jahr durften wir mit vier Kollegen erstmals an der #CraftConf teilnehmen! Zwei inspirierende Tage voller #SoftwareCraftsmanship & #SoftwareDelivery. 💡 Danke an die Organisatoren & Speaker für dieses tolle Event! 🙏 #craftconf24 #Weiterbildung

  38. Is there a way to "calculate" the date for the "Global Day of Coderetreat"? I know that it was the first Saturday (and Friday) in November this year, but it wasn't like that in the last years. Is there some kind of rule to that, so that I can plan ahead?

  39. Hi everyone! I am Vangelis and this is my #introduction!

    I do #softwareengineering for a living, building #coversationalAI agents. I like #philosophy, #martialarts and #foss.
    I'll mostly be posting about #python, managing engineers, #softwarecraftsmanship and building efficient teams.