The new JetBrains terminal is pretty cool (but I'd still use my own prompt with it)
The JetBrains Blog
The New Terminal (Beta) Is Now in JetBrains IDEs | The IntelliJ IDEA Blog
The new terminal (Beta) is now in JetBrains IDEs and will be available in the new UI starting from the 2024.1 version of the IDEs.
https://chrisdown.name/2018/01/02/in-defence-of-swap.html
TLDR: swap is useful even with large amounts of RAM available on the machine
TLDR: swap is useful even with large amounts of RAM available on the machine
chrisdown.name
In defence of swap: common misconceptions
tl;dr: Having swap is a reasonably important part of a well functioning system. Without it, sane memory management becomes harder to achieve.
Astral.sh are killing it.
Probably the biggest innovation in Python packaging over the last 5 years.
So long, Poetry, and thanks for all the fish! Dependency resolution & installation are going to be 10-100x faster now.
Probably the biggest innovation in Python packaging over the last 5 years.
So long, Poetry, and thanks for all the fish! Dependency resolution & installation are going to be 10-100x faster now.
astral.sh
uv: Unified Python packaging
Manage entire Python projects and even Python itself with a single unified tool.
Just found a really useful feature of
It allows executing actions against the running container during development, such as syncing source code or rebuilding the image on file changes.
This is more versatile than mounting large directories into the running container. The feature supports multiple conditions and exclusion of certain files.
Example with
Docker Compose
called watch
. It allows executing actions against the running container during development, such as syncing source code or rebuilding the image on file changes.
This is more versatile than mounting large directories into the running container. The feature supports multiple conditions and exclusion of certain files.
Example with
uv
docs.astral.sh
Using uv in Docker | uv
A complete guide to using uv in Docker to manage Python dependencies while optimizing build times and image size via multi-stage builds, intermediate layers, and more.
Recently I’ve spent some time working on dagster-ray.
Pretty happy with the result: now there is a bunch of ways to kick off computations on Ray from Dagster pipelines, all with their own advantages and tradeoffs, including two types of Pipes clients (Dagster Pipes has been my main project for the last 3 months).
It's still early but anyway, it's probably the most complicated and feature-rich of all my personal projects. I know there has been demand for a proper Ray integration in the Dagster community. Hopefully, folks will have more options going forward.
Pretty happy with the result: now there is a bunch of ways to kick off computations on Ray from Dagster pipelines, all with their own advantages and tradeoffs, including two types of Pipes clients (Dagster Pipes has been my main project for the last 3 months).
It's still early but anyway, it's probably the most complicated and feature-rich of all my personal projects. I know there has been demand for a proper Ray integration in the Dagster community. Hopefully, folks will have more options going forward.
GitHub
GitHub - danielgafni/dagster-ray: Ray integration for Dagster
Ray integration for Dagster. Contribute to danielgafni/dagster-ray development by creating an account on GitHub.
Mind blowing amount of optimizations for faster dev environment startup mentioned in this blog post by GitPod.
Intuitively it makes sense that Kubernetes isn't the best platform for dev environments, and they also go to great lengths in order to support this claim.
Pretty nice read.
Intuitively it makes sense that Kubernetes isn't the best platform for dev environments, and they also go to great lengths in order to support this claim.
Pretty nice read.
www.gitpod.io
We’re leaving Kubernetes - Blog
Discover why Gitpod is moving away from Kubernetes for cloud development environments after 6 years of experience at scale. Learn about Gitpod Flex and our new approach to development infrastructure for developers.
Somehow it's the first time I'm hearing about Burrito - think ArgoCD for Terraform.
Looking really great, should make terraform development much easier. Might try for me personal infra management soon.
Looking really great, should make terraform development much easier. Might try for me personal infra management soon.
GitHub
GitHub - padok-team/burrito: 🌯 Burrito is a TACoS Kubernetes Operator - "Argo CD for Terraform"
🌯 Burrito is a TACoS Kubernetes Operator - "Argo CD for Terraform" - padok-team/burrito
It's happening! Astral is building a Python type checker in Rust.
Can't wait to get my hands on it.
https://x.com/charliermarsh/status/1884651482009477368
Can't wait to get my hands on it.
https://x.com/charliermarsh/status/1884651482009477368
I decided to post an original piece of content instead of doing another effortless repost.
You can read my take on organizing and building Python monorepos efficiently with
Teaser:
In this post, I am going to share an approach to building Python monorepos that solves these issues in a very elegant way. The benefits of this approach are:
- it works with any `uv` project (even yours!)
- it needs little to zero maintenance and boilerplate
- it provides end-to-end pipeline caching --- including steps downstream to building the image (like running linters and tests), which is quite rare
- it's easy to run locally and in CI
—
You can read my take on organizing and building Python monorepos efficiently with
uv
and Dagger
on my website.Teaser:
In this post, I am going to share an approach to building Python monorepos that solves these issues in a very elegant way. The benefits of this approach are:
- it works with any `uv` project (even yours!)
- it needs little to zero maintenance and boilerplate
- it provides end-to-end pipeline caching --- including steps downstream to building the image (like running linters and tests), which is quite rare
- it's easy to run locally and in CI
—
uv init --package --lib weird-location/nested/lib-three
uv add --package lib-three lib-one lib-two
dagger call build-project --root-dir . --project lib-three
✔️ connect 0.2s
✔️ load module 5.4s
✔️ parsing command line arguments 2.0s
✔️ monorepoDagger: MonorepoDagger! 2.1s
✔️ .buildProject(
│ │ debugSleep: 0.000000
│ │ project: "lib-three"
│ │ rootDir: no(digest: "sha256:7112225e5254a6bc947b4ce9318d5ed7e8e5a713df2bb1acefa52bbd739077ce"): Missing
│ ): Container! 8.2s
✔️ .defaultArgs: [String!]! 0.0s
✔️ Container.mounts: [String!]! 0.0s
✔️ Container.entrypoint: [String!]! 0.0s
✔️ Container.platform: Platform! 0.0s
✔️ Container.user: String! 0.0s
✔️ Container.workdir: String! 0.0s
_type: Container
defaultArgs:
- python3
entrypoint: []
mounts: []
platform: linux/amd64
user: ""
workdir: /src
Extremely excited about Dagster Components being released!
This is going to dramatically improve UX with Dagster development (it's already high so I guess the new bar is just unimaginable) and significantly smoothen the learning curve. I imagine even people who can't really code (like your typical data analysts) will be able to have impact with this system!
This is going to dramatically improve UX with Dagster development (it's already high so I guess the new bar is just unimaginable) and significantly smoothen the learning curve. I imagine even people who can't really code (like your typical data analysts) will be able to have impact with this system!
GitHub
Previewing dg CLI + Components: A New Era for Dagster 🚀 · dagster-io/dagster · Discussion #28472
Previewing dg CLI + Components: A New Era for Dagster 🚀 We’re excited to announce the preview of three significant additions to the open-source Dagster framework: dg, our new CLI : A new command-li...
This is something I fully agree with! Constructors are overrated. Declarative (attributes) > imperative.
https://blog.glyph.im/2025/04/stop-writing-init-methods.html
https://blog.glyph.im/2025/04/stop-writing-init-methods.html
blog.glyph.im
Stop Writing `__init__` Methods
YEARS OF DATACLASSES yet NO REAL-WORLD USE FOUND for overriding special methods just so you can have some attributes.