2,476 karma · joined February 16, 2018
and this is why they bought Peter. i’m betting he will come to regret it.
not really? doesn't git checkout only retrieve the current branch? the checkpoint data is in another branch.
we can presume that the tooling for this doesn't expect you to manage the checkpoint branch directly. each checkpoint object is associated with a commit sha (in your working branch, master or whatever). the tooling presumably would just make sure you have the checkpoints for the nearby (in history) commit sha's, and system prompt for the agent will help it do its thing.
i mean all that is trivial. not worth a $60MM investment.
i suspect what is really going on is that the context makes it back to the origin server. this allows _cloud_ agents, independent of your local claude session, to pick up the context. or for developer-to-developer handoff with full context. or to pick up context from a feature branch (as you switch across branches rapidly) later, easily. yes? you'll have to excuse me, i'm not well informed on how LLM coding agents actually work in that way (where the context is kept, how easy it is to pick it back up again). this is just a bit of opining based on why this is worth 20% of $300MM.
if i look at https://chunkhound.github.io it makes me think entire is a version of that. they'll add an MCP server and you won't have to think about it.
finally, because there is a commit sha association for each checkpoint, i would be worried that history rewrites or force pushes MUST use the tooling otherwise you'd end up screwing up the historical context badly.
That's not an upside in that it's unique to LLM vs human written code. When writing it yourself, you also need to make it crystal clear. You do that in the language of implementation.
I mean, that's not quite it. By that logic, had memory been defined in decimal from the start (happenstance), we'd have 4000 byte pages.
Now ethernet is interesting ... the data rates are defined in decimal, but almost everything else about it is octets! Starting with the preamble. But the payload is up to an annoying 1500 (decimal) octets. The _minimum_ frame length is defined for CSMA/CD to work, but the max could have been anything.
Similar signal will be there for any email provider or server-side filter that downloads the content for malware inspection.
Pixel trackers are nearly never implemented in-house, because it's basically impossible for you to do your own email. So the tracker is a function of the batteries-included sending email provider. Those guys do that for a living, so they are sophisticated, and filter on the provider download of images.
umm, anti-glare/matte used to be the norm for LCD. Around 2005-2006 that changed. As laptops became more of a consumer product, and DVD watching was an important usage, the glossy screens became the norm.
https://forum.thinkpads.com/viewtopic.php?t=26396
So, I would call it a massive step backwards! The 2006 MBP had an optional glossy screen, and the 2008 was the first one with default glossy. Around 2012 Apple dropped the matte option altogether.
rather inelegant, similar to an autodialer for safes.
i was hoping to see something that worked like a human lockpicker!
But a country-sized network with the purpose of evading a blackout would likely have to be full mesh. A network organized into a hierarchy (aggregated routing tables) requires some coordination that could quickly be identified and squashed.
The size of such a mesh is limited by scaling factors, so this couldn't span a nation. Let's say you could do that though. The network would be completely choked up with traffic to the point of unusability.
I think starlink, satphone, maybe packet radio on small scale are the most realistic options.
the tweet starts off pretty strong, which I didn't care for but I understand. this phrase however feels wrong. i guess i don't understand Italy, but isn't this like saying the SEC or FCC is quasi-judicial?
> In other words, Italy insists a shadowy, European media cabal should be able to dictate what is and is not allowed online.
ah, unlike when CF themselves decides unilaterally, not even as part of a cabal, what should and should not be allowed online. got it.
it’s true, you can’t. however the VCs and the employees don’t own the same shares. even the VCs in different rounds don’t own the same shares.
where TFA analysis falls short is assuming employees have to be paid out at all. since the execs are moving over, there’s definitely some equity being traded in this “non-exclusive licensing deal” but it doesn’t have to involve common stock at all.
however this breaks backward compatibility, as you noted. in the golden age of unix it was critical to maintain backward compatibility so that local tooling didn't magically break.
HP-UX seems to have an env var UNIX95 that affects XPG4 compliance in operation/output. Solaris always had a /usr/xpg[46] path (and /usr/ucb). GNU tools have POSIXLY_CORRECT. and so on.
I never liked using any of those because then you're on some other system, or in a break glass situation, and none of the tooling works as you expect. In the today world of a near monoculture of linux, it's fine I guess. And there's no reason today that complex commands like `ss` shouldn't be controllable via env var.
love your blog, thanks for the link.
ransomware would beg to differ.
it's really, really easy to say that applicants don't meet the requirements, since hiring is sooo subjective. "none of the applicants had 8 years and 2 months experience in this company working on this team, so they won't be able to perform the duties".
or, if they do have a flood of qualified applicants (the point of the website), they can simply not go forward with PERM at this time for their selected candidate. PERM roles aren't new jobs in the sense that the employer is "down" one employee if they don't fill it. PERM roles are simply a status change for an existing employee.
I'm not just being imaginative for the sake of argument. One of my parents does exactly this.
I do thank you for not saying "begs the question"! ;)
FWIW I have never been asked this question or similar, but since it's so famous I do have my own answer at the ready, which is just slightly more complex than the naive solution, but still well within the realm of production-worthy (maintainable, testable, readable) code. We don't really ever see any discussion of such because of course it isn't "interesting".
Yes, very much yes.