Collaboration Code Diary Entries

This is part of the Semicolon&Sons Code Diary - consisting of lessons learned on the job.

• Be cognizant of local settings before trying commands on another machine
• Before setting up a system get client to trial it first
• Cc any developer affected
• Check original email when quoting
• Clarify exact versions when there is any ambiguity
• Code reviews
• Communicate when you will work next week
• Debug coworkers issues using their staging credentials if possible
• Deploy imperfect now if client insists on perfect
• Double check code when assisting teammates
• Ensure other teams get distinct test logins
• General tips
• Get the client to list preferred urls for each page up front
• If you are working with another developer to provision or deploy give version numbers
• Itemize estimations to your client
• Look over planned feature set before coding
• Never assume the bug is someone elses
• Never do in ENV files what can be done in config files
• Never remove a flow from code without consulting all potential stakeholders
• Not setting expectations that changes are possible only until cutoff time
• Professionalism
• Senior mindset book takeaways
• Shared screen is the fastest way to debug issues
• Specify project and branch and ENV when communicating
• Test code given by other teams immediately
• Test end to end before handing to client
• To write a good setup readme follow it through in a fresh machine
• Use predictable file structure
• When you modify code likely to cause severe conflicts communicate this