Saša Blagojević (@blackcat_dev) header
Saša Blagojević (@blackcat_dev) profile picture

Problem solver, mostly #php #kotlin | wanna be hardware guy | coffee and code addict | amateur buddhist | whiskey connoisseur

Banja Luka, Serb Republic, BiH
Joined March 2014
Photo by Saša Blagojević (@blackcat_dev)Photo by Saša Blagojević (@blackcat_dev)Photo by Saša Blagojević (@blackcat_dev)Photo by Saša Blagojević (@blackcat_dev)Photo by Saša Blagojević (@blackcat_dev)Photo by Saša Blagojević (@blackcat_dev)Photo by Saša Blagojević (@blackcat_dev)Photo by Saša Blagojević (@blackcat_dev)Photo by Saša Blagojević (@blackcat_dev)
Saša Blagojević retweeted
how could they massacre my boy like that 😭 😭
169
160
136
3,522
154,649
Now this is a bit embarassing
被 CVE-2026-128064 气笑了 PHP 的 HTTP/FTP 流包装器在识别 scheme 时不分大小写,但只有在第五个字符是小写 s 时才启用 TLS。于是 HTTPS://、httpS://、FTPS:// 会被当成明文的 HTTP/FTP 发出去。 看到commit记录的那一刻释怀了。
1
107
Hopefully he’ll shut the fuck up now, he got his money
wtf this looks like a horror movie
1
48
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.
39
106
18
911
33,147
Saša Blagojević retweeted
When you are tired, drained and burned out, but you still go to work because you need money
31
4,898
209
32,596
414,646
It's truly astonishing how little fucks Apple gives about developers. It's been 9 days now, no response from Apple Developer Support.
1
54
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.
142
132
20
2,433
79,244
Saša Blagojević retweeted
Docker vs Kubernetes
15
131
9
1,120
73,678
Saša Blagojević retweeted
realizing all the hard shit you accomplished on your resume pre 2026 is just a prompt now
103
541
69
9,133
219,753
Saša Blagojević retweeted
Java4Shell explained. @calif_io
21
451
29
2,817
187,973
Saša Blagojević retweeted
I made a device that lets you scratch Spotify, live.
335
1,467
209
12,536
501,049
Saša Blagojević retweeted
Dunder Mifflin
54
765
38
25,812
2,529,704
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
5
26
1
162
5,418
I can only hope this is rage bait
i deleted all the tests in my repo and banned them in AGENTS.md tests were always just a second, worse copy of your logic. a leaky imitation humans wrote because we couldn't hold every invariant in our head (staying green half the time the real bug happened anyway) opus 5.5+ is good enough at raw logic now to read the intended invariants straight from the codebase maintaining that duplicate copy is just economic waste. plus it makes tasks take way longer while agents burn compute running tests when they almost certainly got it right anyway
55
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.
7
10
2
96
17,135
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.
2
53
4
304
28,532
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.
🚨 BREAKING: A critical Java flaw that reportedly lets hackers hijack servers without a password leaked before its patch. Security firm Calif says it found the bug, dubbed Java4Shell, and will publish details today. Oracle fixes 11 Java flaws today but hasn't tied any to it.
10
44
5
430
63,255
Saša Blagojević retweeted
61
206
17
3,351
68,529
“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.
10
2
2
97
3,157