Найти похожее

Advent of Code 2022, small programming puzzles for a variety of skill sets that can be solved in any programming language. #coding @thedevs https://thedevs.link/HxnXh2

Goodbye, clean code. #coding @thedevs https://kutt.it/e8ePSG

Name It, and they will come. #coding @thedevs https://kutt.it/emm4ZE

Claude Code/ Codex/ Antigravity 终极启动器 （iTerm2 版） 丝如滑。最近优化了 Keyboard Maestro 快速在 iTerm 中启动 Claude Code/ Codex 宏动作。（已放评论） 结合我的快捷键启动建议，双击 Command 键读取选中的文件或文件夹，通过 iTerm2 在 Claude Code 中打开该目录位置，如果没有选中内容则跳转到预设目录。这里好用的是如果识别到 iTerm2 窗口已经打开，则开启新的 Tab 窗口分栏进入 Claude Code 打开，默认 Cmd+T 直接打开默认窗口；Codex 双击 Option 键同理。 还有个双击 Ctrl 可以 Antigravity 中同样快捷获取路径打开 iTerm Claude Code cd 到对应目录。如果 Antigravity 未打开，双击 Ctrl 则先打开该该窗口。 相关链接： 1 Claude Code 终极启动器 2 目前我的顶级生产力启动器 3 iTerm2 #coding

#coding I had some discussions with serval people about writing good code during machine learning experimentation. Whenever it comes to the part of writing formal code, opinions diverge. So, should we write good code that is easy to read with typing and tests, even in experiments? The spirit of experimentation is fast and reliable. So naturally, the question comes down to what kind of coding style allows us to develop and run experiments, fast. My experience with running experiments is that we will never run the code just once. Instead, we always come back to it and run it with different configurations or parameters. In this circumstance, how good shall my code be? For typing and tests, I type most of my args but only write tests needed to develop and debug a function or class. - Typing is important because people spend time figuring out what to put in there as an argument for a function. With typing, it is much faster. - Here is an example for tests: If I need to know the shape of the tensor deep in a method of a class, I would spend some seconds writing a simple test that allows me to put breakpoints in the method to investigate inside. But, the above is a bit trivial. How about the design of the functions and classes? I suggest taking your time writing those that are repeated in every experiment. We will hit some ceiling in development speed real quick, if we always use the first and most naive design for these. In practice, I would say, design it twice and write it once. One such example is data preprocessing. When dealing with the same data and problems, data transformations are usually quite similar in each experiment but a bit different in details. Finding the patterns and writing some slightly generic functions would be helpful. There is always the risk of over-engineering. I prefer to improve things little by little. I might generalize a function a little bit in one experiment. And also, don't hesitate to throw away your code to rewrite. Rewriting will take little time, and it usually brings in improvements. That's my five cents on code quality for developing and running machine learning experiments.

#Coding 今天闲下来重构一下以前坏掉的 Bilibili 网页播放器增强插件，发现我在其他项目中通过 Vite 构建 userscript (如 Tampermonkey) 插件脚本的依赖项目引流到另一个项目：vite-plugin-monkey，试用了一下确实是更加好用，也提供了不同框架的脚手架，给零碎的小需求节省了不少时间（不要问我小需求为什么不直接写单文件 vanilla js 呢🤣）

#Coding I found a nice place to practice programming thinking. It is not as comprehensive as hackerrank/leetcode but these problems are quite fun. https://codingcompetitions.withgoogle.com/

你要学会把代码和你自己分离，不要成为代码的拥有者。你要优化代码，便于其他人找到方法来修复错误和添加功能，把代码的控制权分散。因为你需要解放自己，继续去做下一个项目，否则你将永远无法脱身。 -- 《我编程20年的指导原则》 #Coding

#coding

我VPS上的Selfhost服务 以前刚玩博客的时候用的 Wordpress 作为博客系统，基本上都搭建在一些互联网的公益服务上，如今还记得就是 wpoak 这个平台，不过这些服务难抵时间漫长，大多因为成本问题关门大吉了。 所以之后开始自己买 VPS 进行博客程序部署，也开始慢慢重视起数据的重要性和自我保有。 刚开始 VPS 还是玩的非常简单，实例化完成后便用 lnmp 等程序一键装好 PHP 环境，然后下载上传 WordPress 安装程序便算完事了，后来接触的多了才知道 VPS 能做的事情元远不止于此。 后来我开始接触到 Docker，然后研究各种 Selfhost 的应用、服务。 文章地址：https://1900.live/wo-vpsshang-de-selfhostfu-wu/ #Docker#Selfhost

一些现取现用的 box shadow 样式 #coding#tool

静态博客两周年 & Hugo 装修小记之四 #blog#coding