About

About

1
2
3
4
5
6
7

student@code0-god.github.io:~$ ./life
[INIT]     Launching life process (PID 1)
[FAULT]    Unrecoverable condition encountered
[LOG]      Dumping state to /var/log/life.log
[REFLECT]  Reflection service started
[RESUME]   Execution resumed
student@code0-god.github.io:~$

About Code0:

Welcome to Code0: , a personal log and reflection space by a computer‑architecture researcher and enthusiast.
I document my journey in as follows:

  • C/C++
  • Computer Organization & Architecture (CO&A)
  • Operating Systems (OS)
  • AI acceleration (AI-accel) research (as an undergrad intern),
  • Coding Challenges
  • Data Structures & Algorithms

Here, system faults and unexpected traps in both silicon and life become an opportunities to record, reflect, and resume.

Philosophy

  • Faults are inevitable.
    Just as a page fault or pipeline hazard can’t always be prevented, unexpected events in research and life will occur.

  • We don’t hide or “fix” every glitch.
    Instead of masking errors, we dump state, examine the logs, and learn from the failure.

  • Reflection is the key to progress.
    Each post includes lessons learned, acting as a “reflection daemon” that turns raw logs into insight–so the next execution runs more smoothly.

What You’ll Find Here

  • Study Notes
    C/C++ tips, CO&A topics, OS internals, AI-accel Research, and more.

  • Project Logs
    Undergrad AI‑acceleration research, hardware benchmarks, system‑level experiments, and internship stories.

  • Coding Challenges
    Baekjoon problem write‑ups, algorithm optimizations, and competitive programming insights.

  • Reflections
    Lessons from failures, performance tuning stories, debugging journeys, and retrospective analyses.

How to Navigate

  1. Home
    A rolling feed of the latest logs and posts.

  2. Tags
    Browse by topic: C/C++, CO&A, OS, research and more.

  3. About
    (You’re here!) Principles and purpose behind this site.

  4. Contact
    Reach out via GitHub issues or at code0.sin@gmail.com.

This is my trace buffer: a living record of faults, findings, and forward progress. Execution continues–always.