Joel's test
I read the book “Joel on Programming” the other day, in which there is a test of the quality of a team of software developers. I decided to publish its results for the company I work for now.
1. Do you use source code version control system?
Not. This company is the second in which I work as a php programmer. For some incomprehensible reason, neither the system nor the previous one used such systems, which is very sad. How much less would be a problem. By the way, Joel himself advises the programmer to start using CVS himself and try to add other developers to this.
2. Can you build the product in one step?
No I can not. Although for some projects there are scripts for automatically deploying a web application on a production server. But this is only for a few new projects.
')
3. Do you perform daily compilation?
Well no. Unfortunately, I don’t know how the Java programmers team works.
4. Do you maintain a database of errors in the program?
Not.
5. Do you fix bugs before writing a new code?
Not. Often errors are detected already at the stage of “industrial operation”. And most often, the correction of errors is entrusted to completely different people who had no relation to the project before. Very sad situation.
6. Do you have a current work schedule?
Haha Yes, there is some kind of nonsense that is crammed into a calendar in an exendzh server, but it isn’t exactly that to be relevant. And there is no detail of the schedule, which "requires" Joel.
7. Do you have specifications?
I would say no. It happens that some papers are written. If you're lucky, there will be screens to do. If less, then the text with a bunch of ambiguous texts. Often I will just take a look at this, and then put it on the edge of the table, because they are all pretty useless.
8. Did you create a calm environment for the work of programmers?
This item upsets me the most, probably. No, no and NO. Next to the programmers are managers, phones are always ringing, someone is walking, talking. Half of the programmers have disgusting chairs, after an hour of sitting on which the ass becomes square. In general, I would say that the conditions are disgusting.
9. Do you try to use the best existing tools for work?
Let’s say yes. That is, I must say that we have different programmers. And different applications are written in different languages (C #, Java, PHP, Perl) and use different databases (Oracle, MySQL, PostgreSQL). True, I do not know who and what is guided by the choice of languages, tools and technologies.
10. Do you involve testers?
Not. Also a terrible moment. Programmers are testing everything themselves. Then another manager can potestit.
11. Do you offer job seekers to write code during the interview?
Well, when I was interviewed, the second part was the execution of test tasks. The tasks were very simple, they could hardly assess me somehow. Everything that could be said about them, that yes, I at least read the book “PHP in 24 hours”. Spolsky himself advises checking out a little more. But we shall.
12. Do you test “usability” on random people?
No, if the general liked it, then so be it.
Total three points. What about this Joel writes: “Ideally, you should score 12 points. 11 points is a tolerable amount, and 10 or less indicate serious problems. In fact, most software organizations work with only two or three points, and they need major improvements because companies like Microsoft keep 12 points all the time. ”
And how are you?
Apd If interested, then Joel Spolsky maintains a blog “Joel on Software” , based on which books are published.
Apd # 2 Original of "Joel's test" with explanations .
1. Do you use source code version control system?
Not. This company is the second in which I work as a php programmer. For some incomprehensible reason, neither the system nor the previous one used such systems, which is very sad. How much less would be a problem. By the way, Joel himself advises the programmer to start using CVS himself and try to add other developers to this.
2. Can you build the product in one step?
No I can not. Although for some projects there are scripts for automatically deploying a web application on a production server. But this is only for a few new projects.
')
3. Do you perform daily compilation?
Well no. Unfortunately, I don’t know how the Java programmers team works.
4. Do you maintain a database of errors in the program?
Not.
5. Do you fix bugs before writing a new code?
Not. Often errors are detected already at the stage of “industrial operation”. And most often, the correction of errors is entrusted to completely different people who had no relation to the project before. Very sad situation.
6. Do you have a current work schedule?
Haha Yes, there is some kind of nonsense that is crammed into a calendar in an exendzh server, but it isn’t exactly that to be relevant. And there is no detail of the schedule, which "requires" Joel.
7. Do you have specifications?
I would say no. It happens that some papers are written. If you're lucky, there will be screens to do. If less, then the text with a bunch of ambiguous texts. Often I will just take a look at this, and then put it on the edge of the table, because they are all pretty useless.
8. Did you create a calm environment for the work of programmers?
This item upsets me the most, probably. No, no and NO. Next to the programmers are managers, phones are always ringing, someone is walking, talking. Half of the programmers have disgusting chairs, after an hour of sitting on which the ass becomes square. In general, I would say that the conditions are disgusting.
9. Do you try to use the best existing tools for work?
Let’s say yes. That is, I must say that we have different programmers. And different applications are written in different languages (C #, Java, PHP, Perl) and use different databases (Oracle, MySQL, PostgreSQL). True, I do not know who and what is guided by the choice of languages, tools and technologies.
10. Do you involve testers?
Not. Also a terrible moment. Programmers are testing everything themselves. Then another manager can potestit.
11. Do you offer job seekers to write code during the interview?
Well, when I was interviewed, the second part was the execution of test tasks. The tasks were very simple, they could hardly assess me somehow. Everything that could be said about them, that yes, I at least read the book “PHP in 24 hours”. Spolsky himself advises checking out a little more. But we shall.
12. Do you test “usability” on random people?
No, if the general liked it, then so be it.
Total three points. What about this Joel writes: “Ideally, you should score 12 points. 11 points is a tolerable amount, and 10 or less indicate serious problems. In fact, most software organizations work with only two or three points, and they need major improvements because companies like Microsoft keep 12 points all the time. ”
And how are you?
Apd If interested, then Joel Spolsky maintains a blog “Joel on Software” , based on which books are published.
Apd # 2 Original of "Joel's test" with explanations .
Source: https://habr.com/ru/post/63596/
All Articles