dilyevsky

7 ms·

1.
by dilyevsky 15d ago
Ime it remains the best model for prototyping, sims, visualization etc throwaway scenarios. Just don’t look at the generated code if you just let it rip on the problem for hours ;) but that advice applies to any model unfortunately
2.
by dilyevsky 15d ago
Wouldn’t finding such bugs be considered advantageous? That is unless someone just yoloing the result directly to customer ofc
3.
by dilyevsky 17d ago
Are you aware of the syzkaller and how many bugs it still finds including in networking stack?
4.
by dilyevsky 17d ago
Yes, lots. Early spdy was vulnerable to CRIME attacks and so was TLS1.0 (and to bunch of other attacks). Kaminsky DNS cache poisoning is another one that comes to mind
5.
by dilyevsky 18d ago
Lmao that output genuinely gives me the creeps. What's you opnion vs. SGLang in this regard?
6.
by dilyevsky 18d ago
Even 25 years ago being “too online” - back then it was icq, livejournal, and forums - was already destructive as hell and always led to some pretty cringe outcomes. At least these days some people make a career out of it, back then it was
7.
by dilyevsky 21d ago
Very poor analogy - information security has very few commonalities with ballistics (duh)
8.
by dilyevsky 23d ago
how is the user being held hostage? you can redirect hide my email addresses to any domain
9.
by dilyevsky 26d ago
First of all, web/api being down is not the worst case scenario - i didn't even notice this till late in the day. Secondly, even 1M qps at the edge is tiny amount of compute, what you have here is not a scaling problem it's a
10.
by dilyevsky 26d ago
Yes, just absolutely crazy way of doing load shedding. > why does it take more than seven hours to just raise the minimum on the Autoscaler for HAProxy and let the workload scheduler evict workloads that are less important than, say, the
11.
by dilyevsky 27d ago
What TP is talking about has nothing to do with workload preemption and is more of a variation of loadshedding (e.g overload management in Envoy). When I was part of the team that ran Google's clusters we had very few priority classes
12.
by dilyevsky 28d ago
backoff is only applied to individual pods/containers not across pods. the point is at scale it's easy to get into a situation where it's not possible to recover without (usually manual) full service drain
13.
by dilyevsky 28d ago
1. was already mentioned in sibling - cascade failures 2. you'll have massive number of restarts for various flake reasons and missing things that got papered over with restarts until you hit 1 and everything is broken. another popular
14.
by dilyevsky 29d ago
article description is low on details but i don't think what you and OP are describing can be categorized as overfitting in the statistical sense and more like "reward hacking" by the model. like you said more likely than not
15.
by dilyevsky 29d ago
on older PC bios would perform a memory test - you may remember those - and that's where it would mark a bunch of pages dead/unusuable and it was not uncommon at all.
16.
by dilyevsky 1mo ago
this reminds me how in the late aughts russian government tried to create some national, lib-free wikipedia version so what they did was rip entirety of wikipedia, deleted some articles and then search-replaced "wiki" with their n
17.
by dilyevsky 1mo ago
RS and XOR EC are definitely useful features for an object store that's storing from like tens of petabytes to exabytes worth of data but for a remote block device with a typical size up to a couple dozen terabytes I'm not so sure
18.
by dilyevsky 1mo ago
Slow, buggy and resource hungry. Faster spdk-based engine rewrite has been on the way for like 7 years now
19.
by dilyevsky 1mo ago
why longhorn and not mayastor? longhorn doesn't even have nvmeof that is not experimental
20.
by dilyevsky 1mo ago
For sure! I haven't had the opportunity to burn many tokens on this but given how quickly it was able to fuzz it into crashing i'm sure it can manage.
21.
by dilyevsky 1mo ago
Well it's SPoF for a shard not the whole thing so in practice that makes this considerably better. Secondly, it's not a datapath SPoF so presumably all tailscaled processes would continue running and exchanging traffic no problem
22.
by dilyevsky 1mo ago
With opus 4.7-ish to fable 5, immediately after release - before they locked it down, it was shockingly easy to find crash bugs in a lot of very heavily used DBs and other software.
23.
by dilyevsky 1mo ago
Because then you’d have to pay taxes
24.
by dilyevsky 1mo ago
Agree on the equity, afaik it’s due to how eager European countries are to tax illiquid shares on exercise instead of on sale like in US. Even without the equity part i think most engineers should be thankful for not having to hit their kpi
25.
by dilyevsky 1mo ago
First of all it's not just SV - all of US sales is like this. Second, if you're talking about Europe - base/variable comps split may not be 50/50 but it's often the same OTE structure with some modifications due to
26.
by dilyevsky 1mo ago
if i'm working for a company i sure hope they're sending their sales reps to a tropical paradise, and if they don't, i hope i don't own any equity.
27.
by dilyevsky 1mo ago
Clearly ai written comment
28.
by dilyevsky 1mo ago
That was exactly my process on this article and the rest. Often i actually scrap claude/chatgpt edit because it sounds so fake and rewrite it myself. And like i said elsewhere - diagrams are pure ai because i don’t personally care for
29.
by dilyevsky 1mo ago
the soak tub in the kitchen was nice
30.
by dilyevsky 1mo ago
I actually do get public cloud as well as running your own racks. There is room for both. Your startup is growing 100% every quarter but you're not sure if you have real PMF yet? Yeah probably stick with cloud. Zombiecorn growing 10-20

More ›