And just as I typed that, Kimi made one where 9 and 10, and 11 and 12 overlapped.

So far, I’d give qwen the prize for most artistic impression of a clock.

Kimi K2 appears to consistently get it right.

Hey I have plenty of floppies still around, and my beard is not grey.

I shave.

And a cloud inside the folder. And a floppy disk inside the cloud.

Did it ever make sense?

Weird, it should be standard C++20. Hope are you invoking gcc?

godbolt link: https://godbolt.org/z/6Tn4Kcjrs

Edit: be sure to call g++, not gcc.

#include <cmath>
#include <iostream>
#include <numbers>

int main()
{
  decltype ( NAN ) f { std::numbers::pi };
  std::cout << f << std::endl;
} 

3 hours ago of course.

Which means you replied to a comment 10 hours before it was posted.

Flexibility training.

The C family tree puts the Godfather to shame.

I have seen and worked on many projects that use inheritance, polymorphism, interfaces, all the staples of OOP. It’s true that none of these use only OOP principles and applies them rigorously. Real world projects are almost? always a mix of many different paradigms, because the truth is no one paradigm matches all use cases - and every programmer is only familiar with a few anyway.

This is one of the ways I believe Java went wrong: the program entry point is naturally a function, not an object. Wrapping main in an object makes little sense. Similarly, having absolutely everything inherit “Object” is forcing OOP where it doesn’t belong.

But that doesn’t mean OOP isn’t used in the real world. It is.

See you just type the o and e really really fast. That way the o doesn’t have the time to get out of the way of the e and they sorta get smooshed together. It takes some practice but you’ll get there.

You should hear how the French pronounce it. Can’t even recognise it as English anymore.

Big butts if true.

I feel like a lot of what he attributes to malice or obfuscation is rather his unfamiliarity with the technical side of things.

Mapping numbers to non-sequential glyphs is exactly what happens in PDF, and PostScript before it. So is text positioning by Cartesian coordinates rather than in reading order.

Ligatures and multiple font variations have been around since fonts existed. Fonts that render incorrectly unless you use them in one specific way are legion (turns out font designers often have very little technical understanding, or just don’t care).

The only thing that sounds like obfuscation to me is changing the font encoding on every call. And if that is indeed its purpose, it’s a very poor attempt.

Unfortunately the murderer was their significant other.

I still have an encyclopaedia on my shelf. I have to admit it’s the small edition though.

I also still have a bunch of dictionaries (different languages), and a very outdated atlas.

Poor bat. They are misunderstood creatures, and very cute.

The things you mentioned are very good, but what I’m missing is feedback and a good foundation.

Feedback should come from other developers - ideally experienced, but a good dialogue between beginners can also teach both sides a lot. For me this came only after I started working, through code reviews. But you could also try contributing to open source, or putting your own code online. Although I fear you won’t get much feedback.

A good foundation is about software and hardware designs. Without this you will inevitably come to a point where you made a fundamental mistake in design.

For hardware design I recommend YouTube. Many channels talk about low level hardware. You don’t need to become an expert, just get a high level understanding.

For software design, check out the gang of four’s Design Patterns. It is a seminal work. You don’t need to read it all but be aware of the patterns, and study a few like factories and facade in detail.

Take a picture and store it in the phone.

Wait…