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

For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is the third post of the Mayfield + DEV Discussion series. Please feel free to go back and answer previous questions as well.
For further actions, you may consider blocking this person and/or reporting abuse
Jean Santana -
Sloan -
Sloan -
Graham Morby -
Discussion (23)
I started my development career at my current company and I’ve had nothing but support from my line manager, he works with me on my career goals and I’m so thankful for his support, he gives me projects to challenge me and even though it can be tough it pushes me and I love it. It’s so rewarding in itself to have that support and it’s only made me a better developer. I then get to see my work live on our software and the proud feeling I get of what I’ve done is the best feeling 😊
Fully remote, flexible working, using my technical stack and a good team.
I think I can create pretty anything to solve my/others' needs is pretty amazing.
Help others 💙
Onboarding other engineers and coaching them to become the best versions of themselves.
Generally doing the work makes me better at the work — at a pace which will allow me to do more interesting things in the future. That reality can often be interrupted, but it's pretty rewarding most of the time.
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.).
I wanted to say "remote," but there are more and more people who can enjoy this configuration in their daily job, which is great.
To me, the most rewarding part is to face the difficulty and find my own solutions.
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.
Two things:
Getting the satisfaction after users/clients are very happy with the software you created. The "This is really amazing" gives me a lot satisfaction.
Getting paid for the job I do. We need to make a living in this world.
My paycheck I guess 😂
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... ☺️
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.
I get to work on building community building software with the community helping build that as well.
And with that altruistic motivator aside, I am able to work from home, have a nice salary, and am able to work at the times that work for me. This meant that we were able to foster puppies and then adopt one of them. And that means I've known her since she was 10 days old.
And with "me" focus aside, I have the opportunity to collaborate with folks both at the Forem and in the community; to interact with folks across the globe and share a bit of my career journey as well as learn from others.
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.
Hearing from users that what I'm working on is helping them ❤️
Recognition. And any feedback of my contribution.
Helping others succeed at their job.
Getting paid to learn.
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.
Teaching others and watching them improve
Working with my colleagues, who range from very smart to absolutely brilliant.
Leaving it on friday. At least i know i'll have two days without the corp draining the life out of me