by Natasha Carlyon | Jun 6, 2018 | Agile, Quality code
Software design is hard. Although getting the software to work is essential, it is also important to keep in mind the design of the software. Rules The four rules of simple design is an excellent guide to designing software. Kent Beck discovered the rules while he was...
by Leah Wynn | Apr 16, 2018 | Agile, Apprenticeship, Quality code, Software, Software craftsmanship, Unit testing
To follow up with my last blog post, I am going to talk about how to get started writing unit tests. In my last blog post I talked about what a unit test is and why unit testing is important. If you’re ready to start writing unit tests, read on to learn how we do...
by Natasha Carlyon | Mar 27, 2018 | Agile, Growth, Learning
This is the conclusion of my Retrospectives series. Set the Stage Gather Information/Generate Insight Take Action(the current blog post) Take Action After generating insights, the team works together to create a list of actions items. This sounds simple enough;...
by Leah Wynn | Mar 21, 2018 | Agile, Apprenticeship, Learning, Quality code, Software, Software craftsmanship, Unit testing
This blog post is the first part of a two-part series on unit testing. The second part is posted here. My inspiration for writing about this topic comes from leading and helping to facilitate several workshops and events as part of my time here at Greater Sum. One...
by Natasha Carlyon | Mar 6, 2018 | Agile, Growth
This is part two of my Retrospectives series. Set the Stage Gather Information/Generate Insight(the current blog post) Take Action Gather Information This is possibly the most diverse step in the retrospective. There’re so many different ways to gather...
by Natasha Carlyon | Feb 11, 2018 | Agile, Growth, Learning
Retrospective comes from the latin word ‘Retrospectare’, which means to look back. In the software development world, retrospective refers to a team meeting together at regular intervals to reflect on past work, usually just a week or two. I’m a deep...
