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?

Part of me wants to believe that this product can really deliver a solution to migrate my Web Forms applications to ASP.NET Core. Certainly those of us with legacy Web Forms applications would like to see a successful tool that moves these applications forward without a complete rewrite.

On the other hand, since Microsoft isn’t supporting VB.NET on ASP.NET Core, in my case any migration tool would also switch it to C#, which isn’t my preferred way forward. Also, they seem to price based on the size of the project, and don’t provide clear pricing information on their site for any of their migration tools, suggesting to me that it might be cost prohibitive in many cases.

Visual Studio Magazine reports on two new reports on language and technology usage that Visual Basic is a top in-demand programming language in 2021, above C#.

I had completely forgotten about the Option Infer feature in Visual Basic, but noticed it the other day when I was checking some other settings.

This article isn’t quite as bad as the title, Programming jobs for losers — and how to escape them | InfoWorld, would suggest. It is certainly true that some programming jobs (just like all jobs) are more fun and engaging than others. That being said, it is unfortunate that the article approached this by calling the programmers in these jobs “losers”.

Today, in stupid programmer tricks, I updated my copy of Xcode on the Mac because Apple helpfully told me there was an update. Unfortunately, suddenly I was having trouble compiling iOS applications because I wasn’t referencing the correct iOS SDK. I wanted to go back to the previous version, but I couldn’t find the download. Now suddenly this is all working again (maybe I just needed a Mac and/or a Windows reboot?) but now I also discovered where previous versions of Xcode can be found, so I’m documenting it so that I can find it again.