HN user
Strumming/picking requires significantly more (and more frequent) motor control than fretting. Most music will only use a handful of notes/chords, but multiple strumming/picking patterns which need to be performed on precise timings. Your strumming hand is often doing an order of magnitude more precise motions than your fretting hand.
"The President in particular is very much a figurehead — he wields no real power whatsoever. He is apparently chosen by the government, but the qualities he is required to display are not those of leadership but those of finely judged outrage. For this reason the President is always a controversial choice, always an infuriating but fascinating character. His job is not to wield power but to draw attention away from it. On those criteria Zaphod Beeblebrox is one of the most successful Presidents the Galaxy has ever had — he has already spent two of his ten presidential years in prison for fraud."
The Claude sandbox is so antithetical to good security posture it almost seems intentional[0]. Having both "default read to the entire file system" and "the agent can and _will_ disable the sandbox, without even asking the user[1], in order to complete tasks" would not pass muster in a freshman level security course.
[0] assuming a human with security training was involved in the design/prompting of the sandbox development.
[1] Claude has well used mechanisms for asking the user before taking potentionally dangerous actions. Why it is not part of the "disable my own SANDBOX" branches of code is confusing.
I'm a crypto skeptic, but I don't feel exceptionally informed of the other side of the argument(s). Can you recommend any posts/articles/summaries about the mistakes you're referring to?
I've heard good things about the mobile OS, but with Mixer Microsoft missed the mark.
They did a decent job of copying the Twitch UI to make the transition familiar, but then had a number of unnecessary friction points that I'm sure drove folks away. As an example with my own experience: I was a somewhat regular Shroud viewer on Twitch. When he had his first Mixer stream I tuned in, only to find out that A) his overlay notifications hadn't been integrated and B) I couldn't even minimize the chat pane of the viewer without signing up for a Mixer account, which was an onerous process.
Not having a large streamers overlay integrations working prior to his debut stream tells me that MS does not understand how critically important community engagement is in live streaming.
Forcing me to sign up just to be able to control the viewer UI drove me away and removed any chance of me returning and finding organic reasons to sign up for Mixer.
That was the one and only time I watched Shroud after his move.
Presumably in a company like Coinbase there is already an infrastructure team that runs the AWS instances, helps build the AMIs, etc. This team could re-tool and hire some k8s experts to help them make the shift.
The key is that there is a lot of additional services and interface points to handle. As the Coinbase article noted, you need extra pieces on top of k8s (storage, service mesh, config/secrets, etc) that need care and feeding. Even if the company moved 100% of their services into k8s there's now more work to be done for the same level of service.
: The control points that k8s exposes are not simple "drop in your provider here" bits of integration. You would likely still have the same core providers (ex: EBS for storage) but there is now more code running to orchestrate them, and more access control to implement and verify.
awe.sm (http://totally.awe.sm) - San Francisco, CA
We're seeking an DevOps Engineer to help us maintain the reliability of our core services, grow our engineering processes as we build new applications, and automate as much as possible.
We are a small, close-knit, and enthusiastic team of hackers building analytics that measure the ROI of social media. Our engineering culture embraces data-driven decision making, failing fast, and abiding by the UNIX philosophy: building small, powerful tools with clean interfaces. Additionally, we live on our internal IRC server, relish an opportunity to discuss new technology, and have a bi-monthly board game night.
Learn more about us or apply at http://totally.awe.sm/jobs
awe.sm (http://totally.awe.sm) - San Francisco, CA
awe.sm is a small, tight-knit team of hackers building social media insight tools on top of busy APIs and years of data. We do closed loop social attribution allowing our customers to understand the real value of their social activity. Our team is a family, and we're looking for dedicated engineers to grow with.
Our engineering culture embraces data-driven decision making, failing fast, and abiding by the UNIX philosophy: building small, powerful tools with clean interfaces. We live on our internal IRC server, collaboratively building bots to manage our systems and provide stress relief.
We're seeking an operations engineer to help us grow our engineering culture while being the champion of uptime and deploy automation. Experience in architecting systems is a plus, we value operational insight for building reliable systems on unreliable clouds.