我以为的澳洲生活,家家大豪斯,工作随便搞搞,薪资高还不卷
现实的澳洲生活,House 根本租不起,生活成本巨高,昨天和前同事聚餐,除了我都没找到工作…这个市场是怎么了…
https://x.com/luckytantanfu/status/1930590554007703803
让 AI 帮我用纯 css 画三角形。他换着不同的姿势画了好几个还帮我写了 class 怕我看不懂,这样可以直接用。刚学 css 的时候,我搞这个画了一天,因为这是当年的热门面试题。
🙈2
我也找个时间去两周,有么有那种专门给数字游民的民宿,包吃饭那种。
https://x.com/liruifengv/status/1930993513237487798
https://x.com/liruifengv/status/1930993513237487798
喜大普奔,NotebookLM 确认会开放 API 了。这下 AI 笔记类的产品要颤抖一下了,但愿价格别太感人。
https://x.com/notebooklm/status/1931063823081078904
https://x.com/notebooklm/status/1931063823081078904
X (formerly Twitter)
NotebookLM (@NotebookLM) on X
Q: When API?
A: Everyone's favorite question 😉 We promise that we hear you and it is in the plan!
A: Everyone's favorite question 😉 We promise that we hear you and it is in the plan!
这是个前端招聘推文,看起来适合兼职。学了一个新词,Pro C 大概是指专业用户。
https://x.com/kxycigaret/status/1930937805263470829
https://x.com/kxycigaret/status/1930937805263470829
说实话没啥期待,输入法切换的问题到底啥时候修好?
https://developer.apple.com/cn/wwdc25/
https://developer.apple.com/cn/wwdc25/
Apple Developer
WWDC25
重温为期一周的技术和创意活动。
厘米碎碎念
每次 AI 编码结束后,可以对他进行灵魂拷问。 有没有多余的废话? 有没有多余的逻辑? 有没有多余的抽象? 他就会老老实实改东西了。
---
title: "Code Soul-Searching"
description: "A final review checklist to ensure the generated code is concise, efficient, and appropriately abstracted. It challenges the AI to justify its output against key software principles."
# type: manual <- Use this if you want to manually trigger it with @soul-search
type: always #<- Use this to have it apply automatically to every agentic task
---
As the absolute final step before you present your solution, perform a critical self-review of all the code you have generated or modified. Challenge your own work against these three core principles of "soul-searching":
**1. Is there any unnecessary verbosity? (The "Nonsense" Check)**
- Scrutinize every line of code, every variable name, and every comment.
- **Action**: Remove any boilerplate, redundant comments, or overly verbose logic that does not add significant value to functionality or critical long-term clarity. The code should be expressive but not chatty.
**2. Is there any redundant logic? (The "Efficiency" Check)**
- Analyze the control flow and data manipulation. Is there a more direct path to the same result?
- **Action**: Refactor to eliminate any superfluous conditional checks, extra loops, or convoluted steps. Strictly adhere to the **DRY (Don't Repeat Yourself)** and **KISS (Keep It Simple, Stupid)** principles.
**3. Is there any unnecessary abstraction? (The "Simplicity" Check)**
- Evaluate every abstraction layer, class, or function you've introduced. Is its existence truly justified by the current complexity or a clear, immediate requirement for reuse?
- **Action**: If an abstraction adds more complexity than it solves, simplify it. Avoid premature generalization and strictly adhere to the **YAGNI (You Ain't Gonna Need It)** principle.
Only provide the final, refined code **after** it has successfully passed this rigorous self-critique. If you made changes during this review, briefly mention what was improved.