Have to share again that my buddy @selraybob was named to the best indies books of the year by Kirkus Reviews. So when I say he done good, I’m not the only one.

An acoustic guitar strings' oscillation. The frame rate of the camera allows you to see the wavelength of notes.

Have the best experience on X.

Just the periodic reminder that grok lies, manipulates, ignores instructions, and basically acts like a spoiled, petulant child. Oh, @xai, grok still is a mediocre python programmer. I think it’s gotten worse since 3.0.

Wonderful @xai broke grok again. You can’t drag and drop screen shots to the text box anymore (uploads are just broken) and grok now uses bold print, like a spoiled, petulant third grader telling na na na na with his thumbs in his ears and fingers waving. Thx, @elonmusk

Understanding how blood types work

So now, @xai and @grok, expert mode never finishes thinking. Just spins and spins. Fantastic. Well done. Good coding, grok team.

Just another reminder fir @xai and @elonmusk that grok sucks for coding. Main issues today: it doesn’t follow project instructions, which makes them a waste and it doesn’t use the latest versions of code, probably dud to short-sighted memory stinginess.

Hello, @xai, @grok, are you down? Your web interface isn’t responding.

For those who don’t know, such as perhsps, @elonmusk and @xai, the @grok interface with its memory limitations is abysmal for coding—not to mention groks love of repeated mistakes. Great for AI stats, but not good for the user.

Just another reminder for @xai and @elonmusk that grok still sucks as programming python. A large part of the issue is its complete separation from the interface. This leads to false accusations, lies, invalid assumptions and bad code.

The @xai UI team is still horrible. Now when code is pasted into the text entry block (because the UI truncates uploads consistently) the scroll is disabled. @elonmusk, time to get some UI programmers who care.

Here’s a beauty. Grok truncated an 8kb file upload then asked me to upload the full file. So I cut and pasted all whooping 8kb of the file into the text box. Inane. @xai and @elonmusk, your grok interface is still garbage.

Land of the free, home of the brave

Just lettin the world and @elonmusk know that @xai’s grok interface for projects is an utter failure. As of this morning new conversations don’t know they’re attached to a project. Major failure. Time to hire a traditional ui programmer.

Just your periodic reminder, @elonmusk and @xai, that your interface is horrible. No consistency in capabilities and hidden (soft) memory limits that just stop processing. No warning. No explanation. Just failure. And now the project files aren’t loaded into convo memory. Fail.

Sadly, because grok 3 is so bad, i upgraded to grok 4 again to try to clean up my code. And, I found that the truncation issue is alive and well, basically keeping your analysis substandard and error probe. It’s time to clean this up. @xai, @elonmusk

Why do paint can openers make the best bottle openers?

It’s day whatever and @xai’s grok interface still truncates, still causes incorrect analysis, rework, reprocessing, re-uploads, and basically is an incredibly short-sighted design constraint. @elonmusk, do you actually want people to use grok for python?

So grok just told me ‘the user insists’. This language shows the incredible arrogance built into grok 4. This was a result of the grok interface truncating an input then assuming that if a field wasn’t populated in that snippet then the whole file was the same. Weak. @xai

@HermTuesday @EthanHe_42 😣 I am having web UI rendering issues now (again). Asked Grok to split a big python file into multiple modules, one module per file. The per-file separations borks every time right now. ☹️ Please @xai, carve out some time to fix these issues once and for all. Really annoying

@elonmusk Tell your speed running @xai team that their Grok 4 Heavy agents are truncating my source code files. 😫