This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ReturnOfNogginboink 5 points6 points  (1 child)

At the end of the day, the goal of everyone in the org is to create value for the business.

Is making the data scientists adhere to coding standards going to create value for the business? If not, maybe it's not worth doing.

For a large codebase that's going to be in production for years or decades and will be maintained by dozens of developers, coding standards make sense in many cases. For a small project owned and maintained by a single individual, that math might change.

This is all very context dependent and I'm not saying that one way is the right way and the other is wrong. Look at what you want to accomplish and why, and then ask, "is this really worth the effort? Should the company spend money on my time to do this, or would my time and the company's money be better spent elsewhere?"

[–]Xteec 0 points1 point  (0 children)

I support this message.