Training the next generation of FDEs and AI engineers

Excited about training the next generation of FDE and AI engineers at Plank! The way we build software is changing every few months and the only way businesses can keep up is with on-going training of team members.

The way you built 6 months ago is already LEGACY.

On a post by Plank2,838 followers
Our AI accelerator team just released a new video! This time, we're showing a bit of what we've been building: AI extraction pipelines, async processing, parallel workflows, and human validation based on confidence scores.
Read Plank’s full post on LinkedIn 
  • Forward deployed engineering
  • Plank

Keep reading

Coding agents

PostHog's 70x faster SQL parser built with Claude Code

Robbie Coomber from PostHog rewrote PostHog's SQL parser using multiple long-running Claude Code sessions in parallel. The result was 16K lines of "hand"-rolled parser code, 5K lines of tooling, a few more K of tests, and a ~70x speed up! Thats awesome. There really is no excuse to not ask Claude or Codex to optimize your codebase. Of course it requires providing the right evals and harness so that it has a way to measure correctness in an objective way. Also I love that they have a formal declarative grammar for the parser using ANTLR .g4 format. Read more here: posthog.com/blog/sql-parser

Software architecture

Microsoft pg_durable and keeping everything in the database

Microsoft open sources pg_durable - this allows durable task execution within PostgreSQL. I personally really like the pattern of keeping everything within the database and avoid external queues, multiple databases to manage state, locks etc. Every additional architecture module introduces complexity that might not be needed. In most applications if you keep everything within the DB, it makes each individual flow fast, clean, contained. And re: scaling, just scale vertically and then shard as needed. That works for most b2b apps. github.com/microsoft/pg_durable