128GB of the most in demand consumer chip when all the manufacturers are switching to HBM manufacturing because the margins are far better there will do that to you. It sucks.
They'll make it a requirement for building codes to have it on file when you installed them. Just like septic systems all being transitioned to aerobic systems. Then it'll be on file in the county and they'll tax you on the capacity.
CAFE isn't all they have to deal with. NTSB has stricter safety requirements now and we will probably not have small vehicles again. I just want a damn Hilux.
The fun part about that `grill-me` command is that when the questions are over, I've found that I can go right into implementation without needing to dump a PRD or some sort of broken up plan. Now this is obviously completely predicated on what you are asking it to grill you on. But for tasks that are semi complicated, it's fantastic.
I went from Alacritty to Ghostty for ligatures and some other small goodies. I could probably get those same goodies with Kitty, but I didn't want to try nor have the desire to try. I may go back to Alacritty if I grow tired of Ghostty.
And even if it _was_ related to AI, they would not admit it. First course of action is to blame user/programmer error and then QA process error. You shall not blame the golden calf. I am half serious and half not. But I do recommend reading the book "The Field Guide to Understanding 'Human Error'" in conjunction with my hyperbole.
Schools have always lagged and can barely keep up. Books once printed on any tech topic is almost always outdated by the time it reaches students. Anecdotally, I went through high school being told over and over that I wouldn't always have a calculator in my pocket. I think the messaging they conveyed was done poorly, and should have said "you need to understand the fundamentals and why the calculator gave you the answer".
The sweet spot for being just fast enough to not irritate you is 10tok/s. Still slow but faster than you can sustain at typing and thinking. Just interesting to observe.
> Couldn't you also just have an LLM review the PR and quickly fix any issues? Or even have it convert the PR into a list of specs, and then reimplement from there as you see fit?
Sometimes I'm not a fan of the change in its entirety and want to do something different but along the same lines. It would be faster for me to point the agent at the PR and tell it "Implement these changes but with these alterations..." and iterate with it myself. I find the back and forth in pull requests to be overly tiresome.