Happy new year! It seems like good time for a Quality Coding retrospective. I also want to share some goals for 2018.
…Did someone say, “Are you writing a book?”
Subscribers
In 2017, Quality Coding crossed over 2,000 subscribers! (Are you one of them? All subscribers get my test-focused code snippets.)
…Crossing the 2,000 threshold also means I graduated out of MailChimp’s free program. This means I’m incurring regular costs to send out email updates. So, I’m looking for advertisers to help support this site. If you have something to advertise, I’m running a New Year’s sale: 40% off through February!
[thrive_link color=’blue’ link=’https://qualitycoding.org/advertising/’ target=’_self’ size=’small’ align=”]Learn More about Advertising[/thrive_link]
Site improvements
I invested in various improvements for this site:
- A new look, including more readable code samples.
- I moved to a new hosting provider. Main goal: better speed for you.
- Spent money on a more robust optimization plug-in. Again, for speed.
The site feels snappier to me. Does it feel faster to you? I’m continuing to experiment to see what investments make a difference.
Besides these speed improvements, I also invested in a new comment system. You can now up-vote comments! By default, up-voted comments will appear first. …So give a thumbs-up to the comments you find helpful.
TDD workshop
2017 brought some new things to my TDD workshop:
- For the first time, the workshop went outside of conferences.
- Expanded from one day to a 2-day format.
- I created a 17-page reference guide for participants.
I’m eager to bring this workshop to your iOS team. To that end, I’m running a New Year’s promotional sale here, too: 40% off bookings made through February! That is, you can schedule a workshop any time during 2018 …as long as we make the arrangements soon.
[thrive_link color=’blue’ link=’https://qualitycoding.org/services/tdd-workshop/’ target=’_self’ size=’small’ align=”]Learn More about Workshop[/thrive_link]
About that book…
Over the years, folks have asked if I would write a book. In my 2017 Reader Survey, I learned that many of you were interested. …But what should it focus on?
That’s why I recently ran another survey to learn about your greatest pain points when it comes to iOS testing. Thank you to everyone who participated! I spent time during my Christmas break reading, analyzing, and categorizing your responses.
Because I want to make sure I write something that will help you in your testing struggles.
Writing a book is a daunting idea. But I want to give it a go. Here’s to 2018!
