Principal Engineer · 16+ years
Architecture, evaluations, observability, failure handling, cost and latency: the parts a demo never has to answer for.
Or go deeper: the live cohort ↗For directors, heads of function and founders: eight live evening sessions with Ehsan Gazar and Anoosh Zeighami, ending with a one-page 2027 AI plan for your organisation, built on a real workflow and ready for your leadership team.
Starts Wed, 4 Nov · 7:00pm London · live on Zoom
$1,495, or $1,045 with code EARLYBIRD until 23 Oct.
Enroll on Maven ↗Free, live, 30 minutes, for organisational leaders. Take one knowledge workflow apart and redesign it around AI: which old constraints still shape it, what AI changes, what must stay human, and how to run a first bounded experiment.
Also on Maven, waitlist open: Production-Ready Systems with LLMs and Agents ↗ · From Senior to Staff: Master the Architecture Skills That Get You Promoted ↗
29+ engineers and colleagues, sharing what changed after we worked together.
“Gazar is very expert in front-end knowledge. He is very kind and patient in helping and guiding without any judgment. Whenever I talk to him, I learn many things. Actually, he shares his updated knowledge in front-end and AI with me. I am very grateful to him for his help without any expectations.”
“It has been a pleasure working with Ehsan. He is a dedicated, self-motivated and knowledgeable software engineer. He always embraces new challenges at work. He has a positive attitude and desire to produce quality work that serves him well. He would be a valuable team member of any software team.”
“Working with Ehsan has been a blast! Ehsan has done an excellent job as the JavaScript Developer at Round Table Apps. He is also very attentive to details and creative in creating an engaging experience. I would highly recommend Ehsan as an invaluable asset to any organisation or team.”
An open-source terminal for running coding agents. See what each one changed, read the diff, then stage and commit without leaving it. No account, no telemetry.
See Marlin →One TypeScript problem, written from memory against hidden tests, on a schedule that brings it back just before you would have forgotten it. No account needed to try one.
Your team added AI to one step and the work arrives no sooner. The workflow itself is built on old constraints, and that is what needs redesigning.
Your AI plan looks like your last digital programme: a tool, a rollout, a go-live date. What carries over, what breaks, and what to run instead.
Your AI pilot made one step faster, but the results did not move. The cause is usually the slowest step, and what you did with the time.
Vendors call everything an agent. Here is what each step from chatbot to agent adds, and how much supervision each one needs from you.
AI can do brilliant work and still fail a simple task. Leaders need to separate what it can do from whether they can depend on it.
I use AI every day, I enjoy it, and I am not going back. What it quietly took is the part of me that produces code from an empty file: the best practices I used to apply without thinking, and the problem solving underneath them. Why the existing practice sites did not fit, and what I built instead.
What other engineers have been reading in the last seven days.
Replaced ESLint with oxlint in a React TypeScript project and cut lint time from 12 seconds to under one. What I traded away and whether it was worth it.
Lefthook replaces Husky and lint-staged with a single Go binary, parallel hook execution, and built-in file filtering. Here is why I switched and kept going.
Compare the leading monorepo tools: NX, Turborepo, Bazel, Rush, and PNPM workspaces. Choose the right fit for your team size, stack, and build needs.
Clayton Christensen showed why good engineering teams build irrelevant products. The paradox of listening to your best customers, and how to stop ignoring the toy technologies that will eventually replace you.
The kernel dropped the experimental label, Cloudflare rewrote its proxy, and your JavaScript build is already Rust underneath. That is the case for learning it. The case against is that the most important TypeScript tool of the decade picked Go. Here is how I read the trade-off, and where I would still not leave TypeScript.
Worked solutions to every SQLZoo SELECT from WORLD exercise, from basic filtering to population and GDP-per-capita queries, each explained step by step.
The deep dives I'd point a senior engineer at first, grouped by topic.
Worked SQLZoo solutions, joins, aggregates, GROUP BY vs HAVING, and subqueries — the queries interviewers actually ask.
9 deep dives · Start reading →
Indexes, query optimisation, sharding, replication and normalization — how to make a database fast and keep it fast.
8 deep dives · Start reading →Why oxlint replaced ESLint, pnpm vs npm, Lefthook vs Husky, and the Rust/Go shift in the frontend toolchain.
6 deep dives · Start reading →
Arrays, linked lists, stacks, queues, trees, tries, graphs, heaps and hash tables — implemented and explained in TypeScript.
12 deep dives · Start reading →
Insertion, selection, merge and quick sort, plus binary and substring search — the classic algorithms, step by step.
6 deep dives · Start reading →
What a design system really is (per Atlassian), how Dropbox and Netflix build theirs, and how to roll out an internal UI component library.
6 deep dives · Start reading →
Horizontal vs vertical scaling, capacity estimation, resilience patterns and the architecture principles behind systems that grow.
6 deep dives · Start reading →
Head-to-head breakdowns — oxlint vs ESLint, REST vs GraphQL, SQL vs NoSQL, Svelte/Preact vs React — with the trade-offs that decide it.
12 deep dives · Start reading →
