Tim Corey

@James_M_South Sure! Just shoot me an email or DM and we can get something set up.

Does anyone who does videos or podcasts want to talk about ImageSharp and co?

Here are 10 C# libraries to save you time and energy: youtube.com/watch?si=a7F_s…

Have you ever wanted to access appsettings.json during setup in Program.cs? Here is how to do it. youtube.com/watch?si=U9tDH…

Let's separate the AI hype from the AI reality: youtube.com/watch?si=f-jz9…

Adding Swagger UI to our API - C# on Linux Episode 15 by @IAmTimCorey youtube.com/watch?v=KyrH3D… #aspnetcore

Here is what is going to be important in the future for software developers: youtube.com/watch?si=FqFqp…

🎙️New Betatalks: Why Developers Still Matter in the Age of AI. @rickvdbosch and @oscarvantol talk with @IAmTimCorey about learning, fundamentals, and why understanding your code matters. They also discuss AI as a tool for developers, not a replacement. buzzsprout.com/1622272/episod…

Using comments in Visual Studio is even easier now. youtube.com/watch?si=WVJ1j…

As a software developer, don't forget to work on upgrading your job, not just your software: youtube.com/watch?si=dYpGn…

Let's discuss the right C# web framework for your project: youtube.com/watch?si=TQinQ…

I mostly agree, but I think there is more to it than just that the world is changing. Yes, the load on their servers is astronomically higher. That is going to cause scale issues. And it is. However, the reliability issues with GitHub didn't start when the additional load of AI hit. They started way before then. Back when Microsoft took over, added more functionality to Actions, added Codespaces, etc. That reliability was always touchy. The added load of AI made it exponentially worse. But then, you also have the issue of how GitHub has handled the issues. The removed the uptime percentages on their status page (they are back now) and they don't show an overall uptime status because it looks bad. But even now, their status page lies. Their own incident pages show downtime when their status page shows no incidents for that day. It isn't an isolated issue. Multiple days have this issue. Also, not all of these issues that they've had recently are scale issues. The missing PRs from yesterday was a scale issue (although they say it was a bot attack), but the merge queue issue from the 23rd was a code issue. At the end of the day, companies rely on GitHub. GitHub is failing to do their job. It isn't all their fault, but it is absolutely a problem that needs to be addressed. It has been bad for months. Something needs to change.

I find much of the discourse around GitHub discouraging. The world changed on them faster than most. They need to improve to handle it. They know they need to improve. Everything suggests they are working on it. Punching them while they do so is not productive, IMHO.

GitHub's AI Problem - How AI Is Damaging the Platform youtu.be/TJujaEVO7rQ

Automate your web app deployments with GitHub Actions. youtube.com/watch?si=z4QNV…

Sat down with @IAmTimCorey the master of practical, no‑nonsense developer teaching. We dug into how devs can keep learning in a world reshaped by AI. Clear insights, real guidance. youtu.be/P-WttH3ULAc

Sometimes you need to succeed despite your management. youtube.com/watch?si=BT63K…

HA/DR has a cost and you will never protect yourself against everything. Learn how to balance the cost vs risk: youtube.com/watch?si=8Ax1m…

Every developer fails. Here are 3 ways every developer fails and how to avoid these failures: youtube.com/watch?si=HLfq1…

Installing Aspire And New Project Setup - C# on Linux Episode 12 by @IAmTimCorey youtube.com/watch?v=YV2p0N… #aspnetcore #aspire

Don't get caught with out-of-date skills. Upgrade your skills today: youtube.com/watch?si=uezaL…

Learn how to get better results from your resume: youtube.com/watch?si=VN3fg…