Kerrick Long (code)Hey all, @kentbeck is livestreaming! https://www.youtube.com/watch?v=ouGJSC5SdRQ
#Programming #Python #TDD #TestDrivenDevelopment #Genie #LLM #AI #VibeCoding #AIAssisted #SoftwareEngineering
YouTube
Jan Van RyswyckOn 4 ๐๐ง๐ 5 ๐๐๐๐๐ฆ๐๐๐ซ 2025, Iโll be hosting my workshop ๐๐๐ฅ๐ฅ-๐๐๐ฅ๐๐ง๐๐๐ ๐๐๐ฌ๐ญ-๐๐ซ๐ข๐ฏ๐๐ง ๐๐๐ฏ๐๐ฅ๐จ๐ฉ๐ฆ๐๐ง๐ญ at the ๐๐ซ๐๐ข๐ง ๐๐ฆ๐๐๐ฌ๐ฌ๐ฒ ๐ข๐ง ๐๐ง๐ญ๐ฐ๐๐ซ๐ฉ.
โฐ The early bird discount expires this Friday, 31/10! So donโt wait if you want to master the art of writing loosely coupled and highly maintainable automated developer tests.
๐ Secure your spot now: https://principal-it.eu/training/well-balanced-test-driven-development.html
#tdd #testdrivendevelopment #unittests #unittesting #softwaredesign
Nacho CougilHere you've the slides I shared about #TestDrivenDevelopment at #JavaCro ๐
http://tiny.cc/how-john-tdd-javacro
And here you've the feedback form, in case you can help me (1min of your time) with some words about how I can improve ๐ ๐ฃ๏ธ
http://tiny.cc/how-john-tdd-feedback
#TDD #testingFirst
http://tiny.cc/how-john-tdd-javacro
And here you've the feedback form, in case you can help me (1min of your time) with some words about how I can improve ๐ ๐ฃ๏ธ
http://tiny.cc/how-john-tdd-feedback
#TDD #testingFirst
Ey #Java developer!
If, by any chance, you're at #JavaCro and are interested in listening to a history ๐๏ธ about how "somebody" started to practice/use #TDD and see an example with #SpringBoot come today at โฐ 3:55 to Hall B ๐
#TestDrivenDevelopment
https://2025.javacro.hr/eng/Agenda#:~:text=how%20John%20started%20to%20like%20TDD%20(instead%20of%20hating%20it)
If, by any chance, you're at #JavaCro and are interested in listening to a history ๐๏ธ about how "somebody" started to practice/use #TDD and see an example with #SpringBoot come today at โฐ 3:55 to Hall B ๐
#TestDrivenDevelopment
https://2025.javacro.hr/eng/Agenda#:~:text=how%20John%20started%20to%20like%20TDD%20(instead%20of%20hating%20it)
Domain-Driven Design BarcelonaNext Wednesday, October 15, starting at 18:45 weโre holding the #Meetup "TDD & DDD From The Ground Up by @ChrisSimonAu at N26's office.
Check out more information and confirm your attendance at:
https://www.meetup.com/dddbcn/events/311446227/
#DDD #DDDesign #DomainDrivenDesign #DDDBCN #TDD #TestDrivenDevelopment
SoftwareArchitecture Gathering๐ค How can we combine #AI with #TestDrivenDevelopment without losing the human touch? @claresudbery shares insights from her workshop "How Can You Combine AI With Test Driven Development?" and her session "Letโs Stop Making Each Other Feel Stupid" on fostering learning, psychological safety, and human-centered practices in software development.๐ก
Read the full interview ๐ https://t1p.de/d9p1z
#SAGconf #SoftwareArchitecture #HumanInTheLoop #PsychologicalSafety #TDD #LearningCulture #iSAQB
Alternatively, with Test-Driven Development (TDD), software developers start by writing a small test then write just enough code to make it pass, and iterate โ building quality into software from the get-go instead of after the fact. This approach aligns heavily with the shift-left testing philosophy where quality is built in, rather than inspected in later. (2/2)
#tdd #testdrivendevelopment #unittests #unittesting #softwaredesign
Software developers using traditional methods start out by first writing the code. Only when the work has already been completed do they shift their focus to testing. (1/2)
#tdd #testdrivendevelopment #unittests #unittesting #softwaredesign
SnackOverflowOk this is fun!
My #bzip2 implementation in #Rust is coming along nicely and I've been loosely following a #TestDrivenDevelopment approach which makes working with LLMs a breeze. If an AI assisted rework turns tests red you can immediately start debugging, tuning and optimizing, which is nice and focused.
I'm done with everything including the Move-To-Front Transform encoding and am already getting text file sizes down by 25 to 30%.
Next up: Huff huff huff!
When naming tests, avoid using technical names of functions/classes. When we encorporate the name of a function into the descriptive name of a test method, and the respective function is later renamed, then the description of the test becomes completely useless. A better approach is to describe the behaviour of the production code under test. That way we can refactor more confidently without rendering the names of our tests as obsolete.
