home.social

Search

967 results for “tdd_fellow”

  1. "Parallel Change" is one of my main go-to moves when refactoring, as it allows *me* to choose which tests (and code) to "break", instead of breaking a whole bunch all at once.

    Basically, allows me to apply MMMS(S)S (h/t GeePawHill) by letting me take small (safe) steps to the new world.

    #TDD #MMMSS #MMMS(S)S

  2. @shuttle I consequently use #TDD, where possible.

    Yes, sure, #Rust prevents a lot of bugs at compile time already, but not logic bugs.

    For example in #CSVDiff we have ~70 unit tests and ~12 integration tests. The only "bug report" we have ever gotten was due to a corrupted CSV file (being mistaken with a bug in diff):

    See here (qsv):
    github.com/jqnatividad/qsv/iss

    csv-diff:
    gitlab.com/janriemer/csv-diff

    In the future I'd like to add property and mutation testing as well 🤓

    #RustLang #Testing #UnitTest

  3. @shuttle I consequently use #TDD, where possible.

    Yes, sure, #Rust prevents a lot of bugs at compile time already, but not logic bugs.

    For example in #CSVDiff we have ~70 unit tests and ~12 integration tests. The only "bug report" we have ever gotten was due to a corrupted CSV file (being mistaken with a bug in diff):

    See here (qsv):
    github.com/jqnatividad/qsv/iss

    csv-diff:
    gitlab.com/janriemer/csv-diff

    In the future I'd like to add property and mutation testing as well 🤓

    #RustLang #Testing #UnitTest

  4. @shuttle I consequently use #TDD, where possible.

    Yes, sure, #Rust prevents a lot of bugs at compile time already, but not logic bugs.

    For example in #CSVDiff we have ~70 unit tests and ~12 integration tests. The only "bug report" we have ever gotten was due to a corrupted CSV file (being mistaken with a bug in diff):

    See here (qsv):
    github.com/jqnatividad/qsv/iss

    csv-diff:
    gitlab.com/janriemer/csv-diff

    In the future I'd like to add property and mutation testing as well 🤓

    #RustLang #Testing #UnitTest

  5. @GeePawHill Barrier to delete code has been lowered (as I always want, but also always needs work). Doing yet-another-spike only took two #pomodori, after which - more #QuietConfidence - I understand better how and why this stuff is built, and everything new is a library by default. It's a bit like the 'ratchet' metaphor of #tdd but with skill instead of code. Moving a step up, and then being relaxed in the knowledge, so I don't have to think or worry about it anymore.

  6. TDD: да или нет?

    Эта статья, в формате небольших тезисов, нацелена на открытие дискуссии на тему "Test Driven Development" – методологии разработки через тестирование. На моем текущем месте работы существует несколько мнений: начиная от полного принятия и стремления(к tdd), как к идеальному инструменту написания рабочего и лаконичного кода, вплоть до полного отвержения: TDD не работает, убивает время разработчиков, увеличивая при этом time-to-market. К каждому тезису, которые я выделил, я буду оставлять свой комментарий, стараясь быть объективным и не транслировать какую-либо позицию. Итак, поехали

    habr.com/ru/articles/839658/

    #tdd #test_driven_development #tests #time_to_market

  7. TDD: да или нет?

    Эта статья, в формате небольших тезисов, нацелена на открытие дискуссии на тему "Test Driven Development" – методологии разработки через тестирование. На моем текущем месте работы существует несколько мнений: начиная от полного принятия и стремления(к tdd), как к идеальному инструменту написания рабочего и лаконичного кода, вплоть до полного отвержения: TDD не работает, убивает время разработчиков, увеличивая при этом time-to-market. К каждому тезису, которые я выделил, я буду оставлять свой комментарий, стараясь быть объективным и не транслировать какую-либо позицию. Итак, поехали

    habr.com/ru/articles/839658/

    #tdd #test_driven_development #tests #time_to_market

  8. This book chapter is very relevant to me as I think about expanding JitterTed's #TDD Game (tddga.me)...

    "Board Games as Part of Effective Game-Based Learning Strategies"

    link.springer.com/referencewor

    #EducationalGames #Learning

  9. This book chapter is very relevant to me as I think about expanding JitterTed's #TDD Game (tddga.me)...

    "Board Games as Part of Effective Game-Based Learning Strategies"

    link.springer.com/referencewor

    #EducationalGames #Learning

  10. This book chapter is very relevant to me as I think about expanding JitterTed's #TDD Game (tddga.me)...

    "Board Games as Part of Effective Game-Based Learning Strategies"

    link.springer.com/referencewor

    #EducationalGames #Learning

  11. The use of #TDD is a great way to write #minimalCode that reduces #overengineering. By writing tests first, you force yourself to think about the requirements before you start coding. This can help you avoid writing code that you don't need

  12. The use of #TDD is a great way to write #minimalCode that reduces #overengineering. By writing tests first, you force yourself to think about the requirements before you start coding. This can help you avoid writing code that you don't need

  13. The use of #TDD is a great way to write #minimalCode that reduces #overengineering. By writing tests first, you force yourself to think about the requirements before you start coding. This can help you avoid writing code that you don't need

  14. Uso #ExtremeProgramming da quando facevo #debugging all'università, oltre 20 anni fa.

    Una cosa non cambia: scrivere codice è facile, definirne tutto il comportamento no.

    🎤 A #PyConIT 2026 porterò un #workshop su #Python 🐍 e #TDD:
    dalle variabili al primo test, per chiarire cosa il software debba fare prima di implementarlo.

    2026.pycon.it/it/event/primi-p

    #TalksAndWorkshops #python #pytest #BestPractices

  15. Uso #ExtremeProgramming da quando facevo #debugging all'università, oltre 20 anni fa.

    Una cosa non cambia: scrivere codice è facile, definirne tutto il comportamento no.

    🎤 A #PyConIT 2026 porterò un #workshop su #Python 🐍 e #TDD:
    dalle variabili al primo test, per chiarire cosa il software debba fare prima di implementarlo.

    2026.pycon.it/it/event/primi-p

    #TalksAndWorkshops #python #pytest #BestPractices

  16. The Apprentice Team: Stop setting up Early-Career Engineers to fail!

    Splitting new cohorts across busy product teams rarely works. Instead, keep them together with a dedicated coach. They learn TDD, Ensemble Programming, and CI/CD on real work in a structured 2-year journey.

    We need to engineer junior talent development.

    Full blueprint: medium.com/cloudnative-ly/the-

    #SoftwareEngineering #EarlyCareer #TechTalent #Onboarding

  17. Oh, so it is 2026 already? And the month is February already? The last thing I remember is diving into a rabbit hole called "Surely writing my own c2ffi translator for my WGPU project is no big deal."

    What's done is done. I am slowly recovering and ready to get back to my WGPU project. While the need for a custom translator is still debatable, I guess further practice will show if that's actually the case. Even if it was overkill, the time wasn't completely lost: I’ve learned more about Common Lisp and even did TDD for the first time in my life - who would've guessed it would finally happen in CL? :blobcat_thisisfine:

    Behold, the monstrosity! github.com/keelah-mt/cl-kl-c2f

    #commonlisp #cffi #wgpu #programming #lisp

  18. Oh, so it is 2026 already? And the month is February already? The last thing I remember is diving into a rabbit hole called "Surely writing my own c2ffi translator for my WGPU project is no big deal."

    What's done is done. I am slowly recovering and ready to get back to my WGPU project. While the need for a custom translator is still debatable, I guess further practice will show if that's actually the case. Even if it was overkill, the time wasn't completely lost: I’ve learned more about Common Lisp and even did TDD for the first time in my life - who would've guessed it would finally happen in CL? :blobcat_thisisfine:

    Behold, the monstrosity! github.com/keelah-mt/cl-kl-c2f

    #commonlisp #cffi #wgpu #programming #lisp

  19. Oh, so it is 2026 already? And the month is February already? The last thing I remember is diving into a rabbit hole called "Surely writing my own c2ffi translator for my WGPU project is no big deal."

    What's done is done. I am slowly recovering and ready to get back to my WGPU project. While the need for a custom translator is still debatable, I guess further practice will show if that's actually the case. Even if it was overkill, the time wasn't completely lost: I’ve learned more about Common Lisp and even did TDD for the first time in my life - who would've guessed it would finally happen in CL? :blobcat_thisisfine:

    Behold, the monstrosity! github.com/keelah-mt/cl-kl-c2f

    #commonlisp #cffi #wgpu #programming #lisp