Skip to content
View peterlimg's full-sized avatar
🚀
🚀

Block or report peterlimg

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
peterlimg/README.md

Hi, I’m Peter

Former VP of Engineering. Now building an AI FinOps product.

I have spent the last 14 years building cloud systems, leading engineering teams, and working mostly in Go, AWS, Kubernetes, and distributed infrastructure.


About

  • I am working on AI FinOps: helping teams move from cloud-cost recommendations to changes they can trust.
  • Before this, I was a VP of Engineering and technical lead across cloud-native systems.
  • I helped bring a blockchain infrastructure project to launch after it had been delayed for more than three years.
  • I write about the build as it happens: product decisions, engineering tradeoffs, AI workflows, and lessons from running systems in production.
  • I am most useful around Go, AWS, distributed systems, infrastructure, and engineering leadership.

Distributed Systems Work

Some of my deepest engineering experience came from building blockchain infrastructure from the ground up.

This was not distributed systems in the usual CRUD-service sense: APIs, databases, queues, and scaling knobs. The system had no lead node with special authority. Every node in the network had the same duties, the same rules, and the same chance to participate.

The network worked only when independent machines could follow the protocol, validate state, communicate under unreliable conditions, and still converge on the same outcome. Together, those nodes formed the foundation that more complex business logic could run on.

What we could rely on was the protocol, careful implementation, enormous test coverage, and a lot of long nights debugging timing, state, networking, and consensus issues. Getting that system to launch, and stay alive, was one of the most challenging and fulfilling things I have worked on.


Core Skills

  • Programming: Go (Golang), C++, Python, React.js
  • Cloud: AWS
  • Containers: Docker, Kubernetes, Helm
  • Infra as Code: Terraform, CloudFormation
  • Distributed Systems: Consensus protocols, blockchain infrastructure, peer-to-peer networks, event-driven systems
  • DevOps: CI/CD, GitHub Actions, Observability, Monitoring

Connect

LinkedIn Substack Medium Twitter/X


Latest Writing

Latest on Substack


Current Focus

  • Building the first version of the AI FinOps product.
  • Writing in public while the product takes shape.
  • Talking to teams that care about cloud cost, infrastructure risk, and making recommendations actionable.

The hard part is not finding cloud waste. It is knowing which change is safe to make next.

Pinned Loading

  1. 0chain/0chain 0chain/0chain Public

    Züs (formerly 0Chain) is a decentralized blockchain-based storage platform with no vendor lock-in and a 3-layer security - fragmentation, proxy re-encryption, and immutability. It has close to wire…

    Go 121 62

  2. 0chain/gosdk 0chain/gosdk Public

    A client SDK in Go to interface the blockchain and storage platform, and other smart contracts

    Go 30 32

  3. 0chain/blobber 0chain/blobber Public

    A storage provider (blobber) interface to the blockchain and consumers of storage.

    Go 21 27

  4. goccy/go-json goccy/go-json Public

    Fast JSON encoder/decoder compatible with encoding/json for Go

    Go 3.7k 195

  5. View change test View change test
    1
    Before VC is enabled:
    2
    - No new magic block should be created, no miners or sharders should be removed from magic block even they are offline
    3
    
                  
    4
    After VC is enabled:
    5
    - New magic blocks will be created, we can see current VC phase in sharder /diagnostics page, possible phases are: `start`, `contribute`, `publish`, `wait`. 
  6. supabase-e supabase-e Public

    Go