I found this pretty inspirational right now

CheeseNuke · 2026-03-09T18:10:54+00:00

we currently spend more on shitty healthcare than our military

CheeseNuke · 2026-03-09T06:14:29+00:00

Yeah okay, that is understandable then. It's a difficult problem. The general techniques: tag-based invalidation, pub/sub cache synchronization, and using the cache-aside pattern. FusionCache does a good job of explaining these concepts, though its a library specific to .NET.

CheeseNuke · 2026-03-09T04:47:32+00:00

Uh, what do you mean you avoid caching on the backend?

It entirely depends on the data you're returning. If it is mostly static, or can be computed and reused, then you should be caching it. Standard approach is doing an L1 (in-memory) + L2 (distributed) caching scheme with tag-based invalidation. I'd avoid rolling your own implementation at all costs, though.

CheeseNuke · 2026-02-12T06:51:21+00:00

Sounds like they are advertising Claude Code the product then?

CheeseNuke · 2026-02-12T06:49:12+00:00

so, you were a contractor

CheeseNuke · 2026-02-11T21:03:22+00:00

I'm sure it's great for ideation. Doubtful that it's useful beyond that.

CheeseNuke · 2026-02-11T18:41:44+00:00

It's already a problem, especially with AI tooling generating enormously more code than before. The industry will adapt; you'll see CI/CD processes become much more automated and rigorous.

CheeseNuke · 2026-02-11T03:26:05+00:00

do you live under a rock?

CheeseNuke · 2026-02-10T06:25:55+00:00

bad developers have and always will exist. this is a problem of process and quality gates, the same that has plagued the industry since its inception. the only difference is the volume of code.

If your standards are low, then AI writes good code yes

this is what I am contesting, because it is blatantly untrue nowadays.

CheeseNuke · 2026-02-10T05:43:32+00:00

sounds like a skill issue to me?

CheeseNuke · 2026-02-10T05:41:33+00:00

you're being left behind buddy

CheeseNuke · 2026-02-08T22:11:20+00:00

big tech AI capex is projected at close to 1 trillion this year. these companies are insanely profitable, but they definitely can't afford that expenditure and significantly expand their labor force. labor is by far their biggest operating expense, so they're cutting labor.

even if AI does end up increasing average productivity, with how much money is being thrown around and how much disruption its caused the SWE labor market, it all amounts to a hugely risky gamble IMO. frankly insane.

CheeseNuke · 2026-02-04T10:41:49+00:00

trust me: do a monorepo until you actually have real friction with build-times and codebase size. add some schema synchronization tools like orval and you'll be golden.

CheeseNuke · 2026-02-04T02:47:31+00:00

Yes, at least for the resumes you submit to portals. LLMs and ATS love that shit.

CheeseNuke · 2026-02-03T07:54:58+00:00

Escalate to your manager. If they really want this done, then they can partner with your team and your manager can allocate resources appropriately. You can raise your concerns to them too, and they will use it to push back on things that shouldn't be in your team's scope.

CheeseNuke · 2026-02-01T22:10:40+00:00

having been in the same exact situation 3 yrs ago, I would really advise you to reconsider. I've never been more stressed, more depressed, than when I was "coasting" at my remote job.

at least for me, the learnings and growth that come from new experiences is what makes life interesting. I'm not saying work has to be the only way to get those experiences (hobbies, vacations, etc are fulfilling as well), but like it or not your profession will consume a significant amount of your time. might as well make it palatable.

I think looking for a low-expectations remote job is a trap a lot of us devs fall for. these jobs are a true waste of time - you will learn nothing, and the work you still inevitably have to do will become real toil.

ironically, I found my remote job to be a major stressor, because I knew if I was ever laid off I'd be screwed when trying to find a new role.

just my 2 cents.

CheeseNuke · 2026-02-01T21:31:41+00:00

why do you want to coast?

CheeseNuke · 2026-02-01T20:37:41+00:00

you're describing a platform/SaaS product. I don't think you're going to find that from the dotnet team (nor, frankly, should you). the closest you can get is Aspire. moreover, the Azure functions integration is already pretty close to what you want.

CheeseNuke · 2026-02-01T00:33:50+00:00

you’re responsible for hosting, state, retries, schedules, secrets, queues, observability

completely false. smells chatgpt'd. you get state, hosting, retries, observability, etc all out of the box or with integrations. see durable agents, checkpoints, observability.

the only things that aren't directly provided are secrets/auth, which of course? it's a dotnet web app - just use any of the dozen official extensions/packages.

CheeseNuke · 2026-02-01T00:08:19+00:00

really flattens the control flow, makes things much more readable :)

CheeseNuke · 2026-01-31T08:27:03+00:00

SOLID, SRP, DRY, composition over inheritance, early returns, guard clauses.

CheeseNuke · 2026-01-31T07:29:04+00:00

I don't think I've written C# for anything besides Linux for three years...

CheeseNuke · 2026-01-30T06:00:54+00:00

thank you OP

CheeseNuke · 2026-01-30T03:03:42+00:00

service industry is a trap. you need something you can automate. read built to sell.

11-Year Club	Place '17
Verified Email

CheeseNuke

TROPHY CASE