Ashley Shultz Email & Phone Number

I tell computers what to do, and sometimes they listen.I’ve been programming professionally since 2016. I’m a self-taught programmer; I first learned Python to hack a midi-controller to use with a music program called Ableton, and have continued to use Python in some capacity at every job I’ve had as a professional developer. While I’m most comfortable with Python, I also have used JavaScript, GoLang, Bash, Java, and other languages for various applications throughout my career. I believe in writing well-tested, reusable, and readable code, which is possible regardless of the language used.I currently work remotely as a “Lead Software Engineer,” which means I spend my day writing code, doing code reviews, proposing architectures, prioritizing new features, mentoring teammates, conducting 1-on-1s, “putting out fires,” parsing technical requirements from upper management and the legal team, and generally just trying to solve whatever new challenges manifest themselves. I’ve spent most of my career working at startups where my job description might change week to week. While startups can be stressful, I enjoy not being bored. I look forward to whatever challenges the future may bring.Random Opinions:- Functional Programming > Object-Oriented Programming- Simple > Complicated- Monorepos > Polyrepos- Any formal process that does not increase output should be discarded- They call it a "sprint", but developers actually run marathons- Discussing the "points" needed to create a feature does not make the feature any more reliable, better documented, or more thoroughly tested- "Agile" does not mean you get to skip the planning phase of development- Curiosity and humility are essential for continued growth in the development field- Unit tests should be written by the developer who writes the feature

Listed skills include Python, Javascript, Nodejs, Testing, and 40 others.