Chris Thoburn

Only if by drama you mean people that haven’t watched a game of basketball. Good riddance.

Has he Played ok against a couple of bad teams lately? Sure, but he’s getting extra minutes with starters sidelined and still only putting up 3rd option numbers as the top scorer on the floor, and is now predictably “injured” again. The guy misses games if he passes gas.

Honestly getting annoyed with how diplomatically polite Kerr and Dunleavy are about Kuminga.

He was shit, and a liability. He’s still shit and a liability. Yeah, he is good when he does everything he’s supposed to: the problem is he never ever does everything he’s supposed to.

Bay Area is either on the third false spring or it’s actually summer already. Won’t know for a month 😂

the reason I find this interesting is I don't feel like there would have been a ton of examples of this in its training set - as its decidedly not how humans approach problems on average.

one of the things I find the most interesting about LLM code output for complex things like codemod work is the ease with which it uses recursion to simplify/achieve complex tasks in a small number of lines. Stuff we know we should do but have a hard time reasoning through and thus don't.

More sites need to offer a manual uninstall or refresh button. Also it’s crazy how hard browsers make it to find and remove them

The answer is easily melon

Games like today are why I continue to believe the warriors are closer to a championship than not. Before the Butler injury I even felt like it was maybe this year. They have the pieces.

Next year with the cap space they have is gonna get interesting.

Some folks worry what this does to their career. Personally I find it’s letting me get back to being more creative and more effective and do a lot of the things that originally turned me into an engineer in the first place but for which I never had enough time to do.

And importantly - validation of ideas matters a lot less when it’s the person with the need producing the feature. A whole industry exists because folks couldn’t solve their own problems and needed others to figure out how to understand their needs - and that just matters less now.

Except it was.

The cost of producing bespoke software was too high even when the needs were well understood and organizational overhead was low. Even higher when needs needed to be translated. Multiple layers of human and time costs have vanished here.

This is really similar to another point I’d make about LLM assisted coding’s effects on velocity: I’m watching tons of non-technical folks build software solutions for their small business needs.

I think small businesses ultimate benefit the most from AI coding. “The code was not the bottleneck”

Companies still spending tons of time deciding what to try instead of trying lots of things quickly and iterating on what’s working will fail

Historically, spending a ton of time on research and planning was beneficial because the cost of building the wrong thing was so high. That cost is no longer high - the calculus has changed.

The enormous, depressing, overwhelming, unconquerable human costs of convincing folks what to try vanish when it becomes easy to just do or show. Code velocity changes organizational velocity significantly.

I disagree with this take.

I watch product teams spend tons of time trying to validate ideas that turn out wrong. Or products fail because the cost of prototyping ideas is so high that most ideas are left untested.

Product velocity absolutely can be the hardest part of it all… and that’s changing

Got a catalogue? I’m curious mostly because I’ve never hit one of these and so now I want to know what features I’m not using but should be 🫣

Because we only need a few very tiny libraries and/or spec’d browser built-ins to make reactivity the default if the mechanism is standard. Standardized a signals end frameworks and ecosystem lock-in.

As for knowing explicitly what is a signal - it’s really not important at all.

Before I go too much further: computed is not a signal imo though most don’t differentiate that, I’m referring to true roots only. Apps can make liberal use of primitives like computed that layer over signals - apps don’t need to define signals.

I’ve been prototyping this way a lot recently and it makes Claude a super power: I wrote some additional utils to make the 3 sources of state that WarpDrive doesn’t handle yet also reactive. Apps built with it can be authored with zero signals of their own.

The same way devs should never need to think about what is/isn’t a signal or manually mark things as signals, LLMs won’t need to know either. There’s no training to be done - just use the language.

If signals are standardized and the 4 basic roots of state in web apps are reactive, nothing else has to be. All code other code is naturally reactive and functionally a derivation of those reactive roots.

At the same time though: I’m not arguing the current spec needs to just be declared standard and we move on: more that we need to be moving with urgency. The state of LLM coding would be massively different right now if signals were standard, as regular JS just works and every library interops.

I still don’t see anything here that can’t be layered by a framework above a basic signal mechanism. But also this feels like overuse of signals.

literally everything can be implemented with it, fairly easily. Not sure what features you want to layer on top - but most the disagreements are literally just about that.

We should just be standardizing the mechanism not the sugar. And tbh the current proposal is too much sugar - needs less.

with the advances that have been made in AI authored code - I'm even more convinced that we need signals standardization yesterday.

Hey @nbcbayarea.com can we remove the silly video game circles under the player with the ball in this Warriors/Celtics game?

Components aren’t a refactoring boundary though