惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

量子位
T
The Blog of Author Tim Ferriss
U
Unit 42
Microsoft Security Blog
Microsoft Security Blog
WordPress大学
WordPress大学
Vercel News
Vercel News
MongoDB | Blog
MongoDB | Blog
P
Proofpoint News Feed
D
DataBreaches.Net
The GitHub Blog
The GitHub Blog
大猫的无限游戏
大猫的无限游戏
C
Check Point Blog
Blog — PlanetScale
Blog — PlanetScale
I
InfoQ
Y
Y Combinator Blog
F
Full Disclosure
B
Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
G
Google Developers Blog
博客园_首页
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
月光博客
月光博客
博客园 - 三生石上(FineUI控件)
博客园 - 叶小钗
S
SegmentFault 最新的问题
腾讯CDC
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
V
Visual Studio Blog
Apple Machine Learning Research
Apple Machine Learning Research
人人都是产品经理
人人都是产品经理
Recent Commits to openclaw:main
Recent Commits to openclaw:main
The Register - Security
The Register - Security
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Microsoft Azure Blog
Microsoft Azure Blog
云风的 BLOG
云风的 BLOG
Last Week in AI
Last Week in AI
F
Fortinet All Blogs
C
CXSECURITY Database RSS Feed - CXSecurity.com
Hugging Face - Blog
Hugging Face - Blog
T
Threatpost
GbyAI
GbyAI
G
GRAHAM CLULEY
L
Lohrmann on Cybersecurity
T
The Exploit Database - CXSecurity.com
P
Palo Alto Networks Blog
L
LangChain Blog
T
Tenable Blog
C
Cisco Blogs
T
Threat Research - Cisco Blogs
Google Online Security Blog
Google Online Security Blog

Pierce Freeman

A browser for agents | Pierce Freeman The grey market of podcast appearances The way I travel | Pierce Freeman Fixing slow AWS uploads | Pierce Freeman Local tools should still use vaults We solved scratch content first Starting a podcast in 2025 Being late but still being early Automating our home video imports Adding my parents to tailscale A deep dive on agent sandboxes Language servers for AI | Pierce Freeman My simple home podcast studio We need centralized infrastructure | Pierce Freeman Coercing agents to follow conventions using AST validation My unified theory of social selling My personal backup strategy | Pierce Freeman July updates to the homelab How the KV Cache works httpx is the right way to do web requests in Python Reputation is becoming everything | Pierce Freeman Building a (kind of) invisible mac app Updated knowledge in language models Making an ascii animation | Pierce Freeman How speculative decoding works | Pierce Freeman Under the hood of Claude Code Doing things because they're easy, not hard Speeding up sideeffects with JIT in mountaineer Firehot for hot reloading in Python Misadventures in Python hot reloading How text diffusion works | Pierce Freeman The tenacity of modern LLMs The ergonomics of rails | Pierce Freeman How language servers work | Pierce Freeman Just add eggs | Pierce Freeman Unfortunately SEO still matters | Pierce Freeman The futility of human-only web requirements Setting up Input Leap | Pierce Freeman Checking in on Waymo | Pierce Freeman The react revolution | Pierce Freeman Speeding up many small transfers to a unifi nas Quick notes on swift libraries AI engineering is a different animal San Francisco | Pierce Freeman Debugging a mountaineer rendering segfault Local network config on macOS Building our home network | Pierce Freeman Introducing Envelope.dev | Pierce Freeman Legacy code and AI copilots Typehinting from day-zero | Pierce Freeman Generating database migrations with acyclic graphs Lofoten | Pierce Freeman Mountaineer v0.1: Webapps in Python and React Constraining LLM Outputs | Pierce Freeman Passthrough above all | Pierce Freeman Accuracy in kudos | Pierce Freeman How quick we are to adapt The curious case of LM repetition Costa Rica | Pierce Freeman Debugging chrome extensions with system-level logging Speeding up runpod | Pierce Freeman Inline footnotes with html templates Parsing Common Crawl in a day for $60 An era of rich CLI The Next 10 Years | Pierce Freeman Adding wheels to flash-attention | Pierce Freeman LLMs as interdisciplinary agents | Pierce Freeman New Zealand | Pierce Freeman Representations in autoregressive models | Pierce Freeman Let's talk about Siri | Pierce Freeman Minimum viable public infrastructure | Pierce Freeman Reasoning vs. Memorization in LLMs Automatically migrate enums in alembic Greater sequence lengths will set us free On learning to ski | Pierce Freeman Dolomites | Pierce Freeman Using grpc with node and typescript Opportunity years | Pierce Freeman Buzzword peaks and valleys | Pierce Freeman Buenos Aires | Pierce Freeman Network routing interaction on MacOS Independent work: November recap | Pierce Freeman Debugging slow pytorch training performance The provenance of copy and paste Debugging tips for neural network training Patagonia | Pierce Freeman Santiago | Pierce Freeman My 2022 digital travel kit AWS vs GCP - GPU Availability V2 Independent work: October recap | Pierce Freeman Planning Patagonia | Pierce Freeman Relationship modeling | Pierce Freeman The power of status updates A new chapter | Pierce Freeman Give my library a coffee shop AWS vs GCP - GPU Availability V1 Switzerland | Pierce Freeman Headfull browsers beat headless | Pierce Freeman Webcrawling tradeoffs | Pierce Freeman Copenhagen | Pierce Freeman
All or nothing with remote work
2023-09-04 · via Pierce Freeman

Since there's nothing that starts flame wars more than talking about remote work, hope you brought your matches.

I find myself thinking of remote work a lot when I'm on trains to somewhere new. It means we're saying goodbyte to our old rythms and need to figure out everything from scratch - where to work, where to get coffee, where to work out. In Cascais we solved for some of these by joining a local coworking space.1 More than 80% were remote workers.

Covid was the largest natural experiment we've seen within the last 50 years. It forced adaptation in places that otherwise see no need to change. And that proved a few things to me:

  • Companies can add tech and policies to faciliate remote work. Even notoriously secretive companies (consulting groups, lawfirms, etc) were able to configure remote working tools to their infosec policies. And they adapted very quickly when productivity was on the line.
  • Most BigCo executives had never even considered remote work. It's not that they weighed the pros and cons and picked the office. They didn't entertain it as a reasonable choice or the purview of "serious companies".
  • People can be equally productive at home but bosses typically trust them less. That can impact career growth especially when you're competiting with people who are in person. There's game theory to the individual choice to go to the office when it's presented as an option.
  • The main increase in productivity typically comes from fewer breaks and sick-days. On average people seem able to lock in both in person and remotely about the same.

Some companies jumped the gun a bit on permanent policy changes though:

The company said if employees are in a role and situation that enables them to work from home and they want to continue doing so “forever,” then “we will make that happen.”

Musk emailed employees at 2:30 in the morning, writing that "office is not optional." In the email, he complained that half of the San Francisco headquarters was empty the day before.

-- Twitter 2020 vs. 2023

Like clockwork, the same arguments are usually raised on one side and the other. I'm ignoring the work-life balance of remote work not because it isn't important in life, but because companies are always going to want to maximize throughput.

Pro Remote:

  • More focus and fewer distractions to actually getting work done
  • Less time on commute means more time for work
  • Better talent when searching worldwide
  • Forced documentation of processes and knowledge because it's built into decision making culture

Pro Office:

  • People are less productive at home
  • People need to be in the office to be creative or collaborate
  • People build community in person and a corporate culture helps people stay engaged
  • People need to be in the office to learn

What seems clear to me: there's no definitively right answer. Some people prefer the atmosphere of working in person. Some people hate the commute and need the peace of their own space to do their best work. The answer is clear at the personal level. At the organization level, it's impossible to say.

This leads to a tension in established organizations. There's a tug from the management to get back in the office. That's a question of personality (more extroverts in management than introverts) and job description (supervision is easier when you're in the same room). Among people actually doing the work it's a harder question. How much space you need to process information, where do you do your best work, how much deep focus you require, etc?

If a company starts from scratch, it has an inherit advantage. You can choose to recruit from the pool of people who prefer in-office work, or choose to recruit from the people that prefer remote only. If expectations are clear up front you can make sure to hire the right people given your priority set. The difficulty in larger companies is they already have a mix of those people, either from covid where everything was remote or when people discovered their preference was actually working remotely.

Hybrid is the worst of both worlds. You're obligated to be in-person a few days a week, but there's probably a few people on your team that are remote that same day. So you've just sunk time into the commute only to hop on the same Zoom call you would have done at home. One wasted hour of productivity for zero increase in collaboration.

This poses a huge opportunity for startups that make a choice from the get-go and don't waver. They know exactly the talent pools to choose (Github of the best engineers worldwide vs local personal networks) and can build a culture that matches their needs.

Either 5 days in the office or 5 days remote. For me there is no in-between.

  1. I do wish WeWork had waited to go bankrupt until it became a verb. It has a way better ring to it than coworking. ↩