It's interesting most of you equate being "good" with being able to close a lot of tickets. I'd take a collegue with knowledge of the fundamentals and that kno

It's interesting most of you equate being "good" with being able to close a lot of tickets. I'd take a collegue with knowledge of the fundamentals and that knows how to ask the right questions - and when not to - over "produces a metric shit ton of code, but when asked doesn't actually know anything". The first one might be slow and might be editing his, horrors or horros, documentation entries by hand, but that's because he is thinking and refining while he is doing it. He is not an automaton spitting out "work units". After some contemplation he will wipe the whole project off the table, because in the grand scheme of things it doesn't pan out while collegue number two was busy generation a metric shit-ton of work units and being happy about his productivity. No LLM will tell you that or more specifically, no LLM will tell you that if you don't know what to ask for in the first place.