If you’re a developer, you can’t have failed to spot that Stack Overflow is celebrating its tenth birthday. Similarly, I’m sure I’m not alone in owing a great deal to Stack Overflow in terms of my professional development. I thought about sending an eCard, but decided that a blog post might be a more fitting tribute. In today’s post, I want to share my memories of how transformative Stack Overflow was and the impact it had on me personally.
The policy at my new company is to prefix commit messages with the ID of the story they relate to. This week I tried doing an interactive rebase and came a little unstuck. Turns out that our use of hash symbols in commit messages upsets the interactive rebaser. Read on for the details…
Everyone loves a good technology horror story, right? The gorier the better in my experience. Well, over the last weekend we had an, um, “incident“. To my mind, it’s got all the ingredients of an excellent example of the genre: a small mistake, complicated conditions, and a big financial hit (mercifully averted). Sound like your kind of thing? Read on. I hope I do it justice…
After nearly a decade of coding in Visual Studio, a recent change in employment has put me in front of VS Code. The experience has had its ups and downs, so I thought I’d post a few pointers for anyone else who ends up in my situation. Moving beyond practical matters, I’d also like to take a moment to reflect on what the experience of weaning myself off Visual Studio has taught me. Zooming out further still, I close this post by considering what VS Code says about the state of the .NET ecosystem and try to put it all in perspective. If you can stomach all that, read on…
Just over a year ago I was emphatically singing the praises of Postman. Before that, I’d been using Fiddler to make calls to REST APIs and man, was that a drag! Recently I’ve had a similar experience when I discovered an alternative REST client called Insomnia. Unlike last time, however, I won’t be ditching the previous flavour of the month… Read on to discover why (for the time being at least) they both get a spot on my desktop.
I’ve been away for a while, but have finally stopped moving and am getting back into a normal routine. Since this is my first week in a new job, I thought it’d be a good time to give a quick update and to set the agenda for the next few posts.
It’s been a while since I last posted anything here, but that’s because I’ve been busy. My family and I are relocating to Australia from the UK and we’ve been making all the necessary preparations. This post is a bit of a digest of all the things that are happening, some observations about the process of applying for a job overseas, and finally some teasers for future blog posts.
Lately, I’ve been trying to improve my Salesforce skills. It’s been getting pretty interesting, to the point where I’d like to dedicate a post to it. (Hardcore .NET/C# readers may want to skip this week!) There are bits of the Salesforce developer ecosystem which I love and a few bits that are a little janky. I think the most interesting thing for developers is “Salesforce DX”, which I’ll try to explain briefly.
I’ve recently blogged about how excited I am by the promise of Blazor. Well, I’ve built my first Blazor app and, having tried it, I’m no less excited. There are still plenty of rough edges (which I talk about below), but it fundamentally works. In this post, I’ll try to outline the pitfalls as best as I can, in the hope that others find it useful. Please don’t construe anything I write as a criticism of the Blazor team – what they’ve done is already game-changing.