|
|
|
|
|
by xKingfisher
231 days ago
|
|
> Coding for others is not art. It absolutely is, and I think it's what separates good from bad and junior from senior devs. Most devs can produce an artifact that more or less works. But one that has an internal consistency others can understand and extend, one which accurately captures the problem as it exists and ways it will likely change, is much more of an art form. A big part of that is knowing which situations are worth making a stand. Every you write code or leave feedback, your doing it for your team current and future. |
|
You shouldn't strive for internal consistency with yourself, you should strive for external consistency with the other developers in your team. If someone reads your code and immediately knows it was you, you probably aren't doing a good job.
And that's the difference. If you are doing a good job as a software engineer, no one should notice you. If you're making good art, everyone should see you. And that is the difference between devs who think they're good, and devs who are truly good.