@glyph totally to your point tho… the party trick might just be that. It feels fun to have progress happen when laundry is being folded but in the end I might end up churning anyways
R
raphael@mastodon.sdf.org
@raphael@mastodon.sdf.org
Posts
-
I wish I could recommend this piece more, because it makes a bunch of great points, but the "normal technology" case feels misleading to me. -
I wish I could recommend this piece more, because it makes a bunch of great points, but the "normal technology" case feels misleading to me.@glyph lowering of activation energy is how I see that. And while I agree that the futzing is way undercounted (and that, IMO, a lot of this falls over in longer sessions and is just not worth it)… a strong dev who knows exactly what the solution is supposed to look like can get paper cut-y stuff cleaned up. A lot.
The “whine on slack about a thing being busted” turns into a fix, and most of that you can just go get a cup of water or review something in the meantime. Cool party trick at least
-
I wish I could recommend this piece more, because it makes a bunch of great points, but the "normal technology" case feels misleading to me.@glyph I like your breakdown in those articles.
I think that some of the more valuable stuff has been not when juniors prompt and don’t get value, but when seniors prompt, go do something else for a bit while the machine churns for a couple of minutes, and then come back to something that is pretty close to a good solution.
Think about a thing that might take you 15 minutes to kinda menially do (add some CLI bo flag that then needs to get passed down 3 layers in some spot for example)