Async communication is like gzip compression for humans—more upfront processing, but greater throughput with fewer packets.
What the heck is asynchronous communication anyway?
Async is a game-changer even for co-located teams, but it's an absolute must for teams collaborating remotely.
What the heck is asynchronous communication anyway?
Async is a game-changer even for co-located teams, but it's an absolute must for teams collaborating remotely.
Asynchronous Communication Is The Future Of Work | I Done This
Whether you fear its impersonal nature or thinks its the best thing since streaming television, asynchronous communication is here to stay Remote work is rising and online education is becoming more accepted and commonplace, both due to changing attitudes and the pandemic. These factors are only going to increase the…
Working from Home and Phatic Communication
Working from home, being what’s called a remote worker, is a really fascinating frontier of Work. It’s fascinating both because as a paradigm, it creates new challenges, and it also mak…
Why writing matters in remote work — Tim Casasola
In remote work, we communicate primarily through writing. We send messages in Slack. We document projects in Notion. We send meeting invites with a written description of the purpose. We’re writing all the time. Many organizations are working from home at the moment. Thus, writing is even
Why Remote Work Is So Hard—and How It Can Be Fixed
The challenges aren’t just technological. They’re managerial.
be diligent
For individuals It's challenging to work a process when it moves slower than feels appropriate. In the context of computer conversations, the tactic of s...
The Unbearable Slowness of Being: Why do we live at 10 bits/s?
Researchers at Caltech quantify human behavioral information throughput at approximately 10 bits/s across various tasks, highlighting a vast discrepancy with the brain's sensory input capacity,...
Fragile narrow laggy asynchronous mismatched pipes kill productivity - Tristan Hume
Something I’ve been thinking about recently is how when I’ve worked on any kind of distributed system, including systems as simple as a web app with frontend and backend code, probably upwards of 80% of my time is spent on things I wouldn’t need to do if it weren’t distributed. I came up with the following description of why I think this kind of programming requires so much effort: Everything is fragile narrow laggy asynchronous mismatched untrusted pipes. I think every programmer who’s worked on a networked system has encountered each of these issues, this is just my effort to coherently describe all of them in one place. I hope to prompt you to consider all the different hassles at once and think about how much harder/easier your job would be if you did/didn’t have to deal with these things. I think this is part of why web companies like Twitter seem to have so much lower impressiveness per engineer productivity than other places like game companies or SpaceX, although there’s other pieces to that puzzle. While part of the difficulty of distributed systems is inherent in physics, I think there’s lots of ideas for making each part of the problem easier, many already in common use, and I’ll try to mention lots of them. I hope that we as programmers continually develop more of these techniques and especially general implementations that simplify a problem. Like serialization libraries reducing the need for hand-written parsers/writers, I think there’s a lot of developer time out there to save by implementing generalized solutions where we currently painstakingly reimplement common patterns. I also think all these costs mean you should try really hard to avoid making your system distributed if you don’t have to.
The Power of Asynchronous Communication
Asynchronous communication allows us to maintain the essential bonds of friendship and dialog with the people that matter to us.
Secure coding technique: Default behavior of Zip libraries can lead to Remote Code Execution - Blog
This week we are going to talk about the default behavior of Zip libraries. If you are an application developer, it is very likely that you have used this before. Most resources that are downloaded over the internet are in zip format, this makes sense; compressed data is smaller, so it downloads faster and consumes less bandwidth.
The Stress of Remote Working | HackerNoon
In software engineering, remote working makes a lot of sense since, most of the time, you only need a computer and an internet connection to perform your duties. So there are fewer reasons to force people to sit in a predefined office everyday. Consequently, it has become an important feature of a lot of IT jobs, even in Belgium, while it is definitely not the most forward looking job market. That said, most of the time, the remote working offer only apply to a part of the week (1 or 2 days a week seems to be the most frequent proposition here). Nevertheless, it definitely is getting a hold in most companies.
DSPy on Twitter / X
DSPy is the highest-bandwidth language to talk to computers in a just-precise-enough way.First 36 lines below:1. Take arbitrarily long content: `chunks`.2. Build a global Table of Contents.3. Distribute chunks into sections to be written.4. Recursively write each section. pic.twitter.com/7NN61isFLs— DSPy (@DSPyOSS) May 13, 2025
The Cost of Ephemeral Communication
Modern communication is built for the scroll. Think: Slack and Discord chats, disappearing messages, DMs, and social feeds. But when it’s the only system of record, ephemeral channels quickly erase institutional memory.
