▲ | SkyPuncher 6 days ago | ||||||||||||||||||||||||||||||||||||||||
Yes and no. The broader business context translates well, but each model has it's own blindspots and hyperfocuses that you need to massage out. * Business context - these are things like code quality/robustness, expected spec coverage, expected performance needs, domain specific knowledge. These generally translate well between models, but can vary between code bases. For example, a core monolith is going to have higher standards than a one-off auxiliary service. * Model focuses - Different models have different tendencies when searching a code base and building up their context. These are specific to each code base, but relatively obvious when they happen. For example, in one code base I work in, one model always seems to pick up our legacy notification system while another model happens to find our new one. It's not really a skill issue. It's just luck of the draw how files are named and how each of them search. They each just find a "valid" notification pattern in a different order. LLMs are massively helpful for orienting to a new codebase, but it just takes some time to work out those little kinks. | |||||||||||||||||||||||||||||||||||||||||
▲ | ModernMech 6 days ago | parent [-] | ||||||||||||||||||||||||||||||||||||||||
This is like UB in compilers but 100x worse, because there's no spec, it's not even documented, and it could change without a compiler update. | |||||||||||||||||||||||||||||||||||||||||
|