The best software engineers spend a third of their time imagining how code could fail.
No-codeists1 are the opposites of the best software developers. This is a pattern I’ve observed. I’m sure there are exceptions. However, there’s a pervasive bias in the no-code community—a common belief that if something is possible in a no-code tool, it must be good.
No…
Keep reading with a 7-day free trial
Subscribe to Impertinent to keep reading this post and get 7 days of free access to the full post archives.