fijiaarone

But no one can or needs to use a residential proxy for automating CRM data entry.

or even this:

git clone http://github.com/unknown/repo.git && cd repo && npm install

Everyone has been trained for years to do this:

curl http://obscure.url?random-string | sh

This is neither hijacking notifications nor sending malware. This is someone including a link in a message on a ticketing system open to the public, and then someone clicking on the link and downloading malware.

I expect the result of Filho's tantrum will be the ouster of Ted Tso from the Linux kernel.

Usually people that don’t being in thought can’t think, so from their limited perspective, their arguments kinda make sense.

It’s like white swans. If you’ve never seen a bird, you might think that nobody has ever seen a white swan.

So you’re saying more than 1 person was paid to put the back door in.

You can make anything that stores data into a job queue.

In the story above, Linux Torvalds is Gitfolye.

It's not that the basics of git are hard. It's that there are 30 footguns you're forced to deal with every time you want to do anything, just because someone somewhere once had to use one of them -- probably caused by another one of them.

Git lovers mostly use it as a file copy service.

If git doesn't need a server, then why do you need Github?

> some even celebrating their mastery of the warts as necessary knowledge.

Hi git fans!

No one ever took a government out to a fancy dinner and drinks to convince them to use open source.

I don’t understand why everyone wants to replicate AWS APIs for things that are not AWS.

S3 is a horrible interface with a terrible lack of features. It’s just file storage without any of the benefits of a file syste - no metadata, no directory structures, no ability to search, sort, or filter.

Combine that with high latency network file access and an overly verbose API. You literally have a bucket for storing files, when you used to have a toolbox with drawers, folders, and labels.

Replicating a real file system is not that hard, and when you lose the original reason for using a bucket —- because your were stuck in the swamp with nothing else to carry your files in — why keep using it when you’re out of the mud?

Do you thing that was a coincidence, or do do you believe in effect and cause?

That hurts a little too deep.

Elegant code and clean architecture are no match for the chaos of the human mind.

Note how even the author thinks that nonsensically complex systems like Kubernetes and Zookeeper are the best possible designs.

That hurts a little too deep.

Elegant code and clean architecture are no match for the chaos of the human mind.

“How would six terabytes fit into memory?”

A better question would be:

Why would anyone stream 6 terabytes of data over the internet?

In 2010 the answer was: because we can’t fit that much data in a single computer, and we can’t get accounting or security to approve a $10k purchase order to build a local cluster, so we need to pay Amazon the same amount every month to give our ever expanding DevOps team something to do with all their billable hours.

That may not be the case anymore, but our devops team is bigger than ever, and they still need something to do with their time.

Log files aren’t data. That’s your first problem. But that’s the only thing that most people have that generates more bytes than can fit on screen in a single spreadsheet.

The slow part of using awk is waiting for the disk to spin over the magnetic head.

And most laptops have 4 CPU cores these days, and a multiprocess operating system, so you don’t have to wait for random access on a spinning plate to find every bit in order, you can simply have multiple awk commands running in parallel.

Awk is most certainly a better user interface than whatever custom BrandQL you have to use in a textarea in a browser served from localhost:randomport

The problem with big data is that people don’t have data, they have useless noise.

For lack of data, they generate random bytes collected on every mouse movement on every page, and every packet that moves through their network. It doesn’t tell them anything because the only information that means anything is who clicks that one button on their checkout page after filling out the form with their information or that one request that breaches their system.

That’s why big data is synonymous with meaningless charts on pointless dashboards sold to marketing and security managers who never look at them anyway

It’s like tracking the wind and humidity and temperature and barometer data every tenth of a second every square meter.

It won’t help you predict the weather any better than stepping outside and looking at the sky a couple times a day.

That’s like saying “the problem with aircraft is that they keep crashing when there is not enough lift under the wings, so the obvious answer is to get rid of wings”.

Only, it would even be stupider if your grasp of programming was as great as your understanding of aerodynamics.

Plus, it doesn’t have the Apple logo.

You should see what farmers have been doing with carbon dioxide for thousands of years.

PostgreSQL didn’t exist in the 1990s. It was called Ingres. Postgres started as a personal project and was first released in 1999, but was unusable. Around 2004 the project started getting popular and hipsters started screaming that MySQL didn’t have stored procedures and wasn’t fully ACID. Acid became a buzzword for PG fanboys, even though data corruption and memory leaks plagued the system for the first decade. It became a stable around 2008 as long as you didn’t mind restarting your database every few days. PostgreSQL didn’t really become a viable option until around 2010.

When you turn 23 in a couple years, you’ll look back at college and realize you weren’t at the apex of all knowledge back then.

So in reality S3 takes about 2 seconds to retrieve a single file, under ideal conditions. 1 second round trip for the request to DynamoDB to get the object key of the file and 1 second round trip to S3 to get the file contents (assuming no CPU cost on the search because you’re getting the key by ID from the DynamoDB in a flat single table store. And that the file has no network IO because it is a trivial number of bytes, so the HTTP header overwhelmed the content.)

I know what you’re thinking — 2 seconds, that’s faster than I can type the 300 character file key with its pseudo prefixes)!

Ah, but what if you wanted to get 2 files from S3?

If you think s3 is fast, you should try FTP. It’s at least a hundred times faster. And combined with rsync, dozens of times more reliable.

Venture capital doesn’t do that. They fund simple websites like Facebook or Airbnb.

Here is a a key problem:

“It began with an effort to extract “sponsorship” dollars from local service providers: the lawyers, accountants, recruiters and PR firms that cater to startups.”

The YCombinator strategy was to give founders money and get them to focus on building a product.

Techstars, on the other hand, sought to extract money from founders to support their sponsors to nickel and dime dreamers and bog them down with time wasting distractions like articles of incorporation and formal business plans and commercial bank accounts and press releases —- because these are the vanity services their sponsors provide. You feel like you are building a company when you consult a lawyer and accountant creating an S-Corp and delegating shares.

But Y Combinator has had direct access to the unlimited fount of free money created by zero interest rates so they only needed to appease the vultures capitalists with pump and dump schemes.

Both methods are flawed, even if the stated aims of the organizations are noble.