Skip to content
View petesramek's full-sized avatar

Block or report petesramek

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
petesramek/README.md

Hi, I'm Pete Sramek 👋

I build software that stays understandable, behaves well in production, and can keep evolving without becoming an operational burden.

Most of my background is in backend, cloud, mobile, and distributed systems. I invest in understanding system behavior, keeping architecture proportional, and dealing with practical concerns like performance, diagnostics, and reliability.

This is the technical territory I tend to operate in most often, along with the principles that shape how I approach it.

Frameworks

  • .NET
  • ASP.NET Core
  • .NET MAUI

Cloud platforms

  • Azure
  • Amazon Web Services (AWS)

Systems

  • Backend, mobile, and cloud systems
  • Monoliths built for MVP delivery
  • Distributed systems, including service-oriented, microservice-based, and stateful systems

Concerns

  • System design and product foundations
  • System behavior, data consistency, and correctness
  • Performance, reliability, observability, and operability
  • System modernization, migration, and technical debt
  • Application and data security
  • CI/CD and engineering workflows

Principles

  • clear design over unnecessary complexity
  • production behavior over theory
  • maintainability over cleverness
  • useful automation over ceremony
  • systems teams can understand, operate, and keep evolving

Repositories

A selection of hands-on comparisons, diagnostics labs, reusable libraries, and protocol experiments.

Microservices vs Virtual Actors

Hands-on comparison of two approaches to the same distributed workflow, focused on trade-offs in state ownership, concurrency, deployment, observability, and operations.

.NET Production Diagnostics Lab

ASP.NET Core diagnostics lab showing production-style problems and practical improvements around reliability, performance, and observability.

Polyline Algorithm for .NET

A .NET library for encoding and decoding Google-compatible polylines, designed to stay small, predictable, and easy to integrate.

ReqCap

A .NET library for evaluating capabilities against requirements, focused on explicit rules, structured outcomes, and extensible evaluation logic.

TinyLink

A lightweight serial communication protocol experiment for constrained devices, built around reliable UART communication and practical robustness under tight limits.

Links

Pinned Loading

  1. polyline-algorithm-csharp polyline-algorithm-csharp Public

    Lightweight .NET Standard 2.1 library implementing Google Encoded Polyline Algorithm.

    C# 6 1

  2. reqcap reqcap Public

    A lightweight requirements and capabilities evaluation library for .NET

    C#

  3. dotnet-production-diagnostics-lab dotnet-production-diagnostics-lab Public

    ASP.NET Core diagnostics lab showing common production-style problems and practical improvements for reliability, performance, and observability.

    C#

  4. microservices-vs-virtual-actors microservices-vs-virtual-actors Public

    Hands-on comparison of microservice-style and virtual actor-style designs for the same distributed workflow, including development, testing, deployment, scaling, and operational trade-offs.

    C#

  5. tiny-link tiny-link Public

    TinyLink is a lightweight, template-based serial protocol for reliable UART communication between microcontrollers. It features a robust state machine, checksum validation, and a hardware-agnostic …

    C++ 1