Skip to content

Instantly share code, notes, and snippets.

View mindreframer's full-sized avatar
🎯
Focusing

Roman Heinrich mindreframer

🎯
Focusing
View GitHub Profile
@mindreframer
mindreframer / docker-clear-orphaned-volumes.py
Created December 4, 2013 13:51
volumes clearing script for docker, a copy from https://github.com/dotcloud/docker/issues/197 with some fixes
#!/usr/bin/python
import json
import os
import shutil
import subprocess
import re
dockerdir = '/var/lib/docker'
volumesdir = os.path.join(dockerdir, 'volumes')

DevOps / SRE - Go(lang) / Kubernetes / Google Cloud - Junior / Senior

Talon.One is a young startup building a Promotion Engine as a service for business clients. Our core product is a platform that integrates with our clients’ systems via public APIs and automates all kinds of promotional marketing campaigns (using discounts, coupon codes, loyalty and referral programs). Marketers manage their promotions via our web app, while developers can customize the platform with webhook integrations, custom events, and even writing code in our specialized LISP dialect Talang!

There is currently no comparable product on the market that provides such level of flexibility.

Effective Engineer - Notes

What's an Effective Engineer?

  • They are the people who get things done. Effective Engineers produce results.

Adopt the Right Mindsets

$ root@plz-playground:~/please# ./bootstrap.sh
Installing Go dependencies...
pypy not found; won't build parser engine for it.
You won't be able to build Please packages unless all parsers are present.
Building Please...
Build finished; total time 0.36s, incrementality 0.0%. Outputs:
//src:please:
plz-out/bin/src/please
//src:please_parser_python2:
@mindreframer
mindreframer / gist:825e292183f15a8e7e7f134502293b14
Created October 25, 2016 10:45 — forked from SzymonPobiega/gist:5220595
DDD/CQRS/ES/Architecture videos

If you have two days to learn the very basics of modelling, Domain-Driven Design, CQRS and Event Sourcing, here's what you should do:

In the evenings read the [Domain-Driven Design Quickly Minibook]{http://www.infoq.com/minibooks/domain-driven-design-quickly}. During the day watch following great videos (in this order):

  1. Eric Evans' [What I've learned about DDD since the book]{http://www.infoq.com/presentations/ddd-eric-evans}
  2. Eric Evans' [Strategic Design - Responsibility Traps]{http://www.infoq.com/presentations/design-strategic-eric-evans}
  3. Udi Dahan's [Avoid a Failed SOA: Business & Autonomous Components to the Rescue]{http://www.infoq.com/presentations/SOA-Business-Autonomous-Components}
  4. Udi Dahan's [Command-Query Responsibility Segregation]{http://www.infoq.com/presentations/Command-Query-Responsibility-Segregation}
  5. Greg Young's [Unshackle Your Domain]{http://www.infoq.com/presentations/greg-young-unshackle-qcon08}
  6. Eric Evans' [Acknowledging CAP at the Root -- in the Domain Model]{ht
@mindreframer
mindreframer / infra-secret-management-overview.md
Created May 16, 2016 16:29 — forked from maxvt/infra-secret-management-overview.md
Infrastructure Secret Management Software Overview

Currently, there is an explosion of tools that aim to manage secrets for automated, cloud native infrastructure management. Daniel Somerfield did some work classifying the various approaches, but (as far as I know) no one has made a recent effort to summarize the various tools.

This is an attempt to give a quick overview of what can be found out there. The list is alphabetical. There will be tools that are missing, and some of the facts might be wrong--I welcome your corrections. For the purpose, I can be reached via @maxvt on Twitter, or just leave me a comment here.

There is a companion feature matrix of various tools. Comments are welcome in the same manner.

@mindreframer
mindreframer / dyanmic_or_di_elixir.md
Created September 5, 2016 16:45 — forked from timruffles/dyanmic_or_di_elixir.md
Approaches to dependency-injection/dynamic dispatch in elixir

In many production systems you'll want to have one module capable of talking to many potential implementations of a collaborator module (e.g a in memory cache, a redis-based cache etc). While testing it's useful to control which module the module under test is talking to.

Here are the approaches I can see. The two points that seem to divide the approaches are their tool-ability (dialyzer) and their ability to handle stateful implementations (which need a pid).

Passing modules

Modules are first class, so you can pass them in. Used in EEx, where passed module must implement a behaviour.