A typical day at Workplace 2020

Everyday is unique at the workplace. Each day, you solve different problems at work. There are some aspects of the job that may remain the same. Eventually, the work you do defines us. It tells what kind of workload you can handle, how an effective employee you are on a daily basis, how enthusiastic and passionate you are at work, and how much work oriented you are.

  • attend morning standup with co-workers. Plan work for the day.
  • proactively raise issues or impediments found.
  • analyse, debug, and fix defects.
  • read and understand product user stories and customer requirements.
  • record analyses in the JIRA tickets.
  • help product owners and defect managers in analysing user stories and defects.
  • attend meetings and actively contribute ideas on solving technical problems.
  • ask right questions at right time to get responses from the right people.
  • put forth technical solutions as proposals to productt architects.
  • read, understand code written by other developers.
  • write code and unit tests.
  • learn actively as you code.
  • test code against mock data.
  • test code against the given specification.
  • verify code against specific customer environment by building and running docker containers.
  • share screenshots or screen recording as a means to verification.
  • ensure that there are no build failures at local or remote Git branches.
  • review code thoroughly before raising a pull-request to minimise further changes due to reviewer comments.
  • raise Pull-Request(s), monitor for feedback or comments, and resolve the comments at the earliest possible.
  • raise Pull-Request(s) to release branches where the content might be old (cherry-pick & resolve merge conflicts).
  • resolve merge conflicts in Pull-Request(s) by rebasing developer branch with latest code from the master branch.
  • follow up with reviewers for approvals on Pull-Request(s)
  • send Pull-Request for further Quality Assurance check or peer-review
  • verification before merging the code to main branch.
  • report any defects found to the product owner.
  • take responsibility for any mistake or defect introduced by you and fix them immediately.
  • fix build failures, if any.
  • review code and give feedback.
  • help other developers in removing their obstacles (but not to spoon feed)
  • deliver committed work for the day.
  • a brief review of work done with the team at the evening.