Almost every software tool decision I make is one of garbage quality with features vs ok quality with no features. I can choose a text editor that does the basics but nothing else I need or an ide that does everything poorly. From browsers to package managers to debuggers to operations tools, the quality of software tools is absolutely atrocious. Why master any of this garbage when more garbage tools will be required later? It's hard to stay sane just using them. Yes, non software tools like reading and writing comprehension are useful, but for the most part, investing heavily in a tool that's bound to fail over and over again seems like a terrible idea. Then again, there simply isn't enough time to write proper versions of these tools. But amazing things have been built with much less tooling than we use today which leads me to think that the proliferation of software tools partly exists only to make the tool developers happy as they create useless rube Goldberg machines (especially in js land).
Justice is whatever the 'justice' systems says it is. Citizens have no recourse. The 'justice' system has no checks or balances that can be accessed, except by the rich. There are no penalties for abuse or misuse, even when uncovered.
Yeah, that's exactly what I think of when I think of the concept of 'justice'. One day some people might create a just society, but it almost certainly won't be in the US.
It's always been complicated, though. Alexis Ohanion has repeatedly talked about the importance of Reddit as a censorship-free platform and talked up the company as embodying unfettered free speech.
Obviously that's not true, but major figures at the company have said it from the early days up through very recently. And the difference between moderation (in the "no spam, no personal threats, communities enforce their own rules" sense) and administrative speech restrictions is a big and challenging one.
So no, Reddit has never quite been that, but it's been one of their selling points regardless.
I should have been more clear. I was referring to storage auto-scaling. Aurora gives you access to up to 64TB of disk billed in 10GB increments. You don't need to preallocate and manage the scaling of your disk as you do with RDS.
Couldn't agree more. If you have a monolith, you can probably get away doing dev ops as long as you don't grow too much. We have a handful of microservices and trying to keep up with the ops work has been hell, though part of that is due to AWS's tools. And this is without even a growing user base, just a growing app base. Burn out is definitely a problem in either case.
This is interesting. I've had a lot of people on the internet tell me that a monolith must become unmaintainable at some point, and the only way to keep it serviceable is to break it up into microservices.
The main lesson here is to leave a company that doesn't pay you immediately. The rest of the lesson is only for the idiots who didn't do that like the author.
The problem is that most contractors will feel trapped by the sunk costs -- fallacy or not.
If you've put a month of work towards something, and they say "funding's coming through, give us a couple weeks for the first payment," you have two choices: keep working and have a chance that you'll get paid, or stop working and be guaranteed you'll never be paid for that month you put in.
Or you can refuse to start work without a deposit or payment up front. It's really that simple.
The life of a small shop requires you get paid before you do the work. You tell the client that you'll pass the savings in your nonexistent collections department on to them. If they won't do it walk away, since fucking this concept up is the fastest known way to kill your business.
