You're overcomplicating production

Comments

• 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

  • 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

      • -> View More Comments
• HybridSarcasm@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

  I think fans of Nix and NixOS would agree.

  source

  • something_random_tho@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

    Is it too late for, “I use nix btw”? I use it at home and for development.

    I planned to focus this blog series on ol’ faithful (Debian), but I could definitely see writing an articles on how to use Nix and OpenBSD if people find it helpful.

    source
  • fl42v@lemmy.ml ⁨4⁩ ⁨weeks⁩ ago

    Well, I guess nixos itself isn’t too overcomplicated, but fun begins when you start layering abstractions over abstractions 😁

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

    Why would you think Nix has any bearing on a production environment?

    source
  • dashcubeit@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

    That’s interesting. I never got started with nix because I thought it’d be too complicated. So looking it up again…

    source
• rookbrood@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

  I agree with the sentiment of your article and I’m looking forward to seeing your follow ups. I’m always trying to keep things as simple as the problem I solve allows for.

  source
• Shimitar@feddit.it ⁨4⁩ ⁨weeks⁩ ago

  Not a bad take per-se, but a bit condescending. While I agree and like the KISS paradigm, remember that no solution works at a lower complexity level of the problem itself.

  So, define your problem clearly, find the simplest possible solution. Don’t overcomplicate, I agree, but don’t be fooled by false hopes.

  Is it really simpler? Yes. Will it scale if I need it to? Maybe not, but will I really need for it to scale?

  And so on.

  source
• betweenthesixes@lemm.ee ⁨3⁩ ⁨weeks⁩ ago

  I understand this take and the frustration it is born out of, however, extremes are rarely the right answer. If this were a series of posts, I would gladly read along and expect that the author would learn some valuable lessons from this approach.

  Are certain things often needlessly complex? Sure. Does that come at a cost? Sure.

  However as a business (or deployment) grows, it becomes subject to more requirements, regulations, risks, etc. that often demand the complexities that the industry and author have witnessed.

  All business decisions are made through a lens. What is important today? Based on what I know today, what does the future hold? What constraints do I have? The key is a logical, but balanced decision.

  source