Posts tagged as python

  1. ()

    Fridays are for learning. These are some interesting links for the week ending August 10, 2018. You can’t debug systems with dashboards. Dashboards (by design) can only display aggregate data, but your users don’t care about aggregates — they care only whether their requests succeed or fail. You can be 100% up for virtually all your users, but 100% down for your most important user and your dashboard will likely still be green. … (read more)

  2. ()

    Fridays are for learning. These are some interesting links for the week ending August 3, 2018. On serverless testing in production: it’s not that you shouldn’t be doing testing before releasing to production, it’s that you should also be doing some kind of testing in production as well. Production is where reality hits your systems; it’s the only place you will be able to find real-world conditions. Feature flags, canary deployments, staged rollouts, rich instrumentation, and observability-first development are all useful here. … (read more)

  3. ()

    Fridays are for learning.1 These are some interesting links for the week ending June 29, 2018. This week’s big news (for me anyway): Python 3.7 is out! Cool new features in Python 3.7. My favorites are from __future__ import annotations to enable lazy parsing of type annotations, importlib.resources to replace simple usages of the much-heavier pkg_resources, and making ordered dictionaries a requirement of the language instead of just an implementation detail. … (read more)

  4. ()

    Fridays are for learning.1 These are some interesting links for the week ending June 22, 2018. Joe Duffy says “Hello, Pulumi!” Pulumi is a new service to configure cloud services/IaaS programmatically using JS/TypeScript/Go/Python. Modern deployment systems now mean diving into piles and piles of YAML, compounded by the piles of additional YAML you need to configure that YAML for tools like Helm. So in a general sense I agree that higher-level tools would be useful. … (read more)

  5. ()

    Fridays are for learning.1 These are some interesting links for the week ending June 8, 2018. “Go for industrial programming.” As time goes on, I have embraced this kind of thinking more and more. While the term “industrial programming” seems to be intentionally distancing, the idea that building systems that are intended to last (even as individual developers come and go and business requirements change) requires specific attention to succeed really makes sense to me. … (read more)

  6. ()

    This post is part of a series reimplementing one of my past projects using technology available these days; for a general overview, please see the prologue. Continuing on from last time, the design of the system as a whole is, intentionally, pretty boring. I think boringness is underrated by developers as a whole; I actually want my projects — especially my work projects! — to be as boring as possible because it buys you predictability. … (read more)

  7. ()

    Fridays are for learning.1 Another batch of videos from PyCon US 2018 (see the YouTube channel for more), for the week ending May 25, 2018. Barry Warsaw, “Get Your Resources Faster With importlib.resources Watch this video at YouTube. An introduction to Python 3.7’s new importlib.resources, which incorporates some (tiny fraction) of pkg_resources into the standard library. Alex Gaynor, “Learning from Failure: Post Mortems” Watch this video at YouTube. Failures happen. … (read more)

  8. ()

    Fridays are for learning.1 These are the first batch of videos from PyCon US 2018 (see the YouTube channel for more) for the week ending May 18, 2018. Larry Hastings, “Solve Your Problem With Sloppy Python” Watch this video at YouTube. I think Larry has a good point (things you build for yourself to automate personal tasks don’t need to be held to the same standard as code you write for others to consume); I like to use these opportunities to try out new tools. … (read more)

  9. ()

    Recently I’ve been thinking about how much easier it is to achieve quite complex things these days compared to back in The Olden Days. In fact, it almost feels like we suffer from a surfeit of mature, high quality pieces that we can use to build almost anything.1 There’s one project I worked on in the past — many years ago now — that I still think about from time to time; how would I accomplish those same tasks now, with everything that’s easily available to a professional today? … (read more)

  10. ()

    It’s that time of year again... time to catch up on this year’s PyCon US talks. I’m planning to post and comment on some of the ones that made me think the most. To start, I really enjoyed Lennart Regebro’s “Prehistoric Patterns in Python”. Watch this video at YouTube. Even though I think most of these old patterns have largely gone away, sometimes the “Old Way” of doing things can resurface. … (read more)