Built the backend foundation for a mobile application, with spatial data in PostgreSQL/PostGIS and access checks at the API boundary.
Architected the backend and database foundation using Node.js, Express, Supabase, PostgreSQL, and PostGIS.
Built REST API routes for authentication, map events, profiles, organizations, posts, and messaging.
Implemented JWT authentication, ownership validation, and role-based access control.
Implemented rate limiting to secure backend endpoints.
DART Aerospace
IT Technician InternJuly 2026 – Present · Montreal
Enterprise IT operations across 6 global facilities
Key contributions
Incident troubleshooting, root-cause analysis & service restoration
User access & Microsoft 365 administration
Software deployments, security & access control
Technologies
Microsoft 365FreshserviceIT SupportAccess ManagementSoftware DeploymentTroubleshootingSecurityIncident Management
Enterprise IT support focused on restoring services, managing access, and documenting incidents across 6 global facilities.
Troubleshot incidents with IT teams, analyzed root causes, restored services, and documented incidents in Freshservice.
Managed user access, software deployments, and Microsoft 365 administration.
Applied security and access-control practices across enterprise systems.
Projects
FinCore
In Development
Account changes and transactions share domain rules, keeping lifecycle state and balances consistent as the API grows.
Status: Backend in development. Account lifecycle and transaction behavior are implemented; classification, forecasting, and portfolio management remain future scope.
Customer appointments and barbershop administration, with an admin console, booking calendar, and financial charts. Booking requests recheck availability inside a locked database transaction.
Status: Core booking flows implemented. Demo hosted on Render.
Shared application configuration and file storage; runs independently of web visits.
Persistent Storage
Durable application files and database data.
Conceptual request flow and service responsibilities, not a literal Docker network topology. Files live in persistent storage; metadata lives in the database.
4 running at captureCompose project: nextcloud · Up ~7 days · PostgreSQL healthy
Separate containers keep the application, PostgreSQL, Redis and scheduled jobs independently manageable.
Volumes or bind mounts preserve data beyond a container's lifecycle. Deleting that storage can still lose data; the database retains its own persistent records.
Cron uses shared application configuration and data so jobs can run without web traffic.
Compose groups service definitions and dependencies for inspection, logs and explicit restarts over SSH.
Tailscale Serve forwards HTTPS to the local loopback service on port 8080. Redis caching and locking settings, mount paths and backup procedures are not established by the capture.
Private services are accessed through authorized devices without exposing unnecessary public endpoints.
Public Minecraft
External PlayersConnect for multiplayer
playit.ggSeparate public tunnel
Minecraft ServerProminence II on Debian
The game server uses a separate public tunnel for multiplayer access.
Local DNS Filtering
Home DevicesConfigured DNS clients
Raspberry Pi 4Dedicated network device
Pi-hole / DNSResolves and filters domains
Configured home devices use the Raspberry Pi for DNS resolution and filtering.
Three separate access paths. The public tunnel serves Minecraft; Nextcloud stays on the private path. Local DNS applies to configured home devices, not automatically to every tailnet device.Access & security notes
Devices must be authorized and connected. Nextcloud and SSH authentication, updates, device security and access controls remain necessary; private networking does not secure the whole host.
SSH over the tailnet is the administration route. This does not imply that Tailscale SSH is enabled.
DNS resolution and service reachability are separate checks. Resolving a name does not confirm that the service itself is reachable. Pi-hole filters at the DNS/domain level.
The home network connects through a Bell router. Device identifiers, real addresses, credentials and tunnel endpoints are omitted.
Minecraft console, htop monitoring, and playit.gg connectivity.Process-level CPU and memory readings help distinguish a busy process from overall host pressure; these are live checks rather than historical monitoring.View full-size ↗
Prominence II
Real multiplayer workload hosted on Debian.Memory allocation · CPU load · Process management · Connectivity & reliabilityView full-size ↗
Pi-hole Dashboard
DNS requests, filtering activity, and client statistics.View full-size ↗
Self-hosted File Storage
Nextcloud Files
Nextcloud Files — Self-hosted file management running on my Debian server.View full-size ↗
Docker Compose
Docker Compose — Nextcloud, PostgreSQL, Redis, and Cron running as separate services.View full-size ↗
Hey, I'm Tim — a backend developer who enjoys building systems that solve real problems.
I have production experience with C#, ASP.NET, SQL Server, and Azure, along with backend development
using Node.js and PostgreSQL.
My experience also includes enterprise IT support at DART Aerospace.
Outside work, I read books, listen to Hans Zimmer, and build personal applications. I enjoy
experimenting with APIs and automation, learning something new, and turning everyday problems
into useful projects. I also like helping others work through a problem, so feel free to reach out.
