[{"data":1,"prerenderedAt":1012},["ShallowReactive",2],{"article-category-labels":3,"article-category-items-backend-development":20,"tag-labels":952},[4,10,15],{"title":5,"slug":6,"description":7,"order":8,"indexable":9},"實驗紀錄","experiments","生活、工作與學習中的觀察與方法。",1,false,{"title":11,"slug":12,"description":13,"order":14,"indexable":9},"後端開發","backend-development","後端技術、API、資料庫與服務部署的學習與實作紀錄。",2,{"title":16,"slug":17,"description":18,"order":19,"indexable":9},"職涯進修","career-learning","跟工作相關持續學習的經驗整理。",3,[21,204,581,644,767],{"id":22,"title":23,"author":24,"body":25,"category":12,"cover":187,"description":188,"extension":189,"featured":9,"meta":190,"navigation":191,"path":192,"publishedAt":193,"relatedTools":187,"seo":194,"slug":195,"status":196,"stem":197,"tags":198,"updatedAt":187,"__hash__":203},"articles\u002Fblog\u002F20260902-nodejs-course-review.md","六角學院【後端】Node.js 直播班心得：從作業、最終專案到部署踩坑覆盤","jessie",{"type":26,"value":27,"toc":179},"minimark",[28,33,37,44,47,50,53,56,59,62,65,68,71,74,77,80,84,87,90,106,112,123,129,133,136,139,142,145,148,151,154,158,161,164,167,170,173],[29,30,32],"h3",{"id":31},"針對-js-直播班的覆盤在-nodejs-真的做到了","針對 JS 直播班的覆盤，在 Node.js 真的做到了",[34,35,36],"p",{},"在報到任務時，我曾經許下這個心願：",[34,38,39],{},[40,41],"img",{"alt":42,"src":43},"作者在課程 Discord 分享希望每週按時完成 Node.js 作業的目標","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fnodejs-course-review\u002Fb726ce3837ed6e64.webp",[34,45,46],{},"當時收到大家的按讚，通知一直跳出來，也像是在不斷提醒自己曾經許下的目標。",[34,48,49],{},"而這一次，撇除八月份工作上的變動，讓生活稍微混亂了一些之外，前七週的作業和每日任務，我確實都有按時完成～",[34,51,52],{},"一方面覺得自己真的很厲害，另一方面也讓我感受到什麼叫做「慢慢進步」。當進度不再一直累積，遇到不懂的地方時，能有時間查找資料，甚至進一步延伸學習。",[34,54,55],{},"經過這次每天都完成的過程中，我也慢慢有了「餘裕」，不再像上一次參加 JS 直播班時，被截止日期追著跑，最後只能想辦法趕快「完成」。",[34,57,58],{},"這一次，不只是完成作業，體會到校長說的希望為生活留「餘裕」。",[29,60,61],{"id":61},"做完後終於了解每一堂課程在後端專案中的位置的最終作業",[34,63,64],{},"這次的最終作業真的好難啊！",[34,66,67],{},"最大的難點是要從零開始建立後端。一開始真的完全不知道該從哪裡下手，還好有助教直播可以跟著做。初始環境、M1 和 M2 都是跟著直播一步一步建立起來的； M3～M6，則是自己半拚半湊完成。",[34,69,70],{},"遇到卡關時，先回去看課程直播回放，再對照助教直播的實作方式。如果還是改不動，才會找 AI 。等到功能完成、測試通過後，再回頭慢慢整理與調整程式碼。",[34,72,73],{},"第二個難點是建立資料表之間的關聯，尤其是多對多關聯。像是教練與技能的關聯，以及課程預約相關的資料表，我光是這兩個部分就卡了整整一天。",[34,75,76],{},"在建立關聯和查詢資料的過程中，常常會被外鍵、關聯方向和回傳資料的結構繞進去。雖然處理的過程很痛苦，但實際走過一次後，對資料表之間如何互相連結，以及 TypeORM 如何取得關聯資料，也比原本清楚了許多。",[34,78,79],{},"在每周直播課，以及完成當周作業都感覺一個區塊一個區塊都很好懂，但實際開始做最終作業時，發現真的無處下手，在完成最終作業的過程中，也把整期 Node.js 的課程都串連起來了！",[29,81,83],{"id":82},"兩門課程的連動利用-cloudflare-r2-完成加分題","兩門課程的連動，利用 Cloudflare R2 完成加分題",[34,85,86],{},"在完成 M0～M6 的作業要求後，我先將作業繳交，再回頭研究加分題。之前只大致看到加分題要求上傳圖片，仔細閱讀後才發現，還需要將圖片上傳至雲端儲存服務，並回傳可以直接開啟檢視的 URL。",[34,88,89],{},"這時我想到 8 月初 AI 開發進化營介紹 Cloudflare 的加碼課程中，曾經提到 R2，因此決定使用 Cloudflare R2 完成圖片上傳功能。",[34,91,92,93,97,98,101,102,105],{},"實作過程中，卡比較久的地方是在 Docker 與 GitHub Actions 的環境變數設定。我原本在 ",[94,95,96],"code",{},"docker-compose.yml"," 中指定載入 ",[94,99,100],{},"backend\u002F.env","，但 ",[94,103,104],{},".env"," 不會上傳到 Git，因此 GitHub Actions 執行 Docker Compose 時，會因為找不到該檔案而無法啟動服務。",[34,107,108,109,111],{},"後來我將 ",[94,110,100],{}," 改成選用設定：本機存在時就載入，GitHub Actions 中不存在時則略過。",[34,113,114,115,118,119,122],{},"不過修正後仍然無法啟動，原因是上傳圖片的 controller 在模組載入階段，就立即透過 ",[94,116,117],{},"config.get()"," 讀取 R2 環境變數。GitHub Actions 沒有設定 R2，因此讀到 ",[94,120,121],{},"undefined"," 並拋出錯誤，導致整個後端在 healthcheck 前就停止。",[34,124,125,126,128],{},"最後，我將 R2 設定改成只有在實際呼叫圖片上傳 API 時才讀取。如此一來，即使 GitHub Actions 沒有 R2 環境變數，其他 M0～M6 功能與 healthcheck 仍能正常啟動；本機有提供 ",[94,127,100],{}," 時，上傳功能也可以正常使用，最後終於成功啦！",[29,130,132],{"id":131},"終於被幸運之神眷顧卻差點錯過","終於被幸運之神眷顧，卻差點錯過",[34,134,135],{},"這次完成預習任務後的抽書活動，我居然抽中了！但我本人完全不知道 XD",[34,137,138],{},"直到壓線繳交完最終任務、準備回頭做加分題時，我去看直播回放才發現自己中獎了 XDD 嚇得我趕緊截圖詢問校長，確認現在是否還能領取。真的很感謝校長最後還是讓我領書～",[34,140,141],{},"在 00:51 收到校長的回覆，那一刻感受到校長一直說「自己住在 Discord 上」原來是真的 XDD",[34,143,144],{},"回想 2025 年的軟體工程師體驗營，那一期校長真的是大放送！只要完成每日任務就可以參加抽書，一天一本，每週都會抽出 5本，有時候校長上課還會額外加碼抽到10 本。",[34,146,147],{},"當時我還想說：「感覺中獎機會很大耶！」結果一次都沒有抽到過 QQ",[34,149,150],{},"從那之後，我對抽書這件事就不會過度關注了 XDDD",[34,152,153],{},"沒想到啊，沒想到！這次幸運之神居然真的眷顧我了 XDDDD 而且在我差點錯過的情況下！",[29,155,157],{"id":156},"也想感受到累積的力量","也想感受到「累積」的力量",[34,159,160],{},"這次看校長在會後的產品實驗室中，分享 ToolNeko 的成長紀錄。雖然我知道產品實驗室的主題是期待清單，但 ToolNeko 的故事反而更吸引我 XD",[34,162,163],{},"其實在 Node.js 開課前，我也曾經想過要做一個工具網站，主要是想把自己平常會用到的工具整理起來，以後就不用每次都到處搜刮～",[34,165,166],{},"不過，我從來沒有想過，原來當網站慢慢累積出流量後，還可以進一步投放廣告。聽到這件事時，真的有種新世界突然被打開的感覺 XDD",[34,168,169],{},"另外，我也參加了卡斯柏老師的 AI 開發進化營。看到老師的部落格是自己開發的網站，也覺得非常酷 XDD",[34,171,172],{},"目前我已經先買好網域了！下一個目標是：等到參加 AWS 雲端架構部署課程時，直接用自己的網站來繳交心得牆作業。希望到了那個時候，我也能開始真正感受到持續「累積」帶來的成果 XD",[34,174,175],{},[40,176],{"alt":177,"src":178},"六角學院 Node.js 直播班心得與覆盤插圖","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fnodejs-course-review\u002F90c584887f318a9d.webp",{"title":180,"searchDepth":14,"depth":14,"links":181},"",[182,183,184,185,186],{"id":31,"depth":19,"text":32},{"id":61,"depth":19,"text":61},{"id":82,"depth":19,"text":83},{"id":131,"depth":19,"text":132},{"id":156,"depth":19,"text":157},null,"從每週作業、資料表關聯到 Cloudflare R2 與 GitHub Actions，重新走完整個後端專案，也開始感受到「累積」的力量。","md",{},true,"\u002Fblog\u002F20260902-nodejs-course-review","2026-09-02",{"title":23,"description":188},"nodejs-course-review","published","blog\u002F20260902-nodejs-course-review",[199,200,201,202],"nodejs-backend","cloud-deployment","course-review","hexschool","_5aDBShvNGrTjZafZHpQ1QUpAI1AELejaLlwTeWLjhw",{"id":205,"title":206,"author":24,"body":207,"category":12,"cover":187,"description":211,"extension":189,"featured":9,"meta":570,"navigation":191,"path":571,"publishedAt":572,"relatedTools":187,"seo":573,"slug":574,"status":196,"stem":575,"tags":576,"updatedAt":187,"__hash__":580},"articles\u002Fblog\u002F20260802-postgresql-index-explain-analyze.md","PostgreSQL 學習筆記：認識資料庫索引與 EXPLAIN ANALYZE",{"type":26,"value":208,"toc":555},[209,212,217,220,223,226,229,239,243,266,270,273,279,284,321,328,375,378,381,396,433,436,445,451,457,461,464,479,482,486,489,496,503,506,522,526,529,532,535,542,545,551],[34,210,211],{},"本篇為六角學院2026年node.js直播班中，關於資料庫索引的學習筆記整理，課中使用的資料庫為PostgreSQL，筆記內容來自課程、PostgreSQL官方文件整合而來。",[213,214,216],"h2",{"id":215},"索引是甚麼","索引是甚麼?",[34,218,219],{},"相當於一本書的目錄，記錄某章節在第幾頁。",[34,221,222],{},"下過索引後，資料庫在進行該索引條件的搜尋時，只需要找到該條件在索引中對應的資料庫位置，直接到那個位置拿資料即可。不用看跟條件不相關的資料，以此減少搜尋的時間。",[213,224,225],{"id":225},"建立索引",[213,227,228],{"id":228},"建立的重點",[230,231,232,236],"ol",{},[233,234,235],"li",{},"優先替經常查詢，且能有效縮小結果範圍的欄位評估索引",[233,237,238],{},"可下多條件(複合索引)，當多條件時，會優先從最左邊的欄位開始找資料，所以欄位的排列順序很重要。",[213,240,242],{"id":241},"什麼時候不需要建立索引","什麼時候不需要建立索引?",[230,244,245,248,251,254,257,260,263],{},[233,246,247],{},"資料表本身很小",[233,249,250],{},"查詢時會取出大部分資料",[233,252,253],{},"欄位選擇性低，且沒有其他條件輔助",[233,255,256],{},"幾乎不會被查詢的欄位",[233,258,259],{},"資料需要大量且頻繁的寫入，但查詢收益有限",[233,261,262],{},"已有功能重疊的索引",[233,264,265],{},"條件寫法無法匹配索引",[213,267,269],{"id":268},"怎麼判斷資料庫有沒有用我的索引","怎麼判斷資料庫有沒有用我的索引?",[34,271,272],{},"PostgreSQL提供兩種方式",[34,274,275],{},[40,276],{"alt":277,"src":278},"PostgreSQL EXPLAIN 與 EXPLAIN ANALYZE 指令差異表","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fpostgresql-index-explain-analyze\u002Ff827932a99d98a5a.webp",[34,280,281],{},[94,282,283],{},"EXPLAIN",[285,286,290],"pre",{"className":287,"code":288,"language":289,"meta":180,"style":180},"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",[94,291,292,299,304,309,315],{"__ignoreMap":180},[293,294,296],"span",{"class":295,"line":8},"line",[293,297,298],{},"EXPLAIN\n",[293,300,301],{"class":295,"line":14},[293,302,303],{},"SELECT * FROM bookings WHERE member_id = 1;\n",[293,305,306],{"class":295,"line":19},[293,307,308],{},"-- 可能得到\n",[293,310,312],{"class":295,"line":311},4,[293,313,314],{},"Index Scan using idx_bookings_member_id\n",[293,316,318],{"class":295,"line":317},5,[293,319,320],{},"(cost=0.42..8.44 rows=200 width=20)\n",[34,322,323,324,327],{},"以下使用 ",[94,325,326],{},"EXPLAIN ANALYZE"," 作為建立索引前後的範例",[285,329,331],{"className":287,"code":330,"language":289,"meta":180,"style":180},"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",[94,332,333,338,342,347,352,357,363,369],{"__ignoreMap":180},[293,334,335],{"class":295,"line":8},[293,336,337],{},"EXPLAIN ANALYZE\n",[293,339,340],{"class":295,"line":14},[293,341,303],{},[293,343,344],{"class":295,"line":19},[293,345,346],{"emptyLinePlaceholder":191},"\n",[293,348,349],{"class":295,"line":311},[293,350,351],{},"Seq Scan on bookings  (cost=0.00..1834.00 rows=200 width=20) (actual time=0.015..18.432 rows=200 loops=1)\n",[293,353,354],{"class":295,"line":317},[293,355,356],{},"  Filter: (member_id = 1)\n",[293,358,360],{"class":295,"line":359},6,[293,361,362],{},"  Rows Removed by Filter: 99800\n",[293,364,366],{"class":295,"line":365},7,[293,367,368],{},"Planning Time: 0.089 ms\n",[293,370,372],{"class":295,"line":371},8,[293,373,374],{},"Execution Time: 20.104 ms\n",[34,376,377],{},"以這份資料表而言，當系統累積到十萬筆預約紀錄後，查詢某會員的預約紀錄就要花費20.104ms",[34,379,380],{},"針對這張表建立索引",[285,382,384],{"className":287,"code":383,"language":289,"meta":180,"style":180},"CREATE\nINDEX idx_bookings_member_id ON bookings(member_id);\n",[94,385,386,391],{"__ignoreMap":180},[293,387,388],{"class":295,"line":8},[293,389,390],{},"CREATE\n",[293,392,393],{"class":295,"line":14},[293,394,395],{},"INDEX idx_bookings_member_id ON bookings(member_id);\n",[285,397,399],{"className":287,"code":398,"language":289,"meta":180,"style":180},"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",[94,400,401,405,409,413,418,423,428],{"__ignoreMap":180},[293,402,403],{"class":295,"line":8},[293,404,337],{},[293,406,407],{"class":295,"line":14},[293,408,303],{},[293,410,411],{"class":295,"line":19},[293,412,346],{"emptyLinePlaceholder":191},[293,414,415],{"class":295,"line":311},[293,416,417],{},"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",[293,419,420],{"class":295,"line":317},[293,421,422],{},"  Index Cond: (member_id = 1)\n",[293,424,425],{"class":295,"line":359},[293,426,427],{},"Planning Time: 0.102 ms\n",[293,429,430],{"class":295,"line":365},[293,431,432],{},"Execution Time: 0.203 ms\n",[34,434,435],{},"建立索引後，查詢某會員的預約紀錄時間僅需 0.203ms",[437,438,439],"blockquote",{},[34,440,441],{},[442,443,444],"em",{},"此案例時間僅代表本次測試環境，重點是比較相同條件下建立索引前後的執行計畫與相對差異。",[213,446,448,450],{"id":447},"explain-analyze在說甚麼",[94,449,326],{},"在說甚麼？",[34,452,453],{},[40,454],{"alt":455,"src":456},"PostgreSQL 執行計畫中的掃描、索引、成本與時間欄位說明表","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fpostgresql-index-explain-analyze\u002F1317530aeaf8f00d.webp",[213,458,460],{"id":459},"join的時候怎麼規劃索引","JOIN的時候怎麼規劃索引?",[213,462,463],{"id":463},"對症下藥才能有效提升效能",[465,466,467,470,473,476],"ul",{},[233,468,469],{},"先查看完整執行計畫",[233,471,472],{},"找出真正成本較高或掃描資料過多的節點",[233,474,475],{},"評估連接鍵、篩選欄位及資料量",[233,477,478],{},"再決定哪張表需要哪種索引",[34,480,481],{},"多表連接時，應透過執行計畫逐一確認各資料表的掃描與連接成本，再針對常用連接鍵或篩選欄位評估索引，而不是直接替所有欄位建立索引。",[213,483,485],{"id":484},"為什麼建立-index-但資料庫還是逐筆搜尋","為什麼建立 Index 但資料庫還是逐筆搜尋？",[213,487,488],{"id":488},"資料庫本身也有思考",[34,490,491,492,495],{},"即使建立索引，但在執行查詢時，PostgreSQL 內會有 ",[442,493,494],{},"planner","，負責比較不同計畫的估算成本，選擇它認為總成本最低的方案。",[34,497,498,499,502],{},"且因索引是獨立於資料表的資料結構，一般 ",[94,500,501],{},"Index Scan"," 還可能先從索引找到資料位置，再回原資料表取得完整欄位。",[34,504,505],{},"如果他判斷逐筆查詢成本較低，就不會使用索引。",[437,507,508],{},[34,509,510],{},[442,511,512,513,521],{},"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 ",[514,515,519],"a",{"href":516,"rel":517},"https:\u002F\u002Fwww.postgresql.org\u002Fdocs\u002Fcurrent\u002Fsql-explain.html",[518],"nofollow",[94,520,283],{}," 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.",[213,523,525],{"id":524},"索引的成本有哪些","索引的成本有哪些?",[213,527,528],{"id":528},"索引不免費",[34,530,531],{},"前面提到過索引是獨立於資料表的資料結構，所以會占用儲存空間；資料新增、修改或刪除時，也可能需要額外同步更新索引。",[34,533,534],{},"可以說",[437,536,537],{},[34,538,539],{},[442,540,541],{},"建立索引就是犧牲部分增刪修，讓查的效能最大化。",[34,543,544],{},"其實每次的優化就是一個取捨的過程，假設有一張資料表在建立索引前，每次查詢都需要花費5s，寫入需要1.35s，建立索引後查詢只要0.05s，寫入變成1.47s。這樣該表的業務情境下是否值得建立索引呢?",[34,546,547],{},[40,548],{"alt":549,"src":550},"作者補充說明：以課程練習與實作經驗整理技術筆記","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fpostgresql-index-explain-analyze\u002Fdaccc04020965d70.webp",[552,553,554],"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":180,"searchDepth":14,"depth":14,"links":556},[557,558,559,560,561,562,564,565,566,567,568,569],{"id":215,"depth":14,"text":216},{"id":225,"depth":14,"text":225},{"id":228,"depth":14,"text":228},{"id":241,"depth":14,"text":242},{"id":268,"depth":14,"text":269},{"id":447,"depth":14,"text":563},"EXPLAIN ANALYZE在說甚麼？",{"id":459,"depth":14,"text":460},{"id":463,"depth":14,"text":463},{"id":484,"depth":14,"text":485},{"id":488,"depth":14,"text":488},{"id":524,"depth":14,"text":525},{"id":528,"depth":14,"text":528},{},"\u002Fblog\u002F20260802-postgresql-index-explain-analyze","2026-08-02",{"title":206,"description":211},"postgresql-index-explain-analyze","blog\u002F20260802-postgresql-index-explain-analyze",[577,578,579,202],"postgresql-database","database-performance","learning-notes","y_fTAv8SaCd5InCyg86y2tJqpipsam8tAZoPcrhHyDU",{"id":582,"title":583,"author":24,"body":584,"category":12,"cover":187,"description":633,"extension":189,"featured":9,"meta":634,"navigation":191,"path":635,"publishedAt":636,"relatedTools":187,"seo":637,"slug":638,"status":196,"stem":639,"tags":640,"updatedAt":187,"__hash__":643},"articles\u002Fblog\u002F20260704-express-middleware-vue-router-guard.md","用 Vue Router Guard 理解 Express Middleware",{"type":26,"value":585,"toc":631},[586,589,592,595,598,601,604,607,610,613,616,622,625,628],[34,587,588],{},"這兩周六角Node.js課程的每日任務多集中在Middleware，由於 Middleware 這個概念第一次出現時，提供的解釋包含像解決 CORS 時使用第三方套件，並說明這類東西就屬於 Middleware，所以我以為它就是別人寫好、針對某件特定事情處理的單一功能性套件，大概就像是 Axios 這種 package。",[34,590,591],{},"包含後面的每日任務中也有提到「自訂 Middleware」，感覺就跟前端開發時自己寫一個共用元件是很類似的概念。後來去查才發現 Middleware 其實是 Express 框架下，請求流程中的中介處理機制，並不是只指套件。",[34,593,594],{},"簡單來說，只要符合請求流程中的中介處理機制，不論是自訂或者使用第三方，都可以是 Middleware。",[34,596,597],{},"以 Express 框架來說，Middleware 通常會接收三個參數，分別是 Request、Response 和 Next。",[34,599,600],{},"針對 Request進行一些基本驗證或共用前置處理，比如驗證 token 、解析 JSON 等等。處理完成之後，如果已經可以決定結果，可以直接用 Response 回傳，或者使用 Next 讓這一段請求進入到下一段的邏輯。",[34,602,603],{},"然後在查Middleware的過程中，感覺這段描述怎麼跟我 Vue 的路由守衛有點相似。",[34,605,606],{},"這兩個的差異在於，Vue 的路由守衛是針對前端要切換路由前，去做一些事情，比如驗證當前使用者是否有進入該頁面的權限。如果沒有權限，就把他導向錯誤頁面或重新登入；在符合權限的情況下，才讓他進入準備要去的路由。",[34,608,609],{},"這其實跟 Middleware 有點類似，雖然可能沒有到百分之百一樣，但底層邏輯其實是非常相像的。",[34,611,612],{},"最終都是為了解決重複程式碼以及後續維護的成本，將驗證層進行收攏，把多處請求都需要做的共用前置處理，拉到同一個層面上，讓業務邏輯專注在業務邏輯之上。",[34,614,615],{},"其實像 Middleware 這個中介層，如果不去看它的名稱，單純從它在解決的底層邏輯來看，很多框架都有類似的流程攔截或前置處理機制，只是名稱、使用方式和實作細節不同。",[34,617,618],{},[40,619],{"alt":620,"src":621},"Vue Router Guard 與 Express Middleware 的流程攔截概念比較圖","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fexpress-middleware-vue-router-guard\u002F57fff0eac385193d.webp",[34,623,624],{},"補充說明：",[34,626,627],{},"我目前是一名非本科轉職的前端工程師，實務經驗約一年，近期正在慢慢往後端領域學習。Medium 上的文章多半是我在課程練習、實作過程與日常學習中，整理出的個人理解與技術筆記。",[34,629,630],{},"由於我仍在學習階段，內容可能有不夠完整或不夠精確的地方。如果有任何需要修正或補充的部分，歡迎大家友善交流，也謝謝願意指正與分享經驗的人。",{"title":180,"searchDepth":14,"depth":14,"links":632},[],"從前端路由守衛的角度，重新理解 Express Middleware：它不是單一套件，而是請求流程中的中介處理機制。",{},"\u002Fblog\u002F20260704-express-middleware-vue-router-guard","2026-07-04",{"title":583,"description":633},"express-middleware-vue-router-guard","blog\u002F20260704-express-middleware-vue-router-guard",[641,642,579],"express-middleware","frontend-backend","f8x4SfcpTkuZiZs-SskQ9w77aUN-SKkwhwX68EGF7kU",{"id":645,"title":646,"author":24,"body":647,"category":12,"cover":187,"description":651,"extension":189,"featured":9,"meta":757,"navigation":191,"path":758,"publishedAt":759,"relatedTools":187,"seo":760,"slug":761,"status":196,"stem":762,"tags":763,"updatedAt":187,"__hash__":766},"articles\u002Fblog\u002F20260628-http-success-status-codes.md","關於後端回覆「請求成功」的狀態碼的使用時機整理",{"type":26,"value":648,"toc":755},[649,652,659,714,717,720,723,726,729,735,738,749,751,753],[34,650,651],{},"完成六角 Node.js 直播班 Day 11 CRUD 實作與資料驗證任務時，當日任務要求如下：",[34,653,654,655,658],{},"完成四條路由（前綴由 ",[94,656,657],{},"app.use('\u002Fmembers', ...)"," 提供）：",[465,660,661,671,688,702],{},[233,662,663,666,667],{},[94,664,665],{},"GET \u002F","：回傳所有會員，狀態碼 ",[668,669,670],"strong",{},"200",[233,672,673,676,677,680,681,684,685],{},[94,674,675],{},"POST \u002F","：必填欄位 ",[94,678,679],{},"name","，成功回傳 ",[668,682,683],{},"201","；欄位缺失回傳 ",[668,686,687],{},"400",[233,689,690,676,693,695,696,699,700],{},[94,691,692],{},"PUT \u002F:id",[94,694,679],{},"，找不到回傳 ",[668,697,698],{},"404","，欄位缺失回傳 ",[668,701,687],{},[233,703,704,707,708,711,712],{},[94,705,706],{},"DELETE \u002F:id","：成功回傳 ",[668,709,710],{},"204","；找不到回傳 ",[668,713,698],{},[34,715,716],{},"其中 status code 204 引起了我的興趣，在工作過程中針對成功的請求，其實我只看過200、201，雖然當時也不是很確定這兩個差異，但是至少是非常常見的！",[34,718,719],{},"不過 204 到底是甚麼？且只在 method DELETE 時回覆 204 ？",[34,721,722],{},"綜合以上，我詢問 GPT：",[34,724,725],{},"「在後端開發裡，一般 GET 的 status code 是 200，而 POST 則是 201，代表建立資料，然後 DELETE 則用 204 代表資料刪除嗎？」",[34,727,728],{},"而 GPT 的回覆我整理成表格後如下：",[34,730,731],{},[40,732],{"alt":733,"src":734},"HTTP GET、POST、PUT、PATCH 與 DELETE 常見成功狀態碼對照表","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fhttp-success-status-codes\u002F8047b567ebd7c497.webp",[34,736,737],{},"也就是說，200 與 204，並不是單靠 method 區分，關鍵區別是後端 response「有沒有回傳值」",[465,739,740,743,746],{},[233,741,742],{},"成功 && 有資料回應：200",[233,744,745],{},"成功 && 建立新資料：201",[233,747,748],{},"成功 && 沒有資料要回：204",[34,750,624],{},[34,752,627],{},[34,754,630],{},{"title":180,"searchDepth":14,"depth":14,"links":756},[],{},"\u002Fblog\u002F20260628-http-success-status-codes","2026-06-28",{"title":646,"description":651},"http-success-status-codes","blog\u002F20260628-http-success-status-codes",[764,765,579],"http-status-codes","api-design","kfJP0G3nQ7pmiVivYPB5B2oonKecMOsfawC99W5YYzQ",{"id":768,"title":769,"author":24,"body":770,"category":12,"cover":187,"description":941,"extension":189,"featured":9,"meta":942,"navigation":191,"path":943,"publishedAt":944,"relatedTools":187,"seo":945,"slug":946,"status":196,"stem":947,"tags":948,"updatedAt":187,"__hash__":951},"articles\u002Fblog\u002F20260513-javascript-backend-course-review.md","六角學院 - 【後端】JavaScript 直播班心得與覆盤",{"type":26,"value":771,"toc":934},[772,776,795,799,806,813,816,831,834,838,849,852,856,859,870,873,882,885,894,897,906,916,920,923,926,932],[213,773,775],{"id":774},"_1-報名初衷為後端與雲端佈局","1. 報名初衷：為後端與雲端佈局",[34,777,778,779,782,783,786,787,790,791,794],{},"身為一名習慣 ",[668,780,781],{},"Vue 3"," 與現代 ",[668,784,785],{},"JS"," 語法的開發者，其實我瞄準的是六月的 ",[668,788,789],{},"Node.js"," 跟之後的 ",[668,792,793],{},"AWS"," 雲端部，因為預計在明年轉職成為後端工程師（Backend Engineer），所以打算多多培養全端（Full-stack）思維。",[213,796,798],{"id":797},"_2-kata-刷題的反思","2. Kata 刷題的反思",[34,800,801,802,805],{},"學習過程中，最有趣的莫過於每日任務的 ",[668,803,804],{},"Kata"," 刷題。我原本預期難度會跟每日任務一樣一點一點深入變難，結果中途遇到一題「求三角形另一角的度數」。",[34,807,808,809,812],{},"當時的我：用一分鐘打完程式後，盯著螢幕 10 分鐘，不斷懷疑自己「真的只有這樣嗎？」、「是不是有陷阱？」結果按下 ",[668,810,811],{},"ATTEMPT"," 秒過後，真的讓我哭笑不得。",[34,814,815],{},"另一次深刻的反思是「過度工程」（Over-engineering）。有一題要求回傳陣列內最大的兩個數，我當下腦袋卡住，花了半小時寫迴圈（Loop）去比較、蒐集。後來才突然驚覺：",[437,817,818],{},[34,819,820],{},[442,821,822,823,826,827,830],{},"只要先用 ",[668,824,825],{},"Set"," 去重（De-duplicate），再用 ",[668,828,829],{},"sort()"," 排序後取前兩位不就好了嗎？",[34,832,833],{},"那一瞬間，我真的很難理解半小時前的自己大腦是不是當機了。",[213,835,837],{"id":836},"_3-fetch-api-的衝擊","3. Fetch API 的衝擊",[34,839,840,841,844,845,848],{},"在工作上習慣了 ",[668,842,843],{},"Axios"," 的便利，這次課程中重新操作原生的 ",[668,846,847],{},"Fetch","，真的有種「返璞歸真」的衝擊感。雖然原生語法寫起來比較繁瑣（心裡默默吶喊：這啥？##），但讓我也經歷了一場「技術記憶大復甦」。",[34,850,851],{},"從一開始的「這是什麼新套件？」到後來的：「靠，對欸！資策會剛學程式時有學過！」。這種從便利回歸原始的過程，雖然寫得很苦，但也讓我對於目前所有套件的開發者充滿敬畏，因為他們真的讓現在的開發變得簡單很多很多。",[213,853,855],{"id":854},"_4-優雅的寫法跟課程需要的古老寫法","4. 優雅的寫法跟課程需要的古老寫法(?)",[34,857,858],{},"在工作上我一般習慣使用箭頭函式（Arrow Function），因為覺得他寫起來很美，既優雅又簡潔～",[285,860,864],{"className":861,"code":862,"language":863,"meta":180,"style":180},"language-javascript shiki shiki-themes github-light github-dark","const a = b => b++\n","javascript",[94,865,866],{"__ignoreMap":180},[293,867,868],{"class":295,"line":8},[293,869,862],{},[34,871,872],{},"如果使用一般寫法就是：",[285,874,876],{"className":861,"code":875,"language":863,"meta":180,"style":180},"function a(b) { return b++; }\n",[94,877,878],{"__ignoreMap":180},[293,879,880],{"class":295,"line":8},[293,881,875],{},[34,883,884],{},"還有操作陣列的回調函式（Callback Function），明明可以：",[285,886,888],{"className":861,"code":887,"language":863,"meta":180,"style":180},"arr.map(a => a.uuid)\n",[94,889,890],{"__ignoreMap":180},[293,891,892],{"class":295,"line":8},[293,893,887],{},[34,895,896],{},"但就要變成：",[285,898,900],{"className":861,"code":899,"language":863,"meta":180,"style":180},"arr.map(function (a) { return a.uuid })\n",[94,901,902],{"__ignoreMap":180},[293,903,904],{"class":295,"line":8},[293,905,899],{},[34,907,908,909,912,913,915],{},"這次的後端新手小遊戲，有些題目好像會根據是否有 ",[94,910,911],{},"function"," 判斷回答是否正確。習慣了箭頭函式的簡潔優雅後，回去寫傳統語法真的寫得很苦 QQ。每一行多出來的 ",[94,914,911],{}," 和花括號對我來說都像是多餘的雜訊。但這也強迫我重新適應不同的代碼規範（Code Style），練習在不同的開發語境下切換自如，算是在痛苦中的一種意外收穫。",[213,917,919],{"id":918},"_5-覆盤","5. 覆盤",[34,921,922],{},"這一次透過刷題跟每日，我自己非常有感的是對陣列（Array）操作的直覺變得更敏銳了。對我來說，學習是一場馬拉松，我享受這種每天一點點的過程。",[34,924,925],{},"無論你是從資策會轉職，還是正在挑戰新的技術，不要被眼前的繁瑣語法擊倒。學習是一個不斷「解壓縮」與「重啟」的過程。只要還在這條路上，最後會發現那些當初看得一頭霧水的東西，最後都會變成你實力的一部分。",[34,927,928],{},[40,929],{"alt":930,"src":931},"六角學院 JavaScript 直播班心得與覆盤插圖","https:\u002F\u002Fassets.jessieyulab.com\u002Farticles\u002Fjavascript-backend-course-review\u002F7b8ca123f9c2d65e.webp",[552,933,554],{},{"title":180,"searchDepth":14,"depth":14,"links":935},[936,937,938,939,940],{"id":774,"depth":14,"text":775},{"id":797,"depth":14,"text":798},{"id":836,"depth":14,"text":837},{"id":854,"depth":14,"text":855},{"id":918,"depth":14,"text":919},"身為一名習慣 Vue 3 與現代 JS 語法的開發者，其實我瞄準的是六月的 Node.js 跟之後的 AWS 雲端部，因為預計在明年轉職成為後端工程師（Backend Engineer），所以打算多多培養全端（Full-stack）思維。",{},"\u002Fblog\u002F20260513-javascript-backend-course-review","2026-05-13",{"title":769,"description":941},"javascript-backend-course-review","blog\u002F20260513-javascript-backend-course-review",[949,201,202,950],"javascript-basics","career-change","Le-8Nr9TetaKNMrZ7V5JuUOWlrHFA8QIIhQW4EoX1Y0",[953,957,960,963,966,969,972,975,979,983,987,991,995,1000,1004,1008],{"title":954,"slug":955,"description":956,"order":8,"indexable":9},"方法","methods","可以重複使用的思考與操作方法。",{"title":958,"slug":765,"description":959,"order":14,"indexable":9},"API 設計","API 回應、介面規劃與實作原則。",{"title":961,"slug":950,"description":962,"order":19,"indexable":9},"轉職工程師","轉職軟體工程師的學習、工作與成長歷程。",{"title":964,"slug":200,"description":965,"order":311,"indexable":9},"雲端部署","雲端服務、自動化流程與部署問題的實作紀錄。",{"title":967,"slug":201,"description":968,"order":317,"indexable":9},"課程心得","課程參與、作業實作與學習成果的回顧。",{"title":970,"slug":578,"description":971,"order":359,"indexable":9},"資料庫效能","資料庫查詢、索引與效能分析相關筆記。",{"title":973,"slug":641,"description":974,"order":365,"indexable":9},"Express 中介軟體","Express 請求流程與中介處理機制的學習筆記。",{"title":976,"slug":977,"description":978,"order":371,"indexable":9},"前端開發","frontend-development","前端框架、瀏覽器互動與介面開發經驗。",{"title":980,"slug":642,"description":981,"order":982,"indexable":9},"前後端觀念","從前端與後端不同角度理解共通開發觀念。",9,{"title":984,"slug":202,"description":985,"order":986,"indexable":9},"六角學院","六角學院課程、活動與作業的學習紀錄。",10,{"title":988,"slug":764,"description":989,"order":990,"indexable":9},"HTTP 狀態碼","HTTP 回應狀態與 API 使用情境整理。",11,{"title":992,"slug":949,"description":993,"order":994,"indexable":9},"JavaScript 基礎","JavaScript 語法、瀏覽器功能與基礎觀念。",12,{"title":996,"slug":997,"description":998,"order":999,"indexable":9},"學習成長","learning-growth","長期學習、能力累積與自我成長的經驗。",13,{"title":1001,"slug":579,"description":1002,"order":1003,"indexable":9},"學習筆記","課程、文件與實作過程整理出的學習筆記。",14,{"title":1005,"slug":199,"description":1006,"order":1007,"indexable":9},"Node.js 後端開發","使用 Node.js 建立後端服務的學習與實作紀錄。",15,{"title":1009,"slug":577,"description":1010,"order":1011,"indexable":9},"PostgreSQL 資料庫","PostgreSQL 資料庫設計、查詢與效能分析筆記。",16,1795182585835]