Nine of the easiest mistakes developers can make in a start-up IT company

Intermediary transaction SEO diagnosis Taobao guest Cloud host technology Hall

Absrtact: As the saying goes, the beginning of all the difficulties, the start-up of IT companies will always encounter some not smooth, because in this industry is not without the direction of the negative. It is the real benefit to learn from the mistakes. Look at the article of the IT company founder in the beginning of what can be avoided mistakes!

The writer Scott Gerber is an entrepreneur, columnist and TV commentator. In this article, the author interviewed nine it entrepreneurs in the YEC he founded. Talk about "The easiest mistakes developers can make," and each respondent gives a practical answer, hoping that these "common mistakes" will give you a warning. (The following is compiled content)

In today's springing up world of startups, it's always better to weigh the pros and cons of doing whatever you do, especially in the service industries that are now making the difference between success and failure. Software developers--this seemingly insignificant role in the entire team is actually a daily workload as much as a fire-fighting fireman, tracking and focusing on possible problems, and accidentally causing the company such or such trouble.

To find out what bugs are the most common mistakes of start-up IT companies, I asked nine successful entrepreneurs from the Young Entrepreneur Association (YEC): What are the most common (easy to avoid) mistakes that developers in a start-up it enterprise make? Here are the answers:

1. Create products on the basis of errors

Most startups pay more attention to solving practical problems. The real problem is that startups tend to consider planning and solutions for personal problems as a planning and solution to community problems. Instead, they build their products based on their own needs and think of solving problems in their communities. This is a major factor in failure.

Startups need to be sure that there is a real problem in their tech community, and that there is a real understanding of why the technology community is having these problems. The only way to accomplish these tasks is to communicate deeply with the technical community, identify the source of the problem, and develop a detailed and rational solution. --john Jackovin, Bawte

2. Built up too much gaudy content

There are a lot of things to do in the process of creating a product that is as small as possible, and how do you do it? The first is to make simplicity the primary prerequisite and then test your assumptions as early as possible. The next step is to organize a small beta test team to start testing the product, using the feedback from the testers, and only the feedback from the Test team, and not to take any information that is not relevant to the Test team, followed by the crucial part: integrating the flashy parts. --peter Awad, Goodblogs

3. The code created is too stiff

While it is not necessary to implement full scalability at the initial stage of the development platform, it is critical to ensure that your platform code will support scalability in the future, not when your company has already run successfully.

It is frustrating to modify the stiff code that is actively used by the client, and it is likely to affect the company's growth rate once the code plays a significant role. --fehzan Ali, Adscend Media LLC

4. A flexible strategy at the early stages of a product release is most important

Startups may encourage the implementation of a product launch strategy, and it's not too late to collect user feedback after the product is released, but the current "post-fix" attitude is silly, especially if the product you released later found a lot of bugs.

If you want to develop the business, your customers will need more products, so throughout the process must not be porous. Be prepared to postpone the release of a few days later than the expected release time, so you can set aside more time to fix bugs that may affect the user experience and help maintain your corporate image. --danny Wong, Blank Label

5. Too concerned about the code

The mistake you've made before is that you care too much about code, and that code determines everything.

But in early product development, it's much more important to take the time to solve problems that customers encounter than to write code. If you focus on dealing with customer issues, this will help you get more accurate code, because in the process of solving the problem you will be able to grasp the customer's real concerns. --wade Foster, Zapier

6. Not fully related to the enterprise business aspects of product development

The development design that does not really involve the business aspect of the enterprise, or does not understand the real demand of the company customer is a common mistake, because the product is not a company, the company can not only revolve around the product.

Developers must understand how the product is being developed to achieve the company's overall goals, strategy, and customer uptake of this overall operation, which is the key to the success of product development and deployment. --panos Panay,sonicbids

7. Failure to address the problem of lack of time

After the launch of a product, many developers will feel at the beginning of their own time capacity is not enough-many departments are looking for you, and you can't do everywhere. The smartest thing to do, though, is to build on some platform-ideally a communication platform, so you can solve all the problems on this platform. In this way, you can build a better product and avoid distracting your development team in different places, weakening the overall strength.

For some companies, it may be hard to allocate resources between mobile devices such as computer software and mobile phones. For others, this could lead to a focus on iphone technology that ignores Android development. But ultimately, you need to find out where you want to highlight and then start optimizing them!—— Aaron Schwartz, Modify Watches

8. Planning is not based on code

Before you start implementing a development project, it is essential that you develop a planning process table. When planning, you need to thoroughly figure out how to do it and how to run those features on the basis of workable code.

In fact, the planning here seems to have nothing to do with the code, but the code is the key to solve the problem, when you encounter problems, should not ask: "Let it work the simplest way to do?" Instead, you should ask, "What's the easiest way to make it work for the user?" --james Simpson, Goldfire UBM

9. Confusing collaboration between departments

The first thing to do when a startup is set up is to separate the innovative developer team from the rest of the organization, and make it clear that the technical geek is not going to look at the financial statements. --yuriy Boykiv, Gravity Media

Source: TNW (Compilation/Silliang Zebian/Zhangjiang)