Have you tried one-shotting real distributed systems problems? What was the result and how did you verify correctness?
364 karma · joined October 7, 2011
Have you tried one-shotting real distributed systems problems? What was the result and how did you verify correctness?
It’s also about an influx of new ideas, different lenses to view problems, and connections to people like them, amongst a number of other reasons.
I reflexively reload HN many times per day, but I'm wondering if I need a walled garden with some sort of curation of individuals - which sucks - to get the signal level I want.
Longer answer: About 10 years I moved into leadership roles (VP Eng) and while I continued to write code for POCs, it hasn't been my primary role for quite some time. DDIA has been a book I pull out often when guiding leaders and members of my teams when it comes to building distributed systems. I'm writing more code these days because I can, and I still reference DDIA and have the second edition preordered.
https://bernste.in/writings/the-unreasonable-effectiveness-o...
Every day, millions of people read content checked by Acrolinx. Our AI platform ensures that what companies publish is accurate, on-brand, and high-quality. You'll join the team building the next generation of these language-aware services. You'll work in python, integrating LLMs, optimizing performance, and delivering features to customers ranging from Fortune 500s to startups.
You should have: 3+ years of Python (HTTP APIs, relational/NoSQL, experience with a cloud platform like AWS/GCP/Azure) Strong grasp of system design, algorithms, data structures, and testing. Experience with LLMs and a desire to build products utilizing them.
Bonus (not required): Experience with any of the following - PyTorch, Hugging Face, FastAPI, Docker/K8s, async Python, Temporal/Airflow. Experience integrating LLMs into products.
We're a small, remote-first team working in cross-functional squads. If you're excited about building AI-powered products, let's talk: recruiting-mb@acrolinx.com
Here's my pointless randomly made up on the spot anecdote - you're more likely to write a vulnerability in your own logging system than being impactedby using a widely adopted opensource one.
"Revisiting assumptions
Considering "Camels" might be a mistake for "Kools," leading to confusion. This inconsistency complicates solving the puzzle, showing the need for careful brand assignment."
Tracking puzzle progress
I’m mapping out various house and nationality combinations, but the classic conclusion is the Norwegian drinks water and the Japanese owns the zebra.
Analyzing the arrangement
I’m working through the classic puzzle structure and noting variations, while consistently identifying the Norwegian drinking water and the Japanese owning the zebra as the final solution."
I assume you mean that sub 80% capacity nuclear has issues being cost effective (which I agree is true).
You could pair the baseload nuclear with renewables during peak times and reduce battery dependency for scaling and maintaining higher utilization.
She's made the same baseless argument for a long time: "Nuclear power is slow, expensive — and wildly dangerous"
https://ourworldindata.org/nuclear-energy#:~:text=The%20key%....
CO2 issues aside, it's just outright safer than all forms of coal and gas and about as safe as solar and wind, all three of which are a bit safer than hydro (still very safe).
All of the above are significantly better than burning gas or coal - but nuclear is the clear winner from an CO2 and general availability perspective.