| pronouns | he/him |
| languages | [ 🇩🇪q=1, 🇺🇸q=1, 🇯🇵q=0.75, 🇮🇩q=0.5 ] |
| languages | Java, Groovy, Kotlin, Clojure |
| website | https://georg.berky.dev |
| pronouns | he/him |
| languages | [ 🇩🇪q=1, 🇺🇸q=1, 🇯🇵q=0.75, 🇮🇩q=0.5 ] |
| languages | Java, Groovy, Kotlin, Clojure |
| website | https://georg.berky.dev |
Seems like I had the right hunch. Here's the long version from the real master:
My friend is writing her thesis in data science and is looking for engineers to participate in her survey about data quality in ETL pipelines.
If you have data wizards in your extended circle or are one yourself, here's her survey:
https://uc2456.customervoice360.com/uc/hybrid_data_quality_monitoring_in_etl_pipelines/
“What’s it like having a view of the ocean every day?”
“Well. Often when the wind hits like 50mph or so it knocks down my Camellia plant and that is pretty annoying. But the white caps are pretty to watch.”
I really appreciated Hillel Wayne's article on hazard controls and "safety engineering": https://www.hillelwayne.com/post/hoc/
The hierarchy is quite clear, and can probably be applied to software development in various areas.
The other day a mechanical engineer introduced me to the Hierarchy of Controls (HoC), an important concept in workplace safety. 1 (source) To protect people from hazards, system designers should seek to use the most effective controls available. This means elimination over substitution, substitution over engineering controls, etc. Can we use the Hierarchy of Controls in software engineering? Software environments are different than physical environments, but maybe there are some ideas worth extracting.
You are not defined by the work you do, and any long "coding streak" someone says you have should be seen as a helpful signpost that you might be struggling to manage your workload or maybe suffering low self-esteem.
You are great, and the number of commits you made has nothing to do with that.