News for hackers. Stuff that matters.
Re:Best practices for remote software engineering by mandeepj on Monday April 26, 2021 @05:20PM (#26948309)
> avoid 3 hours of writing unit tests

Why? Unit tests are our closest allies

Re:Best practices for remote software engineering by arvinsim on Tuesday April 27, 2021 @01:13AM (#26952276)
Just because something is important doesn't mean it is enjoyable.
Re:Best practices for remote software engineering by mandeepj on Tuesday April 27, 2021 @02:03PM (#26959305)
I consider Unit tests to be essential. People who don't like them, maybe they never tried to drive a value from them.

I also use-to consider them not important, but they have saved my as* so many times.

How would you drive a big refactor, without introducing new bugs - without unit tests?

With a solid test coverage, via a button click, you can conclude - how functional is your code base. Of course, not on the basis of weak tests.

Re:Best practices for remote software engineering by twh270 on Tuesday April 27, 2021 @10:05AM (#26955973)
I know this sounds like evangelism, but I absolutely hated writing unit tests until I learned TDD. Now, I don't always write tests first, but I usually do.

I'll also say that I have seen a lot of time wasted writing useless unit tests. That can contribute significantly to the "I hate unit tests" feeling.

Re:Best practices for remote software engineering by noisem4ker on Tuesday April 27, 2021 @01:12PM (#26958729)
Maybe not enjoyable, but also not anxiety-inducing like certain foundational design tasks can be. For procrastinators, writing a small unit test can be a near-mindless, easy activity to get going.