Following "Digital Minimalism," "Deep Work" was the second book by Cal Newport that I immersed myself into. The former had an overemphasis on "success stories" which seemed disruptive to me, but in "Deep Work," Newport strikes the right balance, in my opinion.
In early 2020, I discovered Cal Newport's book "Digital Minimalism", a discovery inspired in part by Marcel's insightful blog post on the subject.
Konferenzen und Conference Buddy
In dieser Folge spreche ich mit Mirjam Aulbach über Konferenzen und ihr "Ding" Conference Buddy (Website, Mastodon, Twitter). Es geht aber auch um unsere Erfahrungen auf Konferenzen, wie diese zugänglicher gemacht werden können (von Organisatoren und TeilnehmerInnen), wie das alles mit Hundetraining zusammenhängt und mechanische Tastaturen (Mirjams Tastatur ist die Saber 68, Mechanicon).
A few weeks ago, I decided to reactivate my podcast, "Herr Zenzes wills wissen". For the last few years, I hosted it with Podigee, but it became too expensive for my use case. I don't produce enough content to take full advantage of the smallest package, so I can save some money by hosting the podcast myself again.
Christian (Blog, Mastodon) arbeitet als System Engineer bei der SVA. Er ist zudem einer der Hosts von "FOCUS ON: Linux".
In der aktuellen Folge sprechen wir über Configuration Management, Infrastructure as Code und Ansible.
April has started with a few minor updates that I'd like to share here on the blog.
Zenzes zauberhafter IT-Zirkus
Daniel meldet sich mit dem Podcast aus der längeren Pause zurück. Wir starten unter neuem Namen nochmal durch. Damit ihr wisst, was auf Euch zukommt, nutze ich die Folge um den Podcast und mich nochmal vorzustellen und gebe einen kleinen Ausblick auf das, was da kommt.
There are topics in the IT world that divide opinions: what needs to be tested, test-driven development, do we work alone, in pairs or even in a mob? Do we need estimates for tickets?
Today I want to discuss estimates and why I think they are essential in a dev team. I realize many developers see it differently because estimates have an awful reputation. Critics say that they don't bring much to the team, take a lot of time in meetings and at the end "management" gets a statement when which feature is (guaranteed) available. In the sprint, people are then also quick to talk about why a supposedly small task is taking a long time. So, we have something that costs us a lot of time as developers and makes life difficult afterward because someone converts story points into time. And sure, if that's how estimates are lived in team, then I would question them in that form as well. But estimates can also be useful, help the team and help to plan things.
Today I updated an article that is about automatically switching Node.js version with nvm. In the course of this I wanted to delete two old articles and bring them to the current article via an HTTP redirect.
As I host my blog on Netlify, all I need is a _redirects file with the redirects: