Skip to content

🏇天码行空 · SkyHorse

🐴 Fly ⏭⇉ Sky 🏙️

Submissions History

Still very hard to believe how 4,699 submissions in 2024 came......

Bilingual ReadingBilingual CodeFramework
🔵English + 🔴中文Docusaurus️📜

📖 Blog Guide

🗂️️ Home Display & Double Indices 📍

Each home page card represents an article for a LeetCode problem.

Catalog integrates two indices: outer index on Data Structures & Algorithms topic; inner index on difficulty.

Articles Cards Double Indices

Bilingual: 🔠English & 中文🀄

Indices here aren’t the only doubled feature.

Entire blog posts are also bilingual: English + 中文. Top right toggle is the switcher.

Bilingual English Bilingual Chinese

Programming: 🅿️Python & 🅒C++

How about adding another doubled feature, shall we?

Code examples offer Python and C++ by switchable tabs.

Python Code C++ Code

How I Set SkyHorse 🤔

In Chinese, horse (马) and code (码) has the same pronunciation “ma”, and their shapes look alike.

A Chinese phrase called 天马行空 combines sky (天) and horse (马) to metaphor creativity.

SkyHorse Origin 🎬

Back in early 2024, when I first created this SkyHorse repo, my only goal was to archive all my data structures and algorithm practice code. I never expected myself to one day come up with the name SkyHorse.

As a complete beginner stepping into data structures and algorithms at that time, I was having big doubt, constantly questioning whether I could survive. Navigating Professor Tim Roughgarden’s open source lectures was really brain-burning 🧠.

Evolution Journey 🚙

Two years have flashed by me so fast. My feel with data structures and algorithms has totally changed.

I used to think of myself as someone who just preferred living a chill life and disliked using my brain. Yet, without realizing it, I now find my mind entirely locked in. I dedicate quite some time to solving untouched LeetCode Hard problems:

  • Pushing limits of execution speed.
  • And even refining code styles just to be cleaner 😆

It is very hard to describe what is going on inside my mind, but I know for sure that problem-solving has become a big part of who I am.

Present: Keep Climbing 🧗

Repo History

One day, as I casually scrolled through my repo’s history and noticed 200+ commits, a thought hit me: “Why stop here?”

I decided to start writing detailed problem explanations to document my intuition & thought processes when faced with complex problems.

A lot of times, these breakthroughs were from late realizations that only truly appeared after tackling a problem for 10th time.

Though these growths arrived late, perhaps this is exactly why they are much like a fine wine that only grows with time 😄