<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Time Management on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/time-management/</link><description>Recent content in Time Management on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 16 Sep 2026 21:00:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/time-management/index.xml" rel="self" type="application/rss+xml"/><item><title>After the Wheelchair Blew Up — Part 2: Sixteen Months from NAND Gates to Computer Networks</title><link>https://blog.lynxflow.co/en/posts/cs-self-study-timeline/</link><pubDate>Wed, 16 Sep 2026 21:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/cs-self-study-timeline/</guid><description>&lt;img src="https://blog.lynxflow.co/images/cs-self-study-timeline-cover.png?v=0922" alt="Featured image of post After the Wheelchair Blew Up — Part 2: Sixteen Months from NAND Gates to Computer Networks" /&gt;The Tab I Owe from Last Time The last post, &amp;ldquo;After the Wheelchair Blew Up,&amp;rdquo; ended with three routes: the foundation, the hard core courses, and using your own machine as the battlefield. After publishing that piece, I got a question—one that I asked myself: &amp;ldquo;What about time?&amp;rdquo;
A route without time is just a wish. This post pins the time down.
First, Acknowledge Three Constraints Before laying out the schedule, admit three things—or the schedule is just self-deception:</description></item></channel></rss>