HN user

m1keil

500 karma
Posts3
Comments231
View on HN

I don't think that guesstimating that something is an AI slop is very harsh these days. It sure has the signs of one:

- HN User created 66 days ago

- In these 66 days it submitted 4 stories about this project

- The heavy lifting is all done by v86 project (not jslinux as initially suspected)

- The project is a "rebrand/fork" from another project by the same author - "traits.build".

- In the original project, the first commits that mention v86 seem to start at around 23rd of April.

To be clear, I don't really mind people vibing & slopping around. I just would want to have a disclosure about it.

SOC2 is quite a racket on its own so I'm not surprised to read this industry creates players like this.

I hope that with LLMs, answering security questionnaires will be much less time consuming for companies and less would opt out to get a full blown SOC2 cert. But it will probably play the other way.

I'm highly skeptical of this claim as well. Going through NATGW with EIP or auto-assigned IP is the exact same cost for the actual traffic.

This is more about guiding the readers, making sure the expectations are crystal clear and that they can follow me throughout an explanation.

Sure, but this holds true for the blog version as well, right?

To be clear, I'm not advocating for The Little Schemer version, and am not arguing that the blog version is the best it can be, but surely we can agree that book padding phenomenon does exist.

By the way, I have read parts of your book over at O'Reilly Learning, and I do think it is a good book. So I'm not trying to take a dump on your work. My criticism is aimed at publishers.

I learned a ton from my DE. Like, really, a ton. Before that, I had been writing on various blogs for about a decade, but writing online is all about being direct because most people don’t have time. With a book, it’s different. People made a deliberate decision to buy your book. Now, it’s your job to bring them somewhere valuable. And if that takes time (meaning more words), so be it.

I have a hard time with this point. It feels to me like a lot of books have A LOT of unecassery padding all over the place.

The example of taking 28 words and turning it to 120 is pretty good at showing this. The first paragraph is totally pointless - we are reading a book about 100 most common mistakes, obviously this mistake is very common, how did this increased the value?

Then we have another line that explaining what happens in the code, which is totally useless because the code is super trivial.

Then the code, with more explanations on the side as if the previous line was not clear.

And only after that we get to the crux of the issue.

I understand that book publishers feel they need to justify the price of a book by reaching the 300p mark in some or other way, but in my way this only makes the book worse.

If you are at the point of having to deal with individual servers and have a very fast-paced development (startup), or have to deal with very burstable traffic spikes (say e-commerce), cloud is probably your friend.

But sometimes you just need more compute and you are the type of organization that buys compute by the floor space and power consumption...

Regardless of the nuances of each situation, I think jsiepkes's comment meant to say that in the data center you can buy pretty killer hardware that will be totally overkill for the moment and won't require you to count active timeseries in order to not pay $300k a month for your metrics, and at the same time will last you for the next couple of years.

Also, for most companies, the next point of inflection will never come and this server will probably last them for a very, very long time.

I'm sharing my point of view as someone who works at an organization that took money as the only consideration and managed to grow over the years to now having to start taking both time and money into consideration because taking only money into consideration proves to be too expensive.

Maybe I'm misreading what you mean, but I don't understand why it's not solving problems. Lack of capactiy solved buy buying more hardware or replacing existing hardware with more powerful hardware. In the datacenter you need to have capacity planning pretty early on, while in the cloud you can get by until reaching very large cloud bill.

I also don't think that every organisation that needs file storage must build a storage solution that should compete the reliabiltiy and features of S3. Most of the times you can get by just fine at fraction of the cost.