1000000 瀏覽次數的感想

在下自2010年開始撰寫這個 Blog ，至今已在 2026年 終於達到 1000000 瀏覽次數。

衷心感謝各位讀者的支持，願意閱讀在下的文章。

最初，在下因學習需要，為了方便回顧過去的知識(主要是科技方面)，
因此啟用了 Google 的 Blogspot 服務，開始撰寫與學習相關的文章，並將自己收集的遊戲資料整理發佈。
那時的構思主要是聚焦於 Java編程，因為在下 Java 有興趣，而且當時也在學校學習。
但不久後，在下覺得撰寫主流科技資訊並不適合自己，因為網上已經有很多作者在撰寫相似內容，競爭激烈，想要突圍並不容易。
於是，在下決定改變思路，轉向非主流科技資訊，認為這樣可以學習到更多額外的知識，同時也能夠別樹一格。

在此期間，因為課程的安排，需要使用 Linux 。
最初對 Linux 十分抗拒，這是因為在下已經習慣使用 Windows ，對於新系統的學習感到畏懼。
然而，為了完成作業，如果家中的電腦沒有 Linux ，必然會影響在下的學習進度。
最終，在下安裝了 VMWare Player 及 Ubuntu 來解決這個問題。隨著學習進度，在下發現 Linux 並不如別人所說的那樣難用，
反而有些在 Windows 上無法執行的任務，在 Linux 上卻運行得十分流暢。

在下對 Linux 的不確定與恐懼也逐漸下降。於是，在下開始投入更多時間學習 Linux ，也漸漸地改變了自己的使用習慣。
由於大多數主流軟件都不支持 Linux ，因此在下的日常工作逐漸轉向使用支持 Linux 的非主流軟件、開源軟件及自由軟件。
在這個過程中不僅學會了如何有效使用 Linux ，認識到開源社群。

到了 2016年，在下因進修關係，需要一邊工作一邊讀書，在雙重壓力讓在下經常覺得疲倦。
不過因為在工作的同時能夠應用到在學到的知識，都感到滿足。
直到 2018年 ，那時在下忙於完成 Final Year Project ，面臨了巨大的壓力。

不知是否壓力太大， 2018年末 的一個早上，在下突感劇痛。起初以為只是小病痛，便去附近的診所檢查。
不料，醫生告訴在下情況可能很嚴重，於是給予在下轉介信，要求在下迅速前往急症室。
當在下到達急症室並提交轉介信後，不到 5分鐘 ，療護人員便推著病床，將在下送進診斷室。
經過檢查後，在下被確診為癌症，隨即需要住院進一步檢查。

在住院期間，在下向家人、學校督導及工作上司報告了在下的情況。
最終在下與學校督導傾談後 申請2年休學 ，並根據工作上司的安排 申請2個月病假 。
不久後，在下接受了首次手術治療。在醫院的日子十分無聊，在下請求家人帶來在下的手提電腦，以便在住院期間更新Blog及娛樂。
期間，除了家人的探望，還有學校督導、同學、工作同事、朋友及網友不時來探望。
2週後，終於出院，但療程並未結束，隨之而來的是一連串的化療及定期的醫療覆診。

化療期間給自己拍攝的相片，化療液流進身體會感到寒冷。

出院不久就是新年，家人勸在下專心休養。在整理物品時，在下偶然發現一個PS1遊戲控制器，這個 PS1遊戲控制器 竟然成為了在下撰寫文章的轉捩點。
過去，在下一直專注於軟件相關的科技知識，但看到這個控制器的那一瞬間，在下心中閃過一個念頭：「能否改裝成在電腦上使用的遊戲控制器？」
這一思考讓在下開始接觸硬件相關的科技知識，於是在下決定探索這個領域。

2019年起，在下開始在 Blog 上撰寫有關微控制器、集成電路及電子零件的文章，並探索與硬件通訊的方法。
由於在下曾經使用 Packet Capture 及 MITMProxy 擷取 Ingress 的 HTTP請求 ，並用其他方法來發送 HTTP請求 玩 Ingress ，這段經歷成為學習硬件的基礎。
在下認識了硬件通訊的原理後，發現控制硬件的關鍵在於發送正確的訊號。
如果能夠發送與原生軟件相同的訊號，便能正確控制硬件。
這促使在下開始學習訊號破解的技術，這樣便不需要依賴原生軟件，可以自行編寫更符合需求的軟件來控制硬件。

從最初撰寫科技文章的動機，原本只是希望避免忘記學習過的知識，
但回顧這 16年 ，在下最大的收穫不是學會甚麼知識或技術，而是耐性與堅持。
從使用 Windows 到轉用 Linux ，從使用主流軟件到轉用非主流軟件，關鍵就是耐性及堅持。
在下並不是 遊戲高手 、 科技專家，在下只是嘗試一些不是主流的事情，
即使原本的知識不足，只要願意投入時間與耐性去學習，許多事情最終都能夠完成。

在下認為，如果想要完成某件事情，便會主動尋找方法；而如果不想完成，則會不斷尋找藉口。
就如同玩 Bio Hazard 的各種挑戰，例如競速通關、不儲存通關、無傷通關或刀通關等，在下曾經認為這些目標不能達成。
然而，當在下觀看了其他玩家的遊戲影片，看到他們在這些限制條件下成功完成遊戲後，
才知道，不是這些挑戰不可能完成，而是在下無有能力去完成。
自己無法達成目標的主要原因是因為能力不足後，在下決定挑戰這些限制條件，
在下仔細觀察別人操作方法，了解機制後，便可以創造屬於自己的技術，
這種學習流程不只令遊戲玩更好，還能夠套用到不同情況。

當然，並不是付出努力能夠完成事情，在下都有很多事情想達成，但暫時未能完成，亦可能完全無法完成，
如果想做的事情並不犯法，又沒違背道德，不要害怕嘗試，不要恐懼失敗，不要羞於求助他人，知道自己不足有助提升自己。
因此在卻步之前，不如先問自己：「為何要放棄嘗試？」這次未能達到目標，重新再嘗試就可以，
如果現實無法容許繼續嘗試，必須放棄，那就放棄，
不要因為做不到目標就是失敗，因為已經在嘗試中獲得知識及經驗，而這些都會成為未來成功的重要基石。

感謝各位讀者的支持，希望未來能繼續與大家分享更多的知識與經歷。

Reflections on Reaching 1,000,000 Views

Since I started this blog in 2010, I have finally reached 1,000,000 views in 2026.

I sincerely thank all readers for your support and for taking the time to read my articles.

Initially, I began this blog for my studies, to conveniently revisit past knowledge (mainly in technology). I utilized Google's Blogspot service to start writing articles related to my learning and published game data that I had collected. At that time, my focus was primarily on Java programming, because I was interested in Java and was also learning it at school. However, I soon felt that writing about mainstream technology did not suit me, as there were already many authors writing similar content online, making it difficult to stand out. Hence, I decided to shift my approach towards non-mainstream technology information, believing that this would allow me to learn more additional knowledge and create something unique.

During this period, due to course requirements, I needed to use Linux. Initially, I was quite resistant to Linux because I was used to using Windows and was fearful of learning a new system. However, to complete my assignments, I needed Linux on my home computer, or it would hinder my learning progress. Eventually, I installed VMWare Player and Ubuntu to solve this problem. As I progressed in learning, I discovered that Linux was not as difficult to use as others had said; rather, certain tasks that could not be executed on Windows ran very smoothly on Linux.

My uncertainty and fear of Linux gradually diminished. I began to dedicate more time to learning Linux and slowly changed my usage habits. Since most mainstream software did not support Linux, my daily work gradually shifted towards using non-mainstream software, open-source software, and free software that were compatible with Linux. In this process, I not only learned how to use Linux effectively but also got to know the open-source community.

By 2016, I had to work while pursuing further studies, and the dual pressure often left me feeling fatigued. However, I felt fulfilled because I could apply the knowledge I had learned in my job. Until 2018, when I was busy completing my final year project, I faced immense pressure.

I don't know if it was too much pressure, but one morning at the end of 2018, I suddenly felt acute pain. At first, I thought it was just a minor issue, so I went to a nearby clinic for a check-up. To my surprise, the doctor informed me that it might be serious and provided me with a referral letter, asking me to go to the emergency department immediately. Upon arrival and after presenting my referral letter, within 5 minutes, the medical staff pushed a stretcher and took me into the examination room. After checking, I was diagnosed with cancer and had to be hospitalized for further examination.

During my hospitalization, I informed my family, school supervisor, and work supervisor about my situation. After discussing with my school supervisor, I applied for a 2-year leave of absence and, following my work supervisor's arrangements, applied for 2 months of sick leave. Shortly after, I underwent my first surgery. The days in the hospital were extremely dull, so I requested my family to bring my laptop so I could update the blog and entertain myself during my stay. Apart from visits from family, school supervisors, classmates, colleagues, friends, and online acquaintances came to see me from time to time. After 2 weeks, I was finally discharged, but the treatment wasn't over; it was followed by a series of chemotherapy sessions and regular medical check-ups.

During chemotherapy, I felt cold when the chemical infusion entered my body.

Not long after being discharged, it was New Year, and my family advised me to focus on recovery. While organizing my belongings, I accidentally discovered a PS1 game controller, which surprisingly became the turning point for my writing. Previously, I had been focused solely on software-related technology knowledge, but at that moment, the thought crossed my mind: "Can I modify this to use as a game controller for my computer?" This thought led me to begin exploring hardware-related technology knowledge, and I decided to delve into this field.

Starting from 2019, I began writing articles about microcontrollers, integrated circuits, and electronic components on my blog, and explored methods of communication with hardware. Because I had once used Packet Capture and MITMProxy to capture HTTP requests for Ingress, and employed other methods to send HTTP requests to play Ingress, this experience became the foundation for my hardware learning. Once I understood the principles of hardware communication, I realized that the key to controlling hardware lay in sending the correct signals. If I could send the same signals as the native software, I could correctly control the hardware. This inspired me to learn signal cracking techniques, allowing me to write software tailored to my needs without relying on native software.

The initial motivation to write technology articles was simply to avoid forgetting the knowledge I had learned, but reflecting on these 16 years, my greatest gain is not the knowledge or skills acquired, but patience and persistence. From using Windows to switching to Linux, from using mainstream software to non-mainstream software, the key has been patience and persistence. I am not a gaming expert or a technology specialist; I just attempt to try things that are not mainstream. Even with insufficient initial knowledge, as long as one is willing to invest time and patience into learning, many things can eventually be accomplished.

I believe that if one wants to accomplish something, they will actively seek methods; if they do not want to achieve it, they will continuously find excuses. Just like the various challenges in playing Bio Hazard (Resident Evil), such as speedruns, no-save runs, no-damage runs, or knife-only runs -- I once thought these goals were unattainable. However, after watching other players' game videos and seeing them successfully complete the game under these restrictions, I realized that the challenges are not impossible to achieve but rather that I lacked the capability to do so. The main reason for not achieving my goals was a lack of ability, so I decided to challenge these restrictions. After carefully observing others' techniques and understanding the mechanics, I was able to develop my own skills; this learning process improved not only my gameplay but could also be applied to various situations.

Of course, effort alone may not lead to accomplishing everything. There are many things I wish to achieve that I haven't been able to, and some might be completely unattainable. If the things we want to do are not illegal and do not violate moral standards, we should not be afraid to try, nor should we fear failure, and we should not be ashamed to seek help from others. Acknowledging our shortcomings is beneficial for self-improvement. Thus, before we hesitate, we might as well ask ourselves: "Why should I give up trying?" If we do not achieve our goals this time, we can simply try again. If reality does not allow for further attempts and we must give up, then let's do so. We should not view not being able to achieve a goal as failure because through our attempts, we gain knowledge and experience, all of which will become important foundations for future success.

Thank you to all readers for your support. I hope to continue sharing more knowledge and experiences with you in the future.