What Makes a Good Web Development Company

<p>The world of web development is still very much misunderstood. We've even heard people call it a "dark art". So when you need help turning your ideas and designs into a high quality website or web application, how do you know who you can trust to get this done?</p><p>The purpose of this post is to provide some key points on what makes a good web development company, and will help you understand the kind of questions you should be asking development companies.</p><p>This is going to be a very opinionated post and we make no apologies for it. If you disagree with anything we are certainly open to discussing it further.</p><p>Now to get on with the post. Below are the key areas we are going to be looking at, and what you should be looking for in a web development company.</p>Able to do both front-end and back-end development&#13;
Don't specialise in one back-end technology&#13;
Should follow best practices&#13;
Understanding of marketing strategies surrounding the<!--nextpage-->projects&#13;
Invests time in research and development&#13;
Has a rigorous testing process, including automated tests&#13;
Flexible to change&#13;
Use source control<p><strong>Able to do both front-end and back-end development</strong>&#13;We don't subscribe to idea of developers that do front-end development and developers that do back-end development. That's the equivalent of having a plumber who only fits pipes and leaves the fitting of the baths, showers, sinks and toilets to someone else.</p><p>We agree there is a separation between web developers and web designers, there's a completely different thought process going on there, but the separation between front-end and back-end is just wrong. To be a good web developer you need to understand the full development cycle and to be able to get involved in the project from start to finish. There is also much to be learnt from the working with the varying technologies, but we'll come on to that.</p><p><strong>Don't specialise in one<!--nextpage-->back-end technology</strong>&#13;There are a number of good back-end technologies that are appropriate for web development including Ruby on Rails, ASP.Net and PHP (and others). They all have their strengths and weaknesses and not one is perfect. A good web development company should be flexible in which technologies they use, so that they use the most appropriate one for their clients' needs.</p><p>The key reason we have spent time learning a number of technologies is to able to pick and choose the bits we like. Over the years the developers involved in The League have been able to take the good parts of each technology and formulate a number of best practices and use them across all platforms.</p><p><strong>Should follow best practices</strong>&#13;The key to being a good web developer is not the technologies that you use, but the best practices that you follow. As technologies come and go in our very fast moving industry those best practices will remain, or at least evolve. As a<!--nextpage-->developer if you have a good grounding then you can move with the times and technologies fairly easily.</p><p>So what are these best practices that we are talking about. Below are some of the key ones we follow.</p>Writing semantic HTML&#13;
Follow web standards for all front end coding&#13;
Automated testing of both front-end and back-end code&#13;
Use of a MVC framework<p><strong>Understanding of marketing strategies surrounding the projects</strong>&#13;We've heard this complaint many times that web developers don't think about the marketing strategy of a project. This is generally because developers don't care. Well they should. How can they advise clients and think about helping clients produce the right solution, if they aren't thinking about the "bigger picture" (sorry, we know it's a horrid phrase, we'll go wash our mouths out now). If a developer blindly does the work, they are not offering the client a service, they are just being a meat puppet.</p><p>The most important<!--nextpage-->question a developer can ask is "Why?". Take time to understand the client's requirements fully, and advise them, after all the client doesn't understand the ins and outs of web development, you do. Make the development cycle a two way conversation.</p><p><strong>Invests time in research and development</strong>&#13;As everyone knows the web industry is a very fast moving industry. Things come and go in the blink of an eye. A good web development company gives it's developers allocated time each week to look at new trends and technologies. Admittedly some of these trends and technologies are dead ends, but you won't know unless you look into them.</p><p>If you want to know if a web development company knows there stuff, simply ask them what their developers have been looking into recently. You don't have to understand everything you are told, note them down though and look them up on the internet to understand if the company are looking at new trends or not.</p><p>R&amp;D is probably<!--nextpage-->the most important time each week for a developer. If developers don't evolve, the solutions they build will become stagnate and dated very quickly. As a client do you want an out of date solution before you even start?</p><p><strong>Has a rigorous testing process, including automated tests</strong>&#13;Too often we have seen the client is <strong>the</strong> tester for a project. If this is happening, then, to put it bluntly, the development company don't understand your project well enough, they are just "banging out" code.</p><p>A good web development company should be writing automated tests (integration tests, unit-tests etc) for all their code, both front-end and back-end. On a simple level, tests help developers to concentrate on the code they are writing at that given time, they also help developers to write more concise code. More concise code means the code base is easier to understand and cheaper to maintain.</p><p>The major benefit of a test suite to a client is that when<!--nextpage-->changes are made to the code in the project there can be a lot more confidence in the fact that the change, or new code, hasn't broken anything else.</p><p>We are not saying automated testing is the silver bullet of web development, and tests are only effective if they are written well, but they certainly should be part of any web developers toolset.</p><p>Automated tests aren't the only important aspect of testing. The web development company should also have a level of human testing as well, and this is certainly something clients should be involved in. <a target="_new" rel="nofollow" href="http://en.wikipedia.org/wiki/User_story">User stories</a> are key to this process. As part of the development process, clients should work with the web development company to put together User stories, so that all parties involved understand how users will interact with the site or application and the results of those interactions.</p><p><strong>Flexible to change</strong>&#13;We've all heard<!--nextpage-->developers complaining how their clients' change the requirements of a project midway thought a project. Developers need to stop complaining about this, it happens to us all and it's never going to change. A good web development company should have processes in place to cope with change. If you are a client, ask how change requests will be handled.</p><p>Web developers should work to short release cycles, preferably 1 - 2 weeks. The worst thing that can happen to a project is that the developers get the brief, start the work and then 2 months later they announce it's finished, only for the client to say "This isn't what I asked for!". By working to short release cycles, clients can be involved at all stages. At the end of each release the client should review the project so far and submit any change requests.</p><p><strong>Use source control</strong>&#13;Our final recommendation is a pretty obvious and simple one, to most people, but we still speak to developers who don't use any form<!--nextpage-->of <a target="_new" rel="nofollow" href="http://en.wikipedia.org/wiki/Revision_control">source control</a>. This seems more prevalent with freelancers as they don't see the need as they are the only ones working on the code. If that's how they see it, then they are missing the point.</p><p>There are lots of reasons why all code should be source controlled. We're are only going to mention a couple of key points here. Firstly it's a great way of keeping a log of changes made to code. (As long as developers put a comment into the commit). Secondly and most importantly is allows developers to change code without the fear of losing already work already done. This is especially useful when trying out other possible coding solutions to a problem.</p>
<div><div id="article-resource">
<p>John Polling has been working as a web developer for approximately 10 years now and has recently set up his own <a target="_new" href="http://theled.co.uk">web development company</a>.</p><p>He has worked for KPMG, McCann-Erikcons, Daimlyer Chrysler UK and a few smaller marketing agencies.</p> </div><p>Article Source:
<a href="http://ezinearticles.com/?expert=John_Polling">http://EzineArticles.com/?expert=John_Polling</a>
</p></div>