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.
(or - Stop users button mashing while you generate their reports)
Imagine you have a webapp that dynamically generates reports, maybe they're PDFs (mine often are). Sometimes these reports take a while to produce, because they're retrieving and processing a load of data from some huge database.
While introducing agile development ideas, one of the things which went down really well with the project team was the process I used at the end of iterations. This was based around two simple, regular emails that followed the same pattern. I thought it might be useful to talk about them.