CodePruner.comPostsPOSTS ADR is an Architecture Decision Record, but if we leave it like that, it won’t tell you anything. So let’s deconstruct the name into smaller pieces.Architecture Decision I like to describe it as: “Every decision in the development team that has an impact on the state of the application and the way of working in a particular time”. Ok… we have it, but here are some examples:Use TypeScript and React on the frontendCreate backend in .NETCreate the application for a cloud. Tr...

Przemysław Walkowski Oryginalnie wpis miał się nazywać Log Driven Develompment ale okazało się, że już coś takiego istnieje, nie chce tu wchodzić w szczegóły, ale jak by co zapraszam pod link, gdyby kogoś to interesowało. Mój wpis będzie o moim pomyśle, który z powodzeniem stosuje od kliku lat w projektach. Mianowice o tworzenie kodu w oparciu o logi. Czyli zamiast debugowania, proponuje przestawić się na przeglądanie logów. Poniżej szczegóły i opis tego pomysłu.

Debugging production is bad. Even access to production is bad. But debugging production is evil. I even cannot describe how evil I think it is. But if you ask most developers (including myself), they will say that this can be useful. Up to last week, I thought it cannot be done in safety way, but a new feature in Application Insights called Snapshot collector.

Often developers as a log store use text files, system events, output console or database. In some cases they use distributed systems such Splunk or Elasticsearch. In this article I would like to present how to store logs in the form of objects, rather than plain text, which also offers all sorts of graphs and charts called dashboards.