dene

[Virendra Patel @V1rendra_]

A test that only checks the happy path gives you confidence...

until reality happens.

What about:

Empty input?
Invalid input?
Duplicate request?
Missing permission?
Database failure?
Timeout?

Good tests don't just prove that things work.

They help you understand how things fail.

[Citizen Kau @citizen_kau]

We’re living in actual hell.

[James Grugett @jahooma]

DeepSeek V4 Flash is now free for everyone worldwide!

This is a huge upgrade over MiMo 2.5 🔥

Try it now, with our ad-funded coding agent:
https://t.co/uCHw0PuzKO

[Anaya @Anaya_sharma876]

DSA is dead.
Web development is a waste of time.
Spring Boot is dead.
Node.js is dead.
Django is dead.
FastAPI is dead.
AI/ML is dead.
App development is dead.
AI is taking engineering jobs.
AI will replace backend engineers.
AI will replace frontend engineers.

You’ve probably seen 100s of posts like this.

And if you start believing them, your career might actually die.

Nothing is dead.

Tech evolves. Tools change. Engineers adapt.

Stop chasing “what’s dead.”

Start learning.
Start building.
Start shipping.
Start growing.

[dene @fido977]

@Pirat_Nation I read almost all the comments hoping for an answer on how to avoid this. Or learn more about how hackers are doing this. Turns out 95% of comments are just clowning on the browser, while adding zero value to the conversation. People are fucking retards man...

[dene @fido977]

@realutdfan @swapnakpanda And that's the sad part. Why am I the only one who is calling this out? People who are praising this are bot accounts, or they are so far gone they can't even critically think themselves... Either way, they are screwed...

[dene @fido977]

@michael_kove Finally someone said it...
If the code is structured properly, every stage has it's own place,everything is only responsible for one thing and the skill file contains good examples,it has no choice but to follow it and write clean code. (But also tests are mandatory in this case)

[𝗠𝗶𝗰𝗵𝗮𝗲𝗹 𝗞𝗼𝘃𝗲 @michael_kove]

In defense of the "read the code" crowd....

The skill and ability to look at the code produced and understand it IS STILL necessary.

But do you have to read the code?

No. not for most small tasks, if you have everything setup properly.

Where you SHOULD read the code:
- initial architectural design of codebase
- authentication, authorization, guards, middleware
- when setting up models/entities, database queries, migrations

Once you have good foundation in place, a good harness (Claude Code, Codex, Cursor) will follow it. SOTA models will proper reason through existing documentation.

...but that's a thing, most vibecoders don't. They don't understand the fundamental of "good code" and proper architecture.

At one point their codebase gets too convoluted even for AI to properly understand.

So running a periodic AI code audits, refactoring, de-slop and re-structuring is required if you're NOT going to to read the code.

[dene @fido977]

@CantelopePeel @Vlad_GitHub Do you think they care about your problem? Or solving your problem? They only care about is the free luch at the cantine, and survive the day somehow... lol

[dene @fido977]

@Vlad_GitHub @CantelopePeel @Vlad_GitHub you didn't understand a single word, let me help you.
He was just pointing out that you guys don't have enough Unit tests, Feature tests, and Stress tests. In case you have they are a pile of crap.
(Numbers don't lie)
Hope it helps ;)

[Mark Kretschmann @mark_k]

This is a great real-world example of AI-assisted coding: Linus Torvalds just fixed a nasty Linux kernel GPU bug with substantial help from AI.

The bug caused part of Intel Xe GPU compression metadata storage to be incorrectly exposed as usable VRAM, resulting in corrupted page tables and black screens. The eventual fix was basically a one-liner: round_up() → round_down().

Finding it was the hard part: 24 debugging patches and 18 kernel boots. Linus says AI did much of the grunt work, repeatedly adding debug code and analyzing the results as he narrowed down the problem.

The funniest part: the AI repeatedly told him the problem was "impossible and unsolvable" and suggested giving up. Linus kept pushing it until they found the bug.

And then he let the AI write the commit message. 😄

[dene @fido977]

@djkellywaves @jovial_core @apnahive @laravel Probably people who don't know about eloquent connections and scopes

[dene @fido977]

@fjzeit well said

[dene @fido977]

@jovial_core @apnahive I personally really like DTOs. I also use them when two services are communicating with each other. Just to make sure that by the time the data reaches the other service,it's validated and type checked. Service only contains business logic. Everything is responsible for one thing

[dene @fido977]

@apnahive @jovial_core I wouldn't do it. It's job is to validate the request through a DTO, then forward it to the right service. That's why it's called a Controller.

[dene @fido977]

@adrianthedev And that's when the slop generating machine begins because it have to figure out on it's own.

[dene @fido977]

@adrianthedev If you don't want comments write it in the skill file, maybe one more time in a checklist at the end.
If the agents solves a 3 liner with 100 lines it means that the project is badly structured,not enough good examples, not clear what responsible for what.

[dene @fido977]

@apnahive @jovial_core Why would you place a query in a controller? You are contradicting yourself.

[Shayan @ImSh4yy]

I have a small circle, but what I'm seeing is that "vibe-coding" hasn't really amounted to "everyone will be developers" and the gap didn't close as much as it widened.

It's mostly been amplification so far: competent engineering, design, and product people now have leverage, going after bigger ideas, shipping faster, and producing higher quality output.

Everyone else got a faster way to produce slop without any meaningful improvement in the actual work.