1.1 KiB
| key | title | id | language | format | tags | level | speakers | videoId | presentation | draft |
|---|---|---|---|---|---|---|---|---|---|---|
| four_diseases | Four Diseases | PmoMEVHO3imfUIMXsPai | English | conference | [_wtf] | beginner | [piotr_przybyl] | <nil> | <nil> | false |
How a developer can tell if the system is sick just by taking a look at the input and the output? If you'd like to know that (plus you like standup comedy), come an see! The treatment is safe ;-)
One approach to get familiar with a system is a long and intense reading the manual (and to run an eye over the source code sometimes). Another approach is to take a deep dive into the data model (often in the DB) and to surf the user interface. Both are natural ends of the system, the legendary Input and Output. By examining these ends one can check if there's good digestion or if guts are rotten. Careful examination can confirm "common DDDosis", "malignant stringosis", "regex diarrhoea" or "not-made-here syndrome". Unfortunately, sometimes developers get infected in their prenatal life (meaning: at their university). Let me invite you to treatment. A laxative one. (That is: a sequel of "Passwords. Do you keep them safe?")