@leeerob, do you know if there are any plans to upgrade Vercel Style Guide to ESLint v9 and maintain the package in the long run?
Sizing up whether it’s worth moving away from it if it’s no longer being maintained
Four new international CSS features from the CSS Text Module Level 4 are coming to Chrome. Chrome 118 for 7 languages, 119 for Japanese, and two more features under development for Chinese, Japanese and Korean. Find out more: https://t.co/JEfRA884uU
In case you haven't heard, @nextjs is moving away from patching global fetch in the context of redesigning their cache API.
That is a great decision. I hope that the community feedback has played a role in making it. Please publish a post-mortem on the fetch patching.
I'm all for specialization in software engineering, but client/server isn't a good boundary. As a frontend engineer you need to control the entire user experience, and that requires being empowered to program the frontend server.
The way that Jensen Huang runs Nvidia is wild:
40 direct reports, no 1:1s
- Believes that the flattest org is the most empowering one, and that starts with the top layer
- Does not conduct 1:1s - everything happens in a group setting
- Does not give career advice - "None of my management team is coming to me for career advice - they already made it, they're doing great"
No status reports, instead he "stochastically samples the system"
- Doesn't use status updates because he believes they are too refined by the time they get to him. They are not ground truth anymore.
- Instead, anyone in the company can email him their "top five things" with whatever is top of mind, and he will read it
- Estimates he reads 100 of these everyone morning
Everyone has all the context, all the time
- No meetings with just VPs or just Directors - anyone can join and contribute
- "If you have a strategic direction, why tell just one person?"
- "If there is something I don't like, I just say it publicly"
- "I do a lot of reasoning out loud"
No formal planning cycles
- No 5 year plan, no 1 year plan
- Always re-evaluating based on changing business and market conditions (helpful when AI is developing at the pace that it is)
This org is optimized for (1) attracting amazing people, (2) keeping the team as small as it can be, and (3) allowing information to travel as quickly as possible
@jenewland1999@bunjavascript For me it’s
✋Blockers to adoption
1. Parsing .npmrc
2. Migrating from existing lock files
3. Windows support
✨Wish list
1. Symlinks on Mac (if it ends up being faster in future)
2. Automatic implementation of .gitattributes to parse Bun lock files nicely for PR review
It took @googlecloud FOUR hours to post a critical incident on their status page just now.
And no GCP, the incident did NOT begin at 11:02 PT. It began at 7:30 AM PT because @render engineers got paged well before yours did.
Using "any" in a TypeScript library is occasionally necessary.
Using "any" in an app's TypeScript code is rarely necessary.
So, an "any" in app code is likely caused by one of two things:
1. Inexperience
2. Laziness
Solve #1 via linting, pairing, and code reviews.
Solve #2 via a 1:1 conversation.
disclaimers, nuance, details are *hand wavey* up for debate, but in general the principle holds imho. good software products are developed with very intentional steps and sunlight, not multiple leaps of faith.
something I said today: if you do "sprints", you have roughly 20 chances per year to do course correction as a team. but if you do mainline deploys (with feature flags or whatever), you can do it per commit, which even at 20 commits a week, is ~1000 chances of feedback per year.
General rule: The fewer environments a web app has, the better.
Why? Environments = overhead.
Environments are a sign of manual processes. They exist to support unpredictable, slow, manual checks.
The solution?
1. Automate checks
2. Continuously deploy
@alexdotjs@nextjs Had the same issue with an engineer earlier in the week, where we were using .at() in a API route - was able to resolve by upgrading his Node version from 14 to LTS
Statically typed links are coming to @nextjs:
◆ Autocompletion
◆ Error on invalid routes
◆ Prevents 404 links during build
◆ Dynamic, catch-all, and optional catch-all routes
◆ Works with both `pages` and `app`
◆ No extra configuration needed!
@dan_abramov React as a...
• Library → sprinkle interactivity into any webpage
• Architecture → UI patterns and primitives for frameworks to build with
• Community → well adopted and documented, incrementally adoptable
• Ecosystem → learn once, write everywhere (web, native, 3d, etc)