models are top-notch and I found myself using them a lot.
IMHO, the editors w/o tight AI integration will fade away at some point.
Cursor is an editor with most notable integration with AI API, allows to have nice interactions with code suggestions from LLM.
Another notable example is NeoVIM. This year I’ve invested a lot into making baby steps with nvim. Probably, the easiest way to start is by using NVChad, a curated set of plugins. I used to use vim a lot back in the days with Ruby on Rails development and I liked the experience back then. NeoVIM makes integration of a lot of tools a breeze with LUA. It was interesting to discover Clojure dialect of LUA - Fennel. Fennel can be used to write extensions for NeoVIM as well. DHH is moved away from macOS to Linux and his new tech stack includes NeoVIM with curated configs gathered in a tool “Omakub”. I clearly see this trend to build platform-like utilities. For example, once - is a command line tool used to deliver updates to the standalone applications, like WriteBook.
Cable Management is an interesting topic for me, as my passion towards tech gadgets encourages spending some money during black friday on something fascinating. Typically, it’s one of the “next one more thing”.
Creating a distraction free space is crucial for creativity. Cluttered space creates tention, hindering the productivity. It’s so important to keep the place nicely organized!
Here is a couple of cable management solutions I tried at my home.
One of the greatest talks from Rich Hickey was about making changes to software systems. Search for it with “Spec-ulation” keyword in Youtube.
Long story short, you may break or not break the system by removing something like class or function or by changing a function signature (read: parameters), changing in this context means you remove the old function with the same name and add a new one with different parameters.
Little known fact about SmallTalk programming language.
The code written in SmallTalk should be able to be read aloud and it should make sense to a human.
Waypoint is a tool by Hashicorp to manage builds, artifacts and deployments.
It has a CLI interface and also a nice UI and uses HCL instead of YAML for configuration and templating.
It might not be needed if you have something like GitHub Actions and may felt redundant, but actually it's a kind of missing piece for having a good UI for CI/CD pipelines, as it gives a handy tool for a developer to streamline build/deploy/release process.
As, probably, many of you, I did a long journey from manual FTP sync, to semi-automated tools like Capistrano, then manually managed docker deployments, then anisble managed docker containers and finally, met the orchestration system of choice - Hashicorp Nomad.
TLDR: Kubernetes is too heavy for my moderate needs. Hashicorp Nomad strikes the right balance between features and maintenance complexity.
At some point in time I felt a need for better container orchestration system that I could run by myself in Hetzner. Funny enough, DHH and Co. came to the same conclusion, but implemented in a different way. They developed completely own version of ansible on steroids named Kamal. This has right for existence, but imho has own flaws, like manual nodes management for fault tolerance and challenge to keep versions of deployed artifacts in sync. The push based deployment always suffers from this. People were trying to solve this issues already for quite a long time by using systems like Chef of Puppet.
Rubu on Rails development changes a lot every year and sometimes it's not easy to keep up with the changes.
I've recently bought Sustainable Rails Book and it's hard to overestimate how valuable is it for me.
Here are couple of thoughts after reading first chapters.
Dare to add, invest heavily in CI/CD process, with modern GitHub offering it's just way easier then maintaining own on-prem solution.
The article provides overview of facts why Emacs is so different but also so powerful comparing to other editors. It gives a good starting point for the reader to understand the fundamentals and start own journey to effective work.
The way of learning is painful, but rewarding. The essense of Emacs is to codify your specific repetitive tasks so that eventually you realize, the editor contains a lot of customizations speeding up your daily routines, as no other editor does.
I do the following things in Emacs:
While Ansible is a great tool for certain use cases, such as building new AMIs when used with Packer, it has some downsides. These become apparent when using it for container orchestration (which I have witnessed at scale) or keeping the configuration of a set of nodes in sync.
Another significant, though not dramatic, downside is related to Python version and dependency management. This adds extra complexity that I would prefer to avoid in a system management tool.
Recently, I stumbled upon a concept that sounded new to me: Compliance as a Code.
The core idea is to “embed compliance policies into the code that can be repeated and tested automatically.” But what does it mean in practice?
For example, consider PCI DSS, which requires measures to secure credit card information to ensure compliance. Tools like Terraform, Ansible, and others should contain the code for encryption, access control, and data obfuscation. Additionally, before deployment, automated tests in the CI/CD pipeline should validate that the application meets PCI DSS requirements.
