Heading to Orlando for #InvestOps2026 next week and joining a great panel on how investment ops leaders can cut through the noise and pick tech that actually moves the needle.
Come say hi or grab drinks → luma.com/uwsjm8wjIf
Hello from Toronto 🇨🇦! Totally want to visit and check out the tech scene out there.
dAppwright quietly hit 122 stars. If you're building or testing dApps, take a look.
All resources go to AI now. No need to render the site.
Agreed! Every since I started practicing pair programming back in 2009, haven't looked back. Decisions become to much easier when folks aren't sharing higher fidelity context with each other.
Someone updated the intro to Silicon Valley 🤩
There is always a natural tension between workflow convenience and security measures. I wonder where this will all land with AI pushing so strong for efficiency. 🤔
Turns out my laptop battery is draining in 30-45 minutes because of this... 👀
👏👏👏
Waiting for the first co-op to come in that ask why we use keyboards to code. You can be pretty hands off these days.
My laptop's workload for the past couple of months now that agents are constantly tinkering on things in the background.
I personally went a bit too intense when I first started. Working on 5-10 major features, then suffering the effects of too much context switching.
Ultimately I've pulled back and work on 2 major features, then up to 5 background tasks that are smaller tasks (ie. small refactors, TODOs).
I feel like as the whole industry grapples with what the new normal looks like in terms of #ai tooling, this is something really important to keep track of.
Needs sprinkles 🍩🙌
👆 great though in a world where feature generation is getting easier. Just because you can, doesn’t mean you should.
Congrats! Sounds like you reached that plateau of a super personalized setup. You’ll never want to go back. 👏👏👏
Mastering your toolset means you should be curious about new things 🙌
Grateful to UTMIST and the @developers.google.com team for putting this together and cultivating this community.
Student-led organizations like UTMIST play an important role in creating spaces where the next generation of builders can learn directly from those just a few steps ahead. The curiosity and ambition in that room were a great reminder of why these conversations matter.
What stood out most were the questions from the room: navigating early technical decisions, building with limited resources, and knowing when to pivot. The kinds of questions without easy answers, but that show real thoughtfulness about the path ahead.
Thanks to UTMIST for inviting me to Friday's panel alongside founders Anthony Azrak and Rachel Wong.
Cool temps means faster benchmarks 🙌
key example of someone chasing the same goals in a project and realizing that it requires a ground-up rewrite vs slow adoption. Optimizing your current code in the same language doesn't escape from the logical complexity you'd need to detangle engineering.fb.com/2026/01/27/s...
very interesting premise, I wonder how you would tangibly adopt this to a project at scale. docs.script-lang.org/blog/introdu...
There are a lot of tasks that AI isn't suited for, but there are a ton of tasks where it augments and greatly accelerates workflows.
Any tool can be used in a right and wrong way. I think the world is still figuring this one out.
Agreed. You need to own and secure the entire stack(s) to a solution to really accomplish true E2EE.
Beyond all of this, @metamask.io is looking better than ever. Always like seeing all the easier ways folks can onboard into the ecosystem.
Doing requires an environment flag (PW_CHROMIUM_ATTACH_TO_OTHER = '1') to be set before the context is created. Since dAppwright creates its own context, this is easy for us to do at runtime without introducing a breaking change for burdening users with this context.
