ccc

[Mitchell Hashimoto @mitchellh]

The problem with the "if it works who cares what the code looks like" mindset for agentic work is that it assumes the agent has a perfect understanding of "works." Realistically, things are underspecified, agents make bad assumptions, etc.

To be fair, agents are pretty good at unit test coverage. They're pretty bad at designing human experiences (API, CLI flags, etc.), especially cohesive ones for future roadmap plans they may not have visibility into (unless your backlog is perfect and vision fully laid out, which I doubt). They're bad at knowing where performance matters and what type (CPU vs memory tradeoffs). They're bad at where compatibility matters and where it doesn't (and tend to err on the side of preserving it without further guidance). Etc.

Unless you have this ALL specified, you can't possibly claim "it works" without taking a look and thinking about it.

[suikwa @w36nvvi]

你好と谢谢を除いて弟の唯一覚えてる中国語が操你妈なの嫌すぎ

[Homelander @Homelandertc]

My Chinese fans really cooked with this outfit.

[Тsфdiиg @tsoding]

Programming is understanding. If you don't understand what you are doing, you are not programming. You are generating text.

[GORM THE OLD @GORMTHEOLD25]

President Evil (A.I. Video)

[Тsфdiиg @tsoding]

Polish is a very expressive language

[antirez @antirez]

@ericc__ch @mitsuhiko In the most nightmare-ish way.

const re = /foo/g; re.test("foobar"); re.test("foobar");
The first is true the second false. Great design.

[vaxry @vaxryy]

supply chain attacks?

yeah no, I use C++. We don't even have a package manager.

[Bryan Johnson @bryan_johnson]

How to avoid tons of life problems:

go to bed on time.

[Gavinly @Fengyi1811]

烂尾三巨头，大家都认识吗？

[spidey @lochan_twt]

how life feels without chatgpt, claude, cursor

[Klaas @forgebitz]

software engineering in 2026:

- your package manager is compromised
- your cloud provider blocks your account
- github itself is hacked

software is solved

[Mitchell Hashimoto @mitchellh]

Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).

If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!

I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.

Feeling pretty swell about this mentality with all the supply chain attacks happening.

[i2cjak @i2cjak]

Host your own GitHub? That’s impossible. Do you know how hard it is to reach 89% uptime???

[God @TheTweetOfGod]

I dislike most of you.

[GitHub @github]

We are investigating unauthorized access to GitHub’s internal repositories. While we currently have no evidence of impact to customer information stored outside of GitHub’s internal repositories (such as our customers’ enterprises, organizations, and repositories), we are closely monitoring our infrastructure for follow-on activity.

[yetone @yetone]

团队本身就是创业公司的第一个产品，其他的产品都是这个产品的衍生品。