Photo of Amine crossing his arms and smiling

Who Am I?

Hello there! It's great to see you here. If we haven't met yet, I'm Amine. Some may label me as a developer, coder, programmer, or Software Engineer. But my favorite title? Product Engineer with a touch of Web Artisan flair. 🤓👨‍💻🚀 My passion? Crafting web apps using the vibrant tools of Javascript, Typescript, React, and Next.js.

My story so far...

For over a decade, I've crafted code professionally. I started my journey at consulting firms, developing software mainly for large enterprises using Java and ColdFusion. When Angular.js emerged as the trending framework in the JavaScript arena, I was captivated and promptly pivoted to an all-JS approach. Since then, I've contributed my expertise to diverse projects as a contractor. Currently, I'm a member of a hypergrowth startup, shaping the future of work.

Values I live by…

In both my personal and professional life, a core set of values serves as my guiding compass and shapes what I value in the workplaces I choose:

  • - Ownership: Taking responsibility and leading with initiative.
  • - Excellence: Striving for the highest standards in every endeavor.
  • - Humility: Recognizing the importance of continuous learning and valuing others' perspectives.
  • - Transparency: Embracing open communication and authenticity.
  • - Respect: Honoring the dignity and worth of every individual.

Principles I follow...

In my pursuit of mastery within my craft, I've been inspired by philosophies such as Zen Python, among others. These core principles define my approach to solutions I create:

  1. 1. Clear is better than clever.
  2. 2. Simple is better than complex.
  3. 3. Explicit is better than implicit.
  4. 4. Done is better than perfect.
  5. 5. Done is when users can use it.
  6. 6. Make it work first, if necessary, make it beautiful, if you really need to, make it fast.
  7. 7. Above 100ms, it does not feel instantaneous anymore.
  8. 8. There should be one - and prefebly only one - obvious way to do it.
  9. 9. If the implementation is hard to explain, it's a bad idea.
  10. 10. Errors should never pass silently. Unless explicitly silenced.