Matthew C.

🚀 Just published: Effective Go Development with Claude – Best Practices for AI Pair Programming Over the past few months, I’ve been working closely with Claude-code to build real-world Go applications. It’s powerful — but only if you use the right structure, tooling, and discipline. In this article, I share a practical framework for working with LLMs, not around them: interfaces-first design, sub-agent workflows, strict linting, automated reviews with second-opinion, and more. If you’re building Go code with Claude (or thinking about it), this will save you time and sanity. #golang #AI #Claude #LLM #softwareengineering #pairprogramming #devtools

23

2 Comments

"Stop using Pull Requests" Andrea Laforgia His latest Substack article on Pull Request is pure gold. Well researched, well written. I wish I would be able to write such articles... My copy-past outtake: Pull requests have become the default code review mechanism in software teams everywhere. But the pull request was invented for open source projects, where strangers contribute code to repositories maintained by people who don’t know them. => When private teams of trusted colleagues adopt the same process, they import a model designed for low trust into an environment that should operate on high trust!!! The result is a post-development inspection system that the evidence says catches few bugs, introduces enormous waiting time, incentivises large batches, and fractures teams into isolated individuals. Link to his article: https://lnkd.in/gbyNJazj

88

15 Comments

New Article: Zero-Downtime Schema Migrations: Expand-Contract with Dual-Write Cutovers If schema changes scare you, this walkthrough helps. It shows expand-contract, dual-writes, chunked backfills, and how to flip reads with a flag and no outage. Key take-aways: Safe SQL patterns for online changes Dual-write code you can lift into your repo Backfill jobs with resume tokens and metrics Shadow reads to validate before cutover 👉 Read it: https://lnkd.in/dEa3Jj2p Curious how your team ships migrations without downtime. #systemdesign #database #postgresql #onlineddl #operability

1

Your CI/CD bill is not exploding because of “expensive runners,” it is bleeding out through flaky tests, over-parallelized jobs, and slow feedback loops that quietly tax every deploy This piece shows you how to redesign pipelines so you cut compute waste, shrink queues, and speed up developer flow without adding yet another approval gate or YAML religion Full breakdown in the comments. #DevOps #CICD #PlatformEngineering

8

1 Comment

Scaling your startup on AWS without burning through your budget? Sounds like a dream, but AWS actually hands out credits and runs programs that can save you serious cash - if you know how to grab them. This guide breaks down how startups can tap into the AWS accelerator, snag free credits, and turbocharge growth without sweating over the cloud bill. Spoiler: it’s less complicated than you think, and skipping this means leaving money on the table. #AWS #Startups #CloudComputing #TechGrowth #Entrepreneurship

2

Some engineering work is valuable, not because of features the end user sees, but because it removes complexity from the way systems are built and operated. For teams building #geospatial systems, #H3 is often a foundational part of the stack. In Go, that has usually meant working through a CGO-based library, which is more than just an implementation detail. It can complicate cross-compilation, containerization, and deployment in ways that are easy to underestimate. Removing that dependency from a foundational geospatial library does more than clean up the code. It simplifies the systems used to build and ship it. ⏩ Repo link for the pure Go implementation: https://lnkd.in/gkRXRw8F This is an example of where AI-supported development can shine. The task was not to invent a new abstraction. It was to reimplement an established library in pure Go, preserve compatibility with the existing Uber h3-go interface, and validate the result against the H3 C implementation and test suite. This is exactly the sort of problem class suited for #AI: a bounded implementation problem, a well-defined public API, and a clear external standard for correctness. #GIS #OpenSource #AIDevelopment #AIEngineering #ResponsibleAI

20

🚨 Heads up, NEAR developers Free public RPC endpoints under near.org and pagoda.co will begin deprecating on June 1, 2025. Here’s what’s changing 🧵 After review by the NEAR Infrastructure Committee, all public RPC endpoints on near.org and pagoda.co will be phased out starting June 1. This move supports decentralization and sustainability in the ecosystem. 🧠 Why this matters Pagoda’s subsidized RPC services made it harder for decentralized, high-quality RPC providers to gain traction. With Pagoda winding down, it’s time to move toward dedicated, community-powered infrastructure. 🔻 What’s being deprecated? All RPC and archival endpoints under: • rpc.*.near.org • archival-rpc.*.near.org • rpc.*.pagoda.co • archival-rpc.*.pagoda.co • and other v2, beta, and internal variants 🗓️ Deprecation timeline & rate limits: Phase 1 – June 1, 2025 • Mainnet: 120 RPM • Archival Mainnet: 16 RPM • Testnet: 120 RPM • Archival Testnet: 80 RPM Phase 2 – July 1, 2025 • Mainnet: 60 RPM • Archival Mainnet: 8 RPM • Testnet: 60 RPM • Archival Testnet: 40 RPM Phase 3 – August 1, 2025 • Mainnet: 30 RPM • Archival Mainnet: 4 RPM • Testnet: 30 RPM • Archival Testnet: 20 RPM These will be the final limits. Endpoints will remain online (via FastNear) to prevent legacy breakage. 🛠️ What you need to do Migrate away from these endpoints by June 1, 2025. Any large-scale usage after that may be rate-limited or blocked. ✅ Recommended RPC providers: • FastNear • Lava Network • Full list: https://lnkd.in/ezW2Ud52 High-volume apps should consider: • Running their own NEAR node • Using a paid tier from providers This is a major step toward a healthier, decentralized NEAR ecosystem. Don’t wait. Migrate now. 🧵🔚

2

Agents ≠ workflows. The real leverage is the hybrid: agents for judgment, flows for precision. We just rolled out Skillful Flows alongside our fully agentic stack—built for control, auditability, and speed. Read the piece. Then build your first Agent–Flow in https://app.skillfulai.io/

18

2 Comments

Are you ready to say "Hasta la vista" to outdated search methods? Elastic is releasing its first live coding session: "How to Build Hybrid Search with Elasticsearch." What’s in it for you? ✅ Learn how to combine full-text search and semantic search into a powerful hybrid search solution ✅ Discover how retrievers like Reciprocal Rank Fusion (RRF) and Linear retrievers can fine-tune your search results ✅ Watch a live demo featuring a movie search app inspired by sci-fi classics Whether you're a developer, data scientist, or just passionate about AI-driven search technology, this session will equip you with the tools to build smarter, faster, and more relevant search engines. 📅 Date: July 21 📍 Location: YouTube 👉 Register here: https://gag.gl/LqiFi0

39