Ashvind Maudhoo

I write codes, take photos & shoot videos

[Anton Martyniuk @AntonMartyniuk]

I built a working Minimal API with EF Core in 3 files.

You can do the same in 10 minutes.

No solution file.
No csproj.
No project setup.

Just three .cs files and the dotnet CLI.

This is file-based apps in .NET 11 Preview 3.

And it's a complete shift in how you can build internal tools and prototypes.

𝗧𝗵𝗲 𝟯-𝗳𝗶𝗹𝗲 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲

1. Order.cs
↳ Plain POCO with Id, OrderNumber, CustomerName, Amount, CreatedAt

2. OrdersDbContext.cs
↳ The EF Core DbContext with inline Fluent API mappings

3. main.cs
↳ DI setup, Minimal API endpoints, app[.]Run()

That's it: 3 files in a folder.

𝗧𝗵𝗲 𝗺𝗮𝗴𝗶𝗰 𝗶𝘀 𝗶𝗻 𝟰 𝗱𝗶𝗿𝗲𝗰𝘁𝗶𝘃𝗲𝘀 𝗮𝘁 𝘁𝗵𝗲 𝘁𝗼𝗽 𝗼𝗳 𝗺𝗮𝗶𝗻.𝗰𝘀

#:sdk Microsoft[.]NET[.]Sdk[.]Web
↳ Unlocks WebApplication and ASP .NET Core types

#:package [email protected]
↳ Pulls in the SQLite provider on first run

#:include Order.cs
↳ Brings the entity into the compilation

#:include OrdersDbContext.cs
↳ Brings the DbContext into the compilation

Four lines replace an entire csproj and sln.

Below the directives, it's standard ASP .NET Core code.

I can run it with a single command:

𝚍𝚘𝚝𝚗𝚎𝚝 𝚛𝚞𝚗 𝚖𝚊𝚒𝚗.𝚌𝚜

First run restores EF Core.
Every run after that is fast.

You now have a real web API with a real database.

✅ When file-based apps win

→ Internal tools without ceremony
→ Prototypes you can share as a single folder
→ Demos that work in a few minutes
→ Replacing Python scripts where you want strong typing
→ Onboarding new devs without csproj confusion

❌ When you should NOT use them

→ Multi-project solutions with shared libraries
→ Apps with custom MSBuild logic
→ NuGet package authoring
→ Production apps with full CI/CD and test projects

And when your script outgrows itself, one command converts it:

𝚍𝚘𝚝𝚗𝚎𝚝 𝚙𝚛𝚘𝚓𝚎𝚌𝚝 𝚌𝚘𝚗𝚟𝚎𝚛𝚝 𝚖𝚊𝚒𝚗.𝚌𝚜

You get a full csproj with all directives translated.

I've covered the complete workflow with all code samples in this week's newsletter issue.

📌 Read the full guide:
↳ https://t.co/oenvrHRypH

Inside you'll find:
✅ Full HTTP health-check tool walkthrough
✅ Complete Minimal API with all 4 endpoints
✅ Exact EF Core mappings, DI setup, and migration step
✅ The checklist for when to convert to a full project

Where would you try file-based apps first - scripts, prototypes, or internal tools?

——

𝗣.𝗦.: 𝗔𝘇𝘂𝗿𝗲 𝗖𝗼𝗽𝗶𝗹𝗼𝘁 𝗠𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗔𝗴𝗲𝗻𝘁 𝗶𝘀 𝗛𝗲𝗿𝗲
Microsoft's Azure Copilot Migration Agent can turn complex migration data into clear answers. With natural language prompts, you can evaluate readiness, risk, ROI, and automate landing zone requirements to make confident decisions for you and your team.

Download the free playbook to get started: https://t.co/pPsd2dRg0P

——

♻️ Repost to help other .NET developers build faster

➕ Follow me ( @AntonMartyniuk ) to improve your .NET and Architecture Skills

[Sonal Shukla @sonalshukla3377]

🎯 𝟮𝟱 𝗩𝗦 𝗖𝗼𝗱𝗲 𝗘𝘅𝘁𝗲𝗻𝘀𝗶𝗼𝗻𝘀 𝗘𝘃𝗲𝗿𝘆 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗦𝗵𝗼𝘂𝗹𝗱 𝗧𝗿𝘆

The right VS Code extensions can save hours of work, improve code quality, and make development way more productive 🚀

Here are 25 powerful VS Code extensions every developer should definitely try.

1. Prettier
♦ Code formatter that enforces consistent style.

2. ESLint
🔹 Find and fix problems in your JavaScript code.

3. Live Server
♦ Launch a local development server with live reload.

4. GitLens
🔹 Supercharge Git in VS Code.

5. Auto Rename Tag
♦ Rename paired HTML/XML tags automatically.

6. IntelliCode
🔹 AI-assisted development to boost your productivity.

7. Thunder Client
♦ Fast, lightweight REST API Client for VS Code.

8. Material Icon Theme
🔹 Beautiful material design icons for your files.

9. Bracket Pair Colorizer
♦ Colorizes matching brackets for easier reading.

10. REST Client
🔹 Send HTTP requests and view responses in VS Code.

11. Tailwind CSS IntelliSense
♦ Intelligent Tailwind CSS class completion.

12. Better Comments
🔹 Improve your code with colored comments.

13. Path Intellisense
♦ Autocomplete filenames and paths in your project.

14. Error Lens
🔹 Highlight errors, warnings, and messages in your code.

15. Code Spell Checker
♦ Spelling checker for source code.

16. Docker
🔹 Build, manage, and debug Docker containers.

17. Remote SSH
♦ Edit and debug code on remote machines via SSH.

18. Tabnine
🔹 AI code completions that save you time.

19. Import Cost
♦ Display import size in your code editor.

20. Markdown All in One
🔹 All you need to write Markdown easily.

21. Color Highlight
♦ Highlight colors in your code.

22. CodeSnap
🔹 Take beautiful screenshots of your code.

23. TODO Highlight
♦ Highlight TODOs, FIXMEs, and other annotations.

24. Inline Fold
🔹 Fold code blocks inline to keep your view clean.

25. ChatGPT - CodeGPT
♦ AI assistant right in your VS Code. Code, explain, refactor, and more.

❤️ Like
🔁 Retweet
🔖 Bookmark

Follow @sonalshukla3377 for more such posts

[Ritesh Roushan @devXritesh]

System Design Series - Day 30/30

Deployment Strategies That Prevent Disasters

The most dangerous moment in engineering is deploying to production.

Most junior engineers know one strategy: push it and hope.

Here are 5 deployment strategies that separate junior from senior engineers 👇

1. Strategy 1: Rolling Deployment

The most common and safest starting point.

Instead of updating all servers at once, update one server at a time.

- Server 1: Updated and healthy
- Server 2: Updated and healthy
- Server 3: Updated and healthy

If Server 2 fails health check:
Stop deployment.
Only Server 1 and 2 are affected.
Roll back Server 2.
Server 3 stays on the old version.

Zero total downtime.
Built-in safety net.

2. Strategy 2: Blue-Green Deployment

Run two identical production environments.

- Blue: Current live version (serving all traffic)
- Green: New version (deployed but receiving zero traffic)

Steps:
1. Deploy new version to Green
2. Run full test suite on Green
3. Switch traffic from Blue to Green (instant)
4. If problems: Switch back to Blue (instant rollback)

Zero downtime.
Instant rollback.
Gold standard for zero-risk deployments.

Cost: Double the infrastructure (worth it for critical systems).

3. Strategy 3: Canary Deployment

Named after canary birds in coal mines.

Instead of switching all traffic at once:

- Deploy new version
- Send 5% of traffic to new version
- Monitor for 30 minutes
- If stable: Increase to 20% → 50% → 100%

If problems at any stage: Route 100% back to old version.

Only 5% of users are ever affected.

Used by Netflix, Google, and Amazon for every major release.

4. Strategy 4: Feature Flags

Ship code without activating features.

Deploy the new checkout flow to production.
Feature flag is OFF.

- Internal team: ON for employees only
- Beta users: ON for 10% of users
- Full rollout: ON for everyone

Problems during rollout?
Turn the flag OFF.
Instant rollback without redeploying.

Tools: LaunchDarkly, Unleash (open source), or simple database boolean.

Separates deployment from release.

5. Strategy 5: Database Migration Safety

The deployment strategy nobody teaches but everyone needs.

You cannot change database schema and deploy code simultaneously.

Old code running while migration runs = broken queries.

The safe pattern (backwards compatible migrations):

- Week 1: Add new column (nullable, old code ignores it)
- Week 2: Deploy new code (uses new column if present)
- Week 3: Backfill data in new column
- Week 4: Remove old column

Never break existing queries during migration.

This is why experienced engineers fear schema changes more than new features.

Which deployment strategy does your team currently use?

Reply with the number (1-5).

This concludes the System Design Series.

Thank you for following along for 30 days.

#SystemDesign #Deployment #Backend

[Leonard Rodman @RodmanAi]

This 32-min Stanford lecture by Graham Weaver will teach you more about living boldly than 10 years of self-help books.

Bookmark it and give it 32 minutes, no matter what. It’s the best way to start your week.

[liminal @Liminal1988]

25 sentences I wish I'd read sooner in life

[Alok Kumar @Alokkumarzz]

Instead of watching an hour movie, watch this. In 14 minutes, an Anthropic engineer who wrote Building Effective Agents will teach you more about building agents right than most developers figure out on their own in months.

[Suhani @tiwarisuhani_11]

Today I learned about Load Balancers and the algorithms behind how traffic gets distributed across servers efficiently

[Anuj @anujcodes_21]

20 SITES TO GET A REMOTE JOB THAT PAYS IN USD

1. https://t.co/WDnpJokAiY

2. https://t.co/ELaM9Mkn7v

3. https://t.co/D0sY3Rd2F9

4. https://t.co/oJOC71SkSm

5. https://t.co/59MAByq1Mo

6. https://t.co/lBhJMbGYWV

7. https://t.co/uWSSNdLg3a

8. https://t.co/KZaPDGjx0u

9. https://t.co/zo4SZ1VujI

10. https://t.co/RCidUObRKI

11. https://t.co/JYkUOn8GCy

12. https://t.co/F0XrUDeEq9

13. https://t.co/GnpFxxyhav

14. https://t.co/IWKIALj8Y1

15. https://t.co/5EYrjuuh5y

16. https://t.co/Xqx3IAGAtH

17. https://t.co/rMOr8qAvqu

18. https://t.co/0EPuE5n0RF

19. https://t.co/D7uYOIv7mc

20. https://t.co/hFl1b4EGif

Follow me @anujcodes_21 for more AI IDEA.

[Radha Tripathi @Radha_AI]

A man spends 50 years teaching at MIT.

He knows his time is running out.

So he records one last lecture — everything he knows, distilled into a single hour.

He died 5 months later.

This is that lecture.

The most important hour you'll watch this week. 👇
Bookmark it for later

[Dhanian 🗯️ @e_opore]

WHAT IS MICROSERVICES ARCHITECTURE?

Grab the Software Architectures Ebook:
https://t.co/w4kamEyznT

[AilaunchX @Ai_Tech_tool]

Instead of watching an hour of Netflix, watch this 2 hour hour Stanford lecture will teach you more about how LLMs like ChatGPT and Claude are built than most people working at top AI companies learn in their entire careers.

[Vala Afshar @ValaAfshar]

A masterclass on ‘how to speak’ by MIT professor Patrick Winston - 15 key lessons

[Dhanian 🗯️ @e_opore]

Load Balancing Architecture

[Al Tach @MindsetF28912]

Howto lead different generations

[Dr Milan Milanović @milan_milanovic]

𝗦𝗦𝗢 (𝗦𝗶𝗻𝗴𝗹𝗲 𝗦𝗶𝗴𝗻-𝗢𝗻) 𝗲𝘅𝗽𝗹𝗮𝗶𝗻𝗲𝗱

SSO is an authentication process that allows users to access multiple apps with a single master key.

This is accomplished using a central authentication server that stores the user's credentials and verifies them for each application.

Here are 𝘁𝗵𝗲 𝘀𝘁𝗲𝗽𝘀 that happen if you want to access the Trello web app by using your Google account:

1. Use the Trello login web page and select Google account as a login method
2. Trello redirects the user to the Google login page
3. User is served with the Google login page
4. The user enters their Google credentials
5. Google sends authentication info to the SSO Authorization server
6. If credentials are valid, the Authorization server returns the auth token (SAML)
7. Google sends the auth token to the Trello
8. In the last step, Trello sends the token to the Google Authentication server to validate its
9. If the token is valid, Trello will allow access to the user and store the session for future interactions

✅ The 𝗯𝗲𝗻𝗲𝗳𝗶𝘁𝘀 of SSO are:

🔹 Improved user experience. Users do not need to remember multiple usernames and passwords.
🔹 Increased security. Users are less likely to reuse passwords across applications.

❌ The 𝗱𝗶𝘀𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 are:

🔸 Single point of failure. One of the most notable disadvantages is that SSO creates a single point of failure. If the SSO system is compromised, the attacker could access all connected applications and services.
🔸Security risks. If credentials are compromised, the security of all connected applications could be at risk.

Some 𝗰𝗼𝗺𝗺𝗼𝗻 𝘁𝘆𝗽𝗲𝘀 𝗼𝗳 𝗦𝗦𝗢 are:

🔹 𝗦𝗔𝗠𝗟-𝗯𝗮𝘀𝗲𝗱 𝗦𝗦𝗢. This is the most common type of SSO. It uses the SAML protocol to exchange authentication information between the SSO server and applications.
🔹 𝗢𝗽𝗲𝗻𝗜𝗗 𝗖𝗼𝗻𝗻𝗲𝗰𝘁. This is a newer SSO type based on OAuth 2.0. It is a more straightforward protocol than SAML and is easier to integrate with web applications.

And 𝗽𝗼𝗽𝘂𝗹𝗮𝗿 𝗦𝗦𝗢 𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻𝘀 are:

➡️ Azure Active Directory
➡️ Okta
➡️ Ping Identity
➡️ OneLogin
➡️ Google Cloud Identity Platform

[Nainsi Dwivedi @NainsiDwiv50980]

This is the Claude Code Resource Bible.

54 tools.
Agents. MCP servers. Skills. Automation.
Most people still haven’t discovered this stack.

That’s your edge. ⚡

Here’s the curated version (3 best links per section) 👇

🟦 OFFICIAL

• https://t.co/4o8VOOgZ2s — Claude Code docs
• https://t.co/laPvgykw3v — official MCP servers
• https://t.co/N6xZRiUqlv — free certification

🟧 DIRECTORIES

• https://t.co/TGr4PjSLLR — everything Claude Code
• https://t.co/GcZ9KMVMtv — MCP list
• https://t.co/q0U424jY9Z — 50+ MCPs

🟨 MCP SERVERS

• https://t.co/q6xQX7hnCh — browser automation
• https://t.co/ml2Sd1SZTP — database + auth
• https://t.co/relFondA98 — deploy apps

🟩 SKILLS

• https://t.co/3u23g80Wej — browser control
• https://t.co/ZHAmHlxVRF — full dev workflow
• https://t.co/4lDVEtnBYN — recurring tasks

🟪 MULTIPLEXERS

• https://t.co/NTv0UMML2b — agent terminal
• https://t.co/SXr00Xdc2w — orchestrate agents
• https://t.co/NDTR0qvuia — parallel dev

🟥 AGENT FRAMEWORKS

• https://t.co/x0hXlDlR0M — multi-agent coordination
• https://t.co/g2Vlux0sib — agent collaboration
• https://t.co/oDcSBofEpp — NousResearch agents

⚙️ AUTOMATION

• https://t.co/DqNqV1EB9v — workflows in code
• https://t.co/QAT0L6HrNj — monitor agents
• https://t.co/vtOYfhlZAy — self-hosted infra

📚 ARTICLES

• https://t.co/tYcXf1HzyT — best CLI tools
• https://t.co/zVGTx4Vaza — top MCP servers
• https://t.co/qBhy12KNj9 — parallel agents

This is basically the Claude Code ecosystem map.

Learn it now → you're early
Ignore it → you're late

Bookmark this. You'll need it

[Evan Luthra @EvanLuthra]

INSTEAD OF WATCHING NETFLIX TONIGHT, WATCH THIS 1 HOUR FULL CLAUDE COURSE.

THANK ME LATER!!!

[Nainsi Dwivedi @NainsiDwiv50980]

Claude is actually insane.

Most people are using it like a smarter Google.

That’s the mistake.

You can literally turn it into a personal teacher, strategist, and thinking partner — all in one.

Here’s what changed everything for me:

Instead of asking for answers…

I tell Claude:

“After every task, explain how you thought, what you considered, what you rejected, and what I should learn from this.”

Now every output comes with:

• the reasoning behind decisions
• alternative approaches it didn’t choose
• tradeoffs most people ignore
• mistakes and dead ends
• how everything connects
• what an expert would notice
• lessons I can reuse in totally different problems

This is a completely different experience.

You’re not just getting results.

You’re learning how to think.

And once this clicks, you realize:

AI isn’t just a tool for doing work faster.

It’s a system for compounding intelligence.

You can use it to: • break down complex topics
• simulate expert thinking
• learn any skill faster
• turn ideas into structured plans
• improve your decision-making

Most people will keep chasing better prompts.

But the real unlock is this:

Make AI explain its thinking, not just give answers.

That’s where the leverage is.

Almost no one is doing this yet.

Bookmark this — you’ll want to try it once and you won’t go back

[Reads with Ravi @readswithravi]

“You escape competition through authenticity.” - @naval

[Shrimad Rajchandra Mission Dharampur @SRMDharampur]

True intelligence comes from 3 core abilities: solving problems with clarity, adjusting with grace in any situation and making decisions that are thoughtful.

When these qualities grow, so does your inner strength. Nurture them a little every day and watch the shift within you.