For practical fixes, consider replacing the TV with a “commercial monitor” and connecting an Apple TV device instead (or an open source thingy).
Disconnecting “smart tv” from internet to use Apple TV is possible and might work, but you will get nagged to reconnect all the time. And TV mfr will eventually try to find workarounds - purchase access to wireless connections from large-footprint connectivity providers (Xfinity WIFI, 4g/5g networks, etc) or create a p2p network among their own connected devices. I doubt they do it right now as it’s less profitable to focus on niche audience, but eventually it might become profitable enough.
The original selling point of mobile web (tiny screen with text-only data, before real mobile web) on mobile phones or even watches was checking stock prices and weather. It was really weird that checking stock prices was something you need to do on the go, especially from the watch.
Most valuable thinking is done at the margins, where you don’t have much capacity to emphasize with a diverse and unknown audience.
That said, abdicating to an LLM is the worst of all worlds - you’re not thinking and the product is not tailored.
The solution is obvious - write as much detail as you need and allow readers to interrogate the virtual you with an LLM, maybe not even reading what you write.
Happy is tall order, but there is a uniquely American sense of impending doom that is always hanging over your shoulder that doesn’t exist in most other countries.
Do you find that given a formal spec an agent can write complete implementation you don’t have to even read?
I keep thinking about various ways of “pushing back” on an agent, shortening feedback loop and extending what we can grantee about results.
At the most low level we can nullify probability of the next token if that token is not desirable (eg json schema enforcement under constrained inference), this is the fastest pushback. Various compiler checks, linters, unit tests, exotic type systems, e2e tests, production traces. Wondering what else is out there.
On a tangent, iirc pascal allowed single-pass compilation, so I wonder if we can embed compiler directly into inference, sort of constrained inference on steroids.
I think that reading and reviewing software is responsible.
Source code exists for humans to read first, and for computers to read second. Programming languages are unambiguous, and most languages take well to abstraction. Software can be written at a level that is appropriate for human review. Boilerplate can be avoided. It's well written when it is easy for stake holders to understand directly, without translation and without an LLM to summarize it.
Software should be the output artifact of the process, because it exactly describes the behavior of the system. The formal specification explains how the software embodiment must work, and in constructive proofs, it's even possible to extract the software embodiment from this specification. But, from a practical perspective, this is too time consuming. Instead, specification should be written to explain the rules that software must follow, instead of the exact behavior. In this case, the source code is still an important artifact, and it should be reviewed and improved upon as part of the process.
Can it debug the apps? That would the app singularity - user speaking at their phone until phone complies and produces desired app for the current moment.
It can debug, yes, but capability ranges from godlike for algorithmic issues to mediocre for subtle UI things. We are pretty close to your described app singularity if the app is within GPT’s wheelhouse.
Yes, you can iterate on the app and ChatGPT Work will then create new versions of the app.
If something in the UI of the app looks weird, you simply take a screenshot and ask ChatGPT to fix it. Or what I also like to do is add a logging functionality to the app. If something goes wrong, I then just upload the log to ChatGPT so that it can fix it.
Memory-hard hash functions maybe? Like, you must dedicate 4gb of ram to compute the function. Not a problem for a one-off, but is a problem when reading lots of pages at once.
Or… the site will serve a random seed and the device must compute 4gb of pseudo-random data, then supply a value at a random server-demanded offset.
Disconnecting “smart tv” from internet to use Apple TV is possible and might work, but you will get nagged to reconnect all the time. And TV mfr will eventually try to find workarounds - purchase access to wireless connections from large-footprint connectivity providers (Xfinity WIFI, 4g/5g networks, etc) or create a p2p network among their own connected devices. I doubt they do it right now as it’s less profitable to focus on niche audience, but eventually it might become profitable enough.
reply