@jayphelpsi
iAccount based inUnited States!
About this account
- Account based in
- United States
- Connected via
- United States App Store
! X says this location may be affected by a proxy or VPN.
Account-level information from X, not a live location or the device used for a specific post.
Server-Driven UI, compilers, language design, and reactive programming. Shared Client Foundations at @Netflix
Austin, Texas
Joined April 2009
- Tweets32.9K
- Following853
- Followers25K
- Likes7.1K
Still early but, as my daily driver, thus far it feels like Grok 4.7 is a step backwards from 4.6 and 4.6 was a step backwards from 4.5.
So strange. Hoping I'm wrong. I've been using 4.6 enough now that, at least for my use cases, I'm confident it was vs. 4.5
4.7, FOR ME MIND YOU, seems to be skipping very obvious things. Taking shortcuts and half-assing things. It reminds me of why I needed Plan Mode. Which I know flies in the face of what they've *said*, but thus far my experience.
Pure speculation but maybe their drive to try and beat the other top models led to it not being as great of a daily driver; maybe it's better on paper at some things but in practice not good enough to use as the daily driver. I expect my daily driver to do tasks that aren't particularly hard, but aren't just trivial either. 4.5 seems like it's better at that, thus far. Will give 4.7 another couple weeks then switch back to 4.5 if that pattern holds. I was *very* happy with 4.5 as a daily driver. Again, emphasizing this is all highly unscientific. It could just be coincidence.
For some reason I thought @ThePrimeagen was replying to @TejasKumar_ here
Productivity. If you use AI *heavily* do you feel like you are doing:
(poll character limits make wording weird)
74%more in same amount time
4%less in same amount time
7%(mostly) unchanged
15%see results
54 votes • Final resultsMe asking AI: "How hard would this be to migrate?"
AI: "Massive, multi-quarter initiative."
*do migration using AI in a day*
Me trying to remember what coding was like before AI, and I've been doing this for well over 20 years
Kidding (somewhat) but seriously: if you're not contributing PRs across the stack, to repos you don't own, you're doing it wrong. I don't mean blindly vibe coding changes. I'm saying: it takes less time for you to have AI figure out where the bug or missing gap is and fix it, you review the changes, have it then submit the PR, than it does for you to waste time trying to Slack them and ask for someone to eventually find the issue and fix it and land it: 1 day vs weeks, if that. Don't let org boundaries hold you back anymore.
If anyone non-Netflix streaming service UIEs follow me: the biggest feature request I have is to stop having back button leave your player if I just finished scrubbing. I'm trying to dismiss the player controls, not leave the player.
Best advice with AI coding: don't use the same company's models to review your code as what you used to create it. e.g. use Sol to review Grok, or the other way around.