I empower people to become software developers, especially those with kids/family responsibilities, full-time jobs, or who feel too old to start over. 🥰👩🏽💻
Location
Washington DC
Education
Duke University | The Firehose Project (coding bootcamp)
Great question; my first-ever ticket was to set my development environment up, which was quite involved. My first contribution at work was to update the env-setup documentation :)
After that, I took tickets that involved small code updates, like HTML changes, or including a table column that allows an object to receive a new attribute. Most of what we code on my team ends up in front-end production, so I see the "fruit" of my work in a very visual way. Seeing my little changes reflected on our production sites gave my confidence such a boost.
I would say that, so far, my biggest trip-ups at work have been GitHub-flow related. Which is why I shout from the rooftops: "Get involved in opensource!!!" In my opinion, it's the closest you can approximate a professional coding environment, and it's great practice in code review, reading, understanding and modifying code, avoiding adding code debt, etc. If you're into Rails and/or JS, the Dev.To opensource project is just stellar!
Good luck!
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Joseph!
Great question; my first-ever ticket was to set my development environment up, which was quite involved. My first contribution at work was to update the env-setup documentation :)
After that, I took tickets that involved small code updates, like HTML changes, or including a table column that allows an object to receive a new attribute. Most of what we code on my team ends up in front-end production, so I see the "fruit" of my work in a very visual way. Seeing my little changes reflected on our production sites gave my confidence such a boost.
I would say that, so far, my biggest trip-ups at work have been GitHub-flow related. Which is why I shout from the rooftops: "Get involved in opensource!!!" In my opinion, it's the closest you can approximate a professional coding environment, and it's great practice in code review, reading, understanding and modifying code, avoiding adding code debt, etc. If you're into Rails and/or JS, the Dev.To opensource project is just stellar!
Good luck!