2min chapter

Go Time: Golang, Software Engineering cover image

Bob Logblaw Log Blog

Go Time: Golang, Software Engineering

CHAPTER

Using Log Lines in Test Driven Development

I'm imagining some of your scenarios are writing logs to like help debug stuff. And I can imagine that those ones, yeah, over time, stop adding value. Like once you have tests and everything, you know, it's all working. It's kind of like, is that running every single time that function runs really adding value? Whereas like other parts of it definitely could be. Yeah, I tend to do that for marking bits, just that it reached it. So that's probably why I go through and remove the log statements. But also if I'm doing test driven development, I will tend to log a bit less really,. Unless there's specific kind of tricky behavior, something

00:00

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode