What rules of software development do you follow?

In "What rules of software development do you follow?" I answer a programming question.

[jeroenadamdevenijn]

I love your videos, keep going, I came up with a question :)

I work in a small software company, my boss is very talented and prefers to build many internal tools himself instead of using standardized software. I said himself, but I meant himself and an assisting senior dev. Although he subscribes to the idea of KISS, it makes it too complicated for junior devs who not only are doing dev work for our clients, but also have to use all this non-standardized internal tooling. My boss sees that as an investment, he owns the code repository, but sometimes it sets junior devs and the testers their brains on fire because of the many non-standardized approaches. So the question is, does it reward a company enough to own its own tools or is it better to focus on client needs?

[recycle-bin-camp]

Hey Frederick, does it happen at your job that someone writes code with security flaws or doesn't implement the specification completely, but when you talk to them, they don't understand because they can't see the flaw? They don't get it and convinced that it was done in a good way