[isaacremuant]

I understand where you're coming from and the admiration for someone for whom no problem is seemingly impossible.

I wouldn't glorify "brilliant code" that much though because code should be made to be changed. If it isn't, it's a fragility trait, not a positive trait. Code that no one knows how to change is opportunity lost.

I do understand that it may be hard to create stuff for others when you're alone and going very fast but I don't think praising it is the right idea.

[safetytrick]

I don't think changeable code is the number one priority. The goal is to solve a problem and code that solves a problem without needing to change is sufficient.

Code that doesn't need to change is a really good sign that you've got something good.

[isaacremuant]

The real world moves. If your code didn't change it must be generating value against something that is very standard but I'd be very surprised that you're not modifying, adding, etc based on usage to derive even more value somehow.

> Code that doesn't need to change is a really good sign that you've got something good.

Not really, but you're thinking in terms of "my code nailed it because I'm not touching it" and that has NOTHING to do with it being easy to change.