Weekly Links #4

Top Links For 26/2-3/3:

  1. A great article by Zach Holman about how to deploy software. He gives some methods for ensuring the quality of the code before the deployment, explains some different types of deployments,  shows some tools that can be used during the deployment itself and describes some checks that need to be done after the deployment is over.
  2. Every developer is specialized with some programming languages. It is important to be familiar with the building blocks of the language. A living example on C# is the post of David Belmont about building lambda expressions dynamically. Most of C# developers use lambda expressions on a daily basis, and this is a good opportunity to learn how it is constructed behind the scenes.
  3. All the developers which consider themselves serious, must stay updated and constantly learn new things. Karloine Klever gathers some tools for improving your skills. This is actually the second part in her series of “upskilling your upskilling skills”, and you can read the first article as well from the link above.
  4. Loose coupling is a basic concept in system design. It means that the components of the system should be independent of each other as much as possible. In the following article of Peter Vogel, he explains this concept and give ideas how to make code more loosely coupled.
  5. Here are some leadership tips from Andy Hurd, which are based from his experience as a first-time manager. I agree with most of his ideas. I think that his point of “being prompt with difficult conversations” is extremely important. When we identify a problem, we should handle it as early as we can and not to avoid from doing this and let it grow.
  6. Abstraction is a key concept in object-oriented programming. We use it in a lot of problems, while there are cases when abstraction can be harmful, as this article, which is written by Tyler Treat, suggests. It is important to be aware of the weaknesses of abstraction, and yes, something violation of DRY(Don’t Repeat Yourself) is preferred to forcing of  not suitable abstraction.
  7. So after Microsoft acquired Xamarin, it is really a good time to know what is Xamarin, in this informative post of Julien Fiaffé.

More Quick Refs:

  1. Visual Studio – Debugging Improvements in Visual Studio 2015
  2. .NET Framework Compatibility Diagnostics
  3. Do You Know These Eight HTML5 Tags?
  4. A Quick Study of the Rails Directory Structure
  5. Five Practices for Robust Ruby on Rails Applications
  6. Unit Testing Allowed Me to Pick Up My Kid Today
  7. Constructor or Setter?

 

Advertisements