Romania 🇷🇴

Are you using the ARM or the x86 system images? The x86 ones are a lot faster.

Depends if the bug cause could have been easy to spot by reading the code.
Some bugs are easy to predict, others are not so easy.

You didn't have QA on the change?

@Grumpy That was a simple case, but in practice there are several conditions for if statements and instead of putting them all in the IF and chaining them there, you can easily declare them just before it.
For example, tell me what can you as an outsider read faster:

if (object.getMainContainer().isSet(randomvar) || (randomVar.length > 0) || ((randomVar.length%2)==1)) {
...
}

versus

varSet = object.getMainContainer().isSet(randomvar);
atLeastOnce = randomVar.length > 0;
oddCount = (randomVar.length%2)==1;

if (varSet || atLeastOnce || oddCount) {
...
}

The second version gives more information to the next guy reading it. Keep in mind that in practice there might be even more conditions.

Or you could do the cleaner version and go with:
notBar = !foo.isBar();
foo.setBar(notBar);

@chasb96
Ofc they want it fixed, but if they don't confirm the path they want to get to the solution there's a chance they'll want you to do it yet again using another method...

@stackodev the css needs to be loaded in the same order.
So if the css in the index file was loaded before the style.css, when you move it it also has to be before the rest of the css from there.

There is a reason why it's still unknown.

See http://caniuse.com/#search=grid

Irony at its finest, on the website the name gets cut off due to its length.

Note to devrant.io web dev, add to the CSS:

.rantlist-title {word-break: break-word;}

You can easily remove the results you don't want.
At the end of your search query add the words you don't want in your results like this:
-setup -tutorial

How about green/black tea as an alternative?