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".
Zen 5 has 8.3 billion transistors in a chiplet, Zen 1 had 4.8 billion per chiplet. If we add on some more to compensate for the separate I/O die then we're looking at basically one doubling over several generations and 7 years.
There's still significant gains to be had, but the exponential growth is really petering out.
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.
Does she think this really does the complexity of each case justice though? I doubt you can compress an anamnesis into a two-liner without losing essential data.
> Does she think this really does the complexity of each case justice though?
Do you believe that -prior to the 2020-ish mass evacuation of doctors from the profession- the typical specialist would misrepresent the facts of a case when asking for a cross-check?
Related: Have you ever worked as "the guys who actually work on the thing"-level tech support for a nontrivial Enterprise Software Product (or System)? If you have, did you never send a quick message to a knowledgeable coworker to double-check something that you were pretty sure was correct, but weren't 100% certain about?
An enterprise product is not comparable with the human body at all. A single cell contains hundreds of times more information/entropy in its state than an operating system.
> An enterprise product is not comparable with the human body at all.
Incorrect! Enterprise products are often sprawling projects that
* are poorly designed
* are inadequately (and often incorrectly) documented
* have confusing and/or inadequate diagnostic facilities
* are far, far too large for any one person to completely understand
* have one or components that no one adequately understands
* are pretty much constantly in a state of partial failure
* usually don't require an understanding of -say- the QM principles that govern the behavior of the medium that embodies system in order to perform system diagnostics and repair
Given that you dodged them, I'll assume that your answer to my first question to you is "Yes", and to my second is "No".
> 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.
reply