Give me a mission, give me a vision and I will take up the rest.
If I have to work solo on a topic I am not afraid, as long as this will contribute to be a global benefit.
For the organization itself, for the colleagues or for the outside world.
If you believe on this, I believe on it too.
Inspire me, and you will get inspired from the outcome.
Working in Startups for most people is the fear of losing comfort in the long term.
I personally enjoy contributing in a thrilling environment.
I like to come up with new solutions when I see "a missing block". Most of the time I do this in my spare time ( after-work or on the weekend ).
Although I much rather prefer to invest this time at my Job. Because I believe working with someone is helping each other. The help is not only a one side communication channel.
Experimenting is in my blood, archiving perfection too. Restricting goals in time is something I also learned. I recognize limits, yet I prefer to squeeze the perfection in every product I work on. As much as I can.
Debugging is usually a task no one really prefers. This one is not me. I actually enjoy it.
Why? Because I believe that debugging is a learning process, a way to understand the limits of any argument that is related to the task
Let it be an argument, a topic, a technical tool, a knowledge area, whatever.
Learning to recognize the limits ( technically, conceptually or whatever ), helps on knowing where you can push further.
Working solo is not a problem for me, although working in a team makes my job more enjoyable. This is why I always prefer working in a team, rather than alone.
I don't mind differences of any kind, let it be culture, technological based or whatever. As long as we push on the same direction, I will be there.
I truly believe in the team spirit, I am ready to take responsibilities if I fail somewhere. Learning to fail, is the first step to get better.
Learn to fail, fail to learn.
Working with different set of technologies, makes you realize nothing is perfect. Instead you prefer to focus on what does solve your issue.
This is why I do personally not focus on a specific tool, but instead I focus on which requirement is being covered and how.
When I forge an architecture ( or look at one ) of any product, I always keep in mind my left and right side. Nothing is there casually. Everything must have a reason.
Actually, since I don't consider them a Skill, I use practically any OS out in the market: Windows, Linux, OSX, iOS, Android.
But If I have to say a preference, Windows is my favourite OS ( for Desktop usage, of course ).
While for Mobile I prefer Android for its freedom.