chris_nielsen

Yeah exactly. I noticed Claude start doing exactly this a month ago too. It recursively breaks problems down while allowing you to either change direction at each level or keep going. This is where claude jumped up to be legitimately better at solving real world problems than a substantial amount of developers. I can only assume the other AI companies are just going to copy the approach shortly too.

Yeah LLMs ingest all 4 and can conversationally give you all 4. I suppose it’s orthogonal.

Where would ChatGPT fit?

Yeah “how this logic flaw occurred” is the wrong question.

How a common bug was rolled out globally with no controls, testing, or rollback strategy is the right question

Page wont load for me. BUT, this title is the first sensible thing I’ve heard someone say about Agile in 10 years.

I just don’t use the word Agile. Too many people like it for the wrong reasons, or hate it for the wrong reasons. Everyone has a different understanding of it. It’s just not useful.

If I say “let’s use Agile” it’s just going to lead to arguments and misunderstandings.

Id always rather be more specific about which Agile idea I think will be useful. E.g. “let’s build a prototype before we waste time planning too much detail” or “lets get something built and released so we can learn more about what our customers want” etc.

I feel like there are some very precise ways to think about these things.

For example, a backlog is a priority queue. A priority queue can only be long if work is added more frequently than it is removed.

Work can be removed if it is either completed or abandoned.

Work can be added when users request features, users find bugs, product owners predict features will be useful, or the dev team adds technical improvements.

Talking to users will increase the bugs identified and the user requested features.

So by these relationships, talking to customers will directly increase the size of the backlog.

And the overall backlog length may be large due to many factors unrelated to talking to customers: slow development, never deleting out of date work, adding too many technical tasks, adding too much unvalidated vision work, etc.

Does anyone know of any books, blogs or youtubers that bring this kind of logical system level thinking to software work management?

That's awesome, ok I'm going to go check it out. Great work!

I love this, but Im using DataSpell from JetBrains at the moment because it has 2 killer features:

    1. Variable viewer so I can see the current value of all variables in scope. 
    
    2. Interactive debugger

Maybe the variable viewer is only important because Jupyter notebooks don’t track and rerun dependencies? So I wouldn’t need it with Marimo. But the interactive debugger is priceless.

Any plan to add debugging?

This looks super useful, can’t wait to try it at work tomorrow!

Not trying to be cheeky, but why not c#? Has pts 2, 3 and 4. For pt 1, what in Rusts type system are you looking for?