How was your first day at work?

Question

Programming

Tell us about your first day at work. The answers of programmers will be especially interesting.

Answer 1

- every first time you came sleepy
- the first day is relaxed (and I thought that they would harness it)
- specialists are a myth (we all cook on water, I mean in a search engine)
- no one requires anything from you (requires, requires and requires a desire to study)
- everyone I wonder what kind of pepper ( friend or foe )
but just do it differently, it used to be good, and that I wanted to quit immediately (they promised mountains of gold, but in reality &%#?! )
but what has always and everywhere been -> here is your computer , install any software that you need to work, etc.
that's all) and good luck on the first working day, and the main thing is not to star, but to study people;)

Answer 2

I got a job at the sys factory. admin. Wasn't afraid. He just came and sat down and didn't do shit. After half a year, I set up a server and put a bee there, then I didn’t do shit for another half a year. I sat and thought - something would break. However, nothing broke and I quit

Answer 3

agreed on a job, learned CakePHP in a week
, didn’t really understand anything at first, cursed everything and everything,
then I got used to it and started to figure it out,
and it’s always the same when I encounter unfamiliar APIs or frameworks
, you sit, you don’t understand anything, then you read the manual
and time everything falls into place

Answer 4

acquaintance, design, acquaintance with Linux, raising the project, acquaintance with zend 2 / Doctrine 2 and part of the project
, they will now tell me to do something, but I don’t know how (c) Soultaker
well, apparently this is the first job, so you are a junior, and you will not be given something complicated
, and most likely the first time you will just read the code and understand the technologies
, they will most likely attach a person with whom you will work on 1 task,
they will pay attention to the cleanliness / readability of your code (t .e. you will have to do a lot of refactoring your code), say what books to read (of course, if a serious project that is planned to be supported and developed in the future)
cannot but work out :)

Answer 5

I worked in a state institution as a system administrator, it is unrealistic to work. More precisely, they just don’t give it, the head of the aunt doesn’t want to delve into problems and doesn’t want to solve problems under 50 (purchases, or push something like that, I’m silent about the server’s AD, but why it works the same way), but how it breaks something almost an IT guru. I worked a little and went to the private sector where there are colleagues there, if something is not entirely clear, you can consult, and you get experience faster. In general, in state budget organizations, the system administrator is not a person (PS If you don’t know something, there is Google, colleague, habr (toaster)

Answer 6

Workplace setup, Git, Redmine, code analysis.
Didn't go to lunch either.