You could argue that the value is in the entertaining filming/acting/story telling etc, but if the videos are about digging holes then I think it's valid to say someone is paying you to dig holes.

I'm guessing it's because the laptops are popular enough that there's a dedicated group of people that make it work [0].

I'm still on X11, dunno what the story is like with Wayland though.

[0] https://asus-linux.org/

It's funny, because you could actually take that story and use it to market AI.

> I once watched a team spend six weeks building a feature based on a Slack message from a sales rep who paraphrased what a prospect maybe said on a call. Six weeks.

Except now with AI it takes one engineer 6 hours, people realize it's the wrong thing and move on. If anything, I would say it helps prove the point that typing faster _does_ help.

Otherwise I don't understand how MCP vs CLI solves anything.

I couldn't find much info here, but I'm guessing they've built tooling to automatically convert model weights to RTL and the reason it's such an old model is that it takes a long time tape a chip out (especially the first one). Would be interesting to know how much is automated and how much is handcrafted.

I think the "next big thing" with AI hardware will be when they switch from "digital" implementations of LLMs to "analogue". We already know that we can lose some bits of precision and still have a "workable" model. If/when folks figure the fine-tuning out, I'm guessing it'll be another order of magnitude improvement.

I'm a bit younger (33) but you'd be surprised how fast it comes back. I hadn't touched x86 assembly for probably 10 years at one point. Then someone asked a question in a modding community for an ancient game and after spending a few hours it mostly came back to me.

I'm sure if you had to reverse engineer some win32 applications, it'd come back quickly.

I would have imagined that the data could be used to get mostly accurate numbers.

Things rarely went to plan, but as soon as any blip occured, there'd be plans to trim scope, crunch more, or push the date with many months of notice.

Then I joined my first web SaaS startup and I think we didn't hit a single deadline in the entire time I worked there. Everyone thought that was fine and normal. Interestingly enough, I'm not convinced that's why we failed, but it was a huge culture shock.

I just try and get LLMs to do it for me because I'm lazy, and they like to use setInterval instead of mutationObservers and if it works, I just live with the inefficiency.

Interesting to hear now that the opinion is the opposite.

To simplify it as much as possible, to make a chip multiple masks are created for different layers. The top layers are metal(scaffolding) and the base layers are silicon(steel). The metal layer masks are much cheaper to make than the base layers. So we add extra unused cells in the base layers and then if there are issues we try to fix them only in the metal layers.

It's not really an art nowadays, since it's been refined so much with tooling and processes. But your analogy is very applicable, I might try to refer to it in the future if I ever need to explain the concept to someone.

No more dealing with dishes, dishwashers, stray items on the table, boiling water etc. The only thing you need to worry about is cleaning your one huel cup which you can do right before you prepare your next shake.

I did it for a few years, eating breakfast + lunch at the office and then Huel for dinner or eating out at restaurant.

It relies on their hosted services/infrastructure. I avoid Plex for that reason. I just host my media with nginx + indexing enabled. Wireguard for creating the tunnel between the server-client and Kodi as the frontend to view the media (you can add an indexed http server as a media source).

Works great, no transcoding like Plex, but that's less of an issue nowadays when hardware accelerated decoders are common for h264 & h265.

If anything, I know people that are getting pissed off about all the AI stuff in windows and are considering switching.