Why KaufmanICT?

По-русски

• Risks are minimal
• Success chance is maximal

Primary Competitive Advantages

1 Solid experience in project management combined with high programming qualifications

· working in programming 50+ years, Doctor of Physical and Mathematical Sciences, former full professor of Lomonosov Moscow State University

· repeatedly had to salvage projects, including international

2. Ability to productive business activity in the field of the latest technologies

· most recently conceived and implemented several non-trivial programming services, and also mastered blockchain-technology

3. Explicitly formulated base of constructive behavior in the rapidly changing world

· Employment niche for capable veterans, Habitological analysis, Natural properties (axioms) of the Web, Social Axioms, Registration revolution, Commandments of programmer,  etc..

Details below.

Employer vs. contractor

Nearly all my life I was an employee. My first 50 years I lived in USSR, where that was the only option for people like me. The situation was changed in Finland when I was 68 (the retirement age here). My employer wanted to continue our productive cooperation but said that it would be better if I would open my own firm and we would continue our cooperation nearly in the same way but formally as a contractor and a private entrepreneur, not as an employer and an employee. This way I became a private entrepreneur having my own small firm KaufmanICT. It was better for my contractor since the firm saved money and got more freedom (no need to pay in corresponding social funds, no trade union restrictions, etc.) and it was OK for me since I lost nothing following our new contract  (I has the same payment, the same working environment, etc.) . So, a contract with KaufmanICT could be much preferable for our potential contractor then a direct contract with Vitali Kaufman as an employee. You would get the same kind of ICT procurement but without any additional legal restriction. If you would satisfied by KaufmanICT, no problem to continue , if not, no problem to cancel the contract.

Recent working environment specifics

The most important recent preference in the field ICT procurement is a remote cooperation (specially,  the results delivery). Of course, «real world» meetings could be still important and productive but they could be much more seldom than before. So, in our case it means that contractor location is not essential in practice (if contractor is interested in results, not in anything else).

My personality (KaufmanICT specifics)

What I can do much above the average (resume):

• Select a great point in an idea, project,
• As a professor of in Moscow State University, I participated in many professional USSR-wide meetings.  It was happen many times, that my reformulation of the speaker results was much more clear for the auditorium then the original speech.
• This way I could help to my students and post-graduate students ( I was a scientific supervisor of 11 Ph.D on Computer Sciences ).
• Evaluate of projects, ideas, presentations
• I was involved in evaluation of not only dissertations or presentations, but also project propositions and projects as the whole. In result I have now my own collection of relatively simple criterions that helps me to make a reliable evaluation even in a very strong resource restriction.
• The following sample is related to my participation in ISO-IEC/JTC1/SC-22/WG-9 — Programming Language Ada.
• When we had a meeting in Frankfurt in 1991, we had to vote many times for propositions by representatives of different countries (by the way, that time a was a representative both USSR and Finland :).
• A representative of Switzerland asked me privately how could I vote so quickly, reasonable and meaningful, having a need to follow so deep professional discussion by native English speakers.
• I had replied that I had a very simple criterion for Ada language: «if a proposition could make the language teaching easier, I votes Yes, else I voted No».
• Another sample is related to my evaluation of a project by Siemens to Nokia. My conclusion was that the project was bad. As I know, the project was finally rejected by Nokia.
• Invent some new ideas
• I had invented a lot of promising ideas. Some became subject of my first and second doctoral dissertations, and also dissertations of my post-graduate students. I am collecting my ideas for years. Some are still actual. I would be glad to discuss them with potential partners for joint realization.
• Make ideas working
• All my programming projects were finished having working program as a result.

• One of the last samples — Vicita
- an implementation of my idea of common internet tool for video citation (allowing deeply structured contents).

• Vicita is made by me at 2014 and is improved essentially at 2018.
• Another sample of my recent (2015) project - LIS (Light Instrument for internet Surfing).
• Integrate of systems based on completely different platforms
• I have an expertise in many completely different programming and mathematical fields - from operational systems and translators to program correctness proofs, from Ada language teaching and international standardization to PHP programming, from project management and evaluation to work in computer operator role.
• By the way, the last was not a kind of exotics but an essential part of my work as a project manager. It helped me to realize of every essential problems in the team cooperation.
• Such background helps me to integrate successfully of systems having completely different platforms and time of creation.
• Salvage projects that seemed catastrophic until I got involved
• Representative samples as follows.
• A team in Research Computer Center (RCC) of the Lomonosov Moscow State University, leading by Evgenij Zogolev, was working in 1965-1970 on a multi-language modular programming system SIMPR, a time-sharing operation system and a compiler for modular extension of Algol 60 (SALGOL) for the Russian computer BESM-6.
• This was a joint work with  JOINT INSTITUTE FOR NUCLEAR RESEARCH (JINR) that was responsible for Fortran 66 compiler for the system.
• Unfortunately, there were no working system from RCC for several years. The RCC leadership thought the project state is catastrophic and it was crucial to make the system working to preserve the partnership with JINR
• I was invited as a young "emergency manager" to help the team to make the system working very shortly, in several months.
• We worked in extremely intensive way, implemented several special methods to improve the team member cooperation and effectiveness.
• That time I was invented and used successfully my personal management method for such kind of emergency situation - to work simultaneously on several levels of the project - namely, in this project, as a project leader, as a computer operator, a tester and an analyst. In result, every morning every team member had got test results having my notes related to his (her) bugs  that I had found at night
• This way I could do my best for the project team and simultaneously my "live sample" was the best way to improve all team members personal responsibility.
• Our system was made working exactly at the prescribed date.
• Some basic ideas of the project are worth to underline, especially comparing to well known .Net Framework released in 2002 only.
• SIMPR was invented by Evgenij Zhogolev to provide language interoperability (each language can use code written in other languages) across several programming languages (that time there were an assembler, SALGOL and Fortran 66). Programs written for SIMPR should be executed in a language independent software environment (a semantic level runtime), supported by a language independent library and a dynamic loader.
• Now it is quite obvious, how promising were the ideas by Evgenij Zhogolev.
• Unfortunately, these promising ideas were not understood that time by our leadership. The partnership with JINR was canceled. The JINR had released a very restricted version of our joint system having just a single Fortran compiler, and the system (DUBNA) was used in the USSR for many years.
• I saved also of the X-Change project /at least the I_GUI related part) that seemed catastrophic until I got involved.
• X-Change was an international (EU) project - Flexible Change Management for the Factory of the Future. Teams from Germany, France, Greece and Finland were involved. More details about the project could be found in my resume.
• I've realized that a key point to help the project survive was to create a set of debugging web services that would model partners web services, The model services help us to separate our work, to help us move ahead without waiting when all partner services would ready to join.
• The last story, by the way, shows that I can quickly understand a complex (international in this case) project, estimate the project, set correct priorities, invent and implement crucial solutions, and finally save the project.

What I'd want:

• Collaborate with a structure that have serious intentions and serious opportunities
• Help the structure to evaluate successfully
• Create promising projects and make them successful

Directions of collaboration where my knowledge and skills could be especially productive:

• Analysis, invention and evaluation of ideas
• Testing (especially blockchain applications and smart contracts)
• Programming projects evaluation (especially in early project stages)
• Distance education (including management of qualification works of students and post-graduate students)
• Integration (including legacy systems)
• Super-vitality systems
• Web services
• Localization, translation, editing
• Standardization

So, why KaufmanICT?

• Risks are minimal
• Success chance is maximal

Some links:

• Resume
• Vicita
• Habitology
• Habitological analysis
• LIS
• KaufmanICT_Integration_Mapping_Web_Service
• Intellectual Value Laws: a Sensible Alternative to Intellectual Property
• Social Axioms

17.2.2023

Comments and suggestions would be appreciated. You can send them to Vitali Sh. Kaufman.