JLamch

When I started to work with Azure everyone told me that's there are two ways of creating things with Azure one way PaaS another way is IaaS . So what's the difference and what it is in the first place? PaaS is the new way of making things and IaaS is the old way, what do I mean by old ways. Well long, long time ago there where desktops, and some times there were Virtual Machines working on desktops, it was pretty simple because virtual machine was almost the same as normal with the difference that it needed additional software to run and wasn't physically connected to hardware rather with proxy application like Dropbox or VMware or any other. So IaaS is the same but on a could. IaaS is a VM with all needed stuff somewhere in data center available for me via internet. It's Infrastructure as a Service (Iaas). It's not only VM but IP address and other network related stuff I don't know too much about.

I'm going to create simple build with different test frameworks the repository is already available on my GitHub . So Vsts will contain build definition and GitHub contains the code. I need to make a connection between them.

GitHub is great. I have a GitHub account and I'm planning to share all source code for this blog on GitHub, especially that public repoes are free on GitHub. But I also have a Vsts account, well to be honest a few of them for different purposes, but in the end one is my main directory and others are just for fun, experiments or other strange stuff. Why I don't have all in GitHub? Vsts has no capacity restriction on it's content so I can have everything there, and the most important detail is that Vsts is free and it is private. No one not-invited can see my code collection, and not all code should be public. I also store file like old emails that felt right to be archived somewhere, or some documentation file related to very old projects like my master thesis (this really should not be seen by public anymore :D ). This is my private space for all my code at least since 2012.

There's always a story to tell behind the stage, and this is one of many why I like VSTS ( Visual Studio Team Services ).  Recently I was working with a client trying to find the best cloud architecture for their project.  The small problem was that they we're writing in Java and I am a Microsoft Technology Stack, so the first problem I encountered was how to start because I know 'something' about cloud and azure but I don't know how to proceed with web applications wrote in Java. The easiest way is to Google something... but Googling something isn't enough because you can Google only the source code and you need something up and running ready to show.  The running something is the biggest problem here - how I can build Java, how to test it. So I have some skills in DevOps in VSTS, i love VSTS and i like creating Continuous Integrations on it. 

I never had a mentor or even a person that believed in me. Well not never ever because I'm talking about first five years of my commercial job. After those five years I found friends, allies that at least where on my side.

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