@perrymetzger The best thing is that it actually *answers* the question that you asked. Search returns results *about* the search terms you entered. That saves me a lot of time.
I iterate. I’m around 4-5 on the first pass(es) because I value getting working code early. Then down to 2-3 for a review/tidy pass(es). What do you do?
The "should you read code" debate is dumb because the real decision isn't binary, it's a scale:
1. Reading every line of every diff
2. Scanning every diff, reviewing important lines
3. Ignoring diffs but understanding the 'why' of every PR
4. Spot checking PR's instead of reading every one
5. Ignoring PR's, but doing regular spot checks on the codebase
6. Ignoring the code, but spot checking agent traces to help improve the system
7. Ignoring both the code and the system, let models handle everything
Where are you on the scale?
@deanwball@AndrewCurran_ I agree with this. Of course no-one really knows where and how fast model capabilities will grow, but we have no reason we are there yet and the sky’s (not even) the limit. Exciting times.
Did you know - Ash has its own built-in Xterm compatible terminal, complete with retro '80s vibes.
You can also !one-shot bash commands, but sometimes you need to drop into a full terminal session.
Working on some visualisations . I find @observablehq awesome but fiddly. The AI is crushing it. I can be much more ambitious and achieve more - faster.
@mitsuhiko I know what you mean. I found a bug the other day because my tests were suddenly slow. Turned out my wifi connection was shitty. Never would have found the bug otherwise.