Professionalism

This is part of the Semicolon&Sons Code Diary - consisting of lessons learned on the job. You're in the collaboration category.

Last Updated: 2024-03-02

Test links in incognito mode before handing off to client

E.g. for Google Docs etc.

This can reval access problems early

Always download all artifacts of a coding project to your own machine.

In Project T, I used Paperspace to demo a machine learning model. About a month later I wanted to make a web endpoint out of this model. However, when I logged into Paperspace, the location at which they stored my pre-trained model was inaccessible for the day, meaning I was blocked.

Always check for JS errors in the console before calling a bug done

There is often something lurking

Proof read every commit and PR before submitting

Often something is lurking

Test every change

As in don't change a file and assume it works. Very by running the code

In many codebases, this might even mean manually.