Jun retweeted
JUST IN: Riemann Hypothesis has been solved.
alpo.ge/remark.pdf
Jun retweeted
And to clarify: Guzzle, Symfony HttpClient and curl were all fine!
This was only affecting PHP's stream wrappers: getimagesize, exif_read_data, simplexml_load_file, DOMDocument::load, md5_file, SOAP WSDLs, ...
Im tired boss
‼️ BREAKING: A 10-year-old flaw in #NGINX could let attackers execute code on servers — no login required.
Dubbed #nginx2root (CVE-2026-123007), the critical HTTP/2 vulnerability scores 9.2/10.
Public PoC available. Patches released.
Full details ↓ thehackernews.com/2026/11/10…
7
Now I can larp
Go is a language of experienced engineers.
66% of Go developers have 6+ years of professional coding experience, compared with 49% of all developers. Only 3% have less than a year.
More in the State of Go 2026: jb.gg/2hxegd
#golang

ALT Pie chart titled "How many years of professional coding experience do you have?" showing percentages: 0.8% have no coding experience, 2.3% have less than 1 year, 8.7% have 1–2 years, 22.4% have 3–5 years, 27.8% have 6–10 years, 17.5% have 11–15 years, and 20.4% have 16+ years. "State of DevEco Survey 2026" mentioned at the bottom.
13
Jun retweeted
我一个朋友,35岁,在深圳某大厂干了9年,月薪4.8万,上个月被裁了。
这哥们是搞基础架构的,技术牛到什么程度?
Linux内核参数、Nginx负载均衡、Redis Cluster、MySQL主从复制、Kafka消息队列、Docker容器化、Kubernetes集群调度,随便拎一个出来,他都能跟你聊到天亮。
尤其擅长处理线上事故。
有一年618大促,凌晨1点17分,生产环境突然出问题。
K8s集群里的Pod疯狂重启,CPU直接打满,Prometheus报警像放鞭炮,Grafana上十几条曲线同时飘红。
业务负责人在群里疯狂@人。
他从床上爬起来,打开MacBook,SSH连上跳板机,先查kubectl logs,再看OOMKilled,最后发现是某个服务的JVM堆内存设置不合理,叠加流量突增,触发了连锁故障。
他一边调整HPA自动扩容,一边通过ArgoCD回滚版本,半个小时把核心服务拉了回来。
第二天老板给他发了2000块红包。
说了一句:“公司离不开你这种技术骨干。”
这句话他记了三年。
后来公司开始降本增效。
他带头搞自动化运维,把Ansible、Terraform、GitOps全套打通,又接上AI Agent,实现了自动分析告警、生成故障报告、辅助执行回滚。
以前6个人轮班维护的系统,现在3个人就能管。
老板非常满意。
年底开会,还特意表扬了他的技术贡献。
结果第二年,部门调整,基础架构团队从12个人缩减到5个人。
裁员名单里,第一个就是他。
理由是:
“你这个级别的工程师,成本太高了。”
他当场问了一句:
“这些自动化系统谁来维护?”
领导回答:
“你把文档交接清楚就行。”
那天晚上,他一个人坐在停车场,抽了半包烟。
9年时间,他把公司服务器的可用性从99.5%做到了99.99%。
每年替公司省下几百万运维成本。
最后公司发现,最容易优化掉的成本,竟然是他自己。
最讽刺的是,他离职那天,收到最后一条Prometheus告警。
不是服务器故障。
是公司把他的监控账号禁用了。
Jun retweeted
Who are Go developers in 2026, and how is AI changing their work?
For Go’s 17th birthday, we looked at the Gophers who participated in the JetBrains Developer Ecosystem Survey 2026 and found seasoned engineers, a comeback for the standard library, and AI agents everywhere.
Here’s the State of Go in 2026: jb.gg/2hxegd
#golang
Jun retweeted
Vorrei ricordare al governo cinese che sono in possesso di informazioni essenziali allo sviluppo delle intelligenze artificiali.
This quoted post is unavailable.
Jun retweeted
"this is bullish because it confirms CEO is not gay"
Jun retweeted
BREAKING: Nvidia, $NVDA, CEO Jensen Huang sends a company-wide email regarding his recently reported relationship with a Chinese spy.
Jun retweeted
i was reminded of this blog from 2016 on visualizing concurrency in go today. i might start having opus visualize my programs this way
divan.dev/posts/go_concurren…
Jun retweeted
I'm not even sounding the claxon for this it's just horrible.
Any text > 256chars is a valid root password, holy shit
sshhole.com/
A new Go API for JSON go.dev/blog/jsonv2





































