Blog

Engineering in depth

Technical content on architecture, performance, developer experience, and the craft of building software that scales.

AI AssistantsScopingProduct StrategyWorkflowsAI SystemsData FoundationsKnowledge SystemsArchitecture

39

Archive posts

29

On-site

10

External

4/5

Page

AI AssistantsScopingProduct StrategyWorkflowsAI SystemsData FoundationsKnowledge SystemsArchitectureTechnical LeadershipStartupsEngineering ManagementDeliveryResearch CollaborationUniversitiesProfessorsTechnical Writing
AI AssistantsScopingProduct StrategyWorkflowsAI SystemsData FoundationsKnowledge SystemsArchitectureTechnical LeadershipStartupsEngineering ManagementDeliveryResearch CollaborationUniversitiesProfessorsTechnical Writing

39

All posts

29

Original site essays

10

External links

10

Medium posts

Crawlable archive

Engineering in depth

39 published articles in this archive. Internal essays stay on-site and external posts open on their original platforms.

Cloud / DevOps

Building at scale: Lessons from 300M+ event pipelines

How we optimized AWS serverless workloads to manage massive analytics ingestion and speed up Athena queries by 12x.

8 minJan 2025
Read
AI / ML

AI in production: Guardrails and trusted workflows

Moving beyond chatbots: implementing robust RAG systems with rigorous evaluation and autonomous agents that don't hallucinate.

6 minJan 2025
Read
FinTech

FinTech & Engineering: Where MScFE meets systems

Applying quantitative finance models to distributed engineering architectures for high-frequency trading platforms.

5 minDec 2024
Read
Web Dev

Type-Safe APIs with tRPC and Next.js App Router

A deep dive into building end-to-end type-safe monorepos, reducing runtime errors to near zero.

4 minNov 2024
Read
Blockchain

Basics of Blockchain Everyone Should Know - Part 1A: The Fundamentals

An approachable introduction to decentralization, cryptography, and distributed ledgers for readers entering blockchain from a practical angle.

BlockchainWeb3Fundamentals
5 minOct 2024
Open on Medium
Cloud / DevOps

Running Puppeteer/Chromium on AWS Lambda with Node.js 20+

A deployment-focused guide for getting Puppeteer and Chromium working on modern AWS Lambda runtimes with fewer compatibility issues.

AWS LambdaPuppeteerNode.js
7 minOct 2024
Open on Medium
Cloud / DevOps

Scaling Node.js/Express App Using Worker Threads and Clusters

A Node.js scaling article exploring how worker threads and clusters help reduce bottlenecks in CPU-heavy or concurrency-sensitive services.

Node.jsExpressScaling
6 minJul 2024
Open on Medium
Web Dev

Optimizing 3D Model Rendering in Next.js with React Fiber Offscreen

A performance-minded article on reducing blocking time while rendering 3D assets in Next.js and React-based interfaces.

React Three FiberNext.jsPerformance
6 minMar 2024
Open on Medium
Web Dev

Creating Animated Avatar for Your Portfolio Website Using Ready Player, Mixamo, Next.js

A practical portfolio engineering article covering animated avatars, Mixamo workflows, and web presentation with Next.js and 3D tooling.

Portfolio3DNext.js
7 minFeb 2024
Open on Medium

Editorial model

Why the archive is split this way

01

On-site posts are written for deeper internal linking, stronger SEO coverage, and longer-form architectural explanation.

02

External posts remain linked to their original source so the canonical article stays where it was first published.

03

Source filters make it easier for readers and search engines to understand where content lives and how it relates.

04

Pagination is route-based so archive pages remain crawlable without client-only query state.

This archive intentionally combines original on-site essays with external writing so readers can evaluate one connected body of work while still respecting the canonical destination of outside posts.

Publishing system

How the archive grows

A content model shaped by production work, research-facing thinking, and public technical artifacts.

01

Start from repeated friction

The best articles begin with recurring technical, product, hiring, or research questions that keep showing up in practice.

02

Connect to evidence

Every useful article should connect to shipped systems, public projects, open source, or clearly scoped technical direction.

03

Link the knowledge graph

Articles should guide readers toward related services, projects, profiles, and adjacent essays instead of living in isolation.

04

Preserve canonical destinations

When a piece belongs on an external platform, the archive links outward instead of pretending the post was originally published here.

Topics covered

Archive taxonomy

The recurring technical and strategic themes represented across this archive.

AI AssistantsScopingProduct StrategyWorkflowsAI SystemsData FoundationsKnowledge SystemsArchitectureTechnical LeadershipStartupsEngineering ManagementDeliveryResearch CollaborationUniversitiesProfessorsTechnical WritingNext.jsPerformanceSEOContent PlatformsHiringInterviewsFull-StackAI EngineeringConsultingAdvisoryCollaborationRAGGuardrailsProductionOpen SourceDue DiligenceEvaluationCloud CostOptimizationData EngineeringObservabilityAWSAnalyticsPlatform EngineeringDeveloper ExperienceAdoptionInternal ToolsCase StudiesClient WorkHackathonsRoadmappingPrototypingMonorepoModernizationCI/CDPackage DesignMaintenanceAcademic PartnershipsResearchProduct ThinkingEngineering JudgmentFinTechProduct SystemsRiskMentorshipCode ReviewTeam GrowthFinancial EngineeringSystems ThinkingServerlessContainersCloud ArchitectureInfrastructureTechnical EvaluationWeb3BlockchainProduct DesignSmart ContractsReact NativeiOSXcodeAndroidBuild ConfigFundamentalsAWS LambdaPuppeteerNode.jsExpressScalingReact Three FiberPortfolio3DWeb WorkersQuantum ComputingPWASerwist

Archive FAQ

Common questions

A few quick answers about how the archive works.

Some articles were originally published elsewhere and remain canonical there. The archive keeps them visible while sending readers to the original source.

They make the archive easier to browse, easier to index, and easier to understand for both readers and search engines.

Yes. On-site essays are usually more tightly integrated with the rest of the portfolio through internal linking, related sections, and deeper context.

Absolutely. The best prompts for new writing usually come from real engineering, hiring, research, or product questions.

Want to turn these ideas into execution?

The archive is one way to evaluate how I think. Direct collaboration is where that thinking becomes implementation leverage.