Customer Support

Created by Polywork
724 People have this badge

What everyone's up to

Life long learner
Troubleshooting an issue
I encountered an issue while pushing my code from local repository to its remote version today. 

Here's what I learnt:


To repository
 ! [rejected]  local-repo -> remote-repo (non-fast-forward) 

error: failed to push some refs to '' 

hint: Updates were rejected because the tip of your current branch is behind hint: its remote counterpart. 

Integrate the remote changes (e.g. hint: 'git pull ...') before pushing again. 

hint: See the 'Note about fast-forwards' in 'git push --help' for details.


I found  an helpful article from GitHub docs from my Google search which can be viewed here

I hope you find it useful.
Sep 10, 2021
Deployed a Backend System
Troubleshooting an issue
Used Terraform
Wrote technical documentation
+ 2
Helped head of QA to deploy two microservices to new QA environments.

In future these services, which the team I am on owns, have their deployment documentation improved. 

This involved:
  • reading and fixing some terraform
  • using deployment logs
  • working with platform team and QA to ensure the services report as healthy
  • setting up third-party provider integrations. 
It will enable colleagues to deploy their branches for QA, prior to release in production.
Troubleshooting an issue
tfenv really helped my day to troubleshoot some tf provider issues !
Sep 03, 2021
last day of work
It has been a blast, Brightcove! 

Senior Software Engineer, Brightcove
Troubleshooting an issue
Managed cross-functional teams
In college, I misspent a few summers working as a Desktop Support grunt. I've always been hesitant to leverage this experience in my professional life—one, tech has changed a lot in 20 years; two, I don't want to be that developer, stepping out of his lane with flimsy-ass qualifications and the confidence of a Mediocre White Man™.

But for the second time this summer, I've managed to help resolve a security software issue with a basic problem outline and spot support in case comments from the IT team. Avoiding the need to remote-in (or even live chat!) has saved hours on both ends of the collaboration, and I think fostered trust and cross-departmental communication.

It's a good reminder for me not to hold back on bringing my full range of skills to bear at my Day Job—even when note specifically called for—as well as a nice moment to be grateful to work at a solutions-oriented company where open communication and low egos are the norm.
Front-End Developer, Otter Products
Started 27 days ago
Wrote a tweet
Creating a process for Tweet creation
Sharing a tweet
Software engineering
+ 2
I tweet on the Who Moves Twitter account about interesting articles, books, tips and more on various software development topics.