In the last couple of months, I’ve been doing some hefty juggling. Being a very disorganized person naturally, doesn’t really reconcile with managing multiple suppliers, following up, and making sure I don’t become a bottleneck. For my agile viewers – I’ve tried post-it notes. I found out that this didn’t work when working with external
Sometimes things I do actually work.So I thought of putting them in writing. Best case scenario, you, the reader, might get something out from them. Worst case – I made you laugh or just feel pity. It’s a win-win either way. There is an overarching theme here: process analysis. These are things that I become
After the LIDNUG presentation, we stayed online to discuss unit testing experiences. A couple of things stayed with me from that talk. One: we’re (we developers) are obsessed with tooling and technology (you didn’t expect hard news here, right?). Our main focus should be about solving the business problem first. But, us geeks, we like
Last week I gave my “unit testing in the wild” presentation on LIDNUG. It was nice, and once the recording is up I’ll get all the info. But I wanted to talk about the experience. First of all: people, I’ve hit the jackpot. I’ve hit on one of the best ways to extract gold out
Last week, I gave a presentation at the Israeli SharePoint user group on unit testing SharePoint applications. Slides below. Me closer (lurking in the shadows). As an objective observer, I compared the two and only alternatives for Isolation frameworks for SharePoint: Typemock Isolator and Microsoft Moles. And here’s my objective decision: Isolator wins by a
I’ll be presenting (in Hebrew) on unit testing SharePoint apps this Wednesday. More information here.If you’re interested in the topic (SharePoint., unit testing or both), come one, come all.
After my last post, I got some feedback, that I didn’t really answer the question in the title. So I’m going to fix that. Roughly speaking, 10% of developers are doing unit testing today (Let’s call them group A). Some 15% have heard or tried (B), and the rest don’t even know it exists (C).
.. and why I’m willing to live with it. Brian Harry has started a series of posts on how he writes code. By the way, he is responsible to manufacture a small software package called Microsoft TFS, so I usually listen to what he has to say, The first posts refer to both his iterative
As part of my design for testability talk, I talked about how tools and languages impact testability. Then I came about Brett Schuchert’s post about TDD and if it’s language neutral. The post concentrates on how different TDD looks like in different languages. Moreover, how it is interpreted, based on the language of choice. And
InfoQ has a treasure trove of good advice. Go read it.