Today, I saw a news recommendation on the homepage, saying "technical challenges for programmers in entrepreneurial teams ". After reading this, I still thought the same way: the pattern is a little small.
First of all, I think most of the content in this article is correct-that's right. As a programmer, you should do this. However, I think it is not accurate when there are some points.
First, most of the content mentioned here can be done in large companies, small companies, or even entrepreneurial teams. It doesn't mean that you can find such a challenge in a startup team-your company hasn't given you a chance, so you can try it on your own. For example, refactoring your code, automating daily work, good development habits, and maintaining your learning enthusiasm. I think as long as you are not in a very rigid Company, you still have the opportunity to do this.
Second, there are some things related to your existing capabilities and the power you hold, such as improving your products, improving resource utilization, and planning resources. If there are many people in the company, you may not have such rights. As for the lack of people and the lack of ability, it will not actually happen, because the company cannot find a competent person in such an important position. In other words, you have the opportunity to learn, but the probability of actual command execution should be relatively small. Of course, there is another third case, that is, the company is really not very good. The people who assign you such an important task are also confused about the situation. Of course, if your level does not meet the requirements, the probability that this sort will make it difficult for you to replace the game. The larger the number of companies, the less. In other words, there are more opportunities in small companies, depending on whether you have the ability to seize them.
Third, there are some other things, such as the question "Can someone else use a few machines to support the access traffic? Can they use less hardware to support you"? I would like to ask in turn: how many visits do you plan to use a single machine to support? Is it the access volume of the blog site, or is it like Facebook? In fact, for most Internet applications, if you have such access traffic and you have achieved such a scale, you will find that the hardware cost is actually only a small part. (Except for videos or large online games ...... If you want to do this, I will not say anything .)
Recently, I interviewed a candidate. Their company chose a large SAN storage device, and even expanded its capacity to more than 10 times in the future, as a result, the database occupies 2% of the total storage capacity. What's more interesting is that, in fact, the most important access volume of this system is caused by employee input within the company. What does this mean? Many times the problem is not to say: you see how much traffic I have, so I need to press it. But: You see, my access traffic is not that big at all. Don't buy anything that expensive. Or, you see, if you think too much, I don't actually have such a huge access volume now, it is too early to consider this issue. In this example, the hardware is purchased early, and the software design is the same. In many cases, the problem is too early. Your precious time is wasted on the performance of the computer.
Performance Tuning and scalability are true. Sooner or later, it will be done. But before doing this, please first set a priority for your questions on hand to see if it is the most important thing currently? If yes, it will be no longer time to move on. Many times you may find that many of the functions that determine whether a user buys your account have not been implemented yet, or the UE is not good enough. Even if you want to broaden your horizons, you may find that the partner has not been well-positioned. This is the most important thing.
Those mentioned above are not the main problems. The most important thing is that you have a stable and large company that doesn't go there. What exactly is the figure of running a startup company?
If you are a technical capability problem, and you have no ambition, and want to mix it for life in a large company, the technology must be strengthened first. If you feel like a big company has a radish, and you can learn less as a screw, you can only go to a challenging entrepreneurial team. So, really, look at things other than technology. There are only two things you can learn from a startup company: How he died or how he survived. What are your reasons for staying in such a company? There is such a good opportunity to know for yourself what you have no chance to contact these big companies! How a company can survive or why it will die is far from the only technology. Even if I dare to make a pass, the probability statistics will definitely not take a big part. Do you think Microsoft is successful because of how well the Bill Gates code is written? Do you think the iPhone is on fire because of Steve Jobs's code? I have already written this question many times before.
So what can I see? For example:
1. How do they manage a company? For example, some companies pay great attention to some corporate culture content from the very beginning, some companies may pay attention to personnel training, and some companies may emphasize that finance and human resources departments are not power departments but service departments;
2. How do they find and locate their own products and directions? Start-ups are usually crossing the river by feeling the stones, so you will often find that the direction of the company has changed. So you need to ask why the change is happening and why it is like this instead of that;
3. How do they package products? Product Packaging is also a very important issue, related to how much upstream and downstream you can pull;
4. How do they do marketing?
5. How do they plan to quit?
In fact, you don't need to check the above items. It's very simple. You just want to do what you plan to do if you start an identical company on your own one day. From top to bottom, you will suddenly become open-minded, knowing how the head of the department is arranged, how the head of the Department should be arranged, and how the head of the Team is arranged. In fact, this way of thinking is quite interesting. You will find many answers to your real-life questions, such as why your salary is not increased.