Get Started for FREE
Sign up with Facebook Sign up with Twitter
I don't have a Facebook or a Twitter account
 Your new post is loading...
Your new post is loading...
Scoop.it!
The Boy Scouts have a rule: "Always leave the campground cleaner than you found it." If you find a mess on the ground, you clean it up regardless of who might have made the mess. You intentionally improve the environment for the next group of campers. Actually the original form of that rule, written by Robert Stephenson Smyth Baden-Powell, the father of scouting, was "Try and leave this world a little better than you found it." 
No comment yet.
Sign up to comment
Scoop.it!
tl;dr version
Rule #1: write commit comments before coding Rule #2: write what the software should be supposed to do, not what you did
Scoop.it!
IoC containers are not just about dependency injection.
Scoop.it!
When bugfixing, the branching approach I like best involves first finding the commit that introduced the bug, and then branching from there.
This approach has several advantages.
Scoop.it!
Within the field of user experience, visual design is sometimes perceived as a bit of an outsider. Indeed, some visual designers are apparently feeling a pressure to rebrand themselves as “user experience” designers to progress their careers. In my experience with clients, visual design is often likened to decorating the walls of your living room. It makes everything a little nicer, but it’s hardly a key part of the architecture of your house.
There are at least four key principles of visual design that have an important impact on usability. These four principles — contrast, repetition, alignment and proximity — were originally given the engaging acronym CRAP by Robin Williams (the visual designer, not the comedian). You can exploit these four principles to make user interfaces both more attractive and easier to use.
Scoop.it!
Objects, classes, and constructors are an interesting thing in Smalltalk. Coming from languages like C#, Visual Basic, or Java, one expects to be able to declare constructors in your classes. You also expect them to be "special" nameless methods that can only be called by the "new" keyword when creating instances of your class. Smalltalk is different, and better, or worse, depending on your point of view.
|
Scoop.it!
Big Ball of Mud ... alias Shantytown or Spaghetti Code
Scoop.it!
I’ve spent the past nine months or so overcoming resistance to the DevOps movement in both public forums and inside client companies. During that time, I’ve begun to notice a common misconception that I think is fueling much of the negative initial reaction that some people have to DevOps ideas. I want to take a shot at clearing it up now:
DevOps is not a technology problem.
Technology plays a key part in enabling solutions to DevOps problems. However, DevOps itself is fundamentally a businessproblem.
Scoop.it!
I used to be a huge supporter of comments.
I loved to see glorious, rich, voluminous comments in all the code I read. I loved to write them. I thought that for a program to be 60% comments was a pretty good start. But as my teams began to write cleaner code, they sometimes would brag that the code was so clean that it almost didn't need comments. Now I want all of my code to go beyond almost.
Scoop.it!
Last week I spoke to an undergraduate data structures class at GVSU. The talk was partially about data structures, but mostly about becoming a good developer. Most of this is old hat, but I think it’s good advice to just about anyone.
Thanks for sitting through my talk on Friday. It’s always fun to come back to my alma mater and talk to new computer scientists. If you have any questions, whether it be about a talk topic, career advice, or internships, feel free to send me an email. Below are resources on some of the topics I mentioned
Scoop.it!
In mainstream object oriented programming languages, objects are created by invoking constructors. This is rather ironic, since you can say a lot about constructors, but you cannot honestly say that they are object oriented. Ok, so what? Isn’t “object-oriented” just an old buzzword? If constructors work well, who cares?
Scoop.it!
Firstly, what am I talking about? Applications that meet some of the following descriptions:
1. Stored procedures with a fair amount of conditional logic or complicated business rules buried in a sub-query (some would argue sprocs at all).
2. Web pages with lots of conditional output again encoding business rules in snippets of view logic. if else checks that display the latest price for something if before and certain date or a default price.
3. The majority of ‘unit tests’ require a database, or web and application server to be up and running.
4. The majority of code files make reference to language default I/O or database libraries.
5. Hours are spent trying to determine if differences in version of infrastructure are the cause of certain bugs.
|
