Don't really have a masterplan for this pearltree. Its filled with stuff I either found interesting or useful and I didn't want to forget it. Mar 27
Get flash to fully experience Pearltrees
One of the painful parts of teaching a lab-based embedded systems course is that over and over I have to watch a team with a relatively simple bug in their code, but who is trying to fix it by repeatedly making random changes.
Hystrix : it’s the genus name for “Old World” porcupines , and it’s also the latest release from Netflix . But you won’t see it in their catalog of movie and TV titles, and you can’t add it to your queue, because it’s not content–it’s how Netflix makes sure its content is highly available.
IoC container solves a problem you might not have but it’s a nice problem to have | Krzysztof Koźmic on softwareOn frameworks and libraries
By Evan Miller February 6, 2009 ( Changes ) PROBLEM : You are a web programmer. You have users. Your users rate stuff on your site.
14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star Plenty of people want to get involved in open source, but don’t know where to start.
Originally located at http://www.pphsg.org/cdsmith/types.html , this article explained some basic concepts of type systems. Unfortunately, that page is gone and I had to fetch it from the web archive of that page . The note at the bottom states that contents are in the public domain, so I think it's OK to reproduce here.
Background People who create web forms, databases, or ontologies are often unaware how different people’s names can be in other countries. They build their forms or databases in a way that assumes too much on the part of foreign users.
Heron-Centric: Ruminations of a Language Designer The Principles of Good Programming by Christopher Diggins July 24, 2011 Today's post is a lightly edited repost from my blog at The Area , a web-site dedicated to users of Autodesk media and entertainment products. I came up with this list of principles to help with a recent C# training I gave, and I thought that members of the Artima.com community could appreciate these principles and have some interesting insights to share. The principles of good programming are closely related to principles of good design and engineering. The following programming principles have helped me over the years become a better programmer, and I believe can help any developer become more efficient and to produce code which is easier to maintain and that has fewer defects. DRY - Don’t repeat yourself - This is probably the single most fundamental tenet in programming is to avoid repetition.
I spoke about this topic quite a bit in ALT.Net Seattle. This is mostly relating to application architecture and how you structure your application. This is the logical result of applying the Open Closed and Single Responsibility Principles. Feature may not be as overloaded a term in our industry as a service, but it still important to define exactly what I mean. A feature, in my eyes, is a discrete part of the application that perform some operation.
You are not a Software Engineer.
Security companies and IT people constantly tells us that we should use complex and difficult passwords. This is bad advice, because you can actually make usable, easy to remember and highly secure passwords. In fact, usable passwords are often far better than complex ones.