Programmers Quotes

As web applications certainly continue to become the way of the future for programming, many within the industry are becoming more and more interested in what the top apps currently are so that they can build to suit future consumer demands.
Here are some of the top web apps currently:
1. Last.fm (Audio) This social music directory provides users with the ability to listen to full tracks online and to create custom stations around their music interests.
2. Elance.com- This freelance platform brings service providers and buyers together under one roof; web programming, web design, graphic design, editing, writing, translation, transcription, legal, engineering and sales are among their most popular categories.
3. Gmail- This communication platform is rapidly becoming the most widely used online by individuals and businesses.
4. Amazon Web Services- This web service platform powers many of the largest web services and storage companies.
5. Google Maps- As navigation systems become more mainstream, users are searching for the best available online tools. This system offers users the ability to find and print driving directions and to locate updates on things such as local traffic.
6. Flickr- In alignment with the growing popularity of social media platforms, this Yahoo format for photo and video sharing is being taken by storm by users worldwide.
7. Google Docs- For individuals and small business who are in search of an easy and free document sharing solution, Google docs is the system of choice.
Web programmers should become familiar with these popular web apps when searching for enhancements, additions and even completely new apps to begin developing.

A common programmer credo is “Don’t Repeat Yourself” (Pragmatic Programmer) or “Once and only once” (Extreme Programming). Like all credos, we risk following it even when it is not appropriate.

The larger truth is that we have choice between three evils:

• We can duplicate our code, thus duplicating effort, understanding and being forced to hunt down twice.
• We can share code and affect everyone who shares the code every time we change to code to better fit our needs. If this is a large number of people, this translates into lots of extra work. If you’re on a large project, you might’ve experienced code storms: Days where you’re unable to get any work done as you’re chasing the consequences of other people’s changes.
• We can keep shared code unchanging, thus forgoing improvements. Most code I (and I expect, you) write is not initially fit for its purpose, so this means leaving bad code to cause more harm.

I expect there is no perfect answer to this dilemma. When the number of people involved is low, we might accept the noise of people changing code that’s used by others. As the number of people in a project grows, this becomes increasingly painful to everyone involved. At some time, large projects start experiencing paralysis.

If we’re not happy with the state of the code when paralysis sets in, it might be that there’s really only one option left: To eschew the advice of the masters and duplicate the code.