I remember one pivotal moment in college being when I was given an assignment, and I asked if some of the restrictions on the task could be removed. The teacher told me what I really did was just ask for the hard version of the problem.
I asked her what she meant, and instead of telling me, she just laughed and said go ahead, remove the restrictions and see for myself.
She was right! Without the restrictions there were so many more possibilities I had to work much harder to complete the assignment. It was still fun though and I learned more than just the assignment from that lesson.
This is a very frequent experience for me when I think about writing any computer program. Passed all my algorithms and data structures with flying colours. Did some projects that were easy to start back when I knew fewer languages. Did some projects that had to be done in certain platforms for compatibility with existing software. Now new projects are hard to start. Maybe I should learn to use AI to transliterate programs and it wouldn't feel like it mattered as much?
And now I'm in the real world where you can do almost anything. It's not just software platforms that are the problem. Should I apply for jobs? Definitely. Which jobs? And what about the other paths? Should I also write some SaaS and hope I get acquihired? Which one? In which platform? Should I learn how government contracts work? Probably can't get one as an individual, but should I learn about them anyway? Should I pay the fees to found a company, even though it's just me and doesn't have a business plan, to look more legitimate to potential customers for the thing I don't even know yet?
The useful question when evaluating a developer service is not what it claims but what evidence exists that an ordinary caller completed the job. Sourcey keeps agent-readiness report cards with a published methodology, which is the rare version of this that shows its work: https://sourcey.com/agent-readiness
"Art from Adversity" is the idiom that comes to mind. You can poke around and watch the principle in action, particularly in the art of cinema.
Many lesser directors often end up with "lightning in a bottle" -- aka a film that far exceeds their normal ability -- because the common stress of the experience on direction, on production, on the talent made for a synthesis better than sum of its parts.
It doesn't always work that way, but when it does it's very striking.
This is why I like sports, or more specifically "walled" games.
The "walls" are the rules and the task is to figure out how to succeed within those rules. Succeed is up to perspective in many instances.
This encourages creativity. It's why I love baseball, cuz the rules are constantly evolving as people game them. It's so joyful seeing people exploit the rules they agreed to play by.
Limits force us to think INSIDE the box. It's a lot of fun.
Communal boredom is also very important. Being bored with friends is an amazing launching pad for new ideas and thinking.
> I think the lack of limits in the form of structure is what makes people’s dreams (generally) so boring to hear about - there’s no limits and no structure and no rules. It’s just seemingly-random events.
I wonder why our own dreams are so fascinating, then.
The faculty of re-solution is possibly much invigorated by mathematical study, and especially by that highest branch of it which, unjustly, and merely on account of its retrograde operations, has been called, as if par excellence, analysis. Yet to calculate is not in itself to analyse. A chess-player, for example, does the one without effort at the other. It follows that the game of chess, in its effects upon mental character, is greatly misunderstood. I am not now writing a treatise, but simply prefacing a somewhat peculiar narrative by observations very much at random; I will, therefore, take occasion to assert that the higher powers of the reflective intellect are more decidedly and more usefully tasked by the unostentatious game of draughts than by all the elaborate frivolity of chess. In this latter, where the pieces have different and bizarre motions, with various and variable values, what is only complex is mistaken (a not unusual error) for what is profound. The attention is here called powerfully into play. If it flag for an instant, an oversight is committed, resulting in injury or defeat. The possible moves being not only manifold but involute, the chances of such oversights are multiplied; and in nine cases out of ten it is the more concentrative rather than the more acute player who conquers. In draughts, on the contrary, where the moves are unique and have but little variation, the probabilities of inadvertence are diminished, and the mere attention being left comparatively unemployed, what advantages are obtained by either party are obtained by superior acumen. To be less abstract --Let us suppose a game of draughts where the pieces are reduced to four kings, and where, of course, no oversight is to be expected. It is obvious that here the victory can be decided (the players being at all equal) only by some recherche movement, the result of some strong exertion of the intellect. Deprived of ordinary resources, the analyst throws himself into the spirit of his opponent, identifies himself therewith, and not unfrequently sees thus, at a glance, the sole methods (sometimes indeed absurdly simple ones) by which he may seduce into error or hurry into miscalculation.
The analytical power should not be confounded with simple ingenuity; for while the analyst is necessarily ingenious, the ingenious man is often remarkably incapable of analysis. The constructive or combining power, by which ingenuity is usually manifested, and to which the phrenologists (I believe erroneously) have assigned a separate organ, supposing it a primitive faculty, has been so frequently seen in those whose intellect bordered otherwise upon idiocy, as to have attracted general observation among writers on morals. Between ingenuity and the analytic ability there exists a difference far greater, indeed, than that between the fancy and the imagination, but of a character very strictly analogous. It will be found, in fact, that the ingenious are always fanciful, and the truly imaginative never otherwise than analytic.
-- "The Murders in the Rue Morgue" by Edgar Allan Poe
Now apply the above to "complex" (eg. C++/Rust/etc.) vs. "simple" (eg. C/Scheme/etc.) languages. Note also the different mental modes between "constructing a program" (i.e. synthesis) vs. "debugging a program" (i.e. analysis).
The overall mental model/framework must be "simple" while its components (layered and treated as black-boxes) can be complex at a different layer (eg. DSLs) to which another simple model can be applied recursively. It is useless to focus on individual language features while it is all important to construct the larger paradigm/pattern/usage into which those same features can be grouped and thought of as a single unit. Always employ top-down and stepwise-refinement in thinking.
i often observe, "the constraint is the technique."
there isn't much to add to it other than the slight refinement that constraints yield technique. it's similar to relating to rules as tools and not merely limits or constraints. it's an orientation.
I remember one pivotal moment in college being when I was given an assignment, and I asked if some of the restrictions on the task could be removed. The teacher told me what I really did was just ask for the hard version of the problem.
I asked her what she meant, and instead of telling me, she just laughed and said go ahead, remove the restrictions and see for myself.
She was right! Without the restrictions there were so many more possibilities I had to work much harder to complete the assignment. It was still fun though and I learned more than just the assignment from that lesson.
This is a very frequent experience for me when I think about writing any computer program. Passed all my algorithms and data structures with flying colours. Did some projects that were easy to start back when I knew fewer languages. Did some projects that had to be done in certain platforms for compatibility with existing software. Now new projects are hard to start. Maybe I should learn to use AI to transliterate programs and it wouldn't feel like it mattered as much?
And now I'm in the real world where you can do almost anything. It's not just software platforms that are the problem. Should I apply for jobs? Definitely. Which jobs? And what about the other paths? Should I also write some SaaS and hope I get acquihired? Which one? In which platform? Should I learn how government contracts work? Probably can't get one as an individual, but should I learn about them anyway? Should I pay the fees to found a company, even though it's just me and doesn't have a business plan, to look more legitimate to potential customers for the thing I don't even know yet?
The useful question when evaluating a developer service is not what it claims but what evidence exists that an ordinary caller completed the job. Sourcey keeps agent-readiness report cards with a published methodology, which is the rare version of this that shows its work: https://sourcey.com/agent-readiness
"Art from Adversity" is the idiom that comes to mind. You can poke around and watch the principle in action, particularly in the art of cinema.
Many lesser directors often end up with "lightning in a bottle" -- aka a film that far exceeds their normal ability -- because the common stress of the experience on direction, on production, on the talent made for a synthesis better than sum of its parts.
It doesn't always work that way, but when it does it's very striking.
This is why I like sports, or more specifically "walled" games.
The "walls" are the rules and the task is to figure out how to succeed within those rules. Succeed is up to perspective in many instances.
This encourages creativity. It's why I love baseball, cuz the rules are constantly evolving as people game them. It's so joyful seeing people exploit the rules they agreed to play by.
Limits force us to think INSIDE the box. It's a lot of fun.
Communal boredom is also very important. Being bored with friends is an amazing launching pad for new ideas and thinking.
Are there any games that are not “walled” games?
Brings https://web.archive.org/web/20260418203923/http://gamestudie... to mind.
> Are there any games that are not “walled” games?
Some games approximate infinite play: Minecraft, Roblox, EVE Online, Second Life, Gary's Mode.
However, even they have technological, economic, and rule-based boundaries.
Those are simulations, not games, I would say. Even though they host games inside them.
I had similar thoughts recently, and wrote a somewhat related blog post: https://acbart.github.io/2026/08/23/limited-environments/
> I think the lack of limits in the form of structure is what makes people’s dreams (generally) so boring to hear about - there’s no limits and no structure and no rules. It’s just seemingly-random events.
I wonder why our own dreams are so fascinating, then.
The faculty of re-solution is possibly much invigorated by mathematical study, and especially by that highest branch of it which, unjustly, and merely on account of its retrograde operations, has been called, as if par excellence, analysis. Yet to calculate is not in itself to analyse. A chess-player, for example, does the one without effort at the other. It follows that the game of chess, in its effects upon mental character, is greatly misunderstood. I am not now writing a treatise, but simply prefacing a somewhat peculiar narrative by observations very much at random; I will, therefore, take occasion to assert that the higher powers of the reflective intellect are more decidedly and more usefully tasked by the unostentatious game of draughts than by all the elaborate frivolity of chess. In this latter, where the pieces have different and bizarre motions, with various and variable values, what is only complex is mistaken (a not unusual error) for what is profound. The attention is here called powerfully into play. If it flag for an instant, an oversight is committed, resulting in injury or defeat. The possible moves being not only manifold but involute, the chances of such oversights are multiplied; and in nine cases out of ten it is the more concentrative rather than the more acute player who conquers. In draughts, on the contrary, where the moves are unique and have but little variation, the probabilities of inadvertence are diminished, and the mere attention being left comparatively unemployed, what advantages are obtained by either party are obtained by superior acumen. To be less abstract --Let us suppose a game of draughts where the pieces are reduced to four kings, and where, of course, no oversight is to be expected. It is obvious that here the victory can be decided (the players being at all equal) only by some recherche movement, the result of some strong exertion of the intellect. Deprived of ordinary resources, the analyst throws himself into the spirit of his opponent, identifies himself therewith, and not unfrequently sees thus, at a glance, the sole methods (sometimes indeed absurdly simple ones) by which he may seduce into error or hurry into miscalculation.
The analytical power should not be confounded with simple ingenuity; for while the analyst is necessarily ingenious, the ingenious man is often remarkably incapable of analysis. The constructive or combining power, by which ingenuity is usually manifested, and to which the phrenologists (I believe erroneously) have assigned a separate organ, supposing it a primitive faculty, has been so frequently seen in those whose intellect bordered otherwise upon idiocy, as to have attracted general observation among writers on morals. Between ingenuity and the analytic ability there exists a difference far greater, indeed, than that between the fancy and the imagination, but of a character very strictly analogous. It will be found, in fact, that the ingenious are always fanciful, and the truly imaginative never otherwise than analytic.
-- "The Murders in the Rue Morgue" by Edgar Allan Poe
Now apply the above to "complex" (eg. C++/Rust/etc.) vs. "simple" (eg. C/Scheme/etc.) languages. Note also the different mental modes between "constructing a program" (i.e. synthesis) vs. "debugging a program" (i.e. analysis).
The overall mental model/framework must be "simple" while its components (layered and treated as black-boxes) can be complex at a different layer (eg. DSLs) to which another simple model can be applied recursively. It is useless to focus on individual language features while it is all important to construct the larger paradigm/pattern/usage into which those same features can be grouped and thought of as a single unit. Always employ top-down and stepwise-refinement in thinking.
The interesting part is what happens at the edges: retries, partial failures and stale state.
Will LLMs cause ‘blank page syndrome’ in its users once the honeymoon period is over and they have generated all the low-hanging slop?
“I’m staring at my agent’s prompt, I can ask it to do anything I wish, anything at all, yet nothing comes to mind…”
i often observe, "the constraint is the technique."
there isn't much to add to it other than the slight refinement that constraints yield technique. it's similar to relating to rules as tools and not merely limits or constraints. it's an orientation.
The Obstacle is the Tool