与「PRACTICE」相关的搜索结果

人的三重哲学进阶 1 兽性 猴子🐒猴急猴急 —喜欢吃快餐，喜欢暴富，喜欢走后门！ 2 人性具有一定的责任 ，喜欢讲故事，塑造形象！ 3 神性 静中取乐，喜欢静中作乐，修行！ 我们最初都是猴子🐒演变而来 The three philosophical stages of human development: 1. Animality - Monkey-like impatience and eagerness - fond of fast food, sudden wealth, and backdoor deals! 2. Humanity - bears a certain responsibility, enjoys storytelling, and image-building! 3. Divinity - finds joy in tranquility, enjoys amusing oneself in silence, and practices self-cultivation! We all evolved from monkeys in the beginning @elonmusk

The Across domain is currently down while we secure it against an attack from earlier today. At ~18:45 UTC, a social engineering attack on @Namecheap (our domain registrar) gave a bad actor control of the Across domain. Within 15 minutes of this attack, we were alerted and immediately worked to shut the site down. SEAL911 marked across.(to) as a phishing site with major wallets, and Cloudflare worked with us to mark the domain as at risk, and later pulled the site’s DNS records. At the time of this post, Across.(to) is fully down, and the phishing site is no longer available. In the brief period before Cloudflare fully blocked the malware site, some users who visited across.(to) may have been affected. No third-party integrations or API users were affected. Users who believe they were affected should DM us with transaction details and revoke attacker permissions (see next tweet for details). Despite our best efforts, @Namecheap has been unresponsive, and we have not been able to properly secure the domain to bring Across’s services back up. Across’s frontend and API will remain down until we can properly secure them. We will always put user safety first. Across’s domain was fully locked down with best-in-class security practices; this unauthorized takeover should not have been possible. We will be investigating this deeply and will provide a post-mortem on how this domain takeover was possible once we have more information.

We're still so small but I'm loving the team we've got at Superlogical. They're so talented and kind and love their craft. It's a different era of software development and our expectations and practices reflect that. I want to share a bit about how we work. First, everyone is trusted to push to main. We do machine-aided code review pre-push and human plus more machine-aided code review post-push. Limited to no PRs. Culturally, we've all agreed that if we ever hire someone who we DON'T trust to push directly to main, then they probably aren't the right fit for the team (so far, not an issue). Some common sense here: if someone is stepping outside their lane or comfort zone, we'll open PRs. For example, I'm pretty trash at macOS/iOS UI, so I'll open PRs for UI-affecting functionality and ask for eyeballs/help. But for business logic and internals, I push to main. Second, everyone can cut a release. Our release process is fully automated and when you start a release (for any platform) it triggers a Slack notification and a 15 minute countdown. The 15 minute warning is a final gate that allows people to review plus collaborate on a changelog. During that 15 minutes, anyone in the company can pause the release rollout. After 15 minutes, the train leaves the station. You can't override the 15 minutes (except to pause). It gives everyone a chance to step in. Third, we avoid synchronization through fast remediation rather than through planning. The server and clients on various platforms ship features as fast as they can. We use post-hoc human review and AI-assistance to identify feature mismatches across products ("Windows has support for X and Mac doesn't." or "Mac and Windows differ in their behaviors for Y in this way."). This avoids expensive "sync" meetings and coordination. We trust that producers of features are mindful of what they're producing and we trust that adjacent product lines will self-synchronize quickly. In practice, we see feature parity across platforms within 24 to 48 hours. All of this works on mutual trust. It ONLY works with mutual trust. Everyone at all times has to trust that they've got each others back: 1. Push to main only works if you fix your mess, or if you don't, that someone else will quickly but that you'd do the same (and generally in equal amounts). 2. Anyone can deploy only works if you trust everyone to cut at the right time, with the right changelog, and that people will respect the 15 minute timer. 3. Sync through fast remediation only works if you trust other teams will pick up and integrate your work quickly, which only works if you would too. It also only works if you are fairly producing mismatches (e.g. not constantly). We've got a great team. I know we're still small and that these practices will change in many ways as we scale. But this is already a markedly different practice than what I would've done 15 years ago. In general, we are building from day 1 on a foundation of mutual respect, excellence, and trust. And it's been awesome.

斯坦福居然把一门 Vibe Coding 课程免费公开了！ 课程名叫 CS146S: The Modern Software Developer。 课件、作业和学习资料全部对外开放，不用是斯坦福学生，也能跟着学。 📚 斯坦福课程官网： 🎬 YouTube 学习视频（第三方讲解）： 我看了一下课程内容，发现它教的远不止怎么用 AI 写代码，而是怎么让一个人借助 AI，独立完成一个软件项目。 主要有 5 个部分：👇 1️⃣ 学会真正使用 AI 从 Prompt、AI IDE 到 Terminal，系统学习怎么跟 AI 协作开发。 很多人现在用 AI 写代码，还是复制需求、等它输出、报错了再把错误贴回去。 这门课就是帮你摆脱这种纯靠碰运气的开发方式。 2️⃣ MCP：让 AI 真正连接外部世界 AI 的未来肯定离不开 Agent。 但 Agent 不能只会在聊天框里回答问题，还得能读取文件、调用工具、访问数据库、执行任务。 MCP 就是其中很重要的一环。 学会之后，你可以让 AI 直接参与自己的项目，而不是做出第 10086 个聊天机器人。 3️⃣ 部署、监控和 UI 这是我觉得特别值得学的一部分。 以前一个人做产品，前端、后端、设计、部署、运维，哪个环节都能把你卡住。 现在借助 AI，一个人也有机会把这些事情串起来。 重点不再是写出几百行代码，而是能不能把产品真正交付给别人使用。 4️⃣ Best Practices AI 能生成代码，不代表生成的代码就能直接上线。 怎么测试？怎么排查 Bug？怎么管理上下文？怎么避免 AI 越改越乱？ 这些才是从 Vibe Coding 走向真正软件开发必须补上的东西。 5️⃣ Skills：给 AI 装上专业能力 我觉得 Skills 是 Agent 发展中特别值得关注的方向。 以前你需要反复告诉 AI 怎么做事，现在可以把工作流程、工具和规则封装成 Skill，让它重复执行。 写报告、处理 Excel、制作 PPT、设计网页，都可以逐步变成可复用的能力。 当然，装了 Skill 不代表 AI 就成了专家，最终结果还是得验证。 最后，说个可以直接照着做的实操，别光收藏课件，自己用 Cursor 做个 AI 资讯看板。 先搭 UI，再通过 MCP 接入 3 个 RSS 新闻源，最后做个 Skill，自动去重、分类和生成摘要。 部署到 Vercel 后，拿 20 条真实新闻测试，故意混入重复链接和失效地址。 这一套做下来，Prompt、MCP、Agent、Skills、UI、部署和测试就全串起来了，比看十遍教程有用多了。 想真正学会用 AI 做产品的，可以直接开干了！！！