Developer, systems & network engineer, and product builder.

I build software, cloud infrastructure, AI systems, automation, data platforms, geospatial tools, and the occasional project that somehow becomes much bigger than originally planned.

A lot of my work lives somewhere between software engineering, infrastructure, data, security, and solving problems that should probably not require five different systems.

I work on systems for businesses, organizations, institutions, and operational teams.

That includes:

• Full-stack web platforms
• Enterprise software
• AI-powered applications
• Machine learning workflows
• Cloud infrastructure
• Data engineering
• Big data systems
• Business automation
• Internal tools
• APIs and system integrations
• Infrastructure monitoring
• Secure operational platforms
• Geospatial and satellite-based systems
• Mapping and location intelligence
• Public safety software
• Administrative and institutional platforms

Some systems are public.

Some are private.

Some are better left without a repository name on the internet.

I also work on software designed for public institutions and security-related operations.

This includes systems that can help with:

• Operational coordination
• Information management
• Secure internal workflows
• Geographic awareness
• Incident and activity tracking
• Data analysis
• Decision-support tools
• Public safety operations

The goal is simple: use technology to make important systems more organized, reliable, and useful for the people operating them.

Good software cannot fix everything.

But bad software can definitely make everything worse.

I build tools that use location data, mapping, and satellite imagery for organizations and businesses.

Depending on the use case, that can include:

• Satellite imagery visualization
• Geographic information systems
• Custom interactive maps
• Asset and location monitoring
• Infrastructure visualization
• Territory analysis
• Location-based analytics
• Operational dashboards
• Geographic data processing

Basically, sometimes a normal dashboard is not enough.

Sometimes you need the planet.

I work with:

Artificial Intelligence · Machine Learning · LLMs

AI Agents · RAG · Prompt Engineering

Model Integration · AI Automation

Data Processing · Analytics

I am particularly interested in AI that becomes part of a real system instead of being added just so someone can put "AI-powered" on the homepage.

Python · SQL · PostgreSQL

Data Engineering · Big Data

ETL · Data Processing

Analytics · APIs

I like turning messy data into something people can actually use.

Sometimes the hardest part of data engineering is discovering that three systems all spell the same customer's name differently.

TypeScript · JavaScript · Python

Next.js · React · Node.js

REST APIs · Backend Systems

System Architecture · Integrations

I build both the things users see and the things users should never have to think about.

AWS · Linux · Docker

GitHub Actions · CI/CD

Cloudflare · DNS

Networking · Ubiquiti

Servers · Security

I spend enough time with servers to know that "it was working yesterday" is not a debugging strategy.

I build software that connects operations, data, APIs, infrastructure, accounting systems, CRM platforms, and internal workflows.

Tools and platforms I work with include:

Salesforce · Zoho

Workflow Automation · API Integrations

CRM · Business Systems

If someone copies the same information from one system to another every morning, I immediately start thinking about how to make them stop doing that.

I build different kinds of software, including:

• Developer platforms
• Cloud tools
• School management systems
• Administrative systems
• Business applications
• Internal enterprise tools
• AI-enabled products
• Public safety systems
• Infrastructure platforms
• Data and analytics systems
• Geospatial applications

Not every project needs to be public to be interesting.

And not every good project needs a landing page.

• Good architecture
• Reliable infrastructure
• Security
• Useful AI
• Clean interfaces
• Automation
• Data quality
• Performance
• Scalability
• Systems that people can actually understand
• Technology that solves real operational problems

And backups.

Always backups.

Preferably tested backups.

Usually somewhere between:

• building something
• designing something
• training something
• deploying something
• fixing something I deployed
• reading logs
• debugging an API
• checking a server
• staring at a map
• waiting for DNS propagation
• promising myself not to start another project

The last item remains experimental.

Fishing, technology, learning new things, and occasionally remembering that the laptop can actually be closed.

Build useful things. Keep learning. Ship carefully.