WWW.YOUINFO.SITE
标签聚合 experience

/tag/experience

v2ex · 2026-06-11 18:15:27+08:00 · tech

We are looking for someone who: - Has experience in C# (.NET 8+, ASP.NET Core) - Enjoys and has experience building RESTful APIs, preferably having built APIs from scratch - Has experience with Agile/Scrum - Has experience with CI/CD tools to get projects to production - Has experience applying good coding principles, testing and backend system architecture design - Has experience with SQL databases; familiarity with MySQL, MariaDB or PostgreSQL is a plus - Experience with Kubernetes and MS Azure hosting is a strong advantage - Annual Bonus: A well-deserved reward for your contributions. - Hybrid Working: Enjoy the flexibility to balance office and WFH. - 6 Weeks Working from Abroad: Take your work to inspiring locations around the world. - 25 Paid Days Off: Plus the option to buy more. 地点 Amsterdam 可以从中国之间请,不能远程 全英文交流,这个必须 有意就请发英文简历到 am9obmF3ZXNvbWUxN0BnbWFpbC5jb20= 顺便英语手写介绍一下情况,联系电话和方便联系的时间

v2ex · 2026-06-10 18:23:37+08:00 · tech

Just Be Patient is a short, atmospheric interactive experience about waiting, noticing, and slowly figuring out what is really going on. It does not rush you with complicated controls or loud objectives https://justbepatient.online/ . Instead, it invites you to stay present, pay attention to small details, and let the story unfold at its own pace. The game feels quiet, a little mysterious, and strangely personal. Every moment is designed to make you wonder whether patience is just part of the gameplay, or the real message behind it. If you enjoy small experimental games with emotional tension, simple interaction, and a sense of hidden meaning, Just Be Patient is the kind of game that stays in your head after you leave.

LinuxDo 最新话题 · 2026-06-06 09:02:08+08:00 · tech

不知道有佬友被封的pro被解封? 原帖子: OpenAI Status Some users may experience issues accessing OpenAI accounts - OpenAI Status The team is uncovering some additional impacted users and is still working through related subscription and credit impacts for affected users. Impacted users will be receiving an email shortly. OpenAI Status Some users may experience issues accessing OpenAI accounts - OpenAI Status The team is uncovering some additional impacted users and is still working through related subscription and credit impacts for affected users. Impacted users will be receiving an email shortly. 原文:An issue caused some user accounts to be incorrectly suspended. We’re restoring access and working through related subscription and credit issues. 5 个帖子 - 4 位参与者 阅读完整话题

linux.do · 2026-05-01 23:01:26+08:00 · tech

经过每天17个小时的高强度使用Codex CLI,分享使用经验 Q:每次提了一大长串要求,但最后成品像是没改或者简陋实现? 1.这种情况主要是compact了,上下文被压缩再开始,很多东西细节全部丢失,所以使用的时候需要尽量节省context。 绝对不要触发compact,如果你想获得最好效果建议将每次used控制在90%以内 2.多多使用plan mode 按住shift再加tab,先和AI对齐需求 后清空thread 选择clear and implement ,每次开始新的改动都先/clear。 3.每次都只对一个小点提修改,不要试图一次性输入要求,等待时间长效果还不理想。 基本上等45分钟以上效果就会超级差,1小时至1小时+完全浪费时间,这个时候AI自己都不知道在干什么了,几乎是修失忆写的垃圾代码 4.来源、参考、项目目录改动必须具体描述,不要靠“你来决定”“最好的实现办法”,AI不会知道,必须要精确的要求。 尽量少的提超大面积修改需求,上下文限制根本无法完成,比如优化诗山代码,减少性能开销,检查每一处代码,对所有源代码进行检查这些都是空谈,根本没用 5.不要相信AI对你的项目的任何全面分析的报告和评分,因为compact之后AI对之前的检查全部都基于潜行记忆,全部是虚假无依据内容,当你以为让他改完获得更高的项目结构评分,那就简直是自嗨。 6.创建新项目的时候不要让codex一次全面实现,plan mode几乎都会让你选阶段性实现。 在Plan mode下codex提供的选择中万不得已不要选择recommend以外的选项,这些选项就像是谋士给的上中下策,实际上你只有一个策略可以选(勘误:对详细内容里写明确不推荐和大块复写的选项避开,与recommend工作量差不多可以选),只是让你有更多的实现思路 7.关于spec 即步骤准备文档 ,这是一个由社区总结出来的计划方案,先通过话聊的方式建立一个开发框架,由你和AI进行补充、对齐和更改。主要是txt格式。形成之后切勿让codex再去更新文档 可添加agent.md进行约束 ,将全局步骤分割各个小模块分割成小文档,再让AI对小模块的开发计划顺序执行,理论上比纯plan mode强,因为plan mode的最后开发计划也属于一种compact。 个人经验看,plan最后的开发计划太长、内容太多,到了最后也要踩坑。spec的小文档不够小也会引发上下文惨案。 祝你好运! 8 个帖子 - 3 位参与者 阅读完整话题