Where in Moscow can you get practical skills in the technical organization of the work of the development department (priority in PHP)?

Question

IT education

The very essence of the question is indicated in the title, if in detail, then the full stack is of interest:

1. task management (board, redmine, jira?)
   
2. organization of a devel environment (one server or virtual machines, code access and subdomains)
   
3. code management in git (how many branches and who merges where?)
   
4. organization of code review (programs, pre- or post-moderation?)
   
5. organizing automated tests (Unit and/or BDD, codeception, selenium, how to test a DBMS?)
   
6. organizing a CI server with Git hooks to run tests, check the code style and deploy to a test domain.
   
7. is it possible to organize branches in git, code review and autotests, so that one developer's crooked commit does not stop others? Ideally, I would like the developer to not be able to merge their commits into a common branch, without code review or with failed tests, how to organize feedback in this case?
   
8. logging and monitoring servers
   

I note that if we consider each issue separately, then of course there is a lot of information on the network (and there are even more holivars), but with a full working stack: from the task to the developer to the release, it’s already more difficult, I want to “feel with my hands” a working sample.
Maybe there are suitable paid courses, maybe some companies organize seminars or open days for money?
Thanks in advance for the replies.

Answer 1

Where to get practical skills...?

Oddly enough, only in practice.
Any experience shared with you will be subjective and specific in any case. It is necessary to understand just the fundamental (read theoretical) approaches. They will come up with "practical" solutions depending on the situation. The development process in each case may be different. He must be flexible, adapt to changes, solve emerging problems, etc.
An open day is unlikely to help. You don't want to look at people sitting at computers, do you?
In general, I can share our experience (in some skype). We closed the questions for ourselves on all points long ago. Lately I've been thinking about writing an article on all these and similar issues.

Answer 2

throw your uncertainty, just talk logically and how it will be convenient. and google the tools.

Answer 3

It's unclear what experience you have in development. If for you all these are abstract points that need to be done, the courses may not help, trust the main developer. If not, feel everything with your own hands.
The organization of a code review depends on the level of people. Automated tests are generally an extensive topic, under which one more department can be singled out, the tools and approaches are very extensive.
With strict settings such as full code style, autotests and reviews, you need to take care of the developers' time management first of all. If they write the tests too, and they also review them (each commit), ~20% of the time will remain for the functionality.

Answer 4

in fact, there is no 100% template methodology, basically everything is formed by trial and error, taking into account the specifics of the business. Therefore, if one scheme will work in one company, then it is not a fact that it will suit you.
it is best to identify the problems and try to solve them individually.