best-practices - lesser daemon

30

Mar

do not engage

I got a bitter and nasty email this morning that kind of threw off my whole day. I don't, generally, like it when people are mad at me, especially in a circumstance like this one where I am pretty much entirely confident that I have done nothing wrong. In this case I was furious about the whole deal and had to stop and calm myself down before proceeding.

Not responding might be the best option - and usually is if it's a social media stranger - but this was someone I know and I have never much liked ghosting people.

Sustainable Software

About a week ago I had a nice long conversation with my brother about wine. This is something that happens a lot in my family: my brother is a wine rep, my uncle spent a while running a small wine importer, I've worked in wine production and sales, and the rest of my family really enjoys drinking wine even if they've kept it out of their professional lives. I am the annoying friend who likes to talk about and think about the wine we're drinking at dinner but I pale in comparison to most of my family.

My brother has

Testing Is Good, Actually

Me not writing tests til I'm nearly done with a project.

After a mere ten years of writing code professionally, I have finally attempted to start a project by writing out tests for its core functionality first. Apparently this is a whole thing. Who knew?

I tend to fall into the Grug school of thought on testing. A lot of the time I don't think it's super worthwhile to start writing tests before I really understand the problem space of a project, especially since historically I've switched frameworks and tools so often that the first few weeks of work on