1. X
  2. Mukesh Murugan
Log inSign up
Mukesh Murugan
2,050 posts
user avatar
Mukesh Murugan
@iammukeshm
Helping 50k+ .NET Engineers reach Senior Levels | Microsoft MVP YT: youtube.com/@codewithmukesh
Trivandrum, India
codewithmukesh.com
Joined April 2020
2,180
Following
5,785
Followers
RepliesRepliesArticlesArticlesMediaMedia
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
Don't miss what's happening
People on X are the first to know.
Log inSign up

New to X?

Sign up now to get your own personalized timeline!

Create account

By signing up, you agree to the Terms of Service and Privacy Policy, including Cookie Use.

  • user avatar
    Mukesh Murugan
    @iammukeshm
    13h
    Every .NET dev hits this fork the first time they need background work, and most pick by vibes. Both run work outside the request pipeline. The difference is how much they make you write. The lower-level option gives you a start method and a stop method. You own the whole
    933
  • user avatar
    Mukesh Murugan
    @iammukeshm
    Jul 25
    The same interview question can get you hired or quietly end the conversation. The difference is never the definition. It's whether you know why. Take a simple one. The interviewer shows you a read-only endpoint returning a list and asks what you'd change. The answer that ends
    620
  • user avatar
    Mukesh Murugan
    @iammukeshm
    Jul 24
    I don't read the code my agents write. I barely open the IDE anymore. Sounds reckless. For a long time, I'd have agreed. Robert Martin, aka @unclebobmartin, framed the shift in a way that stuck: in agentic development, you trust the constraints, not the code review. That's
    777
  • user avatar
    Mukesh Murugan
    @iammukeshm
    Jul 24
    Most .NET devs using Claude Code set up one file and stop there. That one file helps. But the real leverage is in treating the whole config folder as five distinct tools, each with a clear job. The memory file is your standing rules and project facts. It loads every session, so
    945
  • user avatar
    Mukesh Murugan
    @iammukeshm
    Jul 24
    The clock code in most .NET apps is a static call your tests can never control. That one fact causes more flaky time bugs than any library ever will. DateTimeNow reads the local clock of whatever machine happens to run the code. Deploy that same service to a server in another
    1.1K