Hacker News new | ask | show | jobs
by freework 4924 days ago
Don't worry about the process. Worry about the outcome of the process. Is the site always down? Do you fail to ship? If so then you need to fix things. Otherwise just let people work the way that lets them be most productive.

For instance, I'm not a fan of unit testing. I find that 99% of the time when my tests fail, the failure is the test itself, not he code. WHen I'm forced to write uni tests for everything, it slows me down greatly. I prefer to keep my code clean and readable, instead of focusing on 100% code coverage. The same principle applies to CI and other such "processes", in my experience. But thats just me, everyone works their own way.

2 comments

I agree with this, if everything works with the company's current process, there will be no way to convince people to change, and there wouldn't be any reason to.

Try to maybe focus on fixing problems that your company actually has.

Will do that.
Are you a single dev or do you work in a team ?