brgd.eu
Hi, this is my website.
I wanted to have an outpost where I can share things I have found on the web. This is what you will find below in the link list. Besides that, there's currently not much more to see here.
Link List
Valeriepieris circle - Wikipedia
https://en.m.wikipedia.org/wiki/Valeriepieris_circle2022-03-14
Pandemic Backsliding Project (PanDem)
https://www.v-dem.net/shiny/PanDem/2022-02-24
Looks at the democracy indices and violations of most countries of the world during the pandemic. When one clicks on the country one can find a link to the corresponding Github project which lists the reasonings for the score of that country in more detail.
1 + 1 = 3: Explaining Busyness and Background Noise on Websites · Jens Oliver Meiert
https://meiert.com/en/blog/1-1-3-explaining-busyness-and-background-noise-on-websites/2022-02-13
A fascinating design concept I didn't know about. I should keep it in mind. It's also nice that the article is short. Further, it links to other books by Edward Tufte. Definitely worth it to check these out!
History: The Agile Manifesto
https://agilemanifesto.org/history.html2022-02-12
Writes a bit about how the "Agile Manifesto" came to be. This was linked on the last blog post (below) I wrote about. An interesting passage from the article: m> The Agile movement is not anti-methodology, in fact, many of us want to restore credibility to the word methodology. We want to restore a balance. We embrace modeling, but not in order to file some diagram in a dusty corporate repository. We embrace documentation, but not hundreds of pages of never-maintained and rarely-used tomes. We plan, but recognize the limits of planning in a turbulent environment. Note: Only now I realized that this is even from agilemanifesto.org, ha!
Agile as Trauma
https://doriantaylor.com/agile-as-trauma2022-02-10
Thought-provoking write-up on agile methodologies. Goes into how they came to be, how most of it existed already before the Agile Manifesto etc. The article goes further into many more details, notable here are the point that collaboration is talked very much about, while at the same time that exactly is so time-consuming. Furthermore, I find the ideas of the "specifity gradient" and especially the "conceptual integrity" very useful. Conceptual integrity, meaning that everybody in the company has the same mental models of the software being built, is something I have seen missed before multiple times. Finally, another interesting topic in the article I would like to highlight is features vs. behavior. While features are important for marketing, behavior might be what you really want to look out for. Besides the interesting topics the article touches it also gives some further links and background reading that I think would be interesting to read next.
Gorillas: Special offer - unicorn slices, 150g 🦍❤️
https://zerforschung.org/posts/gorillas-en/2022-01-26
Interesting write-up on the security practices of Gorillas, a quickly growing German (?) startup that delivers groceries super quickly. The write-up is especially interesting if one wants to understand how security vulnerabilities can be found and how they might be used to access resources that were not thought of consumption. For me it was good to counter-check whether the stuff I develop myself is secure.