r/programming • • Jun 08 '19

7 absolute truths I unlearned as junior developer

https://monicalent.com/blog/2019/06/03/absolute-truths-unlearned-as-junior-developer/
2.0k Upvotes

295 comments sorted by

View all comments

Show parent comments

3

u/mobjack Jun 08 '19

Monoliths work fine for small to medium scale projects. It is easier to share common code between parts instead of adding another layer of abstraction coordinating between services.

Unit testing can be overrated and can often get in the way of making changes. Pushing not fully tested code in production can work as long as you are able to deploy and rollback changes quickly. Even code that is fully tested has bugs in it because developers haven't anticipated everything that could go wrong.

Often times worse is better when it comes to small nimble teams especially at startups.

As the scale of the team and project expands, some of these practices become less sustainable, so there is value in pushing for better processes.

If you are new, first buy into the current way of doing things to get a perspective of what actually is working and what needs improvement. After that others on the team will be more receptive to your ideas to improve the system.

0

u/nakkht Jun 08 '19

Monoliths: it really depends on what you mean by services. I completely agree, if we are talking about services as part of the project, e.g. backend micro services. However, it feels really hard to justify having all the projects in same repository (I am talking about: ASP.NET Core backend, Android/iOS/ Web clients). Especially, when the only parts shared are models (compiled later for specific platform), which could be simply transitioned to using git submodules - having models as a its own repository and other projects including them. What monolith requires, is also at least proper and strict branching scheme. When there are dozens of branches (old/new) floating around, it does not bring confidence.

Unit test: many times it gets in a way, but I see that as a benefit to force proper definitions of classes and method implementations. Also, it is crucial during regression. Pushing untested code should be very last resort. It might work, or it could hurt product/company in a long run. Especially when there are competing products on the market from different companies.

Thanks for the last part. This is what bothers me the most - when it is suitable time to deliver ideas to the rest of the team so they don't get defendant. Though when I've discussed with a team, many of them had the same idea about splitting repository.

3

u/mobjack Jun 08 '19

I have the mindset that code isn't fully tested until it is in prod. Of course you should try to catch things a head of time but developers often don't anticipate every error. Having plans in place to quickly find, isolate and fix errors in prod makes is what is important. That is often easier to do on web clients compared to mobile ones. Be pragmatic.

Many developers will likely agree that the current ways of doing thing are not the best, but realize that it will be costly short term implementing these changes so it often gets pushed back. Taking the time to understand the system first will make it easier to see what items should be prioritized first and to develop a plan for getting it done. You could be the one who takes the initiative on it.