Software and cloud engineering

Most of the work is underground.

Samwise Development is Penn Porterfield’s software and cloud practice. I build the app, and I build what keeps it running after launch: the infrastructure, pipelines, backups and alarms nobody sees until they fail.

Current client ELS911school safety mapping

A plant labelled “your app” above ground. Below it, a large root system; each root ends at a label: DNS and CDN, CI/CD pipelines, IAM and secrets, queues and workers, Terraform, monitoring and alerts, and Postgres, backed up nightly.

Services

What I take on

Usually one of these, often two at once. Small companies tend to need the app and the ground under it from the same person.

  • Apps people useweb apps, APIs, internal tools

    Customer-facing web apps, admin dashboards, and the APIs behind them. Built to be read by whoever maintains them next, with tests where breakage would cost you money.TypeScriptReactVuePythonRustNodePHP/Laravel

  • The ground under themcloud infrastructure and delivery

    Networks, compute and databases on AWS, Azure, GCP or Cloudflare, written as Terraform so the whole thing can be rebuilt from a clean account. Deploys that take one command, alerts that page a person, and backups that have actually been restored.TerraformKubernetesDockerGitHub ActionsPostgresLinux

  • Devices in the fieldsensors, edge, IoT

    Hardware that reports over BLE, GPS or LoRaWAN, and the pipeline that gets its readings into a database without losing any when the signal drops.MQTTembedded CSPImanaged IoT services

  • A second opinionarchitecture reviews and cost audits

    A few days inside your setup, then a written report: what’s fragile, what’s overpriced, what to fix first, and roughly what each fix costs. Useful before a launch, a funding round, or a surprising cloud bill.

Record

Where I’ve dug before

Clients like ELS911, agency work, a few startups I helped start, and research before all that. Oldest layer at the bottom, like any core sample.

  1. Client, 2026

    ELS911 school safety infrastructure

    LiDAR scans of K-12 buildings turned into floor plans that police, fire and EMS can open in seconds. Scan processing, plan tooling, and the systems behind them.

  2. 2022 to now

    Samwise Development

    Full-stack applications for clients, and the cloud infrastructure they run on.

  3. 2021 to 2022

    Google I/O via Left Field Labs

    Production pages for Google’s developer conference. Headless Preact on the front, Jinja and Python behind it.

  4. 2020 to 2021

    Distributron co-founder

    An alcohol delivery startup that got as far as a Y Combinator interview. Vue, geofencing, JAMstack.

  5. 2019 to 2020

    Safety+

    A React and Firebase app for logging factory safety incidents as they happen. Coca-Cola was one of the first clients.

  6. 2019 to 2020

    Treetz co-founder

    An 8-bit space game for mobile, built in Unity. Co-led six developers and artists from first sketch to production builds.

  7. 2018 to 2019

    1SEO Digital Agency

    Client sites in Philadelphia on WordPress, Drupal and Magento, with React and Vue where they fit.

  8. 2010 to 2013

    Penn State Applied Research Laboratory

    Data analysis for autonomous underwater vehicles in the Underwater Acoustics Department, on DARPA-funded work.

B.S. Network and Cloud Engineering, WGU, 2026. M.S. Computer Science at Georgia Tech, in progress. Security+, Network+, ITIL 4.

Process

How a project goes

There and back again, in four steps. You talk to the person doing the work from the first call to the handoff.

  1. A call, then a written scope

    What gets built, what it costs, and what’s out of scope, in plain English. No surprises in the invoice.

  2. Something running in week one

    Small, but real and deployed, so you can click on it and react early.

  3. Written updates every Friday

    What shipped, what’s next, what’s stuck. Meetings when they help, not by default.

  4. You keep everything

    Code in your repo, infrastructure in your cloud account, and runbooks for whoever takes over.

Contact

Send me the problem.

A paragraph is plenty, and a messy doc is fine. I reply within one business day. If I’m not the right fit, I’ll say so and point you to someone who is.

fundlush@proton.me

Want the long version first? My résumé is at penn.goolz.org/cv.