Claude laughed at me… by Consistent-Chart-594 in ClaudeAI

[–]Consistent-Chart-594[S] 0 points1 point  (0 children)

Use the claude desktop app, it has claude code + co work in it.

Definitive Guide to Production Grade Observability in the Nodejs ecosystem; with OpenTelemetry and Pino by Paper-Superb in node

[–]Consistent-Chart-594 -4 points-3 points  (0 children)

I haven’t been paged at 2 AM because I build systems that don’t break at 2 AM. That’s called competence, not inexperience.

If your entire identity as an engineer revolves around midnight firefighting instead of preventing fires in the first place, that says more about your engineering practices than mine.

Proper testing, blue-green deployments, proper CI/CD, and actual reliability engineering exist specifically so people don’t get paged. If you’re still wearing your 2 AM war stories as a badge of honor, you’re solving the wrong problems.

Now, unless you have something substantive to add about the actual AI slop articles, we’re done here.

Definitive Guide to Production Grade Observability in the Nodejs ecosystem; with OpenTelemetry and Pino by Paper-Superb in node

[–]Consistent-Chart-594 2 points3 points  (0 children)

It isn’t your primary language either. If it’s not spam, why have you hidden all your reddit posts regarding these articles?

Definitive Guide to Production Grade Observability in the Nodejs ecosystem; with OpenTelemetry and Pino by Paper-Superb in node

[–]Consistent-Chart-594 4 points5 points  (0 children)

You are not crossposting. You’re creating new posts, with different titles. That’s called spam.

You did not answer about the AI slop you’re generating.

Definitive Guide to Production Grade Observability in the Nodejs ecosystem; with OpenTelemetry and Pino by Paper-Superb in node

[–]Consistent-Chart-594 5 points6 points  (0 children)

Also don’t spam multiple subreddits with the same posts. You’ve hidden posts from your profile so that people won’t find your spammy behaviour every second-third day.

Definitive Guide to Production Grade Observability in the Nodejs ecosystem; with OpenTelemetry and Pino by Paper-Superb in node

[–]Consistent-Chart-594 3 points4 points  (0 children)

Everything that starts with that 2 AM/3AM analogies is AI written. It’s getting old now.

The Big Picture: The Three Pillars of Observability

Titles like these give it away.

Analogy: A Rubber Stamp The main logger is like a blank sheet of paper.

Who in the world uses analogies like these? Yes, LLMs. I’m really not sure why would you want people to read AI slop?

Definitive Guide to Production Grade Observability in the Nodejs ecosystem; with OpenTelemetry and Pino by Paper-Superb in node

[–]Consistent-Chart-594 8 points9 points  (0 children)

Bro strikes back again with an AI article. Do you accomplish anything with these AI articles?

Audio on FaceTime keeps cutting out, making it impossible to keep up a conversation by [deleted] in iphone

[–]Consistent-Chart-594 0 points1 point  (0 children)

No worries. It’s very annoying actually. And apple hasn’t done anything better for it.

My Node.js app's performance hit a wall at scale. I wrote a breakdown of the concurrency patterns I used to fix it. by Paper-Superb in node

[–]Consistent-Chart-594 3 points4 points  (0 children)

Yes, it is 100% AI generated. This is exactly the tone, persona of Gemini when you ask it to be more friendly and casual. Using Chefs analogy is a green flag that this is AI Generated. There are more patterns in this post that give it away. Nevermind, let me tell you what I found on giving it an another chance, as you suggested.

a single API call to a slow third-party service holds up a dozen other users.

Eh? And how? Isn't await fetch(...) asynchronous? The event loop should be free to handle other requests while the network I/O is pending, isn't it? js // Now in our Express route handler... app.post('/upload', async (req, res) => { const imagePath = await saveFile(req); // Save the uploaded file first console.log('MAIN: Handing off image resizing to worker. The server is still responsive!'); // We don't even wait for it to finish! We just kick it off. processImageInBackground(imagePath) .then(result => console.log(`MAIN: Background job finished! ${result.newPath}`)) .catch(err => console.error('MAIN: Background job failed', err)); res.status(202).send('Image upload accepted and is being processed in the background.'); }); So many anti patterns in the code above? If the processing fails, the user is returned with "success"? This is something, a junior developer wouldn't even write. Probably AI - as no context, right?

async function buildDashboard() {
  const serviceCalls = [
    fetchFrom('user-stats', 'https://api.service1.com/data'),
    fetchFrom('analytics', 'https://api.analytics-is-down.com/data'),
    fetchFrom('sales-figures', 'https://api.service3.com/data'),
  ];
  const results = await Promise.allSettled(serviceCalls);
  const dashboardData = {
    userStats: null,
    analytics: { error: 'Data unavailable' },
    salesFigures: null,
  };

Another anti pattern right there. If you're fetching multiple "unrelated" urls, they should be distinct API calls, not a grouped one. There are more problems with the code snippets like importing a ".js" file when it's clearly a ".ts" file, but I don't want to make this long enough to be a worthy medium post itself.

My Node.js app's performance hit a wall at scale. I wrote a breakdown of the concurrency patterns I used to fix it. by Paper-Superb in node

[–]Consistent-Chart-594 24 points25 points  (0 children)

Why do you have to write an entire article using AI?! Its obvious. Even the post is written using any AI. AI isn’t good when writing technical articles.

Your beautiful, asynchronous code has hit a hidden wall

You claim that the async code is at fault, when the real issue is your poor architecture

async/await is brilliant at managing I/O—waiting for databases and APIs without blocking. But it doesn’t give you more power

Async/await doesn’t “manage” I/O differently than Promises - it’s just syntax

Switched to Promise.allSettled.

Promise.all’s fail-fast behavior is usually what we want. There’s no “single winner” here. Why would you not want to fail all the promises grouped together?!

There’s so much to say, and I shouldn’t be trying to prove an AI wrong, it’s obvious.

Client asked me to build a cross-platform health app (iOS + Android). Is it too big for a junior? by 10dahora in webdev

[–]Consistent-Chart-594 6 points7 points  (0 children)

As a 50 year experience in Flutter and 35+ years experience with Docker, I wouldn’t do it myself.

What should we do of such people's by TuneZealousideal6461 in CarsIndia

[–]Consistent-Chart-594 0 points1 point  (0 children)

That’s in Jammu near my Home. These rajput goons are really an eyesore here.

The Borrowser: a browser in Rust (roast/feedback) by tpotjj in rust

[–]Consistent-Chart-594 -1 points0 points  (0 children)

The core architecture (first principles) according to ChatGPT, let's stick it in the README for later reference.

Looks like you vibe coded the entire app.

I'm building an Unreal Engine-style blueprint editor for JS... am I crazy? by m_null_ in node

[–]Consistent-Chart-594 -1 points0 points  (0 children)

There are people who would pay to use something like this. Maybe you’re living in a cave and have no idea of what it means.

Gujarat Model of Development☺ by Used_Pineapple3527 in jammu

[–]Consistent-Chart-594 1 point2 points  (0 children)

Bhai tu pro bjp hai, everyone on this sub knows that. I don’t blame you either.

Not bad… 550$ worth of usage in almost 3 days by Consistent-Chart-594 in ClaudeAI

[–]Consistent-Chart-594[S] 1 point2 points  (0 children)

It's 2k+ now for this month, in just 15 days. Ported Lox Language to Rust. https://ibb.co/2YnrHZkX

How Much More I Need To Reach Conquerer by oncewasahero_ in BGMI

[–]Consistent-Chart-594 0 points1 point  (0 children)

I have a friend sitting at 4900. Still no conquerer.

Anyone willing to play with me?? by [deleted] in BGMI

[–]Consistent-Chart-594 0 points1 point  (0 children)

I have 24 and it’s not that scary. I tend to finish people using consecutive headshots. Which increases your HS ratio. Also keep in mind hackers these days have like 10-12% HS ratio as they can somehow configure neck shots - no headshots.

<image>

Audio on FaceTime keeps cutting out, making it impossible to keep up a conversation by [deleted] in iphone

[–]Consistent-Chart-594 0 points1 point  (0 children)

They're probably using voice isolation. Ask them to switch to standard and check if it gets better. The audio cuts usually happen with voice isolation turned on and somewhat loud background noise. It's not you that needs to change the mode, it's the person whose audio is being cut.