- Do some research before asking a question. At the very least you should google a few keywords and look at the first 5 pages before raising it with someone els

- Do some research before asking a question. At the very least you should google a few keywords and look at the first 5 pages before raising it with someone else. - Don't ask things you can easily find yourself. I've had junior engineers asking me "does git blah has a flag for ...?". It's disrespectful of that person's time. - Don't question every tiny little thing you come across. Organisations can't maintain perfection, there's gonna be ugly things and people are aware that there's always room for improvement. Sometimes there is complicated history behind things that look stupid on the surface. Some things are the way they are just because they are. Not everything has some grand reason or justification behind it. Sometimes people keep asking questions like "Why was this written this way? Why was it not written that way? Why can't we make it better? Why can't we make it faster?" - Remember the ugly crap you are seeing today was someone else's shiny shit some time ago and you are not an exception. The cycle will continue and the perfect little happy function you are writing today that's gonna solve everyone's problems is going to be the next person's ugly crap to rewrite and refactor and clean up after you have moved on.