Saša Blagojević retweeted
🚨 A bunch of people who bought Anthropic to flip it already have a paper loss of 13% — in less than an hour. 🚨
Live by the sword, die by the sword.
Saša Blagojević retweeted
Saddest thing about LLMs in tech is that nobody cares about actually removing layers of unnecessary complexity anymore, since models happily absorb it until their context window explodes.
People will just keep piling crap on top of existing crap hoping to outcompute the entropy.
Saša Blagojević retweeted
“I don’t believe in rewrites into any language. I believe in constant and never-ending polishing, iterating and refactoring.”
daniel.haxx.se/blog/2026/11/…
Saša Blagojević retweeted
realizing all the hard shit you accomplished on your resume pre 2026 is just a prompt now
Saša Blagojević retweeted
Today, we published the biggest piece of content on the Kotlin YouTube channel yet: A four hour long course on coroutines. I hope you'll find it useful! 🥳
youtu.be/2kkvXR-J45E
Saša Blagojević retweeted
Couldn't agree more. Right now, you can spin 10 or a 100 AI agents and have them run their own "software factory" with you just looking at the results (even doing that very passingly) and getting the feeling that you're a 100x engineer.
In reality, you're going to own all the code (including the slop) that the AI produces. You face a speed-control tradeoff: Move faster with more AI agents and lose control or move a bit slower and have full visibility/control over what the agent does (btw, this doesn't mean that you're writing the code yourself, just that you're fully aware of the decisions the AI makes).
There is currently a lot of pressure on engineers to ship more and more with AI, which is why a lot of people are just letting the AI agents do whatever they want. I think that over time, there will be a regression to the mean, where the industry slows down a bit as bugs/issues catch up with the devs and they can't explain them or take ownership.
people are all trying to figure out what i mean by this
Its quite simple:
There is a bunch of whatever work that goes on (hey move this button here), yeah its easy to make a bunch of small changes
But this is a problem, you never take a step back and deeply think about what you are building and thus we get slop constantly. You don't take the time and figure out what is the best path forward, you just fix the next thing in front of you while having 10 of them going at once.
Take a moment, think about what you are doing.
Saša Blagojević retweeted
Looks like Java4Shell will be a more limited affair, sourcing details from the @datadoghq writeup by @Frichette_n and Sebastian Obregoso:
1. Requires x86-64 CPU with AVX-512 VBMI. From what I can gather, this is most newer generation cloud instances that aren’t ARM. You can run `grep -om1 -E 'avx512[_]?vbmi' /proc/cpuinfo` on the host to see if you’re potentially impacted.
2. It’s far easier to try and abuse this to cause a DoS than a full RCE. RCE must be targeted and is not generic.
3. Patches are out and two mitigations exist: starting the JVM with option `-XX:-UseBASE64Intrinsics` or a more breaking change `-XX:UseAVX=2` which reduces performance and will break ARM64 JVMs if it’s in a shared config.
4. The full exposure is really JDK 17.0.6+ on AVX-512 VBMI x86 hosts, with code that Base64-decodes untrusted input through the JDK’s basic or URL decoders.
I’d treat this as a high-priority DoS with a targeted RCE possibility, not a Log4Shell.
Saša Blagojević retweeted
This one looks legitimate. It’s x86 specific and is a consequence of a bug in the JIT.
Long story short, the java.util.Base64 decoder has an AVX-512 (SIMD) routine swapped in at runtime to speed up the decoding. Except there’s a bug in the routine which could lead to memory corruption.
The primary concern here is that Base64 is used in a number of application servers for HTTP basic authentication, Kerberos, SAML, WebSockets, etc. You might not even use these features, but if the server decodes the string before rejecting it, it may be too late.
Until a fix is in place the workaround is to add the flag -XX:-UseBASE64Intrinsics to your application startup to disable the AVX-512 routine.
Saša Blagojević retweeted
“Employers want someone with a strong grasp of AI”
Speak for yourself. I’ll take, “understands CompSci fundamentals and knows how to read/write software” over “I turn the crank on the slopcannon” 7 days a week and on Sunday.
It’s a false dichotomy, of course. Anyone who understands software engineering deeply almost certainly has gotten up to speed on LLM technology.
Things that are wrong with this picture:
> No one cares about your computer science degree.
> No one cares about the tech stack you're familiar with.
> Only *some* AI/LLM development tucked in there at the end as if it's an afterthought? 🚩
Employers want people who have a strong grasp of AI and how to use it.
Saša Blagojević retweeted
most developers would do much better just using one AI chat a time and actually think about what they are doing
too many of y'all larp
Saša Blagojević retweeted
We have an epidemic of students turning in essays they didn’t write about books they haven’t read, and if teachers are now using AI to grade assignments en masse we may as well shut down the schools because no one here is teaching and no one is learning.
The college admissions essay is in a very weird place. It's impossible to say just how many of them are now written by AI, but at this point, experts agree that it's a lot of them. And while colleges generally frown upon that practice, they're using AI to evaluate the essays, too. cnn.com/2026/11/15/tech/ai-s…
Saša Blagojević retweeted
same way cars were invented. they left a horse running over the weekend.




































