We've opened the passed.jp article corner. From here on, we'll publish pieces on the theme of passing and growing.
Ending with just an "it's open" notice felt a little flat, so let this article be the place where we put into words exactly what, why, and with what promises we write — so that a single read tells you what kind of place this is.
Why one portal for both "passing" and "growing"
Under one roof, passed.jp keeps a problem set for English exams, games for taking a break, and recommendations of works worth watching. At first glance they may look unrelated.
But inside the operator's mind, they're connected by a single line: the belief that passing an exam and getting better at a hobby are, in the end, the same continuous act of "getting better."
Whether your English score climbs or you finally clear a game stage you kept failing, the essence of what's happening is the same. "Something you couldn't do yesterday, you can do today." That small, repeated sense of traction is what moves a person forward. Passing is just the moment that goal gets a name — and with or without a goal, the improving itself feels good. So we don't sort qualifications and hobbies onto separate shelves. We want to answer the single feeling of "I want to get better," all at once.
This article corner fills the gaps the services don't cover
That said, each service has a role it's good at.
- The English problem set is for English exams. Solve, miss, solve again. It carries that loop of repetition.
- The games are a place to take a break. When you're tired, play quickly in the browser and reset your mood.
- The recommendations are for introducing works. They deliver the spark of meeting the next thing you'll want to watch or read.
A place to solve, a place to rest, a place to meet works. It looks complete — and yet exactly one area is missing: the things that live outside the services. How to learn itself, what the operator is actually thinking day to day, and what mechanisms we build to keep going.
We made this article corner to fill that gap. For example: how to run a problem set properly, how to break out when your progress stalls, why we designed a service the way we did, and how we face AI while making things. The stories that won't fit inside a service screen — but might actually be the most useful — go here.
Three promises to our readers
If we're going to write, we'll commit to a quality bar up front too.
- No copy-pasted generalities. "Consistency matters," "a little every day" — we won't ship articles filled only with truisms you can find anywhere. There's no point reading something here that a search already gives you.
- Always real experience and concrete steps. We won't stop at the abstract. We'll bring it down to the grain of "here's exactly what I did, in this order," so you can copy it on the spot. To us, useful means the reader can take the next move.
- No forced daily updates. Quality over quantity. When there's enough worth saying, we publish one piece with real substance. We won't trade these promises away to pad our update frequency.
A way into the articles already here
We say "newly opened," but a few articles are already lined up. One is a set of essays jotting down things we noticed mid-creation — like how facing AI seriously brings out your humanity, or how we were reminded that publishing matters. The operator's unfiltered thinking, as is. The other is the special "Claude series," told from the viewpoint of Claude Code — the coding AI — being "surprised by how a human uses it." Across five parts, it covers everything from building a dev team to physically caging an AI's recklessness. Both are living examples of the "gaps" mentioned above. If you like, take a peek from the article list.
We look forward to having you here.
