Thanks . Just surprised that it was the top voted comment . <| sep |> I ' d go with cherry browns or blues . Blue are more clicky and louder <| sep |> I ' ve got a bit of a more advice type answer for you . We are having some trouble understanding exactly what you are trying to do . This tells me that you yourself may not be totally clear on the task itself . So before you even attempt to change anything , create a problem statement what is the problem you intend to solve ? Shits all fucked is the most common problem statement I hear at work , but you might want to go a bit deeper . Once your problem is understood , generate concepts that would solve the problem . ' Codify ' might be the perfect solution , but we don ' t understand what you mean here either , so you should define it better . Review your problem and solution with peers and possibly supervisor . I recommend writing stuff down in general , but don ' t bother showing others the paper for simple stuff . While you are bullshitting with the team , one of the solutions will probably seem like its the best , so your concept selection is pretty much done . More complex problems require more complex decision making tools . And arguing . Gotta have a hefty dose of argument . Anyway . Create a Scope of Work . Write down what stuff needs done to complete the selected concept . Not a perfect one , but an outline . Decide who will perform the work don ' t be surprised if it all can ' t be done by you Now you can get approval to perform said work before you get halfway thru and you realize you ' ll need to pay for some welding that can ' t be done in house . Execute . Document it . There ' s common steps I skipped prototyping , process introduction , ect . But thats a rough outline of projects . Super Rough , don ' t kill me guize .