For anyone curious, https://t.co/8Jq4mwPisw
I really wanted a tool that avoids the pitfalls of vibe coding and prompting without line level context. I can review the code, ask questions, and prompt changes. All while easily staging/ignoring anything inconsequential.
Hacking on a tool to bridge the gap between "agent finished iterating on a plan" and "committing+pushing my changes for review"
It's basically `git add -p` with super powers, letting you prompt+polish as you go. Experimental and still lots of jank, but fun so far!
@whatisakatie High Performance MySQL like mentioned above is great, I reference it all the time. I just started reading https://t.co/ZAMW1fzghT too and so far it's been helpful a time or two (I've jumped around chapters though).
Use the index https://t.co/3n3UhzO2TF goes pretty in depth too.
do you work primarily in a terminal via SSH or a codespace? I made a tool that you may be interested in! it provides clipboard access and `open` support through ssh so itโs almost like working locally.
https://t.co/OhMDveq2JD
I've been using TypeScript on a side project and I'm really loving how much type safety you can achieve with a bit of effort. I ended up migrating from hbs to JSX/React to get even more type-safety and wrote a post about it.
https://t.co/KfqVNglyvk
the issue is that the formatter turns the with parens version into the without parens (and breaks things). there's only one quick fix I can think of and that's to make all method calls add `()`, which seems not great.
Imagine `foo().bar().baz() unless some_method_value().nil?()`
Hacking on a code formatter for Ruby and learned about this fun shadowing edge case:
With explicit parens calls the method defined on the class, without returns nil.
Added `set -g status-right '#(cd #{pane_current_path}; git rev-parse --abbrev-ref HEAD)โ` to my `~/.tmux.conf` and got rid of RPROMPT to show the current git branch and itโs been great.
@Randemonium @kddeisz Lots of trial and error, not production ready yet but Iโm feeling pretty good about the underlying approach now in terms of consistency.
Just needs more time invested in widening AST support, tightening up indentation rules, code cleanup, etc.