The idealization of farming by tech (News)

What up, nerds? I'm Jerod and this is Changelog News for the week of Monday, March 31st, 2025. Here's a perfectly joyous use of tech: the jumbotron operator for the Indiana Pacers adds a "crying" filter to visiting Lakers fans' faces during game breaks. The effect compounds as the Lakers fans begin to laugh along, giving the appearance of uncontrolled sobbing. [You just gotta see it for yourself](https://www.youtube.com/shorts/-Q8lfUhan4E). Ok, let's get into the news.

[The idealization of farming by tech](https://tjmorley.com/blogposts/cottagecoreprogrammers.html) In a #longpost, Theodore Morley wonders why we tech workers so frequently point our wanderlust toward hands-on trades: > Why does everyone who sits behind a computer long to be out in the fields or workshops? Is this specific to some subgroup in tech that I happen to cross paths with regularly, or is it a broader modern ennui? Theodore grew up working on a farm, so his desire to escape manual labor so he could be "getting paid to sit in an air conditioned office" make him puzzled by our seemingly collective desire to move the opposite direction. > Why would people who are so comfortable, whose job was to me a lifelong goal, want to do exactly what I worked so hard to move away from? I suspect the answer is tied up in the nature of our work in the modern world, as well as in the inspection of who has been mythologized in American history. An enjoyable deep dive follows, but I believe the old adage explains this phenomenon well: we always think the grass is greener on the other side, even though we get to specify the exact RBG values of our digital grass... it pales in comparison to its natural analog.

[Know this before choosing Next.js](https://eduardoboucas.com/posts/2025-03-25-you-should-know-this-before-choosing-nextjs/) Eduardo Bouças (who works at Netlify, a Vercel competitor, so keep that in mind): > There is nothing wrong with a company profiting from an open-source software it created, especially when that helps fund the development of the project. In fact, there are plenty of examples of that model working successfully in our industry. > > But I think that can only work sustainably if the boundaries between the company and the open-source project are abundantly clear, with well-defined expectations between the maintainers, the hosting providers and the users about how and where each feature of the framework can be used. > > I want to explain why I don't think this transparency exists today. > > My goal is not to stop anyone from using Next.js, but to lay out as much information as possible so developers and businesses can make an informed decision about their technology stack. This post was prompted by how Vercel recently handled a critical security vulnerability with Next.js, which Eduardo describes as "so poor, reckless and disrespectful to the community that it has exacerbated my concerns about the governance of the project." He lists three facts that give him pause regarding the project: 1. No adapters 2. No official serverless support 3. Vercel-specific code paths

[xan is the CSV magician](https://github.com/medialab/xan) > xan is a command line tool that can be used to process CSV files directly from the shell. > > It has been written in Rust to be as fast as possible, use as little memory as possible, and can easily handle very large CSV files (Gigabytes). It is also able to leverage parallelism (through multithreading) to make some tasks complete as fast as your computer can allow. > > It can easily preview, filter, slice, aggregate, sort, join CSV files, and exposes a large collection of composable commands that can be chained together to perform a wide variety of typical tasks. This tool looks super handy for anyone who works with CSV files regularly. It even has its own expression language so you can perform complex tasks. Oh, and its terminal support is on point.

It's now time for Sponsored News! [Heroku plants new roots with Fir](https://blog.heroku.com/planting-new-platform-roots-cloud-native-fir?utm_source=changelog&utm_medium=newsletter&utm_campaign=changelog-news) The next generation of Heroku is called Fir, and it's being built on open source standards and cloud native technologies like the Open Container Initiative (OCI), Cloud Native Buildpacks (CNBs), OpenTelemetry, and Kubernetes (K8s). This next technology stack represents the next decade and beyond for Heroku while building on their core principle: maximize developer productivity by minimizing distractions Here's what Terence Lee has to say about Fir: > Fir is still the Heroku you know and love. It’s rooted in the world renowned developer experience while built on a bedrock of security and stability. We achieve this by offering seamless functionality out of the box with the flexibility to customize as needed. In today's complex development landscape, minimizing cognitive load is crucial. This allows you to focus on what truly matters: delivering value to your customers. Follow the link in your chapter data and the newsletter to learn all about it and thanks to Heroku for sponsoring Changelog News.

[What we can learn from Milk Kanban](https://brodzinski.com/2025/03/milk-kanban.html) Pawel Brodzinski takes us back to Kanban's roots and original purpose: > In its original meaning, Kanban represented a visual signal. The thing that communicated, well, something. It might have been a need, option, availability, capacity, request, etc. > > In our Kanban systems, the actual Kanban is a sticky note... > > It represents work, and given its closest environment (board, columns, other stickies, visual decorators), it communicates what needs, or needs not, to be done. > > A visual signal all the way. He then tells a story of how his office mate, Kasia, designed a perfectly simple Kanban system for milk inventory. It's a good example with an even better lesson.

[There is no vibe engineering](https://serce.me/posts/2025-31-03-there-is-no-vibe-engineering) Sergey Tselovalnikov weighs in on "vibe coding" –the tech industry's buzzword *de jour* (and quite honestly one of my favorite terms of late): > The term caught on and Twitter quickly flooded with posts about how AI has radically transformed coding and will soon replace all software engineers. While AI undeniably impacts the way we write code, it hasn't fundamentally changed our role as engineers. Allow me to explain. Sergey's overarching point is one Amal Hussein and I agreed about on Changelog & Friends last week: vibe coding as a practice is here to stay, but whether or not it will every produce production-grade applications... that's still a big question mark. > It is possible that there’ll be a future where software is built from vibe-coded blocks, but the work of designing software able to evolve and scale doesn’t go away. That’s not vibe engineering – that’s just engineering, even if the coding part of it will look a bit different.

That's the news for now, but also scan the companion newsletter for even more links worth clicking on. Such as: - [Stamina is a quiet advantage](https://kupajo.com/stamina-is-a-quiet-advantage/) - [Apple needs a Snow Sequoia](https://reviews.ofb.biz/safari/article/1300.html) - [A desktop from a bygone era](https://github.com/winblues/blue95) Get in on the newsletter at changelog.com/news Have a great week! Leave us a 5-star review if you dig our work, and I'll talk to you again real soon.