4,763 karma · joined October 1, 2009
Yes, agreed but what is the point? What problem are we solving?
This extra coordination “friction” is the killer. The lesson is, if you want more dinner parties you have to reduce the extra coordination “friction” to a minimum.
More details in the CHANGELOG: https://github.com/beanshell/beanshell/blob/main/CHANGES.md
- license number
- license class
- license issue date
- license expiration date (birth day and month in my state)
- birth date
- eye color
- sex
- height
Are any of these very difficult to find?> I get unreasonably upset when people nitpick holes in good analogies…
What you’re describing is exactly why I strongly recommend avoiding analogy when communicating: Don’t tell me what a thing is like, tell me what the thing is. This forces really thinking about how to describe the thing precisely and succinctly. (Edit: The listener will make their own analogy.)
There are millions of Single Page, and other “complex” web apps. You not liking it does not invalidate anything.
Isn’t that what’s actually happening though? Traders are making real money from bad predictions?
“These are the Sharps actually making money on prediction markets” Odd Lots podcast (Bloomberg) 2026 https://youtu.be/MFAnQpdgkZE
If the dev is pushing code to production they should not simultaneously be pushing environment configs, this is doing two logically distinct things at once: Changing application behavior AND reconfiguring the server environment.
If the dev is adding secrets to their local config and they’re pushing that config to insecure places that means their deployment pipeline is broken and it should be fixed. .env is never committed to source for this reason, for example.
> From the outside, this looks like competence. But if you don't understand why the solution works, you're not actually becoming more capable. You're becoming dependent on the machine to maintain the illusion.
So many things in life operate exactly like this: We don’t need to understand the why, we just accept the solution as-is and move on. An experienced professional has another skill: keeping track of which things matter enough to dig in to and develop mastery, and which things can be “good enough”. This is also informed by the “intuition of how machines behave” that the author mentions.
“What’s at stake in the Canada-U.S. trade deal? How looming tariffs could cost Canada 90,000 jobs”. Trevor Tombe, professor of economics at the University of Calgary
https://thehub.ca/2026/08/20/whats-at-stake-in-the-canada-u-...
The article shows that the market value of the intern is lower: Work was not prioritized and given to a higher-cost junior engineer.
> … pre-AI that feature would not have been given to an intern (because they wouldn't be able to own it)…
Meaning, a more-skilled, higher-cost employee would have to do some or all of the work.
Edit: Another meaning of “worth” is a “intrinsic value”. Humans have worth in this sense.
So, interns can still produce some value. How much value?
> In our product, there was a feature which had been requested for years, but had not been built yet. It wasn’t overly complex, but it was not critical.
Said another way: The feature was of so little value that it was not even worth assigning to a non-AI-assisted intern! This is what most of us mean when we say “AI lowers the value of…”
https://www.cps.edu/media/community-updates/2025/january/neg...