1,230 karma · joined April 30, 2009
There is no way in the world that the only effort taken related to infrastructure is entirely encapsulated in ~ $200 per year.
Everything is built up and torn down via Terraform, and ZERO maintenance tasks are done via the console. Changes to infrastructure configuration are managed via CAB which approves PRs on Github which are automatically deployed via TF cloud.
We do monthly disaster simulations where we replace a _production_ environment.
I'll agree that AWS paints a very rosy picture of their own services, but there is substance underneath that PR.
But ... most web applications are still IO bound, and labour is surprisingly expensive.
Also, you'll never get into a situation on AWS where you have a 3 day lead-time for a replacement GBIC, or NVMe drive, or seomthing, while your customers scream and bail out for a competitor that isn't down.
Yes, you need to manage the infrastructure, but now it's a software configuration task instead of a physical maintenance one.
It's absolutely true that colo is cheaper than AWS for projects that can absorb the labour and failure related costs, but that usually is only true for hobby or very small business services.
Sadly, you're missing a zero.
Out of the whole bunch, FreeCAD is probably the best open source solution.
If you don't mind pending a bit of $, and need something parametric, then Alibre CAD ticks a lot of the same boxes as F360. Windows only though.
If OTOH you don't need parametric design, I've gotten pretty far with Rhino3D, although again that is Windows/Mac only.
- Hofstadter's Law: It always takes longer than you expect, even when you take into account Hofstadter's Law. -> It's gonna take longer than an afternoon. Always
- Opportunity cost: Your app needs to DO something, and spending time building dependencies steals quality from your core business proposition, even if it's a small (Haha: see previous point) dependency.
- While there are a ton of crap libraries out there, there are also a lot of good ones, which include hard lessons learned, about even simple tasks. You _could_ rewrite a very simple http client in an afternoon (telnet hostname 80\n GET / HTTP/1.0\n\n), but you'll probably have a ton of glaring flaws just waiting to bite you _badly_.
https://www.edn.com/arm64-vs-arm32-whats-different-for-linux...
You can get Arm64 linux workstations now.
https://www.anandtech.com/show/15733/ampere-emag-system-a-32...
- Monitor room light level for fluctuations that correspond to advertising broadcasts for advertising proximity fingerprinting, or location fingerprinting, ie: the illuminance profile for a video broadcast is moderately unique, and can identify the fact that it's playing on a screen near the user
- Side channel for data exfiltration attacks (we require permission to use the microphone for more reasons than just listening for people talking)
- Monitoring for in/out of pocket/purse state for the phone
- Probably a ton of other nefarious stuff that I am not devious enough to think of.
You clearly didn't read the actual judgement. It very clearly states Insects and/or vermin. I'm pretty sure that qualifies as a reasonable term for 'other small lifeforms'.
The judgment is very clear that it rejects the claims for BOTH the insect and vermin clause, and acknowledges that while spiders are not "scientifically" insects, they are insects according to normal use, and also because of previous case-law.
In other words, if this test (and similarly the stanford study in LA) have even a small rate of false positives, combined with any sampling bias, it's going to lead to some misleading conclusions.
I also wouldn't want to sleep in a bed _in_ a cage, given the option of sleeping in a bed _outside_ of a cage.
And I think that we agree on the underlying reasoning; the consistency. I am just arguing that cubicles aren't an optimal place to spend your time, merely a convenient one for those that want to warehouse you while you work. The fact that it's consistent doesn't make it good.
Is this the same thing for cube-dwellers?
But yeah, that's still expensive for a box.
As someone who has deployed K8S at scale several times, this is nonsense. Learning K8S deeply enough to deploy AND MAINTAIN IT is a huge undertaking that requires an entire team to do right. Sure, you can deploy onto AWS via KOPS in a day, and you can deploy a hello world app in another day. Easy.
But that only gets you to deployment, it doesn't mean you can maintain it. There are TONS of potential failure modes, and at this point you don't understand ANY of them. When one of them crops up, who do you page at 3AM, how do you know it's even down (monitoring/alerting isn't "batteries included"), how do you diagnose and fix it once you _do_ know what's broken?
Not to mention the fact that you _have_ to continuously upgrade K8S as old releases go out of maintenance in under a year. If you're not continuously testing upgrades against production equivalent deploys, you're going to footgun spectacularly at some point, or be stuck with an old release that new/updated helm charts won't work against.
TL;DR: If you can afford a team to deploy and maintain K8S, and have a complex enough application stack to need it, it's awesome; but it's not free in either time or staff.
First off, don't shirk the Chemo. It works (I had hodgkins lymphoma, in case you have the same), and the cure rate is very good. I wouldn't hesitate to do it again if I relapsed.
Next; yes, chemo-brain is a thing, and you'll be a bit slower for the duration of the chemo. It was especially noticeable when trying to keep multiple ideas in my head at the same time. Navigating more complex codebases was definitely a challenge.
It'll also take some time afterwards to get back to normal. I felt like I was back to "normal" about a year afterwards, but was at 90%-ish about 3 months after I finished chemo.
The closest thing I can compare it to is a medium grade concussion (having had a mild-medium concussion while mountain biking). It is a slower recovery than a broken bone, but you do recover.
In the years since, I've been lead architect, and head of engineering for various cloud infrastructure software projects. It definitely hasn't held me back in any way I can identify.
Rust was originally released in 2010.
Anybody spot any others?
That said, statutory civil penalties (fines per occurrence) for the effects of the bug in production _would_ fix the problem. Who is going to keep giant data-lakes around when they are the business equivalent of toxic waste? The developers are still able to write code, but they are incentivized to not collect extraneous user data.
> I'm widely known for my extreme stupidity.
Loving the zero <expletives> given approach from the maintainer. Installing now.
I remember the late 90s though. Ugh. Staircase aliasing and horrible stroke widths.
While it can be tempting to just push through, that can be dangerous. Sometimes that "meh" feeling is a symptom of burnout. Did you have a long week? Lots of hours? Put out some fires? Decompressing now will be better than fully burning out in a few months with some shoddily coded side project to show for it.
That said, it's also possible that you need to "chop wood, carry water" as mentioned by another poster, but if you do that, take a moment to look at your side project from another level. Are you slogging because of some architectural debt, or because you're just poking at the problem to see what works? Personally, I get bogged down when I haven't thought through the problem at a higher level. Sometimes I'll just write a series of steps to get from where I am, to where I need to be, and identify the thing I am dreading doing.
TL;DR: Sometimes you need a break, sometimes you need to step back and take a 10k foot view of what's bugging you, and sometimes you just need to push through. It depends ;)
Once you get to 117 years old, there are only a few people worldwide that can be used to determine that survival rate, and those people are already subject to a selection bias of people that are exceedingly long-lived.
That said, for a lot of things, I think containers are premature optimization. People get so excited about deploying their little app that they deploy a 6 node K8S cluster with all the associated complexity, for an app that would happily run HA on two regular nodes with systemd starting it up.
Once you are plumbing together a dozen different microservices using a few different languages though, K8S starts to make a lot of sense. Service discovery, container-container routing, namespacing, and all that other good stuff make your life _easier_, but only past some level of scale.
Oh, and docker compose is amazing for local dev and integration testing of those more complex service compositions, just saying.
Example: https://www.youtube.com/watch?v=A0MXPq8LLhU
I guess this is the modern equivalent?