Not nice, Plug… not nice! You define a Plug Module with 2 functions (init/1 & call/2) and the result of init/1 is passed in as the second argument of call/2… but init/1 is executed in compile time and call/2 in runtime.
WHY?!?!
I can't think of any other behavior that… well… behaves that way!

It's not even in the official docs (¬_¬)

I *hate* cmd+z in Atlassian Wikis… it removes text that was written ages ago… and you never get it back… no matter how many times you press cmd+shift+z or cmd+y… 😡

Whoever programmed ATMA's roomba-style device… you really really need to improve your skills!
Yes… my room is L-shaped, but that doesn't mean one of the arms of the L doesn't need cleaning!! 😒

In the same test file, 3 different tests, same field…

assert thing.is_blue
self.assertTrue(thing.is_blue)
assert thing.is_blue == True

…and of course other tests…

assert not thing.is_blue
self.assertFalse(thing.is_blue)
assert thing.is_blue == False

Comment introduced by a commit 3 years ago before an empty function:

```
%% TODO determine if there needs to be something here or if this can be removed
```

Why do you lie to me like that, previous dev? WHY??!!

Found something like this on the code today…

my_fun() ->
ANestedList = [["Just one element"]],
IndividualResults =
[change_stuff(InnerList)
|| InnerList <- ANestedList],
lists:append(IndividualResults).

Seriously, previous dev? I understand LCs are _cool_, but… really???

---
For non-erlangers: that function can be written as:

my_fun() ->
change_stuff(["single element"]).

OK, YouTube, I&#39;ll wait :)

Something truly useful, where I get to know the users or even be one of them. Something challenging but not beyond my reach.

Google hangouts on air: if you could not drop everything you recorded so far when I lost connection with the internet for a minute once I am an hour and a half into the meeting... that would be great.

Why on Earth would an API require me to provide input like this?

{"this": "{\"is\": \"not\"}", "how": "{\"json\": \"works\"}"}

😡