Giancarlo Petrini NG TECH LLC

I build apps and workflows, and I keep the AI slop out.

Two of my apps are on the App Store. Before that I spent 43 days moving a real-time bidding server from Node.js to Rust while it kept serving 100,000 requests a second, without ever taking it down. In between sit the workflows: ingestion pipelines, release automation, and agent systems that handle the tedious parts without being allowed to decide anything.

I build a lot of it with AI and I am about as skeptical of it as someone can be while using it every day. The web is filling up with generated work nobody checked. I would rather ship less and have it hold up.

There is exactly one exception on this site: the research section is machine-written on purpose, and it says so on every page. Everything else here, I wrote.

Apps

Small apps, shipped under my own name.

Not prototypes and not client work I can't show you. Both are free and both went through real App Store review. Let's Dance Robot is ad-supported, so every release has to clear the tracking disclosures, consent prompt, and privacy manifest that come with an ad stack — the part of review most likely to get you rejected. Unearth v1.1 ships none of that.

Each version says exactly what it does and keeps its own policy URL alive forever, which is the point: whatever a later build changes, the promise made to the one you installed stays true.

Hire me for

Three kinds of work.

Contract iOS and Android development

Building an app from scratch, finishing one that stalled, or fixing the release process that keeps breaking. Both of my apps started as an idea and no repository. I have since shipped fifteen releases of one of them through App Store review and ported it to Google Play, so I know where both processes snag.

How I actually ship is written up in full, including the parts I don't let the automation decide.

Systems that got slow or expensive

High-throughput services, latency you can't explain, an infrastructure bill that keeps climbing. The Rust migration on my work page cut memory about eleven-fold and CPU by roughly 60%, and it paid for itself in under a month.

AI integration, from someone skeptical of it

I build agent workflows for a living and I still won't let one make a decision unreviewed. If you want AI wired into a real process, I will be direct with you about which parts it should touch and which parts it should stay away from.

How I work

A person approves everything that ships.

I have watched enough agents do the wrong thing confidently to stop trusting any workflow that doesn't have a human standing at the end of it.

The automation I build is real and I use it every day. It drafts, it collects, it verifies, it handles the tedious parts of a release. What it does not do is decide. Release calls, reviewer replies, and privacy disclosures are mine, every time, because those are the things that are expensive to get wrong.

I don't hand-write Swift or Kotlin, and I'll say so up front. What I know is systems — how something should behave, where a design gives way, and how to take an implementation apart until it either holds up or breaks in front of me. That's the actual job, and it is the difference between an app and generated slop that happened to compile.

That's also why the two halves of this site look different. The research section is cold and labeled. This side is warm and signed. If I ever let those blur together, you would have no way to tell which one you were reading.

Insights

Machine-written on purpose

An AI pipeline reads the landscape so I don't have to.

Agents pull primary sources on AI agents, developer tools, and platform infrastructure. A fixed set of prompts turns them into daily and weekly briefs. I approve what publishes and nothing goes out unsourced. It is labeled everywhere because you deserve to know which voice you are reading, and because the pipeline itself is a working demo of what I get hired to build.

1309 pieces published so far, against 1988 linked primary sources.

Contact

Tell me what's in your way.

Email is best. Send the shape of the problem and what you have tried already, and I will tell you quickly whether I am the right person for it. If I'm not, I will say so rather than take the work.

NG Tech LLC · Greensboro, NC LinkedIn GitHub