|
|
|
|
|
by scj
2976 days ago
|
|
95% of the time I want to do something in a clearly sub-optimal way is because I'm required to use an unmodifiable code base that forces a path. But sometimes explaining how the situation arises: * Violates NDA/secrecy/licensing agreements. * It can be complicated to explain the conditions that created the situation to people that aren't working with a custom/proprietary tech stack. * Is irrelevant. If the operation needed to solve my problem can be concisely stated, why type a distraction? I remember one post where someone said something like: "It'd be better if you tried this, but if you really need to do X..." followed by an explanation that solved my problem. It made my day. |
|