[{"data":1,"prerenderedAt":129},["ShallowReactive",2],{"posts-list":3,"categories":101},{"code":4,"msg":5,"data":6,"count":100},200,"查询成功",[7,18,27,36,44,53,63,74,84,92],{"id":8,"name":9,"image":10,"cate_id":11,"description":12,"thumb_up":13,"clicks":14,"create_time":15,"update_time":15,"cate_name":16,"comments":13,"tags":17},159,"百万在线 IM 已读未读怎么设计？","https:\u002F\u002Ftp.myong.top\u002Fstorage\u002Farticle\u002F20260701\u002Fdfe49400b9fbdd240fbff867d9e4aead_thumb.png",1,"IM 已读未读的难点不在状态字段，而在海量消息下的存储膨胀、高频上报和群聊统计。核心做法是用已读游标替代逐条状态，并按单聊、大群、回执群分别设计。",0,6,"2026-07-01 22:36:49","技术杂谈",[],{"id":19,"name":20,"image":21,"cate_id":11,"description":22,"thumb_up":13,"clicks":23,"create_time":24,"update_time":25,"cate_name":16,"comments":13,"tags":26},158,"HTTP\u002F3 的 QUIC 基于 UDP，为什么仍然可靠？","https:\u002F\u002Ftp.myong.top\u002Fstorage\u002Farticle\u002F20260630\u002F79e6b956998d908a8e4c25b74722752f_thumb.png","QUIC 并不是裸用 UDP，而是在 UDP 之上实现确认、丢包恢复、流量控制、拥塞控制、加密握手、多路复用和连接迁移。理解这 7 点，才能把 HTTP\u002F3 的可靠性讲清楚。",11,"2026-06-30 00:10:22","2026-06-30 00:10:23",[],{"id":28,"name":29,"image":30,"cate_id":31,"description":32,"thumb_up":13,"clicks":23,"create_time":33,"update_time":33,"cate_name":34,"comments":13,"tags":35},156,"Superpowers：把 AI 编程从提示词技巧升级成工程流程","https:\u002F\u002Ftp.myong.top\u002Fstorage\u002Farticle\u002F20260628\u002F8bdcd50c0b35154f898196124260a8dc_thumb.png",16,"Superpowers 的价值不在于让 AI 更会写代码，而是把需求澄清、计划拆分、测试验证和系统调试变成可执行流程。本文结合官方资料与项目热度，拆解新手为什么先从 4 个核心 skill 入手，以及团队如何把它落地为可复盘的 AI 编程规范。","2026-06-28 00:41:22","Ai",[],{"id":37,"name":38,"image":39,"cate_id":31,"description":40,"thumb_up":13,"clicks":41,"create_time":42,"update_time":42,"cate_name":34,"comments":13,"tags":43},155,"别再把 Codex 当聊天框：把 AI 用成一支可管理的开发队","https:\u002F\u002Ftp.myong.top\u002Fstorage\u002Farticle\u002F20260625\u002F6e83cfaf93e0b108efaa40908989d9c3_thumb.png","本文提出一种将 Codex 从“普通聊天框”升级为“可管理的 AI 开发队”的使用方法。核心思路是把一个项目拆成清晰的工作区与独立 Thread，先 Plan 再实现，完成后用 Review 做代码审查，并通过 AGENTS.md、Skills、MCP 和定时任务把规则、流程和重复劳动标准化，从而降低上下文混乱和返工成本",14,"2026-06-25 23:54:55",[],{"id":45,"name":46,"image":47,"cate_id":31,"description":48,"thumb_up":13,"clicks":49,"create_time":50,"update_time":51,"cate_name":34,"comments":13,"tags":52},154,"Codex 实战技术分享：把 AI 编程助手接入真实工程流","https:\u002F\u002Ftp.myong.top\u002Fstorage\u002Farticle\u002F20260622\u002Fe53d70cddc06c25db64c1895a49e9b68_thumb.png","本文介绍 Codex 在 CLI、IDE、App 和 Cloud 中的使用场景，梳理任务闭环、Prompt 编写、AGENTS.md 与 config.toml 配置、安全边界和团队落地方法，帮助研发团队把 Codex 接入可审阅、可验证的工程流程。",17,"2026-06-22 20:03:56","2026-06-22 20:04:41",[],{"id":54,"name":55,"image":56,"cate_id":11,"description":57,"thumb_up":58,"clicks":59,"create_time":60,"update_time":61,"cate_name":16,"comments":13,"tags":62},150,"你浏览器上的那把小锁，到底锁住了什么？——白话聊聊 HTTPS 与 HTTP","https:\u002F\u002Ftp.myong.top\u002Fstorage\u002Farticle\u002F52\u002F2fe023056f3e30ee89fa368e3f78cc_thumb.jpg","网址前面那个不起眼的“s”和一把小锁，往往是安全与裸奔的分界线。本文用人话拆解 HTTPS 证书究竟在背后做了什么，以及它与“裸奔”的 HTTP 到底有哪些实打实的区别。读完你会发现，从明信片到保险箱，只差这一步。",5,44,"2026-05-29 23:01:30","2026-06-20 03:46:42",[],{"id":64,"name":65,"image":66,"cate_id":67,"description":68,"thumb_up":13,"clicks":69,"create_time":70,"update_time":71,"cate_name":72,"comments":13,"tags":73},149,"被误解的 Redis 单线程：为什么它依然是快如闪电的秘密","https:\u002F\u002Ftp.myong.top\u002Fstorage\u002Farticle\u002F69\u002F38924b4eb5e960ecdb0961eb143096_thumb.jpg",13,"一提起 Redis 的单线程，总有人觉得这是浪费服务器资源的老古董设计。但当你真正理解它的内存操作本质和 I\u002FO 多线程的演进后，你会发现这是一个把“简单”和“安全”发挥到极致的精妙权衡。这篇文章聊聊 Redis 单线程的那些过人之处，以及它真正怕什么",30,"2026-05-25 00:04:13","2026-05-29 00:04:46","Redis",[],{"id":75,"name":76,"image":77,"cate_id":14,"description":78,"thumb_up":13,"clicks":79,"create_time":80,"update_time":81,"cate_name":82,"comments":13,"tags":83},148,"SQL 跑得慢？别慌，这里有份排查手册","https:\u002F\u002Ftp.myong.top\u002Fstorage\u002Farticle\u002F47\u002F99a9dc36e27ae31744abfc94176cef_thumb.jpg","线上一条 SQL 突然变慢，往往是开发与 DBA 最头疼的问题。本文不讲晦涩理论，直接梳理一套落地的排查路径：从快速定位问题 SQL，到读懂执行计划、揪出索引与锁的毛病，再到系统资源与配置调优。下次再遇慢查询，照着清单查一遍，多半能找到病根。",28,"2026-05-23 00:43:43","2026-05-29 11:26:33","Mysql",[],{"id":85,"name":86,"image":87,"cate_id":14,"description":88,"thumb_up":13,"clicks":69,"create_time":89,"update_time":90,"cate_name":82,"comments":13,"tags":91},147,"数据库索引的定海神针：B+ 树凭什么这么能打？","https:\u002F\u002Ftp.myong.top\u002Fstorage\u002Farticle\u002Fde\u002F36593248f37397d88a6a0d873ebaad_thumb.jpg","为什么 MySQL、PostgreSQL 等关系型数据库的底层索引，清一色选择了 B+ 树？这篇文章从磁盘读写特性、查询稳定性、范围扫描和存储模型等角度，把 B+ 树相对 B 树的那些碾压级优势拆开了聊，看清它在工程上的“独一份”价值。","2026-05-21 22:36:06","2026-05-29 11:15:53",[],{"id":93,"name":94,"image":95,"cate_id":14,"description":96,"thumb_up":13,"clicks":79,"create_time":97,"update_time":98,"cate_name":82,"comments":13,"tags":99},146,"MySQL 查询优化：如何减少恼人的“回表”","https:\u002F\u002Ftp.myong.top\u002Fstorage\u002Farticle\u002F47\u002F7aaf5aeee68d3e4794a17c6d5b2eea_thumb.jpg","在 MySQL InnoDB 中，二级索引查询往往需要“回表”去聚簇索引捞取完整数据，而这一步常伴随着代价高昂的随机 I\u002FO。本文会先用一个生活化的比喻说清楚什么是回表，再谈谈它为什么这么慢，最后结合实战场景，分享覆盖索引、索引条件下推（ICP）、延迟关联等切实可行的优化方法，帮你避开回表带来的性能坑。","2026-05-21 00:09:20","2026-05-29 11:41:42",[],143,{"code":4,"msg":5,"data":102,"count":13},[103,107,109,112,113,116,119,120,123,124,126],{"id":104,"name":105,"count":106},2,"PHP",48,{"id":11,"name":16,"count":108},23,{"id":58,"name":110,"count":111},"Python",19,{"id":14,"name":82,"count":31},{"id":114,"name":115,"count":23},4,"Linux",{"id":23,"name":117,"count":118},"工作项目",9,{"id":67,"name":72,"count":58},{"id":121,"name":122,"count":58},12,"Nginx",{"id":31,"name":34,"count":114},{"id":41,"name":125,"count":104},"前端",{"id":127,"name":128,"count":11},7,"JavaScript",1783431642978]