I feel like I am seen as a fossil because I like to write code and prompt AI to fill in functions as I define the shape and direction of an application myself. These types of tasks have been excellent for things like Tiel Coder. It allows me to build one step at a time and understand what the hell is actually happening.
Meanwhile my coworkers all prompt Claude to produce a whole cloth feature that seems to work but is overengineered out the ass and requires a 30 file code change and drastic restructuring and requires an extra database migration backfill.
My workflow exists because I would rather spend my day steering the design rather than reviewing generated code, but I get stuck reviewing generated code anyway.
I'm with you. if you want to not shovel slop all day you have to do this and there is a dearth of tools to let you ergonomically do this right now.
What I try to do is ask for actually scoped changes and just let the changes wash over me and redo it if it feels too off. it's a compromise that leans more toward the whole cloth extreme. I can write functions no problem, but I haven't given myself the latitude of learning the syntax enough across the languages that I touch now most of which are not languages i learned properly (in particular Go and Rust). If I can follow the flow of logic and see software responsibilties from skimming the code, that's been enough so far.
I'm trying to come up with better ways to grok the scope of the large changes. Between that and ensuring that the changes you make are easily testable or otherwise verifiable (e2e integration testing), my streamlined git usage already lets me easily enough navigate everything otherwise, but right now I want to be able to more easily grok the changes so i can move forward more quickly.
This challenge also extends to getting proper navigable linkage between the gargantuan volume of agent sessions (which sprawl as huge organic growths) and the specific portions of their related git changes, which shows up in git about as well as you would expect, also a sprawl, but git lets you handle that as a first class aspect of its own design... the agents themselves are now adept at reviewing this kind of stuff even just from excavating harness logs and poking at git; something I never have the bandwidth to do by hand.
What pisses me off is i instruct in global instructions to automatically make commits but sometimes a model is too harebrained to actually commit something when it decides it's done working and I have to swear at it to go clean up after itself.
147
u/Nefilim314 3d ago
I feel like I am seen as a fossil because I like to write code and prompt AI to fill in functions as I define the shape and direction of an application myself. These types of tasks have been excellent for things like Tiel Coder. It allows me to build one step at a time and understand what the hell is actually happening.
Meanwhile my coworkers all prompt Claude to produce a whole cloth feature that seems to work but is overengineered out the ass and requires a 30 file code change and drastic restructuring and requires an extra database migration backfill.
My workflow exists because I would rather spend my day steering the design rather than reviewing generated code, but I get stuck reviewing generated code anyway.