SleepyDogUniverse

When i was a little kid, i had a "4d puzzle" of new york city.

You built the cardboard jigsaw base, then the foam island, and then you had plastic buildings and bridges.

And it had instructions to place the buildings in chronological order, as well as a timeline, hence "4d".

And i just fucking remembered. In 2001 on the timeline a step was "remove buildings #xx and #xy (World Trade Centers)" with no other explanation.

This is because as a beginner, you have troubles because you don't have much knowledge.

But then you learn a bunch more, and now you've got the skills to do a bunch of stuff, so you run into a lot of problems because you're doing so much stuff, and only an expert could figure them out.

But then one day you are an expert. You can reprogram everything and build new hardware! You understand all the various layers of tech!

And your problems are now legendary. You are trying things no one else has ever tried. You Google them and get zero results, or at best one forum post from 1997. You discover bugs in the silicon of obscure processors. You crash your compiler. Your software gets cited in academic papers because you accidently discovered a new mathematical proof while trying to remote control a vibrator. You can't use the wifi on your main laptop because you wrote your own uefi implementation and Intel has a bug in their firmware that they haven't fixed yet, no matter how much you email them. You post on mastodon about your technical issue and the most common replies are names of psychiatric medications. You have written your own OS but there arent many programs for it because no one else understands how they have to write apps as a small federation of coroutine-based microservices. You ask for help and get Pagliacci'd, constantly.