10 questions never should be put for developers

10 questions never should be put for developers

Do you know the word which will describe a person who creates the website for you? Yeah. It is Website Developer. They do a wide range of tasks: from front-end (HTML, CSS and JavaScript) to back-end (PHP, Ruby, Java, Python…,), PM (project management, database maintenance, deployment, even web designer.

It is true that some clients without experience of working with developers may be confused of putting some questions related to job, price and so on.

Here are 10 questions which you should not give to developers including solution for each situation.

1. “Can you do this for free?”

Budget is one of factors which always makes businessman headache because anyone wants to minimize expenditure.  However, developers also have to make a living. One rule is that no one works for free!

Even some individuals work for their passion. Meanwhile, throughout the time the spent to get skill in the pass or the time they spare for you today, it is worth money.

So what is the solution for this case? Well, sit down and debating with developers. Tell theme about your affordability, how much money you can pay for website? The deal will come from both and FREE is not a good option.

2. “Can I pay you after the work is done?”

Of course not!

We are all running business. It means that we do not know each other. Developers can not be sure whether client is a good person or not.  Normally, there will be instalment payment which you need to charge every period of done works.

There is no guarantee at all. If developers do not feel safe, there is no transaction occur.

At the very least, you should require that a percentage of the full amount be paid up-front; anywhere from 10% to 50% depending on the job. This shows that you are professional and take your work seriously. And if the client backs out or disappears, the monetary damage to you is kept to a minimum.

3. “Why is it so expensive? My friends said they can do it for only $X.”

It is clear that price of creating a website will be different in different company/ business unit. It will rely on time/ human resource/ skills. You can not know exactly how much is reasonable. The only thing you can do is refer price, then compare to jump to conclusion.

Not sure that lower charge will have the same result of website. You need to always remember that ” You get what you pay for” . Nothing is sure until the juice comes out.

If you’re looking to keep cost to a minimum, it’s important to ask your developer a lot of questions. Has she made a clear and concise development plan that includes all of your requested features? What types of technologies does she plan on using to build the site? How will you update your own content? How will she launch the site and continue to deploy changes?

4. “Can you just give me the code and I’ll do it myself?”

This goes back to what I said earlier about how a developer has a specific set of skills that the client does not have. The client hired the developer to do work that he is most likely not capable of doing. The client shouldn’t assume that he’ll be able to dive right into the code and understand it!

What you’re also hiring when you hire a developer is experience. Your developer has probably seen it all: nasty bugs, hosting problems, broken code, missing files… you name it. She has the experience to deal with these problems efficiently and the skills to keep the project from getting derailed by one simple issue.

5. “I don’t have any content yet. Can you just build the site without it?”

During work, we met so many questions like this. Clients only give us topic of website such as gym, car, fashion, toy… and request us to make a perfect website. Fortunately, there are hardly ever complains. We have to spend so much time to build website content with them. A designer or developer needs to know how much text to account for, what types of headers or taglines you plan on having, and even the size, quantity and style of images.

Sure, lorem ipsum placeholder text and dummy images work fine, and one can argue that their use is industry standard. But they are no replacement for the real content that your users will see every day.

The longer development goes with dummy text and images, the more likely it is that adjustments will need to be made once the final content is added. More adjustments means more time and more risk that the project will go over-budget.

6. “Can’t I just buy a  template?”

Sure, you can buy a  template… if you want a cookie-cutter site design with no unique functionality!

Some CMS frameworks are designed so that people with no design or development skills can get a blog up and running with minimal effort.

However, chances are that your site is not just a blog. Almost of websites are created to do business which sells goods like handmade jewelry, or offering online cooking classes, or managing your town’s community events. In all of these cases, only template is not enough to do.

A developer can create a template from scratch that is customized to fit your needs.

Even better, she can work with a designer to create a unique design for your site. So instead of having a design that’s also being used by any number of other sites, your site design is just for you!

7. “Can you make this one small change really quickly?”

Sir, please remember that sometime, that very small change will waste much time than ever. You are not person who valuate. It’s developer!

Developers tend to focus on one task at a time, and it’s difficult to hit the pause button and temporarily switch to another task, especially if their current task is something like building out a large feature or fixing a particularly nasty bug.

If you’re working with a freelance developer, it’s likely that he’s working on multiple projects simultaneously and has very specifically planned out his work schedule for the week. The day you make your small change request may be a day that he’s already planned to work on another project.

Respecting your developer’s time and schedule is important. Instead, state as clearly as possible what you’d like changed, and ask your developer about response time.

8. “Can you just make my site look like [insert other site here]?”

This one is for all our designer friends out there!

If you ask your designer to simply copy another site, it defeats the purpose of hiring her in the first place!

As a client, you’ve hired a designer to create a unique and beautiful style for your site that sets it apart from all the other sites out there. It’s a waste of your money, and frankly, your designer’s time to steal the style of another site.

Did you notice that word we used? Steal? As in plagiarize?? That’s something the Internet at large notices. If your site becomes more widely known, people will start to wonder why your site looks so familiar. You may even be violating another’s site’s copyright. That is not the kind of publicity you want!

The best thing to do as a client is to choose what parts of the other site you like. Maybe you’re drawn to the color scheme. Maybe you like the shape and size of the buttons. Maybe you like the nav layout. Whatever it is, those are the things your designer should try to incorporate into your site’s unique design.

9. “WAIT! It doesn’t do X?!?!”

Assumption is a dangerous thing!

You should never assume that your developer knows all the features you want to include in your website. Just because the majority of sites have a contact form doesn’t mean that your developer will create one for your site by default.

Make sure your developer has a detailed list of all the features you want to see on your site. Seriously, the more granular the better!

If you’re a developer, ask lots of questions while creating your development plan and document every feature your client wants. It’s much easier to know everything ahead of time than to go back and trickle in surprise features!

10. “I decided I want to change everything.”

Okay, so this one isn’t really a question, but it’s a statement that no developer ever wants to hear.

While it’s okay to want to change the style, layout or functionality of your site (or all three!), as a client you must understand that this most likely falls outside the scope of the initial project outline. This means lots of extra time, work and money, and your developer reserves the right to charge extra for these new changes.

As a developer, there is no way to fully prevent this from happening, but you can minimize the likelihood by having a successful planning stage for the project.

Of course, having a contract that clearly outlines how you will handle work that falls outside the scope of the project is important, and will help to minimize disagreements and awkward conversations in the future.

Source: skillcrush.com


Nothing is impossible!

Related News