However 'normal people' buying into the stock market via 401ks or otherwise likely (and arguably sensibly) will be in index funds, that of course are exposed to the bubble via (grossly?) inflated tech stocks. Effectively their current pension/savings contributions are being clipped by whatever the delta is between now and post bubble. Time in the market and all that, but still it might be a hefty haircut.
1. Understand that code that has been wholly or partly LLM generated is tainted - it has (in at least some part) been created neither by humans nor by a deterministic, verifiable, process. Any representations to its quality are therefore void.
2. Ban tainted code.
Consider code that (in the old days) had been copy pasted from elsewhere. Is that any better than LLM generated code? Why yes - to make it work a human had to comb through it, tweaking as necessary, and if they did not then stylistic cues make the copy pasta quite evident. LLMs effectively originate and disguise copy pasta (including mimicking house styles), making it harder/impossible to validate the code without stepping through every single statement. The process can no longer be validated, so the output has to be. Which does not scale.
It depends on the nature of the code and codebase.
There have been many occasions when working in a very verbose enterprise-y codebase where I know exactly what needs to happen, and the LLM just types it out. I carefully review all 100 lines of code and verify that it is very nearly exactly what I would have typed myself.
The first freedom of course is freedom from fear (e.g. from fear of being snatched from the street just because you are brown and speak with an accent)
Wifi never seems to work 'out the box', so be ready to connect to the internet using ethernet to download the latest drivers and thus get wifi to work.
Ah I think what is happening is that a brand new laptop may not have had its drivers added to the latest download/image version of your chosen distro. Hence the need to connect and update to get those drivers.
For me, it was a ThinkPad X1 Gen 11 and Mint 21.2 (MATE) about a year ago.
Interestingly, in the Lambda Calculus, where everything is a function, a standard representation for a natural number n (i.e. a whole number >= 0), is indeed a function that 'iterates' (strictly, folds/recurses) n times.
My understanding is that the 'extra thing' is control flow - blocks can force a return in their calling scope. For example a loop that calls a block may be terminated/skipped by a break/continue statement in the block itself. However I'm not a Ruby programmer, so please check my working.
Blocks can force a return in their defining scope. If you pass a block down through multiple methods and then call it, the return will exit the lexical scope the block was defined in, not the method it was ultimately called from.
It usually looks pretty much the same, and so for most intents what you described is "close enough" to get most used of blocks.
[1] https://en.wikipedia.org/wiki/AI_winter#The_setbacks_of_1974
[2] https://en.wikipedia.org/wiki/AI_winter#AI_winter_of_the_199...