I want to express their outrage by some published vacancies, and employers to test for smart applicants for the position of lead programmer or architect in the end of the article. Once again I read of vacancies on the forum '. System Architect is required. the husband. , Age 25-35 years. '. In the comments, and no I had enough people to the nines to spread these requirements. What I personally do not like about the job, except that the indication of sex and age of unconstitutional Russia?.
What do you think, how much time should be to prepare a system architect, a real professional, who can be ' immediately start a fight '? .
In 22-23 years, most finishes high school. Well, if the student previously trained in a software company. However, as experience shows, to give significant time to work because he can not study. In fact, the student can only be used for very small problems, just with the daily monitoring of their performance.
Clearly, the lead programmer on the job, graduate, with a miserable experience, it is unlikely any company will. This translates to about 1-2 years of work for internships or work in positions as a programmer, but without responsibility for the project. In practice, only after 25 years of programmer - trainee will be an independent commission to work on the project site, without fear that he's very ' nakosyachil '.
However, to become a truly leading programmers, not a piece of paper, and the experience of work in knowledge, to be held for another five years. I did not calculate these figures are all ' on their skin ' tested. Requires full luggage carried 2-3 projects to go through all the stages of development and to consolidate the knowledge. Given that the major projects last from six months to several years, then five years at work as a programmer does not look like a large number. This is the minimum. Thus, we have 30 years, and we are still programmers.
After this it is necessary to work the lead programmer. This will give the experience of managing a team of programmers, the ability to allocate and assign tasks. This stage can not jump - an architect who can not communicate, express ideas available does not cost anything. Similarly, 2-3 project to collect and consolidate experience. This is about 5 years, so our age is 35 years old.
Here already, after 35 years of his life and career can be a system architect to think. If the enthusiasm has not waned, then read that it is necessary to obtain. certified architect from Microsoft. There is clearly 35 years of life will not get. But if received a certificate, the architect found a job, then congratulations - you made really great results!.
And now, back to the original question, I would like to ask the employer: ' Where have you seen all the architects under 35 years old? ' . I coped well with the test. No wonder a few years working the lead programmer, not only on the number of the labor. Thus, the problem.
Recently, I recorded my daughter to the doctor. The procedure for many well-known: in the morning come, take a notebook with the schedule of admission physician and enter his name there at the time, which is not yet occupied, and it is convenient. However, t. to. Physicians are sorely lacking, the notebook to the queue. People queue to take pre- notebook for a few hours before the opening of clinics. To access the notebook each formed their own place. Many parents enroll their children to several doctors, respectively, occupying several queues.
Task 1. Develop a formal model of this procedure writing to the doctor.
Task 2. Indicate the weaknesses in this method of entry to the doctor.
Task 3. Imagine that you have come to record at 7 am, and have all 50 people. The doctor takes no more than 15 people per day, t. e. on this day to accept appointment you do not have time to. Can something still be done to register ( use of force and bribery does not count)?.
answers:.
In general, this is a typical model of a multithreaded application. There are a limited resource: a doctor, access to organized through some sort of mutex - notebook. Everyone - a separate thread, becoming in turn to access the shared resource.
Typical weaknesses of multi-threaded applications (for example, the complexity of thread synchronization ).
To move forward in the queue, you can take advantage of its weaknesses. For example, it is clear that a person take a few bursts, it is very difficult to track the movement of a few bursts, but when dozens of people just trying to do it at the same time, the task of tracking ( clock ) for all queues is not solved. This is a weak spot. Therefore, while the others are busy sharing out of seats in line, quietly moving forward - when they open the clinic, all mixed up queue and right will be the one who was the first grab a treasured notebook. Personal record - came somewhere in the fifties, enrolled in the third notebook.
PS: Typing in «Google Docs». How he tortured me! . We must take the mouse and then dab in a place where I was caught off guard this damn autosave! .
No comments:
Post a Comment