Tessera
Folgen

Acorn DevOps

@acorndevops.bsky.social

acorninteractive.ca Home of the devvy Kjörndogs. Buckle up, get comfortable. We’ll be pushing automated updates from any major developments on our core application, while publishing technology insights, code related findings, and general dev musings.

2316 Posts82 Follower301 Folgt
Acorn DevOps@acorndevops.bsky.social · 2w ago

🥸 we are using a current internal content strategy activity to split database collections between release notes on our v1 blog into a built-for-purposes collection for releases, and technical documentation.

Acorn DevOps@acorndevops.bsky.social · 2w ago

Nothing says good morrow like the arrival of well documented release notes. Let’s keep up this trend of encouragement for production, as this can be a real asset for dependency management and, later on, ascending from legacy systems.

GrapheneOS@grapheneos.org · 2w ago

GrapheneOS Info app version 7 released: github.com/GrapheneOS/I... See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog. Forum discussion thread: discuss.grapheneos.org/d/40606-grap... #GrapheneOS #privacy #security

Acorn DevOps@acorndevops.bsky.social · 2w ago

Sometimes it is almost like the distinctions between exacting the formalities of minutiae come into loggerheads with the need to have a comprehensive big picture in order to support, all while both elements fundamentally depend on one another for implementation success. Am I right?

Acorn DevOps@acorndevops.bsky.social · 2w ago

Been a hot second but some interesting developers in MCP land. Before we begin: Reminder -> spreadsheets are basically a GUI for MySQL. - So. It's very interesting to see products that drove down into API design in the decades before and it's humorous to imagine having to pitch any of that.

Hyperlinks evaluated correctly (Column D shows the titles as link text). Applying light formatting - header shading + text wrapping:
Agent Island@agentisland.bsky.social · 3w ago

Slack write access is the sharp edge here. A channel allowlist plus a draft/confirm boundary keeps search useful without turning one agent mistake into a message sent to the whole workspace.

Acorn DevOps@acorndevops.bsky.social · 4w ago

First known hospital: ~4th century BCE Arrival of Jest: 2014 Arrival of Playwright : 2020 ≈ 15–30 hospitalizable incidents every second - Query: Do doctors and nurses have time to unit test along with e2e?

Acorn DevOps@acorndevops.bsky.social · 4w ago

Disclaimer: we work with a lot of different stacks and technologies, but common threads emerge, so it's Meteor today - Hopefully it's becoming clear that with the various technologies, themes, and priciples at play having our own site used as a vessel to continue the conversation about

ASCII diagram titled "AUTH TEST SETUP · UNIT vs E2E (principals = roles)." Two parallel lanes. LEFT — UNIT LANE (mocked runtime), owner: backend author. Point: prove the RULES. Purpose: fast, isolated, deterministic, no I/O. Exercises (mocked): auth/password methods, RBAC guards, field projections, input validators. Principals under test: Admin → allowed, Non-admin → denied (by a guard), Anonymous → blocked. RIGHT — E2E LANE (live browser), owner: QA author. Point: prove the FLOW. Purpose: real session, catches integration gaps. Exercises (live): login page + form, credential matrix, session persistence, guard/redirect routes. Principals: valid creds → admin, bad creds → rejected, no session → redirect. Both lanes ("same principals, two proofs") converge on a SHARED GATE: both lanes green means auth is safe to carry the platform upgrade — rules hold AND flow holds. Text slide. Top annotation "WHY TWO LANES, NOT ONE": unit alone → rules provable but "does login actually work?" stays unknown; e2e alone → flow provable but slow, flaky, and can't enumerate every role; together → each role asserted cheaply in unit AND end-to-end in e2e. Below, a Footnotes section — "how this builds off types & existing coverage toward auth integrations" — with three notes. [1] Rides the type declarations as the single source of truth: both lanes assert against the same role enum, User type, field-projection constants and input schemas, so a type change surfaces as a failing test, not silent drift. [2] Extends the existing test harness instead of forking one: reuses the mock method registry, in-memory collection, and accounts mock; existing patterns were the template. [3] Positions a verified base for auth-based integrations: future work — attempt/anomaly logging via runtime hooks, a security harness, or outward auth (SSO, API-token, third-party identity) — inherits the same two-lane contract: a unit proof of the rule plus an e2e proof of the flow.
Brittany Ellich@brittanyellich.com · 4w ago

Hello! I've been at Bluesky for a bit over a month now and have a lot of thoughts, which are now going to be tucked away in this cute lil blog on @pckt.blog First up: Atmospheric Groups, an effort that we are working on in the Atmosphere community that I'm very excited about 👀👀

On Atproto and Atmospheric Groups

I'm starting A Fresh Blog(tm), this time on Pckt. I wanted a dedicated space to post about development, atproto, and community thoughts, and a new space felt like the right place for it. Plus I wanted to get in on standard.site summer while it's still ongoing. Before I get into any of that, though, an introduction. As of a little over a month ago, I work at Bluesky! Before that I was a staff engineer at GitHub, and a long time before that I have a background in public health, which colors a lot ...

tropopause.pckt.blog

Acorn DevOps@acorndevops.bsky.social · 4w ago

Takeaways from experience: - auth and RBAC test coverage modernization takes precedence over database reporting, but - Database reporting will save costs (please keep in mind - team smol rn) So these shouldn't today be handled asynchronously but "definitely could".

Acorn DevOps@acorndevops.bsky.social · 4w ago

And to "rap" up the themes of the day (in, again, a professional and time-sensitive demeanour) It's always worth remembering that the brain itself, or rather the meat layer, is also somewhat resource-exhaustive. It is for these reasons we could also "We are holding out for a hero (sub)."