CWC

Tech & AI Grinding

[CWC @chuawenching]

Day 14 (delayed due to busy schedule) - ship #14

One line of Markdown puts your heatmap in your GitHub README.

https://t.co/uGFpZmbS60

or snippet below.

```
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://t.co/vYr290t9w3">
<img alt="@[handle] on shiplogg" src="https://t.co/SrtHXci2rf">
</picture>
```

Light and dark. Updates itself.

[CWC @chuawenching]

Now I see the true value of herdr

Left - codex
Right - claude code

They can talk to each other and get the job done. Codex Astra 6 medium for building and Claude Code Fable 5.1 for QA. Sweet combo!

[CWC @chuawenching]

Your day if Grok Bot is unused:
chase follow-ups / rewrite meeting notes / dig for receipts / babysit CI

Your day with one good Bot:
wake up to a 5-bullet brief that already pulled mail + calendar

Same seat. Different use.

[CWC @chuawenching]

Day 13 - ship #13

New leaderboard view, nice.

[CWC @chuawenching]

Day 13 - ship #12

My contribution heatmap graph. But it shows who did the work.

Claude Code, Codex and me.

The leaderboard has one founder on it and it's me.

Most shipped - 82% agents

Here's a screenshot anyway.

[CWC @chuawenching]

Day 12 (delayed due to busy schedule) - ship #11

Every attributed commit is checked against GitHub. My split is verified from [N] commits.

Trailer doesn't match? The entry stays, gets a note. I never silently re-attribute.

[CWC @chuawenching]

If you're not "technical," ignore half the agent X.

You don't need fleets, schemas, or ops packs on day one.

You need:
- a named Bot
- Marketplace in the sidebar
- one draft-only job
- a weekday routine

That's it.

[CWC @chuawenching]

Grok Bot isn't ChatGPT with a hat on.

It's a teammate with a computer.

Blank sidebar? Normal.
Wrong model? Also normal.

Stop asking it clever questions. Give it an outcome.

[CWC @chuawenching]

You don't need 20 Grok Bots.

You need one with a real job and a boring routine.

Morning brief. Meeting closer. Follow-up cop.

That's the whole game.

[CWC @chuawenching]

I didn’t realize Ruby on Rails could cover most of the use cases I want to build.

I chose Rails because it’s easier for me to understand. I know Claude and Codex can generate code in other stacks too, but with Rails, I feel like I have a better understanding of what I’m actually building and how everything works.

With Claude and Codex, it feels like we can turn ideas into working products much faster. Looking forward to shipping more stuff!

[CWC @chuawenching]

Day 11

Fixed 9 bugs, 2 additional bugs and 1 Gap. Good to know Codex &amp; Claude can work well.

[CWC @chuawenching]

Day 10

Added Codex as my QA expert, reviewing what Claude/I have done so far and fixing them before shipping next. Codex (Astra 6) has identified 9 bugs, which need Claude to fix them.

[CWC @chuawenching]

Day 9 - ship #10

Tested shiplogg integration to Github in production. It worked too.

[CWC @chuawenching]

Day 9 (delayed due to busy schedule) - ship #9

- Added shiplogg integration to Github (connect button on dashboard).
- Tested locally, will roll out in production next.

[CWC @chuawenching]

Day 6 - ship #8

Added support for Antigravity 2.0 and Antigravity IDE

- Users can install today with
shiplogg init --agent antigravity

[CWC @chuawenching]

Day 5 - ship #7

Built support for Codex and it worked.

- Users can install today with
codex plugin marketplace add chuawenching/shiplogg-client
- Followed by
codex plugin add shiplogg@shiplogg

[CWC @chuawenching]

Day 4 - ship #6

The real test. Made a normal commit with Claude Code. Didn't touch shiplogg.

Ten seconds later it's on my page, attributed to claude_code.

This is the whole product working for the first time.

- Users can install today with /plugin marketplace add chuawenching/shiplogg-client
- Followed by /plugin install shiplogg@shiplogg

[CWC @chuawenching]

Day 3 - ship #5

The git hook. POSIX sh + curl. Runs after every commit, never blocks one. Reads the Co-Authored-By trailer to tell whether Claude Code or I made the commit.

Tested against localhost. It works.

[CWC @chuawenching]

Day 3 - ship #4

Remote MCP endpoint, JSON-RPC 2.0 over HTTPS, as a Rails controller. Three tools: log_ship, list_recent, stats.