Last week, I pushed code to a shared repository. I did it with trepidation; it’s been a long time since I worked on a collaborative coding project. 

There’s a lot of difference between working on your own passion projects (that may or may not see the light of day), and working on something with someone else for public consumption with the knowledge that some other developer might take over the code someday. 

One, it requires you to understand code that someone else wrote and while developers with more practice might find this easy, my code literacy is unpractised. 

Two, you have to write code in a way that makes sense to someone else. Your variable names have to be verbose, you should include comments. Your commit messages have to say more than “make edit”. 

Three, the edits you make could affect the entire app, affecting the work that your collaborators have done. 

I only made a single front-end (cosmetic) change to the app, but there was fear as I typed “git push” and prepared to press ENTER. 

After pushing, I realised that I should have pushed to a branch instead, and after that requested a merge. 

My heart pounded. Nothing will break, my rational mind said. And even if it does, there are ways to fix it

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s