lancerkind
Software Engineer gets recognition from mayor and governor: episode 251 and 252
Test Automation Pyramid illustrated with music
Agile Thoughts uses music to illustrate how test automation and Continuous Integration works: https://agilenoir.biz/en/agilethoughts/test-automation-pyramid-series/
Spider-Man:Miles Morales Came to Sony Playstation
PlayStation developer Chris Barton interviews with SciFi Thoughts about his work with PlayStation, what it's like to work on AAA games, and what's the story with Miles Morales. Listen to episodes 209 through (upcoming) 211: https://lancerkind.com/series/scifi-thoughts/
episode 176 Software Engineer gets the Keys to the City and State
episode 177 How Discovering Moon Debris made a Software Engineer Famous
DevOps engineer makes discovery on the moon, now governor knows him
Shanmuga (Shan) has an IT industry day job, but that didn't stop him from discovering the debris from lunar discovery mission and becoming famous for it. Hear him tell the story during his SciFi Thoughts interview, episodes 175, 176, 177, and (upcoming) 178: https://lancerkind.com/series/scifi-thoughts/
Why Developers Don't TDD (An IT Audio Drama)
A fun voice acted drama that gets to the heart of the matter: https://agilenoir.biz/en/agilethoughts/why-developers-dont-tdd-a-radio-drama/
And it's free for a few weeks.
Game Fun for the Virtual Office
What games are fun to play with a team in the virtual office?Please share your favorites and the Agile Thoughts podcast will produce an episode about the topic. https://agilenoir.biz/en/agilethoughts/
Systems Thinking novel Agile Grande releases chapter 3
Blockchain entrepreneur talks of travails with secure email product
Listen on Episode 78 on Agile Thoughts: https://agilenoir.biz/series/agile-thoughts/?utm_source=hackernews
Is Your Thanksgiving Agile Enough? Kansan for Family Agility
SciFi series Orphan Black continues as audio drama, SciFi Thoughts interview
UX Designers and Agile Team Love/Hate
Agile Thoughts podcast ( https://agilenoir.biz/series/agile-thoughts/?utm_source=hnews ) is seeking designers who are passionate for/against Agile. We will collect interviews to create a series on Agile Teams and the UX Designers who love/hate them. Send Lancer an email, with subject line “UX Agile”: [email protected] and he’ll coordinate with you for a convenient time to record a chat.Feel...
Camelot, the Holy Grail, and Freeing the Human Spirit with Fast Agile
Founder of FAST Agile talks through how FAST Agile is beyond Scrum. Agile Thoughts is running a series with episodes 43, 44, 45, 46 and ongoing. Show archive: https://agilenoir.biz/series/agile-thoughts/
“Plausibility” in Science Fiction
Compelling Science Fiction magazine’s editor lays it out in episode 38 on ScFi Thoughts podcast: https://lancerkind.com/series/scifi-thoughts/
Don't you think it's a misuse if ALL of your development is using spikes?
Don't you think that this use of Spikes is a crutch to avoid something you are unmotivated do and haven't invested time to learn?
I'll have to do a show on "spike and stabilize." This strategy of "late" refactoring and micro testing is something we are forced to do when encountering untested legacy code. So this as part of the "tool kit" to be a master and difficult for someone who is proficient.
My perception is that Spike and Stabilize, always takes longer than TDD because:
1) I have to spend time "re-discovering" what the code is supposed to do in order to write the test.
2) If I need to use the debugger or print statements to learn what the code is doing,
these temporary diagnostics aren't automatable and the value achieved
can't be checked into source code.
3) I have to work harder at bad design decisions that occur when not thinking about unit testing.
4) I find APIs aren't as intuitively crafted because TDD forces you to define your interface
to get started (a simple version which evolves as needed) rather than
the steps of: "write code, get it working, go back and refactor and test"
5) The costs increase with Spike and Stabilize with the time delta between
the moment the code is written to the moment tests are added.
6) Plus Spike and Stabilizes allows people to be pressured into doing the
wrong thing: ship it now, worry about test automation later.
If you're disciplined, this won't matter because you can simply say no.
If you're not, test debt increases. TDD removes this possible risk.
Thank you for the suggestion on explicitly adding the TDD "mantra" of red/green/refactor. In episode 22, TDD with a Stack Overflow Master Developer, it explores TDD versus Spike and Stabilize Later in a dramatic presentation: https://agilenoir.biz/podcast/022-tdd-with-a-stack-overflow-...
This story of a developer going through the challenges of getting his team to do TDD starts with episode 14: https://agilenoir.biz/series/agile-thoughts/Thank you for the name, "spike and stabilize." It sounds better than "Test Later Strategy" but I fear it obscures the risky and uncertain future.
What Does “Proficient” at TDD Look Like?
When we say someone is proficient at TDD, what outcomes have they achieved? What capabilities do they have?I’ll take your suggestions to put together another TDD episode for Agile Thoughtshttp://agilenoir.biz/en/agilethoughts/why-developers-dont-tdd-a-radio-drama/Here is what I’ve got so far.Here is what I’ve got so far.You’re proficient when (scroll left to right to read): You can write a...
Ask HN: What Does “Being Proficient” at TDD Look Like?
When you say someone is proficient at TDD, outcomes have they achieved? What capabilities do they have?I’ll take your suggestions to put together another TDD episode for Agile Thoughtshttp://agilenoir.biz/en/agilethoughts/why-developers-dont-tdd-a-radio-drama/Here is what I’ve got so far.You’re proficient when: You can write a dozen tests in an eight hour day. You are have refactored 4 big...