Tim Corey @IAmTimCorey

Microsoft MVP. I make learning easy. If you want to learn C#, this Mastercourse will teach you more than a degree: https://t.co/98XPHj83Op iamtimcorey.com Dallas, TX Joined November 2011

Tweets

4K
Followers

11K
Following

125
Likes

2K

Tim Corey @IAmTimCorey

25 minutes ago

Knowing what employers are looking for is an important first step in getting hired. youtube.com/watch?si=oouHS…

0 0 0 74 1

View Details

Tim Corey @IAmTimCorey

3 days ago

The factory pattern is a powerful one to master. Here is how to use it in C#: youtube.com/watch?si=4n8EW…

0 0 2 510 5

View Details

Tim Corey @IAmTimCorey

a week ago

Learn how to upload files using Blazor in this free mini course on YouTube: youtube.com/playlist?list=…

0 0 2 445 1

View Details

Tim Corey @IAmTimCorey

a week ago

Do you know why partial classes exist in C# and how to use them? youtube.com/watch?si=bJ9w9…

0 0 4 588 1

View Details

Tim Corey @IAmTimCorey

2 weeks ago

Learn how to do CSS isolation in Blazor in less than 10 minutes: youtube.com/watch?si=ewkC8…

0 0 2 514 1

View Details

Tim Corey @IAmTimCorey

2 weeks ago

AI Hurts Everything - The Downside of the AI Hype youtu.be/oCs2hLsgwR8

0 0 1 458 1

View Details

Tim Corey @IAmTimCorey

2 weeks ago

Here are 7 tips to make your work less stressful. youtube.com/watch?si=FsSB2…

0 0 2 592 0

View Details

Tim Corey @IAmTimCorey

3 weeks ago

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

1 0 2 322 0

View Details

Tim Corey @IAmTimCorey

3 weeks ago

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

0 4 6 797 3

View Details

Tim Corey @IAmTimCorey

3 weeks ago

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

0 0 6 637 2

View Details

Tim Corey @IAmTimCorey

4 weeks ago

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

0 0 6 466 0

View Details

ASP.NET Core News @aspnetcore_news

4 weeks ago

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

0 1 19 2K 8

View Details

Tim Corey @IAmTimCorey

a month ago

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

0 0 2 479 1

View Details

Betabit | Managed software development @Betabitnl

a month ago

🎙️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…

0 1 3 361 0

View Details

Tim Corey @IAmTimCorey

a month ago

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

0 0 1 409 1

View Details

Tim Corey @IAmTimCorey

a month ago

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

0 0 2 454 1

View Details

Tim Corey @IAmTimCorey

a month ago

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

0 2 3 517 0

View Details

Tim Corey @IAmTimCorey

a month ago

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.