aarmot

And now your mentor arrives and demands you change one character to source all input*.txt files

You can put your entropy in comments and strings

You can pull the wire and second string together so you have always a single string in conduit.

From your bragging one could tell that you have seen _a lot_ of charging mistakes and "happy" refund stories from AWS. It's scary that a single human can do extensive statistics on personal experience about these monetary horror stories, don't you think?

The wakewords could be simply "buy", "cheap", "sale", "price" etc - and then collect the exact words around it. I bet the pool fencing conversation followed with the exchange of ideas where to get equipment.

> ... Falcon 9 ... nearly 10 flights per booster

Just curious: what year is your data from?

Because author of the article likes to be edgy and parrot the deep truth he learned yesterday - that TCP is "reliable" and UDP is not.

The reality, of course, is somewhat different and muddy. For example, if you have network outage following later by a software crash or a reboot, then all the TCP buffer worth of data (several kilobytes or upto some megabytes - depends on your tuning) is mercilessly dropped. And your application thinks that just because you used TCP the data must have been reliably delieved. To combat this you have to implement some kind of serializing and acking - but the article scoffs us that we are too dumb to implement anything besides basic stream /s

I'm not arguing that TCP is useless, just that UDP has its place and we - mere mortals - can use is too. Where appropriate.

That study is far from being conclusive. Please read also

https://cloudinary.com/blog/the-case-for-jpeg-xl

Author possibly meant something like this (but yeah, same idea) fffind () { find . -regex ".$1."; }