3 ms·
"While developing a new project is like rolling on a green field for you, maintaining it is a potential dark twisted nightmare for someone else." There is noth
by jroseattle 9y ago
"While developing a new project is like rolling on a green field for you, maintaining it is a potential dark twisted nightmare for someone else."
There is nothing about this list of best practices that makes any applicable project more maintainable without understanding the practices being followed.
As long as these practices are well-known within the company and enforced over the lifecycle of code/product/project/etc., it will succeed. Without that understanding, this list eventually becomes untrusted.
Good on the folks at hive for following what appears to be solid practices in their JS projects.
- vahidpg 9y agoThanks, for your comment. I do agree that "best practices" isn't the best word. I probably should have said, "Hive common practices". Most developers have understanding of the process but just have a different taste and styles, we just tried to make things more consistent. We thought having such a document is better than not having it, and even if a developer doesn't understand the practices being followed this document brings an opportunity to learn them. I know it's not perfect and looks abit random, that's why we made it public to get some feedback.
- jroseattle 9y agoYep and understood -- it's what works best for your team. And yes, consistency is where the value lies. I've found these efforts to be successful as long as those guidelines are socialized among the team and it's treated in a consistent manner. Looks like a great list thus far!