Design 16: Operating Systems

Theme

I renamed Puzzle 7, "Operating Systems", to "A History of Operating Systems" because the puzzle focused on different consumer operating systems rather than operating system concepts. This created a gap in the archive since I didn't have a puzzle focused on the concepts themselves.

I get a bit concerned if I release back-to-back relatively inaccessible puzzles. For example, the previous puzzle, "Queuing Theory", is not a commonly studied area of computer science compared to others. Operating systems are one of the more accessible and commonly studied areas of computer science, especially in undergrad. Most developers have at least encountered topics like processes, scheduling, and locks even if they have never formally studied operating systems.

Grid

I was worried whether I could physically fit all the answers as I began constructing the grid. The answers for this puzzle were relatively long. Five answers were 9 characters or more, eight were 6 - 8 characters, and the shortest was 5 characters long.

My previous puzzle, "Human-Computer Interaction", had a very unbalanced grid (11 across, 3 down) due to the answer lengths and lack of shared letters. As a result, I had to stack most of the answers horizontally to fit them within the grid.

I didn’t want to repeat that here. Thankfully, I was able to create a much more balanced grid (8 across, 6 down). Even better, I think the grid looks nice despite the relatively long answers. The answers shared many letters in common, which created more opportunities for intersections and eliminated the need to stack answers horizontally.

Clues

The answers I chose for this puzzle were fairly typical for an operating systems theme. Answers like process, thread, scheduler, mutex, semaphore, and deadlock are canonical topics discussed in operating systems courses. As a result, I didn’t feel the answer selection itself was particularly unique.

This also influenced how I approached writing the clues. Initially, most of the clues followed common textbook definitions simplified for clarity. However, I added additional clauses to make them less textbook-like and more interesting. For example, details like "made time-sharing systems practical in the 1970s and 1980s" and "hierarchical directories were introduced in Multics in the 1960s" were included to provide additional historical context.

Tradeoffs

I originally wanted to include Microkernel, Monolithic, and Tanenbaum in the puzzle. Together, these three clues reference different approaches to kernel architecture design, a topic famously discussed by Andrew Tanenbaum and Linus Torvalds. Microkernels emphasize modularity and isolation, while monolithic kernels favor simplicity and performance.

However, I decided to prioritize foundational operating systems concepts over a more specialized topic.

Notes

In my previous design note, I mentioned that the next puzzles would be "Computer Security" followed by "Computer Architecture." This puzzle was an unplanned addition after taking a closer look at the previous operating systems puzzle.

Next up is "Computer Security" as originally planned!