// Code > Ideas > Experiments // http://cloudshock.dev
Nothing here yet.
Junior implies youth, which may not be accurate. Either way I think you should focus on your contribution to the team and the product, not your title. And please, please, please stop referring to yourself as a "Software Developer I". You are not a software package who will one day receive an upgrade. 馃ぃ
No. We have a saying on my team: "It's my first day" It's tongue in cheek, but there is a kernel of realism to it. Every day we are learning something new, regardless of how long we've been programming. There are no experts, and every day brings something new. It's why we love it, and why it stresses us out. Or to paraphrase Jayme Edwards (Healthy Software Developer), software isn't like building a bridge or stamping out widgets, it's knowledge work. It's impossible to estimate how long, or difficult, something will be because every project we are, hopefully, building something new or unknown. You are absolutely never too old to become a programmer. In fact, I'm sure you will bring non-technical experience, maybe about an aspect of business or a process or a role to the team that would otherwise be unrepresented by someone right out of college with a CS or MIS degree. YES, you CAN be a programmer!! Just remember to take it slow, keep learning, and make time to enjoy life!!
As others have said, learn a second language or work on a side project to combat coding burn out. It sounds counter intuitive, but in reality coders' brains are hardwired to solve problems. I find that thinking about a problem, that is outside of my day to day, is refreshing. It doesn't necessarily need to be a coding project either. Most of the senior DEVs I know have side hobbies like woodwork, games, puzzles, music, or even art and design. Each allows the mind to express creativity and solve problems without the deadline pressure and to do so on your own terms.
Paul, Great write up of the technical steps! I did something similar and used Hugo to generate pages based on mark up and deployed to S3 via a Github / Travis CI build process. For me, figuring out (and tweaking) the Hugo template system was the most challenging aspect. As a cloud platform I find AWS fairly straight forward, and the integration with 3rd parties like Travis are remarkably easy. Also you can't beat the free AWS Certificate Manager certs, especially now that Chrome wants everything to be HTTPS.
