About JorgenHoc
JorgenHoc publishes in-depth technical guides for .NET developers — focused on Entity Framework Core, async/await patterns, and cloud hosting decisions.
Every article is built around one principle: be specific. Complete code examples you can copy and run, explicit trade-offs instead of vague advice, and — where the topic warrants it — interactive components you can step through rather than read about.
What you'll find here
- EF Core guides — migrations, LINQ, relationships, performance patterns, and the N+1 query problem solved properly
- Async C# guides — async/await, Task vs ValueTask, ConfigureAwait, IAsyncEnumerable, cancellation tokens
- .NET hosting comparisons — Azure, AWS, Railway, Fly.io, Render — plan tiers, deployment steps, and honest trade-offs
The interactive difference
The three pillar guides embed live, interactive components directly in the page. The async/await guide has a step-by-step execution visualizer, the EF Core guide has a LINQ→SQL translator, and the hosting guide has a filterable, sortable comparison table. They aren't gimmicks — for those three topics they're the fastest way to build an accurate mental model.
Who writes this
JorgenHoc is written by Jorge Calderón, a software engineer based in Bogotá, Colombia, who has spent over a decade building and operating .NET applications in production: Entity Framework Core data layers on SQL Server, ASP.NET Core APIs, and deployments on Azure, in containers, and on the smaller hosting platforms compared on this site.
Every number published here was produced on his own hardware or on accounts he pays for. The BenchmarkDotNet runs, the EF Core statement counts, the k6 latency tests, and the Railway, Render, and Azure deployments behind the hosting screenshots all come from the public dotnet-samples repository, so anyone can rerun them. When a measurement contradicted what the documentation implies, the article says so.
Corrections are welcome. If a claim is wrong, open an issue on the samples repository or use the contact page, and the article will be fixed with a visible revision date.
GitHub profile ↗ · LinkedIn ↗ · Benchmarks & sample code ↗
Questions, corrections, or suggestions? Visit the contact page — feedback on any article is always welcome.