Perlisisms (1982)
cs.yale.edu
Perlisisms (1982)
1–10 of 64 posts
Re: Perlisisms (1982)
#2And in #27 we find the rationale behind all LLM coding agents, "Once you understand how a program works, get someone else to write it for you."
Re: Perlisisms (1982)
#3This feels so quaint today. How I'd like to be back in that timeframe.
Re: Perlisisms (1982)
#4Random self plug - I liked a lot of these quotes from Alan Perlis, so around a year ago I bought the domain https://perl.is/ to display them.
Re: Perlisisms (1982)
#5And in #27 we find the rationale behind all LLM coding agents, "Once you understand how a program works, get someone else to write it for you."
I think you misunderstood what the phrase actually means. You can only successfully manage or outsource a process once you understand it well enough to explain it. Therefore, most of the people doing agentic engineering are not following this Perlisim.
Re: Perlisisms (1982)
#6And in #27 we find the rationale behind all LLM coding agents, "Once you understand how a program works, get someone else to write it for you."
Once you understand how a program works, get someone else to write it for you. Then, you will quickly find out your understanding was insufficient.
Re: Perlisisms (1982)
#7Random self plug - I liked a lot of these quotes from Alan Perlis, so around a year ago I bought the domain https://perl.is/ to display them.
Neat! What do you think about adding a "-2, -1, 0, +1, +2" agreement scale to each quote and showing the average instead of votes?
I think many of those are pretty subjective, and maybe not always right for everyone or for all time. But there are certainly going to be some universal pearls of wisdom, and neither of us can - by ourselves - tell which ones they are.
Re: Perlisisms (1982)
#8>1. One man's constant is another man's variable.
Did you ever have one of those days when variables didn't and constants weren't?
Re: Perlisisms (1982)
#9> 2. Functions delay binding; data structures induce binding. Moral: Structure data late in the programming process.
A good way to enforce this is to encrypt the data at the beginning of the process.
Then any function that returns structured data is clearly foolish and can be marked for removal.
Re: Perlisisms (1982)
#10> A programming language is low level when its programs require attention to the irrelevant.
Great definition actually