At least 3 out of 5 electronic goods do not work at peak performance for 5 years without a repair. Many open-source repositories go unmaintained after a few months of activity. What if every engineer takes an oath to develop products that run till the end of the earth without a major outage? What system design decisions and quality benchmarks would be needed to achieve a long shelf life of the hardware, software, services, or firmware product? Let's discuss it.
Back in 2015, I was reading the book Remote, office not required by Basecamp and it felt like a distant dream to work from home (WFH) even though I worked in the tech industry as an independent contributor. Due to the pandemic, almost overnight the IT employees became accidental WFH professionals. It was a good choice because the infrastructure inside and outside the office was built around the concept of Social distancing. Back to the topic, I have tweaked and adapted to my WFH lifestyle, I have enough maturity to establish the process at the new location. Download my checklist for WFH in 2021.
It's very rare to see software without issues and development teams with fit & healthy individuals. Rampant operations issues, longer meetings can take a toll on software teams and their health. Here are 6 actionable tips which you can follow to keep up your software team's health.
Having spent a couple of years at graduation school aka college~~~~, we have learned a few good lessons which are applicable in real life too. Here I summarize 3 of those tips along with one lifesaver tip.