I disagree with smaller docs being easier to write. Quite the opposite, it is easy to write longer text, which then requires more effort from the reader to understand it.
To write shorter text, you must put in the effort beforehand to compact, crystallize and organize the ideas. Each reader then doesn't have to do that themselves in their heads.
Maybe not save "us", but possibly the Rohingya during the Myanmar genocide, which was fueled by hate speech and disinformation spread through and promoted by Facebook.
My impression is that the current Sonos app becomes unusable when your home Internet connection is unstable. It usually works fine here, but when our 5G starts switching channels due to a snowstorm, the Sonos app becomes erratic.
I understand there's also issues with mDNS discovery and maybe other things, but the worst mistake seems to be the assumption that everybody has a stable Internet connection all the time.
There are other apps that have made a similar mistake. E.g. Ubiquiti's UniFi management app has problems connecting to the local LAN console if you originally signed in using a cloud account and Internet becomes unstable.
One app that handles this right is the Home Assistant Companion app. It detects when you're using a local WiFi SSID and connects directly to the internal LAN address which always works, and otherwise uses the cloud connection or public WAN address.
Whenever I have created API keys for a product, this is the #1 feature I want: easy copy-pasteability. Just letters and numbers, no special characters that break double-click-selecting the key.
AWS SDKs handle some important stuff though, such as retrying database operations with backoff delays. Without it your app will fail in unexpected situations because the cloud service is designed to be stateless and return specific error codes when the client needs to retry.
For me, 2024 was the year I finally got completely rid of Windows and switched fully to Ubuntu on all computers. I had kept Windows for playing Steam games, but I realized Proton will play them just fine on Linux when you enable it in the Steam compatibility settings.
It feels really good to get rid of WSL, Docker in VM and other hacks that kind of make Windows work for development, but always cause various issues. Developing natively on Linux just lets you forget all those hacks.
One thing I also did was switch from NVIDIA RTX to Radeon RX. I haven't had to worry about GPU drivers and settings and heat issues in Linux after that.
There are many interesting Web3 apps, like decentralized social media, decentralized web (IPFS), decentralized domain names, decentralized organization management, etc, but they have not seemed to mature enough to become mainstream. They all have various kinds of problems with usability especially for "ordinary people". But the core idea is there and it's good: Make the Internet truly decentralized and peer-to-peer again, and enable it by incentivization via crypto transactions. But it's going to take time.
If you use your own Docker images, you lose one of the main benefits of Lambda, which is that AWS will take care of automatically patching all the security vulnerabilities in the infrastructure platform. My goal is always to outsource as much of the code as possible to AWS, and implement myself as little as possible.
In my view, the big promise of server-side WASM is to have an evergreen platform that doesn't need regular updates to the application. Just like HTML web pages work "forever" in browsers, WASM-based applications could work forever on the server-side.
Currently it is a huge PITA to have to update and redeploy your AWS Lambda apps whenever a Node.js or Python version is deprecated. Of course, usually the old code "just works" in the new runtime version, but I don't want to have to worry about it every few years. I think applications should work forever if you want them to, and WASM combined with serverless like Lambda will provide the right kind of platform for that.
Yes indeed. I did a quick search and it's really difficult to find images of that original color scheme. I have fond memories of long coding sessions in Turbo Pascal 3.x with the black background and green and white text.
Delphi was great too and I probably spent an order of magnitude more time in Delphi, but I have fonder memories of Turbo Pascal
To write shorter text, you must put in the effort beforehand to compact, crystallize and organize the ideas. Each reader then doesn't have to do that themselves in their heads.