What did I get, as a software engineer, out of choosing a general high school?
Here is what this post covers:
- Introduction
- KOSEN (computer science) vs. a general high school
- Subjects that turned out useful
- What was a waste
- What about now, in the age of AI?
- Wrapping up
Introduction
Some background for readers outside Japan. After junior high school, at around 15, most Japanese students go on to a three-year high school. A general high school (futsūka) teaches academic subjects and mostly prepares students for university entrance exams. A KOSEN, or national college of technology, is the other option: a five-year program that starts at 15 and teaches engineering alongside general subjects, so its graduates can start work at 20.
In my third year of junior high, I was torn between a KOSEN and a general high school with an entrance score around 60 on the Japanese deviation scale, the kind of school people call a “self-proclaimed college-prep school.” In the end I picked the high school for a reason that, looking back, was pretty silly: someone I disliked was going to the KOSEN.
I regretted that choice for a long time afterward. But now that I am a software engineer, one question came to mind: were there actually any skills I could only have gotten from a general high school?
In this post I compare the KOSEN curriculum with a general high school’s, one situation at a time, by how useful each is to a software engineer. I also look at how that comparison changes now that writing code with AI has become the norm.
KOSEN (computer science) vs. a general high school
What you learn at a KOSEN
In a KOSEN computer science department, computer science subjects build up year by year.
- In the Department of Information and Computer Engineering at National Institute of Technology, Toyota College, you take Programming I in year 1, Algorithms and Data Structures in year 3, Object-Oriented and Software Design in year 4, and Theory of Programming Languages in year 5
- At National Institute of Technology, Ibaraki College, year 4 covers software engineering, databases, operating systems, and language processing, and year 5 adds information security
- Across computer science departments in general, students cover a wide range, from networking and security to hardware
Side by side, situation by situation
Put next to a general high school, it looks like this.
| Situation | KOSEN (computer science) | General high school |
|---|---|---|
| Job hunting and the first year at work | Already has implementation experience and CS fundamentals | University graduates start work at 22, two years later than KOSEN graduates |
| Algorithms and complexity | Took data structures in year 3 | Many people first learn it at university |
| OS, networking, databases | Studied systematically in years 4 and 5 | Picked up on your own or at university |
| English technical documents | Mostly general-subject English, so it varies a lot by person | Reading skills from exam English give you a base |
| Math | Strong in engineering math | Builds up through Math III (the most advanced high school course, covering calculus) |
| Japanese and writing | Tends to be a weak spot | Pays off in design documents, blog posts, and requirements definitions |
| Range of paths | Three options: a job, an advanced course, or transferring into a university | A wide choice of universities, faculties, and departments |
Note that what a KOSEN teaches varies a lot by department. This comparison is for computer science departments.
On specialized CS knowledge and getting to work early, the KOSEN clearly comes out ahead. Where the general high school is strong is the foundation in general subjects such as English, math, and Japanese, and the range of paths it leaves open.
Subjects that turned out useful
So which of the things I learned at a general high school actually help at work? Looking back, there are four.
| Subject | Where it helped | What I got from it |
|---|---|---|
| English | Understanding official documentation and technical articles in English | Reading comprehension in English |
| Essays and fiction (modern Japanese) | Reading about architecture and design theory | Reading comprehension, putting things into words |
| Preparing for the second-stage university entrance exams (math and others) | System design and planning out work | Not calculation but thinking, the ability to lay out a line of reasoning |
| Kanbun (classical Chinese) | Tracing NLP or string manipulation in my head | A feel for rearranging word order, following syntax mechanically |
- English pays off most directly, since technical documentation is mostly in English.
- Modern Japanese is the foundation for putting things into words when I write design documents or blog posts.
- Preparing for the second-stage exams, which are each university’s own written exams with long-form answers, trained me not just to reach an answer but to work out how to solve the problem. That has the same structure as system design.
- Kanbun is classical Chinese read as Japanese by reordering the words with marks. That reordering feels similar to tracing string processing in my head. That said, this is just my own impression, and it may well be bias. I dig into that impression in Was reading kanbun a parser running in my head?.
What was a waste
On the other hand, some things look like a waste in hindsight. This includes school life itself, not just subjects.
| Item | Why |
|---|---|
| Classical Japanese | I never saw the point of studying it |
| PE | Sports day and martial arts classes added stress and lowered my IQ |
| Home economics | It felt like too much time spent on things you can do at home |
| School rules | There were a lot of pointless rules, which doubled my stress and lowered my IQ |
| Pressure to study for entrance exams | The pressure was far too high, which doubled my stress and lowered my IQ |
PE, the school rules, and the exam pressure all stay with me as memories of being too stressed to think clearly. I also wrote about how my high school managed students in Why finding out that everyone is doing the same thing kills your focus.
What about now, in the age of AI?
Everything above assumes that engineers write code with their own hands. These days, though, having AI write the code is the norm. Once that assumption changes, the KOSEN-versus-high-school comparison looks a little different.
The KOSEN’s edge shifts from writing code to judging it
First, the gap that comes from implementation experience itself has narrowed. Ask an AI, and even someone who has never studied algorithms gets working code. The KOSEN graduate’s advantage of “already being able to write code” in the first year on the job is not as big as it used to be.
That said, CS fundamentals have not lost their value. To judge whether the complexity of AI-generated code is reasonable, or whether it handles the database or the network sensibly, you still need that knowledge. I think the CS fundamentals taught at a KOSEN have changed roles: from knowledge for writing code yourself to knowledge for judging whether the AI’s output is right.
The general high school’s strengths matter more, if anything
- Putting things into words, trained by modern Japanese: Instructions to an AI are written text. The more clearly you can write down what you want to build and what constraints apply, the better output you get from the AI. Just as with design documents and requirements definitions, your ability to put things into words shows up directly in the quality of what gets built.
- Laying out a line of reasoning, trained by the second-stage exams: When you hand a large task to an AI, you first need to work out how to break it down and in what order to ask for each piece. Practice at thinking through how to solve a problem pays off here.
- Reading English: AI now translates and summarizes English documentation, so the gap in English reading ability is smaller than it used to be. Still, there remains a difference in whether you can check the original when the AI’s summary is wrong.
Now that writing code with AI is easy, two abilities carry more weight: deciding in words what to build, and judging what comes out. The first is close to the reading, writing, and thinking I got from a general high school; the second is close to the CS fundamentals a KOSEN teaches. Neither one is enough on its own, so I think someone from a general high school like me ends up filling in CS fundamentals later, while someone from a KOSEN ends up filling in the ability to put things into words.
Wrapping up
What I got from a general high school was not specialized skills but the ability to read, write, and think. I think that is a strength the KOSEN’s specialized courses do not give you, and now that writing code with AI is the norm, I feel those three abilities are worth more, not less. Then again, if I had gone to the KOSEN back then, I would probably have come away with a different set of strengths.