|
|
|
|
|
by eternityforest
513 days ago
|
|
Very interesting! I wonder if this is actually possible or practical for all devs. Then mention subconscious skill, and I think some people improve with practice more than others, and there may be individual differences in the "Noise floor" of trivial mistakes, like swapping plus and minus for no reason you could explain, they're just in the same category and you vaguely pattern matched that an operator goes there, and didn't think about it because people don't analyze every single token like a robot. I can ship code that is more or less bug free, and I always aim to do so, but I don't really consider the idea of directly writing good code. I try to remove opportunities to fail, designing an architecture that I think wouldn't take a lot of skill to implement, and then write the code, and then assume I have still failed in every imaginable way, and check for those failures, even if I have looked over the code ten times and am sure that I didn't make some particular mistake. This is generally how I think about life in general too, I'm always thinking "Use a protective case" instead of "Just don't drop it". |
|