Skip to content
loading...
Discussion
markdown guide
 

5 servers in total, frontend vuejs to consume graphql api with jwt, backend laravel with graphql doing API, 400 workers processing 100k of requests day, doing web scrapping on 5 or 6 sources and communicating by pusher, mysql and redis.

all by me.

 

Recently when I realized every year that goes by, I am always ashamed of the kind of code I would write a year ago.

 

Ah the ole shame-to-pride maneuver. Keep it up!

 

I had at least a couple such moments:

  • About 10 years ago, when our first cloud application went into production. Complex distributed application which supports dynamic automated up/down scaling does not look regular even today.
  • About 7 years ago, when PoC we were working on passed all tests performed by customer and was accepted for creation of production version of the system. I've designed the architecture and leaded small team which implemented the PoC.
 

I've had a few little exciting peaks here and there including articles becoming popular, or people finding my github repos useful, but those tend to be really exciting for a little while but don't last.

The one that really sticks with me is from a person who reached out to me to ask for mentorship via the wonderful CodingCoach platform. They were so close to giving up on themselves and their dream of becoming a software engineer, but after working with them, they found their spark again, finished their learning and went on to get a job as a dev!

I was genuinely over the moon that I could help someone because I know what it's like starting out and it can be a tough, lonely road.

 

That's easy: contributing to open source and actually having people notice (and contribute back). A close tie is/was feeling appreciated on dev.to. I appreciate the culture and positivity that is fostered here.

Classic DEV Post from Jul 30 '19

PublishTo.Dev: Scheduling article publishing on dev.to

Ben Halpern profile image
A Canadian software developer who thinks he’s funny. He/Him.