home.social

Search

682 results for “tdd_fellow”

  1. 🧠 Struggling with complex input scenarios? Use the 'Triangulation' technique to test one variable at a time. Say goodbye to missed and over-tested scenarios.

  2. Preemptive design specialization often leads to more issues down the line. Stick to what you know you need.

  3. Why wait for a formal code review when you can do an ad-hoc session? If you spot an issue or improvement in code, invite the responsible team member for a quick, on-the-spot review. 🖥️

  4. Questioning the business value of a task is not just about rejecting wasteful work. It's also an educational exercise that increases the team's understanding of the business, customer, and product. 📚

  5. Continuous refactoring is a trainable muscle. Do it hundreds of times per day, and you'll be ready to tackle massive architectural changes with almost zero risks. It's not just a practice; it's a skill set.

  6. Think a task list is overkill for small tasks? Maybe. But when tackling large, complex problems, it's your best friend. It'll keep you aligned and laser-focused. 🎯

  7. Reach and Endurance: Understand the boundaries of a problem—how much it 'reaches' into other aspects of your life and how long it will 'endure.' It'll help you strategize solutions more effectively.

  8. 💡 Inaction is costlier than wrong action. If you're still contemplating, you've already lost valuable time. Embrace uncertainty and act, you can always pivot.

  9. Integrity isn't just about keeping promises; it's also about refusing work that doesn't align with your ethics. Your values are your moral compass in a world of complex decisions. Stick to them. 🧭

  10. Questioning the business value of a task is not just about rejecting wasteful work. It's also an educational exercise that increases the team's understanding of the business, customer, and product. 📚

  11. Why wait for a formal code review when you can do an ad-hoc session? If you spot an issue or improvement in code, invite the responsible team member for a quick, on-the-spot review. 🖥️

  12. Preemptive design specialization often leads to more issues down the line. Stick to what you know you need.

  13. Neglecting integrity in software delivery can lead to harmful outcomes. From dark UI patterns to unethical business practices - we must remain vigilant.

  14. I’m happy to announce my workshop, ‘𝐖𝐞𝐥𝐥-𝐁𝐚𝐥𝐚𝐧𝐜𝐞𝐝 𝐓𝐞𝐬𝐭-𝐃𝐫𝐢𝐯𝐞𝐧 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭’ on 21 𝐚𝐧𝐝 22 𝐌𝐚𝐲 2025 at 𝐓𝐡𝐞 𝐁𝐫𝐚𝐢𝐧 𝐄𝐦𝐛𝐚𝐬𝐬𝐲 𝐢𝐧 𝐀𝐧𝐭𝐰𝐞𝐫𝐩. This two-day, hands-on workshop blends theory with practice in a real-world codebase. You'll be collaborating together with fellow attendees to master the art of writing loosely coupled and highly maintainable automated developer tests.

    (1/2)

    #tdd #unittests #softwaredesign #softwarecrafting

  15. It was a successful weekend for , the new federated meetup alternative: Now there is a header on every page, and on the homepage the communities are displayed with their picture in a responsive grid. Architecture tests with were introduced and thanks to we have a test coverage of 100%. This gives us a good feeling for refactorings and also when testing PRs. I'm already looking forward to spending a few evenings working on it next week! Screenshots will follow soon! 🤓

  16. Has anyone used the #PersonalSoftwareProcess (a.k.a. #PSP)?

    How did you learn it? I am trying to learn by myself, but the learning process highly recommends taking classes with a coach/trainer. Is it really worth it?

    I have also found that the exercises are aimed towards a #waterfall approach, so have you used it with a highly #iterative / #agile approach like #tdd?

    As a reference, I'm following the #psp for the 21st century (softwareexcellencealliance.org) but there are also materials for the whole thing:

    * PSP for Engineers - softwareexcellencealliance.org
    * PSP Fundamentals - softwareexcellencealliance.org

    (It's also difficult to understand which one to select. There are overlaps in both versions)

    I read the book from W. S. Humphrey but I found it somewhat difficult to follow after the first few chapters.

    Call to all #developers #coders #programmers #devs

    #SoftwareEngineering #SoftwareDevelopment #software #Development #personal #process #CMMI

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

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

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

  20. [Перевод] 37 советов и приемов по написанию качественных тестов для фронтенда

    Мне нравится писать тесты. Написание теста и последующее обновление кода для его прохождения — всегда увлекательный процесс. Но нет ничего хуже, чем выяснение того, что проверяют существующие тесты (раньше я сам часто был автором таких тестов). Представляю вашему вниманию мои советы по написанию высококачественных тестов для фронтенда.

    habr.com/ru/companies/timeweb/

    #javascript #js #testing #test #jest #vitest #timeweb_статьи_перевод #тестирование #тест #tdd

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

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

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

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