I am glad it was so helpful.

Awesome! It sounds like you are doing everything I recommend.

Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/

Excellent! Best wishes on your job search.

This is a complicated question to answer, because some things seem to be mixed together. First, the cloud does not mean serverless. The cloud is just someone else's computer. You can run Virtual Machines in the cloud. You can host your website on what looks like a traditional web server. You can also use serverless technology (which is still running on a server, it is just that you don't configure the server or have access to it). Second, when you want to move a desktop app to the cloud, you have to define what that means. It could mean that you turn your desktop app into a web app. Or, it could mean that you host your desktop app as a download on a web server. I'm going to assume the first option. In that case, you might have to redo everything, or you might not. It depends on how the desktop app was written. If most of the code was in a class library and only the user interface-specific code was in the desktop app project then creating a web front-end is not a total rewrite. It could mean rewriting 20% of the app. However, if the desktop app has all of the code in the UI project itself and not separated out, then yes, it could mean a total rewrite. If you want to see how to architect a desktop app the right way, where you can move to the web easily without redoing a lot of work, check out the TimCo Retail Manager playlist here on my KZfaq channel. We build a WPF app (desktop app) that is supported by an API. Later, we build a Blazor WebAssembly app (web app) that uses the same API. We don't rewrite much code at all. That design allowed me to have both a desktop app and a web app without reworking the entire app. That means that I can continue to maintain both and give both types of users what they want. Finally, desktop apps aren't the same as web apps. Just saying "I want this desktop app in the cloud" isn't necessarily a good call. It depends on the app. You might lose functionality. You are definitely going to face new challenges that you didn't have to consider.

I know a guy who supports the software of the postal service in an African country. That is his only income. The hardware that runs their software can no longer be bought (1970's equipment) so every piece of device software has to be manually written by him to work on newer hardware and tie in with existing software.

You are welcome.

Often the ideas available from people or the internet are outdated as well. Python IS slow if you use its basic loop for very large data sets. If you use (say) pandas for your loops through data are suddenly faster than C or C#. Most people you speak to say .NET is best avoided because it ties you into the Microsoft/Windows stable but that idea is more than 5 years outdated.

There's a balance with everything. You don't want to focus too much on the performance of a language since you aren't creating the next Google, but you also don't want to ignore it either. The key is to have a balance.

The problem is that being that definitive sounds good but isn't actually good advice.

@@IAmTimCorey I totally get that, but this video missed the mark because it didn't really encapsulate what you clearly wanted. You don't have to be absolute to provide definition and I really feel that nuance was what was lacking here.