So, I'm an intern and I'm always eager to learn new things and do new things. I want to give all the knowledge I have to improve the projects at work.
I give a lot of opinions about the projects I'm working. Ways to improve it. I sometimes ask why somethings where done that way, to understand.
My supervisors don't like that.
Sometimes I get very anxious because my life is very fucked up in the moment.
I think no one there likes me.
It's funny because in one of the meetings we had about this at some point in the conversation, I don't remember why, they said that "people are not robots", "people have feelings".
But they are always mad about something I said or asked (meanwhile, everyone else are saying bad things about the projects, about other people, even about HR).
I guess people need to unload their stress into someone.
I just want to finish this internship, get my fucking grade, and get out of this fucking company.

I'm thinking about turning myself into a robot.
A human robot.
I'm only going to say: yes, ok, sure, yes sir, hello, goodbye.
Just work like a robot like they want.

  • 3
    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)
  • 2
    I 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
  • 2
    @shivayl lol. How dare you observe. The nerve of it... ๐Ÿ˜‚๐Ÿ˜‚
  • 4
    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.
Add Comment