6 ways to go to hell of ready-made solutions and lower a million or two

Hi, now I’ll tell you what will happen to a promising project, if from the very beginning I turn to ready-made solutions a la Wordpress, Open Cart and any CMS, thinking that this is MVP. I will be based on a three-month experience working on one of the projects on GitHub which over the previous 8 months has not dropped a single commit in the production branch.

Recipe for bloated VP / OC / CMS to geostationary orbit

1. Choose any ready-made CMS

In no case do not call architects and forget about microservices and architecture tailored to your needs. Our task is to make it possible to twist the admin panel already 5 minutes after the developer turned on the PC, and not to make development easy to manage. A true MVP should consist entirely of turnkey solutions. After all, it is in our project that plugins will never conflict and are already designed for loads of any intensity.

2. Prohibit documenting anything

Not a single cms needs to be documented. Prohibit documenting anything. Especially kernel modifications. After all, after 3 months the freelancer turns into a keeper of sacred knowledge about how this emerald dumpling works, and with the magical techniques of starting a server, which, naturally, is one, and no one has recreated it since the initial installation of the set of utilities. The key to decent management is dependence on employees and, of course, on a single working server.

3. Call GURU!

After the fixes for conflicts between the 234 and 417 plugins began to take at least 10 times longer than the introduction of new functions, your right way is to look for a GURU, wise by experience, who will effortlessly refactor (rewrite) a little code in a week, and the next 500 plugins will take their rightful place. By the way, I was “lucky” to be in the role of a guru who turns technology, and therefore this is a real medical history.

4. Your project should consist of one area of ​​responsibility

We safely and consciously put on microservices from the very beginning, and after 5 months it’s time to hire a new programmer. And let him be responsible for layout. Well, a little bit more for the backend, because we have them mixed. Well, for databases, because how to answer for a backend without databases. Well, let’s be responsible for the fixes. And more ... and more ... and more ...

5. Trello + Jira + Slack + Excel + ... + Skype

Thanks to the good one and a half thousand plug-ins that ALREADY exist, there are 5 errors every day, the resolution of which requires 2 days. The writing speed of features decreases exponentially. Obviously, we are thrown for a while developed. And you need to introduce a third task manager. (Yes, clinical projects usually have two task managers). Trello, Jira and Excel are just the foundation of control. Some wizards also use intra-corporate task managers, pinned chat messages and unplanned sudden instructions.

6. Transcripts of voice conferences

Developers lead us by the nose, and therefore all voice conferences for the approval of bug fixes need to be archived, saved to the cloud and regularly listened to. After all, it is always up to developers ...

Tip 1: Testing was successful - urgently discard ready-made solutions and write a suitable architecture.

Tip 2: If you are not just a motivated startup and you have either resources or a financial strategy, then be sure to include in it writing from scratch. Anyway, give this matter to professionals or the technical director. (It is important that this was a programmer, and not a professor from a research institute, otherwise you won’t get a punch card)

What if ALREADY and you are in charge?
- Rewrite.

What if ALREADY and you are not in charge?
- Explain the essence of the problem to management and rewrite.

PS The project used Yii2, but even with it there were these problems. What happens to WP is a disaster at all.

PPS The reason, of course, is the incompetence of management, although the monolithic architecture also does not stand aside.

Also popular now: