置顶嘟文

本转码选手 参加了第一次周赛!AC了两道题!!我膨胀了!! :ablobgrin: 还有没有象友在用js刷题,一起mock改简历不 :blobcatboo:


最近喜欢的古典音乐youtuber。有时候又觉得人类可以创造这么美好的音乐,不应该灭绝 :ablobmeltsoblove: :blobsad: youtu.be/YRCHnIUaZ9w

摇滚年关闭后,我和一些朋友在163相册重逢;163相册没落后,我和一些朋友又在博客大巴、搜狐博客、songtaste陆续相遇;songtaste没了后,虾米偶尔还能见到一些熟悉的身影——直到虾米也没有了。
这些重逢,无一例外都是在茫茫ID中辨识出对方,小心地试探,惊喜且短暂的寒暄,然后归于沉寂。
少数朋友加了QQ,甚至面过基,交流依然随着平台的流逝而消散——直至某一天,我连QQ密码也再想不起。
一旦平台不在,曾经的社区氛围、互动方式改变后,就很难再延续交流。
赛博世界,人和人的关系很难突破平台创造的那个虚拟小宇宙,有机的移动到另一个宇宙。
任何一个成熟的社区都是不可替代的,一旦死了,就是死了。
——
道理是这么个道理,作为一名赛博遗老,这二十年不可谓不是看尽花开花落,潮涨潮消,聚散离合。一直笃信万事随缘即可。
但如今我的看法有些改变:当下的消散,跟过去我经历的任何一种消散都不一样——以前那些基于个人情绪、群体关系、商业行为,自发产生的自由的聚散,与翻云覆雨手打出一套从天而降的掌法,截然不同。
所以,珍惜同温层吧,可能在未来更寒冷的日子里,那是抵御失温的救命毯。
[写在豆瓣的话,同步一下

刷题面试和被面试多年(并没有)的经验,我的一点拙见,轻踩 

逼逼,逼逼就完事了 :ablobdundundun:

刷题和面试太不一样了,要我说刷个差不多五十题就应该开始去找人模拟面试或者试着给人讲题,别管地里那些什么四五百题才能去面试的。。。也不是说不行,纯粹靠肌肉记忆当然也有效果,但是明明可以靠和面试官合作完成的事情为啥非得执着于这种折磨人心智的做题家思路。。

我在前司起码面了几十个 new grad,基本都是 berkeley 的本科亚男,题目是万年不变的 word search ii,首先对方不管懂不懂都会直接开始一通说,带着一种迷之自信的气场,作为面试官的我也容易进入和对方一起讨论的环境中,并且更容易引导对方往 trie 的思路上面去想,我在写 feedback 的时候也能写说讨论之后对方自己想出了 trie 解法云云。

说实话一开始做面试官我简直 imposter syndrome 疯了,我算哪根葱面试这些天才儿童。。后来慢慢发现咱基础也没有差太多就是缺这见招拆招的从容自信,慢慢也就没那么妄自菲薄了。

同时也想强调模拟面试的重要性,刷题是有边际效应的,刷到一定程度就应该把重心慢慢挪到准备真正的面试上面,如何简洁准确地传达你的思路,如何边想边说边写,如何在 coderpad 里面用光标高亮选中来给对方像讲幻灯片一样地讲代码实现还有走一遍 test case,这些都和刷题一样重要,都需要加以练习,正式面试的时候就不会那么紧张了。

PS 如果有象友需要 mock 的话欢迎来问我,我愿做小黄鸭 :mtfront_duck:

感恩节购物repo:健身环和just dance很香,买来以后几乎每两天都有运动一次。塞尔达还挺好玩的,太花时间了,拜托室友帮我藏起来了🥲

【leetcode第二天】推荐leetcode的study plan,不用自己选题目…无脑做题就好了🥲强制刷题小帮手(因为身份限制要拖到晚一点才能投简历了 哭哭 我也很想面向面试学习啊)

在毛象上刷到一条推荐这个reddit上关于junior dev求助的帖子:
reddit.com/r/webdev/comments/8

读下来作为senior倒是学到了一些关于如何mentor和expect的点。

觉得写得最有意思的两条回复:

❝When I hire a junior dev, I'm not looking so much for experience as aptitude. I know you are not going to be a full contributor immediately. I do not expect you to refactor the codebase your first week. I'm looking for someone who thinks the right way; I'm gonna teach you what you need to know.

The first few months are literally just training you on how our huge architecture and millions of lines of codebase works. You'll work with a variety of our senior devs and team leads on tasks that introduce to you our workflow. If the timing works out, we send you to a conference or two, usually with some strong suggestions on which panels to attend.

The fact that they're giving you training is a positive! Why would I invest time and money in training someone I didn't think had potential? So they obviously see something in you even if you don't entirely see it yourself.

The point is, we don't expect our junior devs to be full contributors until about six months in. We don't even count them into our sprint calculations until about month 4. It may be more than a year before they are fully confident in working on their own.

The other thing I try to do is give constant feedback to our juniors so they know where they stand. It sounds like this might be where the disconnect is for you. I was having a beer with one of our juniors at a conference a few years back and he opened up about how he thought he was so far behind and was thinking about quitting.

I was like, "Dude, you're doing fine, you're right where you're supposed to be." He looked like he was about to cry and the world fell off his shoulders. Since then I try to check on in juniors weekly or so just to reassure them that they're doing okay and/or provide feedback, although I will admit to being lax about this recently because I've been slammed. So maybe ask your peers for honest feedback.❞

❝Communicate. Ask questions. Restate things to make sure expectations are clear. When you realize something is wrong, give a status update. Your manager/lead/project manager will be much happier to hear, "this looks like it might take twice as much time" with a week to go rather than, "I only got halfway through this effort."

Set a time limit for how long you are willing to grind on a given problem before asking for help. This is something our organization just implemented per scrum team because even experienced developers often don't know when to ask for help.
These things can help you find a better solution you might be missing, or alert the entire team to a big problem they may be able to avoid. Even if nothing can be done to fix a 2x increase in dev time, at least people know.

Be kind. To yourself and others. We all have different experiences and strengths. People have wildly different feelings and reactions to asking for help, to being helped, to learning something, or to being corrected, so don't beat yourself up or berate others for not knowing something. Even things that seem like basics might be foreign to someone who transferred roles or doesn't work in a language as often.

Sometimes we just need a fresh perspective to get un-stuck. Sometimes there's some crucial knowledge we had no other way to acquire. Sometimes we make a mistake or an assumption. Nobody is perfect or infallible, so don't expect it from yourself or others.❞

问:你不生小孩,你爸妈看到别的同龄人抱孙子,会很羡慕的。
答:羡慕羡慕习惯就好,我看别的富二代开法拉利也羡慕呢,我不也没怪我爸妈不买给我。

我好爱just dance!!快乐运动了一小时,要是早点买就好啦!!! :ablobmeltsoblove: (该嘟嘟来自一个 前健身房zumba 爱好者

我终于学会mongoose和express了 :ablobcatattentionreverse: (第一遍学的时候arrow function、OOP还不熟,现在都能看懂啦!)

周日晚上清点完食材存货以后修订了一遍冰箱白板贴上的meal planning清单。写完突然觉得读上去就很好吃的样子,所以决定发一下!

推荐买个这种磁性冰箱白板贴(大概15$),能大大提升meal planning体验。

我分了「可做」「待用」「需买」三块。平常的流程是周末买菜筹备好做什么并写进「可做」,工作日看看清单给自己点菜就行,吃完一样就就擦掉一样,擦得差不多了就知道该买菜了。

暂时还没有具体计划的食材写进「待用」免得忘记。有什么想吃的就写进「需买」,下次采购一起搞定。

这样提前计划可以保证每天都吃得均衡健康,同时不会有太多用不完的食材被浪费掉。节约了很多时间,也在meal planning上省了很多脑容量。

字丑所以手动列一下「可做」里的菜:
- 白萝卜连锅汤
- 咖喱鱼蛋乌冬面
- 烤鸡夹馕+彩椒
- 番茄鸡蛋焖肉丸通心粉
- 炒四棱豆
- 双色蒸饺
- 煮花豆
- 腊肠焖饭
- 芽菜肉臊面
- 虾仁丝瓜
- 味噌汤
- 烤红薯
- 椰丝燕麦红莓粥
- 豆豉烧肉
- 香辣粉蒸排骨

每顿还会开水30s烫一碗leafy greens一起吃,这个就没有具体写出来了。

个人博客试了hexo,hugo都莫名失败,最后还是用了wordpress.com :blobsad: (这个表情系列好可爱啊


今天刚学了SASS!太棒了啊哈哈哈哈哈哈!CSS真的好难用啊> <
简历里一个能看的项目都还没有呢,快点开始吧!

我会对现状感到痛苦只是因为我是如此忠于我受到的教育,关于正直、善良、勇气、智慧与人性。当看到中大学生会关闭,发文问为什么我们的学生组织不能谈政治,我就要想到1919年北京大学的学生组织谈政治谈马克思主义。当我看到网络禁言和越来越近的审查机制,我就要想到防民之口甚于防川,川壅而溃伤人必多。有那么多人和我一样从小接受这样的教育,为什么大家可以在现状面前假装没什么不对劲?为什么大家合起伙来撒谎让善良的人变得不安,让诚实的人自我怀疑,让天真的人心灰意冷?

学着deploy博客 弄了一晚上还是失败了啊啊啊啊啊啊啊…换个教程吧 :blobsad:

实在不堪USCIS每天查询状态的煎熬,决定自动化信息获取的流程。
晚上折腾了半天做了个telegram bot,定时去USCIS网站抓取数据,然后给我和家属发送最新的case status update。从此解放鼠标点击,每天刷刷telegram bot消息就能知道最新进展了 :douchi_cat_roll:

follow了这个教程:betterprogramming.pub/automate

对了 我还在中间穿插看了一阵子Java课和模拟电路数字电路课…后来问了前辈,终于决定专心做项目找前端职位。
上了岸再去读学位啦~好想有很多钱啊,呜呜呜

显示全部对话
显示更早内容
长毛象中文站

长毛象中文站是一个开放,友好,有爱的社区。长毛象中文站主题为喵,汪,各种动物,社交,科技,编程及生活。发言内容只要没有明显违法内容均不禁止。无论你的兴趣点是什么,我们欢迎友好、热情、乐于分享的朋友。

Donate using Liberapay