Hacker News new | past | comments | ask | show | jobs | submit login

A couple strategies come to mind, but may need a bit of tweaking for your specific situation.

Code style: mostly an already lost cause debate between two coders. Pick a third party style that you both can agree to use and agree never to add special rules. Just don’t. Use auto formatter. Debate settled, and both (all) parties will adapt to new style. Ex: in python, use ‘black’ formatter, end of story.

Extra features that make code harder to read: don’t make the problem about the coding/technical problems, make it about end user usage, business problems, and business opportunity cost. Will the end user care more about this dynamic hyper optimized code thing, or an extra feature? Can the business charge more for the extra optimization?

No matter how brilliant the code is, it’s useless if the end user doesn’t end up using it - if they don’t know how or if they just won’t really care.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: