Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
robshippr
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
by
robshippr
4mo ago
[flagged]
2.
▲
Brute-Force Retrieval Holds Through 5k Memories. Then It Doesn't
(strake.dev)
1 points
by
robshippr
4mo ago
|
2 comments
3.
▲
by
robshippr
4mo ago
Best of luck to you, I hope you find something soon.
4.
▲
GPU probably isn't helping your retrieval system
(strake.dev)
3 points
by
robshippr
4mo ago
|
0 comments
5.
▲
by
robshippr
6mo ago
This is especially true for dev tools. Engineers already have 20 browser tabs open with dashboards, CI/CD, docs, and logs. The last thing anyone wants is another Electron app eating RAM in the background. The best tools meet you where
6.
▲
by
robshippr
6mo ago
The "too risky to deploy" problem is really a visibility problem. When you can't quickly see what's actually changing in a deploy, fear becomes the default. The teams that break out of this aren't the ones who stop
7.
▲
by
robshippr
6mo ago
The interesting detail from the GitHub thread is shaanmajid's observation that every legitimate v1 release had OIDC provenance attestations and the malicious one didn't, but nobody checks. Even simpler, if you're diffing your
8.
▲
by
robshippr
6mo ago
The interesting detail from this thread is that every legitimate v1 release had OIDC provenance attestations and the malicious one didn't, but nobody checks. Even simpler, if you're diffing your lockfile between deploys, a brand n
9.
▲
by
robshippr
6mo ago
Second major supply chain compromise in a week after the axios npm attack. 40 minutes and 500k machines affected. SOC2 won't catch this. The real question is whether your CI pipeline would have flagged a dependency change that happened
10.
▲
by
robshippr
6mo ago
Three hours between the malicious publish and npm pulling the versions. If your CI ran an install during that window, this went straight to prod. Most teams I've worked with still have loose version ranges somewhere in their dependency
11.
▲
by
robshippr
6mo ago
The real issue with LocalStack was always drift. Tests pass locally, then something breaks in staging because the S3 response format is slightly different or DynamoDB throttling doesn't match. After getting burned enough times we just
12.
▲
by
robshippr
6mo ago
This at least makes me feel like I am not going crazy when I say "Github used to be much more reliable before Microsoft bought them"
13.
▲
by
robshippr
8mo ago
I am very good at writing down notes, especially in meetings... I am not so great at going back to those notes. I also have an issue with jumping around to different notebooks.
14.
▲
by
robshippr
8mo ago
I miss his writing, I haven't seen a post by him in a while. His blog and Coding Horror are what I used to read all the time in my undergrad.
15.
▲
by
robshippr
8mo ago
Don't give them any ideas haha
16.
▲
by
robshippr
8mo ago
This is so cool. I've become more interested in aerodynamics since I've started watching F1 and reading Adrian Newey's book. This is such a great post, especially the diagrams in the velocity section.
17.
▲
by
robshippr
8mo ago
Incredible job here. Really took a lot of work to get this done. Keep it up.