DaedTech Digest: Agile, Code Review Horror Stories, Test Smells
First of all, some housekeeping. Back when I finally gave Disqus the boot, it reverted comment settings to WordPress’s defaults. One of these was, apparently, to turn off comments after 28 days.
Sorry about that.
Backlink spammers notwithstanding, I welcome comments on posts new and ancient. So I want to be clear that I did not do this intentionally.
Alright, now, back to business. I’m bringing you the second installment of the DaedTech digest wherein I aggregate some of my posts instead of cross posting. The feedback on this format has, so far, been positive, inasmuch as I’ve gotten it. So let me know if you have thoughts one way or the other.
This is part of a pivot that I’m planning with DaedTech, for which I’m currently ideating a bit on a mission statement for the blog. I’m thinking at the moment that the mission, going forward, will be “helping software developers become the boss of their software development.” This could include opportunist plays to earn promotions in the office as well as help with side hustles and going free agent.
And Now, the Digest
But, I digress. Onto the digest. Note that these posts are ones that I wrote some time back. I’m doing beefed up digests to catch up, and then I’ll start linking you to the various posts I’ve written for clients during the week.
- I wrote a post for TechTown Training (ASPE) about the relationship between agile development and refactoring. This echoes the dynamic that Martin Fowler once referred to as “flaccid Scrum” where organizations “go agile” by having different meetings, but approaching the software they same way. I talk about how you need to change your software practices as well.
- Here’s an intro style post that I wrote on the topic of static analysis for NDepend. I’ve always found that people tend to needlessly over-academic-ize static analysis, so I figured I’d treat the world to a less self-important explanation.
- For Submain, I wrote a post called “Code Review Horror Stories.” I’d say this probably speaks for itself.
- Another one for TechTown called “Unit Testing Smells: What Are Your Tests Telling You?” I think this is an important topic because all too frequently I see people have a hard time testing their code and conclude that unit testing sucks. If your code is hard to test, something is wrong with your code.
- And, finally, I did another CodeIt.Right, Rules Explained Post.
Anyway, I think that 5 a week should eventually get us current. But, if not, I’ll crank up the juice on these. Man, putting these together, I realize that I write a LOT of blog posts. I guess it’s no accident that I wound up founding a blogging business.