How to organize the development process alone?

Question

Work organization

In fact, this question has been raised more than once. But he did not touch on some of the topics that interest me.
If you are developing one, is it necessary (justified) to:

1. lead a project using Scrum or Agile methodologies
   
2. implement GitFlow
   
3. use the practice of continuous integration (CI)
   
4. deploy projects via Docker
   

Now everyone and sundry talks about these things. And everyone shouts in one throat that this facilitates the development process.
I tried to figure out all these new technologies and methodologies on my own. And if I understand everything about Agile and GitFlow, then I had difficulties with other things.
As a result, I had a question, do I need this, a person who is developing alone?
It would be great if you share your development experience alone.

Answer 1

CI yes.
More automates tedious testing. Simplifies the laying out of new versions. Your work will be easier, you will make fewer mistakes.
Docker fits nicely into CI. Moreover, modern software implies containers for CI. Typically this is Docker.
Agilie, gitflow, etc. methodologies are meaningless. When working, teams make sense. When working in one - inside your brain, you are much faster and much better to agree.
The order in Git makes sense even when working in the same
PS gitfow and CI are contradictory things.
Gitflow is about cumulative releases. And their support (hotfixes).
And CI suggests the exact opposite - continuous change. No explicit versions
Gitflow is well suited for releasing, for example, certain versions of Linux (which is what git was created for), a full gitfow is appropriate here.
While, for example, GitHub is constantly updating itself and therefore dispenses with gitflow.
Proof https://m.habrahabr.ru/post/189046/
I doubt that a single developer can support several different releases (this is what gitflow is for)

Answer 2

Methodology - no
workflow and CI - yes
docker - perhaps
Methodologies are needed in order to organize the work of the team on the project. Basically - to minimize downtime in the team, increasing overall productivity.
Alone, you can try to imitate the self-organization of the team, but since there will be no visible result in this, you will quickly get bored. For example, a daily stand-up where everyone shares what's going on with each other would look silly in a one-man team.

Answer 3

1. Leading a project in Scrum is justified:
a. You can prioritize your tasks. Pretty things - small, that which will allow you to monetize faster - big.
b. Low priority user stories can be your idea pad.
2. This is optional.
If your project is already making money, then you should rather, as you will need to make quick fixes
when you are currently developing new functionality.
3. It's more for teams.

Answer 4

Hello.
I think that, even when developing alone, GitFlow is already necessary (if I understood everything correctly, this is version control).
I guess solo development is a start, because. large projects alone cannot be carried away and knowledge of the Scrum / Agile and CI methodology will not be superfluous.
Deploy projects through Docker: I'm actually just trying to master this product myself, because. For many employers, this is already the standard.