I’m not saying software is easy. In fact, I know I have some bad software too.

Lots of female programmers have suggested that they they don’t feel that the profession is very inclusive. Personally I’ve never had an issue as a woman, but I do run into this a lot:

Every time I see a story involving planes and “software mistake” I get nervous:

I use Azure DevOps for my freelance software development work. It is (relatively) affordable, and combines issue tracking with source control management and continuous integration. Previous issue tracking systems I used did not have these other features, which meant trying to isolate the code that was changed for particular bugs or enhancements was difficult. I like that Azure DevOps provides an integrated solution, but frankly the issue tracking part of it is not that great. Here are some of the things I wish it would do:

As is typical, industry news is filled with contradictions.

I ran into an issue in a SQL stored procedure where I was using ISDATE to test a string before stuffing it into a date column

Today I ran into a strange problem with a complex form that in ASP.NET WebForms. My form is using Telerik UI for ASP.NET AJAX, and has (among other things), two RadAsyncUpload controls and two RadListView controls. The form had previously worked successfully but after adding the second RadListView control we noticed that the first RadListView control wasn’t getting populated in some circumstances.

I don’t generally follow information about new language features in C#, since my goal is to never use it. But I learned about C# Records from watching this video on www.60second.dev, and was thinking that would be a cool feature for VB too. Good news – according to the documentation here, this is a planned feature for RemObjects Mercury as well. Excellent!

Theo has come up with a fantastic new add-on for Chromium that translates the C# examples on docs.microsoft.com to Swift, Oxygene or Mercury. Cool!

This post caught my eye this today, and it reminds me a lot of what I’ve been saying for quite some time. Everyone likes to focus on the tools or the development methodology (agile, waterfall, etc.) But the truth is that you can have successful waterfall projects, and successful agile projects. Yes, the approach can have an impact, but what’s even more important is the people. Do they communicate and work well together? Are they working towards the same goal, and is that aligned with the project stakeholder?