Code reviews are a good idea for many reasons. They encourage people to share their opinions on how code should look at its prettiest and also what they like to see when they're called in to look at the ashes of a dead production app.
These are my opinions on reviewing code with a view to swearing as little as possible if I have to see it again when stressed.
I get a lot of questions about the fine details of what remote working actually involves for software development. So here's a few descriptions of how various activities play out when I'm working from home.
To format internationalized data properly, Java has a bunch of handy features. If you're English, you'll probably be setting your Locale to
Locale.ENGLISH and all your i18n messages will come out fine, numbers, percentages, currencies etc. look right, and it all pretty much works. However...
I've been remote working as a software developer for more than 12 years. That's full time remote, with occasional trips to "the office". Here's a few of the things I've learnt and passed on to other remoties as we've built a remote working team.
One of my first attempts to use the PiGlow was to give some indication of the state of a headless Pi Zero as it started up and sorted out its server processes.