How Elm slays a UI antipattern: https://blog.jenkster.com/2016/06/how-elm-slays-a-ui-antipattern.html
Argues for GADTs in web dev, and points out a common issue with async UIs that I can't unsee now.
miniblog.
Related Posts
A common UI antipattern is to make the structure directly reflect the implementation.
If you have 4 database tables, you build 4 screens. This may not reflect how users want to get things done.
Does this happen outside of software? I suspect it does, but I can't find examples.
I'm increasingly persuaded that the best kind of architecture diagrams are ASCII text art. It seems to be the only format that others will edit.
I keep seeing an antipattern where someone draws a comprehensive diagram and it keeps getting used even as it becomes less accurate.
Duck programming: https://unspace.ca/dev/2012/duck-programming is a classic antipattern of programmable systems (see also 'inner platform effect')