DEV Community

Discussion on: What is the hardest part of your job?

Collapse
 
grumpytechdude profile image
Alex Sinclair

Two jobs ago, the hardest part was holding to together from the stress. New requirements had to be delivered yesterday. We had no tests. More time was spent playing politics than working in a company of about 20 people. That company doesn't exist anymore.

In my last job, it went from learning how to Salesforce, to learning how to write good automated tests, to learning how to write good Sencha UI code, to learning how to write good automated tests, to learning how to write Capybara (selenium in Ruby tests), to learning how to support a team, to trying to change the culture, to finding a new job after three years of surprisingly unmarketable experience.

In my current job, it's dealing with clients while still delivering. They often want this, then this, then this - all while I'm still working on the thing before those! If I responded to every email with the depth I usually do, I'd have literally no time to work on features for them. So it's often in their best interests for me to delay in responding, or to give shorter answers.

Collapse
 
molly profile image
Molly Struve (she/her)

The client balance is always hard, you want to give all of them the complete answer but you simply dont have the time.