Browse tags
2600(1) activisim(1) ai(3) air quality(2) analog(1) apple(5) attention(1) audio(1) bicycle(4) blogging(15) bread(1) change”(1) climate change(14) co2(6) community(3) computing(22) cooking(1) css(1) cycling(1) design(3) digital nomad(1) django(2) drm(1) education(1) electricity(3) electrification(5) email(1) energy(6) environment(2) fashion(1) finland(1) health(2) heating(1) indieweb(8) induction(1) infastructure(2) internet(11) japan(6) life(1) macos(4) map(1) mental health(1) music(2) nostalgia(10) nyc(1) octopus energy(1) pandemic(3) paper(1) photo(1) photography(2) podcast(1) politics(3) pollution(1) portugal(1) privacy(5) privacy apple(1) product(1) productivity(1) programming(5) project management(1) python(5) renewables(3) running(2) search(1) smartphones(1) social media(11) software(1) solar(4) space(2) taiwan(1) trains(1) transit(1) travel(4) urban design(2) video(17) wind(2) “climate(1)

  • 🔗 Building Search DSLs with Django

    Search DSLs can give a user more granular access to searching without exposing an overly complicated interface.

    GitHub issues provide a DSL that’s accompanied by UI elements. An example query for searching issues would be:

    is:open author:danlamanna

    We can create something similar for use in a custom Django application.
    Improving search on my website has been long on my list of things to do. Something like this would make it easy for me to search my posts like "city:Yokohama type:checkin" to find all checkins in Yokohama. 🤔

  • 🔗 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

  • 🔗 Full Stack Radio | 151: DHH – Building HEY with Hotwire

    Good interview with DHH about Hotwire.dev. Turboframes really excites me - I want to write my web apps in Python, not Typescript/JS.

  • 🔗 Code With Me - Plugins | JetBrains

    Code With Me is a new service created by JetBrains for collaborative development and pair programming.
    I've been doing a lot of remote pair programming at work lately. This Code with Me plugin for PyCharm looks like it could make it a lot easier. Can't wait to try it out.

  • 🔗 jaredks/rumps

    Ridiculously Uncomplicated macOS Python Statusbar apps - jaredks/rumps
    I've been thinking about couple ideas for status bar apps that could help me at work. One of the largest barriers for me to actually build them is re-learning Objective-C (I can't believe ImageXY was almost a decade ago ) or learning Swift. Letting me write apps in Python should allow me to quickly prototype some apps and see if my ideas are actually any good.