seldo

8 ms·

1.
by seldo 2y ago
For agentic use cases, where you might need several round-trips to the LLM to reflect on a query, improve a result, etc., getting fast inference means you can do more round-trips while still responding in reasonable time. So basically any L
2.
by seldo 3y ago
We are planning to move our blog off of Medium (we've been busy!), but this post is public so you can actually just click through the nag screen if you see one.
3.
by seldo 3y ago
Retrieval-Augmented Generation, where you ask an LLM to answer a question by giving it some context information that you have retrieved from your own data rather than just the data it was trained on.
4.
by seldo 3y ago
LlamaIndex lets you attach metadata to Nodes which are basically chunks, although that fact is poorly documented! Will fix.
5.
by seldo 8y ago
This really isn't news, folks. It happens every week. I was just grumpy this morning.
6.
by seldo 8y ago
Further clarifying: npm will revoke all tokens issued before 2018-07-12 12:30 UTC. If you rolled your tokens after that time you will not need to re-issue them. https://status.npmjs.org/incidents/dn7c1fgrr7ng
7.
by seldo 9y ago
Update: (this is not the post-mortem, this is just more detail) http://blog.npmjs.org/post/169432444640/npm-operational-inci...
8.
by seldo 9y ago
We're working on a full post-mortem now. Until then we don't want to give out misleading/partial information.
9.
by seldo 9y ago
Absofuckinglutely. It's being done as we speak.
10.
by seldo 9y ago
Hi folks, npm COO here. This was an operational issue that we worked to correct. All packages are now restored: https://status.npmjs.org/incidents/41zfb8qpvrdj
11.
by seldo 9y ago
I think you should probably re-examine your priorities in life, but that's just me. You do you.
12.
by seldo 9y ago
Yarn does not run a mirror of the registry. registry.yarnpkg.com is a pass-through domain to the npm registry. It allows them to collect stats about yarn usage but is not a mirror.
13.
by seldo 9y ago
L1 visas are easier for the company to get, because there is no cap on the number issued. The employee on an L1 is just as qualified as an H1, but less free -- they cannot switch jobs, and if they get fired they must leave the country wit
14.
by seldo 10y ago
I'm not sure where you've interviewed but everywhere I've worked we always ask what you've done, and at my current company we have no whiteboard interviews. Tech is learning, slowly, how to give proper interviews.
15.
by seldo 10y ago
Funny you should mention a managed relational database service; Instapaper uses one of those and had more than 12 hours of downtime this week: http://blog.instapaper.com/post/157027537441 No database solution is totall
16.
by seldo 10y ago
A few points: as @chrisfosterelli noted, if a package is being squatted we'll give it to you, no problem. As for why we don't automatically/proactively handle squatting: it's a very thorny problem. Whatever minimum stand
17.
by seldo 10y ago
How would you like us to better publicize it? I agree it's a few clicks away from the home page, but as others have noted not a lot of people need to enter this process, so giving it prominence on e.g. every package page would be overk
18.
by seldo 10y ago
How does one contact the moderators to let them know that a comment is racist/sexist/whatever? I don't see any "flag" UI at the comment level, and I don't know who the mods are by name.
19.
by seldo 10y ago
Reminds me of this great presentation: http://lunar.lostgarden.com/Rules%20of%20Productivity.pdf Especially this graph of productivity over time: https://slides.com/seldo/makersquare-6-stuff-everybody-k
20.
by seldo 10y ago
Check out my detailed answer a few comments down: https://news.ycombinator.com/item?id=12861180
21.
by seldo 10y ago
99.9% of our requests are handled by the CDN. The CDN doesn't cache 404s, so 404s are handled by our origin servers, which are much fewer in number and therefore quite easy to overwhelm. You're right that our handling of 404s was
22.
by seldo 10y ago
More efficiently handling 404s, which as many have pointed out we were handling quite naïvely.
23.
by seldo 10y ago
I'm sorry my response looked like I was blaming them, that wasn't my intention. Like I said, it was an honest mistake: these things happen, and they handled it well. Once we determined 404s were the problem we put mitigation in pl
24.
by seldo 10y ago
I was a bit vague :-) India's about 10% of total requests on any given day. VSCode was 10% of requests for a couple of hours.
25.
by seldo 10y ago
A VSCode person can (and probably will) answer in more detail, but at heart it's simple: if you want to add type-checking goodness to a library that isn't itself written in TypeScript, you can create a thing called a declaration f
26.
by seldo 10y ago
CDNs don't usually cache 404s. VSCode was looking for @types packages for any and every npm package its users were using. Packages that had a type description caused no issue, but most packages don't, so we had a > 1000% spike
27.
by seldo 10y ago
I'd just like to say on behalf of npm that Microsoft's handling of this incident was A+. As soon as we alerted them to the issue they were all hands on deck and did a rollback. We've been really pleased that Microsoft chose t
28.
Web app development and web site development are no longer the same thing(seldo.com)
2 points by seldo 10y ago|0 comments
29.
by seldo 10y ago
You make a good point. In practice, we've not found a reliable way to weed out the false positives that result (I would not characterize it as an "explosion", but there are definitely some). However, we've stuck with thi
30.
by seldo 10y ago
Doing what you're doing will probably work, in that you'll get decent candidates. But this approach only works for one kind of good developer -- the kind who can survive this kind of interview. Silicon Valley's diversity prob

More ›