[{"data":1,"prerenderedAt":1510},["ShallowReactive",2],{"tag-labels":3,"tag-items-nodejs-backend":85,"article-category-labels":1499},[4,10,15,20,25,30,35,40,45,50,55,60,65,70,75,80],{"title":5,"slug":6,"description":7,"order":8,"indexable":9},"方法","methods","可以重複使用的思考與操作方法。",1,false,{"title":11,"slug":12,"description":13,"order":14,"indexable":9},"API 設計","api-design","API 回應、介面規劃與實作原則。",2,{"title":16,"slug":17,"description":18,"order":19,"indexable":9},"轉職工程師","career-change","轉職軟體工程師的學習、工作與成長歷程。",3,{"title":21,"slug":22,"description":23,"order":24,"indexable":9},"雲端部署","cloud-deployment","雲端服務、自動化流程與部署問題的實作紀錄。",4,{"title":26,"slug":27,"description":28,"order":29,"indexable":9},"課程心得","course-review","課程參與、作業實作與學習成果的回顧。",5,{"title":31,"slug":32,"description":33,"order":34,"indexable":9},"資料庫效能","database-performance","資料庫查詢、索引與效能分析相關筆記。",6,{"title":36,"slug":37,"description":38,"order":39,"indexable":9},"Express 中介軟體","express-middleware","Express 請求流程與中介處理機制的學習筆記。",7,{"title":41,"slug":42,"description":43,"order":44,"indexable":9},"前端開發","frontend-development","前端框架、瀏覽器互動與介面開發經驗。",8,{"title":46,"slug":47,"description":48,"order":49,"indexable":9},"前後端觀念","frontend-backend","從前端與後端不同角度理解共通開發觀念。",9,{"title":51,"slug":52,"description":53,"order":54,"indexable":9},"六角學院","hexschool","六角學院課程、活動與作業的學習紀錄。",10,{"title":56,"slug":57,"description":58,"order":59,"indexable":9},"HTTP 狀態碼","http-status-codes","HTTP 回應狀態與 API 使用情境整理。",11,{"title":61,"slug":62,"description":63,"order":64,"indexable":9},"JavaScript 基礎","javascript-basics","JavaScript 語法、瀏覽器功能與基礎觀念。",12,{"title":66,"slug":67,"description":68,"order":69,"indexable":9},"學習成長","learning-growth","長期學習、能力累積與自我成長的經驗。",13,{"title":71,"slug":72,"description":73,"order":74,"indexable":9},"學習筆記","learning-notes","課程、文件與實作過程整理出的學習筆記。",14,{"title":76,"slug":77,"description":78,"order":79,"indexable":9},"Node.js 後端開發","nodejs-backend","使用 Node.js 建立後端服務的學習與實作紀錄。",15,{"title":81,"slug":82,"description":83,"order":84,"indexable":9},"PostgreSQL 資料庫","postgresql-database","PostgreSQL 資料庫設計、查詢與效能分析筆記。",16,[86,266,635,696,817,980,1163,1349],{"id":87,"title":88,"author":89,"body":90,"category":252,"cover":253,"description":254,"extension":255,"featured":9,"meta":256,"navigation":257,"path":258,"publishedAt":259,"relatedTools":253,"seo":260,"slug":261,"status":262,"stem":263,"tags":264,"updatedAt":253,"__hash__":265},"articles\u002Fblog\u002F20260902-nodejs-course-review.md","六角學院【後端】Node.js 直播班心得：從作業、最終專案到部署踩坑覆盤","jessie",{"type":91,"value":92,"toc":244},"minimark",[93,98,102,109,112,115,118,121,124,127,130,133,136,139,142,145,149,152,155,171,177,188,194,198,201,204,207,210,213,216,219,223,226,229,232,235,238],[94,95,97],"h3",{"id":96},"針對-js-直播班的覆盤在-nodejs-真的做到了","針對 JS 直播班的覆盤，在 Node.js 真的做到了",[99,100,101],"p",{},"在報到任務時，我曾經許下這個心願：",[99,103,104],{},[105,106],"img",{"alt":107,"src":108},"作者在課程 Discord 分享希望每週按時完成 Node.js 作業的目標","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fnodejs-course-review\u002Fb726ce3837ed6e64.webp",[99,110,111],{},"當時收到大家的按讚，通知一直跳出來，也像是在不斷提醒自己曾經許下的目標。",[99,113,114],{},"而這一次，撇除八月份工作上的變動，讓生活稍微混亂了一些之外，前七週的作業和每日任務，我確實都有按時完成～",[99,116,117],{},"一方面覺得自己真的很厲害，另一方面也讓我感受到什麼叫做「慢慢進步」。當進度不再一直累積，遇到不懂的地方時，能有時間查找資料，甚至進一步延伸學習。",[99,119,120],{},"經過這次每天都完成的過程中，我也慢慢有了「餘裕」，不再像上一次參加 JS 直播班時，被截止日期追著跑，最後只能想辦法趕快「完成」。",[99,122,123],{},"這一次，不只是完成作業，體會到校長說的希望為生活留「餘裕」。",[94,125,126],{"id":126},"做完後終於了解每一堂課程在後端專案中的位置的最終作業",[99,128,129],{},"這次的最終作業真的好難啊！",[99,131,132],{},"最大的難點是要從零開始建立後端。一開始真的完全不知道該從哪裡下手，還好有助教直播可以跟著做。初始環境、M1 和 M2 都是跟著直播一步一步建立起來的； M3～M6，則是自己半拚半湊完成。",[99,134,135],{},"遇到卡關時，先回去看課程直播回放，再對照助教直播的實作方式。如果還是改不動，才會找 AI 。等到功能完成、測試通過後，再回頭慢慢整理與調整程式碼。",[99,137,138],{},"第二個難點是建立資料表之間的關聯，尤其是多對多關聯。像是教練與技能的關聯，以及課程預約相關的資料表，我光是這兩個部分就卡了整整一天。",[99,140,141],{},"在建立關聯和查詢資料的過程中，常常會被外鍵、關聯方向和回傳資料的結構繞進去。雖然處理的過程很痛苦，但實際走過一次後，對資料表之間如何互相連結，以及 TypeORM 如何取得關聯資料，也比原本清楚了許多。",[99,143,144],{},"在每周直播課，以及完成當周作業都感覺一個區塊一個區塊都很好懂，但實際開始做最終作業時，發現真的無處下手，在完成最終作業的過程中，也把整期 Node.js 的課程都串連起來了！",[94,146,148],{"id":147},"兩門課程的連動利用-cloudflare-r2-完成加分題","兩門課程的連動，利用 Cloudflare R2 完成加分題",[99,150,151],{},"在完成 M0～M6 的作業要求後，我先將作業繳交，再回頭研究加分題。之前只大致看到加分題要求上傳圖片，仔細閱讀後才發現，還需要將圖片上傳至雲端儲存服務，並回傳可以直接開啟檢視的 URL。",[99,153,154],{},"這時我想到 8 月初 AI 開發進化營介紹 Cloudflare 的加碼課程中，曾經提到 R2，因此決定使用 Cloudflare R2 完成圖片上傳功能。",[99,156,157,158,162,163,166,167,170],{},"實作過程中，卡比較久的地方是在 Docker 與 GitHub Actions 的環境變數設定。我原本在 ",[159,160,161],"code",{},"docker-compose.yml"," 中指定載入 ",[159,164,165],{},"backend\u002F.env","，但 ",[159,168,169],{},".env"," 不會上傳到 Git，因此 GitHub Actions 執行 Docker Compose 時，會因為找不到該檔案而無法啟動服務。",[99,172,173,174,176],{},"後來我將 ",[159,175,165],{}," 改成選用設定：本機存在時就載入，GitHub Actions 中不存在時則略過。",[99,178,179,180,183,184,187],{},"不過修正後仍然無法啟動，原因是上傳圖片的 controller 在模組載入階段，就立即透過 ",[159,181,182],{},"config.get()"," 讀取 R2 環境變數。GitHub Actions 沒有設定 R2，因此讀到 ",[159,185,186],{},"undefined"," 並拋出錯誤，導致整個後端在 healthcheck 前就停止。",[99,189,190,191,193],{},"最後，我將 R2 設定改成只有在實際呼叫圖片上傳 API 時才讀取。如此一來，即使 GitHub Actions 沒有 R2 環境變數，其他 M0～M6 功能與 healthcheck 仍能正常啟動；本機有提供 ",[159,192,165],{}," 時，上傳功能也可以正常使用，最後終於成功啦！",[94,195,197],{"id":196},"終於被幸運之神眷顧卻差點錯過","終於被幸運之神眷顧，卻差點錯過",[99,199,200],{},"這次完成預習任務後的抽書活動，我居然抽中了！但我本人完全不知道 XD",[99,202,203],{},"直到壓線繳交完最終任務、準備回頭做加分題時，我去看直播回放才發現自己中獎了 XDD 嚇得我趕緊截圖詢問校長，確認現在是否還能領取。真的很感謝校長最後還是讓我領書～",[99,205,206],{},"在 00:51 收到校長的回覆，那一刻感受到校長一直說「自己住在 Discord 上」原來是真的 XDD",[99,208,209],{},"回想 2025 年的軟體工程師體驗營，那一期校長真的是大放送！只要完成每日任務就可以參加抽書，一天一本，每週都會抽出 5本，有時候校長上課還會額外加碼抽到10 本。",[99,211,212],{},"當時我還想說：「感覺中獎機會很大耶！」結果一次都沒有抽到過 QQ",[99,214,215],{},"從那之後，我對抽書這件事就不會過度關注了 XDDD",[99,217,218],{},"沒想到啊，沒想到！這次幸運之神居然真的眷顧我了 XDDDD 而且在我差點錯過的情況下！",[94,220,222],{"id":221},"也想感受到累積的力量","也想感受到「累積」的力量",[99,224,225],{},"這次看校長在會後的產品實驗室中，分享 ToolNeko 的成長紀錄。雖然我知道產品實驗室的主題是期待清單，但 ToolNeko 的故事反而更吸引我 XD",[99,227,228],{},"其實在 Node.js 開課前，我也曾經想過要做一個工具網站，主要是想把自己平常會用到的工具整理起來，以後就不用每次都到處搜刮～",[99,230,231],{},"不過，我從來沒有想過，原來當網站慢慢累積出流量後，還可以進一步投放廣告。聽到這件事時，真的有種新世界突然被打開的感覺 XDD",[99,233,234],{},"另外，我也參加了卡斯柏老師的 AI 開發進化營。看到老師的部落格是自己開發的網站，也覺得非常酷 XDD",[99,236,237],{},"目前我已經先買好網域了！下一個目標是：等到參加 AWS 雲端架構部署課程時，直接用自己的網站來繳交心得牆作業。希望到了那個時候，我也能開始真正感受到持續「累積」帶來的成果 XD",[99,239,240],{},[105,241],{"alt":242,"src":243},"六角學院 Node.js 直播班心得與覆盤插圖","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fnodejs-course-review\u002F90c584887f318a9d.webp",{"title":245,"searchDepth":14,"depth":14,"links":246},"",[247,248,249,250,251],{"id":96,"depth":19,"text":97},{"id":126,"depth":19,"text":126},{"id":147,"depth":19,"text":148},{"id":196,"depth":19,"text":197},{"id":221,"depth":19,"text":222},"backend-development",null,"從每週作業、資料表關聯到 Cloudflare R2 與 GitHub Actions，重新走完整個後端專案，也開始感受到「累積」的力量。","md",{},true,"\u002Fblog\u002F20260902-nodejs-course-review","2026-09-02",{"title":88,"description":254},"nodejs-course-review","published","blog\u002F20260902-nodejs-course-review",[77,22,27,52],"_5aDBShvNGrTjZafZHpQ1QUpAI1AELejaLlwTeWLjhw",{"id":267,"title":268,"author":89,"body":269,"category":252,"cover":253,"description":273,"extension":255,"featured":9,"meta":627,"navigation":257,"path":628,"publishedAt":629,"relatedTools":253,"seo":630,"slug":631,"status":262,"stem":632,"tags":633,"updatedAt":253,"__hash__":634},"articles\u002Fblog\u002F20260802-postgresql-index-explain-analyze.md","PostgreSQL 學習筆記：認識資料庫索引與 EXPLAIN ANALYZE",{"type":91,"value":270,"toc":612},[271,274,279,282,285,288,291,301,305,328,332,335,341,346,381,388,432,435,438,453,490,493,502,508,514,518,521,536,539,543,546,553,560,563,579,583,586,589,592,599,602,608],[99,272,273],{},"本篇為六角學院2026年node.js直播班中，關於資料庫索引的學習筆記整理，課中使用的資料庫為PostgreSQL，筆記內容來自課程、PostgreSQL官方文件整合而來。",[275,276,278],"h2",{"id":277},"索引是甚麼","索引是甚麼?",[99,280,281],{},"相當於一本書的目錄，記錄某章節在第幾頁。",[99,283,284],{},"下過索引後，資料庫在進行該索引條件的搜尋時，只需要找到該條件在索引中對應的資料庫位置，直接到那個位置拿資料即可。不用看跟條件不相關的資料，以此減少搜尋的時間。",[275,286,287],{"id":287},"建立索引",[275,289,290],{"id":290},"建立的重點",[292,293,294,298],"ol",{},[295,296,297],"li",{},"優先替經常查詢，且能有效縮小結果範圍的欄位評估索引",[295,299,300],{},"可下多條件(複合索引)，當多條件時，會優先從最左邊的欄位開始找資料，所以欄位的排列順序很重要。",[275,302,304],{"id":303},"什麼時候不需要建立索引","什麼時候不需要建立索引?",[292,306,307,310,313,316,319,322,325],{},[295,308,309],{},"資料表本身很小",[295,311,312],{},"查詢時會取出大部分資料",[295,314,315],{},"欄位選擇性低，且沒有其他條件輔助",[295,317,318],{},"幾乎不會被查詢的欄位",[295,320,321],{},"資料需要大量且頻繁的寫入，但查詢收益有限",[295,323,324],{},"已有功能重疊的索引",[295,326,327],{},"條件寫法無法匹配索引",[275,329,331],{"id":330},"怎麼判斷資料庫有沒有用我的索引","怎麼判斷資料庫有沒有用我的索引?",[99,333,334],{},"PostgreSQL提供兩種方式",[99,336,337],{},[105,338],{"alt":339,"src":340},"PostgreSQL EXPLAIN 與 EXPLAIN ANALYZE 指令差異表","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fpostgresql-index-explain-analyze\u002Ff827932a99d98a5a.webp",[99,342,343],{},[159,344,345],{},"EXPLAIN",[347,348,352],"pre",{"className":349,"code":350,"language":351,"meta":245,"style":245},"language-sql shiki shiki-themes github-light github-dark","EXPLAIN\nSELECT * FROM bookings WHERE member_id = 1;\n-- 可能得到\nIndex Scan using idx_bookings_member_id\n(cost=0.42..8.44 rows=200 width=20)\n","sql",[159,353,354,361,366,371,376],{"__ignoreMap":245},[355,356,358],"span",{"class":357,"line":8},"line",[355,359,360],{},"EXPLAIN\n",[355,362,363],{"class":357,"line":14},[355,364,365],{},"SELECT * FROM bookings WHERE member_id = 1;\n",[355,367,368],{"class":357,"line":19},[355,369,370],{},"-- 可能得到\n",[355,372,373],{"class":357,"line":24},[355,374,375],{},"Index Scan using idx_bookings_member_id\n",[355,377,378],{"class":357,"line":29},[355,379,380],{},"(cost=0.42..8.44 rows=200 width=20)\n",[99,382,383,384,387],{},"以下使用 ",[159,385,386],{},"EXPLAIN ANALYZE"," 作為建立索引前後的範例",[347,389,391],{"className":349,"code":390,"language":351,"meta":245,"style":245},"EXPLAIN ANALYZE\nSELECT * FROM bookings WHERE member_id = 1;\n\nSeq Scan on bookings  (cost=0.00..1834.00 rows=200 width=20) (actual time=0.015..18.432 rows=200 loops=1)\n  Filter: (member_id = 1)\n  Rows Removed by Filter: 99800\nPlanning Time: 0.089 ms\nExecution Time: 20.104 ms\n",[159,392,393,398,402,407,412,417,422,427],{"__ignoreMap":245},[355,394,395],{"class":357,"line":8},[355,396,397],{},"EXPLAIN ANALYZE\n",[355,399,400],{"class":357,"line":14},[355,401,365],{},[355,403,404],{"class":357,"line":19},[355,405,406],{"emptyLinePlaceholder":257},"\n",[355,408,409],{"class":357,"line":24},[355,410,411],{},"Seq Scan on bookings  (cost=0.00..1834.00 rows=200 width=20) (actual time=0.015..18.432 rows=200 loops=1)\n",[355,413,414],{"class":357,"line":29},[355,415,416],{},"  Filter: (member_id = 1)\n",[355,418,419],{"class":357,"line":34},[355,420,421],{},"  Rows Removed by Filter: 99800\n",[355,423,424],{"class":357,"line":39},[355,425,426],{},"Planning Time: 0.089 ms\n",[355,428,429],{"class":357,"line":44},[355,430,431],{},"Execution Time: 20.104 ms\n",[99,433,434],{},"以這份資料表而言，當系統累積到十萬筆預約紀錄後，查詢某會員的預約紀錄就要花費20.104ms",[99,436,437],{},"針對這張表建立索引",[347,439,441],{"className":349,"code":440,"language":351,"meta":245,"style":245},"CREATE\nINDEX idx_bookings_member_id ON bookings(member_id);\n",[159,442,443,448],{"__ignoreMap":245},[355,444,445],{"class":357,"line":8},[355,446,447],{},"CREATE\n",[355,449,450],{"class":357,"line":14},[355,451,452],{},"INDEX idx_bookings_member_id ON bookings(member_id);\n",[347,454,456],{"className":349,"code":455,"language":351,"meta":245,"style":245},"EXPLAIN ANALYZE\nSELECT * FROM bookings WHERE member_id = 1;\n\nIndex Scan using idx_bookings_member_id on bookings  (cost=0.42..8.44 rows=200 width=20) (actual time=0.021..0.115 rows=200 loops=1)\n  Index Cond: (member_id = 1)\nPlanning Time: 0.102 ms\nExecution Time: 0.203 ms\n",[159,457,458,462,466,470,475,480,485],{"__ignoreMap":245},[355,459,460],{"class":357,"line":8},[355,461,397],{},[355,463,464],{"class":357,"line":14},[355,465,365],{},[355,467,468],{"class":357,"line":19},[355,469,406],{"emptyLinePlaceholder":257},[355,471,472],{"class":357,"line":24},[355,473,474],{},"Index Scan using idx_bookings_member_id on bookings  (cost=0.42..8.44 rows=200 width=20) (actual time=0.021..0.115 rows=200 loops=1)\n",[355,476,477],{"class":357,"line":29},[355,478,479],{},"  Index Cond: (member_id = 1)\n",[355,481,482],{"class":357,"line":34},[355,483,484],{},"Planning Time: 0.102 ms\n",[355,486,487],{"class":357,"line":39},[355,488,489],{},"Execution Time: 0.203 ms\n",[99,491,492],{},"建立索引後，查詢某會員的預約紀錄時間僅需 0.203ms",[494,495,496],"blockquote",{},[99,497,498],{},[499,500,501],"em",{},"此案例時間僅代表本次測試環境，重點是比較相同條件下建立索引前後的執行計畫與相對差異。",[275,503,505,507],{"id":504},"explain-analyze在說甚麼",[159,506,386],{},"在說甚麼？",[99,509,510],{},[105,511],{"alt":512,"src":513},"PostgreSQL 執行計畫中的掃描、索引、成本與時間欄位說明表","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fpostgresql-index-explain-analyze\u002F1317530aeaf8f00d.webp",[275,515,517],{"id":516},"join的時候怎麼規劃索引","JOIN的時候怎麼規劃索引?",[275,519,520],{"id":520},"對症下藥才能有效提升效能",[522,523,524,527,530,533],"ul",{},[295,525,526],{},"先查看完整執行計畫",[295,528,529],{},"找出真正成本較高或掃描資料過多的節點",[295,531,532],{},"評估連接鍵、篩選欄位及資料量",[295,534,535],{},"再決定哪張表需要哪種索引",[99,537,538],{},"多表連接時，應透過執行計畫逐一確認各資料表的掃描與連接成本，再針對常用連接鍵或篩選欄位評估索引，而不是直接替所有欄位建立索引。",[275,540,542],{"id":541},"為什麼建立-index-但資料庫還是逐筆搜尋","為什麼建立 Index 但資料庫還是逐筆搜尋？",[275,544,545],{"id":545},"資料庫本身也有思考",[99,547,548,549,552],{},"即使建立索引，但在執行查詢時，PostgreSQL 內會有 ",[499,550,551],{},"planner","，負責比較不同計畫的估算成本，選擇它認為總成本最低的方案。",[99,554,555,556,559],{},"且因索引是獨立於資料表的資料結構，一般 ",[159,557,558],{},"Index Scan"," 還可能先從索引找到資料位置，再回原資料表取得完整欄位。",[99,561,562],{},"如果他判斷逐筆查詢成本較低，就不會使用索引。",[494,564,565],{},[99,566,567],{},[499,568,569,570,578],{},"PostgreSQL devises a query plan for each query it receives. Choosing the right plan to match the query structure and the properties of the data is absolutely critical for good performance, so the system includes a complex planner that tries to choose good plans. You can use the ",[571,572,576],"a",{"href":573,"rel":574},"https:\u002F\u002Fwww.postgresql.org\u002Fdocs\u002Fcurrent\u002Fsql-explain.html",[575],"nofollow",[159,577,345],{}," command to see what query plan the planner creates for any query. Plan-reading is an art that requires some experience to master, but this section attempts to cover the basics.",[275,580,582],{"id":581},"索引的成本有哪些","索引的成本有哪些?",[275,584,585],{"id":585},"索引不免費",[99,587,588],{},"前面提到過索引是獨立於資料表的資料結構，所以會占用儲存空間；資料新增、修改或刪除時，也可能需要額外同步更新索引。",[99,590,591],{},"可以說",[494,593,594],{},[99,595,596],{},[499,597,598],{},"建立索引就是犧牲部分增刪修，讓查的效能最大化。",[99,600,601],{},"其實每次的優化就是一個取捨的過程，假設有一張資料表在建立索引前，每次查詢都需要花費5s，寫入需要1.35s，建立索引後查詢只要0.05s，寫入變成1.47s。這樣該表的業務情境下是否值得建立索引呢?",[99,603,604],{},[105,605],{"alt":606,"src":607},"作者補充說明：以課程練習與實作經驗整理技術筆記","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fpostgresql-index-explain-analyze\u002Fdaccc04020965d70.webp",[609,610,611],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":245,"searchDepth":14,"depth":14,"links":613},[614,615,616,617,618,619,621,622,623,624,625,626],{"id":277,"depth":14,"text":278},{"id":287,"depth":14,"text":287},{"id":290,"depth":14,"text":290},{"id":303,"depth":14,"text":304},{"id":330,"depth":14,"text":331},{"id":504,"depth":14,"text":620},"EXPLAIN ANALYZE在說甚麼？",{"id":516,"depth":14,"text":517},{"id":520,"depth":14,"text":520},{"id":541,"depth":14,"text":542},{"id":545,"depth":14,"text":545},{"id":581,"depth":14,"text":582},{"id":585,"depth":14,"text":585},{},"\u002Fblog\u002F20260802-postgresql-index-explain-analyze","2026-08-02",{"title":268,"description":273},"postgresql-index-explain-analyze","blog\u002F20260802-postgresql-index-explain-analyze",[82,32,72,52],"y_fTAv8SaCd5InCyg86y2tJqpipsam8tAZoPcrhHyDU",{"id":636,"title":637,"author":89,"body":638,"category":252,"cover":253,"description":687,"extension":255,"featured":9,"meta":688,"navigation":257,"path":689,"publishedAt":690,"relatedTools":253,"seo":691,"slug":692,"status":262,"stem":693,"tags":694,"updatedAt":253,"__hash__":695},"articles\u002Fblog\u002F20260704-express-middleware-vue-router-guard.md","用 Vue Router Guard 理解 Express Middleware",{"type":91,"value":639,"toc":685},[640,643,646,649,652,655,658,661,664,667,670,676,679,682],[99,641,642],{},"這兩周六角Node.js課程的每日任務多集中在Middleware，由於 Middleware 這個概念第一次出現時，提供的解釋包含像解決 CORS 時使用第三方套件，並說明這類東西就屬於 Middleware，所以我以為它就是別人寫好、針對某件特定事情處理的單一功能性套件，大概就像是 Axios 這種 package。",[99,644,645],{},"包含後面的每日任務中也有提到「自訂 Middleware」，感覺就跟前端開發時自己寫一個共用元件是很類似的概念。後來去查才發現 Middleware 其實是 Express 框架下，請求流程中的中介處理機制，並不是只指套件。",[99,647,648],{},"簡單來說，只要符合請求流程中的中介處理機制，不論是自訂或者使用第三方，都可以是 Middleware。",[99,650,651],{},"以 Express 框架來說，Middleware 通常會接收三個參數，分別是 Request、Response 和 Next。",[99,653,654],{},"針對 Request進行一些基本驗證或共用前置處理，比如驗證 token 、解析 JSON 等等。處理完成之後，如果已經可以決定結果，可以直接用 Response 回傳，或者使用 Next 讓這一段請求進入到下一段的邏輯。",[99,656,657],{},"然後在查Middleware的過程中，感覺這段描述怎麼跟我 Vue 的路由守衛有點相似。",[99,659,660],{},"這兩個的差異在於，Vue 的路由守衛是針對前端要切換路由前，去做一些事情，比如驗證當前使用者是否有進入該頁面的權限。如果沒有權限，就把他導向錯誤頁面或重新登入；在符合權限的情況下，才讓他進入準備要去的路由。",[99,662,663],{},"這其實跟 Middleware 有點類似，雖然可能沒有到百分之百一樣，但底層邏輯其實是非常相像的。",[99,665,666],{},"最終都是為了解決重複程式碼以及後續維護的成本，將驗證層進行收攏，把多處請求都需要做的共用前置處理，拉到同一個層面上，讓業務邏輯專注在業務邏輯之上。",[99,668,669],{},"其實像 Middleware 這個中介層，如果不去看它的名稱，單純從它在解決的底層邏輯來看，很多框架都有類似的流程攔截或前置處理機制，只是名稱、使用方式和實作細節不同。",[99,671,672],{},[105,673],{"alt":674,"src":675},"Vue Router Guard 與 Express Middleware 的流程攔截概念比較圖","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fexpress-middleware-vue-router-guard\u002F57fff0eac385193d.webp",[99,677,678],{},"補充說明：",[99,680,681],{},"我目前是一名非本科轉職的前端工程師，實務經驗約一年，近期正在慢慢往後端領域學習。Medium 上的文章多半是我在課程練習、實作過程與日常學習中，整理出的個人理解與技術筆記。",[99,683,684],{},"由於我仍在學習階段，內容可能有不夠完整或不夠精確的地方。如果有任何需要修正或補充的部分，歡迎大家友善交流，也謝謝願意指正與分享經驗的人。",{"title":245,"searchDepth":14,"depth":14,"links":686},[],"從前端路由守衛的角度，重新理解 Express Middleware：它不是單一套件，而是請求流程中的中介處理機制。",{},"\u002Fblog\u002F20260704-express-middleware-vue-router-guard","2026-07-04",{"title":637,"description":687},"express-middleware-vue-router-guard","blog\u002F20260704-express-middleware-vue-router-guard",[37,47,72],"f8x4SfcpTkuZiZs-SskQ9w77aUN-SKkwhwX68EGF7kU",{"id":697,"title":698,"author":89,"body":699,"category":252,"cover":253,"description":703,"extension":255,"featured":9,"meta":809,"navigation":257,"path":810,"publishedAt":811,"relatedTools":253,"seo":812,"slug":813,"status":262,"stem":814,"tags":815,"updatedAt":253,"__hash__":816},"articles\u002Fblog\u002F20260628-http-success-status-codes.md","關於後端回覆「請求成功」的狀態碼的使用時機整理",{"type":91,"value":700,"toc":807},[701,704,711,766,769,772,775,778,781,787,790,801,803,805],[99,702,703],{},"完成六角 Node.js 直播班 Day 11 CRUD 實作與資料驗證任務時，當日任務要求如下：",[99,705,706,707,710],{},"完成四條路由（前綴由 ",[159,708,709],{},"app.use('\u002Fmembers', ...)"," 提供）：",[522,712,713,723,740,754],{},[295,714,715,718,719],{},[159,716,717],{},"GET \u002F","：回傳所有會員，狀態碼 ",[720,721,722],"strong",{},"200",[295,724,725,728,729,732,733,736,737],{},[159,726,727],{},"POST \u002F","：必填欄位 ",[159,730,731],{},"name","，成功回傳 ",[720,734,735],{},"201","；欄位缺失回傳 ",[720,738,739],{},"400",[295,741,742,728,745,747,748,751,752],{},[159,743,744],{},"PUT \u002F:id",[159,746,731],{},"，找不到回傳 ",[720,749,750],{},"404","，欄位缺失回傳 ",[720,753,739],{},[295,755,756,759,760,763,764],{},[159,757,758],{},"DELETE \u002F:id","：成功回傳 ",[720,761,762],{},"204","；找不到回傳 ",[720,765,750],{},[99,767,768],{},"其中 status code 204 引起了我的興趣，在工作過程中針對成功的請求，其實我只看過200、201，雖然當時也不是很確定這兩個差異，但是至少是非常常見的！",[99,770,771],{},"不過 204 到底是甚麼？且只在 method DELETE 時回覆 204 ？",[99,773,774],{},"綜合以上，我詢問 GPT：",[99,776,777],{},"「在後端開發裡，一般 GET 的 status code 是 200，而 POST 則是 201，代表建立資料，然後 DELETE 則用 204 代表資料刪除嗎？」",[99,779,780],{},"而 GPT 的回覆我整理成表格後如下：",[99,782,783],{},[105,784],{"alt":785,"src":786},"HTTP GET、POST、PUT、PATCH 與 DELETE 常見成功狀態碼對照表","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fhttp-success-status-codes\u002F8047b567ebd7c497.webp",[99,788,789],{},"也就是說，200 與 204，並不是單靠 method 區分，關鍵區別是後端 response「有沒有回傳值」",[522,791,792,795,798],{},[295,793,794],{},"成功 && 有資料回應：200",[295,796,797],{},"成功 && 建立新資料：201",[295,799,800],{},"成功 && 沒有資料要回：204",[99,802,678],{},[99,804,681],{},[99,806,684],{},{"title":245,"searchDepth":14,"depth":14,"links":808},[],{},"\u002Fblog\u002F20260628-http-success-status-codes","2026-06-28",{"title":698,"description":703},"http-success-status-codes","blog\u002F20260628-http-success-status-codes",[57,12,72],"kfJP0G3nQ7pmiVivYPB5B2oonKecMOsfawC99W5YYzQ",{"id":818,"title":819,"author":89,"body":820,"category":970,"cover":253,"description":971,"extension":255,"featured":9,"meta":972,"navigation":257,"path":973,"publishedAt":974,"relatedTools":253,"seo":975,"slug":976,"status":262,"stem":977,"tags":978,"updatedAt":253,"__hash__":979},"articles\u002Fblog\u002F20260610-software-engineer-camp-2026-review.md","六角學院 2026 軟體工程師體驗營心得：從 Vue 回到 JavaScript 基礎",{"type":91,"value":821,"toc":962},[822,826,829,832,835,838,841,844,847,850,853,867,870,877,881,884,887,890,893,896,899,902,905,909,912,915,919,922,925,928,931,934,937,941,944,947,950,953,956],[275,823,825],{"id":824},"從框架回到底層我在-30-天軟體工程師體驗營中的學習反思","從框架回到底層：我在 30 天軟體工程師體驗營中的學習反思",[99,827,828],{},"身處在工具快速迭代的現在，最常感受到的壓力之一，是技術變化的速度。",[99,830,831],{},"每天都有新的工具、新的框架、新的開發模式出現。隔幾周AI就又更新了，即使已經進入前端工程師的職涯超過一年，也很容易在大量資訊中產生焦慮：是不是又有新的東西該學？是不是現在會的技術很快就不夠用了？是不是自己前進得還不夠快？",[99,833,834],{},"這也是我決定參加不斷進修的主要原因。",[99,836,837],{},"而參與「30 天軟體工程師體驗營」對我來說是希望透過一個相對輕量、但有明確節奏的學習安排，讓自己重新校準目前的學習方向，並確認自己仍然持續在累積、在前進。",[275,839,840],{"id":840},"一場用來降低資訊焦慮的學習節點",[99,842,843],{},"我目前的工作主要使用 Vue進行開發，平常已經習慣元件化、響應式資料綁定。",[99,845,846],{},"也因為如此，體驗營對我來說最有價值的地方，不是「學到一個全新的技術」，而是讓我有機會重新回到 HTML、CSS與 JavaScript的原生基礎。",[99,848,849],{},"在 Vue裡，很多事情其實已經被框架封裝好了。",[99,851,852],{},"例如：",[522,854,855,858,861,864],{},[295,856,857],{},"畫面如何根據資料更新",[295,859,860],{},"如何透過迴圈渲染清單",[295,862,863],{},"使用者操作後如何改變狀態",[295,865,866],{},"元件之間如何拆分畫面與邏輯",[99,868,869],{},"這些事情在日常工作中很直覺，但當我回到原生 JavaScript時，就必須重新思考：「如果沒有框架幫我處理，我要怎麼用JS完成這件事？」",[99,871,872,873,876],{},"例如，如果不用 ",[159,874,875],{},"v-for","，我要如何用 JavaScript產生重複的畫面結構？如果沒有框架自動幫我處理資料更新，我要怎麼操作 DOM、綁定事件、更新畫面？",[275,878,880],{"id":879},"真正的挑戰從框架思維切回原生邏輯","真正的挑戰：從框架思維切回原生邏輯",[99,882,883],{},"這次主線任務對我來說不是完全無法理解，但難度主要來自於思維切換。",[99,885,886],{},"平常工作使用 Vue時，我會自然地從「資料狀態」與「元件結構」去思考畫面。但在體驗營任務中，當需要使用 HTML、CSS與 JavaScript完成畫面與互動時，就會更直接面對底層實作細節。",[99,888,889],{},"這讓我意識到，自己雖然已經能在工作中完成前端功能，但如果想讓技術能力更扎實，就不能只停留在「會使用框架」這個層級。",[99,891,892],{},"真正穩定的工程能力，應該包含兩個面向：",[99,894,895],{},"第一，是能善用框架提升開發效率。",[99,897,898],{},"第二，是理解框架背後到底幫我們處理了什麼。",[99,900,901],{},"這次體驗營剛好讓我重新直面第二個面向。",[99,903,904],{},"在最終作業中，我透過跟 Codex討論、拆解怎麼使用JS達到元件的效果，練習用原生完成替換內容區塊邏輯。",[275,906,908],{"id":907},"在職學習不只是追技術而是建立可持續前進的節奏","在職學習不只是追技術，而是建立可持續前進的節奏",[99,910,911],{},"整體來說，我覺得六角學院很適合不同階段的學習者。無論是剛開始接觸程式的新手，還是已經在工作中使用前端技術、但想重新補強基礎的人，都可以在這裡找到適合自己的節奏。",[99,913,914],{},"因為學習軟體開發本身已經需要長期投入，如果課程設計能讓人「不被焦慮推著跑」，而是能以穩定、可持續的方式前進，那就會大幅降低中途放棄的機率。",[275,916,918],{"id":917},"每一張證書都是在職學習的累積證明","每一張證書，都是在職學習的累積證明",[99,920,921],{},"這次填寫回饋表單時，我也提出了一個小建議：希望未來個人頁面可以有一個「證書總覽」區塊，讓學員可以直接看到自己歷來完成的課程與取得的證書。",[99,923,924],{},"這個功能看起來像是系統優化，但對我來說，它背後其實有更深一層的意義。",[99,926,927],{},"在職學習並不容易。",[99,929,930],{},"很多課程、任務與作品，都是在下班後、週末，或是精神狀態並不完美的時候，一點一點擠出時間完成的。當學得很累、覺得自己好像沒有進步時，如果能回頭看到自己曾經完成過的課程與證書，那會是一種很實際的回饋。",[99,932,933],{},"校長提到過他有一個HP資料夾，裡面是不同學員的心得回饋，其實我之前不太理解為甚麼這樣可達到回血的效果，但這次在瀏覽過去上的直播課所得到的每一個證書，它像是一份學習軌跡的總覽提醒自己：我不是沒有前進，我只是每天前進得很小步，當下確實感覺都像是在原地踏步。",[99,935,936],{},"但這些小步，最後都會留下痕跡，而證書總覽，就是在疲憊時幫自己「回血」的區塊，提醒自己我已經累計很多，而且有個地方幫我記著我的進步。",[275,938,940],{"id":939},"結語穩定前進比焦慮追趕更重要","結語：穩定前進，比焦慮追趕更重要",[99,942,943],{},"學習軟體工程，不一定要一直追逐最新、最快、最熱門的東西。",[99,945,946],{},"有時候，回到基礎，重新理解自己每天使用的工具背後發生了什麼，反而能讓能力變得更穩。",[99,948,949],{},"對已經在職場中的我來說，這次體驗營像是一個階段性的校準點。它讓我在資訊焦慮中重新找到節奏，也提醒我：真正長期有效的學習，不是靠短暫衝刺，而是能持續累積。",[99,951,952],{},"未來我仍然會繼續學習新的工具與技術，但我也會提醒自己，不需要被焦慮推著跑。",[99,954,955],{},"只要持續理解、持續實作、持續回頭檢視自己的學習軌跡，我就一直在往前走。",[99,957,958],{},[105,959],{"alt":960,"src":961},"30 天軟體工程師體驗營的學習反思重點插圖","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fsoftware-engineer-camp-2026-review\u002Ffa2c6608aede4119.webp",{"title":245,"searchDepth":14,"depth":14,"links":963},[964,965,966,967,968,969],{"id":824,"depth":14,"text":825},{"id":840,"depth":14,"text":840},{"id":879,"depth":14,"text":880},{"id":907,"depth":14,"text":908},{"id":917,"depth":14,"text":918},{"id":939,"depth":14,"text":940},"career-learning","從 Vue 開發經驗出發，重新練習 HTML、CSS 與原生 JavaScript，反思框架、底層邏輯與在職學習節奏。",{},"\u002Fblog\u002F20260610-software-engineer-camp-2026-review","2026-06-10",{"title":819,"description":971},"software-engineer-camp-2026-review","blog\u002F20260610-software-engineer-camp-2026-review",[42,62,67,27,52],"cDyUGj022tBhGxrKtcc0xf3wkf2TO__I8J09GnHm1tI",{"id":981,"title":982,"author":89,"body":983,"category":252,"cover":253,"description":1154,"extension":255,"featured":9,"meta":1155,"navigation":257,"path":1156,"publishedAt":1157,"relatedTools":253,"seo":1158,"slug":1159,"status":262,"stem":1160,"tags":1161,"updatedAt":253,"__hash__":1162},"articles\u002Fblog\u002F20260513-javascript-backend-course-review.md","六角學院 - 【後端】JavaScript 直播班心得與覆盤",{"type":91,"value":984,"toc":1147},[985,989,1008,1012,1019,1026,1029,1044,1047,1051,1062,1065,1069,1072,1083,1086,1095,1098,1107,1110,1119,1129,1133,1136,1139,1145],[275,986,988],{"id":987},"_1-報名初衷為後端與雲端佈局","1. 報名初衷：為後端與雲端佈局",[99,990,991,992,995,996,999,1000,1003,1004,1007],{},"身為一名習慣 ",[720,993,994],{},"Vue 3"," 與現代 ",[720,997,998],{},"JS"," 語法的開發者，其實我瞄準的是六月的 ",[720,1001,1002],{},"Node.js"," 跟之後的 ",[720,1005,1006],{},"AWS"," 雲端部，因為預計在明年轉職成為後端工程師（Backend Engineer），所以打算多多培養全端（Full-stack）思維。",[275,1009,1011],{"id":1010},"_2-kata-刷題的反思","2. Kata 刷題的反思",[99,1013,1014,1015,1018],{},"學習過程中，最有趣的莫過於每日任務的 ",[720,1016,1017],{},"Kata"," 刷題。我原本預期難度會跟每日任務一樣一點一點深入變難，結果中途遇到一題「求三角形另一角的度數」。",[99,1020,1021,1022,1025],{},"當時的我：用一分鐘打完程式後，盯著螢幕 10 分鐘，不斷懷疑自己「真的只有這樣嗎？」、「是不是有陷阱？」結果按下 ",[720,1023,1024],{},"ATTEMPT"," 秒過後，真的讓我哭笑不得。",[99,1027,1028],{},"另一次深刻的反思是「過度工程」（Over-engineering）。有一題要求回傳陣列內最大的兩個數，我當下腦袋卡住，花了半小時寫迴圈（Loop）去比較、蒐集。後來才突然驚覺：",[494,1030,1031],{},[99,1032,1033],{},[499,1034,1035,1036,1039,1040,1043],{},"只要先用 ",[720,1037,1038],{},"Set"," 去重（De-duplicate），再用 ",[720,1041,1042],{},"sort()"," 排序後取前兩位不就好了嗎？",[99,1045,1046],{},"那一瞬間，我真的很難理解半小時前的自己大腦是不是當機了。",[275,1048,1050],{"id":1049},"_3-fetch-api-的衝擊","3. Fetch API 的衝擊",[99,1052,1053,1054,1057,1058,1061],{},"在工作上習慣了 ",[720,1055,1056],{},"Axios"," 的便利，這次課程中重新操作原生的 ",[720,1059,1060],{},"Fetch","，真的有種「返璞歸真」的衝擊感。雖然原生語法寫起來比較繁瑣（心裡默默吶喊：這啥？##），但讓我也經歷了一場「技術記憶大復甦」。",[99,1063,1064],{},"從一開始的「這是什麼新套件？」到後來的：「靠，對欸！資策會剛學程式時有學過！」。這種從便利回歸原始的過程，雖然寫得很苦，但也讓我對於目前所有套件的開發者充滿敬畏，因為他們真的讓現在的開發變得簡單很多很多。",[275,1066,1068],{"id":1067},"_4-優雅的寫法跟課程需要的古老寫法","4. 優雅的寫法跟課程需要的古老寫法(?)",[99,1070,1071],{},"在工作上我一般習慣使用箭頭函式（Arrow Function），因為覺得他寫起來很美，既優雅又簡潔～",[347,1073,1077],{"className":1074,"code":1075,"language":1076,"meta":245,"style":245},"language-javascript shiki shiki-themes github-light github-dark","const a = b => b++\n","javascript",[159,1078,1079],{"__ignoreMap":245},[355,1080,1081],{"class":357,"line":8},[355,1082,1075],{},[99,1084,1085],{},"如果使用一般寫法就是：",[347,1087,1089],{"className":1074,"code":1088,"language":1076,"meta":245,"style":245},"function a(b) { return b++; }\n",[159,1090,1091],{"__ignoreMap":245},[355,1092,1093],{"class":357,"line":8},[355,1094,1088],{},[99,1096,1097],{},"還有操作陣列的回調函式（Callback Function），明明可以：",[347,1099,1101],{"className":1074,"code":1100,"language":1076,"meta":245,"style":245},"arr.map(a => a.uuid)\n",[159,1102,1103],{"__ignoreMap":245},[355,1104,1105],{"class":357,"line":8},[355,1106,1100],{},[99,1108,1109],{},"但就要變成：",[347,1111,1113],{"className":1074,"code":1112,"language":1076,"meta":245,"style":245},"arr.map(function (a) { return a.uuid })\n",[159,1114,1115],{"__ignoreMap":245},[355,1116,1117],{"class":357,"line":8},[355,1118,1112],{},[99,1120,1121,1122,1125,1126,1128],{},"這次的後端新手小遊戲，有些題目好像會根據是否有 ",[159,1123,1124],{},"function"," 判斷回答是否正確。習慣了箭頭函式的簡潔優雅後，回去寫傳統語法真的寫得很苦 QQ。每一行多出來的 ",[159,1127,1124],{}," 和花括號對我來說都像是多餘的雜訊。但這也強迫我重新適應不同的代碼規範（Code Style），練習在不同的開發語境下切換自如，算是在痛苦中的一種意外收穫。",[275,1130,1132],{"id":1131},"_5-覆盤","5. 覆盤",[99,1134,1135],{},"這一次透過刷題跟每日，我自己非常有感的是對陣列（Array）操作的直覺變得更敏銳了。對我來說，學習是一場馬拉松，我享受這種每天一點點的過程。",[99,1137,1138],{},"無論你是從資策會轉職，還是正在挑戰新的技術，不要被眼前的繁瑣語法擊倒。學習是一個不斷「解壓縮」與「重啟」的過程。只要還在這條路上，最後會發現那些當初看得一頭霧水的東西，最後都會變成你實力的一部分。",[99,1140,1141],{},[105,1142],{"alt":1143,"src":1144},"六角學院 JavaScript 直播班心得與覆盤插圖","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fjavascript-backend-course-review\u002F7b8ca123f9c2d65e.webp",[609,1146,611],{},{"title":245,"searchDepth":14,"depth":14,"links":1148},[1149,1150,1151,1152,1153],{"id":987,"depth":14,"text":988},{"id":1010,"depth":14,"text":1011},{"id":1049,"depth":14,"text":1050},{"id":1067,"depth":14,"text":1068},{"id":1131,"depth":14,"text":1132},"身為一名習慣 Vue 3 與現代 JS 語法的開發者，其實我瞄準的是六月的 Node.js 跟之後的 AWS 雲端部，因為預計在明年轉職成為後端工程師（Backend Engineer），所以打算多多培養全端（Full-stack）思維。",{},"\u002Fblog\u002F20260513-javascript-backend-course-review","2026-05-13",{"title":982,"description":1154},"javascript-backend-course-review","blog\u002F20260513-javascript-backend-course-review",[62,27,52,17],"Le-8Nr9TetaKNMrZ7V5JuUOWlrHFA8QIIhQW4EoX1Y0",{"id":1164,"title":1165,"author":89,"body":1166,"category":970,"cover":253,"description":1174,"extension":255,"featured":9,"meta":1341,"navigation":257,"path":1342,"publishedAt":1343,"relatedTools":253,"seo":1344,"slug":1345,"status":262,"stem":1346,"tags":1347,"updatedAt":253,"__hash__":1348},"articles\u002Fblog\u002F20260208-career-change-first-year-reflection.md","《慢慢成長才是比較快的：寫給轉職工程師一周年的自己，那首意外解鎖的傳承之歌》",{"type":91,"value":1167,"toc":1335},[1168,1172,1175,1184,1187,1191,1198,1205,1208,1215,1221,1224,1227,1230,1233,1236,1240,1245,1251,1257,1260,1263,1266,1269,1276,1279,1283,1286,1289,1294,1297,1304,1307,1313,1319,1325],[275,1169,1171],{"id":1170},"一場手殘帶來的重開機","一場「手殘」帶來的重開機",[99,1173,1174],{},"起因是一件令人哭笑不得的意外。",[99,1176,1177,1178,1183],{},"我參加了六角學院的後端體驗營，這次的每日任務是校長花了一個月「肝」出來的遊戲",[571,1179,1182],{"href":1180,"rel":1181},"https:\u002F\u002Fhexschool.github.io\u002Fbackend-camp-game\u002F",[575],"《新人後端生存指南》","，用十個關卡串聯起前後端的基礎知識。就在我準備截圖最後的通關紀錄時，因為一個手殘動作，我竟然把所有存檔清空了 QQ。（但是校長居然沒有防呆 #不是在毀滅性操作的按鈕要加入提示嗎 QQ）",[99,1185,1186],{},"當下看著進度成就消失，我腦中一片空白。已經是週六晚上 11 點了，我只想趕快截圖，回報心得牆，然後關電腦洗澡睡覺，接著明天繼續當社畜。那一刻，我心裡浮現一個念頭：「好吧，那就快速跑一遍吧。」 沒想到，這次重新通關，竟然讓我意外解鎖了隱藏的完美結局，以及彩蛋結局「傳承之路」。",[275,1188,1190],{"id":1189},"凌晨三點的歌詞與一年前的自己重疊","凌晨三點的歌詞，與一年前的自己重疊",[99,1192,1193,1194,1197],{},"在傳承之路中，",[720,1195,1196],{},"《給未來的你.mp4》"," 背景音樂緩緩響起。起初我正專注地看著劇情，只覺得旋律柔和，直到歌詞中跳出校長名言：",[494,1199,1200],{},[99,1201,1202],{},[720,1203,1204],{},"「不用一開始就很厲害，但要開始才會很厲害」",[99,1206,1207],{},"我突然意識到，這首歌居然是校長為了遊戲做的嗎？我開始很認真地聽，在我聽到：",[494,1209,1210],{},[99,1211,1212],{},[720,1213,1214],{},"「慢慢成長才是比較快的⋯⋯人生就像一場馬拉松，我們高估了一年能做的，卻低估了二三十年後自己能走多遠」",[99,1216,1217],{},[105,1218],{"alt":1219,"src":1220},"《給未來的你》影片畫面：人生像馬拉松，別低估長期成長","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fcareer-change-first-year-reflection\u002F338939fd20e16b88.webp",[99,1222,1223],{},"那一瞬間，我的眼眶瞬間就紅了。這句歌詞像是一把鑰匙，打開了我這一年來一直壓抑著的，名為「內耗」的盒子。",[99,1225,1226],{},"回想一年前，我剛從資策會 Java 班畢業，帶著僅有的四個月後端經驗，卻意外踏入了 Vue 前端的世界。",[99,1228,1229],{},"我還記得面試前那限時三天的極限挑戰，那是我第一次使用 Vue 和 Tailwind CSS，所做的東西卻是要用於面試測試。",[99,1231,1232],{},"雖然當時心態上想著「我寫程式才四個月，而且主要學後端，基本上這次面試是無望的，就當作學經驗、跟面試官聊聊」，但實際上卻也是拼命到了凌晨三點，才交出一份自己問心無愧的作業。",[99,1234,1235],{},"後來也順利地 Get offer，成為我的第一份工程師工作。",[275,1237,1239],{"id":1238},"狂做別想背後的絕望與熱愛","「狂做，別想」背後的絕望與熱愛",[99,1241,1242],{},[720,1243,1244],{},"入職後，真正的考驗才開始。",[99,1246,1247,1248],{},"當我剛學會跟冒牌者症候群共處時，迎來第一個獨自切版的畫面。看著那張現在看來其實很簡單的設計稿，當下卻完全不知道如何開始。那種無從下手的無力感，讓我陷入極深的自我懷疑：",[720,1249,1250],{},"「我是不是真的不適合當工程師？」",[99,1252,1253,1254],{},"為了不讓自己退縮，我在心裡一遍又一遍喊著：",[720,1255,1256],{},"「狂做，別想。」",[99,1258,1259],{},"我連假日都在焦慮，只要發現大腦想逃避，就強迫自己埋頭硬幹。好不容易完成畫面、串接完 API 讓專案順利上線，原以為能鬆一口氣，沒想到卻是另一場無止盡的內耗。",[99,1261,1262],{},"我反覆檢討自己：「為什麼切版這麼慢？到底卡在哪？」我把自己關進了「不夠好」的牢籠裡，覺得這是既定事實。",[99,1264,1265],{},"弔詭的是，我明明在研究 API 串接、優化資料傳遞效率時感到無比熱愛與投入，但只要一回到切版畫面，我就會回想起「不知如何開始」的那一次。 不管走得多遠，我依然只看見自己不足的那 1%。",[99,1267,1268],{},"歌詞裡說：",[494,1270,1271],{},[99,1272,1273],{},[720,1274,1275],{},"「明明走了很遠，卻只看見那一分」",[99,1277,1278],{},"真的完全寫中了我的心聲。",[275,1280,1282],{"id":1281},"定義我的穩定版本v10-線上版","定義我的穩定版本：v1.0 線上版",[99,1284,1285],{},"這首歌的所有歌詞，跟我過去這一年來的每個節點完美重疊。",[99,1287,1288],{},"聽著歌流完淚後，我發現自己雖然還沒感覺到所謂的「得心應手」，也還沒等到我的天亮，但我終於很認真地正視一件事：",[99,1290,1291],{},[720,1292,1293],{},"回首我的起點，我已經跑了很遠了。",[99,1295,1296],{},"24 年那個非本科系也從沒寫過程式，連網路通訊都不明白的我，24 年底從 Java 入門，到現在能撐過陌生框架挑戰、獨立優化 API 請求、跟後端討論資料流的前端工程師。",[99,1298,1299,1300,1303],{},"我不再只是開發測試版本的工程師，我決定定義現在的自己為 ",[720,1301,1302],{},"v1.0 線上版","。雖然一定還會持續優化、還會有 Bug 需要修補，但我已經「上線」了，我已經站在賽道上跑著。",[99,1305,1306],{},"謝謝那個手殘的瞬間，讓我有機會在重跑一遍關卡，也重跑一遍這一年的心路歷程。",[99,1308,1309,1312],{},[720,1310,1311],{},"慢慢成長才是比較快的。"," 給那個還在努力的自己，也給所有在人生馬拉松賽道上的你們。",[99,1314,1315,1316],{},"如果現在的你也覺得自己「跑得慢」，或許我們都該回頭看看自己的起點。",[720,1317,1318],{},"其實我們都已經往前走了很遠。",[99,1320,1321],{},[105,1322],{"alt":1323,"src":1324},"致後端新人的一句話：你不用一開始就很厲害，但要開始才會很厲害","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fcareer-change-first-year-reflection\u002F7394eac49425329c.webp",[99,1326,1327,1330,1331],{},[720,1328,1329],{},"完整歌詞："," ",[571,1332,1334],{"href":1333},"\u002Fblog\u002Fmessage-to-future-backend-camp-lyrics","《給未來的你》─六角學院2026後端工程師體驗營 新人後端生存指南彩蛋",{"title":245,"searchDepth":14,"depth":14,"links":1336},[1337,1338,1339,1340],{"id":1170,"depth":14,"text":1171},{"id":1189,"depth":14,"text":1190},{"id":1238,"depth":14,"text":1239},{"id":1281,"depth":14,"text":1282},{},"\u002Fblog\u002F20260208-career-change-first-year-reflection","2026-02-08",{"title":1165,"description":1174},"career-change-first-year-reflection","blog\u002F20260208-career-change-first-year-reflection",[17,67,52],"PN6vdCZKfWwycCi-Gvvp3LcxI5BWmtCl5Fo1I55gOl4",{"id":1350,"title":1334,"author":89,"body":1351,"category":970,"cover":253,"description":1491,"extension":255,"featured":9,"meta":1492,"navigation":257,"path":1493,"publishedAt":1343,"relatedTools":253,"seo":1494,"slug":1495,"status":262,"stem":1496,"tags":1497,"updatedAt":253,"__hash__":1498},"articles\u002Fblog\u002F20260208-message-to-future-backend-camp-lyrics.md",{"type":91,"value":1352,"toc":1489},[1353,1358,1361,1364,1367,1370,1373,1376,1379,1382,1385,1388,1391,1394,1397,1400,1403,1406,1409,1412,1415,1418,1421,1423,1425,1427,1430,1433,1436,1439,1442,1445,1447,1450,1453,1456,1459,1462,1465,1468,1471,1482],[99,1354,1355],{},[105,1356],{"alt":1219,"src":1357},"https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fmessage-to-future-backend-camp-lyrics\u002Fd347d9cac5c2da24.webp",[99,1359,1360],{},"螢幕亮著凌晨三點",[99,1362,1363],{},"我還在追趕看不見的終點",[99,1365,1366],{},"33 歲才開始會不會太晚",[99,1368,1369],{},"每一行程式碼都寫滿不安",[99,1371,1372],{},"他說別急先深呼吸",[99,1374,1375],{},"你的肩膀又內旋了",[99,1377,1378],{},"放下鍵盤去喝杯水",[99,1380,1381],{},"bug可以明天修",[99,1383,1384],{},"慢慢成長才是比較快的",[99,1386,1387],{},"不用一開始就很厲害",[99,1389,1390],{},"但要開始才會很厲害",[99,1392,1393],{},"休息不是偷懶",[99,1395,1396],{},"是為了走更長的路",[99,1398,1399],{},"掙扎這一分那一分 在我眼中一樣",[99,1401,1402],{},"那個聲音說你還不夠好",[99,1404,1405],{},"把自己封印在不夠好的牢籠",[99,1407,1408],{},"明明走了很遠 卻只看見那一分",[99,1410,1411],{},"他說停下看看自己",[99,1413,1414],{},"你已經做到了 專案上線了",[99,1416,1417],{},"那些拼了命想證明的",[99,1419,1420],{},"其實沒有人在乎",[99,1422,1384],{},[99,1424,1387],{},[99,1426,1390],{},[99,1428,1429],{},"程式碼可以重寫",[99,1431,1432],{},"但身體壞了就很難復原",[99,1434,1435],{},"人的一生就像馬拉松",[99,1437,1438],{},"我們高估一年能做的事",[99,1440,1441],{},"卻低估了二三十年後",[99,1443,1444],{},"自己能走多遠",[99,1446,1384],{},[99,1448,1449],{},"只要你不放棄自己",[99,1451,1452],{},"我也不會放棄你",[99,1454,1455],{},"加油我會等你的",[99,1457,1458],{},"等你準備好了",[99,1460,1461],{},"我們再一起努力",[99,1463,1464],{},"謝謝你海姐",[99,1466,1467],{},"陽光照進來了",[99,1469,1470],{},"┄ ┄ ┄ ┄ ┄ ┄",[99,1472,1473,1474,1477,1478,1481],{},"歌詞為參與 ",[720,1475,1476],{},"六角學院 2026 後端工程師體驗營"," 過程中，反覆聆聽校長「肝」的每日任務遊戲",[571,1479,1182],{"href":1180,"rel":1480},[575],"彩蛋結局所整理出來的「空耳版本」。",[99,1483,1484,1485,1488],{},"其中「",[720,1486,1487],{},"掙扎這一分那一分","」這段，不太確定正確歌詞，歡迎大家一起交流，把這份校長給新人的溫暖指南補充完整。",{"title":245,"searchDepth":14,"depth":14,"links":1490},[],"歌詞為參與六角學院 2026 後端工程師體驗營過程中，反覆聆聽校長「肝」的每日任務遊戲《新人後端生存指南》彩蛋結局所整理出來的「空耳版本」。",{},"\u002Fblog\u002F20260208-message-to-future-backend-camp-lyrics",{"title":1334,"description":1491},"message-to-future-backend-camp-lyrics","blog\u002F20260208-message-to-future-backend-camp-lyrics",[67,52],"OO1SEp4QJ3p1kgn9Av1WLVEAm8r9WAb8etdxxxJOgOQ",[1500,1504,1507],{"title":1501,"slug":1502,"description":1503,"order":8,"indexable":9},"實驗紀錄","experiments","生活、工作與學習中的觀察與方法。",{"title":1505,"slug":252,"description":1506,"order":14,"indexable":9},"後端開發","後端技術、API、資料庫與服務部署的學習與實作紀錄。",{"title":1508,"slug":970,"description":1509,"order":19,"indexable":9},"職涯進修","跟工作相關持續學習的經驗整理。",1795182586072]