Skip to content

SCN.03 · STACK

The Stack

This is the middle of my brain, laid flat so you can read it. Every language, tool and platform I have worked with, grouped the way I think about them, each with one line on how I use it. At the bottom are the integrations my teams wired into production.

201 tools · 67 daily · 134 worked with · 44 integrations named

Showing 245 of 245

Languages and frameworks 58

Every language, framework and library I have actually written in, rather than a list of things I have read about. A few of them I would not choose again, and they are still here.

Languages 13

  • Glue. Every build step, every check and every browser runner in this repo starts life as a shell script.

    Wired intoDevOps

    Open in the brain
  • The language underneath the typed one. Still what I reach for in a scratch script or a browser console at two in the morning.

    Wired intoEngineering

    Open in the brain
  • The same job as Bash on the Windows machine, with an entirely different set of surprises.

    Wired intoDevOps

    Open in the brain
  • What the secret scanners and the one off data jobs are written in. Not my first language, and it does not need to be.

    Wired intoEngineeringSecret Scanner, TextDocument ClearerProduction Data Analyst

    Open in the brain
  • The one language I mostly write against somebody else's schema. Read only, most days, and I would rather bring the query than argue about the number.

    Wired intoData

    Open in the brain
  • Catches the class of mistake I make most often, which is the wrong shape.

    Wired intoEngineeringExecutorCode Reviewer

    Open in the brain
  • Salesforce's own language. I have been in triggers and classes for behaviour no setting could give us.

    Wired intoEngineering

    Open in the brain
  • A service language I have worked in rather than chosen. I like the deployment story more than the ergonomics.

    Wired intoEngineering

    Open in the brain
  • Terraform's own language, which is how infrastructure ends up in a pull request instead of in somebody's memory.

    Wired intoDevOps

    Open in the brain
  • Where I learned to program, writing plugins for a game server. I read it more often than I write it now.

    Wired intoEngineering

    Open in the brain
  • Older platforms I have had to open and fix. Not where I would start something now.

    Wired intoEngineering

    Open in the brain
  • The desktop app I built for myself has a Rust core, which is how it ships as one file that starts instantly. I am slower in it than in TypeScript and I like what that slowness does to my decisions.

    Wired intoEngineering

    Open in the brain
  • What the stylesheets were before Tailwind. I still open it on the older front ends.

    Wired intoDesign

    Open in the brain

Frontend 9

Backend 10

  • Python with the admin and the ORM already in the box. I have maintained services built on it.

    Wired intoEngineering

    Open in the brain
  • What I still reach for when the job is four routes and a health check.

    Wired intoEngineering

    Open in the brain
  • Typed endpoints with the schema generated for me. What I would choose for a new Python service.

    Wired intoEngineering

    Open in the brain
  • Express with the overhead taken out, for the services where request cost actually showed up in the bill.

    Wired intoEngineering

    Open in the brain
  • Python for when the service is small enough that a framework would be in the way.

    Wired intoEngineering

    Open in the brain
  • Go's small HTTP framework. I have read and changed services written in it.

    Wired intoEngineering

    Open in the brain
  • The small server that runs on edge runtimes. What I use when the deploy target is a worker.

    Wired intoEngineering

    Open in the brain
  • Structured TypeScript on the server. Worth its ceremony when a team has to agree on where things go.

    Wired intoEngineering

    Open in the brain
  • The runtime for the services and for every generator in this repo.

    Wired intoEngineeringExecutor

    Open in the brain
  • The Java service framework. I have worked inside one rather than stood one up from nothing.

    Wired intoEngineering

    Open in the brain

UI and motion 11

Data access 6

  • SQL you can still see, with types over it. What I use when an ORM would be too much machinery.

    Wired intoEngineering

    Open in the brain
  • Java's ORM, from the service work. It taught me what a lazy load costs when nobody is looking.

    Wired intoEngineering

    Open in the brain
  • Schemas over MongoDB, which is the only way a document store stays legible a year later.

    Wired intoEngineering

    Open in the brain
  • Typed database access with the schema as the source of truth, and migrations I can read in a diff.

    Wired intoEngineeringPrisma MCP

    Open in the brain
  • The Python side of the same job. I have written queries through it rather than designed the models.

    Wired intoEngineering

    Open in the brain
  • An older TypeScript ORM I have worked in. Decorator heavy, and it shows its age.

    Wired intoEngineering

    Open in the brain

Building blocks 7

  • Shared state without a provider wrapped around the whole tree. Most screens need less of it than they ask for.

    Wired intoEngineering

    Open in the brain
  • Sessions and providers without writing the auth flow myself, which is not a place I want to be clever.

    Wired intoSecurity

    Open in the brain
  • Background jobs on Redis, for work that must not happen inside a request.

    Wired intoEngineering

    Open in the brain
  • Forms that do not re-render the world on every keystroke. Its dirty guard has also caught me out more than once.

    Wired intoEngineering

    Open in the brain
  • Server state done properly: caching, refetching and the loading flags I would otherwise get subtly wrong.

    Wired intoEngineering

    Open in the brain
  • A rich text editor I can actually control, for the places a plain text area was not enough.

    Wired intoEngineering

    Open in the brain
  • One schema that validates at the edge and types the code behind it. Anywhere data arrives from outside, this is there.

    Wired intoEngineering

    Open in the brain

Game servers 2

  • The plugin API I wrote my first Java against. The first code I wrote that other people used.

    Wired intoEngineering

    Open in the brain
  • Where all of this started. I ran a server, people played on it, and what they complained about became my first feature requests.

    Wired intoEngineering

    Open in the brain

Tools and platforms 143

The platforms, databases, clouds and connectors the work runs on, plus every model context protocol server I run or have used. They are grouped the way I think about them rather than by vendor.

AI and agents 11

MCP, apps and comms 15

  • The connector everything Jira and Confluence shaped goes through.

    Wired intoOpsJira and Confluence Operator

    Open in the brain
  • So an agent can read and draft in the inbox rather than me forwarding things into a chat window.

    Wired intoOpsGmail

    Open in the brain
  • So the thing booking the meeting can see the week it is booking into.

    Wired intoOpsGoogle Calendar

    Open in the brain
  • Reaches the documents where they already live, which is the only place anyone is going to look for them.

    Wired intoOpsGoogle Drive

    Open in the brain
  • Lets an agent read and write the pages instead of me copying them into a prompt.

    Wired intoOpsNotion

    Open in the brain
  • Publishes into a marketing site without a person sitting in the content editor.

    Wired intoDesignWebflow

    Open in the brain
  • So a design that a non designer can edit is one step from an agent rather than a download and a re upload.

    Wired intoDesignCanva

    Open in the brain
  • A bundle of hosted connectors, used when the alternative was building the same auth flow for the fourth time.

    Wired intoOps

    Open in the brain
  • Reads the frames and the variables, so a component gets built from the file rather than from a screenshot of it.

    Wired intoDesignFigma

    Open in the brain
  • Reaches the older shared hosting where a couple of sites still quietly live.

    Wired intoDevOpsHostinger

    Open in the brain
  • The other automation platform, for the same reason. Some of the older scenarios already run there.

    Wired intoOps

    Open in the brain
  • The same reach into the other office suite, because half the people I work with live in it.

    Wired intoOpsMicrosoft 365

    Open in the brain
  • Reads and posts in the channels, for the teams that run their whole day inside them.

    Wired intoOpsSlack

    Open in the brain
  • Reads the payments side, so a billing question gets answered out of the data instead of out of a guess.

    Wired intoOpsStripe

    Open in the brain
  • One connector that reaches a long tail of apps I would never write an integration for by hand.

    Wired intoOps

    Open in the brain

MCP, dev, data and browsers 27

  • Drives my own browser through a flow and reads the console while it goes.

    Wired intoQABrowser QAVisual QAChrome DevTools MCP

    Open in the brain
  • The search side of my session memory, so a decision from three months ago is a query rather than a scroll.

    Wired intoDataclaude-mem

    Open in the brain
  • Fetches current library documentation, because my memory of an API is not evidence.

    Wired intoResearchFramework ResearcherPhase Researcher

    Open in the brain
  • Pulls a card or a dataset into the session, read only, so an answer arrives with its query attached to it.

    Wired intoDataDomo

    Open in the brain
  • Issues, pull requests and reviews without leaving the session that is writing the code.

    Wired intoDevOpsGitHub

    Open in the brain
  • The document half of the same rule, under the same read only posture.

    Wired intoDataProduction MongoDB

    Open in the brain
  • A read only session against the relational database, opened for one job and closed after it.

    Wired intoDataProduction MySQL

    Open in the brain
  • Drives a headless browser straight from the session, for the checks nobody needs to sit and watch.

    Wired intoQAPlaywright

    Open in the brain
  • Plain web search inside the session, for the times a link is all that is needed.

    Wired intoResearch

    Open in the brain
  • The console, the network log and the performance trace, read by the agent that is about to fix them.

    Wired intoQAChrome Automation

    Open in the brain
  • The edge side of the same job: workers, records, and what the last deploy actually did.

    Wired intoDevOpsCloudflare

    Open in the brain
  • Search built for an agent rather than a person, for when the question is a shape rather than a keyword.

    Wired intoResearch

    Open in the brain
  • One request, returned as text. The smallest useful server there is, and I still reach for it.

    Wired intoResearch

    Open in the brain
  • Scoped file access for an agent running somewhere I have not handed a shell.

    Wired intoOps

    Open in the brain
  • Turns a site into text an agent can read, for the research that lives behind a page rather than an API.

    Wired intoResearch

    Open in the brain
  • A knowledge graph an agent writes to and reads back, for the facts that have to outlive a session.

    Wired intoData

    Open in the brain
  • Branch a database the way you branch code, from inside the session doing the work.

    Wired intoDataNeon

    Open in the brain
  • Asks the product analytics a question and brings the answer back, instead of me building another dashboard.

    Wired intoDataPostHog

    Open in the brain
  • Schema and migrations handled where the schema is already the source of truth.

    Wired intoDataPrisma

    Open in the brain
  • The older headless driver. Still here for the scripts that were written against it.

    Wired intoQA

    Open in the brain
  • Three servers I wrote myself, so an agent can reach the systems I run without me moving exports around by hand.

    Wired intoDevOps

    Open in the brain
  • Pulls the actual stack trace into the session that is about to go and fix it.

    Wired intoQASentry

    Open in the brain
  • Makes a model lay its steps out before it acts. It earns its place on the tangled problems and gets in the way on the simple ones.

    Wired intoResearch

    Open in the brain
  • Fetches the component source and its examples, so a build starts from the real file.

    Wired intoDesignshadcn/ui

    Open in the brain
  • Schema and rows over the hosted Postgres, without a dashboard in the middle.

    Wired intoDataSupabase

    Open in the brain
  • Deployments and logs for the projects that live there, without a tab open.

    Wired intoDevOpsVercel

    Open in the brain
  • Test plans and runs attached to the tickets, so coverage is auditable.

    Wired intoQAUnit Test Standards Author

    Open in the brain

Databases and data 22

Cloud and infra 13

Hosting and servers 5

  • The first web server I ever configured, with a rewrite rule I did not understand yet.

    Wired intoDevOps

    Open in the brain
  • The same job with the certificate handled for me. Two lines of config for what used to take twenty.

    Wired intoDevOps

    Open in the brain
  • Where I bought my first domains and pointed my first records. Mostly a registrar to me now.

    Wired intoDevOps

    Open in the brain
  • Shared hosting from before I had a pipeline. A couple of sites are still sitting there.

    Wired intoDevOpsHostinger MCP

    Open in the brain
  • Reverse proxy, certificates and static files. It sits in front of more of my things than anything else does.

    Wired intoDevOps

    Open in the brain

Testing and quality 15

  • The performance and accessibility pass before I am allowed to say a page is done.

    Wired intoQA

    Open in the brain
  • Headless browser runs when nobody needs to watch.

    Wired intoQABrowser QAPlaywright MCP

    Open in the brain
  • The accessibility rules an audit is going to run anyway, run by me first.

    Wired intoQA

    Open in the brain
  • Browser tests with a runner that made people actually write them. I have inherited more of these than I have written.

    Wired intoQA

    Open in the brain
  • The dashboards over the metrics. Where I go when somebody says it feels slow.

    Wired intoQA

    Open in the brain
  • The same job in the older repos, still running the suites that were written for it.

    Wired intoQA

    Open in the brain
  • Java tests, from the service work and the plugin years before it.

    Wired intoQA

    Open in the brain
  • Load tests written in JavaScript, for the moment somebody asks whether it holds.

    Wired intoQA

    Open in the brain
  • Traces and metrics in one vendor neutral shape, so changing backend does not mean instrumenting everything again.

    Wired intoQA

    Open in the brain
  • The Python side of the same habit, mostly over the scanners and the data jobs.

    Wired intoQA

    Open in the brain
  • What tells me something broke in production before a person has to.

    Wired intoQASentry MCP

    Open in the brain
  • Static analysis across a whole codebase, for the problems a human reviewer stops noticing around file forty.

    Wired intoQA

    Open in the brain
  • Tests that ask what a person can see rather than what the component happens to be called.

    Wired intoQA

    Open in the brain
  • The browser automation I reach for first. Fewer surprises with real forms.

    Wired intoQABrowser QA

    Open in the brain
  • The unit runner in every TypeScript project I start. Fast enough that I actually run it.

    Wired intoQA

    Open in the brain

Design and media 8

Ops, comms and commerce 18

Source control and CLIs 9

Wired into the ventures 44

These are the systems my teams connected into the products we run. 39 of Merdeka.AI's 65+ integrations are named here. The rest stay private.

Merdeka.AI 39

  • The contact center we migrated 300+ agents onto.

    Open in the brain
  • The sending path for campaign and team messages.

    Open in the brain
  • Where contracts, call recordings and attachments actually live.

    Open in the brain
  • Transactional email. Unglamorous and load bearing.

    Open in the brain
  • The design tool our designers hand off to and pull roof geometry back from.

    Open in the brain
  • A lead push integration. Leads arrive through more doors than anyone expects.

    Open in the brain
  • Automated notifications and escalations, because nobody reads the email.

    Open in the brain
  • The signature at the end of the sales flow, which is where deals become real.

    Open in the brain
  • The BI surface leadership actually opens in the morning.

    Open in the brain
  • The solar sales CRM on the other side of a great deal of my integration work.

    Open in the brain
  • One of the inverter families the equipment rules have to model correctly.

    Open in the brain
  • Another financing brand in the same filter, because homeowners have preferences.

    Open in the brain
  • Outbound calling, routed out of the platform to where the dialers live.

    Open in the brain
  • Utility rate data, which is what makes a savings number honest.

    Open in the brain
  • One more family in the same mutually exclusive catalog.

    Open in the brain
  • One of the loan partners a homeowner's financing can run through.

    Open in the brain
  • Automated panel layout, so a rep is not drawing roofs by hand at a kitchen table.

    Open in the brain
  • The newer financing path, wired end to end through the proposal service.

    Open in the brain
  • The roofing side's CRM, wired in for notes and documents.

    Open in the brain
  • Email marketing automation, tied back to a lead's own history.

    Open in the brain
  • A lease and financing partner wired straight into the proposal flow.

    Open in the brain
  • The finance system of record. I work on the integration, I do not own the ledger.

    Open in the brain
  • Financing, energy intelligence and automatic solar design behind one API.

    Open in the brain
  • The other BI surface, because no two stakeholders ever agree on one.

    Open in the brain
  • A module family the pricing and adder catalog has to know cold.

    Open in the brain
  • The upstream CRM the platform mirrors projects into and out of.

    Open in the brain
  • A third party design service that sends roofing quotes and plan sets back.

    Open in the brain
  • Where the data lands once it leaves the operational databases.

    Open in the brain
  • Another inverter family, with its own set of incompatible options.

    Open in the brain
  • Card payments, and the record of them finance asks about three months later.

    Open in the brain
  • One of the lender wirings behind proposal financing.

    Open in the brain
  • A financing brand the projects list can filter on.

    Open in the brain
  • One more finance type carried in the platform's financing options.

    Open in the brain
  • Batteries and gateways, with rules that do not mix with the others.

    Open in the brain
  • Transactional SMS out to homeowners and reps.

    Open in the brain
  • The other messaging path, for when the first one is not the right one.

    Open in the brain
  • Identity verification, and the reason that data sits somewhere I cannot read it.

    Open in the brain
  • Weather driven insurance requests, which is a very solar problem to have.

    Open in the brain
  • The middleware carrying field mappings into the finance system.

    Open in the brain

Eterna 5

  • What the plan set team draws in when a permit office wants a real drawing.

    Open in the brain
  • A CRM my teams work inside on the client's side of the fence.

    Open in the brain
  • One of the trackers my teams live in, depending on which client they sit with.

    Open in the brain
  • Another tracker, because every client picked a different one.

    Open in the brain
  • The automated permitting path, on the jurisdictions that support it.

    Open in the brain

Want to see how these connect? Open the brain.

OMAR_OS

> Stay hungry, stay foolish. · Steve Jobs