Welcome to yet another edition of DaedTech Digest Friday. I bring this edition to you from a hotel in Detroit instead of an ocean-front condo in San Diego because, as it turns out, I’m insane. Actually, I’m just doing a quick consultation and codebase assessment for the week. And coming to Detroit to do that…
I’ve talked a lot about how not to position yourself lately. Last week, I suggested you not do it by tech stack of framework or whatever. And before that, I suggested you not do it by being a laborer. In general, I’ve talked a lot about positioning lately. But all of the talk has been…
Happy Digest Friday, readers! As the US lurches toward an inflection point on the “I can’t believe this is necessary” subject of how not to regularly gun down its own children, I’ve been heads down dealing with logistics. My own issues seem downright petty next to that one, but nevertheless they’re mine, and I’ve had…
Today, I’m going to keep plugging away with another mid-week post in the developer to consultant series. To recap, I’ve talked recently about how you need to start by figuring out your positioning and then about how that positioning should orient around problem solving instead of laboring. Today, I’m going to build on that momentum. I’m…
Happy Monday, readers! I’m getting back on track with reader question Monday once again. No more excuses about bad web hosting issues. Today’s question is about test driven development. Specifically, it’s about test driven development when you’re trying to get a team to do it — a remote team. Here’s the question (directed at me…
