Viewing profile — seldo
seldo
HN member- Joined
- Tue, Jul 29, 2008, 3:22 AM UTC
- HN karma
- 9,195
- Public activity
- 1,214 items
- HN profile
- View on Hacker News ↗
About seldo
Currently: co-founder and Chief Data Officer at npm, Inc.
In my spare time:
http://seldo.com
http://seldo.tumblr.com
http://lgbtq.technology
Previously:
http://awe.sm (co-founder)
http://apps.yahoo.com (mostly the database)
http://widgets.yahoo.com (a fun gig while it lasted)
Contact:
http://twitter.com/seldo
me@seldo.com
Recent public activity
-
comment
Comment #41371471
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 w…
-
comment
Comment #39445761
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.
-
comment
Comment #39444919
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…
-
comment
Comment #38766703
LlamaIndex lets you attach metadata to Nodes which are basically chunks, although that fact is poorly documented! Will fix.
-
comment
Comment #19362438
This really isn't news, folks. It happens every week. I was just grumpy this morning.
-
comment
Comment #17517023
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.npmj…
- comment
-
comment
Comment #16094902
Update: (this is not the post-mortem, this is just more detail) http://blog.npmjs.org/post/169432444640/npm-operational-inci...
-
comment
Comment #16088000
We're working on a full post-mortem now. Until then we don't want to give out misleading/partial information.
-
comment
Comment #16087995
Absofuckinglutely. It's being done as we speak.
-
comment
Comment #16087905
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
-
comment
Comment #14499813
I think you should probably re-examine your priorities in life, but that's just me. You do you.
-
comment
Comment #14427705
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.…
-
comment
Comment #14144278
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 j…
-
comment
Comment #13888678
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, slowl…
- story
-
comment
Comment #13621813
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/15702…
-
comment
Comment #13431916
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 ver…
-
comment
Comment #13431890
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 …
-
comment
Comment #13112440
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 …
-
comment
Comment #13111546
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/makersqua…
-
comment
Comment #12866193
Check out my detailed answer a few comments down: https://news.ycombinator.com/item?id=12861180
-
comment
Comment #12864998
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 over…
-
comment
Comment #12864856
More efficiently handling 404s, which as many have pointed out we were handling quite naïvely.
-
comment
Comment #12864182
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 determ…