I break them apart and rebuild them to have slightly different functionality. Most end up being throwaway garbage, but they help me see the concept for myself.
💥 Game changer for Web Development announced at GoogleIO- Modern Web Guidance! It’s expert-vetted skills for web development based on best practices of latest specs and APIs.
It ensures your agent/coding harness doesn’t default to older and out of date patterns to build sites.
Instead, it's a single agent skill that finds and retrieves the best guidance for your use case!
Check out the site here: , and can be installed with npx modern-web-guidance@latest install. Our evals run daily with state-of-the-art models and coding agents!goo.gle/mwg
@philwalton showing the difference between two identically functioning AI coded experiences- one that leveraged this skill, and one that didn’t- and the performance difference of each, and one ships unnecessary JS as well
🎉 Today we have some exciting news! We're merging frameworks! Angular and Wiz!
Keynote addressing the change here:
Some of you might know that we use a few frameworks at Google that power our apps.
Most notably, Angular is most-used, and a framework called Wiz, that powers Search, Workspace, and YouTube... Wiz has some innovative approaches to performance, some concepts like resumability.
As the web calls for richer and richer experiences, but also performance and latency guarantees, we noticed that these frameworks, which historically served different usecases actually have strengths that could be shared.
I was going to read 5 books last year and ended up reading 50! It was a really nice way to carve some time out for myself.
Some of my faves, in no particular order:
Non-fiction:
- Thinking in Systems- great read that encourages broader awareness/thinking
- Kill it with Fire- nice one about managing and upgrading legacy systems
- Range- a good primer in how we can apply concepts cross-functionally, a healthy read IMO
Thrillers:
- These Silent Woods- beautifully written and interesting
- Turn of the Key- kind of classic intrigue with twists
- On a Quiet Street- love me some “you’re not who I think you are”
Most of us who work on heavily used systems at scale saw this one coming, and that they would propose a rewrite as they just have, and we also don’t think this is the answer.
This is why hubris is a very counterproductive quality in engineering.
Why do we all agree on this?
Legacy and heavily used systems have decision accumulation over the years:
some decisions were made because of the technology available at the time, some due to a feature need, some due to dependency management, some were made to make the system more secure or to test it.
When the staff were fired/walked out the door, they took with them all of this context. The existing code can tell you what it does and how, but it can’t tell you why.
@KhaledElAnsari@codegodzilla@PhilipJBasile@dabit3 Things I love about Vue: 1/?
- extremely declarative- your code can be highly organized and legible because of nicely done abstractions
- on that note, computed properties are wonderful and cached based on their dependencies. I wrote here about that: css-tricks.com/methods-comput…
@KhaledElAnsari@codegodzilla@PhilipJBasile@dabit3 - Abstractions break down when you can't get under the hood. Vue provides great APIs so that you can do just this, such as custom directives, watchers, and the like
- The new Composition API allows for a few ways to structure reusable pieces of a larger codebase
@KhaledElAnsari@codegodzilla@PhilipJBasile@dabit3 - Things in the ecosystem like Vuex, Nuxt, Vue Router, and Gridsome offer extremely nice tools with great DX that are a pleasure to work with. The Vue core team also either brings these tools in and/or collaborates with teams so that they're in lockstep
It’s been a year since I was asked to do this. Career ladders aren't enough on their own- it’s essential to discuss how they work in practice, which is why I wrote an article too.
Rubrics without action are pointless because they don’t actually drive clarity for your employees.
The truth is, it’s not important for an engineering manager (EM) to use my process in particular. It is, however, *very important* that they are clear with their employees about expectations and direction.