(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.
Remote development mainly involves the same tasks and challenges as when you're sat in the same office, except that any communication issues can't be fixed by physically standing/sitting next to someone. Instead the tools we use have to support us in making the sure communication works.
One of the concerns with remote working is how meetings work. I can't give a general answer, but over about 10 years remote working in software development team, I can talk about the regular meetings that pretty much work for us.
My solar inverter doesn't include any external monitoring or data collection. But it does have an RS232 socket - Raspberry Pi Zero to the rescue! This is a scratch pad page for the project