It's interesting to watch application logic and the code logic drift apart, over time.

I knew it should do that, if you're any good, but I've never watched it happen.

Hmm, I need to figure out this "user stories thing" I always sounded like crappy rationalization for things the party making the application wants and have nothing to do with the customer.

I've never actually seen a user story but from the results I imagine they go something like.

"As a user first arriving at the website, I'd like to see a bunch of platitude laden marketing gobblty-gook that is as inoffensive as possible."

Or

"As a user, I'd like a sales rep to contact me some day to determine how much I can afford to pay for whatever it is that you actually do."

It always seems that the customer stories they invented serve the interest of the business.

yeah, i find when i ask junie to write code to change things it often just piles on more crap instead of changing stuff. very often i wind up rewriting parts of the code and if it fails to actually debug shit and make tests pass, after 3 times i just usually end up writing the code that was needed by hand. and then, of course, the tests pass because it was written the right way.

they can sometimes save a lot of work but sometimes make more work. learning how to avoid those potholes they fall into is a key part of making the work more efficient.

As I see it, we're in a period of "just ship it". We gotta get stuff out the door, and Stella, armed with AI, can do that very rapidly.

Once we get the application to behave the way we want, we can start writing tests to lock in the behavior, then refactor the internals to make it more maintainable and more efficient.

Regarding Svelte, I've spent about a year now reading those docs over and over again...it's all in my 🧠