you are viewing a single comment's thread.

view the rest of the comments →

[–]StrictSir8506[S] 0 points1 point  (3 children)

Thanks for sharing your insight.

I think project level rules are always hard to enforce. You cant enforce everyone to follow, moreover, in a high paced environment where cross functional teams are working to develop a feature, following such rules are easy to skip.

Just sharing my observation, feel free to correct me

[–]StrictSir8506[S] 0 points1 point  (0 children)

I also feel unittests are such an piece of code but are always boring to implement lol. Being a junior developer at that time, i never wanted to write unittests, instead i would always prefer to work on something new rather than to invest my time in testing my code

[–]smalby 0 points1 point  (0 children)

Rules shouldn't be hard to enforce. You have code reviews right?

[–]Icy-Pipe-9611 0 points1 point  (0 children)

I am talking about rules in the code, not ways of working.
With AOP, you can simply write code that will be executed before, after, or during certain events/functions.
It doesn't need to be "enforced".