During my career, I’ve worked at various organizations that had different stances toward open source frameworks and tools. Some of these organizations absolutely did not want anything open source near their code base. Others had a small set of “blessed” open source frameworks we were allowed to use. Some of the better places I’ve encountered, had a process for approving and documenting the use of new open source libraries in the code base.
The reason for this is that organizations tend to recognize that using an open source library comes with a certain amount of risk. Their goal is to manage the amount of risk they are taking on while developing software. The risk of using an open source library usually stems from the license of the library.
Let’s start with the 800lb gorilla in the room, Java. Why Java? Well, let’s start off with the fact that it’s got a ton of community support and documentation everywhere. If you Google a programming problem, chances are within the first three results you will see an example using Java. There is also a plethora of amazing editors available. A good editor is not a replacement for knowing the tools available in a language, but it can help you in learning.
One of the tenets of the agile methodology is feedback. To provide value to your customer, you need to know that what you are delivering is correct. But as an agile coach, I often struggle with teams understanding the importance of getting feedback from the customer as soon as possible. One way to get teams to understand is to use an analogy – cooking.
Recently I started to use a more minimally-responsive CSS framework called Neat, since I was unhappy with the total offerings of so many others. This article will explain how to start using the basics of Neat in order to better understand how the framework works before using it in projects.
Graphing is a great way to visualize a bunch of data. In this article we will talk about a simple way to make graphs for modern web browsers. We will be using dimple.js that is powered by D3. Here I will explain everything that you need to know in order to get a jump start in making SVG charts.
Why should any developer learn more than one programming language?
This is an interesting question. Let’s think of it this way: Does a carpenter only use one type of saw? Does a mechanic only have one type of wrench? No. In short the answer is, as craftsmen of code, we are only as good as the tools that we know how to use; and programming languages are those tools. When it comes down to deciding on what language it is that you want to learn, the question you need to ask yourself is this. What type of developer do I want to be?
In the everyday world, it’s usually a good thing to have what you need ahead of time, even if there’s a possibility of never using it: I’m going to school, better pack my books; I’m taking a flight this afternoon, better bring some earplugs; I’m going to a meeting, better bring a notebook, and coffee… and my phone. If I don’t end up using these things for the task at hand, no problem. » Read more: The Danger of Carrier Objects
As we start to build websites with mobile first in mind, our stylesheets can get messy really quick. In this article, we’ll talk about making your stylesheets more functional and easier to read at the same time. We will take a quick peek into SASS, and the benefits that it will have over your stylesheets. The focus will be about a common problem that I typically see regarding media queries. At the end of this article I hope that you have a better understanding about making your stylesheets easier to read using SASS.