you may want to add, knowing how to read and support old code is important, fixing bugs and adding new feature to existing code base, most likely doing that in most job then building something new. could see what that like by doing this on a existing large opensource produce. Also, it's important to become comfortable with mathematics. I'm often surprised to find that many developers I meet either lack proficiency in this area or do not think it's necessary.

Hey! I get asked by high school kids about going into software, but it is hard to put all my thoughts together at a soccer game or a dinner. SO! This is my first attempt to explain how to get into software. Is it too negative? Too positive? I would love any help or feedback! Thanks!