# simplicity Published articles for simplicity. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why Microservices Can Use Serverless Functions Instead of Socket Servers DevFeed: [Why Microservices Can Use Serverless Functions Instead of Socket Servers]() Original publisher: [Read original article]() Author: Matt Butcher Published: 2025-05-07T12:00:00Z Content type: opinion Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Serverless](), [Microservice](), [Security](), [Architecture & Design]() Tags: [security](), [serverless](), [servers](), [simplicity]() ### AI overview The article argues that microservices do not always need full socket servers and recommends serverless functions as a simpler alternative with less security and operational burden. ### Source excerpt Why continue in the dogma that every microservice needs a full-on socket server? Why shoulder more burden, both security-wise and operationally, than we need to? Simplicity is a virtue. We should embrace the new generation of serverless functions. ## How Senior Engineers Take a Feature from Start to Delivery DevFeed: [How Senior Engineers Take a Feature from Start to Delivery]() Original publisher: [Read original article]() Author: Tiger Abrodi Published: 2024-03-28T17:06:09Z Content type: tutorial Language: en Sources: [Saiyan Growth Letter]() Topics: [Development](), [Users](), [Requirements](), [data](), [iteration](), [pull-requests]() Tags: [data](), [delivery](), [developers](), [development](), [feature-flagging](), [how-to](), [iteration](), [pull-requests](), [requirements](), [simplicity](), [users]() ### AI overview This tutorial presents an approach for taking a software feature from initial justification through delivery. It recommends validating why the feature is needed, defining a minimum viable product, choosing a simple technical solution, breaking the work into small tasks, and using feature flagging and rollout practices. ### Source excerpt How Senior engineers take a feature from start to delivery ## Trying Substack as a Simpler Blogging Platform DevFeed: [Trying Substack as a Simpler Blogging Platform]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2023-07-06T00:00:00Z Content type: opinion Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [Publishing](), [configuration]() Tags: [blog-post](), [blogging](), [simplicity](), [subscriptions]() ### AI overview Bruce Eckel explains why the ceremony of creating blog posts can discourage him from writing and describes trying Substack as a simpler publishing platform. He likes its clean writing workflow, live preview, email delivery, and subscription-based business model, while noting that he is still adjusting to some limitations. ### Source excerpt TLDR: BruceEckel.substack.com I've noticed that I haven't been writing here that much lately, and I began to suspect it is because of the necessary ceremony of creating a blog post. Which, really, isn't that much but I've started to see that even the smallest amount can be an impediment. When I began trying to paint, I discovered these impediments, and they're different for each person. In my case, the stretched canvas was "too important" and I resisted putting paint on it (both parents grew up in the depression, so I am overly careful about wasting things, which makes experimentation hard). ## Using Makefiles to Simplify Command-Line Test Workflows DevFeed: [Using Makefiles to Simplify Command-Line Test Workflows]() Original publisher: [Read original article]() Author: Derek Lee Published: 2022-02-19T05:00:00Z Content type: tutorial Language: en Sources: [art and science of coding]() Topics: [make](), [Command-line interface](), [test](), [unit tests](), [ci](), [iOS](), [Xcode](), [Gradle](), [JavaScript]() Tags: [automation](), [ci](), [command-line](), [communication](), [discoverability](), [gradle](), [ios](), [javascript](), [kotlin](), [make](), [science](), [simplicity](), [test](), [unit-tests]() ### AI overview This tutorial argues for using Makefiles to simplify and standardize command-line test execution across projects. It contrasts Makefiles with Fastlane and shell scripts, and begins an iOS example using Make targets to run an Xcode test suite. ### Source excerpt I make a point of always running the test suite (at least the fastest of the bunch: the unit tests) from the command line before pushing code to CI to confirm that all has gone smoothly. ## Vite.js Next Generation Frontend Tooling + Craft CMS DevFeed: [Vite.js Next Generation Frontend Tooling + Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2021-05-05T00:51:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Vite](), [Front end](), [JavaScript](), [Tooling](), [Content Management System]() Tags: [article](), [cms](), [combines](), [craft](), [frontend](), [generation](), [how-to](), [integrate](), [javascript](), [modern](), [shows](), [simplicity](), [speed](), [tooling](), [vite](), [vite-js]() ### AI overview A tutorial on integrating Vite.js frontend tooling with Craft CMS. It explains Vite.js's speed and simplicity, compares its build workflow with webpack, and describes plugin installation and configuration for a server-rendered Craft CMS project. ### Source excerpt Vite.js is next generation frontend tooling for modern JavaScript that combines speed with simplicity. This article shows you how to integrate Vite.js with Craft CMS ## A Personal Perspective on Programming Languages and Programmer Productivity DevFeed: [A Personal Perspective on Programming Languages and Programmer Productivity]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2015-08-29T00:00:00Z Content type: opinion Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [MSVC](), [C](), [Go Language](), [D]() Tags: [c](), [c-plus-plus](), [complexity](), [go](), [productivity](), [simplicity]() ### AI overview The author describes studying programming languages and helping others understand or solve language-related problems. They evaluate languages primarily by simplicity, clarity, and programmer productivity, and discuss moving beyond C++98 while considering D and Go as alternatives to C++ complexity. ### Source excerpt I have a very narrow set of skills, which can be summarized as "delving into a language and helping others understand and (sometimes) solve problems involving that language." That's too simple, however - because I ultimately seek "the best" language, for my own personal definition of "best." I also leave languages behind. While I once knew all the ins and outs of C++, for example, I stopped studying that language after C++98, searching for a language that gave me more. ## Why Clojure's Simplicity Can Make It Accessible and Practical DevFeed: [Why Clojure's Simplicity Can Make It Accessible and Practical]() Original publisher: [Read original article]() Published: 2014-11-24T00:00:00Z Content type: opinion Language: en Sources: [Adam Bard]() Topics: [Clojure](), [syntax](), [Lisp]() Tags: [article](), [clojure](), [essay](), [language](), [languages](), [practical](), [simplicity]() ### AI overview This essay argues that Clojure's regular syntax and emphasis on simplicity can make the language easier to read, write, and understand. It focuses on accessibility and practical use rather than advanced Lisp concepts, and includes a brief syntax primer. ### Source excerpt The inspiration for the article I wrote last week entitled Clojure is not for geniuses was inspired by Tommy Hall's talk at Euroclojure 2014, wherein he made an offhand joke about preferring Clojure for its minimal syntax, as he possesses a small brain (both his blog and his head suggest this assertion is false). I had intended to bring this up with the original article, but got sidetracked talking about immutable things and never got back around to it. Here I'd like to address that, along with some discussion that arose in various forums after the first article.