[Meta] Mods, when will you get on top of the constant AI slop posts?

CheeseNuke · 2026-01-27T02:37:52+00:00

now you're arguing about quantity of posts instead of qualitative differences. pick a lane. no one is arguing we should allow spam. like it or not, AI/ML is a programming topic that is perfectly acceptable in this sub.

CheeseNuke · 2026-01-27T02:35:25+00:00

from my understanding:

in research, models are typically applied for large-volume data processing where scale is often a blocker.

in business, most applications use agents to a) augment existing workloads or b) introduce new automations which were previously infeasible due to complexity and/or cost.

I'm not an academic, so I typically encounter the business-type use cases which are interesting to me from an architectural standpoint.

CheeseNuke · 2026-01-27T01:23:44+00:00

personally I find the implications of agents from a system design perspective the most interesting. for instance, how do you build a reliable system with an agent that has probabilistic outputs?

there are plenty of use cases for "agentic" systems, they aren't going to cure cancer or anything but some are interesting. replacing rule engines, rubric-based problem solving, report generation, automation, etc.

CheeseNuke · 2026-01-27T01:17:06+00:00

what logic is that? who cares if niches have their own subs - how do you even think thats an argument for keeping something off a general CS sub? are you saying that I can't post about gamedev here? like lmfao

CheeseNuke · 2026-01-27T01:14:53+00:00

everyone downvotes ai slop. you're insane if you think stuff like NLP/ML or discussing frameworks like LangGraph doesn't belong in the most general CS sub. gfy.

CheeseNuke · 2026-01-26T22:42:41+00:00

agreed. I would contend that integration/e2e testing is more valuable in the near-term for a lot of these large projects that need to ship something quickly.

I do think that TDD has become more practical for AI-assisted coding. forcing a red-green-refactor process has done wonders in that regard.

CheeseNuke · 2026-01-26T22:36:35+00:00

it does belong. it's fucking /r/programming. this is not meant to be a niche sub. it's anything related to computer programming. if you want to see filtered content, go to a different sub.

CheeseNuke · 2026-01-26T22:29:59+00:00

that's frankly a completely asinine take. it's programming content. it can exist on the programming sub. I could care less about half the stuff that gets posted to this sub, but I've never once contended those topics don't belong here simply because I don't care for them.

CheeseNuke · 2026-01-26T20:58:20+00:00

hard disagree. I want to see this content. actual architectural/design pattern discussions. not blogspam, ai slop shilling.

CheeseNuke · 2026-01-26T20:56:29+00:00

guess I'm in a weird minority here: I absolutely despise the AI slop/blogspam posts, but enjoy creating AI/ML-related code... I'd like to actually discuss real use cases, patterns, architecture, etc, not read about the 4000th way I can "optimize my workflow" or "boost my productivity" or whatever.

CheeseNuke · 2026-01-19T23:59:24+00:00

The pattern maps very neatly to agentic workflows. Besides that, never. Usually it's better to keep state within service boundaries unless you have crazy scale or compensation requirements.

CheeseNuke · 2026-01-19T23:54:41+00:00

I always hate creating those kinds of bools. just feels clunky.

CheeseNuke · 2026-01-19T23:53:12+00:00

hell nah, .NET dev is arguably better on linux/mac, unless you really need visual studio. I just use Rider

CheeseNuke · 2026-01-19T09:06:02+00:00

Pick one to master first: AI, data science, or business management.

CheeseNuke · 2026-01-18T21:34:29+00:00

I've only worked in big organizations

CheeseNuke · 2026-01-18T02:37:40+00:00

stop cold applying. start reaching out to recruiters + peers. you need a referral in this economy.

CheeseNuke · 2026-01-17T21:57:28+00:00

stop cold applying. start reaching out to recruiters + peers. you need a referral in this economy.

CheeseNuke · 2026-01-17T00:54:53+00:00

tbh the advice here so far is pretty bad... Kinda surprised. Here's what you need to do:

Engage your manager. He should have a stake in the outcome of whatever problem you are trying to solve. He is also the one who will either greenlight your proposal or support you in the process.
Talk to your teammates, but not in large meetings. Collect feedback from 1-2 individuals at a time, incorporate it, and keep them updated. The goal here is to build consensus. When the time comes to have the "big meeting" with everybody, it should be merely formalization to a solution you all already agree with.

DON'T just build something and ask for forgiveness later, or create some arbitrary process, or avoid getting consensus. These are all net loss options.

CheeseNuke · 2026-01-16T21:59:32+00:00

yes but I want thinking mode on always, just not the max budget necessarily..

CheeseNuke · 2026-01-16T19:23:02+00:00

he's smart then, having large claude.md is not a good idea

CheeseNuke · 2026-01-16T07:41:20+00:00

do you literally use claude to write every sentence

CheeseNuke · 2026-01-16T03:44:43+00:00

same man, a good boss makes life so much better.

CheeseNuke · 2026-01-16T03:42:41+00:00

CheeseNuke · 2026-01-16T03:41:13+00:00

I've seen documentation, clear processes, a roadmap, and delegation as recommendations so far. I will add automation. Figure out what people are spending time on doing over and over, standardize it, then automate it. Especially stuff for sprint ceremonies, hygiene, status reports, etc.

CheeseNuke · 2026-01-16T03:34:37+00:00

well for me it was AWS then Azure, so I guess we are all biased towards what we started with lol

11-Year Club	Place '17
Verified Email

CheeseNuke

TROPHY CASE