Best Practices of Spell Design
A tale of programming and software best practices from the Computational Fairy Tales universe. In all his years as a wizard, Marcus has never seen a spell cause this much damage. When Hannaldous's sloppy attempt at a shield spell accidentally curses the castle, the walls start crumbling at an alarming rate. Now Marcus and his apprentice Shelly must figure out how to repair the damage before the castle turns to dust. Along the way they will encounter gossiping worms, perfectionist bakers, opportunistic rabbits, and copious amounts of mold. The Best Practices of Spell Design introduces practical aspects of software development that are often learned through painful experience. Through Marcus and Shelly's quest, the story encourages readers to think about how to write readable, well-tested and maintainable programs. Readers will discover the importance of comments in recipes, the value of testing potions, the dangers of poorly named ingredients, the wonders of code reviews in magic libraries, and the perils of premature optimization.
What people are saying - Write a review
We haven't found any reviews in the usual places.
Agatha answered Marcus answered Shelly apprentice asked Marcus asked Peter asked Shelly asked the steward blueberry muffin bowl bread Breadista cake cast castle’s Chef Casserolii clerk collecting mold copy counter counterspell cursed debugging didn’t DoStuff dough elevator music explained Marcus eyes function Hannaldous Hannaldous’s spell happened heard hedgehog ID class ingredients Ivan Ivan’s kitchen magic Marcus and Shelly Marcus continued Marcus looked master librarian mess mime minutes mistake mock castle mumbled named constants never notebook off-by-one error parchment Pepperton potion Premature Optimization problem race condition ravioli readable recipe refactoring remember responded reverse the spell scroll Shelly asked Shelly felt Shelly looked Shelly started Shelly’s side effects sighed someone spell review stared subspell sure talks to worms test-driven development there’s thought understand unit tests variable Veronica waited walked wall What’s wizards wouldn’t write wrong you’re