Companies that encounter growth or change often struggle with how to guide this successfully.⁽¹⁾ Because the quality of a code-base mirrors that of the company, both need to be worked on.⁽²⁾ This is most effectively done by improving the two things connecting a company to the products or services they offer: 1. people and 2. the processes they use The quality level of code, developers, process and companies can all be measured. There are standards, models and metrics that can be applied to each one.⁽³⁾ More important than quality, however, is health. If an environment is not safe, a company not healthy or developers not happy, quality can never be attained. My primary focus is to instantiate healthy and sustainable changes that lead to improved quality of people, processes, projects and products. In order to do this, by necessity, I am involved with more than just writing code.⁽⁴⁾ If you are only looking for "more hands" to grow your organisation, we will be a poor match. If, however, you are commit to change, I can help achieve real growth and improvement by utilizing my knowledge, experience and personality.⁽⁵⁾ Want to know more? Curious about what I can do for your company? My colleague Sjoerd van Groning will be delighted to answer all of your questions. Feel free to contact him at sjoerd@muze.nl --- (1) For companies, conceiving and orchestrating change can be hard and, sadly, will often fail. There’s research that suggest that the success rate of major change initiatives is as low as 54%. (see http://www.strategyand.pwc.com/reports/cultures-role-organizational-change) (2): Conway's law (which states that the structure of code mirrors organisational structure) can be consideren proven since Baldwin, Maccormack and Rusnak tested the "mirroring" hypothesis in 2011 (see https://dash.harvard.edu/bitstream/handle/1/34403525/maccormack%2Cbaldwin%2Crusnak_exploring-the-duality.pdf) (3): Want to know how? Feel free to contact me here on LinkedIn or at https://twitter.com/potherca (4): Over the years, I have fulfilled various different roles. I have been a programmer, tester, software architect, evangelist, scrum coach, in-house educator, cultural broker and project manager. Besides software development, I have spoken at user-groups and (un)conferences, visited many software related events, co-founded a local user-group, dedicated time to numerous open-source projects and generally improved my skillset. (5): I have done this before at the companies I previously worked with. References of recommendation are available on request.