I'm from Bosnia and I can understand almost everything. There are some words where I have to stop and think but in the end, it's completely understandable. This is a great idea!
Because in EU, to reach the consensus or any agreement on anything, between all countries and then to review that 1000 times through million of EU Commissions, takes decades :)
They first have to love each other, to have common goals and then maybe something will happen. Right now most of the EU countries are there because of the cheap loans, donations, cheap work force and free exchange of resources. Once that flow is stopped, EU will be the past. EU is simply not operating as a one unit, it's not balanced union, that's why I think there has to be some mindset change in order to move the EU forward and to bring big projects to reality.
Survey completed! Maybe a bit off topic, but it would be good to create a list of music artists or bands that programmers listen the most. I'm always thinking about how Pink Floyd for example helped me a lot to finish some important tasks and how their music helped me multiple times to bring myself in to the zone :)))
I have tried a lot of times to enforce the code reviews because I have seen lot of bullshit being checked in to the source control but if you don't have support from other team members then even having the code review is waste of time. Code review should come from the gut feeling, you should be always self critical and let your code being evaluated by other people who care about software development in general and not by the people who just want to make their job done and to have something to mention during the stand up meeting.
So depending on what kind of people you are surrounded with, you should decide is it worth to do it or not.
Code review is not a task or ticket, it should be more natural in all teams. Like it's normal to take a shower or brush your teeth, it's also normal to do code reviews and keep the code clean and good. But recently most of the teams are just skipping everything to make managers and owners happy. And they are always happy with beta, preview or even prototype - so sad.
Unit tests are something else. Good, clean and testable code starts from good and clean requirements that are easily understandable. From there you are able to write clear unit tests and imagine the whole story. If your manager or someone who is defining what needs to be done doesn't have the clear vision or plan then you have a good chance that your code will be bad - then unit tests are implicitly bad.
Well if you want to have recruiters attention and to have your resume look "populated" it might be a good idea, but the one who is deciding if you will get a job, or how high your salary will be, usually doesn't care about certifications. Your best weapons are your references and skills.
This is a really interesting topic. I think almost every developer dreams about his own business or product. I personally don't see that sitting minimum 8 hours per day for someone else makes sense, but on the other side at the same time, you are safe, someone else takes care about lot of things for you.
It's hard to project any path which leads to own successful business. So far what I have seen is that only thing that counts here are balls, if you know what I mean :)
One of the ways which is reasonable for me, is to first try to switch to freelancing and there you can test and see are you actually able to take care about lot of things that are usually done by the company, and btw those things are not coding. With your experience and knowledge you should be able to find really good freelancing jobs or you can even try to join some platform for freelancers...
Being a freelancer is almost the same as starting your own business. Later if you see that you can earn lot more money or to hire some geeks, just open a company and take a next step.
How you feel right now it's completely normal and expected because you are young and you want to learn and gain knowledge. I have changed 4 companies because I was searching for the job where everyone is writing clean code and where best practices, code review, and learning are on the high level. You can forget about that because managers don't care how your code looks like, or if you are using best practices to achieve your goal. Now what I'm doing, I'm trying to get as much as possible time on estimates, that's how you can have time to write clean code, and to learn something. If you are estimating the task, add also the time you need to review what you did and do not be scared of refactoring, if you see that something is written in a wrong way, rewrite it, don't blame around :).
Also, work and learn at home. That's your time and you can learn and do whatever you want.
Keep in mind that there is no job where everything is perfect, so collect all negative things you have at the current position and try to change them. If that's not working then leave :)
What managers love is the example and real POC. So if you think that something is wrong or old, create a POC, make a demo. That way you can get some time and resources to do something new and interesting. Don't think someone will give you such project just like that :)
Such a fantastic answer! Kudos, I share similar views.
To add to what you say, I also believe that while we easily start hating our jobs most of the times, we often fail to realize we were never excelling at them.
When I come to realize that I am currently not enjoying my current role, I think of only two possibilities. I either put in my time and efforts to make myself better at what I am doing or simply do something better that would make me enjoy my job.
