News for hackers. Stuff that matters.

lancerkind

Re: on Sunday February 11, 2024 @12:03PM (#39336366)
The interview series starts at episode 252 and is ongoing.
Interview of Indian software engineer made famous for discovering lander wreckage on moon. Interviewed by NYT and others. Episodes 251, 252, and ongoing.
Re:Test Automation Pyramid illustrated with music on Sunday February 12, 2023 @01:50PM (#34765597)
Macro tests, micro tests, subcutaneous tests. And CI.
Re:Spider-Man:Miles Morales Came to Sony Playstation on Sunday December 18, 2022 @06:43PM (#34045808)
clickable link to the podcast interview: https://lancerkind.com/series/scifi-thoughts/

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/

( Read More... | 1 comment | on HN )
episode 175 Real Life Discoverer of Lost Lunar Lander—Shanmuga

episode 176 Software Engineer gets the Keys to the City and State

episode 177 How Discovering Moon Debris made a Software Engineer Famous

Re:Game Fun for the Virtual Office on Saturday April 11, 2020 @01:09PM (#22842719)
Drawful 2 is great for zoom happy hours. https://www.jackboxgames.com/were-giving-away-drawful-2-for-...

And it's free for a few weeks.

Re:Game Fun for the Virtual Office on Saturday April 11, 2020 @01:07PM (#22842704)
This game requires collaboration and leverages the "doer" and "thinker" model. The negative is that the players will all need to buy a low-cost license. https://apps.apple.com/app/keep-talking-nobody-explodes/id14...

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/

( Read More... | 2 comments | on HN )

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

( Read More... | no comments | 2 points | on HN )
Re:What Does “Proficient” at TDD Look Like? on Sunday March 03, 2019 @05:17PM (#19297288)
About Spikes: They are a tool to be employed when no one on the team has confidence in how to solve a technical problem. Spikes are used to deliver learning through doing. They are a Plan B. Used when we can't do Plan A--write the tests and the code with TDD. Because it takes longer to write tests later, the Spike is a simple implementation to learn something. Once the learning has happened, then you go into the code and use TDD to develop the product code. The spike code is never meant to be product code.

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?

Re:What Does “Proficient” at TDD Look Like? on Sunday February 24, 2019 @03:27PM (#19240430)
So "thinking test first" means you've reached proficiency. How would you observe "thinking test first" behavior?
Re:What Does “Proficient” at TDD Look Like? on Sunday February 24, 2019 @01:29PM (#19239816)
Nice points here.

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

( Read More... | 6 comments | on HN )

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

( Read More... | no comments | 2 points | on HN )

Older »