# simple Published articles for simple. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kotlin Coroutines Compared with Reactor for Sequential and Asynchronous Operations DevFeed: [Kotlin Coroutines Compared with Reactor for Sequential and Asynchronous Operations]() Original publisher: [Read original article]() Published: 2025-10-06T00:00:00Z Content type: comparison Language: en Sources: [Kt. Academy]() Topics: [Coroutines](), [Kotlin](), [kotlin-coroutines](), [Reactive Streams](), [RxJava](), [async/await](), [Android](), [Back end]() Tags: [android](), [async](), [asynchronous](), [await](), [backend](), [compare](), [comparison](), [coroutines](), [kotlin](), [kotlin-coroutines](), [programming](), [programming-languages](), [reactive-streams](), [rxjava](), [simple](), [time](), [workshop-learning-programming]() ### AI overview This article compares Kotlin Coroutines with Reactor for backend and Android development. It argues that coroutines provide more readable and straightforward syntax for sequential and asynchronous operations, while Reactor requires additional operators, concepts, and patterns. ### Source excerpt A comparison of Kotlin Coroutines and Reactor, highlighting the elegance and simplicity of Coroutines over the complexity of Reactor. ## My Simple Knowledge Management and Time Tracking System DevFeed: [My Simple Knowledge Management and Time Tracking System]() Original publisher: [Read original article]() Author: Henrik Warne Published: 2024-11-09T16:10:58Z Content type: opinion Language: en Sources: [Henrik Warne]() Topics: [knowledge-management](), [time tracking](), [Shell](), [Command-line interface](), [Git](), [Script](), [cURL](), [Python]() Tags: [commands](), [curl](), [files](), [git](), [how-to](), [knowledge-management](), [notes](), [python](), [script](), [shell](), [simple](), [time-tracking](), [work]() ### AI overview The author describes a simple personal system using notes.txt to record commands, procedures, and other important information, and worktime.txt to track daily hours and tasks. A Python script calculates daily and weekly hours. The notes provide reusable instructions and command examples, while repeated use helps the author remember them. ### Source excerpt I am using a very simple system for remembering commands and procedures, and for tracking what I work on. I have two plain text files called notes.txt and worktime.txt. In the notes file, I write down things that are important ... Continue reading -> ## Run SpinKube on Rancher Desktop DevFeed: [Run SpinKube on Rancher Desktop]() Original publisher: [Read original article]() Author: Matt Butcher Published: 2024-03-19T12:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [rancher](), [JavaScript](), [App]() Tags: [app](), [build](), [deploy](), [desktop](), [javascript](), [rancher](), [run](), [simple]() ### AI overview A tutorial that builds a simple JavaScript app and deploys it into a Rancher Desktop cluster using SpinKube. ### Source excerpt Let's build a simple JavaScript app and deploy it into our Rancher Desktop cluster via SpinKube. ## How I Built an AI Inferencing API With Llama2 on Spin DevFeed: [How I Built an AI Inferencing API With Llama2 on Spin]() Original publisher: [Read original article]() Author: Caleb Schoepp Published: 2023-09-21T01:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [API](), [Artificial Intelligence](), [Serverless]() Tags: [ai](), [analysis](), [api](), [build](), [serverless](), [simple](), [using]() ### AI overview A tutorial on building a simple sentiment analysis API with Fermyon Serverless AI and Spin. ### Source excerpt We build a simple sentiment analysis API using Fermyon Serverless AI and Spin. ## Fibery vs. Monday. Complex vs. simple processes. DevFeed: [Fibery vs. Monday. Complex vs. simple processes.]() Original publisher: [Read original article]() Author: Michael Dubakov Published: 2021-11-24T21:22:29Z Content type: comparison Language: en Sources: [Stories by Michael Dubakov on Medium]() Topics: [Product Management](), [Databases](), [ui]() Tags: [complex](), [databases](), [mondaydotcom](), [product-development](), [product-management](), [product-management-tool](), [simple](), [software-development](), [software-development-tool](), [ui](), [vs]() ### AI overview A comparison of Fibery and Monday.com for organizing team processes. It presents Monday as feature-rich and flexible but complicated, with weaker support for modeling hierarchies and relationships, while Fibery uses connected spaces, databases, relations, and views to represent product-management structures such as Epics and Features. ### Source excerpt Usually posts X vs. Y are shallow. This post is not. As the Fibery CEO, I have to switch off the bias. Take this post with a grain of salt. The major goal is to explain how Fibery is different and what strengths and weaknesses it has. Monday is a very feature-rich product. However, it's quite complicated. Let's dig something interesting together. General feelings Monday is very similar to ClickUp in many ways, but it seems that Monday is slightly less feature-reach (surprisingly). UI is high-contrast and snappy, but very flickery. When you move the mouse, everything blinks and changes, and this is quite distracting. It is visible that some parts of the system are new, while others are old, so the general feelings about the user interface are mixed. I can't say that I like it, but I feel that I can get used to it with time. The first 30 minutes are hard, but if you overcome the initial resistance, then the system starts to make sense. PhilosophyMonday = Work OSmonday.com is a Work Operating System (Work OS) that powers teams to run projects and workflows with confidence. Monday is a platform to build your processes. In this regard, the main mission is very similar to Fibery. Flexibility is the most important feature here. Monday has all important building blocks to organize processes: Flexible databases, Views, integrations, rules, and many productivity features. 🦐 One serious problem is that you can't model hierarchies and processes in a nice way. It's not possible to have a tree view that shows Epics and Features. It's not possible to have a board that shows Features by Epics, etc. Connections and relations are not a strong part of Monday. For complex processes, you will have to live with many workarounds. Fibery = Set of connected Spaces In Fibery everything is connected. The main building blocks are Space, Database, Relation, and View. Here is an example of a connected workspace for product development. Several connected apps in product development workspace. Spa ## send.firefox.com rocks DevFeed: [send.firefox.com rocks]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-03-28T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Firefox]() Tags: [firefox](), [https](), [large-files](), [simple]() ### AI overview The article recommends Mozilla's send.firefox.com for sending large files to individuals, describing it as simple, easy to use, and powerful. ### Source excerpt If you have to send a large file to an individual, use: https://send.firefox.com/ It is brilliantly simple, easy to use and powerful. Recommended. ## Let's Build A Simple Interpreter. Part 17: Call Stack and Activation Records DevFeed: [Let's Build A Simple Interpreter. Part 17: Call Stack and Activation Records]() Original publisher: [Read original article]() Author: Ruslan Spivak Published: 2019-08-28T15:00:00Z Content type: tutorial Language: en Sources: [Ruslan Spivak]() Topics: [function](), [data](), [Hardware]() Tags: [blog](), [build](), [function](), [hardware](), [implement](), [memory](), [series](), [simple](), [values](), [variable]() ### AI overview Part 17 of a series on building an interpreter explains plans to implement a new memory system for programs, procedure calls, and function calls, replacing the GLOBAL_MEMORY dictionary. It introduces memory as a way to store and access data and distinguishes physical memory from interpreter-level storage by variable names. ### Source excerpt You may have to fight a battle more than once to win it. - Margaret Thatcher ## Using DTMF tones to route phone calls offline in the Simple healthcare app DevFeed: [Using DTMF tones to route phone calls offline in the Simple healthcare app]() Original publisher: [Read original article]() Author: Saket Narayan Published: 2019-08-18T00:55:04Z Content type: article Language: en Sources: [Saket Narayan]() Topics: [App](), [Android](), [Internet](), [data]() Tags: [android](), [app](), [communication](), [data](), [decoding](), [dtmf](), [offline-first](), [proxy](), [simple](), [technology]() ### AI overview The article explains how the Simple healthcare app used DTMF tones to send a patient's phone number to a server during calls, enabling phone-number masking and offline-first operation when internet access was unavailable. ### Source excerpt While working on a healthcare app called Simple at my previous company, we wanted to improve how nurses follow up with their patients. The aim was to replace traditional paper registers + landline phones with the app, which could intelligently suggest patients who are potentially at risk based on their medical history, age, and other [...] The post Reinventing the dial-up modem appeared first on Saket Narayan. ## Writing Consistent Tools DevFeed: [Writing Consistent Tools]() Original publisher: [Read original article]() Published: 2019-02-20T22:13:02Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [Tool](), [Unix]() Tags: [set](), [simple](), [tools](), [unix](), [writing]() ### AI overview The article presents simple guidelines for writing consistent Unix tools. ### Source excerpt A set of simple guidelines to write consistent unix tools. ## Using Goss to validate Packer builds DevFeed: [Using Goss to validate Packer builds]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2018-12-06T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [test](), [Tool](), [builds](), [Server](), [Cloud]() Tags: [build](), [cloud](), [download](), [example](), [file](), [fork](), [git-tags](), [permissions](), [plugin](), [releases](), [run](), [simple](), [test](), [tool](), [useful](), [using]() ### AI overview A practical tip for validating Packer-built images with Goss. The article describes using a Packer plugin and a Goss test suite to check an image before pushing it to Google Cloud. ### Source excerpt Ever wanted to validate your Packer image with Goss? Well, you can! ## HelloKeystore: A Small Android Keystore Experiment DevFeed: [HelloKeystore: A Small Android Keystore Experiment]() Original publisher: [Read original article]() Published: 2017-11-12T21:36:13Z Content type: tutorial Language: en Sources: [maiatoday]() Topics: [Android](), [Code]() Tags: [android](), [code](), [experiments](), [project](), [simple](), [small]() ### AI overview A small Android project explores saving and retrieving data from the keystore, including differences across Android versions. ### Source excerpt Curious Keystore experiments. A small simple project that saves something in the keystore and gets it out again. Tricksiness happens across versions of Android. code ## Easy Approach to Requirements Syntax and the segue to Behavior Driven Development DevFeed: [Easy Approach to Requirements Syntax and the segue to Behavior Driven Development]() Original publisher: [Read original article]() Author: {"twitter"=\>"hlaueriksson"} Published: 2017-07-31T20:00:00Z Content type: article Language: en Sources: [Henrik Lau Eriksson]() Topics: [Requirements](), [Behavior-driven development](), [Specifications](), [User Stories]() Tags: [bdd](), [complexity](), [event](), [feature](), [features](), [format](), [precision](), [requirements](), [simple](), [specflow](), [specifications](), [state](), [test](), [user-stories]() ### AI overview The article introduces Easy Approach to Requirements Syntax (EARS) as a structured way to write requirements and examines how its templates may help translate user stories and acceptance criteria into Behavior-Driven Development tests. It describes five requirement types and the problems EARS aims to reduce, including ambiguity, vagueness, complexity, omission, duplication, wordiness, inappropriate implementation detail, and untestability. ### Source excerpt I was attending a conference six months ago and listened to a talk about quality. During the talk, I was introduced to EARS -- Easy Approach to Requirements Syntax. This way of writing requirements struck a chord with me, given my prior experience reading and writing requirement specifications. ## Using VueJS 2.0 with Craft CMS DevFeed: [Using VueJS 2.0 with Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2016-12-09T20:12:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Vue.js](), [Content Management System](), [JavaScript](), [Front end](), [jQuery](), [Document Object Model (DOM)]() Tags: [angular](), [building](), [cms](), [craft](), [frontend](), [great](), [insights](), [interfaces](), [javascript](), [library](), [manipulation](), [modern](), [powerful](), [simple](), [vuejs](), [works]() ### AI overview This tutorial explains VueJS 2.0 and demonstrates replacing jQuery with VueJS on a Craft CMS website. It contrasts Vue's architecture for building interactive, data-driven frontend interfaces with jQuery's DOM-manipulation toolkit. ### Source excerpt VueJS is a simple yet powerful library for building modern web interfaces, and it works great with Craft CMS ## Let's Build A Simple Interpreter. Part 10. DevFeed: [Let's Build A Simple Interpreter. Part 10.]() Original publisher: [Read original article]() Author: Ruslan Spivak Published: 2016-08-04T13:15:00Z Content type: tutorial Language: en Sources: [Ruslan Spivak]() Topics: [Programming](), [Programming language](), [Code](), [Compiler]() Tags: [article](), [blog](), [build](), [code](), [command-line](), [compiler](), [example](), [github](), [programming-language](), [simple](), [types](), [variable](), [variables]() ### AI overview This tutorial continues a series on building a Pascal interpreter. It updates the interpreter to parse and interpret a complete Pascal program, covering program headers, variable declarations, integer and floating-point division, comments, and grammar changes. ### Source excerpt Today we will continue closing the gap between where we are right now and where we want to be: a fully functional interpreter for a subset of Pascal programming language. In this article we will update our interpreter to parse and interpret our very first complete Pascal program. The program ... ## Simple React slider with touch support DevFeed: [Simple React slider with touch support]() Original publisher: [Read original article]() Author: Stanko Published: 2016-03-12T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [React](), [Code](), [Web Development]() Tags: [dependencies](), [javascript](), [react](), [simple]() ### AI overview A lightweight React slider component with touch support is presented as a dependency-free implementation of about 200 lines of code. The article mentions a demo, GitHub source code, extensibility, and browser support including modern browsers and IE10+. ### Source excerpt I needed simple React slider component, as we are building our new website as a universal React application. But I did not find anything lightweight. There is a crazy trend in JavaScript world - add gazillion dependencies. So again, I made something myself. Check the demo. It has no dependencies, and about 200 lines of code. Very simple and extensible. Every modern browser is supported and IE10+. IE9 should work (if you adapt the CSS), but I didn't test it. Grab the code on GitHub. ## Dasherize, Turbolinks 3 and Parallel DevFeed: [Dasherize, Turbolinks 3 and Parallel]() Original publisher: [Read original article]() Published: 2015-10-08T10:37:04Z Content type: tutorial Language: en Sources: [Jolly Good Code]() Topics: [dashboards]() Tags: [parallel](), [projects](), [simple]() ### AI overview The article explains how the author used Turbolinks 3 and the Parallel gem to build Dasherize, a material-designed dashboard for projects. ### Source excerpt Dasherize is a simple, material-designed dashboard for your projects. In this post, I'll talk about I used Turbolinks 3 and the Parallel gem to build Dasherize. ## lish(1) -- a limited shell DevFeed: [lish(1) -- a limited shell]() Original publisher: [Read original article]() Published: 2014-11-01T17:34:38Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [Shell](), [Command-line interface]() Tags: [command-line](), [commands](), [execution](), [shell](), [simple]() ### AI overview lish(1) is a simple, restricted command-line interpreter that permits execution of only a fixed set of commands. ### Source excerpt lish(1) implements a very simple, restricted command-line interpreter or shell to allow execution of only a fixed set of commands. ## Converting ssh(1) RSA public keys to PKCS8 format DevFeed: [Converting ssh(1) RSA public keys to PKCS8 format]() Original publisher: [Read original article]() Published: 2013-12-30T03:02:43Z Content type: tutorial Language: en Sources: [Signs of Triviality]() Topics: [ssh](), [public key](), [Code]() Tags: [code](), [example](), [format](), [how-to](), [public-key](), [rsa](), [simple](), [ssh]() ### AI overview A brief tutorial showing how to convert an ssh(1) RSA public key into PKCS8 format using a simple code example. ### Source excerpt A brief walk-through of a simple code example to show how to convert an ssh(1) RSA public key into PKCS8 format. ## clogger(1) -- a campfire logger DevFeed: [clogger(1) -- a campfire logger]() Original publisher: [Read original article]() Published: 2013-11-15T18:24:12Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [Logging](), [Messaging]() Tags: [command](), [interface](), [logger](), [messages](), [simple](), [syslog]() ### AI overview clogger(1) is a simple logging and messaging interface analogous to the common logger(1) command. It sends messages to Campfire instead of syslog(3). ### Source excerpt clogger(1) implements a simple logging/messaging interface analogous to the common logger(1) command. However, instead of logging messages to syslog(3), clogger(1) will write the message to Campfire. ## Common Lisp Scoping, Lexical Binding, and Closures DevFeed: [Common Lisp Scoping, Lexical Binding, and Closures]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2013-01-09T10:07:00Z Content type: tutorial Language: en Sources: [Dimitri Fontaine]() Topics: [Common Lisp](), [Functional programming](), [Programming](), [function]() Tags: [article](), [blog](), [function](), [functional-programming](), [lisp](), [shadowing](), [simple]() ### AI overview An article demonstrates Common Lisp scoping through examples involving lexical binding, variable shadowing, generalized booleans, closures, and REPL-based experimentation. ### Source excerpt Thanks to Mickael on twitter I got to read an article about loosing scope with some common programming languages. As the blog article Lost in scope references functional programming languages and plays with both Javascript and Erlang, I though I had to try it out with Common Lisp too. So, here we go with a simple Common Lisp attempt. The Lost in scope article begins with defining a very simple function returning a boolean value, only true when it's not monday. ## Updating Jira tickets via mail DevFeed: [Updating Jira tickets via mail]() Original publisher: [Read original article]() Published: 2012-08-23T02:23:44Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [jira]() Tags: [jira](), [mail](), [reverse](), [simple](), [updating]() ### AI overview The author describes writing a simple reverse mail filter to update Jira tickets via email. ### Source excerpt I wrote a simple reverse mail filter to update Jira via mail. ## How to generate error log from nested exceptions. DevFeed: [How to generate error log from nested exceptions.]() Original publisher: [Read original article]() Author: Andrew Khmylov Published: 2012-04-24T00:00:00Z Content type: tutorial Language: en Sources: [Despite the odds]() Topics: [Exception](), [exceptions](), [Code](), [Logging](), [console]() Tags: [code](), [error](), [exceptions](), [gist](), [how-to](), [logging](), [simple]() ### AI overview This code-focused tutorial demonstrates how to generate readable error logs from nested exceptions in C#. It recursively traverses inner exceptions and handles AggregateException by flattening its InnerExceptions collection. ### Source excerpt Working on error logging for my new application I've realized that I always use the same pattern when it comes to converting actual exceptions into a text form. And since I started posting rare code snippets that I write down all the time on Gist recently, there will be a number of 'sharing code' blog posts in the foreseeable future. The code is rather simple, it traverses down the entire nested exception hierarchy and populates StringBuilder with the appropriate error information. There is a slightly different workflow for AggregateException - we want to flatten its InnerExceptions collection. public string GetExceptionLog(Exception exception) { return UnwrapExceptionTextLoop(new StringBuilder(), 0, exception); } private string UnwrapExceptionTextLoop(StringBuilder sb, int level, Exception e) { if (e == null) { return sb.ToString(); } for (int i = 0; i < level; i++) { sb.Append(">>"); } var aggregate = e as AggregateException; sb.AppendFormat("{0} - {1} [{2}] {3}", e.GetType(), aggregate == null ? e.Message : String.Empty, e.StackTrace, Environment.NewLine); if (aggregate != null) { return String.Join(Environment.NewLine, aggregate.InnerExceptions.Select(inner => UnwrapExceptionTextLoop(sb, level + 1, inner))); } return UnwrapExceptionTextLoop(sb, level + 1, e.InnerException); } Let's put on a simple method that throws several exceptions: public void TestMethod() { try { try { throw new Exception("Inner exception"); } catch (Exception ex) { throw new Exception("Outer exception"); } } catch (Exception ex) { Console.WriteLine(ErrorHelper.GetExceptionLog(ex)); } } And here is the result (I've omitted the large stack trace information): System.Exception - Outer exception [ at Client.App.TestMethod()..] >>System.Exception - Inner exception [ at Client.App.TestMethod()..] ## XePatch Released DevFeed: [XePatch Released]() Original publisher: [Read original article]() Published: 2011-08-20T21:09:52Z Content type: release Language: en Sources: [Eaton Works Feed]() Topics: [Xbox]() Tags: [editor](), [simple](), [small](), [xbox]() ### AI overview XePatch is a small, simple Xbox 360 patch viewer and editor. ### Source excerpt A small and simple Xbox 360 patch viewer/editor. ## Reformater avec pgloader DevFeed: [Reformater avec pgloader]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2011-08-05T09:26:00Z Content type: tutorial Language: fr Sources: [Dimitri Fontaine]() Topics: [etl]() Tags: [articles](), [etl](), [simple]() ### AI overview This article explains how to use pgloader's reformatting function. It presents reformatting as the Transform phase of an ETL process and describes pgloader as a simple solution for ETL needs. ### Source excerpt Dans la série de nos articles sur pgloader, le dernier venu détaille comment utiliser la fonction de reformatage de cet outil. Dans le cadre d'utilisation d'un ETL, cela est assimilé à la phase Transform, ce qui fait de pgloader une solution simple pour vos besoins d'ETL.