Emre Sevinç

“A good program must be written many times. This is true of the programs we show. The first draft may not clearly separate out the concerns, but by making that draft the programmer learns the structure of the problem. We will show two different implementations, which will reveal the evolution of the program as we identify shortcomings in our draft.”
― Chris Hanson, Software Design for Flexibility: How to Avoid Programming Yourself into a Corner

“Note that in the above construction we made a number of choices; here we must beware. Choosing a good categorification – like designing a good algebraic structure such as that of preorders or quantales – is part of the art of mathematics. There is no prescribed way to categorify, and the success of a chosen categorification is rather empirical: its richer structure should allow us more insights into the subject we want to model.”
― Brendan Fong, Seven Sketches in Compositionality: An Invitation to Applied Category Theory

“So the syntax of the regular-expression language is awful; there are various incompatible forms of the language; and the quotation conventions are baroquen [sic]. While regular expression languages are domain-specific languages, they are bad ones. Part of the value of examining regular expressions is to experience how bad things can be.”
― Chris Hanson, Software Design for Flexibility: How to Avoid Programming Yourself into a Corner

“For advanced analytics, a well-designed data pipeline is a prerequisite, so a large part of your focus should be on automation. This is also the most difficult work. To be successful, you need to stitch everything together.”
― Piethein Strengholt, Data Management at Scale: Best Practices for Enterprise Architecture