jb_gericke

6 ms·

1.
by jb_gericke 1y ago
So first off, don’t use Python in prod. Second off, don’t use async because of complexities in multi-threading? A lot of the world runs just find on Python (see Django), async is mature and stable.
2.
by jb_gericke 1y ago
It sounds like the author makes a blanket claim to avoid asynchronous functions, even when using an inherently asynchronous web framework (FastAPI), which would negate any FastAPI asynchronous concurrency gains.
3.
by jb_gericke 2y ago
WASM solves a very different problem to Kubernetes, and you can happily run, scale and orchestrate WASM binaries on Kube.
4.
by jb_gericke 2y ago
I don’t think scale is the only consideration for using Kubernetes. The ops overhead in managing traditional infrastructure, especially if you’re a large enterprise, drops massively if you really buy into cloud native. Kubernetes converges
5.
by jb_gericke 2y ago
Can you qualify this statement? It’s 2024, Kubernetes is old tech and bullet proof at that.
6.
by jb_gericke 2y ago
Having watched the infrastructure side of things evolve from the late 90s/early 2000s, where every HP/IBM rackmount was a snowflake, configuration and releases were hand rolled and debugging server / OS / package depende
7.
by jb_gericke 3y ago
Which doesn’t really make sense, as drinking ACV alone will definitely not result in a body recomp/the addition of muscle (every meat head lifter, myself included, would be drinking a few bottles a day in that case).
8.
by jb_gericke 3y ago
Yeah, especially with containerisation and orchestration / Kubernetes, I get that perhaps not everything is viable to containerise, but in 2023 this feels archaic and like a lot of (potentially unnecessary) engineering work.
9.
by jb_gericke 3y ago
We had our main GCP account suspended because we were running a Lightning node, and some Google automata flagged us as mining. We couldn’t get hold of any actual person at Google, and were told by our Google reseller to buy a fairly expensi
10.
by jb_gericke 3y ago
I can see these popping up all over the show at Burning Man. Maybe the guru dude just knows his audience?
11.
by jb_gericke 3y ago
So TL/DR, the author works for a large org with a less than perfect culture? I’d simply move. Even in keeping to companies of similar scale, there are definitely highly successful enterprises out there that wouldn’t entertain entire de
12.
by jb_gericke 3y ago
Rancher price increases over the last few years have made it prohibitive for a good number of our customers. Personally, I don't think SUSE has done much to evolve the lifecycle side of Rancher - I want a platform that updates my node
13.
by jb_gericke 3y ago
I believe the founding Rancher members left to start Acorn ( https://www.acorn.io ) some time ago.
14.
by jb_gericke 3y ago
Kubernetes not required, just tons and tons of hand rolled Actions and env files and compose files and spaghetti bash. I don't understand the Kubernetes resistors, for a little bit of a learning curve all of this is taken care of for y
15.
by jb_gericke 3y ago
So, um, Signal? https://github.com/signalapp
16.
by jb_gericke 3y ago
It’s actually a Kubernetes focussed course. The JVM isn’t going to auto scale or distribute my service.
17.
by jb_gericke 3y ago
Why not put auth on the endpoint and enforce quotas and rate limiting (an api gateway like kong could handle this for you).
18.
by jb_gericke 3y ago
Reminiscent of Adrian Cockcroft “Gigalith” architecture. Not sure on the economy of scale though - if you need redundancy on a scale up architecture you essentially need to have parity compute sitting idle (likely in another location/r
19.
by jb_gericke 3y ago
Pioneer? Other than rewriting docket swarm it sounds like a stack from the early 2000s…
20.
by jb_gericke 3y ago
Let’s write our own container orchestrator though, because control planes are dumb?
21.
by jb_gericke 4y ago
+1 and Gunicorn with an ASGI server/Uvicorn
22.
by jb_gericke 4y ago
We're seeing the drive to Internal Development Platforms and Platform Engineering teams who are charged with eliminating developer toil and creating golden paths (ironically coined by Spotify engineering)/paved roads to production
23.
by jb_gericke 4y ago
The Shannon number doesn't exist for a middle management role, which could consist of so many variations from organization to organization. I don't disagree that AI assisted decision making is a thing that's happening, but I
24.
by jb_gericke 4y ago
The 'anabolic window' has largely been disproven. Depending on your goals though, from a resistance training perspective you typically need to be in a caloric surplus (although not an excessive one) to put on muscle.
25.
by jb_gericke 4y ago
We've been using K8s to scale incredibly high user and revenue generating services across banks, telcos, insurers for the last half decade. Works pretty well in our opinion ;)
26.
by jb_gericke 4y ago
And when your one big server fails and your first million customers start looking for more stable alternatives?
27.
by jb_gericke 4y ago
Couldn't agree more here. The amount of complexity involved in running moderately complex apps at scale on native compute and the cost to maintain over time vs. the ops savings from the standardization of most of that from Kubernetes i
28.
by jb_gericke 4y ago
I think the greater human population is doing just fine - almost exclusively due to scientific and technological advancements. ( https://lighthouse.mq.edu.au/article/why-has-the-world-popul... )
29.
by jb_gericke 4y ago
Body composition has a rather large effect on BMR ( https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3661116 ).
30.
by jb_gericke 5y ago
Yeah also a doubter, you can get to pretty DRY workflows with GitLab extends, caching is great, built in artifact repositories (including image registry), workflows/rules on when to build (i.e. run certain tasks specifically off MRs),

More ›