Peter Hecke is a Senior Content Developer and seasoned software engineer with over 20 years of experience building scientific and enterprise applications, SDKs, and developer documentation for products like Microsoft Dynamics 365 and Power Platform. Based in Bellevue, Washington, he blends hands-on C# and .NET backend development—especially for Dataverse, Web APIs, and service-to-service authentication—with clear, maintainable technical writing and sample code creation. At Microsoft he authors developer docs and Power Apps samples (including contributions to the high-profile microsoft/PowerApps-Samples repo) while applying cloud and identity technologies such as Azure AD, Service Bus, and OAuth2. Comfortable as a self-starter or a leader on geographically distributed teams, he emphasizes readable, performant code and documentation workflows using GitHub, NuGet, XML, and Markdown. His background spans embedded scientific engineering at Lockheed and SGI to spec-writing at Bluetooth SIG, giving him an uncommon mix of low-level systems intuition and consumer-facing API experience.
10 years of coding experience
14 years of employment as a software developer
Bachelor of Science (BS), Mechanical Engineering, Bachelor of Science (BS), Mechanical Engineering at New Jersey Institute of Technology
Mechanical Engineering, Mechanical Engineering at Santa Clara University
Computer Programming, Computer Programming at Bellevue Community College
Contributions:10 reviews, 1694 commits, 75 PRs in 4 years 1 month
Contributions summary:Peter's contributions primarily involve modifying the `.acrolinx-config.edn` file, likely to adjust the configuration for a content quality and style checking tool like Acrolinx. These changes focus on adjusting allowed branch names and filename matches, as well as settings related to the guidance profile. The commits suggest an effort to refine the documentation process, potentially to enforce specific style guidelines or to exclude certain sections of the documentation from being checked. The changes impact the documentation quality workflow.
Sample code for Power Apps, including Dataverse, model-driven apps, canvas apps, Power Apps component framework, portals, and AI Builder.
Role in this project:
Back-end Developer
Contributions:39 reviews, 182 commits, 244 PRs in 3 years 11 months
Contributions summary:Peter contributed to the Power Apps samples by adding and modifying C# code related to plugins. These plugins interact with the Common Data Service (CDS), creating and updating records, and implementing business logic. They added samples for single-tenant service-to-service authentication with the Web API. Further, the user was involved in updating and modifying project files, showcasing expertise in building and deploying Power Apps components.
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.
Request Free Trial
Peter Hecke - Senior Content Developer at Microsoft