Gunnar_Zarncke

is

Wiki Contributions

Comments

Where do your eyes go?

Forwarded to my computer game playing sons. I wonder what your recommendation for Minecraft would be. 

Book review: The Checklist Manifesto

Our code review checklist looks like this:

  • Have GDPR annotations been added for all fields? (all fields that are stored persistently count)
  • Do interactions with the user happen that should be recorded as events?
  • Is data collected for later use (logging doesn’t count, anything in a database does)? Are there reports or some other way to find this data? 
  • Are there no unencrypted credentials in any files?
  • Are there notable changes that should be recorded in an ADR

(I replaced the links with public alternatives) 

Truth + Reason = The True Religion?

This is pretty impressive for 1722 and better in some regards than what I read from Kant. 

Thanks for writing it up.

Book review: The Checklist Manifesto

Bugs are common in software development [citation needed].

I decided to introduce checklists in the development process of our team. This page in our wiki explains the reason:

Checklists are an essential component of high-quality processes, e.g. in aviation, medicine or construction. But checklists can also be a major obstacle. We want to build high quality software without losing a fast and flexible process. How does that work? We use checklists in a targeted manner and consider when and how checklists make sense.

A very good explanation of what is important can be found here (refers to the very readable Checklist Manifesto).

  • Step 1: Identify “Stupid Mistakes” That Cause Failure → see Known Traps and Post Mortems.
  • Step 2: Seek Additional Input From Others → for example in retro's
  • Step 3: Create Simple “Do” oder "Test" Steps → in a checklist, which should become part of the process
  • Step 4: Create Simple “Talk” Steps → which can take place after the Daily Standup or as part of the Code Review
  • Step 5: Test The Checklist
  • Step 6: Refine the Checklist → nothing is perfect; review the success in a retrospective or when things are not going well

Important: The checklist must only contain the most important sources of error. Completeness is not the goal, but to ward off the greatest risks without slowing down the process. 

We use checklists at three different points of the development process:

  1. A Ready Checklist is used to ensure key business and architecture aspects are considered, and the ticket can be picked up by a developer without (much) further back and forth.
  2. A Code Review Checklist covers business-critical classes of error and things hard to fix later (e.g. database changes). It leaves general adherence to engineering standards to the reviewer's discretion (we use MoSCoW there).
  3. The Approval Checklist is used by testers and subject matter experts to ensure the feature is fit for use (e.g. works on mobile).

I can confirm that people sometimes roll their eyes, but consistently using the checklists leads to much better quality.

Book review: The Checklist Manifesto

The book is great. 

Here is a link to the Surgical Safety Checklist used in hospitals.

After checking whether German hospitals use checklists with unclear results, I decided to print one out and have it available just in case:

Not sure whether doctors will like it when I come up with them in a hospital but so far, that was not needed, luckily.

Writing On The Pareto Frontier

The same thing is called Talent Stacking by Scott Adams. Your explanation is higher on the theoretical dimension vs. the usual Talent Stack explanations you see e.g. on YouTube are higher on the relatable/engagement dimension.

Comments on Jacob Falkovich on loneliness

Thank you for adding so much value to the challenge of loneliness. 

TL;DR: Go out into the wild not only for relationships but for friendship and community. 

History of counting to three?

I have used this in the form of counting down from 3. I use it only with consequences and only for things that are important for me but don't warrant immediate action. I just let the kid know that I disapprove of something. 

Research shows that these kinds of punishments are not effective - except in reinforcing the behavior in the parent!

https://www.lesswrong.com/posts/Sw22Fr6kv42kmLpHx/book-review-kazdin-s-the-everyday-parenting-toolkit 

DanielFilan's Shortform Feed

Related: As I wrote just recently:

The feeling of something being obvious or easy [...] doesn't mean that [it] is obvious or easy to everybody. It just means that you have understood it. When you deeply understand something it becomes obvious and easy over time.

https://www.facebook.com/Xuenay/posts/10161257148333662?comment_id=10161257444543662 

The feeling of something being obvious or easy in the above sense can be mistaken sometimes. It is an intuition or heuristic our brain applies I guess to figure out which things we are supposed to know in a tribe. It can be put on more solid footing by spelling out things and being forced to make intuitions explicit. 

GPT-Augmented Blogging

How long did you take writing this? And how does that compare to other posts?

Load More