home.social

#craftconf — Public Fediverse posts

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

fetched live
  1. Hello from #CraftConf Budapest! As always, I'll be doing my best to liveskeet all the talks I attend (until my computer runs out of battery, which happens earlier every year) Keynote speaker: "Slow Down to Speed up", @[email protected]

  2. @trishagee I'm writing my shiny new talk for #CraftConf using a shiny new tool I built which is the subject of my shiny new talk!

    #meta #ouroboros #allTheShinies

  3. 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

  4. you can find the unabridged (and slightly updated) version of my #craftconf talk "from here to resilience" here: speakerdeck.com/ufried/from-he, discussing what resilience is, how to get there (using a prototypical path) and if you always need to go the whole way. enjoy if you like ... ;)

  5. Summarizing a long function with the help of ChatGPT seems quicker than doing it without, but I worry that it robs the programmer of gradually building a mental model of the intent of the code. I'm genuinely not yet sure how much to worry about that. #CraftConf

  6. TDD, even with ChatGPT's help, seems to nudge the programmer towards FP-style design: decouple the pieces and then compose all the pieces at the end. #CraftConf

  7. TDD with ChatGPT seems to raise the stakes of the integrated tests scam. How interesting! #CraftConf

  8. In seeing Llewellyn Falco's example of a multistep prompt to ChatGPT, I notice that that's what I independently discovered when I first started using it as a partner to practising reading and writing Swedish. #CraftConf

  9. Most LLM prompts need to add guardrails to avoid overconfident responses #CraftConf

  10. Uptime is not equivalent to customer-relevant availability #CraftConf

  11. Focusing primarily on latency and error rates generally works with product development flow too #CraftConf

  12. “Toil” seems to be the SRE jargon for “waste” #CraftConf

  13. Right way to measure latencies:
    1. Tier MTTx by criticality
    2. Measure percentiles
    3. Impacts, not counts

    #CraftConf

  14. Cap’n Proto mentioned by Dave Thomas as a superior alternative to ProtoBuf capnproto.org #CraftConf

  15. Wondering how many XP / Agile efforts fail due to not aggressively simplifying designs #CraftConf

  16. I expect Dave is going to suggest that a good legacy strategy is focused, not a broad transformation (which is generally true for all good strategy) #CraftConf

  17. My next talk at #CraftConf is coming up this afternoon: Testing Without Mocks at 1:40pm on Platform 2. Come see an innovative technique for simplifying and speeding up your tests. It works with legacy code! No design changes or special tools needed.

  18. 25 years later and one of the key strategies for encouraging change is to wait for a crisis to emerge. #CraftConf

  19. If you talk to each other, then you don't need rules. But if you don't talk to each other, then you need rules. It is possible to follow rules that promote talking to each other.

    That works better when it's voluntary and intentional.

    #CraftConf #xplives