You're going to have outages in production. They're inevitable. The question is how to best minimize outages, both their frequency and duration.
Common wi...
Anytime you see anyone post something like “THIS Is How You Do The Thing”, it should automatically be ignored. This article is no exception.
The author is making a big deal about a team of 40 people 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 IN PRODUCTION ENVIRONMENTS”, which is just an ignorant position to take.
If this had come with some sort of metrics, tools, or workflow to back up the claim, then it would be worth reading. Nothing like that here. This is just an inexperienced person’s boasting rant with zero elaboration about what actually works for them, why, or suggestions for others facing some sort of similar situation.
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 wasn’t intending to boast, but I can see how it came across. I just meant to say, “companies are trying to tell you that you need ‘XYZ’ to scale,” and at least at the size of business I ran, you didn’t need any fancy tech at all – we could have made do with a dead-simple setup: a single server running Go and SQLite. It’s something I wish I had known when I started.
I’ll take your feedback to heart and try to produce larger, more substantial posts to follow. Thanks for commenting.
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.
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 articles on how to use Nix and OpenBSD if people find it helpful.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Anytime you see anyone post something like “THIS Is How You Do The Thing”, it should automatically be ignored. This article is no exception.
The author is making a big deal about a team of 40 people 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 IN PRODUCTION ENVIRONMENTS”, which is just an ignorant position to take.
If this had come with some sort of metrics, tools, or workflow to back up the claim, then it would be worth reading. Nothing like that here. This is just an inexperienced person’s boasting rant with zero elaboration about what actually works for them, why, or suggestions for others facing some sort of similar situation.
There is no content here, just time wasted.
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 wasn’t intending to boast, but I can see how it came across. I just meant to say, “companies are trying to tell you that you need ‘XYZ’ to scale,” and at least at the size of business I ran, you didn’t need any fancy tech at all – we could have made do with a dead-simple setup: a single server running Go and SQLite. It’s something I wish I had known when I started.
I’ll take your feedback to heart and try to produce larger, more substantial posts to follow. Thanks for commenting.
Well, apologies for being bluntly critical. I can offer a few constructive tips to help with writing about technical topics:
I think fans of Nix and NixOS would agree.
That’s interesting. I never got started with nix because I thought it’d be too complicated. So looking it up again…
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 articles on how to use Nix and OpenBSD if people find it helpful.
Why would you think Nix has any bearing on a production environment?
Well, I guess nixos itself isn’t too overcomplicated, but fun begins when you start layering abstractions over abstractions 😁
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.