Denis B.

@difficultyang I believe it’s neither. It follows a statistical model of ownership rules which generally produces good results but not always.

Do LLMs truly understand C++ ownership rules or have they simply memorized enough examples to present a simulacra of understanding

@michael_c_law AI can also automate tech debt repayment simply by prompting it to do so.

AI didn't create technical debt. It just automated the process of creating it.

@sivalabs Yes, those layoffs happen regardless of the AI (AI is used as an excuse though). It’s sad because anybody could be affected, and nobody has any certainty at this point.

@denbvk I was talking about the impact of AI where 1000s of employee layoffs irrespective of their performance and AI adaptability. We can say "shit happens", but being a bit empathic doesn't hurt.

I think there is no point in pretending to be a macho man by saying "AI is just another tool". Yes, AI is just another tool but its impact on IT is devastating. - CXOs who have little to no idea is happily firing employees to spend on AI. - There is a new model, a new SDD workflow, a new Agentic IDE to learn which again is going to be called dead in a couple of weeks. - Most of the devs are working in a survival mode worrying about when they may receive the "your role is eliminated" email. Just worrying about it doesn't do any good. But down playing it as "AI is just another tool" is actually making everyone feel "maybe I am not able to handle these hard times". The least we could do is acknowledge that we are going through tough times. These are not normal working conditions. I hope this madness ends soon 🤞

@akramcodez You have no code review? Then I agree with the comment, you are suckers

one of our developers left this right before taking a job somewhere else

@krzyzanowskim If you were a tech lead and handed over this PRD to a team, checked a month later and they’d still be struggling, it’s definitely a skill issue.

"skill issue" - a whole day of writing PRD/specification - half day grilling the PRD/specification - 16h /goal implementing PRD it doesn't work. IT DOESN'T WORK. it doesn't work at all, but also it doesn't work as specified. why broken? "So implementation drift" I'm done with this shit!

@ConsciousRide “Ok bro” and I would start searching for a new job

Tech Lead tells you: “Just store passwords in plain text. Hashing is unnecessary overhead.” What do you say?

@ThePrimeagen Perforce is the worst. It’s has to be an image of “bloatware” article on Wikipedia.

fun fact: my career was svn (tortoise) -> git -> perforce -> git My first year at netflix was a downgrade to perforce... I hated it.

@ConsciousRide We run a marathon, not a sprint. So, slow down, my old fella.

Tech Lead tells you: “Use any everywhere in TypeScript. Types are just slowing you down.” What do you say?

It depends on the scale, really. If you have a couple of backend engineers, it makes no sense to make a DevOps hire: they cost a lot, and one more backend engineer would make more impact. Also, there is no work, really, if you choose a dev platform like Vercel. DevOps is needed when you have custom infra or at least a 15-20 engineer org.

Why do some founders think one backend engineer can do DevOps, security, scaling, and data engineering ?

@MC_chibill @plainionist @dave_alive I see. No other arguments? You’re a smart guy, very smart, lol.

@denbvk @plainionist @dave_alive The fuck does that mean. Please learn English if your going to try and belittle someone that speaks English.

“AI cannot solve truly novel problems.” True or false? 🤔

@romxdev Market standardisation. Like bread sold in supermarkets, which is very bad, but everyone is fine with that because it’s convenient.

How technical interviews became a separate skill that has nothing to do with daily engineering? 🤔

@ryxcommar @buccocapital 100%. Remember when first compilers were released, developers complained that the machine code they produced was total crap. They were not wrong, but we moved on.

@buccocapital I highly doubt it. Not because it won't suck or doesn't already suck, but because everyone is getting dumber and lazier because incremental deliverables are "good enough," and we're starting to forget how to do hard deep work.

Everyone will realize this sucks in 2 years and go back to doing their actual job.

@philthistweet They need to justify the salary of a “Fullstack” engineer.

Why is anyone using JavaScript on the server in the first place?

@birch_js If you need a method, you search using a method name, not local variables, genius.

Yeah good luck searching for "c" in your codebase a month from now

@nxhaaa19 A product people need to + marketing. People will never pay for products they simply “want” the moment they figure out it’s not free.

Builders, You can only pick one: • A product people need • A product people want Which one actually sells?

@BatsouElef You can always refactor it later (later == never)

What’s a coding myth you’ve debunked?

@BatsouElef Unit tests are necessary (they are helpful though when you have a complex stateless domain like math).

@CodeEdison Sanity

Netflix uses JavaScript. Airbnb uses JavaScript. Twitter uses JavaScript. LinkedIn uses JavaScript. Pinterest uses JavaScript. Reddit uses JavaScript. eBay uses JavaScript. Spotify uses JavaScript. Slack uses JavaScript. What’s stopping you from learning JavaScript?

@rambuilds_ CS grads using Claude + Codex

genuine question self-taught devs using Claude + Codex vs CS grads who understand fundamentals who actually wins in the next 3 years ?????