About DCS Media
DCS-Media provides reviews, techniques, technologies, programming and design tips to help you conduct not just business, but smart business.
Using version control is vital to a development shop. Even though I am one developer, I have a subversion code server in my basement that I constantly use. If I write a bad piece of code, it feels so good to rollback to a previous version of code instead of trying to wrack my brain figuring out what code to back out.
DCS-Media provides reviews, techniques, technologies, programming and design tips to help you conduct not just business, but smart business.

Using version control is vital to a development shop. Even though I am one developer, I have a subversion code server in my basement that I constantly use. If I write a bad piece of code, it feels so good to rollback to a previous version of code instead of trying to wrack my brain figuring out what code to back out.
In a team or corporate environment, though, you may have some developers who are new to the team and are unfamiliar with version control software like CVS or Subversion. I know those coming from Microsoft SourceSafe to CVS had some troubles adjusting.

How many of your books have changed since my last post? I'm sure that since 2007 your library of reference books should've changed a little.
A while back, I wrote a post about what books are in your library that are within reach while you develop. I figured now would be a good time to update my post.

For developers who are creating plug-ins to content management systems (or their own, wink wink), there is no reason why you can't automate your social status updates to let your audience know what's happening with you on your social network of choice.
Facebook, LinkedIn, and Twitter are my "home base" of social networks where I hang out at.

How much of your "brains" do you take into a company? This post explains how to determine what code you can and cannot take into a company if you already wrote it prior to being hired.
But first, let's get this out of the way.

Developers know when they see a bad piece of code and that comes from experience. As you progress through your career, you'll see some...uhhh...ummm...interesting code. Most developers have egos and need to check them at the door if you want a quality software product.
Band-aids are described when a coder decides to fix a defect quickly as opposed to fixing the defect correctly. The mentality is that they want it off their plate by fixing the problem as fast a possible, which leaves the defect as a quick fix and not a long term solution.
Every professional has the proper tools to get the job done. What tools couldn't you live without?

DCS (Danylko Consulting Services) Media (as in 'news') was originally meant for my clients to keep them up to date with what's going on in the technology industry and explain a few technologies that may elude them. Using a blog to show them what's happening with technology would provide a way for them to integrate that new technology into their business and (hopefully) allow them to become more profitable.
Rewind back to 2005! What better way to show new technology than to create a blogging engine that includes some of that technology.

Following up with last week's post about Complexity vs. Simplicity, I focus this week on an aspect of coding that is kind of touchy to developers: Maintainability.
Now, I'm not pointing to any one developer, but I'm sure there are other developers out there who know what I'm talking about in terms of "coding spaghetti." That's just one term. Some of these may be familiar to you:
If you haven't been in a corporate environment and you just code like a madman, how do you know if you writing good code? You have nothing to compare it to.

When you are given a project by a client, do you think of a web site or application that does just about everything or do you break it down to what's functional and feasible for a web site that does the job?
Let me try a different approach.
Can a developer code something simple or does it have to be extremely complex with a three-tier architecture with web services and a fat browser full of JavaScript and ActiveX components while overflowing with every jQuery bell and whistle known to man?
After reading Mr. Atwood's post (and the comments) about "Nobody Hates Software More Than Software Developers," I realized that not many programmers out there like (love?) their career of working with computers or coding software.
There was another post about the 10 Things I hate about Software Development as well, but, in my opinion, this list goes with the territory. We're all going to experience one (if not more than one) "thing" at one point or another in our career. Some of them go away (like the boss), but that shouldn't hinder you from your passion of programming.
I'm sorry...I'm rambling. Back to the post...
I recently received a comment post from a reader about how awful a past post was. I read the post over and started thinking about my question, "When to use AJAX programming?"
After thinking about the question and reading it over yet again, I realized something about the reader's opinion:
He was right!