This last month, Nathan Carver volunteered to lead a small group of us through the Pac-Man kata in C#. We had about 10 people the first night, which lead to a second, which lead to a third. This month, we’ll schedule it out for a month. We’ll try to code with a staff level engineer every Thursday night. Join slack.cantoncoders.org if you would like a specific topic covered.
This month’s feature presentation is Sylvia Fronczak as she presents the Transformation Priority Premise in Test Driven Development. We’ll also be hosting our normal lean coffees, and coding every Thursday night with a staff level developer. All event information is at events.cantoncoders.org and join our slack.cantoncoders.org for more details.
Come code with us! Checkout our code!
Back due to popular demand, come join with us.
A (Virtual) lean coffee focusing on elevating the new and growing developers in our community. About this Event As with other lean coffees, the topics will be provided and ranked by the attendees. The format will be slightly different – first the seasoned developers will use Socratic method to answer, but after 3 minutes –…
Read more
Contemporary Development Tools and Practices in the IBM Mainframe Environment About this Event About the Talk Since the late 1980s, much of the world outside of mainframe data centers has ignored the mainframe platform. Conventional wisdom was that it would soon cease to exist. Today, the mainframe is positioned as a viable and cost-effective cloud…
Read more
Fall in love with code again This month’s feature is Cobol Unit’s Author Dave Nicolette discussing Modern Mainframes. Checkout the rest of events, especially the reboot “New & Growing Lean Coffee”. And don’t forget to join our slack.cantoncoders.org and follow us on linkedin.cantoncoders.org .
How do you make your code more testable? One way is to make your classes smaller, so that they’re more directly testable. An easy way to do this is to look for the Primitive Obsession code smell and create new classes that better represent your domain than plain old integers and Strings. Then the magic happens: you’ll see behavior that’s spread throughout your codebase is Feature Envy, another code smell, and the new class will pull in that behavior, providing a better abstraction and an easier way to test it.
How do you make your code more testable? One way is to make your classes smaller, so that they’re more directly testable. An easy way to do this is to look for the Primitive Obsession code smell and create new classes that better represent your domain than plain old integers and Strings. Then the magic happens: you’ll see behavior that’s spread throughout your codebase is Feature Envy, another code smell, and the new class will pull in that behavior, providing a better abstraction and an easier way to test it.
Our community is approximately 8 months old and growing, and as we grow we are learning.
