Conversation
Four short-form posts covering the iceoryx2 adapter, telemetry stack, the /new-adapter Claude Code skill, and the WebSocket adapter plus JS client. Each file has the post body and a separate first-comment block with links.
The adapter is no longer beta — rename the feature flag reference to match.
Lead with the month-to-weekend speedup. Explain how the skill was reverse-engineered from existing adapters and is iterated whenever a new pattern shows up. Add the quality-from-consistency angle. Drop the mention of the /new-adapter-issue companion skill.
Covers kafka_sub / kafka_pub, multi-topic publishing, the FuturesUnordered per-burst delivery model, and the rdkafka / Redpanda testing stack.
Goes deeper than the v3 launch post — closure-driven q queries, run-mode driven time slicing, first-class Sym, kdb_read_cached for backtests, functional insert on write.
Long-form Show-and-Tell style — explains wingfoil briefly, walks through the adapter API, the three polling modes, the gateway-vs-risk use case, and asks for feedback on polling-mode choice and contract evolution.
Frames Rust's strictness as a feature when working with an agent — tight compiler-driven loop beats observe-and-iterate on runtime defects. Uses the Bun-to-Rust news as a hook and poses an open question about Zig without taking shots.
Concrete numbers from coverage of the May 14 merge — 6,700 commits, ~960k lines, six days, 3-8 MB binary shrink — and an honest mention of the ~13k unsafe blocks for balance.
Indexes the seven LinkedIn drafts in the planned sequence (Bun/agentic opener, then the six product topics), plus the iceoryx2 GitHub discussion draft. Notes the post/first-comment format and the two sanity checks to run before posting.
LinkedIn post: two-node adapter overview, per-burst flush, absolute offset resume, SC+SPU cluster shape. GitHub discussion: Show-and-Tell with the adapter API, three integration gotchas (SPU, topic pre-create, container timing), and an open question about single-container local test setup. README updated to add Fluvio as #8 in the posting order.
Replace the weak &str/String example with three cases that would cause real runtime bugs in other languages: use-after-move, Rc<T> across a thread boundary, and non-exhaustive match on a new enum variant.
- Hedge Bun-port unsafe-block claim and drop incorrect uv-as-runtime comparison - Remove fenced code block from Fluvio post (LinkedIn renders markdown literally) - Rework telemetry post's three-piece section so the intro matches the prose - Update README posting checklist: KDB q syntax to be posted as a screenshot
…anguage stack (#382) * Add call-for-contributors post for /new-adapter skill * Add three-language-stack post (Rust/Python/TS foundation) * Make three-language-stack post more provocative --------- Co-authored-by: Claude <noreply@anthropic.com>
…ted status (#389) * Remove duplicate /new-adapter LinkedIn draft, keep contributors version Drop the older new-adapter-skill.md in favour of the later new-adapter-skill-contributors.md, and renumber the posting order in the README accordingly. https://claude.ai/code/session_01WQcZqi3y8wDQJxjXAUuuZK * Soften absolutism in three-language manifesto draft Reframe the thesis as a claim of tendency rather than absolute, and concede Go's and the JVM's genuine technical niches before the closing dare so the provocation reads as informed rather than dismissive. https://claude.ai/code/session_01WQcZqi3y8wDQJxjXAUuuZK * Mark agentic, iceoryx2, and kafka LinkedIn drafts as posted Add a Status column to the posting-order table tracking which drafts have already gone out. https://claude.ai/code/session_01WQcZqi3y8wDQJxjXAUuuZK --------- Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.