Ed Harrod
@ed-ventures.bsky.social
Staff Software Engineer @ Luno
🌱🧘🏉⚽👨💻🏋️🚴
Building in public with #encore, #golang, #supabase, #postgreSQL, #claudeCode
Writing about: #mcp, #ai, #socialimpact
🌱🧘🏉⚽👨💻🏋️🚴
Building in public with #encore, #golang, #supabase, #postgreSQL, #claudeCode
Writing about: #mcp, #ai, #socialimpact
Been using Greptile & CodeRabbit as AI Code Review tools, and I have to say that CodeRabbit wins HANDS DOWN:
1️⃣ More configurable
2️⃣ 1-click suggestions are smoother
3️⃣ Hides non-important information automatically
4️⃣ Greptile's dashboard was frequently giving me errors
5️⃣ The little CodeRabbit poem
1️⃣ More configurable
2️⃣ 1-click suggestions are smoother
3️⃣ Hides non-important information automatically
4️⃣ Greptile's dashboard was frequently giving me errors
5️⃣ The little CodeRabbit poem
December 23, 2025 at 11:26 AM
Been using Greptile & CodeRabbit as AI Code Review tools, and I have to say that CodeRabbit wins HANDS DOWN:
1️⃣ More configurable
2️⃣ 1-click suggestions are smoother
3️⃣ Hides non-important information automatically
4️⃣ Greptile's dashboard was frequently giving me errors
5️⃣ The little CodeRabbit poem
1️⃣ More configurable
2️⃣ 1-click suggestions are smoother
3️⃣ Hides non-important information automatically
4️⃣ Greptile's dashboard was frequently giving me errors
5️⃣ The little CodeRabbit poem
Not as fully fledged as Jira, but at @givrapp.bsky.social we have been using @github.com Projects for managing issues. Process is:
1. Anyone creates an issue
2. Engineers add any technical detail necessary
3. Engineers assign to Claude/Copilot
4. MR is created for the issue
#buildInPublic
1. Anyone creates an issue
2. Engineers add any technical detail necessary
3. Engineers assign to Claude/Copilot
4. MR is created for the issue
#buildInPublic
December 6, 2025 at 7:52 AM
Not as fully fledged as Jira, but at @givrapp.bsky.social we have been using @github.com Projects for managing issues. Process is:
1. Anyone creates an issue
2. Engineers add any technical detail necessary
3. Engineers assign to Claude/Copilot
4. MR is created for the issue
#buildInPublic
1. Anyone creates an issue
2. Engineers add any technical detail necessary
3. Engineers assign to Claude/Copilot
4. MR is created for the issue
#buildInPublic
From Claude Code v1.0.86 you can check your context with the `/context` command. Doing that made me realise just from the Atlassian, Slack & a GitLab MCP servers I was using up 34% of my context window! 😦
Can see why it seems to have built-in preference to using CLI tools over MCP #buildInPublic
Can see why it seems to have built-in preference to using CLI tools over MCP #buildInPublic
December 1, 2025 at 6:16 PM
From Claude Code v1.0.86 you can check your context with the `/context` command. Doing that made me realise just from the Atlassian, Slack & a GitLab MCP servers I was using up 34% of my context window! 😦
Can see why it seems to have built-in preference to using CLI tools over MCP #buildInPublic
Can see why it seems to have built-in preference to using CLI tools over MCP #buildInPublic
Been enjoying using github.com/github/spec-... recently for more complex tasks that you can't "few shot" - trying to convert an iOS app into an Android app (with a shared swift submodule). Created 234 tasks for that pretty easily! Also tying in different AI reviewers at each stage #buildinpublic
November 24, 2025 at 3:12 PM
Been enjoying using github.com/github/spec-... recently for more complex tasks that you can't "few shot" - trying to convert an iOS app into an Android app (with a shared swift submodule). Created 234 tasks for that pretty easily! Also tying in different AI reviewers at each stage #buildinpublic
Cool feature in #encore where a `func (r req) Validate()` function is called on a struct by the middleware when parsing an API request. Unfortunately this is silently skipped if the `req` passed to API definition is a pointer (or vice versa).
I wrote a hook to catch this: github.com/encoredev/en...
I wrote a hook to catch this: github.com/encoredev/en...
Pre-commit hook to catch `Validate()` middleware functions being silently skipped · encoredev encore · Discussion #2095
Encore's validate feature, where a: func (req myReq) Validation() error { function is automatically is run by the middleware is very cool, but unfortunately it silently fails if the validate receiv...
github.com
October 4, 2025 at 12:57 PM
Cool feature in #encore where a `func (r req) Validate()` function is called on a struct by the middleware when parsing an API request. Unfortunately this is silently skipped if the `req` passed to API definition is a pointer (or vice versa).
I wrote a hook to catch this: github.com/encoredev/en...
I wrote a hook to catch this: github.com/encoredev/en...
And another @encoredotdev.bsky.social
snippet so you can auto-generate FE client(s) whenever your #OpenAPI backend spec changes: github.com/encoredev/en...
#buildinpublic #encore
snippet so you can auto-generate FE client(s) whenever your #OpenAPI backend spec changes: github.com/encoredev/en...
#buildinpublic #encore
GitHub action to regenerate TS, OpenAPI & Swift clients in separate repos · encoredev encore · Discussion #1549
Adding a GitHub action which looks for Go changes and automatically regenerates means: you don't have to worry about generating the clients yourself you're less likely to have the BE/FE out of sync...
github.com
September 25, 2025 at 5:54 AM
And another @encoredotdev.bsky.social
snippet so you can auto-generate FE client(s) whenever your #OpenAPI backend spec changes: github.com/encoredev/en...
#buildinpublic #encore
snippet so you can auto-generate FE client(s) whenever your #OpenAPI backend spec changes: github.com/encoredev/en...
#buildinpublic #encore
Sharing an @encoredotdev.bsky.social snippet which allows you to run Encore tests on pre-commit, to "shift left" test failures, so they are caught at commit time rather than in CI: github.com/encoredev/en... #buildinpublic #encore
.pre-commit-config.yaml for running encore tests · encoredev encore · Discussion #1555
I frequently found my deploys were broken because of a failing test, which I didn't realise for a little while. Adding to pre-commit allows you to "shift left" the failures, so they are caught earl...
github.com
September 24, 2025 at 2:35 PM
Sharing an @encoredotdev.bsky.social snippet which allows you to run Encore tests on pre-commit, to "shift left" test failures, so they are caught at commit time rather than in CI: github.com/encoredev/en... #buildinpublic #encore
Connecting multiple MCP servers with
@kilocode.ai feels like cheating: I pasted an error "Detected ID token issuer is not an Apple ID token issuer" and it searched @encoredotdev.bsky.social + @supabase.com logs via MCP, immediately worked it out, and made a PR via
@github.com #MCP 🥳 #buildinpublic
@kilocode.ai feels like cheating: I pasted an error "Detected ID token issuer is not an Apple ID token issuer" and it searched @encoredotdev.bsky.social + @supabase.com logs via MCP, immediately worked it out, and made a PR via
@github.com #MCP 🥳 #buildinpublic
August 25, 2025 at 6:42 PM
Connecting multiple MCP servers with
@kilocode.ai feels like cheating: I pasted an error "Detected ID token issuer is not an Apple ID token issuer" and it searched @encoredotdev.bsky.social + @supabase.com logs via MCP, immediately worked it out, and made a PR via
@github.com #MCP 🥳 #buildinpublic
@kilocode.ai feels like cheating: I pasted an error "Detected ID token issuer is not an Apple ID token issuer" and it searched @encoredotdev.bsky.social + @supabase.com logs via MCP, immediately worked it out, and made a PR via
@github.com #MCP 🥳 #buildinpublic