@adityaag Ok I don’t know what you’re focusing on but my 1:1 do not descent into nitpicking. They’re also not for status. Don’t do status there for sure. 1:1 is for coaching, direction, supporting your people. Not micromanagement.
For ten years my one pro of Tesla has been “they are an infrastructure company”. So firing the whole supercharger team is like, the only thing a shareholder should care about imo.
@Starlink I walked out of Home Depot with a brand new kit and it says registered already. But I can’t submit a support ticket without an account. And I can’t get an account without a device! Can someone reach out?
@QuinnyPig The absolute definition of creating a problem, offering a solution to said problem, and then patting yourself on the back for doing so while costing everyone involved a bucket of money.
@rauchg I agree. The scoped applications I’ve built have been easy to keep running and easy to upgrade. The problem has been “this vendor is deprecating a thing” or “some dependencies break on Node N+2”. IMO the trick is really being selective about dependencies.
@bibhashdash@csswizardry But also: nextjs can build static and simply serve CDN when you want it to. Part of the reason I like next _as a dev pattern_ is it can drop those unnecessary “features” when you wish to eschew them.