Hacker Newsnew | past | comments | ask | show | jobs | submit | nevir's commentslogin

> Crazy. Those same enterprises will get sticker shock and leave.

They are already. Both for sticker shock, and also because of developer sentiment beginning to shift towards Codex. …and then in a month or two the winds will shift again, I'm sure.

It's interesting to see how Claude Code got commoditized so quickly.

---

> and they have the vastly better brand

Strong disagree there. Anthropic has pretty successfully branded themselves as the more ethical & 'human' of the two companies. (whether that's the actual reality is irrelevant)


Especially considering this is very very similar to Figma Make


Same here. And just recently made the switch back to VS Code with CC

Also means you don't have to deal with Cursor's busted VS Code plugins due to licensing or forking drift (e.g. Python intellisence, etc)


https://gist.github.com/kieranklaassen/d2b35569be2c7f1412c64...

Looks like claude calls it just "teams" under the covers


Juniors are also more likely to be the MOST proficient/comfortable with AI tooling.

Pair them with a senior so they can learn engineering best practices:

And now you've also just given your senior engineers some extra experience/insights into how to more effectively leverage AI.

It accelerates the org to have juniors (really: a good mix of all experience levels)


> Juniors are also more likely to be the MOST proficient/comfortable with AI tooling.

Why? That seems unlikely to me. That's like saying juniors are likely the most comfortable with jj, zed, or vscode.


I think a big part of the switching cost is the cost of learning a different model's nuances. Having good intuition for what works/doesn't, how to write effective prompts, etc.

Maybe someday future models will all behave similarly given the same prompt, but we're not quite there yet


Same here. Gemini really excels at all the "softer" parts of the development process (which, TBH, feels like most of the work). And Claude kicks ass at the actual code authoring.

It's a really nice workflow.


It's really not that nefarious.

IAD datacenters have forever been the place where Amazon software developers implement services first (well before AWS was a thing).

Multi-AZ support often comes second (more than you think; Amazon is a pragmatic company), and not every service is easy to make TRULY multi-AZ.

And then other services depend on those services, and may also fall into the same trap.

...and so much of the tech/architectural debt gets concentrated into a single region.


Right, like I said: crazy. Anything production with certain other clouds must be multi-AZ. Both reinforced by culture and technical constraints. Sometimes BCDR/contract audits [zones chosen by a third party at random].


It sure is a blast when they decide to cut off (or simulate the loss of) a whole DC just to see what breaks, I bet :)


The disconnect case was simple: breakage was as expected. The island was lost until we drew it on the map again. Things got really interesting when it was a full power-down and back on.

Were the docs/tooling up to date? Tough bet. Much easier to fix BGP or whatever.


It also doesn't help that most companies using AWS aren't remotely close to multi-region support, and that us-east-1 is likely the most populated region.


> but the US is going to ensure that the energy capability is there.

We're doing a pretty shit job of ensuring that today. Capacity is already intensely strained, and the govt seems to be decelerating investment into power capacity growth, if anything


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: