{"version":"https:\/\/jsonfeed.org\/version\/1","title":"JSON Feed for Anselm Hannemann\u2019s Writings","description":"Feed for Anselm Hannemann\u2019s blog articles, notes and other shared writings.","home_page_url":"https:\/\/helloanselm.com","feed_url":"https:\/\/helloanselm.com\/feed\/","items":[{"id":"https:\/\/helloanselm.com\/writings\/engineering-managers-scrum-masters-teams","url":"https:\/\/helloanselm.com\/writings\/engineering-managers-scrum-masters-teams","title":"Engineering Managers, Scrum Masters & Teams","content_html":"
As humans we think in silos. Scrum Masters often don\u2019t know what an Engineering Manager is, Engineering Managers don\u2019t care about Scrum Masters. But both have their own focus, their very own strengths to create a resilient team. See how important it is to stay open minded enough to see the benefits of other roles, no matter the job title.<\/p>\n
The concepts of a Scrum Master and an Engineering Manager are not equal. The Scrum Master exists to ensure that a team can work effective. The goal is to have effectiveness in a project. Strictly seen, this means that team\/individual happiness is a side-effect but not a primary goal. <\/p>\n
An Engineering Manager exists to give engineers a voice, to translate between Management and engineers, to keep a team healthy. The goal is to create a resilient team. Team and individual comfort is a key principle and goal while effectiveness is a side-effect.<\/p>\n
Therefore, the two roles are not conflicting, they add to each other. If you don\u2019t have both in your project\/team, why not try to enhance your Scrum Master role with Engineering Management skills or vice versa?<\/p>\n
\n\u00bb1:1s\u00ab can be the missing link to understand blockages in a process or in how teams work. Don\u2019t forget about the individuals in a team.<\/p>\n<\/blockquote>\n
As a Scrum Master, \u00bb1:1s\u00ab (also known as \u00bb121-meetings\u00ab) can be the missing link to understand blockages in a process or in how teams work. Don\u2019t forget individuals.<\/p>\n
As Engineering Managers we know how to do honest and psychologically safe 1:1s. But we shouldn\u2019t forget the team (e.g. by doing team retrospectives) and the Managers (Product Owners, Hiring Managers, \u2026).<\/p>\n
This is all about humans, a team\u2019s individual people. If we understand their work, their challenges (e.g. work-life\/family balance) and their motivation, a team will become successful and resilient.<\/strong><\/p>","date_published":"2023-04-04T00:00:00+02:00","date_modified":"2023-04-04T20:56:59+02:00"},{"id":"https:\/\/helloanselm.com\/writings\/i-have-two-jobs-and-all-the-social-algorithms-fail","url":"https:\/\/helloanselm.com\/writings\/i-have-two-jobs-and-all-the-social-algorithms-fail","title":"I have two jobs, and all the social algorithms fail","content_html":"
The fun part of being someone with two jobs in completely different areas. Nearly all of the algorithms of these fancy platforms backed with billions of money don\u2019t work.<\/p>\n
LinkedIn for example is smart enough to realize both of my work categories (web development, agriculture\/gardening) but fails to provide a proper feed, a mixture of network recommendations, etc.<\/p>\n
The world cannot be put in one category.<\/strong> There are many, and building systems for this isn\u2019t such an easy task. Think outside the box.<\/p>\n
#algorithms #socialnetworks<\/p>","date_published":"2023-01-24T00:00:00+01:00","date_modified":"2023-01-24T07:19:04+01:00"},{"id":"https:\/\/helloanselm.com\/writings\/til-css-empty-isn-t-applicable-on-form-fields","url":"https:\/\/helloanselm.com\/writings\/til-css-empty-isn-t-applicable-on-form-fields","title":"[TIL] CSS :empty isn\u2019t applicable on form fields","content_html":"
Today I learned<\/strong> that the CSS
:empty<\/code> selector is implemented to look for child content (think of
innerText<\/code>\/
innerHTML<\/code>).
\nThis means it reports empty for filled form elements<\/em> which are self-closing elements.<\/p>\nFindings<\/h3>\n
\n
:empty<\/code> reports empty for all form input elements because they have their values as attributes, not as inner content<\/li>\n
:empty<\/code> works for
<textarea><\/code> elements depending on how they\u2019re used in HTML<\/li>\n
:blank<\/code> is what we\u2019d like to have but it\u2019s not widely supported in browsers<\/li>\n
:placeholder-shown<\/code> as a workaround works for when there\u2019s a placeholder attribute specified with a value (empty value doesn\u2019t work)<\/li>\n
:empty<\/code> reports empty for
<div><\/code>-elements that have a pseudo-element specified via
::after|::before { content: ''; }<\/code> \ud83e\uddd0<\/li>\n<\/ul>\n
I\u2019ve created a Codepen with various tests that show the possibilities:<\/p>\n
\n See the Pen CSS :empty pseudo-selector does not work well for form fields<\/a> by Anselm Hannemann (@anselmh<\/a>)\n on CodePen<\/a>.<\/span>\n<\/p>\n