My job at this Company is to build tooling for them to test their models with. As well as build other miscellaneous tooling for automation, within Revit. Revit uses C# for their SDK, and for project planning Jira is our main driver.


My first time thinking about performance
Prior to this, performance wasn't really much on my mind, I was very much a person who chose to focus on just getting feature done and then on to the next one. This meant our tools slowly began getting slower. For obvious reasons. So when I finally decided to profile, it was very clear that a lot needed to be done. Luckily the program was already split up in a manner that allowed me to easily find the core issues, and focus on them, before moving forward.
