2 ms·

This post shows some signs of having its parts written by a LLM in my opinion. Or am I crazy? Please tell me that I am. Author having this on his github makes

by efilife 9mo ago

This post shows some signs of having its parts written by a LLM in my opinion. Or am I crazy? Please tell me that I am. Author having this on his github makes me even more suspicious: https://github.com/ashishps1/learn-ai-engineering https://github.com/ashishps1/learn-ai-engineering

tallytarik 9mo ago
It’s entirely written by an LLM.
- MikeNotThePope 9mo ago
  LOL, I was having an online chat with a friend the other day and commented I sound like an LLM.
- efilife 9mo ago
  Are you sure?
  - tallytarik 9mo ago
    Yes. The over-use of bold in the intro (hell, in the first sentence) is a good hint. All of it aligns with https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing Maybe the images were made by hand.
    - deleted 9mo ago
      [deleted]
  - tuetuopay 9mo ago
    Ask an LLM to write such an article and you'll have exactly this. - random bold emphasis that would make disney and marvell comics blush - overuse of "one paragraph then bullet points" - a lot of the bullet lists has a small bold prefix then one line for no good reason - every section has a "why it matters" - and then each section with an useless comparison table that are direct screenshots of ChatGPT/Gemini I would not mind if the author indeed used his alleged insights in the domain, but as other have noted, numbers are way off, and are what CSPs want you to believe to sell more instances in Kubernetes. This does not inspires "I proofread the LLM output". It's a shame because the article has some good advices, but also a lot of misled ideas that would make Grug scratch their head. No, you don't need Redis to have stateless applications. Having a load-balancing tier is as useful for resiliency than it is for scaling. Autoscaling is a trap. If you can afford it, start with the app and DB separated. Let your application perform connection pooling itself from day one, your framework knows more than PgBouncer how connections can be safely reused. Overall, at a high level, the article is good and is a good outline on the order in which to optimize (sharding is dead last), but the details don't meet expectations.
throwaway150 9mo ago
> Or am I crazy? You are not. The entire post is LLM slop. I am as baffled as you are how something like this could be on the front page of HN. The senseless bolding of random words in the text, numbers that are way off and don't make any sense are the clues that the post is LLM generated and the blogger didn't even bother to proofread it.

by efilife 9mo ago

tallytarik 9mo ago

It’s entirely written by an LLM.

MikeNotThePope 9mo ago
LOL, I was having an online chat with a friend the other day and commented I sound like an LLM.
efilife 9mo ago
Are you sure?
- tallytarik 9mo ago
  Yes. The over-use of bold in the intro (hell, in the first sentence) is a good hint. All of it aligns with https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing Maybe the images were made by hand.
  - deleted 9mo ago
    [deleted]
- tuetuopay 9mo ago
  Ask an LLM to write such an article and you'll have exactly this. - random bold emphasis that would make disney and marvell comics blush - overuse of "one paragraph then bullet points" - a lot of the bullet lists has a small bold prefix then one line for no good reason - every section has a "why it matters" - and then each section with an useless comparison table that are direct screenshots of ChatGPT/Gemini I would not mind if the author indeed used his alleged insights in the domain, but as other have noted, numbers are way off, and are what CSPs want you to believe to sell more instances in Kubernetes. This does not inspires "I proofread the LLM output". It's a shame because the article has some good advices, but also a lot of misled ideas that would make Grug scratch their head. No, you don't need Redis to have stateless applications. Having a load-balancing tier is as useful for resiliency than it is for scaling. Autoscaling is a trap. If you can afford it, start with the app and DB separated. Let your application perform connection pooling itself from day one, your framework knows more than PgBouncer how connections can be safely reused. Overall, at a high level, the article is good and is a good outline on the order in which to optimize (sharding is dead last), but the details don't meet expectations.

throwaway150 9mo ago

> Or am I crazy? You are not. The entire post is LLM slop. I am as baffled as you are how something like this could be on the front page of HN. The senseless bolding of random words in the text, numbers that are way off and don't make any sense are the clues that the post is LLM generated and the blogger didn't even bother to proofread it.