Aidan Harding Portfolio
Salesforce developer at Aquiva Labs whose GitHub carries plainly-named utility repos — apex-json-reader, flow-map, apex-stub-as-mock, flow-recursion — alongside his work on Nebula Core, a functional-programming library for Apex built at Nebula Consulting.
Location
Not listed — probably too busy shipping to update the bio.
Skills
What makes it work
A breakdown of the choices that make this portfolio stand out.
Repository names describe exactly what each one does
apex-json-reader and flow-map tell a reader what's inside before opening a single file — rare discipline in naming utility libraries.
Tools built on both sides of the declarative/programmatic line
Shipping both Apex-side (mocking, JSON parsing) and Flow-side (recursion, map utilities) tools shows he treats the platform as one connected toolkit.
Functional-programming concepts applied to a language not built for them
Contributing Nebula Core to bring functional patterns into Apex signals unusually deep language-level understanding.
What Salesforce Developers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Name your repositories after exactly what they do; skip cute project names for utility libraries meant to be discovered by other developers.
Build tools on both sides of the declarative/programmatic line (Flow and Apex) if you work in both — it shows you see the platform as one system.
A GitHub profile with real stars, forks, and multiple small focused repos can stand in for a traditional portfolio for a developer-heavy role.
Projects
Small, single-purpose Apex and Flow utilities, plus contributions to Nebula Consulting's core library. Each repo solves one platform gap and explains its reasoning in the README.
Nebula Consulting's base Apex library, MIT licensed. It includes a metadata-configured trigger framework, iterator-based filter() and map() operations (LazyIterator), a dynamic SOQL query builder, a dependency-injection framework for test data, and a callout wrapper. A slimmer 'Nebula Triggers' package ships just the trigger handlers.
Bringing lazy, functional-style iteration to Apex takes deep knowledge of the language's limits, and shipping it as a reusable package shows library-grade engineering.
filter()/map() over lists in Apex instead of hand-written for-loops
Metadata-driven trigger framework, also shipped as a standalone package
Merged PRs from him across 2022–2023
A small Apex class for reading values out of JSON with path expressions like 'a.b' or 'a.b[2].c', instead of casting through nested Map<String, Object> structures by hand. You can also set a default result for missing keys.
It turns a clumsy, error-prone Apex pattern into a one-line call, which is the kind of small, sharp utility senior developers leave behind on a team.
Dot-and-index path syntax for nested JSON
Configurable result for missing keys
README examples written as runnable asserts
A Flow action that brings a map data structure to Flow. It replaces many-branched decision nodes, such as picking an email template or record type from a picklist value, with one node configured with an input variable and a mapping table. The README compares it with the decision-node version and a Custom Metadata alternative.
It carries a developer idea (maps) into the low-code tool admins use, and honestly compares it with the no-code option.
One node replaces a multi-branch decision
Side-by-side comparison with decision-node and Custom Metadata approaches
Companion to his other Flow repos (flow-old-records, flow-recursion)
More Salesforce Developer portfolios
Ready to build your portfolio?
Follow the Salesforce Developer roadmap — skills, projects, and timeline to get hired.