This page is a look at how I think about technical work—wind development, GIS, layout strategy, automation, and the ways I organize information so projects move cleanly from concept to construction. It’s not a collection of finished projects; it’s a simple overview of the methods, tools, and principles that shape the work I do.
I’m a Development Manager focused on utility-scale wind projects. Most of my work sits at the intersection of GIS, layout design, permitting readiness, and data organization. I use ArcGIS Pro to build turbine, road, collection, substation, and T-line layout concepts, and I support the technical side of development with workflow automation in SQL Server and PowerShell.
I also enjoy the quieter parts of the job: preparing documentation for diligence, keeping geospatial data organized, refining VDR structures, and helping engineers and land teams stay aligned with clean, consistent information.
This section highlights the skills, tools, and methods I use regularly—and the things I enjoy working on most.
View My LinkedInA few small snapshots of how I tend to approach common pieces of development work.
When designing early wind layouts, I start by understanding exclusion zones, topography, landowner constraints, and access logic. I sketch around constraints first, then refine the geometry with engineering feedback and permitting considerations. The goal isn’t perfection—it’s clarity and buildability.
I rely heavily on SQL Server and PowerShell to automate data handling. Consistent inputs and automated checks reduce noise, cut down manual work, and ensure the team always has clean information for engineering and agency reviews.
A layout only works if permitting works. I integrate FAA/DOT/USFWS considerations into early design so we avoid late-stage redesigns. It’s a balance: optimize the layout, stay within the regulatory lane, and make sure decisions are documented clearly.