I was promoted to Leading Software Engineer in recognition of my new role as head of the OrthoModel development team.
This role involves:
- Managing a permanent team of 4 software engineers including myself.
- Managing temporary team members. These are graduate rotations and members of a project based team.
- Responsibility for the technical and functional quality of the OrthoModel product.
- Working with the commercial team on the direction and strategy for the product.
I work as a sailing instructor at the Medina Valley Centre for some weeks each summer.
This has taught me the following things :
- Teamwork both leading groups and supporting
- Enhanced my presentation skills through teaching in a
- Taking responsibility for the welfare and safety of groups of
Allowed me to develop the ability to act calmly and rationally in emergencies
I was promoted to Senior Software Engineer in June for my technical contribution to the Delcam OrthoMODEL team.
This has involved;
- Assuming more of an architectural infrastructure role in the team.
- Taking on supervision of graduate rotations, and being responsible for a remote developer in Russia.
Began as a graduate software engineer, rotated through 4 different departments; Exchange (file conversion), Dental (CAD for tooth restorations), PowerMILL Algorithms (world-leading computer aided manufacture software) and Orthotics (CAD for custom orthotic insoles).
I now am a permanent software engineer working in the orthotics team.
Projects of note: working on a decompiler, working with scanning hardware, dynamic slicing of a model, moving duplicated .NET code for view models into a native language.
3rd year History Project: "The Cardinality of the Real Numbers"
4th year Masters Thesis: "The Axiom of Choice and the Banach-
Mainly focused on Pure Mathematics, but enjoyed computer based modules.
Languages the developer has proven experience and proficiency via actions taken on linked accounts.
Environments the developer has proven experience and proficiency via actions taken on linked accounts.
Frameworks the developer has proven experience and proficiency via actions taken on linked accounts.
Tools the developer has proven experience and proficiency via actions taken on linked accounts.
Skills the developer has proven experience and proficiency via actions taken on linked accounts. Actions can be source code shared on GitHub, answers given to question on Stack Overflow, packages shared on NuGet, courses completed on Treehouse, and much more.
Combination of verified skills and skills the developer has expressed an interest in via information on linked accounts. Interests can be from watching source code on GitHub, Meetup group categories, listed skills on LinkedIn, tags used on Forrst, and much more.
The core traits the developer exhibits through actions taken on linked accounts.
Code repositories the developer has created, owns, or administers. In some instances forked or cloned repositories will be included as well.
Code repositories the developer collaborates on by maintaining, developing, and commiting code. In many instances the developer is a member of the team responsible for the repository.
Code repositories the developer has forked or cloned in order to support development. In most cases changes are made to the supported repository through pull requests.
Code repositories the developer watches or follows driven by an interest in the repository, source code, or functionality.
Code snippets the developer has created and owns.
Educational courses taken in order to increase knowledge of software development skills.
Articles read in order to increase knowledge of software development skills.
Articles written in order to educate and help others in the community.
Answers given to community questions in order to educate and help others in the community.
Presentations created and shared in order to educate and help others in the community.
Recommendations about the coder by peers, supervisors, and others from the community.
All the badges earned on coderbits.
All the badges earned on other sites such as Coderwall, Treehouse, Channel 9, etc.
The teams, organizations, and groups the coder is a member of.
The full history of actions taken by the coder.