Starting point

It is not easy to start. To get out of your cozy little closet or basement, especially when you are an introverted developer always feeling phony about yourself. 
And it really doesn't matter that everyone tells you that you are good, even special and you know so many things that other don't know. It doesn't really feels like it 

And it doesn't help that you have a lot of experience in a lot of technologies. Well lot of experience even make it worse because you always think that other don't need this knowledge. You always think that you don't have anything to share. It's hard to find a topic it's hard to find a worlds and it's just hard to speak. 
So why even bother, why trying? Isn't it good enough like it is? 
Well it's not its very hard world. And it's good to know something more than just technologies or language. It's good to get noticed.
And it's good to know how to learn from others and how to teach because when you are teaching you are learning the most.
I had a pleasure lately to become a mentor. It's nice to teach, it's nice to help somebody else in their way to improving themselves and by teaching I also learned a lot myself and I gain so much energy and so much good emotions that this exceeded all my expectations.
So maybe writing will be also fun and maybe it would help me to break my biggest wall, overcome biggest limitation, barrier in my mind - that is speaking to the audience because I would like to do it and I don't know how.

Popular posts from this blog

Azure post deployment scripts

Image
Let's do a trick. After deploying application (that was easy with Ftp or Git ) it would be nice to take some action. For example send an email, or write release notes to release page. I will do much fancier thing - I will write some text to console output.
Read more

Mobile view lifecycle. Fixing Xamarin.Forms Page lifecycle

Image
For mobile applications the highest priority is user. What user can see and interacts with. Application should react not only on user interacting with it but also user interacting with operating system. That's why not only application has it's own lifecycle but also "view" has it's own lifecycle. In Android view is represented by activity, or a fragment (the right side of android diagram). In iOS view has it's own set of lifecycle methods. In both cases view has the information that application(in this case view itself)  is being suspended and reactivated. View know quite a lot about outside world and view lifecycle is very similar to application lifecycle. Compare below first application and then view lifecycle diagrams: In Android view is represented by activity, or a fragment (the right side of android diagram). In iOS view has it's own set of lifecycle methods. In both cases view has the information that application(in this case view itself)  is...
Read more

Mobile application life-cycle Android vs iOS vs Xamarin.Forms

Image
Lifecycle. One of the most common recruitment questions. No matter what technology you work with this is something that should be well known and understood. It's good to know how application behaves, what it is allowed depending on its state and when to react on specific lifecycle events. In mobile world lifecycle is even more complicated because there is no 1 answer but 3 in this case: Android. iOS. Xamarin.Forms. I use also Xamarin.iOS event names in my diagrams, but the sequence is the same. Lifecycle is the definition when your application have access to resources and when react on state change. For mobile the biggest priority is what user can see and interacts with, so active application have priority in using system resources. System has limited pool of resources, so  applications running in background (not visible to user) is limited by system in how much resources can it use and also system decides when application needs to release all resources (be closed/killed/end o...
Read more