拿不同 offer 互相 compete 互相备胎挺正常 公司招人也这样
但你都接了再 last day 撕 offer 确实不好

爬了爬自己的回复，准也不准，没啥超出我预期的东西...

也挺神奇 你们这些人结婚到底是为了啥

你站仇女跟其他平台上仇男只能说一体两面 非常适配 俗称歪锅配翘锅盖

在国内的时候还真线下见过一个你站网友 不过后来也不联系了

因为相机相比电脑确实贵一些 被先入为主了
一两万的相机确实挺平平无奇的 大概也就是索尼 a74+2070g 的水平？

跟微信一样 你国特色

@V2Try
试试支持 HomeKit(HKSV)的摄像头？

cmos 面积和镜头规格摆在那 你指望长焦能有什么表现…

所以你咋按的键
随手试了试没有问题

印度朋友
怕不是遇上印度人只招印度人了

@ryd994
我的锅 忘了 bracket 这事了
每年报税都是稀里糊涂的

@ryd994
把 401 / espp 算进去是什么鬼算法😂

@ufan0
加州州税大部分人应该落在 9%左右这一档
如果联邦税又落在 32%这一档以上那加起来就有 40%了 这还没算 FICA

@NeoMatrix
噗…
行吧 coe 有的写了

@NeoMatrix
对我写的不太清楚 不是 ddb 的问题
话说回来这么核心的网络配置改变没有 review 就上 prod 么⋯不知道这些人得写几个 coe

要不…试试坚持听下去磨耳朵

说明你站用户挺多单身话多又没啥钱的人呗

看上去一开始是 dynamo dns endpoint 解析出问题 修好以后变成经典 circular dependency

aws 你这 system design 做的也不行啊
Between 11:49 PM PDT on October 19 and 2:24 AM PDT on October 20, we experienced increased error rates and latencies for AWS Services in the US-EAST-1 Region. Additionally, services or features that rely on US-EAST-1 endpoints such as IAM and DynamoDB Global Tables also experienced issues during this time. At 12:26 AM on October 20, we identified the trigger of the event as DNS resolution issues for the regional DynamoDB service endpoints. After resolving the DynamoDB DNS issue at 2:24 AM, services began recovering but we had a subsequent impairment in the internal subsystem of EC2 that is responsible for launching EC2 instances due to its dependency on DynamoDB. As we continued to work through EC2 instance launch impairments, Network Load Balancer health checks also became impaired, resulting in network connectivity issues in multiple services such as Lambda, DynamoDB, and CloudWatch. We recovered the Network Load Balancer health checks at 9:38 AM. As part of the recovery effort, we temporarily throttled some operations such as EC2 instance launches, processing of SQS queues via Lambda Event Source Mappings, and asynchronous Lambda invocations. Over time we reduced throttling of operations and worked in parallel to resolve network connectivity issues until the services fully recovered. By 3:01 PM, all AWS services returned to normal operations.