In the last 2 days, I have tried installing multiple Android Emulators out there on the internet. I will now start writing the review on those one after the other.
I would like to start this with Andy emulator, the one that had tortured me and literally harrasd me.

The biggest downsides of Andy are:

1. It took away a huge piece of disk space. It took 4.5 GB space.
2. Leave about eating away space, the biggest disadvantage is that it did not give me an option during setup to change the location of the installation. It by default installed everything in C drive. What the Heck! is this.
3. It took close to an hour to install on a machine that runs on i5 Intel, with 4 processors and an internet speed on 8GB. BS! a real BS.
4. I did not show what all are its dependencies. Half way through, it started asking me permissions to install Java Virtual Box softwares of multiple types. One more BS. This made me stick to my seat staring at my monitor.

I felt like i will puke (vomit) on my laptop screen before it finishes. Thanks to my mom, she gave me a needed break with a wonderful coffee. 

Visual Studio from Microsoft is mostly used as a paid one except for small application and demos that are done by people like us. For quick code snippets and tutorials, Visual Studio Express has been released a along with VS2010. From then on, Microsoft has been having an eye on the trends and developments in the market.
They have released plugins via their NuGet package manager for Node.js, CofeeScript and many others in the last few months.
After Satya Nadella became its CEO, Microsoft has predominantly been embracing open source communities. Their MVP now includes open source contributions as well.
They have recently released VS-Code editor that fits rightly for a right looking IDE for Node.js. Its light wait and installs quickly. It is a perfect one to develop ASP.NET with Node.js.
  

Ever wondered how easy it would have been as a developer to have something that previews your HTML code changes instantly?
Feels good, isn't it? Here is the answer to all those wonderful feeling - Its Brackets.io

Get a real-time connection to your browser. Make changes to CSS and HTML and you'll instantly see those changes on screen. Also see where your CSS selector is being applied in the browser by simply putting your cursor on it. It's the power of a code editor with the convenience of in-browser dev tools.

This is just an information article. I have tried using the editor and looks awesome and fabulous.

I was working on to puch my node application to heroku last week. Before we can push the code to Heroku, we need to have Git (not GitHub) installed on our machines with a valid SSH token. Git, to reiterate, is a version control tool.
So, when i said >git commit, this was the msg that was shown.
Q) What did i do?
A) inplace of the user.email and user.name, give a value that you think you can remember day in and day out!!!

$ git commit

*** Please tell me who you are.

Run

git config --global user.email "you@example.com"

git config --global user.name "Your Name"

to set your account's default identity.

Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got 'Obby@ObbyWorkstation.(none)')

We know how important it is to be internet social these days. A new communication trend that came into, has made everyone get in for some or the other reason.
Facebook has been leading the internet social scene from the days it got popular. the FB team picked up the tastes of its users and their love and what they want in their social sites quickly. With Agile all over, they are fast in releasing so many new features every now and then.
Twitter, another social networking site, has recently made changes to their user profiles that look very similar to FB. Now, LinkedIn has fallen in this line with change to their premium users profiles.

Have a look here.

During few Coffee time breaks in the last 2 weeks, we a group of 4-5 people have been discussing about Agile and one of my friend asked me -

what is that ONE THING, that is SO GOOD with AGILE that can made this methodology happen and work for so many.

 As always it was, we did have one of our friend supporting waterfall model.

 

image belongs to the respective owner

Here is (are?) my answer(s) :

 ü  Agile is all about developing a part of the application in iterative cycles (sprints). 

ü  At the end of the sprint, a minimal deliverable product that is part of the actual application is delivered. This means, a team or an individual is not dealing with too many things at a time.

ü  When it comes to the manager’s point of view, it means that he or she can see what is going good or what's going bad with the development strategy is. 

ü  When it comes to the owners of the product i.e., the  higher management, it gives them an opportunity to look at how the current application is, assess against the odds on how it’s going to fare.

ü  Show it to the stakeholders or potential customers and get the feedback from them and work again on the application to do what matters the most to the end user.

In contrast, Waterfall is all about collecting all the requirements and executing them over a long period of time and then delivering them. You never know, when the priority of the consumers is going to change.

Before we start talking about Agile, I had an interesting talk with my friend about the posts of my blog here. He says that a lot has been talked about code, clean code, best practices, C#, Agile and what not there are too many people with an experience more than my age!!! So he concludes that i was trying to re-invent the wheel.

My answer was simple and straight forward - I understand and I know there are many of them here. Yet, probably I have the ability to put things very simple. I believe that my posts can reach to those who are looking for things that are told in a little easy way.

If we do things which are for a better than the existing one, its always good and its always new. This only means telling the story more cleanly and clearly with a new additions.

See you next week with Agile Methodology :: Episode 5