- Could you summarize that, please?
- Sure, I can also roninze it.

From the recent podcast: Open-source projects are mostly divided in two categories: frameworks and libraries. Frameworks (e.g. kubernetes) have overarching architecture, have many features and expect you to build in top of it. Libraries solve one specific problem.

If you develop a library, then avoid new features unless they help you solve that specific problem.

This is where "open sourced closed to contribution" is coming from.

A text that is striving for precision need to be easily editable and easily commentable. That's why we use wiki-like engines for the software documentation.

If we could manage to make similar thing with the text of our laws it would bring tremendous effect. Unfortunately no one knows how to do it.

Your documentation has a lot of dead pages and you don't know them. One example: you might have a guide for your devs how to install your product on the local environment but the truth is — you have no idea if it's correct or not unless someone comes in and manually runs it through. In all teams I have ever worked this guide was updated only when a new person was starting in a team.

From the recent Stackoverflow Podcast "Dev meet Ops": SRE always complain about the docs. Docs are written by developers and developers generally hate to write docs. But devs also hate to be disturbed about incidents directly. So we employed a mind-trick. For some reason people are ok writing bullet points and we asked devs to write incident guides as bullet points and the last point was "if nothing in this list helped, contact the developers". Also all the guides were easily editable.

During my Study on there was an exercise with Logic Apps. They reminded me a little about the BPMN but focused entirely on Azure services.

I wouldn't use them even for a simple workflows though - despite being seemingly simple and having a visual editor there's too much magic behind it. Also it's not very scalable once your workflow becomes large enough.

First course in about 50 from the Azure learning paths that I was actually eager to watch till the end. The magic of the good stuff is "learning by doing".

Configuring Azure API Management.

Nice job, Matthew Quickenden

Continuing learning path on Azure solutions.

The identity management course was longer but also better than the others thanks to demos of many features. The topic however is mostly interesting to Core IT admins rather than to Software Engineers

Continuing with AZ-304 Path on - the "Microsoft Azure Security Solutions" course is extremely generic and quite boring - I would prefer live demos instead of lifeless visuals, also some parts can be shortened in half. Self-test is also too easy. Still an ok overview of the topic.

Ничего особо интересного в этом курсе - по сути рассказывается про Log Analytics и базово про то, как настраивать логи и предупреждения (alerts)

Продолжаем изучать AZ-304. Курс про ажуровский биллинг довольно скучный. Единственное, что запомнилось, что исходящий трафик стоит 1 цент за гиг, и что трафик между зонами доступности и между регионами считается исходящим трафиком.

Первые пять гиг они дают бесплатно, но это мало, конечно.

Продолжаю изучать az-304 . С лабами довольно интересно придумали, хотя сами Лабы очень простые пока

В этом сезоне онлайн-квестов мы заняли 3-е месте. До 2-го нам не хватило 72 секунды в последней игре.

Show older
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!