“This could’ve happened in any language,” says devs of only language where this regularly happens
I'm not even sounding the claxon for this it's just horrible.
Any text > 256chars is a valid root password, holy shit
sshhole.com
8
18
462
14,566
Stefan retweeted
Discord is rebuilding its apps from scratch in Rust!
Discord CTO Stanislav Vishnevskiy confirmed they are ditching Electron and React Native. The new client is fully written in Rust and uses GPUI for rendering.
Early preview show massive performance gains:
- RAM usage dropped 2 GB)
- Single, lightweight process instead of endless Chromium helpers
Discord CTO Stanislav Vishnevskiy confirmed they are ditching Electron and React Native. The new client is fully written in Rust and uses GPUI for rendering.
Early preview show massive performance gains:
- RAM usage dropped 2 GB)
- Single, lightweight process instead of endless Chromium helpers
437
1,776
24,518
3,066,308
C++23, the very last C++ version?
everyone's busy paying attention to the other election, but in the meantime: C++26 was voted down.
as someone who has written C++ for a decade and professionally for 5 years, all i can say is: *good*.
i hope this sorry mess of a language can stagnate and die with some shreds committee stuffing another 15 useless garbage incoherent features badly stolen from for other languages into its rotting corpse while everyone desperately pretends they aren't noticing the fact that no one has willingly started a new C++ codebase since 2018.
4
1
26
4,199
Annoying bug in @googlechrome :
1. Open huge file with lots of text (megabytes)
2. Ctrl+F to text search
3. Enter the first character in what you want to search for
4. Chrome starts highlighting all occurrences of the first character (many thousands)
5. The tab goes unresponsive
1. Open huge file with lots of text (megabytes)
2. Ctrl+F to text search
3. Enter the first character in what you want to search for
4. Chrome starts highlighting all occurrences of the first character (many thousands)
5. The tab goes unresponsive
3
0
29
2,126
Stefan retweeted
When I first told @MParakhin that we were planning to move to a monorepo he said wisely:
Moving to a Monorepo is an idea that every engineer absolutely hates, and that once its there, no engineer would ever want to work at a company that doesn't use one. We will definitely do it.
Moving to a Monorepo is an idea that every engineer absolutely hates, and that once its there, no engineer would ever want to work at a company that doesn't use one. We will definitely do it.
moving to monorepo has been a boon for agents at shopify. definitely requires some thoughtful tooling, and has some downsides that take a bunch of effort to mitigate… but man I wouldn’t go back
143
82
2,123
257,060
Switch to monorepo.
Productivity goes up.
No one is surprised.
Productivity goes up.
No one is surprised.
We moved microservices into a mono repo
The results after the move:
→ Development speed: 5x faster
→ Delivery speed: 3x faster
→ Testing speed: 2x faster
→ Issues: 40% fewer
After we moved 5 microservices into a mono repo, our development speed went up 5x, and AI agents are the reason.
"One repo per service" was the rule for years.
It made sense when only humans wrote the code.
But AI agents work in a different way.
They can only change what they can see.
We had 5 microservices in 5 separate repos.
Most features touched 2-3 services at once.
The agent opened one repo and guessed the rest:
→ Wrong validation
→ Missing event consumers
→ Broken contracts found only in QA
So we moved all 5 services into one repo.
Here's what changed for the agent:
1. **Full system context**
↳ The agent sees every service, contract and event in one place.
↳ It stops guessing what the other service expects.
2. **Cross-service changes in one PR**
↳ One prompt updates the contract, the producer and all consumers.
↳ Before, this was 3 PRs in 3 repos, merged in the right order.
3. **Easy local testing**
↳ The agent starts all services and runs integration tests together.
↳ It finds and fixes bugs before the code reaches QA.
📌 The results after the move:
→ Development speed: 5x faster
→ Delivery speed: 3x faster
→ Testing speed: 2x faster
→ Issues: 40% fewer
Testing got faster because agents automated a lot of checks before QA got the feature.
👉 Important note:
A mono repo isn't a modular monolith.
Keep a separate pipeline for each service.
Only the code for all services stays together.
Each service still builds, ships and scales on its own.
Do you keep your microservices in one repo or many?
--
➕ Follow me to improve your .NET and Architecture Skills
3
1
21
1,507
Stefan retweeted
I have witnessed an atrocity.
Software engineer opens a PR.
Then, future tech kicks in. A code review tool so advanced, it is indistinguishable from magic. It thoroughly assesses the code, better than any human could. And it points out three security findings, all signal no noise. It summarizes the issues and lists actionable remediation steps, easy to take. One of the issues is a hardcoded secret. We’ve never had tools that could conduct reviews this good.
Engineer ignores it, approves PR, merges it.
Hell is other people
Software engineer opens a PR.
Then, future tech kicks in. A code review tool so advanced, it is indistinguishable from magic. It thoroughly assesses the code, better than any human could. And it points out three security findings, all signal no noise. It summarizes the issues and lists actionable remediation steps, easy to take. One of the issues is a hardcoded secret. We’ve never had tools that could conduct reviews this good.
Engineer ignores it, approves PR, merges it.
Hell is other people
72
40
1,289
70,461
Stefan retweeted
So much rhetoric about monorepos being bad for agents primarily from people who have no idea how git works clearly.
`git log -- folder_in_mono_repo`
wow look at that perfect history for only one app in a monorepo.
Anyone who has literally ever tried to ship software quickly across a microservice mesh that inevitably arises from separate repos knows how insane this is to choose.
"What if deploying required sequencing eight separate steps and required writing code in 8 different places both forward and backwards compatible?"
Please. Just use a monorepo and make a monolith, extracting services only when failure characteristics and other boundaries *truly* require it.
`git log -- folder_in_mono_repo`
wow look at that perfect history for only one app in a monorepo.
Anyone who has literally ever tried to ship software quickly across a microservice mesh that inevitably arises from separate repos knows how insane this is to choose.
"What if deploying required sequencing eight separate steps and required writing code in 8 different places both forward and backwards compatible?"
Please. Just use a monorepo and make a monolith, extracting services only when failure characteristics and other boundaries *truly* require it.
who thinks monorepos are good for agents
they absolutely are not, it's a completely wrong pattern for agents, it ruins their ability to navigate history because it removes the project specific container
there's zero benefit from monorepos now that we have agents, only downsides
monorepos were solving a different problem that's no longer even relevant
33
12
337
42,311
Stefan retweeted
Look I do try to live up to my name. But I am having to work pretty hard to look nonchalant as everyone rediscovers trunk based development and “CI” that is not some unnatural shit with feature branches because it’s no longer acceptable to move at a glacial pace.
4
13
120
7,765