Browse tags
  • 🔗 Free is a Lie (2014)

    Privacy is between me and myself. Privacy does not mean between me and Google. Privacy does not mean between me and Facebook...Violating privacy violates the United Nations of Human Rights.
    I don't have a specific quote, but I quite enjoyed this talk from Aral (of Small Tech). The premise of the talk is something that most people are familiar with, free (ala Google/Twitter/FB) silos aren't free, but you pay with your privacy. ( This blog respects your privacy and doesn't track you).

    But what really made me think was the chart quadrant chart comparing Open Systems and Closed Systems on Features and Experience. In the upper left Closed / Features you have the leader: Microsoft. Next to that is Closed / Experience, where Apple and Google lead.

    What's in the bottom half where open systems preside? Open source can compete with features, but they often can't compete on experience. Most people care about experience more than they care about features. An entire quadrant of the chart has no competition from open systems!

    And since there's no competition in from open systems on the experience front, the system is going to arch closed. In order to have an open future, open systems must compete not only on features, but also on experience as well. 

    Competing on experience is increasingly difficult as more systems have some kind of hosted server component. I think about this in regards to Tanzawa on a regular basis, but I haven't figured out a model that I think would work.
  • 🔗 Frugal computing: On the need for low-carbon and sustainable computing and the path towards zero-carbon computing

    On the need for low-carbon and sustainable computing and the path towards zero-carbon computing.
    Computing and infrastructure currently use around 11% of the world's electricity and is projected to grow 3 - 4 times over the next 20 years. As makers of software (and hardware) we've got to find a way to extend the lifespan of devices for as long as possible.

    Taking into account the carbon cost of both operation and production, computing would be responsible for 10 GtCO₂e by 2040, almost half of the acceptable CO₂ emissions budget

    The report about the cost of planned obsolescence by the European Environmental Bureau [7] makes the scale of the problem very clear. For laptops and similar computers, manufacturing, distribution and disposal account for 52% of their Global Warming Potential (i.e. the amount of CO₂-equivalent emissions caused). For mobile phones, this is 72%. The report calculates that the lifetime of these devices should be at least 25 years to limit their Global Warming Potential.

    25-years on the same mobile phone. I can't even imagine. I'd love it if that were possible in today's world. Maybe if it was a "dumb" phone. But even then wireless network's lifespans aren't even that long these days. 

    I used my iPhone 6S+ for around 4 years until a pin broke on it and I could no longer charge it. "Repairing" it (my first option) would have meant getting a new iPhone 6S+ for half the cost of a brand new iPhone XR. I hope I can keep my phone for at least as long as I've had my current computer (7 - 8 years).
  • 🔗 Reaching people on the internet in 2021 - The Oatmeal

    A comic about social networks.
    Fantastic comic from the oatmeal about reaching people on the internet. I don't have a mailing list, but I feel the pain – hence Tanzawa.

    Reaching People on the Internet
  • 🔗 Django & Celery in production

    DjangoCon JP 2021 発表資料

    Djangoで非同期処理を実現するために、よく使われているCelery。ただDjangoほど知見が共有されていないため、なんとなく使っているという方も多いのではないかと思います。そのような場合Celeryを使えるようにするまでは順調でも、実際に運用がはじまったあとに困ることが出てきます。例えば、ログの保存、リトライの設計、デプロイ戦略など。
    このトークでは、CeleryをDjangoプロジェクトで実際に運用するうえでの役立つTipsをお伝えします。
    Some good tips about Celery Production tips from Django Congress 2021 in Nagano this year (I couldn't attend). Most of the information is in the docs in English, but it's handy to see it condensed, even if it's in Japanese. A couple key points:

    • Use **kwargs for your tasks input. This makes it easier to make updates to your tasks once they're already running in production if your input needs to change. 
    • Reminders about all of the handy kwargs you can pass to tasks in regards to retry. Especially handy autoretry_for where you can pass a tuple of exceptions that will cause the task to automatically retry
  • 🔗 Newsstand

    Google News RSS reader for Mac OS 9 More than 200 curated topics Top news available for 24 countries Designed with an Apple Platinum interface Natively written in Mac OS 9
    The world needs more software like this. So clean and with minimal system requirements. Lovely.
Previous 23 of 28 Next