The second day of SEF in Minsk
Today was the second day of SEF-2009.
The first report I was at was “The First Steps in TDD” by Pavel Gabriel, a representative of the agile.by community.
Using the example of the simplest Excel macro, which translated Arabic to Roman,
The basic principles of TDD were demonstrated.
First, a test was developed, then its implementation - gradually,
making very small sequential code changes. After each change, of course,
run all the tests.
Two design patterns were named: “faked” and “obvious implementation”, often used in TDD.
')
After that there was a report “Training of software engineers (experience of stolen)”.
The report described the changes in the program and structure of education that are designed to ensure
Ukrainian IT necessary professionals. I must say that sounds reasonably 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 P4 to our IT education. P4 I think is simply not necessary - means
mastered along the way, if there is a theoretical base, it is very easy.
It was told about the transition to a two-stage education (master and bachelor), and about specialties
and about other official nonsense, which is interesting mainly to aunts and uncles from the ministry
education. I do not know who else. Well, the teacher and the developer from the plow did not see much meaning in many important words.
There was one interesting point - internships for IT teachers in leading companies, of course, large ones.
There is an opportunity to hold such an internship for teachers of our department,
although in a small version, in one of the oldest Minsk companies (not EPAM :).
There was a report with a loud name "Application Integration". Told about the transfer process
customer on MS BizTalk Server. The title of the report does not correspond at all, and about the problems
application integration was not told at all.
There was a very interesting and lively report on MediaWiki - an open system on which wikipedia is written.
They even gave a free flash drive with it. What is on the flash drive, while not looking.
The system is really interesting, using the case for documenting the project.
And the interesting phrase “Communication is not information” was uttered,
who walked through my corns - for some time I had the stupidity of working in an organization,
where ICQ logs were the only project documentation.
The report "Automation of enterprise project management processes." Ha, changed the schedule and
There was another report about the .NET implementation of solving a specific XML problem. Fe to the organizers.
Then I missed a couple of reports, and only came to "Organizing the application design process
in a software company. " The report, in principle, is not bad, but it does not correspond to the title. About
interfaces, usability and user experince. Liked the division of professionalism:
1. Newbie
2. Master
3. A man with his own style of work.
Such of p3 are moving the industry, or at least just prominent personalities, like that.
It was said about the organization of interaction on the project, about the role of designers and other brethren,
which I do not pay special attention.
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. does not know what she wants
4. No access to W
5. W and protect each other
6. No W
7. No documentation
8. Changing Requirements
9. Undiscovered requirements
10. Distributed team
11. No need for anything.
12. Leadership drives ahead
13. Many W eats
This is how it is. Solutions were shown, and problem-solving techniques. The speaker is a member of uml2.ru.
The latest report is “Analyst in Agile”. About analyst's prol in Agile, about what he
can do and how to help the team, about its interaction with the Product Owner and so on.
Interesting and lively.
All reports will be published, perhaps, and the 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 time."
Do not kick much for an inaccurate code, it's time to sleep, and get up early - you have to take the exam in the morning.
The first report I was at was “The First Steps in TDD” by Pavel Gabriel, a representative of the agile.by community.
Using the example of the simplest Excel macro, which translated Arabic to Roman,
The basic principles of TDD were demonstrated.
First, a test was developed, then its implementation - gradually,
making very small sequential code changes. After each change, of course,
run all the tests.
Two design patterns were named: “faked” and “obvious implementation”, often used in TDD.
')
After that there was a report “Training of software engineers (experience of stolen)”.
The report described the changes in the program and structure of education that are designed to ensure
Ukrainian IT necessary professionals. I must say that sounds reasonably 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 P4 to our IT education. P4 I think is simply not necessary - means
mastered along the way, if there is a theoretical base, it is very easy.
It was told about the transition to a two-stage education (master and bachelor), and about specialties
and about other official nonsense, which is interesting mainly to aunts and uncles from the ministry
education. I do not know who else. Well, the teacher and the developer from the plow did not see much meaning in many important words.
There was one interesting point - internships for IT teachers in leading companies, of course, large ones.
There is an opportunity to hold such an internship for teachers of our department,
although in a small version, in one of the oldest Minsk companies (not EPAM :).
There was a report with a loud name "Application Integration". Told about the transfer process
customer on MS BizTalk Server. The title of the report does not correspond at all, and about the problems
application integration was not told at all.
There was a very interesting and lively report on MediaWiki - an open system on which wikipedia is written.
They even gave a free flash drive with it. What is on the flash drive, while not looking.
The system is really interesting, using the case for documenting the project.
And the interesting phrase “Communication is not information” was uttered,
who walked through my corns - for some time I had the stupidity of working in an organization,
where ICQ logs were the only project documentation.
The report "Automation of enterprise project management processes." Ha, changed the schedule and
There was another report about the .NET implementation of solving a specific XML problem. Fe to the organizers.
Then I missed a couple of reports, and only came to "Organizing the application design process
in a software company. " The report, in principle, is not bad, but it does not correspond to the title. About
interfaces, usability and user experince. Liked the division of professionalism:
1. Newbie
2. Master
3. A man with his own style of work.
Such of p3 are moving the industry, or at least just prominent personalities, like that.
It was said about the organization of interaction on the project, about the role of designers and other brethren,
which I do not pay special attention.
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. does not know what she wants
4. No access to W
5. W and protect each other
6. No W
7. No documentation
8. Changing Requirements
9. Undiscovered requirements
10. Distributed team
11. No need for anything.
12. Leadership drives ahead
13. Many W eats
This is how it is. Solutions were shown, and problem-solving techniques. The speaker is a member of uml2.ru.
The latest report is “Analyst in Agile”. About analyst's prol in Agile, about what he
can do and how to help the team, about its interaction with the Product Owner and so on.
Interesting and lively.
All reports will be published, perhaps, and the 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 time."
Do not kick much for an inaccurate code, it's time to sleep, and get up early - you have to take the exam in the morning.
Source: https://habr.com/ru/post/60092/
All Articles