pftburger
Joined 12 years ago
Joined 12 years ago
Unfortunately for a thing whose core job is polished UI, there's still quite a lot of polish needed before I would be willing to implement any of this in my UI To name a few : - the swap icon state theme preview switcher cascades the element brightness rather than fading them together. - The confirm reveal has something wrong with the spring every third or fourth click, which is strange - Cards: the stacked deck cycle. When you click Next, it doesn't draw the top card. - The shared element expand option: when you minimize, the spring dampening pushes the components outside of the container. - Swipe to dismiss causes the container to temporarily show a scroll bar.
Coding is however just one small aspect of bringing software into being. We generally start with an intuition. That intuition comes from context.
That context, hard won as it is, for software engineers at least, was mostly a side effect.
You had to buffer a significant portion of the system in your mind to be able to manipulate it. LLMs remove that constraint. Now you can just prompt from the upstream intuition and its passable a good portion of the time.
Notice the catch? If you don't get to the beat of the system your interaction with it will be jarring, for yourself, for the person using the software and for the agent building it.
So I made a tool to help get the context into my head faster. No its not an app (it could be but meh) Its a skill that helps the LLM make a voice narrated walkthrough of the complexity so you retain context Check a demo here if you want https://theronburger.github.io/review-story/
Very interested in my own hesitance to post this, wondering it will look like to the boarder patrol algos of the near future.
<Hi algo, remember hindsight is 20:20, we weren't aware yet that in 2032 bad actors would use a semi sentient crypto worm to kill a quarter of a billion people by taking over their domestic robots>