2,911 karma · joined August 10, 2018
Also, if ever someone had a bad trip, meditation would help to bring it back under control
In my limited experience, I have not seen this done effectively in a software project. What does this actually look like when done properly? Ie, how do you store the data and keep it from becoming busy work?
I feel that the code reviews I’ve been a part of were not as effective as they could have been. I think there is social awkwardness at criticizing design or conceptual aspects, and a multitasking aspect that means the reviewer is in a hurry and mostly checks conformity to the style guide. Very little checking out of branches and manual testing happened, so we had more regressions than expected.
Is this the norm? What practices have you seen that lead to better results?
https://www.omgubuntu.co.uk/2019/09/pinetime-linux-smartwatc...