Yeah, now I see why you want him dead. He used mov after lea

Context cues could be provided by jsonschema, but still it’s unbearable in comparison even with json.

It’s kinda organic in python, but God forbid how often I made mistakes in yaml learning k8s

You can’t be helped, sorry. We will put you to an asylum for people like you

He told the truth but people hated him

I follow these simple rules and encourage my colleagues to do so

1. If I’m just shuffling jsons, then yes, the code should be self documented. If it’s not, the code should be rewritten.

2. If I implement some complex logic or algorithm, then the documentation should be written both to tests and in the code. Tests should be as dull as possible.

3. If I write multithreading, the start, interruption, end, and shared variables should be clearly indicated by all means that I have: comment, documentation, code clearness. Tests should be repeated and waits should not be over 50ms.

The comment section proves that xml is far superior to json

Sorry, was writing it from the toilet. Needed to hurry in order to not miss a PBR

Like yes, but undone armpits generate more wealth than the rocket to Mars

Sounds so painful. We’re integrating AI right N now instead of doing what customers asked us to do or instead of fixing a ton of bugs we have.

I hate corporate

I have never thought about it

This joke is funny only if placed in Arnold-Atyah manifold if Kolmogorov-Ramachandran-Yu metric is defined

Yep, thanks for correcting me. In fact, if they write something like

if (day.isWeekend) {...}

The block will never be executed with the old version of library

No, they were probably getting false every time

It is

Higher temperature -> more chaotic output

People do mention Veritasium, though he doesn’t give any significant explanation of the phenomenon.

I still wonder about 47. In Veritasium plots, all these numbers provide a peak, but not 47. I recall from my childhood that I indeed used to notice that number everywhere, but idk why.

You could trick it with the natural language, as well as you could trick the password form with a simple sql injection.

Have a good walk at least

takes up a bunch of resources that could be doing other things…

You cannot get rid of garbage collectors, but you can always compile your java into binary to reduce the memory footprint.