Summary

If you're wondering what you'll get from hiring me in your team, here's a two-fold overview of myself that focuses on:

Developer profile

I would say that I'm a backend developer ...

... who did a lot of frontend work!

The more I work, the more I tend to prefer spending time on the backend side of things.

In my daily work, I create both. My side projects however are nearly only frontend stuff! You can discover a few of them here.

I don't consider myself ultra knowledgeable in frontend nor in backend. However, I do think that I have serious foundations in both fields. As well as on the DevOps side.

I'm comfortable:

Attitude

When I write code, the first thing I have in mind is people.

I want my code to be as comprehensible for others as if they were the ones who wrote it. That's why I constantly seek to write short, simple and readable code.

Even though my former focus is other people when I build software, I always value and consider my very own opinion on the things I plan to build.

If I judge that what I have in mind would ease everyone life in the future, I'll do speak up to make sure what I think is good for the whole really is so.

Interests

When a project I took part in progresses to a point where novel knowledge is created, I always make sure that new bits of information are documented, either by me or my peers.

Speaking of documentation, I love writing it. Really.

I do understand how valuable it is and, thankfully, my love for writing always makes me enjoy crafting it. Even those my coworkers procrastinate (or simply refuse) doing are ones I enjoy creating.

That's how strong my care about future people well-being is.

I would not feel pleased if any team member (even those I'll never have the chance to meet) has to suffer from a past lack of motivation from writing documentation.

I'm also very customer / purpose centric.

In the sense that I don't simply code the tasks that happen to sit in my backlog. No, no! I always keep the bigger picture in mind. It translates into me constantly considering how meaningful the feature I'm working on is likely to make the boat cruise forward.

It may sound cliché but, of course I like clean code.

It may have to do with my love of offering collegues bits of work that they will enjoy working with, or because I simply truly care about my own sanity when it comes to building something that will not crush my brain weeks after I made it.

Or simply that I seek mastery in my craft.

I know that mastering the art that programming is requires much more than following best practices or applying the right design patterns when it makes sense to do so.

It may also have something to do with the next point...

I love refactoring.

To a point that I can be satisfied by working on a refactoring project for months without doing anything else.

For some reasons (seeking mastery of the craft?), I simply am so passionated about coming up with simpler and simpler solutions, structures or ways to write things to projects I already built.

On, the people-oriented side of things, I thrill when performing refactor over any codebase. In this case, I convince myself that what I just did will offer an easier introduction into the given project to any dev that'll join it or currently works on it.

Aspirations

Currently, my career-related goals are multifold.

Tech ones

I want to soak up knowledge about how software is thought of, made and maintained behind the walls of the biggest industry players.

As I'm a very thougtful as to how I write software, I'm constantly improving my software architecture skills and always thrive to make code simpler to understand, maintain and such.

Once I'll feel comfortable with all the best practices I'd garnered and the experience I'd acquired, I'll focus on sharing all of these.

Teaching, is a discipline I'm extra fond of. And I want to transfer my hardly gained knowledge into simple, funny and easy to digest lessons.

This way, people that also crave learning how software is crafted and taken care of, will also be able to trench their thirst from my materials.

Non-tech ones

The more I work, the better I learn about my job — of course —, but also about myself.

What I recently understood is that I love empowering people as well as writing clean code and everything that gravitates around that.

This made me understand that using my technical skills to help people succeed in their endeavors is something that truly fills me.

Also, I read people pretty easily and have quite an accurate sense of predicting human behaviors. This helps me foresee issues before they get real and I use this to defuse any seed of what may actually become a real issue.

I usually abuse this skill to constantly reach my number goal when it comes to working in a team: maintain a healthy climate with the people.

This leads to better work and personal relationships, as well as more throughput for the organization, which is also something I constantly have in mind.

Want more than a simple overview of my skills?
My skills page is what you're looking for!

Gregordy