OSDev.org

This sounds very familiar. Unfortunately, it doesn't work for OS Dev, as the wiki entry on the Duct von Tape archetype makes clear.


Alt Text: All services are microservices if you ignore most of their features.

For the sake of the visually impaired members of the forum, the transcript given in the comic's Explain XKCD entry reads:

Explain XKCD wrote: [White Hat is sitting at a laptop. Cueball is standing behind him.]
White Hat: Man, Docker is being used for everything.
White Hat: I don't know how I feel about it.
Cueball: Story time!
[Cueball is standing by himself.]
Cueball: Once, long ago, I wanted to use an old tablet as a wall display.
[A picture of Cueball's imagined tablet with two applications open side by side. The app on the left is "LiveCam".]
Cueball: I had an app and a calendar webpage that I wanted to show side by side, but the OS didn't have split-screen support.
Cueball: So I decided to build my own app.
[White Hat and Cueball as before, but White Hat has turned to face Cueball.]
Cueball: I downloaded the SDK and the IDE, registered as a developer, and started reading the language's docs.
[A picture of two smartphones glued together side by side, held on a backing board. The same two applications shown earlier are open on different phones.]
Cueball: ...Then I realized it would be way easier to get two smaller phones on eBay and glue them together.
Cueball: On that day, I achieved software enlightenment.
[White Hat and Cueball still facing each other, with White Hat's arm resting on the back of the chair.]
White Hat: But you never learned to write software.
Cueball: No, I just learned how to glue together stuff that I don't understand.
White Hat: I...OK, fair.

This is super true!
People still use old tutorials and glue stuff together hoping it will work, which it never does.
That is why there is so many paging related questions. (mostly triple faults)
Broken tutorials + broken people = mashup of broken code.
It is true that it is just easier to "steal" something, but hey where is the learning part?

The problem is that for a lot of projects, it does work - for certain values of 'work' which depend on the amount of wiggle room and YAGNI there is in the initial project. It usually results in a buggy, unmaintainable mess, but one that gets the job done fast enough to meet the deadline, and works just well enough, just long enough for the developer to cash their paycheck (or pass their course) and move on to their next disaster.

The result is that there are armies of semi-trained 'developers' who don't really know how to do anything other than glue together hot garbage.

Some of these code-flipping programmers then conclude that gluing together hot garbage is what programming is all about, and decide that they want to try their hand at this 'operating system' thingie people think is so impressive (never mind that they often don't actually know what an OS really is, or even get that they have been using one already).

To be fair, this is often just a phase which newbies are going through, and the better ones do wise up quickly. Too many never do, though. Even for those who do get past it, it often takes a while (and maybe a few whacks with a clue-by-four) before the lesson sinks in.

In some ways, it's part of the natural progression for any programmer when trying something new, and it usually only becomes a problem when they are either trying to reach too far too soon, or persist at it long after they should have gotten a better understanding of the techniques, or if they are trying to build their career on code-flipping without regard to the consequences.