入职准备&新人第一周&职场规范
准备
git常用命令
linux常用命令
语言常用函数
常用软件下载 FTPfilezilla postman 压测软件 SQLyog 网盘 secureCRT git bash
框架知识
中间件知识梳理
公司服务梳理、接口人、接入方式
设备调试 鼠标 显示器 等
密码本 常用命令
公司平台整理
代码库梳理-》输出文档
梳理业务-》输出文档
梳理流程-》上线流程，开发流程，等等
梳理数据报表和常用SQL
学习接口的监控、报警，学会根据报警查问题。
每天和同事打招呼，把自己每天要做的事说出来，写出来
给大家留下好的第一印象
学英语，多说英语
健身
入职第一周目标
新的软件工程师加入团队，对他最简单有效的考核要求，就是每周必须有代码合并进入主分支。
远超预期的完成领导布置的任务，不要有预期之外的事
主动、积极的做事情
不要坐以待毙，让领导看到自己的行动
完成新人串讲
试用期目标
完成试用期串讲
成为独当一面的软件研发工程师
关注项目的难点亮点（架构、数据SQL、），不要当代码的熟练工
项目入门
如何快速进入项目？项目代码本身可能是一团散沙。我们的目标是学习重要的通用代码
- 看数据报表 & 日志监控
- 明确核心业务，以及对应的核心接口
- 学习核心接口的写法 & 业务逻辑
统计xx 3天内 访问次数前N的接口
applogv2
| where Timestamp > ago(10d)
| where Server contains "xx"
| summarize count() by Uri
| order by count_红线
公司红线，安全相关
不要局限于自己的一亩三分地，看下大团队在做什么，跟上别人的进度
敲的代码一定要和产品的需求保持一致；明确思路逻辑、代码组织；
技术评审3个点：
- 存储。模型，甚至key
- 代码。代码组织、结构，内部api封装
- 页面和接口。
办公椅配置
坐姿对背部和颈椎很重要，但是往往没人告诉你怎么调椅子。
一般来说，椅子有五个可以调的地方：
- 升降
- 坐垫前后
- 弹簧弹力 （旋转）
- 靠背模式-躺&靠
- 初始靠背的位置
职场规范
沟通
沟通是工作的一部分。习惯性回复嗯嗯好的。
有和预期不一致的地方提前说，即时汇报
不要随便承诺，说出来就做到，提高自己的置信度。Build up trust.
积极正面，散发正能量，不要散播负面情绪。
主动、积极的做事情。不要坐以待毙，让领导看到自己的思考。
当有人跟你分配了工作之后，一定要和对方确认清楚你们双方对工作内容的理解是一致的。
如果可以的话，最好约一个完成时间，如果你们对工作时间的认知差别太多，一定是对工作内容的理解出了问题。
如果遇到一个问题卡了很久，一定要及时把问题抛出来，让大家帮你解决，至少让大家知道你遇到了什么问题。
开发过程中遇到问题，都可以及时和大家讨论，积极一点，不用过于害羞，也不用觉得过于丢失你的自尊。
如果一个工作持续时间比较长，一定要及时同步工作进展，不如很容易到最后你需要加班或者delay。
提前写完可以休息，晚点告诉别人；有风险的话就提前开始。完不成的话提前汇报。
给老板汇报的时候要给出详细的解释和解决方案。
目标
我们和老板的关系是互相成就。
老板一般喜欢你主动积极的完成任务，不喜欢去push你。push你的时候你已经危险了。
不要delay
干活
写好每一行代码。别依赖 code review。
不要直接 copy 解决方案，要理解后自己去实现
必须知道自己的每一步是在做什么
做到底。做事情只有0和1，没有0和1之外的其他状态。
敲的代码一定要和产品需求保持一致；明确思路逻辑、代码组织；提高代码质量。
提代码前codeformat；发PR注意title；提PR后跑policytest；代码合进去后，在群里周知下大家
少承诺，多兑现
细节
不要把自己搞的非常忙碌，burn out。抓大放小，关注重要的事
不要把垃圾事情挤压在自己手上，成为自己的包袱
不要局限于自己的一亩三分地，跟上大部队，关注团队的整体进度
靠谱
第一印象很重要。如果你给别人留下的第一印象不好，那么你后续要花费十倍的努力来扭转这一印象。
开会就像是打团。你不能只送关键团。
最后更新于 2023年5月15日 by qlili
https://newsletter.kentbeck.com/p/hey-n00b-we-didnt-hire-you-to-complete
Hey, N00b, We Didn’t Hire You to Complete Tasks
Kent Beck
May 15, 2026
Welcome! I am going to pass on to you the secret to a successful and brief noobitude, and I won’t even keep you in suspense: nobody cares how many tasks you complete. Why not, and what we care about instead are the subject of the rest of this essay.
Look at your situation from our perspective (by “our” I mean “older engineers”). We hired a bunch of people like you. Some of y’all (we’ll call them A’s) will be amazing game-changers, making everyone around them wildly more productive. Many of you (B’s) will be solid performers. Some of you (the C’s) won’t be here in a year.
We seniors have our regular work to do, but we also have to figure out which category you fit into. We support the superior performers as much as we possibly can. We support the solid performers enough to help them mature. Brutal as it seems, we’d like to expend as little effort as possible on people who aren’t going to make it.
It’s your job to get in the category you want to be in and send us the signals that tell us that’s where you belong.
That stack of tasks you have to do? Your manager or your tech lead could finish those in much less time and with much less hassle than it takes to help you through them. If all we cared about was today’s productivity, we wouldn’t have hired you at all. Instead, we (the seniors) are focused on the future: we know there’s going to be far more work here than we could possibly accomplish. We are paying your salary now as the option premium on the engineer you are going to become. If we play this game right, we’ll have a kick-ass next generation of engineers. If not, we’ll have to be doing the same engineering jobs ten years from now, and we really don’t want to be doing that.
This quarter’s newsletter is brought to you in partnership with WorkOS.
WorkOS is the infrastructure B2B and AI-native companies use to sell to enterprise. It covers everything enterprise security requires: SSO, SCIM, RBAC, Audit Logs, AI governance, and more. Engineering teams ship it in days. Trusted by 2,000+ fast-growing companies, including OpenAI, Anthropic, Cursor, and Vercel.
Find Out More
The Sorting Hat
Noob A accomplishes 40 tasks this quarter. Noob B accomplishes 20. Which is better?
Not enough information. What if all the tasks were the same difficulty? Then which is better? Still not enough information. Remember, we’re trying to figure out if you’re an A, a B, or a C. What is the information we require to figure that out?
B or C?
The first level of sorting is figuring out if you’re a B or a C. Here are goals that are more important than closing your task in the absolute minimum time:
Any attempt to game the system by claiming to have done work you haven’t done marks you immediately as a C. Assume you can’t game this system.
You will send out some C signals. That’s inevitable. We all did. Never, never send out the same C signal twice. And make sure the balance of the signals are that you are a B.
A or B?
The second level of sorting is, given you’re at least a B, are you an A? What distinguishes A’s is not how many tasks they close, but how much they learn from each task. Remember, your productivity sucks by our standards. We expect that. It’s the first derivative of your productivity that we’re looking for. Here are some signals that you’re an A:
Isn’t it nice that the “kick ass” list is so much longer than the “don’t mess up” list? You have many ways to shine.
All the A signals share one trait—they take longer than just doing the work necessary to close the task. This isn’t permission to spend forever on shiny side-bars. Always get the task done in a reasonable amount of time, just not the absolute minimum time.
But You’re Already Busy
You may be wondering where this “extra” time is going to come from. You’re already committed up to your eyeballs. That’s where Everything You Need To Know About Programming But Didn’t Know To Ask [ed: to be written] comes in. We’ll talk about time management, task queue management, diff queue management, and other topics that will accelerate your progress.
Take the time you save and invest it in yourself in ways that benefit others. That’s what we’re looking for.
一个政治人物不怕被人骂，但是怕被人笑话
和环境相关的，都使用配置
学习Anna 画文件夹的思维导图