Jarrod Parker

Father of 3. Husband to the 1. Data Scientist + Software Engineer. Adirondacker. Martial Artist. AI and Knowledge Graphs @enigma_data

[Jarrod Parker @adkatrit]

@enjalot The ergonomics of it all is still in its infancy. When feedback loops actually become instant, a new flow state will emerge. You’ll still never escape having to succintly express what you actually want. I feel like people are still just under-ambitious with planning.

[Jarrod Parker @adkatrit]

@bernhardsson I’d be super curious to see if there are any examples of places that have smart phones but not social media access

[Jarrod Parker @adkatrit]

@bernhardsson Phones alone dont do this. Its the combo of social media. We no longer have to go to bars to strut our stuff, we anonymously gawk at the top 0.01% preventing the serendipitous encounters that occur IRL.

[enigma_data @enigma_data]

Enigma's card-backed revenue signals are now inside Clay, giving GTM teams real transaction data from actual payment networks. Major financial institutions already rely on this data for compliance. Now GTM teams can use it for growth.
https://t.co/qEefuKC1rI

[Jarrod Parker @adkatrit]

@bernhardsson If you were born before 1970, this comfortably passed in 2024. The disney help line has been fooling people for at least 2 years

[Andrej Karpathy @karpathy]

A few random notes from claude coding quite a bit last few weeks.

Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent.

IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits.

Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased.

Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion.

Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage.

Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it.

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements.

Questions. A few of the questions on my mind:
- What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*.
- Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro).
- What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
- How much of society is bottlenecked by digital knowledge work?

TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

[enigma_data @enigma_data]

The data is unambiguous: when we link 2,000+ @stoolpresidente OneBite scores to restaurant revenue, high ratings consistently map to strong post-review gains. Low scores don’t.

View the full analysis here: https://t.co/YQRDfQXZ0k

[Jarrod Parker @adkatrit]

That masculine feeling of spending 3 weekends in a row trying to fix your mower, then finally getting it and pristinely mowing your lawn in a display of dominance over machines. 💪🏼

[Jarrod Parker @adkatrit]

I agree, but how would you know this is intentional? It’s more likely that smart people choose their level of precision to avoid being unintentionally ambiguous. It’s a learned behavior to cope with the isolating feeling of being constantly misunderstood. Like the double meaning in how you’re using the word “smart”.

[Jarrod Parker @adkatrit]

@bernhardsson Meanwhile, myspace had 20 million teenagers learning html and css to add sparkle animations as a form of self-expression.

[enigma_data @enigma_data]

Businesses are everywhere. So how do you learn more about them? If you're @merinids you hack together some map shaders and create a business radar to test Enigma's new geolocation capabilities.

Take a look at the video we whipped up and sign up for the Enigma graph-model-1 Research Preview to give the Enigma Tracker a try. https://t.co/0PtXVer8cW

[Jarrod Parker @adkatrit]

Buying a Tesla doesn’t make you a nazi any more than buying an iPhone makes you complicit in child labor. (Actually quite a bit less)
This is a cognitive bias called fundamental attribution error and is significantly contributing to societal fragmentation.

[Jarrod Parker @adkatrit]

@quantizor Grape juice bottle from last year. High capacity, non-plastic, easy to replace.
My water container requirements: 1. must support unobstructed chugging. 2. Must be high enough capacity to reduce intraday refills to less than 4.

[Jarrod Parker @adkatrit]

Deep sleep -> restore the body
REM -> restore the mind

If you want to feel better, get to sleep
If you want to think better, stay asleep

[Sahil Bloom @SahilBloom]

Dopamine from information gathering is a dangerous drug. Your entire life will change the moment you stop looking for more information and start acting on the information you already have. Get your dopamine from action.

[Jarrod Parker @adkatrit]

Say what you want about the cybertruck, but we just lost power and its acting as our generator with 15hr to go on only 100mi charge and 20% discharge limit. I expect if it were full and discharge was set lower, we’d get several days power out of it.

[Jarrod Parker @adkatrit]

@quantizor Larry Carlson is the OG of this kind of thing

[Jarrod Parker @adkatrit]

@Andercot This is pretty close to the show Devs https://t.co/aEmG0EMgBj

[Jarrod Parker @adkatrit]

@ylecun No whys?

[Jarrod Parker @adkatrit]

@hydrosquall @enjalot @cyberbgone Reminds me of the work of @cortesi with https://t.co/hLouxb6PYm
I remember seeing this fresh out of college from a security / data viz background and got obsessed with space filling curves for a while.