Those chips need to be scanned from about 3cm away. If you want a locator tag, it needs to carry enough power to broadcast a signal a useful distance. Still, a microchip is handy if you're not sure if it's your tiger you found.
It's happening as a result of a deliberate animation. The CLS metric relates to initial render. So yes, there is layout shift, but it's not CLS per se.
Whose responsibility is it to establish the prerequisite CICD pipelines, HITL workflows, and Observability infr in order for devs to shepherd changes to prod (and track their impact)? Hint: it's not the developer's.
This was the point of "devops" (the concept, not the job title): the team should be responsible for development and operations, so one isn't prioritised hugely over the other.
Exactly my point.
But then developers: "I just want to go to my Heroku days again!" but then with a sufficient big company there are maaany developers doing things their slightly different way, and then other effects start compounding, and then costs go up because 15 different teams are using 27 different solutions and and and...
But yeah, let's just spin-up a shadow IT VM with Debian like GP said, it's easy!
> But yeah, let's just spin-up a shadow IT VM with Debian like GP said, it's easy!
That’s literally how they sold AWS in the beginning.
Cloud won not because of costs or flexibility but because it allowed teams to provision their own machines from their budget instead of going through all the red tape with their IT departments creating… a bunch of shadow IT VMs!
Everything old is new again, except it works on an accelerated ten year cycle in the IT industry.
Indeed. And it stems from the illusion that what works in solo/small teams/scrappy startup works the same when you are bigger, and that a developer can take over all the corollary work to the actual product development.
And yes, a dev that's able to do that properly (stress on properly) is indeed a signal of a better overall developer but they are a minority and anyway as orgs scale up there is just too much of "side salad" that it becomes a separated dish.
Decent analogy in 2nd sentence BUT the 1st doesn't hold water. TIMTOWTDI, statements about "everyone" or "no one" are highly suspect, and the trend of code-assist -> agentic -> delegated / orchestration is just that (a trend), not a universal law. Even in a full-on maximalist yolo paperclip future, many experts will likely ALWAYS want access to a decent IDE. (Note I'm not saying Cursor is necessarily that IDE, and I'm not commenting on the valuation.)
OK, I'll concede that not everyone keeps getting pulled back to vim, the way I do. I simply don't like VS Code or its forks. I like Zed well enough, but I find I use it very rarely...two or three terminal tabs (Claude code, bash, and vim) is usually all I need, or tmux windows and/or panes if I'm working remotely, with Claude Code opened locally and configured to use tmux to talk to the remote system (using a wrapper I made to automate the setup: https://github.com/swelljoe/tandem).
But, even if you want a big all-in-one editor in an Electron app, it seems obvious VS Code is the way to go (or Zed, if you you aren't committed to using an Electron app). I just can't think of anything Cursor offers that makes it worth spending extra money for it.
It's indisputable (borderline tautological) that specialization trades breadth for depth. This (obviously?) implies the risk of targeting a narrower market, and the upside of being more attractive to that smaller population. It's a typical "quality over quantity" tradeoff.
To say there's no "sliver of truth" in pointing that out (let alone w/ an unwarranted jab about projecting fears) is... strange and maybe hypocritical. TLDR your response came across as emotional and passive-aggressive, and confusing.
> It's indisputable (borderline tautological) that specialization trades breadth for depth
I do not necessarily agree with this as stated. A specialist will have access to many roles within their speciality that are not open to a generalist. The market for generalists without deep expertise is also extremely crowded.
reply