The Story: Rise like a phoenix

It’s best to have failure happen early in life. It wakes up the Phoenix bird in you so you rise from the ashes.

Anne Baxter

In this part of the story i will not talk about failures, because i don’t qualify them as failures. They are checkpoints that makes us change, either to be the best of us or the worst, it is up to us to turn the wheel and take the right road. A wise man once said, “The brakes in a car contradicts the purpose of the car which is moving, but this mechanical tool, if was not present, the safety of the passengers will be at stake. Thus the car would be far gone or it would not be used again”. Success always comes after failures, that’s why i called this part a phoenix, in order to be whole again, a phoenix must turn to ashes.

Aside from freelancing and doing various projects with different companies and clients, like Placeholder, Go My Code, La Planète des fournitures, Hexagon Mobile… I chose to keep teaching young people computer science during the weekend. As days pass, i started to grow a strong bond with students and the teams that form and fades. I’ve worked with people older than me, younger than me and the ones that consider them self “Minerva” Gods of knowledge. I never been a god of knowledge or would i be the person who knows everything, No human can do that but we should keep ourselves up to date and try to know the basics things in everything and specialize in the field that we love.

My experience as a developer, publisher, video editor, DevOps, architecture, design, UI/UX, security enthusiast, junior researcher, AI lover, project manager and task breakdown that i acquired from diving into various challenges was missing one thing. Bring it up to the world and use it. That’s when the instructor and freelancer kicked in, i learned how to lead a scaling team, deal with the unpredictable, deal with the painful client negotiation and communication. The last part became more easy through time with expertise. I became wiser and the incredible thing that happened is that i was the only survivor of all the storms than hit Go My Code. This would have not happened if it wasn’t to my flexibility and adaptability.

People say, its difficult to adapt, i say its always gonna change if it wouldn’t then time would freeze. Do what makes you feel good, challenge yourself and break the chains that ties you to the ground.

I’ve always been the CTO of the company despite that i got various titles i never cared about them and it wasn’t a dream. I just wanted to build things, maybe this time it wasn’t a software at first, but it was far greater than that. Building teams and knowledge sources is a great achievement, and as a wise man said “We teach our students and they teach us things that we could have never learned about”. I used my engineering skills despite i was a student, i never thought that engineering is thaugh in the school. I’ve learned about Fourrier Transform 5 years before i learned itin school, I've learned programming 3 years before i would know that they exist in the school, i’ve learned C#, 7 years before they could teach us that C# is C++++. The point is that school is necessary, but engineering is not school, engineering is in the heart and mind, a lot of engineers are out there but they are not doing what are they meant to do: “Design and Build things”.

I was the software engineer behind all of the technology that Go My Code uses, Though i was not alone. I’ve worked with Frontend developers, neuro-scientist and data scientists. I’ve been the manager and the front line code writer. I didn’t drop off the education thing, i constructed the creators program from the ground up, introduced the multi-levels course, the Ada model which is the first graph based knowledge representation backed up behind my Invention Krypton.

I did have the chance to write a Standard Operating Procedures and Emergency Protocols (CP-SOPEP), that list all the procedures and operations that must be performed by various executives that are part of the program. The guideline also foresees all possible risks and issues and proposes various solutions to mitigate them.

By the end of September 2018 and after going to Iceland, i realize that i have succeeded in my mission of building the base blocks of the program and other people can carry on this mission and it is finally the time to focus on the engineering part.

I had chosen to dedicate myself to my other position at that time “Project Engineering Manager” a.k.a “Another hidden nickname of GMCs’ CTO”. So i wanted to improve the product, make it shine and improve the learning model, after all the education part had become defined by the product.

As storms hit me, i still continue to walk on the same path, this would be in another part.

In February 2019, the CTO title was given, it is not a big deal, because i always believe in what i do? and what i get? those two questions complete each other to form a more consistent question: what is my impact on me and on others?

To be continued…

.NET Developer/Junior DevOps/Junior CTO/Experienced C# developer (