I have also started several side projects and never finished any of them. The problem for me was that when I solved the most important problems, I lost interest in it. This year I'm trying something new and I hope to overcome this barrier. So I can imagine your situation. I wish you to choose a project that you will enjoy and find fulfilling and see it through to the end.
I have been programming for over 20 years. I've developed everything from small in-house applications to systems in critical infrastructure... But the working mood and work deployment depends mainly on the setup of the internal company policy :)
Depending on the type of project, sometimes 70% of the time is programming and 30% is consulting with the team. Other times I do 60% design and 40% programming. It's project by project. For me, most projects are greenfield development. Some of them don't even come to fruition after weeks of designing and are lost. The main thing is to do your job the best you can.
Try looking for positions as a developer in industry or look around for companies that have contracts for industry. Such as power plants, heating plants, any other manufacturing plants...
I wish you good luck.
It's true, the beer in Prague is excellent. Overall, I like the beer culture in the Czech Republic. The language is easy to learn, especially if you are from Slovakia like me :)
I would like to say hello to Prague.
Personally, I encounter long functions (as you described, around 100 lines) mainly in older codebases that were written over 20 years ago. In many cases, I get them for rework when developing new software, particularly in industries where the adage is 'if it works, don't change it.' This phenomenon could be attributed to the fact that, at that time, OOP was just emerging, and developers were not yet accustomed to it. I strive to write code that is concise and highly readable. It's important that the function's purpose and usage are immediately evident at first glance, rather than relying on copious comments.
I think the difference between a long function and many short functions that are not reusable is not big. A long function can be cluttered if it is really too long, and also many small helper functions can bring confusion to the code. The advantage of short functions can be their testing, or the division of work in the team. Anyway, if too long functions or too many one-call functions start to appear in the code, the code architecture should be reconsidered.
Invest in yourself, especially in your education when you are young and able to devote yourself fully to education. All the money you invest in education will pay off by opening up new possibilities and paths in life, better employment and earning opportunities.
Most programmers and IT professionals are so busy working, learning and keeping up with rapidly changing technology that they don't have time to focus on global and social issues. Today, a programmer is like a slave-worker, only no one is beating us with a whip. :D
First, quickly go through all the documentation. Then start writing whatever comes to mind. And if you don't understand something, go back to the documentation. For me, that's the best way to learn.
I have a smart home system written in Python that collects data from mqtt, evaluates it and stores it in Postgresql. On top of that I have a web application in PHP through which I control the whole thing. And I would like to rewrite this into Rust, I would like to learn Ricket, Actix, Yew, or something similar.
As already described, it depends mainly on what you enjoy, so that you don't get tired of learning new things. As far as the job market is concerned, knowing only one skill is not an advantage, it is best to excel in a certain combination of skills. And it seems to me that Rust and Machine Learning go together. You can learn the basics of Rust quickly, especially if you already know other languages. How quickly you can understand ML, I don't know, it seems to me to be a very broad term.