All features should now be created via this workflow. It’s basically a ticket going in, a few rounds of questions back and forth with the LLM, then waiting for an hour until it finishes.

Then having to read/review 2k lines of AI-generated code. It’s terrible.

Sometimes I feel like it would be best to only give the agent access to clear API boundaries (say public interfaces to certain modules) and let it work out a new system from scratch given the expected inputs and outputs. Then plug this independent solution into the system. Of course it can still overfit these interfaces but it’s less than having access to the entire codebase.

Thinking about it, maybe it’s possible to let one agent extract those interfaces, then use them as grounding for a new session.

One less nice way of achieving the same is to tell the agent once in a while that it should think completely from scratch (from first principles). But this relies heavily on instruction following in the reasoning part, which sometimes works and sometimes fails.

https://www.raycast.com/new

Not if your company decides to be "AI-first" and puts agent use on your job results.

So you can access the Obsidian markdown files from the web? How are you solving that?

Via VPN or do you sync your files with a server?

No ads, data can be exported, tons of exercises to choose from, live activity on the lock screen, stats, timers, measurements and much more.

Was really worth it and they seem to still be updating the app.

Edit: lifetime subscription is only ~24€

Nice write up of your findings. Enjoyed reading an article written by a real human.

At least some of them had an "ai generated" tag.

And once you notice the bait (via telltale signs) you feel betrayed. Betrayed for your attention, thoughts and time.

Like how do you come up with a cohesive looking set of components for example? I use design tokens but they are not enough to get to a coherent design where components look like they belong together and kind of stand out from other designs.