It doesn't have to be safety critical to be associated with flying.
I've written code for the aviation industry (fuel estimation programs, one thing you really don't want to mess up with) so I fully understand the ins and outs of that, but a pilots log book has already been mentioned and that would be a nice thing to start out with.
True, but you can still fuck up stuff without being DOA-178B (or whatever). My flight planning assistance SaaS example wouldn't be safety critical, I assume.
Just a warning of what to avoid...
Also, I'd personally hate to be responsible for some crash because my flight planning assistance SaaS had a minor, off-by-one bug in it somewhere, or misinterpreted "thar be tornadoes" for "light and variable winds".
(I am an embedded software engineer. I was also a private/instrument pilot.)