There's another great meta-game similar to this. You can play it alone or with friends. It doesn't require any cards or dices, although can be played with them too.
The rules are simple. You join some group, that is playing a game, rules of which you don't know. Yet, you say to everyone, that you know the rules.
Now, your goal is to play as long as possible, before they figure out, that you actually don't know the rules.
Bonus points, if you convince others that it's THEY, who don't know the rules.
> Most Haskell tutorials on the web seem to take a language-reference-manual
approach to teaching. They show you the syntax of the language, a few language
constructs, and then have you construct a few simple functions at the interactive
prompt. The “hard stuff” of how to write a functioning, useful program is left
to the end, or sometimes omitted entirely.
I feel like this is such an issue with lots of languages. Learning your second, third, and so on language is in some sense harder, because “Getting started” tutorials spend too much time on simple concepts, and the hard part of “How do I write X (or what do I do instead)” is usually missing.
It recently occurred to me, that you can find exercises for almost any popular language, and I feel like it is the solution to the problem.
> This tutorial takes a different tack. You’ll start off with command-line arguments and parsing, and progress to writing a fully-functional Scheme interpreter
that implements a good-sized subset of R5RS Scheme. Along the way, you’ll
learn Haskell’s I/O, mutable state, dynamic typing, error handling, and parsing
features. By the time you finish, you should be fairly fluent in both Haskell and
Scheme.
There's not enough tutorials like that in the world
I know nothing about Git development, but it surprised me that most of the changes are kind of internal and affect the end user only on security or performance level.
For some reason, I was thinking there would be more new shiny features. But maybe for the tool that is as mature and wide-used as Git, that's not how it works.
> Some time ago (1999-ish) [...] a number of ways to integrate ads were discussed.
> One was to show a cool video from a respected company (such as Nike) every time the Mac starts up. [...]
This sounds so weird in 2025. However, I can see that probably in those times there was no "norm", and people were trying different things.
Who knows, maybe if it weren't for Steve Jobs, ads at startup might be the norm. And who knows how many similar things we dodged because of people like Jobs.
Kindles have been showing ads on their lock screen for the ad-supported tier for a very long time now.
These days, we have moved to far more insane schemes. E.g. smart TV manufacturers are patenting detection of static frames to show you ads while TV is idle (although I don't think anyone has actually shipped that yet).
Although the article is completely on point, I disagree that theme should be stored in URL.
Imagine you’re browsing a site, and at some point you switch from light to dark theme. After some time, you press “Back”. Do you really expect to switch back to light theme, and not to go to the previous page?
I've seen a lot of “well‑behaved” sites, that are storing their state in the URL, but I've never seen one, that stores current theme.
It’s interesting that the theme is part of the state too, yet you don’t want to store it in the URL. So, this means not every part of the state should be stored in the URL? Then what's the criteria for choosing what to store, and what not to?
The rules are simple. You join some group, that is playing a game, rules of which you don't know. Yet, you say to everyone, that you know the rules.
Now, your goal is to play as long as possible, before they figure out, that you actually don't know the rules.
Bonus points, if you convince others that it's THEY, who don't know the rules.
reply