---
id: 51
title: "Strange codes, multiple identities and team habits"
perex: |
    Just what I had in my mind or have tackled with in the recent past underlayed with the knowledge of the others.
lang: en
author: 31
tweet: "Post from Community Blog: Strange codes, multiple identities and team habits"
---

_originally published at [romanvesely.com](https://romanvesely.com) on 2017-10-16_

---

## `T_PAAMAYIM_NEKUDOTAYIM`
Even though the PHP language is improving and [the next version](https://wiki.php.net/todo/php72) is around a corner, there are some parts it carries from dark ages to the present and will most likely even beyond. Strange things you do not expect to see. Surely, one of them is following message:

> ...unexpected T_PAAMAYIM_NEKUDOTAYIM

"What?" a junior programmer might ask. But it happens that also advanced techies could be left speechless. Well, probably you can just check [StackOverflow](https://stackoverflow.com/a/592326/5549874). Or, of course, could start [learning Hebrew to know](https://philsturgeon.uk/php/2013/09/09/t-paamayim-nekudotayim-v-sanity/) what's going on.

Thankfully, there is [Urban Dictionary](http://www.urbandictionary.com/define.php?term=TGI(A)F) for all other unknown acronyms and phrases.

## Git over schizophrenia
You know you shouldn't use your company's computer to work on your personal projects, do you? For those who don't consider it's a bad idea, aren't aware of possible consequences or those who just work on multiple projects and need to commit under different identities git introduced a [new feature allowing conditional includes](https://github.com/blog/2360-git-2-13-has-been-released#conditional-configuration).

Now you can set different configuration for any project directory. This way you can [maintain several identities](https://dev.to/maxlmator/maintaining-different-git-identities) without pain and fear of being caught at pushing badly signed commits.

## Meeting habits
I hate to attend most of the team meetings since my first fulltime job (current one is the second, but nevertheless). The roots of my aversion probably started sooner, but, clearly, once in a room full of people when even air condition can help no more and you are forced to open all doors to get a sip of fresh air it starts to be clear this isn't the best way to share information.

Calculations of [wasted time and money during standup meetings](https://m.signalvnoise.com/status-meetings-are-the-scourge-39f49267ca90
) only underline my feelings so I quickly became a fan of various ways of [asynchronous communication](https://m.signalvnoise.com/status-meetings-are-the-scourge-39f49267ca90) and started to advocate its benefits. On one hand, I was (jokingly) labeled as a non-team player because of my beliefs, while, on the other hand, an idea of not having any meeting during Fridays was accepted instantly. Who knows why?

I will conclude with this perfect tweet I found (of course, not during any important meeting!):

<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Anyone who ever schedules meetings with developers, please burn this image into your brain, thanks <a href="https://t.co/IEoy10cgxW">pic.twitter.com/IEoy10cgxW</a></p>&mdash; Hatbox Phil 🍕 (@phil_wade) <a href="https://twitter.com/phil_wade/status/896010517617180672?ref_src=twsrc%5Etfw">August 11, 2017</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
