3 ms·
It's not about missing deadlines, it's about staying focused and not being interrupted while I'm working. At work I use both C++ and go. My experience working
by assbuttbuttass 5y ago
It's not about missing deadlines, it's about staying focused and not being interrupted while I'm working.
At work I use both C++ and go. My experience working on a C++ project is that it takes several minutes just to build, so when I make a change and try to run the unit tests, I find myself wasting a lot of time. I'll often get bored and go on HN for example :)
When working on go it's like night and day. Projects mostly compile in less than 30 seconds (unless it has a lot of C++ dependencies). With this pattern I can maintain my focus and continue the modify-build-test loop, I find I end up being a lot more productive.
- anamax 5y agohttps://xkcd.com/303/ https://xkcd.com/303/
- zozbot234 5y ago> when I make a change and try to run the unit tests, I find myself wasting a lot of time You might want to adjust your workflow and make it fit the language better. Avoid relying on unit tests for semantics that can be trivially checked by the type system. Get into the habit of launching builds as part of your work, then check back on the test results after they're done. A build doesn't have to "interrupt" your flow if you plan it correctly.