karolkozub

If this truly is an attempt at censorship, it seems that shadow banning could have been just as effective and harder to detect. Maybe they could even secretly add a generic has_negative_sentiment_towards_an_elon_company modifier to their ranking algorithm and dial the outreach of such tweets way way down, in similar vein to author_is_elon.

I really like the idea of automated code review tools that point out unusual or suspicious solutions and code patterns. Kind of like an advanced linter that looks deeper into the code structure. With emerging AI tools like Github Copilot, it seems like the inevitable future. Programming is very pattern-oriented and even though these kinds of tools might not necessarily be able to point out architectural flaws in a codebase, there might be lots of low-hanging fruits in this area and opportunities to add automated value.

Almost exactly 10 years ago I picked up climbing/bouldering and I cannot recommend it enough. It's a fascinating sport combining elements of pure strength, coordination, technique and problem solving. Every route is unique and it's not uncommon to have vastly different approaches depending on your height, finger strength, flexibility, and many other parameters. Finding a solution that works for you can sometimes be more difficult than the climb itself. It's definitely not as boring and repetitive as weightlifting. I highly encourage everyone to try if they haven't yet.

I think I found one more minor typo – in the Control Flow Graph section I believe "The possible number of calls to c is zero to infinity;" should be "zero to one" instead, as the flow terminates as soon as it reaches "c", so there is no chance for it to be greater than one.

It looks like a machine code snippet. I wonder if we'll develop high level languages and compilers for genetic code in the future.

Typed out version:

> General Note to Myself

> Writing isn't so bad really when you get through the worry. Forget about the worry, just press on. Don't be embarrassed about the bad bits. Don't strain at them. Give yourself time you can come back and do it again in the light of what you discover about the story later on. It's better to have pages and pages of material to work with and sift and maybe find an unexpected shape in that you can then craft and put to good use, rather than one manically reworked paragraph or sentence.

> But writing can be good. You attack it, don't let it attack you. You can get pleasure out of it. You can certainly do very well for yourself with it...!

  The following values were inspected:
  1
  2
  4
  8
  16
  32
  64
  32
  48
  40
  44
  42
  43

The most surprising part for me is that in the integer search 32 is inspected twice. From my brief testing it seems to only happen with infinite ranges. Is that a bug in bsearch or am I missing something?

In my understanding AI is an even broader term and means "any solution that imitates intelligent behavior". E.g. expert systems which are pretty much a bunch of if-then rules are also considered AI.

Wow. That's amazing. That's a 20% increase in revenue for those eligible. I'm guessing they decided the increased value of their products from more smaller developers creating apps for the platform is greater than the lost revenue.

If I understand correctly though, since it's a hard cutoff it creates this gap between 1m and ~1.2m where you're actually worse off by making more money pre-tax.

   999k --[-15%]--> 849k
  1000k --[-30%]--> 700k
  1213k --[-30%]--> 849k