While I was sleeping, in one of the chats there was an active discussion on a number of issues on which I would also like to speak. I'm afraid that everything will not fit into one message, therefore I will issue it as a separate post. So let's go.
It's just that I'm like a child in a toy store - my eyes run wild. I took up yap, but here you need to learn both English and git and some kind of springs, etc. Everything is interesting, but how to combine this and at the same time learn effectively is not clear
Here I can answer with an old anecdote
- Sophie, what will you drink: alcohol, vodka or moonshine?
- Oh, I don't even know, everything is so tasty ...
I see three solutions to the problem of chasing a herd of hares:
The first method is outrageously simple: do not strain your head with any goals, tasks, plans, deadlines and other attributes of "adult" development. And to deal with what is interesting specifically at the moment. It's interesting to touch Spring - touch it, learn how to resolve conflicts in Git - learn, master the use of perfect tenses in the American language - master it. Tired of - put it on the shelf and returned someday when this topic again became relevant in terms of interest. And I can't say that this method is completely useless. Because the study of anything will be fueled by a lively interest, then less effort will be spent on it than in the “necessary” mode, and through this the assimilation of the material may be better. And let a set of knowledge, often superficial, from different areas be obtained,but sooner or later comes the skill of combining this knowledge to create something new. Of the minuses of this approach, I can note the danger of becoming an "ultra-wide profile lamer" when you know a lot of different things, but just a little bit. Another danger lies in the fact that there are too many fields of knowledge that are interesting and we again return to the original problem of “what to drink”.
: “ ”. .. , . Git- — , Spring — , // / — . , , - . . , , -, -, , , - , - .
. .. , , , - / . , - , . , , , - /, . , , , , , .. , — - . .
- , . , . 100500 SMART. ? , ? , , .
?
, : “ / -?” / - . “ ” , . :
TeamCity Kotlin DSL. , . Kotlin TeamCity DSL, - . , .. .
Kubernetes/Helm. , . . .
. , “ ”. : , , , .. , , . , - .
Vim. . - , . …
, -. , . ? . .. DevOps-, , Kubernetes. , . .
If you briefly summarize all of the above, then you can see that with motivation and the right approach, gaining new knowledge can be an interesting and enjoyable process, not always simple, but no less attractive. And a good engineer is distinguished by the ability to find this motivation (internal or external) for himself and to choose the way of acquiring knowledge that is best suited for solving a specific problem.