3 ms·
Let me chime in. I've been consulting crypto(graphic) projects for years and systems that are developed by one person are way way clearer and simple than system
by baby 8y ago
Let me chime in. I've been consulting crypto(graphic) projects for years and systems that are developed by one person are way way clearer and simple than systems developed by nultiple developers. Things like TLS become a mess once multiple developers start collaborating. It's weird. My theory is that one dev working on a project can refactor it many times during development, whereas this would be an insane thing to do when collaborating.
- pvorb 8y agoWhy would major refactoring be insane when collaborating? We do this regularly in my team in early stages of projects and only when really required once projects become stable. But these projects are usually not about crypto, so I might miss the difference here.
- revvx 8y agoYes. After many years I have exactly the same experience that you do. Programming intent and vision is hard to communicate, so sharing code is always a compromise. It's much better to work with smaller units of code that communicate with each other using simple, clear and testable APIs.
- greenyoda 8y ago> systems that are developed by one person are way way clearer and simple than systems developed by multiple developers Brooks called this "conceptual integrity": https://en.wikipedia.org/wiki/The_Mythical_Man-Month#Conceptual_integrity https://en.wikipedia.org/wiki/The_Mythical_Man-Month#Concept...