On my lunchbreak, I was trying to explain to my co-workers what I get out of blogging about code I am writing at work.
You know the expression, if you really want to see if you know something, try describing it to someone else?
That's why I blog.
Software development is brand new to me. It was scary when I first started. I was completely out of my comfort zone. But it got better.
What I am learn at work has been a good foundation. There, I learn about the what, and the how.
It isn't until I start organizing my thoughts, creating a blog post, do I figure out the why.
- How did the software development process I am using take hold? Who first blogged about the concepts I am using? Was it Kent Beck? Martin Fowler? Simon Stewart? Jim Evans? Uncle Bob?
- Who made the toolset I am using? When did it become adopted? Is it industry standard?
- Although I may not understand it, where on GitHub is the open-source code? Can I understand how their project is constructed? Are there unit test formats I can borrow for my automation development?
Through blogging, for me, comes understanding.
And that's my thought of the day!
-T.J. Maher
Sr. QA Engineer,
Fitbit-Boston
// QA Engineer since Aug. 1996
// Automation developer for [ 1 ] year and still counting!
// Check us out on Facebook!
No comments:
Post a Comment