Category: bookmarks

Posted on

Mitmachen. Bürgerprojekt zur Ermittlung von Luftschadstoffen.

“Das Citizen Science Projekt SMARAGD (Sensoren zur Messung von Aerosolen und reaktiven Gasen und Analyse ihrer Auswirkung auf die Gesundheit) ist ein Gemeinschaftsprojekt des Forschungszentrum Jülich (FZJ), des Helmholtz-Zentrum für Infektionsforschung (HZI) und des Helmholtz Zentrum München (HMGU), welches gemeinsam mit den Bürgerwissenschaftsgruppen des OK Lab Köln und der Cologne School of AI geplant und durchgeführt wird. Dabei sollen Daten zu Luftschadstoffen im Großraum Köln mit Gesundheitsdaten in Zusammenhang gesetzt werden

Kontaktieren Sie uns per Mail über smaragd@helmholtz-hzi.de, um von unserem Studienteam weitere Informationen zu erhalten und sich für das Projekt registrieren zu lassen.”

Fast alle Kölner können sich um eine Teilnahme bewerben. Man benötigt einen Platz um die Messtation draußen anzubringen und ein funktionierendes WLAN,  um Daten übermitteln zu können.

https://www.fz-juelich.de/iek/iek-8/DE/UeberUns/Projekte/SMARAGD/SMARAGD_node.html

Posted on

Facebook. Have I been pwned?

“In April 2021, a large data set of over 500 million Facebook users was made freely available for download. Encompassing approximately 20% of Facebook’s subscribers, the data was allegedly obtained by exploiting a vulnerability Facebook advises they rectified in August 2019. The primary value of the data is the association of phone numbers to identities; whilst each record included phone, only 2.5 million contained an email address. Most records contained names and genders with many also including dates of birth, location, relationship status and employer.”

https://haveibeenpwned.com/PwnedWebsites#Facebook

Posted on

Maximizing Developer Effectiveness

After commitment, measurement and empowerment comes scaling.

https://martinfowler.com/articles/developer-effectiveness.html

Working environment

“When we look into these scenarios, a primary reason for the problems is that the engineering organization has neglected to provide developers with an effective working environment. While transforming, they have introduced too many new processes, too many new tools and new technologies, which has led to increased complexity and added friction in their everyday tasks.”

Micro Feedback Loops

“I recommend focusing on optimizing these loops, making them fast and simple. Measure the length of the feedback loop, the constraints, and the resulting outcome. When new tools and techniques are introduced, these metrics can clearly show the degree to which developer effectiveness is improved or at least isn’t worse.”

“The key loops I have identified are:

”

“It is hard to explain to management why we have to focus on such small problems. Why do we have to invest time to optimize a compile stage with a two minute runtime to instead take only 15 seconds? This might be a lot of work, perhaps requiring a system to be decoupled into independent components. It is much easier to understand optimizing something that is taking two days as something worth taking on.”

Posted on

Refinement as Consideration in Code Reviews

“When people think of code reviews, they usually think in terms of an explicit step in a development team’s workflow. These days the Pre-Integration Review, carried out on a Pull Request is the most common mechanism for a code review, to the point that many people witlessly consider that not using pull requests removes all opportunities for doing code review. Such a narrow view of code reviews doesn’t just ignore a host of explicit mechanisms for review, it more importantly neglects probably the most powerful code review technique – that of perpetual refinement done by the entire team.”

https://martinfowler.com/bliki/RefinementCodeReview.html

https://martinfowler.com/bliki/PullRequest.html