Comment

Comment on You're overcomplicating production

just_another_person@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

Anytime you see anyone post something like “THIS Is How You Do The Thing” should automatically be ignored. This article is no exception.

The author is making a big deal about a team of 40 and “millions of customers”…k.

Not sure if anyone is supposed to be impressed by that, but the titular argument here isn’t a position for a small team and product, it’s making the case that “ALL THINGS EVERYWHERE ARE TOO COMPLICATED”, which is just an ignorant position to take.

If this had come with some sort of tools or workflow to back up the claim, then it would be worth reading. This is just an inexperienced person’s rant with zero metrics about what works for them, why, or suggestions for others.

There is no content here, just time wasted.

source

Sort:hotnew top

something_random_tho@lemmy.world ⁨4⁩ ⁨weeks⁩ ago
Hi friend, this was just meant to be an introduction, as I get started blogging and sharing back some knowledge and lessons I learned along the way. I’ve never written a blog before (or much of anything!), and I’m sorry you didn’t find value in this.

I’ll take this feedback to heart and try to produce larger, more substantial posts to follow. Thanks for commenting.

source
- just_another_person@lemmy.world ⁨4⁩ ⁨weeks⁩ ago
  Well, apologies for being bluntly critical. I can offer a few constructive tips to help with writing about technical topics:
  
  Try starting with a simple topic flow: topic -> synopsis/purpose of why you’re writing -> background -> observations -> point<>counterpoint loop to elaborate on purpose -> closing
  
  Stay away from asserting your point in the title unless you’re showing definitive proof of something
  
  Find ways to speak to who may find your writing useful towards the beginning. “If you have a similar problem like X…”, “People who use X may find…”, or “Anyone having similar X experience may find…”. Something like that.
  
  source
  - 1984@lemmy.today ⁨4⁩ ⁨weeks⁩ ago
    I can offer some constructive tips to you as well: dont speak for all of us.
    
    I liked the article. I didn’t interpret it as “everyone must do what I say”. It was simply a viewpoint from a person on the internet. That is what a blog is.
    
    The complexity of tech stacks have increased enormously in the last 10 years, and it’s only sane to see what tradeoffs we are making to be able to scale easily. Perhaps it’s not worth the trouble for 90% of us. If we follow best practice from cloud providers without thinking for ourselves, we will not learn to think for ourselves either.
    
    So let’s do that. Let’s think, wrote blogs, discuss, and allow for discussions. Don’t shut people down.
    
    source
    just_another_person@lemmy.world ⁨4⁩ ⁨weeks⁩ ago
    Wow, nobody should ever say anything then unless they’re on the right side of everyone else’s opinion or else they might be speaking for everyone. Great tip.
    
    source
    -> View More Comments