These days I have been reading a lot. Mainly about whether I want to leave this company. This is not a happy job to me, sometimes I even feel pain when dealing the code, where the same code piece being copied over and over again, and spring's autowire give them the opertunity to invoke anything at anywhere.

The conclusion I got is: bad practise can always have excuses, and good practise is always a right thing to follow. If the company keep saying things like "clients are important" to deliberately avoid following the right thing, I think I'd just leave no matter what.

As always, I want to learn different views, so any comments are welcome, feel free to judge me.

Follow

By "following the right thing", I mean, with current bad code base, with limited delivery time from clients, at least set up a basic rules on how to write normal code. Just stop copy and paste the code when you need it, instead extract it into a method or function. Try think a little bit before writing, try to considering the future.

Today when I saw a spring controller imported both the service and it's implementation class, I was shocked.

Someone think the service is not exposing enough details to do the task, so instead of designing new functions, he just autowired the impl class and skipped the service interface.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.