Tech Stories To Read – January 14 , 2015 Edition

Here are the Tech Stories that I found interesting to read this week. It includes introduction to Puppet, a great site on Android Performance Tips, an article on how to design a login page and more. 

Check them out:

  • Introduction to Puppet : DevOps is all the rage and I do not see that dying down. Chef and Puppet are the names that usually come up. Take a look at an introduction to Puppet and what it can do.
  • Java Tools for Monitoring : If you have deployed a Java Application, the next things to make sure is that there is adequate logging, monitoring and debugging of your live applications. Take a look at this handy list of tools that you could employ today.
  • IoT has 4 Big Data Problems : A well crafted article that clearly highlights 4 key issues that this whole IoT will need to address effectively.
  • Android Performance Patterns : You cannot afford to write Android Apps that do their job. Just like UI/UX in your apps, performance is a crucial element that could kill your application before it can take off. Google has published a series of Performance Patterns videos to help you tune your Apps. Don’t miss this if you are into Android Development.
  • The God Login : Great article on rethinking the login process in our web applications. We take some of these things for granted but the article shows that little things matter and they eventually all add up to create a great experience for the user.
  • 10 Most Common Android Development Mistakes : The title says it all and a good checklist to look at. This is useful for beginners when charting out their Android journey. But make no mistake, experienced developers can gain by reading and following this too.
  • The Ins and Outs of Gradle : An article that covers just about enough you need to know to get going with Gradle inside of Android Studio. Shameless plug : If you are looking for a more detailed introduction, I suggest my series.
  • We Suck at HTTP : Yes we do ! In fact, we hardly even care beyond 4 things in my opinion (200, 404, GET and POST). But if you are into REST APIs, it is important to follow the best practices and make use of most of HTTP specification.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s