Arlo Belshee

AgileEngineeringFluency. A model for undertanding the specific proficiencies involved in creating a good 2+star agile team. Initial draft presented at Agile 2013.

ArlosCommitNotation. A notation for small commits messages that show the risk involved in each step

SimulatableApi. Implements several simulators for common dependencies. These abstractions make it easier to write highly-testable code.

Collaboration. Creating a maturity model for collaboration. Help your team understand where it is at and what is possible.

PresentationKaraoke. Grab 6-200 of your closest friends and present random topics to the worst and most random slides ever created. Fun, and you just might learn something.

arlovsmocks. This project was created in response to a blog post by Arlo Belshee in which mocks were declared smelly. Its intent is to compare the strengths and limitations of code developed with and without mocks. The initial commit has been written in a procedural manner for neutrality. Interesting differences will be highlighted as soon as two opposing implentations have brought the initial commit to full test coverage. Anyone with a strong opinion on the necessity/smelliness of mocks should feel encouraged to contribute their own branch.

ArsEditorExample. A bunch of sample code that demonstrates ways to avoid mocks while still testing units

BlogExamples. More example code for various blog articles

PrintChar. A character layout tool for 4th Edition D&D characters. WYSIWYG editing for card-based character printing, with perfect fidelity from screen to print.

Presentations. A random collection of things I have presented.

GildedRose. A Kata to practice refactoring indebted code

SCIence. Scaled Continuous Improvement is an open-source methodology for teams and large organizations to make software more effectively. It incorporates learnings from Lean Startup, Lean, Extreme Programming, and other sources to find contextual solutions for common problems.

Contract.Annotations. Provides annotations for declaring the contracts in your code, in order to support enhanced static analysis. This includes all the JetBrains.Annotations understood by any published version of ReSharper.