What is the most rewarding part of your job?

This is the third post of the Mayfield + DEV Discussion series. Please feel free to go back and answer previous questions as well.

Comments

[Nixon Islam]

Mostly two things,

1. The Aha moment of solving something.
2. Seeing a happy face, after figuring out their problems

[dallasapper]

The most rewarding part of my job (except for the salary) is communicating with the others and looking for new solutions together. The ideas that people come up with from time to time are absolutely brilliant, and I like listening to them.
It is what I like about our company: it is not only a way how to make an extra $1000 a month, but it’s also a place where students from schools and universities can share their ideas and work to develop them. They don’t have to spend a lot of time here in the office (not more than 15 hours per week), but it’s a good chance for them to become more financially independent from their parents.

[Jake Nelson]

Solving complex problems that effect hundreds of engineers. My work with has the opportunity to simplify developer experience and to accelerate engineers working with Google Cloud by a decent amount. Conversely, the not so great work I do is very obvious because of the large impact and highlights areas I can improve on.

[Duke]

Leaving it on friday. At least i know i'll have two days without the corp draining the life out of me

[Martin Himmel]

Most rewarding is helping non-profits raise money with our software (we do online auctions for non-profits).

Next is probably more red than green as far as commits go. I'm working on a nearly 20 year old code base, so, when I'm making a refactor type of change, I get a lot of joy out of removing more code than I add.

[Kasey Speakman]

It has changed over time. First it was the puzzle to get code working. Then it was trying to find tools/strategies to stop feeling like the whole application needs rewriting after deployment. Nowadays I enjoy supporting my team, which can be various things, mostly collaboration (design, peer coding, etc.).

[Gerard Klijs]

Helping others succeed at their job.

[José Aponte]

Two things:

1. Getting the satisfaction after users/clients are very happy with the software you created. The "This is really amazing" gives me a lot satisfaction.

2. Getting paid for the job I do. We need to make a living in this world.

[Eljay-Adobe]

Working with my colleagues, who range from very smart to absolutely brilliant.

[Souk Syp.]

Recognition. And any feedback of my contribution.

[Keff]

Seeing the app/website/software being used by real people and how that benefits them . Sometimes we can detach from that part as developers, but for me it's one of the most rewarding.

[Sandor Dargo]

My paycheck I guess 😂

[taijidude]

The moment when everything comes together and it works. Maybe you have been debugging for hours trying to find a hard to spot bug. The next moment you see it, facepalm yourself for a second. Say, yes of course and fix it.

Or when you have been working on a longer automation script ironing out the bugs and then comes the moment when the script runs completly without errors for the first time

Oh, sweet bliss... ☺️

[Lucas Perez]

I like automating stuff a lot. From creating some local helper scripts to bigger stuff like a new CI job, or making an old one better etc. And when these things pay off, when we get value out of it, it makes me the happiest. I really like working on my team's workflow and environment, and it is really rewarding.

Also, writing documentation and then using it days later also makes my day.

[Sam E. Lawrence]

Getting paid to learn.