YoungBodhi

I was using disaster recovery as an example. The method is still applicable.

Let's use natural disasters. While reacting to natural disasters response teams must be able to communicate with each other, however communication is typically spotty during natural disasters. Your knowledge of software engineering will allow you to think of a solution to this problem and implement it.

Here's the process I follow, it's simple, but it takes time.

Get involved in an activity -> Become proficient in the activity -> Notice the places software would be beneficial -> Implement -> Product.

I've begun to view my software engineering skills as an amplifier instead of skill that can directly impact the lives of other people. By marrying your software engineering skills with another skill you possess you'll be able to create change quicker, and impact more people than someone without software engineering skills.