Sabitlenmiş Tweet
Writing code was never the bottleneck in software engineering. LLMs made it cheaper to write, not easier to understand, review, or maintain. That’s still the bottleneck. Let’s not pretend it isn’t.
English
Pedro Tavareλ
4.3K posts
Pedro Tavareλ
@ordepdev
I really try to make functions pure, one at a time. Avid reader and @pwlporto organizer.
🇵🇹 🏴 Katılım Mayıs 2017
465 Takip Edilen1K Takipçiler
@sudo_goreng What about companies with real customers that, instead of improving the things customers complain about, are more interested in playing the AI game?
English
Customers want useful features, great UX, superb reliability, and fair pricing; they don't give a fuck if you're tokenmaxxing, they don't even care whether it's a human or a robot writing your code.
English
@ordepdev Too much work, just focus on pointing what is bad and make the author feel bad
English
Rules for engaging code reviews:
> be direct
> reject ceremony
> praise good work
> demand evidence
> question complexity
English
What a time to be a software engineer; I can finally justify the time I spend exploring edge cases and introducing new ways of testing codebases.
English
@thoughtlesslabs Yeah, let's just shut down the internet already, it's over.
English
I would highly, highly recommend you get off the internet forever, find an Amish community and join it, and realize that nothing you have ever let touch the internet was ever yours.
Theo - t3.gg@theo
I would highly, highly recommend you make sure your phone, computer, browser, and important apps are all updated and on the latest versions.
English
Unless I'm actually trying to find something, what's even the point of looking at the git log?
English
Never thought we’d have this exact feeling from a year ago back, but here we are.
English
In corporate lingo, "I took responsibility and delivered fixes" means you're acting as the ultimate safety net, making you a single point of failure.
English
@sudo_goreng You need to see a lot of awful stuff, agree that it's simply awful, and do better. People who don't develop that still have bad taste, even with a lot of experience.
English
Hard disagree. Good taste is a lot more than just experience. There are a ton of experienced engineers with bad taste, and adding more experience won't simply change that.
English
Database internals are such a cool thing to talk about. I gave a talk about Merkle trees in 2019, and I thought I was talking about something so old that no one cared about it. Fast-forward to 2016, and they're still rocking!
Ben Dicken@BenjDicken
Merkle trees are everywhere: - ZFS uses them to detect data corruption - Git uses them to verify repo integrity - Cursor uses them for codebase sync - Bitcoin uses them for transaction verification Talked through how they work on the latest database stream.
English
