Structuring Old Python Code By Ines Panker As developers we like to think of ourselves as highly mathematical beings, highly precise and logical. but the human brain isn't really as logical as it has been painted out to be. the brain. Cognitive biases in code … or why smart developers write silly bugs | bright yellow.
Exhibit A Because Writing A Fresh Query Is Too Much Work Collection From spaghetti code to quality software 🍝 it’s one of the challenges many of us engineers face. how do we move from messy, silly code to systems that actually work in production?. It explains the pattern of “smart but brittle” code better than “llms are dumb.” it connects to a more general point: llms will tend to see everything as agents and stories unless we explicitly tell them, “this part is math.”. Smart engineers don’t wake up wanting to write bad code. bad code is written at 11:47 pm, five minutes before a deadline, while slack notifications keep firing and production is already. Discover why smart developers accept bad code suggestions. explore the cognitive biases, power dynamics, and social psychology.
Why Do Smart Devs Write Silly Code Exhibit B I Just Need To Confirm Smart engineers don’t wake up wanting to write bad code. bad code is written at 11:47 pm, five minutes before a deadline, while slack notifications keep firing and production is already. Discover why smart developers accept bad code suggestions. explore the cognitive biases, power dynamics, and social psychology. Vibe coding—the shorthand for this new ai driven style of software creation rewards intuition and speed. yet, it risks burying the discipline’s oldest truth: verification is not optional. But maybe the goal of eliminating bias was always silly. what we can do is we can multiply our estimates, we can sleep on our “finished” code, and we can ask others to poke holes in our plan. In an experiment, they asked participants to write sql queries. some participants were given a sample query (the “anchor”) to “help” them with the task of writing a new query, while others weren’t given anything. all in all 157 participants took part in the experiment. Hi, my name is ines panker. i'm a python consultant focused on complex systems. observations about the human at work, building software. notes from my years of building software. why do smart devs write silly code? the previous chapters covered anchoring bias and confirmation bias.
Comments are closed.