Future operations development, informed discussion

Once in college in charge of the school website operations (from memory, PCI to HTTP Server kind), later work in Baidu began to do operational automation development, and later with more than 20 people team in 360 from scratch to do two Android projects, I think I'm still qualified to talk about the relationship between transport and peacekeeping development:

I know a lot of operations, working for 2-3 years after the general feel that they are an operator, every day in the middle of the night up "flood relief" do not say, but also occasionally blame. To the end of the year to make research and development, products, testing points ...
But please don't complain, think about it, if you are the boss will not do so?
Research and development, products like DotA in the DPS and Gank, is about the war development; Test, Operation one is a nanny, one is the meat is not valued is very natural.

Operation and development is the inevitable result of the division of labor in the era of Internet mass production, but if you restricting, don't complain about why others are better.

<img src=\ ' #\ ' "//pic3.zhimg.com/7624ba0bf5c19d172e39e464722bcf1a_b.png" data-rawwidth="625" data-rawheight="329" Class="origin_image zh-lightbox-thumb" width="625" data-original="https://pic3.zhimg.com/7624ba0bf5c19d172e39e464722bcf1a_r.png"& amp;amp;gt;650) this.width=650; "src=" Https://pic3.zhimg.com/7624ba0bf5c19d172e39e464722bcf1a_b.png "class=" Origin_image zh-lightbox-thumb Lazy "width=" 625 "style=" width:584px;height:307.418px; "alt=" 7624ba0bf5c19d172e39e464722bcf1a_b.png "/>


What I want to say is:

1. Do not take operations as a career to develop, general operations and 2-3 years will encounter the bottleneck period

2. Engineering developers want to have in-depth development, must understand a certain system operation and maintenance

3. If you are operational, please understand that a program can be run stably online, not what magic, is the development of the pay

4. Due to the rapid development of PAAs, traditional operations (with network equipment, server physical operations) will be less and more, it is recommended that operations and maintenance personnel to operational development or system development transformation

5. If you are developing, please respect the members of the team, do not give others the trouble, as follows

The experience of bat has made me conclude that "it is a shame for developers to write a program that requires someone to wipe their hips."
University was fortunate to have access to the Linux website operation and maintenance work, work-study is responsible for the school's web site operations, and now look back to the technical content of this job is not very high. At that time, the most bull thing is to do the kernel cutting, and then because of curiosity driven, dictionary, ventured to modify the PROFTPD code. Since then embarked on the system development of the non-return, because well aware of the system operation and maintenance of the boring, I have developed a number of procedures for their own principles:

1. Can't crash, to have its own crash recovery mechanism

2. Memory leaks, handle leaks such things are never allowed to happen
   

3. As far as possible statically rely on all the libraries, in addition to common libc, LIBM and so on nothing to rely on, so that can be thrown to the server to run, such as minipy for CentOS 5/6 and asynchronous multi-threaded C/s framework Gko_pool

4. Do a start, stop, restart script

5. function that can be implemented by parameter passing, no need to write configuration file

6. The default parameter is the best configuration, also see the item above

7. Can handle the log itself, with the rotate function, also see the above project

Anonymous user

Operation and maintenance more exercise people. But one thing: Operations are more likely to affect life relative to development. Many operations are on standby for 24 hours.

Pretend to be calm , DBA (focus on Oracle,mysql, various nosql)

I've worked for a few years, and I've been in a 500-strong company, and I've been in a small company (now), with a salary of 17k, and the supervisor says it's a fairly high salary for the OPS, to look at the size of the company, just 50 servers, the technology is weak, and I think the manager is telling the truth. The difference between a few words in a big company and a small company, for the students who are ready to enter this line, refer to:
1.large companies re-process and coordination. Operations are generally divided into first-line second-line, three-wire is often the development of interface people. Many times, do not need your technical ability is very strong, a problem, you independently solve or help a master to solve, the company does not matter, can solve on the line. This has led many people to do a few years of work, the technical ability is actually very weak, bash can not write well. Top of a 500 strong "senior system engineer" title, actually know oneself're up, not say this engineer not, but big company division of Labor is too fine, he will only he is responsible for that small area.
2.the ability of small companies to solve problems quickly and independently. From large companies to small companies to dry operations, will feel from the regular army to the guerrillas, many small companies are really outrageous irregular. Upgrade does not play the application, no documents, no approval, afterwards did not summarize, confused a thing done. Deal with the failure, nor write the case, who do not know how he handled. This style of small companies, looks very efficient, in fact, it is difficult to cultivate a high level of professional engineers, and small companies in the demand for technology is very weak, the requirements of operation and maintenance is weaker, often only require you do not fail on the line.

In General, the development of operations without development has a stamina, but also difficult to demonstrate performance. Especially in the entrepreneurial phase of small companies, research and development is absolutely the core of the company, and operations may be to follow the development behind the soy sauce. Research and development is constantly out of version, this month V1.0, next month V2.0, let the company boss can intuitively feel their performance.and the operation of a lot of brothers, like to deal with the fault of the trouble not to write documents, but also complacent, in fact, the leader know? To do things, we must let the leaders know that performance show out, this is the most important. In my opinion, the operation of OPS is carried out in three levels:
1), wait for the fault to occur, and then handle the fault
2), active in-depth observation system, optimize the system, implementation of automated operation and maintenance
3), optimize operation and maintenance structure, follow up new technology, participate in the development of pre-structure selection
Small companies are mostly on the first level.

ECHOWLT, SA

Because of the psychological shadow from childhood to mathematics, to coding also have a fear of feeling, old can not hand. operation Dimension selected. But now slowly work hard to learn to write code. Experience tells me that there are some things, you go in to find it so much, why not try. What's more, a good operation itself should be at least half developed.

Dengfeng

Operations and development are equally important, only one to the back will find the bottleneck!

Colive Zhang, just I can stop myself!

I will choose operations, the original is also in the Transport and Linux C development hesitated for a long time, do not know the choice, and finally decided to develop, but the results of the search for work or operations. Maybe that's life. love churn, love solves problems

Future operations development, informed discussion