Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Even if you think you know the stuff, it's a really bad idea to criticize existing projects when you're starting a new job.
When everyone talks trash about projects it doesn't mean that you should. Remember, you're an intern / trainee. Listen, learn, improve.
If you want to "criticize" a certain aspect of the project, there's a tip:
Instead of saying that everything is trash and implemented in a wrong way, take a step back and ask why it is implemented in that way and not in the other (as you have been taught / used to do at previous jobs / etc)
shivayl14731yI don't criticize. I just give opinions and ask questions. I don't trash anything.
For example, last one:
I see that who developed the app (bank) was storing the menu items on the DB and then fetched them and created the menu on the front (.net mvc).
I just said "wow, ok, that must be expensive, getting all those records every time a client hits the page".
He responded "that's how it was done" with a mad face.
Then he told my supervisor
TL;DR: people get tilted if you somehow "attack" the result of their work and thus their competence, where attacking has a highly subjective definition. A simple question may be interpreted as an attack.
@shivayl telling the supervisor instead of explaining why it is done in that way is not really mature from him. Also a possibility that he was triggered by your statement that it must be slow (read: his implementation/competence bad) without knowing about the circumstances and requirements (maybe the customer wanted configurable ui, stored in DB, or the feature has been implemented during unpaid overtime 2 hours before the deadline).
Once I said everything I thought about the implementation of a particular legacy component. Loudly. And the guy who implemented it turned out to sit in the same room. He was not that happy.