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
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
The harsh reality for JS Developers: If you don't study the fundamentals, you'll be just another “Coder”. Top learnings on how to get to the mid/senior level faster as a JavaScript developer by Dragos Nedelcu.
Avinash Kumar -
Leonardo Montini -
Chris Jarvis -
Adam Crockett -
Once suspended, devteam will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, devteam will be able to comment and publish posts again.
Once unpublished, all posts by devteam will become hidden and only accessible to themselves.
If devteam is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Ben Halpern.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag devteam:
Unflagging devteam will restore default visibility to their posts.
Top comments (24)
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.
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.
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.
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.
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.
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.).
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.