May 21, 2009 at 00:42The second day of SEF in Minsk
Today was the second day of SEF-2009.
The first report I attended was “First Steps in TDD” by Pavel Gabriel, a representative of the agile.by community .
Using the simplest Excel macro, which translated Arabic numerals into Roman ones, the
basic principles of TDD were demonstrated.
At first the test was developed, then its implementation - gradually,
making very small consecutive changes to the code. After each change, of course,
all tests were run.
Two design patterns were named: “faked” and “obvious implementation”, often used in TDD.
After that there was a report “Training of software engineers (Ukrainian experience)”.
The report spoke about the changes in the program and structure of education, which are designed to provide
Ukrainian IT with the necessary professionals. I must say that it sounds quite reasonable, although
there were skeptics.
The following weaknesses in the training of specialists were noted:
1. group dynamics and communication, roles in the project
2. software engineering process
3. quality assurance
4. software engineering systems and tools
I would refer everything except item 4 to our IT education. I consider P4 simply unnecessary - funds
are mastered along the way, if there is a theoretical basis, very easily.
We talked about the transition to a two-stage education (master and bachelor), and about specialties,
and about other official nonsense, which is mainly interesting to aunts and uncles from the Ministry of
Education. I don’t know who else. Well, the teacher and developer from the plow did not see much sense in many important words.
There was one interesting point - internships of IT teachers in leading companies, of course, large.
There is an opportunity to conduct such an internship for the teachers of our department,
although in a small version, in one of the oldest Minsk companies (not EPAM :).
There was a report with a big name “Application Integration”. We talked about the transfer of
customer processes to MS BizTalk Server. The title of the report does not correspond at all, and the problems
of application integration were not discussed at all.
There was a very interesting and lively talk on MediaWiki, an open system on which wikipedia is written.
They even gave us a free flash drive with it. What's on the flash drive, until I looked.
The system is really interesting, I use it on occasion to document the project.
And the interesting phrase “Communication is not information” was uttered,
which went through my callus - for some time I had the stupidity of working in an organization
where ICQ logs were the only project documentation.
Report "Automation of enterprise project management processes." Ha, we changed the schedule and there
was another report about .NET implementation of the solution to some specific problem with XML. Fe to the organizers.
Then I missed a couple of reports, and only came to "Organization of the application design process
in a software company." The report, in principle, is not bad, just does not match the title. About
interfaces, usability and user experince. I liked the division by professionalism:
1. Novice
2. Master
3. A person with his own style of work.
Such p3 move industry, or at least just outstanding personalities, like that.
It was said about the organization of interaction on the project, about the role of designers and other fraternities,
which I do not pay much attention to.
Report "Typical problems of identifying requirements and their solution." Good report.
1. The gap between the Analyst and the Customer
2. "Yes, but ..." syndrome
3. Z does not know what he wants
4. There is no access to Z
5. Z and they contradict each other
6. No Z
7. No documentation
8. Changing requirements
9. Undetected requirements
10. Distributed command
11. Z does not need anything
12. The manual drives forward
13. Many Zs
Here it is. Ways to solve, and techniques for solving problems were shown. Speaker - member uml2.ru .
The latest talk is Agile Analyst. About the gap of analytics in Agile, about what he
can do and how to help the team, about his interaction with Product Owner and more.
Interesting and lively.
All reports will be published, possibly a video will be. Only where, it is not clear.
I won’t go to SEF tomorrow. I will go to "Sun Open Network Systems: Strategies and Resources of the New Age."
Do not kick much for a sloppy code, it's time to sleep, and get up early - you need to take an exam in the morning.
The first report I attended was “First Steps in TDD” by Pavel Gabriel, a representative of the agile.by community .
Using the simplest Excel macro, which translated Arabic numerals into Roman ones, the
basic principles of TDD were demonstrated.
At first the test was developed, then its implementation - gradually,
making very small consecutive changes to the code. After each change, of course,
all tests were run.
Two design patterns were named: “faked” and “obvious implementation”, often used in TDD.
After that there was a report “Training of software engineers (Ukrainian experience)”.
The report spoke about the changes in the program and structure of education, which are designed to provide
Ukrainian IT with the necessary professionals. I must say that it sounds quite reasonable, although
there were skeptics.
The following weaknesses in the training of specialists were noted:
1. group dynamics and communication, roles in the project
2. software engineering process
3. quality assurance
4. software engineering systems and tools
I would refer everything except item 4 to our IT education. I consider P4 simply unnecessary - funds
are mastered along the way, if there is a theoretical basis, very easily.
We talked about the transition to a two-stage education (master and bachelor), and about specialties,
and about other official nonsense, which is mainly interesting to aunts and uncles from the Ministry of
Education. I don’t know who else. Well, the teacher and developer from the plow did not see much sense in many important words.
There was one interesting point - internships of IT teachers in leading companies, of course, large.
There is an opportunity to conduct such an internship for the teachers of our department,
although in a small version, in one of the oldest Minsk companies (not EPAM :).
There was a report with a big name “Application Integration”. We talked about the transfer of
customer processes to MS BizTalk Server. The title of the report does not correspond at all, and the problems
of application integration were not discussed at all.
There was a very interesting and lively talk on MediaWiki, an open system on which wikipedia is written.
They even gave us a free flash drive with it. What's on the flash drive, until I looked.
The system is really interesting, I use it on occasion to document the project.
And the interesting phrase “Communication is not information” was uttered,
which went through my callus - for some time I had the stupidity of working in an organization
where ICQ logs were the only project documentation.
Report "Automation of enterprise project management processes." Ha, we changed the schedule and there
was another report about .NET implementation of the solution to some specific problem with XML. Fe to the organizers.
Then I missed a couple of reports, and only came to "Organization of the application design process
in a software company." The report, in principle, is not bad, just does not match the title. About
interfaces, usability and user experince. I liked the division by professionalism:
1. Novice
2. Master
3. A person with his own style of work.
Such p3 move industry, or at least just outstanding personalities, like that.
It was said about the organization of interaction on the project, about the role of designers and other fraternities,
which I do not pay much attention to.
Report "Typical problems of identifying requirements and their solution." Good report.
1. The gap between the Analyst and the Customer
2. "Yes, but ..." syndrome
3. Z does not know what he wants
4. There is no access to Z
5. Z and they contradict each other
6. No Z
7. No documentation
8. Changing requirements
9. Undetected requirements
10. Distributed command
11. Z does not need anything
12. The manual drives forward
13. Many Zs
Here it is. Ways to solve, and techniques for solving problems were shown. Speaker - member uml2.ru .
The latest talk is Agile Analyst. About the gap of analytics in Agile, about what he
can do and how to help the team, about his interaction with Product Owner and more.
Interesting and lively.
All reports will be published, possibly a video will be. Only where, it is not clear.
I won’t go to SEF tomorrow. I will go to "Sun Open Network Systems: Strategies and Resources of the New Age."
Do not kick much for a sloppy code, it's time to sleep, and get up early - you need to take an exam in the morning.