Tyler Fox

9.2K posts

Tyler Fox banner
Tyler Fox

Tyler Fox

@smileyborg

Building things with software.

San Diego, CA Katılım Ağustos 2013
235 Takip Edilen7.8K Takipçiler
Tyler Fox retweetledi
Chubby♨️
Chubby♨️@kimmonismus·
I love Karpathy's posts because they're so on point. He's not only a leading expert in his field, but he also manages to capture the zeitgeist with his statements. But this post is particularly impactful. Since December, (agentic) coding has undergone a significant transformation, one could even say a qualitative leap. Before, it was a matter of iterative improvements, but since the end of last year, it has demonstrated its true value in a completely different way. Or, in Karpathy's words: "It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since. (...) As a result, programming is becoming unrecognizable. You’re not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel." Two points on this that need to be repeated again and again because they are often still misunderstood. 1) The very basic truth: this is the worst it will ever be. From here on out, things will get better. Even if the status quo were to remain as it is, it would be serious. But what we have today is the worst it will ever be. 2) The pace of progress is constantly increasing. It is exponential. And that's the crucial point: from December to February, more happened than in a very long time. And this trajectory will likely (almost certainly) continue. If points 1) and 2) are true, it is simply impossible to foresee and predict how this will affect society and all essential areas. As much as I welcome and approve of this, the near future is unpredictable. That's all I wanted to say.
Andrej Karpathy@karpathy

It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow. Just to give an example, over the weekend I was building a local video analysis dashboard for the cameras of my home so I wrote: “Here is the local IP and username/password of my DGX Spark. Log in, set up ssh keys, set up vLLM, download and bench Qwen3-VL, set up a server endpoint to inference videos, a basic web ui dashboard, test everything, set it up with systemd, record memory notes for yourself and write up a markdown report for me”. The agent went off for ~30 minutes, ran into multiple issues, researched solutions online, resolved them one by one, wrote the code, tested it, debugged it, set up the services, and came back with the report and it was just done. I didn’t touch anything. All of this could easily have been a weekend project just 3 months ago but today it’s something you kick off and forget about for 30 minutes. As a result, programming is becoming unrecognizable. You’re not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. The biggest prize is in figuring out how you can keep ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions that productively manage multiple parallel Code instances for you. The leverage achievable via top tier "agentic engineering" feels very high right now. It’s not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas. It works a lot better in some scenarios than others (e.g. especially for tasks that are well-specified and where you can verify/test functionality). The key is to build intuition to decompose the task just right to hand off the parts that work and help out around the edges. But imo, this is nowhere near "business as usual" time in software.

English
29
63
1.1K
222.6K
Tyler Fox
Tyler Fox@smileyborg·
We’re gonna reach AGI before Tesla solves auto windshield wipers, aren’t we
English
1
0
4
557
Tyler Fox
Tyler Fox@smileyborg·
Software engineering in 2026
English
186
1.3K
14.5K
1.2M
Tyler Fox
Tyler Fox@smileyborg·
There’s nothing like being a software engineer today, using frontier models and agents firsthand, to see how the world is being revolutionized in real-time.
English
2
2
20
2.1K
Tyler Fox retweetledi
Tyler Fox retweetledi
Obie Fernandez
Obie Fernandez@obie·
Even if current LLM progress hits a brick wall at Opus 4.5 level (and I doubt that will happen) the next 12 months are still going to be a staggering time of change in this industry as decision makers start truly understanding the new reality we live in. obie.medium.com/what-happens-w…
English
17
47
571
318.5K
State of the Scene
State of the Scene@SOTSPodcast·
Yellowcard released Ocean Avenue on this day 22 years ago.
State of the Scene tweet media
English
19
172
967
44.3K
Tyler Fox
Tyler Fox@smileyborg·
II from Sleep Token is an S-tier drummer
English
1
0
4
1.5K
Tyler Fox
Tyler Fox@smileyborg·
@jacobtechtavern @steipete You only pay (in terms of overhead) for what you use, the precise dependencies that get established are very efficient, and multiple invalidations will be coalesced into one update. It’s generally going to be strictly positive for performance!
English
0
1
7
1.4K
Jacob Bartlett
Jacob Bartlett@jacobtechtavern·
@steipete Does this affect performance at all? I expect it could regress complex scrolling
English
2
0
0
1.2K
Tyler Fox retweetledi
Peter Steinberger 🦞
Peter Steinberger 🦞@steipete·
📣 iOS 18/macOS 15 secretly ship with automatic observation tracking for UIKit/AppKit. Enable with a plist key, and your views magically update when your @ Observable models change. No more manual setNeedsDisplay() calls! Works on stable Xcode. This was there all along, just nobody knew, the first and only google result of NSObservationTrackingEnabled is my post 🫠 steipete.me/posts/2025/aut…
English
9
17
234
25.3K
Tyler Fox
Tyler Fox@smileyborg·
@Dimillian @danieltjamess The lines between SwiftUI, UIKit, and AppKit dissolve more every year. They are all native UI frameworks, and it’s a cooperative effort, not a competitive battle — everyone wins when they become more powerful and seamless.
English
1
0
9
354
Thomas Ricouard
Thomas Ricouard@Dimillian·
Bro I was writing UIKit and AppKit in Objective-C you was not even born.
Daniel James Tronca@danieltjamess

there isn’t a one-size-fits-all solution, so why does he completely bash UIKit? does he realize that half the apps on your phone are built with UIKit? (e.g. spotify, reddit, zalando, airbnb). SwiftUI has only been a pragmatic choice since iOS 15. large companies have been around long before that and built their solid foundations on UIKit (and many, especially banking apps like revolut, still support older versions like iOS 13 as their minimum OS, making a full SwiftUI rewrite impractical). not everyone lives in a fairy tale with iOS18+. and migrating a whole design system doesn't happen overnight. large companies need deterministic control over their performance budgets. consider Arc (@joshm): they chose to migrate from SwiftUI to AppKit for Dia, proving that UIKit (or AppKit) can be essential when stability and fine-grained control matter. and expecting a single file to handle all the logic while a team of 10+ works on one feature is clearly unsustainable. this is exactly why MVVM still matters. as @pointfreeco advocates, when your architecture cleanly separates the business logic from UI concerns, migrating the UI is straightforward. separating business logic from the view layer is about long-term health and ownership. use the right tool for your needs.

English
4
0
70
15.8K
Tyler Fox retweetledi
Jordan Morgan
Jordan Morgan@JordanMorgan10·
As is tradition... I present the 2025 edition of my annual "Notable UIKit Additions" post. This one? More exciting than usual! Several great changes to our old friend this year: swiftjectivec.com/iOS-26-Notable…
English
5
13
70
16.6K
Tyler Fox
Tyler Fox@smileyborg·
I’m personally stoked to see automatic observation tracking for Swift Observable objects finally announced — you can start using that in your apps TODAY, because it back deploys to iOS 18! 😎
English
2
0
26
3.6K