Hi Best practices varies depending on the project & team size. What's best for team of four might be bad for team of 100 or for single developer. For example s

Hi Best practices varies depending on the project & team size. What's best for team of four might be bad for team of 100 or for single developer. For example source control, when I work alone I used it mostly as history of my code and backups but don't care too much about branching, but when I work on something bigger with e.g. ten people involved it's almost impossible to work without setting some rules about that. Agile is becoming a standard for bigger teams, but it also might be bad for some types of the projects. If you join any agile driven methodology you can pick up basics in like one day and then just follow up - I wouldn't worry too much about it. Unit testing from my perspective is really crucial even for small projects developed by one person. On the top of unit testing it's at least good to read a about BDD / functional / integration testing to understand how you can test your code even if you find out it's too much for you. Microservices is another trends worth to read about but it also doesn't mean that you should create every project using microservices/SOA. Best practises are the very open topic, it is hard to know without knowing what kind of project or languages do you use. You should also keep in mind that following trends might be good or bad if you don't understand what you want to achieve - I saw many projects killed because over engineering. From my perspective code is good as long it is simple. I think the best source of knowledge is following technical blogs related to language you are using or industry.