{
    "version": "https://jsonfeed.org/version/1.1",
    "title": "Geekist.co",
    "home_page_url": "https://geekist.co/",
    "feed_url": "https://geekist.co/feed-enriched.json",
    "description": "Geekist is brewed daily with </code>, late nights, and Lora serif dreams.",
    "language": "en-US",
    "items": [
        {
            "id": "https://geekist.co/?p=5643",
            "url": "https://geekist.co/how-to-roast-potatoes-in-an-air-fryer-a-gargantuan-task/",
            "title": "How to Roast Potatoes in an Air Fryer. A Gargantuan Task.",
            "summary": "How to roast crispy, golden air-fryer potatoes with fluffy centres, a serving multiplier, adjustable spices and one gloriously sarcastic domestic encounter.",
            "image": "https://img.geekist.co/wp-content/uploads/2026/11/air-fryer-roast-potatoes-golden-crispy.webp",
            "date_published": "2026-11-16T20:06:59Z",
            "date_modified": "2026-11-17T05:52:57Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Fables for Food"
            ],
            "content_html": "<p><em>On the peculiar relationship between software architecture and the humble potato.</em></p>\nA NOTE FROM THE PRE-KETO KITCHEN\n<p>This story predates my keto adventures. These are actual potatoes, and they come with actual starch. In other words, this is <strong>not a keto recipe</strong>. Imagine that.</p>\n\n\n<p>I've always thought potatoes were rather remarkable.</p>\n<p>Think about it. You could boil one, fry one, mash one, bake one or even bury one in the ground, and the damn thing might reward you with more potatoes.</p>\n<p>Try doing that with a carrot.</p>\n<p>Actually, don't. I have absolutely no idea what happens when you bury a carrot.</p>\n<p>But I digress.</p>\n<p>There's something reassuring about a vegetable that demands so little of us. A little heat, some seasoning, perhaps a generous helping of butter. And out comes something marvellous.</p>\n<p>Which brings me to a rather peculiar conversation I had with Simo.</p>\n<p>I'd been working on fundamental architecture writings. Tell me what's new?</p>\n<p>Now, software architecture is one of those things that can keep someone occupied for hours. There's always another abstraction to consider. Another boundary to examine. And just when you think you've found something elegant, along comes another perfectly reasonable question that threatens to unravel the whole bloody thing.</p>\n<p>I hadn't slept much either.</p>\n<p>So just as I was deep in some morbid architectural abstraction, Simo decided to introduce an entirely different problem.</p>\n<p>“BBBBB ah. You know how to roast potatoes? Might be diffucult”</p>\n<p>...</p>\n<p>What?</p>\n<p>Now, I should explain something about Singlish.</p>\n<p>The words themselves are only half the conversation. The other half lives somewhere between the tone, the expression and a certain rather sophisticated ability to make an innocent sentence sound like a formal assessment of someone's intellectual capabilities.</p>\n<p><em>“Might be diffucult.”</em></p>\n<p>Might...? Might!</p>\n<p>We're talking about a potato here. Not the Large Hadron Collider.</p>\n<p>Although, come to think of it, they both involve applying tremendous amounts of energy to something and observing what happens.</p>\n<p>Probably where the similarities end.</p>\n<p>I think.</p>\n<p>Anyway, I was, in fact, preoccupied with more pressing matters.</p>\n<p>“Oh dear. That's quite a feat baby. I'm dealing with much smaller problems.... like Feature Driven Architecture and Application Programming Interfaces :(”</p>\n<p>A perfectly reasonable response, I thought.</p>\n<p>Except I was talking to a woman who had already decided that the most pressing problem in the known universe was getting some potatoes roasted.</p>\n<p>And if those potatoes happened to emerge golden brown, beautifully crisp on the outside, fluffy on the inside, with just enough salt and butter to make one forget one's manners at the dinner table, well, all the better.</p>\n<p>Preferably without her having to do any of the roasting.</p>\n<p>Therein lay the problem.</p>\n<p>Not the potatoes.</p>\n<p><em>Me</em>.</p>\n<p>Because I was sitting there contemplating the fundamental structure of software, when there was a perfectly serviceable kitchen several feet away. Complete with an air fryer. And presumably, potatoes.</p>\n<p>Simo wasn't having any of it.</p>\n<p>“Seeing you hardly slept and all. Seems like a gargantuan task”</p>\n<p><em>Gargantuan.</em></p>\n<p>Good Lord.</p>\n<p>How big were these potatoes?</p>\n<p>Were we feeding a family? A small village? Had someone discovered an unusually large specimen requiring specialist equipment and a permit from the National Parks Board?</p>\n<p>Or perhaps she'd mistaken the air fryer for a commercial blast furnace.</p>\n<p>I mean, I rather enjoy cooking. Especially when there are spices involved. Throw in some garlic, rosemary, paprika, a generous coating of oil, and the wonderful smell of something roasting begins to fill the kitchen.</p>\n<p>I love that smell.</p>\n<p>That slightly toasted garlic aroma mingling with herbs. The occasional hiss as hot oil meets moisture. And, if all goes well, that lovely golden crust which announces that the inside is about to be soft and fluffy.</p>\n<p>Mmmm.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/2026/11/air-fryer-roast-potatoes-crispy-fluffy-closeup.webp\" alt=\"Close-up of a fork holding a crispy golden roast potato chunk split open to show its fluffy white interior, with rosemary and more air-fried potatoes behind.\" /></figure>\n<p>Actually, now <strong>I wanted potatoes too</strong>.</p>\n<p>Damn it.</p>\n<p>But I still had work to do.</p>\n<p>So, rather than abandon my architectural musings in favour of a root vegetable, I decided to share something I'd been contemplating.</p>\n<p>Something rather profound, I thought.</p>\n<p>I mean, if someone is going to question my ability to roast a potato, surely I'm entitled to question their appreciation of abstract computational structures?</p>\n<p>Of course I am.</p>\n<p>So, with all the earnestness I could muster, I asked:</p>\n<p>“Well, can you perhaps share your thoughts? <em>Atoms is to Components as is Features is to Molecules</em> - I was thinking. What do you think?”</p>\n<p>There.</p>\n<p>An intellectual proposition worthy of serious contemplation. A moment of reflection, perhaps. Some thoughtful deliberation.</p>\n<p>Maybe even a question?</p>\n<p>Simo replied after about 2 <em>grand</em> seconds:</p>\n<p>“This sounds easier than roasting potatoes.”</p>\n<p>...</p>\n<p>Of course it does.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/2026/11/air-fryer-roast-potatoes-ingredients.png\" alt=\"Whole potatoes with cooking oil, garlic powder, paprika, rosemary, salt, black pepper and optional chilli flakes arranged beside an air fryer.\" /><figcaption>The assembled ingredients. A deceptively modest beginning to a gargantuan undertaking.</figcaption></figure>\n<h2>Air-Fryer Roast Potatoes</h2>\n<p>Right. Potatoes.</p>\n<p>For anyone similarly burdened with the gargantuan responsibility of roasting a few humble tubers, here's a perfectly workable air-fryer recipe.</p>\n<p>And yes, we're aiming for that lovely crisp exterior with a soft, fluffy center. Not a lump of disappointment.</p>\n\n\n<p>THE GARGANTUAN POTATO LAB</p>\n<h3>Make yourself useful. Roast something.</h3>\n<p>Set the table, multiply the potatoes, and leave the chilli somewhere within reach. Simo has already decided who is cooking.</p>\n\n<strong>How many are we feeding?</strong>Two medium potatoes per person\n2\n\n\n<p>The ingredients</p>\n<ul>\n<li>Medium potatoes<strong>4 potatoes</strong></li>\n<li>Cooking oil<strong>2 tbsp</strong></li>\n<li>Garlic powder<strong>1 tsp</strong></li>\n<li>Paprika<strong>1 tsp</strong></li>\n<li>Dried rosemary, thyme or mixed herbs<strong>½ tsp</strong></li>\n<li>Salt &amp; black pepper<strong>To taste</strong></li>\n</ul>\n\n\nOptional chilli flakes0 tsp\n<p>Adjust heat per person. Total chilli scales with the people you're feeding.</p>\n<p> \n</p>\nAll is well\n<p>Four potatoes. A little garlic. A civilised amount of seasoning. No one has called the fire brigade. Yet.</p>\n\n190°C air fryer3–5 min preheat15–20 min roasting*\n*Batch larger servings; adding people doesn't magically enlarge the basket.\n<p><br />\n</p>\n\n\n<h3>Method: Golden Outside, Fluffy Inside</h3>\n01\n\n<h4>Wash and cut</h4>\n<p>Wash the potatoes thoroughly and cut them into roughly 2.5 cm chunks. I rather like leaving the skins on. There’s something about that slightly wrinkled, crispy skin that makes the whole affair more interesting.</p>\n\n\n02\n\n<h4>Parboil, if you fancy</h4>\n<p>For an especially fluffy interior, parboil the chunks in salted water for about five minutes. Drain them thoroughly and let the surface moisture evaporate. Give them a gentle toss in the colander if you fancy roughening the edges a little. Those rough edges are rather important. They provide more surface area to brown and crisp up.</p>\n\n\n03\n\n<h4>Season generously</h4>\n<p>Toss the potatoes with your oil, garlic powder, paprika, herbs, salt and black pepper. Make sure every piece gets a decent coating. Add the optional chilli flakes if you have decided the potatoes deserve an argument.</p>\n\n\n04\n\n<h4>Preheat</h4>\n<p>Preheat the air fryer to 190°C for three to five minutes.</p>\n\n\n05\n\n<h4>Give them room</h4>\n<p>Arrange the potatoes in a single layer, allowing enough space for hot air to circulate. If you’re feeding more than a couple of people, cook in batches rather than piling everything into the basket.</p>\n\n\n06\n\n<h4>Roast until golden</h4>\n<p>Air-fry for approximately 15–20 minutes, shaking the basket every five minutes. Larger pieces may need a little longer. You’re looking for beautifully browned edges, a crisp exterior and a centre that yields easily to a fork.</p>\n\n\n\n<p>A little garlic aioli or sour cream on the side would be lovely.</p>\n<p>And <em>butter</em>.</p>\n<p>Good Lord, don't forget the butter.</p>\n<p></p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 13,
                        "name": "Fables for Food",
                        "slug": "fables-for-food"
                    }
                ],
                "recipe": {
                    "@context": "https://schema.org",
                    "@type": "Recipe",
                    "@id": "https://geekist.co/how-to-roast-potatoes-in-an-air-fryer-a-gargantuan-task/#recipe",
                    "mainEntityOfPage": "https://geekist.co/how-to-roast-potatoes-in-an-air-fryer-a-gargantuan-task/",
                    "name": "Air-Fryer Roast Potatoes",
                    "recipeYield": "2",
                    "recipeIngredient": [
                        "Medium potatoes: 4 potatoes",
                        "Cooking oil: 2 tbsp",
                        "Garlic powder: 1 tsp",
                        "Paprika: 1 tsp",
                        "Dried rosemary, thyme or mixed herbs: 0.5 tsp",
                        "Salt & black pepper: To taste",
                        "Optional chilli flakes"
                    ],
                    "image": "https://img.geekist.co/wp-content/uploads/2026/11/air-fryer-roast-potatoes-golden-crispy.webp",
                    "keywords": "non-keto",
                    "recipeInstructions": [
                        {
                            "@type": "HowToStep",
                            "text": "Wash the potatoes thoroughly and cut them into roughly 2.5 cm chunks. I rather like leaving the skins on. There’s something about that slightly wrinkled, crispy skin that makes the whole affair more interesting.",
                            "name": "Wash and cut"
                        },
                        {
                            "@type": "HowToStep",
                            "text": "For an especially fluffy interior, parboil the chunks in salted water for about five minutes. Drain them thoroughly and let the surface moisture evaporate. Give them a gentle toss in the colander if you fancy roughening the edges a little. Those rough edges are rather important. They provide more surface area to brown and crisp up.",
                            "name": "Parboil, if you fancy"
                        },
                        {
                            "@type": "HowToStep",
                            "text": "Toss the potatoes with your oil, garlic powder, paprika, herbs, salt and black pepper. Make sure every piece gets a decent coating. Add the optional chilli flakes if you have decided the potatoes deserve an argument.",
                            "name": "Season generously"
                        },
                        {
                            "@type": "HowToStep",
                            "text": "Preheat the air fryer to 190°C for three to five minutes.",
                            "name": "Preheat"
                        },
                        {
                            "@type": "HowToStep",
                            "text": "Arrange the potatoes in a single layer, allowing enough space for hot air to circulate. If you’re feeding more than a couple of people, cook in batches rather than piling everything into the basket.",
                            "name": "Give them room"
                        },
                        {
                            "@type": "HowToStep",
                            "text": "Air-fry for approximately 15–20 minutes, shaking the basket every five minutes. Larger pieces may need a little longer. You’re looking for beautifully browned edges, a crisp exterior and a centre that yields easily to a fork.",
                            "name": "Roast until golden"
                        }
                    ],
                    "author": {
                        "@type": "Person",
                        "name": "GuruGeek"
                    },
                    "datePublished": "2026-11-16T20:06:59Z"
                },
                "recipe_details": {
                    "ingredients": [
                        {
                            "id": "potato",
                            "label": "Medium potatoes",
                            "mode": "proportional"
                        },
                        {
                            "id": "oil",
                            "label": "Cooking oil",
                            "mode": "proportional"
                        },
                        {
                            "id": "garlic",
                            "label": "Garlic powder",
                            "mode": "proportional"
                        },
                        {
                            "id": "paprika",
                            "label": "Paprika",
                            "mode": "proportional"
                        },
                        {
                            "id": "herbs",
                            "label": "Dried rosemary, thyme or mixed herbs",
                            "mode": "proportional"
                        },
                        {
                            "id": "seasoning",
                            "label": "Salt & black pepper",
                            "mode": "unquantified"
                        },
                        {
                            "id": "chilli",
                            "label": "Optional chilli flakes",
                            "mode": "adjustable"
                        }
                    ],
                    "dietary_classification": "non-keto"
                },
                "rich_media": [
                    {
                        "title": "Make yourself useful. Roast something.",
                        "url": "https://geekist.co/how-to-roast-potatoes-in-an-air-fryer-a-gargantuan-task/#gk-potato-recipe",
                        "has_controls": true,
                        "description": "Set the table, multiply the potatoes, and leave the chilli somewhere within reach. Simo has already decided who is cooking."
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/?post_type=geek_repo_cur&#038;p=5451",
            "url": "https://geekist.co/github/the-seo-framework-wordpress-seo-plugin/",
            "title": "The SEO Framework: quiet SEO, with room to make it your own",
            "summary": "We use The SEO Framework on Geekist, even though the public site is static. Here's why its automated metadata, optional extensions and developer hooks are such a useful combination.",
            "image": "https://img.geekist.co/wp-content/uploads/2026/11/sybrew-the-seo-framework-logo.png",
            "date_published": "2026-11-15T12:18:54Z",
            "date_modified": "2026-11-15T12:18:54Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/sybrew/the-seo-framework\" title=\"sybrew/the-seo-framework - Stars: 491\">Stars491</a><a href=\"https://github.com/sybrew/the-seo-framework\" title=\"sybrew/the-seo-framework - Forks: 66\">Forks66</a><a href=\"https://github.com/sybrew/the-seo-framework\" title=\"sybrew/the-seo-framework - Updated: 6d ago\">Updated6d ago</a><a href=\"https://github.com/sybrew/the-seo-framework\" title=\"sybrew/the-seo-framework - Language: PHP\">LanguagePHP</a><a href=\"https://github.com/sybrew/the-seo-framework\" title=\"sybrew/the-seo-framework - License: GPL-3.0\">LicenseGPL-3.0</a>\n<p>\n</p><h2><strong>What it is</strong></h2>\n<p>There is a particular kind of WordPress plugin we appreciate: one that does its job without trying to become the main character of the dashboard. <a href=\"https://github.com/sybrew/the-seo-framework\">The SEO Framework</a> is a rather good example. We use it on Geekist.</p>\n<p>A search engine doesn't see a website quite the way a person does. Alongside the writing, images and links, it looks for signals explaining which page is which, what each page is about and how related pages fit together. The SEO Framework generates much of that information from WordPress itself: page titles and descriptions, canonical URLs, indexing instructions, social previews and structured data.</p>\n<p>The appealing part is how little ceremony it demands. It starts with sensible defaults, gives each post or page its own controls when needed and shows a compact, colour-coded <em>SEO Bar</em> in WordPress's content lists. No endless dashboard advertising, no theatrical promises that a particular keyword score will win Google over.</p>\n<p>Geekist introduces a twist: <strong>our public website is a static export of WordPress</strong>. We edit on WordPress, use The SEO Framework to produce the right page metadata, then publish the rendered pages through Simply Static. Visitors don't need to run WordPress or the SEO plugin to receive a title, canonical link, Open Graph tags or Schema.org JSON-LD. Those are already part of the exported HTML.</p>\n<p>That distinction matters. A static export carries the <em>output</em>, not the running WordPress plugin. Something like a server-generated redirect, a dynamically produced sitemap or a search endpoint needs its own static-export or hosting treatment. We let the authoring system do what it does well, then verify what actually makes it to the public site.</p>\n<h2><strong>What’s new</strong></h2>\n<p>The <a href=\"https://theseoframework.com/release-notes/tsf/5-2-0-complete/\">5.2 release, named “Complete”</a>, arrived in October 2026 with changes that are especially useful for publishers.</p>\n<p><strong>Authors finally get their own SEO controls.</strong> Previously, many author-archive settings came from global defaults. Now authors can manage archive titles, descriptions, social images, canonical URLs, indexing preferences and redirects. The sitemap respects whether an author archive is actually meant to appear in search results.</p>\n<p><strong>Generated metadata is easier to edit.</strong> Rather than retyping the title or description that TSF proposes, editors can click into the generated text and change only what needs changing. Existing installations may need to enable this in their layout settings. That sounds small until you've edited several hundred articles.</p>\n<p><strong>More control over what search engines and social networks see.</strong> The release adds Fediverse creator attribution for services such as Mastodon, clearer breadcrumb controls across post types, and a stylesheet for sitemaps as browsers move away from XSLT rendering. These are the rather unglamorous details that make a publishing system easier to trust.</p>\n<p>The subsequent <a href=\"https://theseoframework.com/release-notes/tsf/5-2-1/\">5.2.1 release in November</a> concentrates on performance and polish: less work building the SEO Bar, faster title and description processing, improved keyboard operation and a fix for Twitter Card metadata on certain archives. The developers report sub-millisecond overhead on the public routes they benchmarked. That matters most on a dynamic WordPress site; on a static public site, visitors consume the generated output without executing TSF at request time.</p>\n<p>\n</p><h2><strong>What else is similar to it</strong></h2>\n<p><a href=\"https://yoast.com/wordpress/plugins/seo/\"><strong>Yoast SEO</strong></a> offers a broad toolkit with editorial analysis, search previews and a large ecosystem. For authors who want a running commentary on every paragraph they write, its guidance can be useful. The SEO Framework takes a quieter approach, relying more heavily on sensible automatic metadata and contextual controls.</p>\n<p><a href=\"https://rankmath.com/\"><strong>Rank Math</strong></a> brings many SEO features into one plugin, including integrations and reporting. <a href=\"https://www.seopress.org/\"><strong>SEOPress</strong></a> is another established option for metadata, sitemaps and structured data, with free and paid features. They're all viable ways to manage WordPress SEO; the difference is in how much interface, automation and additional tooling you want.</p>\n<p>The SEO Framework's free <a href=\"https://theseoframework.com/extension-manager/\"><strong>Extension Manager</strong></a> is part of that comparison. It offers optional features rather than packing everything into the core plugin. <strong>Articles</strong> enriches posts with structured data and a news sitemap; <strong>Focus</strong> gives keyword-oriented editorial guidance; <strong>Local</strong> adds business information; and the free <strong>Transport</strong> extension helps migrate metadata from other SEO plugins. Some extensions require a paid plan.</p>\n<p>For a site like Geekist, which already has its own editorial and publishing machinery, the ability to choose only the extensions we need is considerably more appealing than installing a second content-management department inside WordPress.</p>\n<h2><strong>Why it’s different</strong></h2>\n<p>The philosophy is restrained: generate good metadata automatically, respect WordPress conventions and stay out of the writer's way. The plugin doesn't need to advertise itself across the dashboard to be useful. Its work turns up where it belongs — in the page's HTML and the editor controls that affect it.</p>\n<p>But there's more depth here than the minimal interface suggests. <strong>The SEO Framework is designed to be extended.</strong> Its <a href=\"https://theseoframework.com/extensions/\">Extension Manager catalogue</a> supplies ready-made modules for things like article markup, local businesses, keyword guidance and migrations. You can choose an established extension instead of maintaining a home-grown solution.</p>\n<p>For developers, the more interesting door is the <a href=\"https://kb.theseoframework.com/kb/filter-reference-for-the-seo-framework/\">filter API</a> and <a href=\"https://kb.theseoframework.com/kb/action-reference-for-the-seo-framework/\">action hooks</a>. There are hooks to adjust generated titles and descriptions, change indexing rules, add sitemap URLs, alter social-image selection and work with the SEO Bar. The structured-data API even exposes <code>the_seo_framework_schema_graph_data</code>, letting a small custom plugin modify the Schema.org graph before it is printed. The documentation gives a concrete example of attaching a <code>VideoObject</code> using a post's custom fields.</p>\n<p><strong>That's the route for making your own extensions.</strong> You don't need to modify TSF's core files or force a custom feature into the official Extension Manager catalogue. A conventional WordPress plugin or must-use plugin can register TSF's documented filters and actions, read your own metadata and change the resulting SEO output. The official extension packages are useful examples of how the authors organise additional functionality, but the documented hooks are the simpler integration boundary for an independent project.</p>\n<p>Our static setup makes that especially interesting. Imagine custom repository metadata, editorial series or rich-media details feeding the site's Schema.org output. The integration runs inside WordPress while Simply Static renders the page; the resulting JSON-LD and social tags then travel with the exported HTML. Just make sure canonical URLs, image URLs and site references end up pointing at the public domain, rather than the private WordPress installation. <a href=\"https://docs.simplystatic.com/article/97-how-to-replace-urls\">Simply Static's URL-replacement settings</a> are part of that equation.</p>\n<p>It's a neat division of responsibility: WordPress remains the editorial workshop, The SEO Framework interprets the material, our own integrations can refine it, and the public website receives the finished artefact. Sometimes the cleverest architecture is deciding which machinery never needs to run in production.</p>\n<h2><strong>How to get started</strong></h2>\n\n\n<ol>\n<li>You need a WordPress site where you can install plugins. Check your installed WordPress and PHP versions against <a href=\"https://wordpress.org/plugins/autodescription/\">The SEO Framework's current requirements</a>; the 5.2 line requires WordPress 7.0 or newer. If you're exploring without a site, use its <a href=\"https://playground.wordpress.net/?plugin=autodescription&amp;login=1&amp;url=/wp-admin/edit.php\">WordPress Playground demo</a>.</li>\n<li>Think about the job you want the plugin to do. Basic page titles, descriptions and canonical URLs work with the core plugin. Structured data for articles, keyword guidance and migration tools are available through optional <a href=\"https://theseoframework.com/extensions/\">extensions</a>.</li>\n<li>If you export a static website, know which address WordPress uses internally and which domain the public site serves. The final canonical URLs, Open Graph images and sitemap links need to refer to the public destination, not merely look correct in the private editor.</li>\n</ol>\n\n\n<ol>\n<li>In WordPress, go to <strong>Plugins → Add New Plugin</strong>, search for <strong>The SEO Framework</strong>, install and activate it. Its default settings already generate essential metadata. Browse the SEO settings once to understand the available controls.</li>\n<li>Edit an existing page or post. Find its SEO settings and compare the generated title and description with what the page actually says. Change a field if you can improve it, save the post and inspect the rendered page source for <code>&lt;meta name=\"description\"&gt;</code>, <code>rel=\"canonical\"</code> and Open Graph tags.</li>\n<li>Want extra features? Install the separate, free <a href=\"https://kb.theseoframework.com/kb/how-to-install-the-extension-manager/\">Extension Manager</a>, then explore <strong>Articles</strong>, <strong>Focus</strong>, <strong>Local</strong> or <strong>Transport</strong> depending on the site. Some features require a subscription; there's no need to activate everything.</li>\n<li>Want to customise your own? Create a small custom WordPress plugin and start with a single documented filter, such as <code>the_seo_framework_title_from_generation</code> for generated titles, or <code>the_seo_framework_schema_graph_data</code> for JSON-LD. The <a href=\"https://kb.theseoframework.com/kb/structured-data-supported-by-the-seo-framework/#developers-customizing-the-graph\">structured-data guide</a> includes an example adding video metadata from custom post fields. Keep the integration separate from TSF so it survives plugin updates.</li>\n<li>For a static site, run your normal export after making a change. Compare the exported HTML with the WordPress-rendered page. Check that the <em>public</em> canonical URL, social images and structured-data references survived correctly.</li>\n</ol>\n\n\n<ol>\n<li><strong>The SEO Framework generates a strange title or description?</strong> Check the post's SEO fields, your global title settings and whether another plugin or theme is generating competing tags. TSF's SEO Bar can help identify the page's current state.</li>\n<li><strong>Your custom hook changes the WordPress preview but not the published site?</strong> Static files won't change until the content is exported and deployed again. Inspect the exported <code>&lt;head&gt;</code>, not just what the WordPress editor displays.</li>\n<li><strong>Canonical links point to the internal WordPress host?</strong> Review <a href=\"https://docs.simplystatic.com/article/97-how-to-replace-urls\">Simply Static's absolute URL replacement</a>. Its guidance explicitly covers canonical and Open Graph URLs. Check the actual generated files rather than assuming all metadata has been rewritten.</li>\n<li><strong>Custom schema duplicates what another extension already emits?</strong> Inspect the final JSON-LD graph and consider enriching an existing entity instead of adding a competing one. The <a href=\"https://kb.theseoframework.com/kb/structured-data-supported-by-the-seo-framework/\">structured-data reference</a> describes the graph hooks and how entity references work.</li>\n<li><strong>A sitemap or redirect works in WordPress but not on the static host?</strong> A dynamic endpoint or HTTP redirect isn't automatically a static file or hosting rule. Ensure your export includes the intended sitemap and that redirects are configured at the public hosting layer where necessary.</li>\n</ol>\n\n\n<p><strong>Explore further:</strong> <a href=\"https://github.com/sybrew/the-seo-framework\">The SEO Framework source</a> · <a href=\"https://theseoframework.com/extensions/\">Available extensions</a> · <a href=\"https://github.com/sybrew/The-SEO-Framework-Extension-Manager\">Extension Manager source</a> · <a href=\"https://kb.theseoframework.com/kb/filter-reference-for-the-seo-framework/\">Customisation filters</a> · <a href=\"https://kb.theseoframework.com/kb/structured-data-supported-by-the-seo-framework/\">Extend the structured-data graph</a> · <a href=\"https://docs.simplystatic.com/article/97-how-to-replace-urls\">Simply Static URL handling</a>.</p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 36,
                        "name": "Modern WordPress Engineering",
                        "slug": "wordpress-engineering"
                    }
                ],
                "code_repository": "https://github.com/sybrew/the-seo-framework",
                "programming_language": "PHP",
                "license": "GPL-3.0"
            }
        },
        {
            "id": "https://geekist.co/?post_type=geek_repo_cur&#038;p=5460",
            "url": "https://geekist.co/github/meteor/",
            "title": "Meteor: the framework that made data feel alive",
            "summary": "Before realtime became a feature checklist, Meteor made applications feel alive. We revisit the magic of DDP, Minimongo and latency compensation, and see how Meteor 3 has brought the idea forward.",
            "image": "https://img.geekist.co/wp-content/uploads/2026/11/meteor-meteor-logo.png",
            "date_published": "2026-11-15T12:06:36Z",
            "date_modified": "2026-11-15T12:31:40Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/meteor/meteor\" title=\"meteor/meteor - Stars: 44.8k\">Stars44.8k</a><a href=\"https://github.com/meteor/meteor\" title=\"meteor/meteor - Forks: 5.3k\">Forks5.3k</a><a href=\"https://github.com/meteor/meteor\" title=\"meteor/meteor - Updated: 4d ago\">Updated4d ago</a><a href=\"https://github.com/meteor/meteor\" title=\"meteor/meteor - Language: JavaScript\">LanguageJavaScript</a><a href=\"https://github.com/meteor/meteor\" title=\"meteor/meteor - License: NOASSERTION\">LicenseNOASSERTION</a>\n<p>\n</p><h2><strong>What it is</strong></h2>\n<p>There was a time when adding a new task in one browser and watching it appear in another felt like a small act of sorcery. No refresh button. No polling loop. No elaborate WebSocket plumbing. Just a change in the data, and the interface followed. <a href=\"https://github.com/meteor/meteor\">Meteor</a> made that experience a first-class part of building an application.</p>\n<p>It's a full-stack JavaScript framework: the server, the browser, the database integration and much of the development workflow are designed to work together. You can build with React, Blaze, Vue, Svelte or Solid rather than adopting an entirely new way to write every interface. Meteor's distinctive idea is what happens <em>behind</em> those interfaces.</p>\n<p>The server publishes the data a user is allowed to receive. The browser subscribes to it and keeps a small local copy using <strong>Minimongo</strong>. Meteor's <strong>Distributed Data Protocol (DDP)</strong> carries changes across the connection, while its reactive system helps the interface respond when that local data changes. You aren't simply fetching a page or an API response; you're keeping a selected part of the application's state in conversation with the server.</p>\n<p>Then there is <strong>latency compensation</strong>: a Meteor method can simulate its effect locally, allowing the interface to respond immediately while the actual request makes its way to the server. The server remains authoritative, but the user doesn't necessarily have to wait for the round trip before seeing something happen.</p>\n<p>That combination was Meteor's original magic trick. It wasn't that developers couldn't build live applications without it. It was that Meteor treated the connections between database, server and browser as part of the framework, rather than a pile of plumbing you had to invent anew for every project.</p>\n<h2><strong>What’s new</strong></h2>\n<p>For a while, the question surrounding Meteor was whether its original ideas could survive the modern JavaScript ecosystem. Meteor 3 answered the hardest part by removing the old <strong>Fibers</strong> dependency and moving server-side database work to ordinary <code>async</code>/<code>await</code>. That was a deep architectural renovation, not a cosmetic version bump.</p>\n<p>The <a href=\"https://docs.meteor.com/history\">Meteor 3.6 release</a> on 9 November 2026 continues the modernisation. <strong>Native TypeScript declarations</strong> let developers generate types for installed Meteor packages with <code>meteor types</code>, while package authors can ship their own. Existing applications can adopt this when they're ready.</p>\n<p><strong>Rspack 2 and React 19.2</strong> modernise the build experience, including faster development workflows, React Refresh and support for React Compiler. The bundled runtime moves to <strong>Node.js 26</strong>, and new local development databases use <strong>MongoDB 8</strong>. Meteor also added pnpm-workspace starters and an installable progressive web app starter.</p>\n<p>An especially interesting addition is <strong>server instrumentation</strong>. The new package exposes events from methods, publications and DDP connections, so the reactive machinery that once felt magical becomes easier to measure and understand. This builds on Meteor 3.5's work around MongoDB Change Streams and more resilient DDP connections.</p>\n<p>The <a href=\"https://github.com/meteor/meteor/releases/tag/release%2FMETEOR%403.6.1\">3.6.1 maintenance release</a> followed on 12 November with Node.js security updates and hardening around authentication, DDP messages and archive handling. The engine is being modernised without abandoning what made it worth building in the first place.</p>\n<p>\n</p><h2><strong>What else is similar to it</strong></h2>\n<p><a href=\"https://geekist.co/github/next-js-a-full-stack-react-framework/\">Next.js</a> also gives JavaScript developers a framework that spans browser and server. Its strengths lie in React, rendering, routing and the surrounding application ecosystem. But a Next.js application usually chooses and connects its own data layer, caching and live-update services. Meteor arrives with a more opinionated answer to how changing data reaches a user's screen.</p>\n<p><a href=\"https://www.convex.dev/\"><strong>Convex</strong></a> tackles a closely related problem from another direction. It offers a reactive backend with live queries and server functions that work with frontend frameworks. For someone who wants Meteor-like data behaviour while retaining a separately chosen application framework, that's an interesting comparison.</p>\n<p><a href=\"https://supabase.com/\"><strong>Supabase</strong></a> brings databases, authentication and realtime capabilities around PostgreSQL. It's a backend platform rather than a complete JavaScript application framework, so you typically assemble more of the frontend-to-backend relationship yourself.</p>\n<p><a href=\"https://geekist.co/github/astro-a-web-framework-built-for-content-driven-sites/\">Astro</a> is worth mentioning for the opposite reason. It's excellent for websites where most of the job is presenting content quickly, and only selected parts need interactivity. If you're building a publication, you probably don't need Meteor's live-data machinery. If you're building a collaborative application where people watch the same information change, the equation looks rather different.</p>\n<h2><strong>Why it’s different</strong></h2>\n<p>Meteor's real achievement was <strong>coherence</strong>. It took problems developers were solving separately — application state, database changes, client caches, server calls, authentication and hot development feedback — and offered a model in which the pieces already understood each other.</p>\n<p>Consider a shared task board. Alice changes a task's status; Bob sees the updated board. The conventional approach may involve a mutation endpoint, a cache invalidation strategy, a realtime channel and client-state reconciliation. Meteor's publication, subscription and Minimongo model can express much of that as one ongoing data relationship. You still write the rules defining what each user may see and do, but you don't have to assemble every synchronisation mechanism yourself.</p>\n<p>There's a trade-off hiding inside that elegance. Live queries aren't free: the server must observe relevant database changes and deliver them to the right subscribers. Broad publications, missing indexes or unnecessarily reactive data can become expensive. The most successful Meteor applications treat publication design, authorisation and observation costs as deliberate engineering choices, not things the framework will magically optimise away.</p>\n<p>And that's why Meteor remains interesting. The JavaScript industry has spent years developing better tools for state, caching, synchronisation and optimistic interfaces. Meteor bundled a remarkably coherent opinion about those problems early on. It may not be the answer to every application, but its central question — <em>why should the user have to think about the journey between their action and everyone else's screen?</em> — hasn't aged a day.</p>\n<h2><strong>How to get started</strong></h2>\n\n\n<ol>\n<li>You'll need a recent Node.js installation (Meteor's installer calls for Node.js 24 or newer), a code editor and a terminal. Meteor runs on macOS, Linux and Windows. For its bundled local MongoDB 8, Windows users need Windows 11 or Windows Server 2022.</li>\n<li>You don't need to install MongoDB separately for a new local project. Meteor brings its own development database, so you can focus on the application first.</li>\n<li>Choose whether you want to explore Meteor with <strong>React</strong> or its original reactive UI library, <strong>Blaze</strong>. Both have <a href=\"https://docs.meteor.com/tutorials/\">official tutorials</a>; we'll use React for the first run.</li>\n</ol>\n\n\n<ol>\n<li>Install the Meteor CLI with <code>npx meteor</code>. Then create a React application with <code>meteor create meteor-lab --release 3.6.1</code>. React is the default starter; the interactive <code>meteor create</code> wizard also offers Blaze, Vue, Svelte and more.</li>\n<li>Run <code>cd meteor-lab</code> followed by <code>meteor run</code>. Open <code>http://localhost:3000</code> and you'll see your first Meteor application, with the local server and MongoDB managed for you.</li>\n<li>Now follow the <a href=\"https://docs.meteor.com/tutorials/react/\">official React task-list tutorial</a> through collections, publications, subscriptions and methods. It shows how to publish a set of tasks from the server and subscribe to it using <code>useSubscribe</code> and <code>useTracker</code>.</li>\n<li>Here's the satisfying bit: once you've built the reactive task list, open it in <strong>two browser windows</strong>. Add or change a task in one and watch the other respond. You're watching DDP, Minimongo and the interface working together, without writing your own WebSocket handler.</li>\n</ol>\n\n\n<ol>\n<li><strong>The <code>meteor</code> command isn't found?</strong> Reopen your terminal and try <code>meteor --version</code>. The <a href=\"https://docs.meteor.com/about/install\">installation guide</a> has npm and platform-specific alternatives.</li>\n<li><strong>The local database refuses to start?</strong> Check the <a href=\"https://docs.meteor.com/about/install#prereqs\">supported platform requirements</a>. Meteor 3.6's bundled MongoDB 8 requires newer operating-system libraries on Linux and Windows 11 for local Windows development.</li>\n<li><strong>Upgrading an existing Meteor 3.5 project?</strong> Back up its local MongoDB 7 data and follow the <a href=\"https://docs.meteor.com/about/install#updating-local-database\">MongoDB 8 upgrade instructions</a> before opening the database with 3.6. A fresh starter doesn't need this migration.</li>\n<li><strong>The second browser isn't updating?</strong> Merely creating a starter app doesn't establish a publication. Complete the tutorial's server publication and client subscription steps, and check that both windows are connected to the same running application.</li>\n<li><strong>Looking at old Meteor 2 examples?</strong> Server-side database methods changed with Meteor 3. Follow current examples using <code>insertAsync</code>, <code>countAsync</code> and <code>Meteor.callAsync</code> where appropriate.</li>\n</ol>\n\n\n<p>One misplaced command became <a href=\"https://geekist.co/its-a-security-thing/\">a MongoDB reset minutes before a VIP demo</a> at Heardable. Our 2016 notes on <a href=\"https://geekist.co/how-to-ssr-with-apollostack-and-meteor-react-router-ssr/\">a Meteor–Apollo server-rendering workaround</a> capture the less magical parts of full-stack development. An earlier experiment with <a href=\"https://geekist.co/building-a-zoomable-ui-with-meteor-js-greensock/\">a zoomable UI built with Meteor and Greensock</a> shows what we were building with the framework back in 2015.</p>\n<p><strong>Explore further:</strong> <a href=\"https://github.com/meteor/meteor\">Meteor on GitHub</a> · <a href=\"https://docs.meteor.com/tutorials/react/\">Build a reactive React app</a> · <a href=\"https://docs.meteor.com/tutorials/data-loading/data-loading\">Understand publications and subscriptions</a> · <a href=\"https://docs.meteor.com/history\">Meteor release history</a> · <a href=\"https://forums.meteor.com/t/meteor-3-6-is-out-with-rspack-2-native-typescript-types-and-node-js-26/64861\">What changed in Meteor 3.6</a> · <a href=\"https://forums.meteor.com/\">Meteor community</a>.</p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 20,
                        "name": "Framework",
                        "slug": "framework"
                    }
                ],
                "code_repository": "https://github.com/meteor/meteor",
                "programming_language": "JavaScript"
            }
        },
        {
            "id": "https://geekist.co/?post_type=geek_repo_cur&#038;p=5510",
            "url": "https://geekist.co/github/coolify-self-hosted-paas-operational-tradeoffs/",
            "title": "Coolify: put your apps online, on servers you control",
            "summary": "Coolify gives your own servers a friendly dashboard for deploying websites, apps and databases. Here's what it does, how it compares and how to try your first deployment.",
            "image": "https://img.geekist.co/wp-content/uploads/2026/11/coolify-official.png",
            "date_published": "2026-11-15T11:46:42Z",
            "date_modified": "2026-11-15T11:46:42Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/coollabsio/coolify\" title=\"coollabsio/coolify - Stars: 66.1k\">Stars66.1k</a><a href=\"https://github.com/coollabsio/coolify\" title=\"coollabsio/coolify - Forks: 6.0k\">Forks6.0k</a><a href=\"https://github.com/coollabsio/coolify\" title=\"coollabsio/coolify - Updated: 4d ago\">Updated4d ago</a><a href=\"https://github.com/coollabsio/coolify\" title=\"coollabsio/coolify - Language: PHP\">LanguagePHP</a><a href=\"https://github.com/coollabsio/coolify\" title=\"coollabsio/coolify - License: Apache-2.0\">LicenseApache-2.0</a>\n<p>\n</p><h2><strong>What it is</strong></h2>\n<p>You've built a website or an app. It works beautifully on your computer. Now comes the awkward part: getting it onto the internet and keeping it running. <a href=\"https://github.com/coollabsio/coolify\">Coolify</a> makes that part considerably easier.</p>\n<p>Think of Coolify as a control room for your own servers. Instead of remembering a collection of commands to install an application, connect a domain, arrange HTTPS and check whether everything is still running, you do much of it from a friendly dashboard. Coolify can deploy websites, apps, databases and ready-made services, then show you their logs, settings and status.</p>\n<p>You bring the server. That might be a rented <strong>VPS</strong> (a virtual private server, essentially a computer you rent on the internet), a machine at home or another Linux server you control. Coolify connects to it over SSH, the usual secure way of managing a server remotely. It can take a project from GitHub and turn it into a running application, or start a ready-made Docker image without needing any code.</p>\n<p>There's a useful choice from the beginning. <strong>Self-hosted Coolify</strong> is free software that you install and manage yourself. With <a href=\"https://coolify.io/docs/choose-your-path\">Coolify Cloud</a>, the Coolify team operates the dashboard for you, but <em>your apps still run on servers you provide</em>. Both offer the same core features. You choose who looks after the control room.</p>\n<h2><strong>What’s new</strong></h2>\n<p>The recent <a href=\"https://github.com/coollabsio/coolify/releases/tag/v4.7.0\">4.7 release</a> makes Coolify more useful after the excitement of the first deployment has worn off.</p>\n<p><strong>Less wasted work when you push code.</strong> Imagine making three changes to an app in quick succession. Previously, all three might queue up for deployment. Coolify can now cancel older queued deployments triggered by Git changes so it concentrates on the newest version. Manual deployments and rollbacks aren't swept away by that default.</p>\n<p><strong>Better visibility into security.</strong> Coolify added optional container-image vulnerability scanning. A container image is the packaged software your server runs; scanning it can highlight known security issues and suggest newer versions. The scans run on your server, with results available in the dashboard.</p>\n<p><strong>More useful backups.</strong> Database and storage backups gained additional destinations, including SFTP, FTPS and WebDAV. These give you more ways to store copies away from the server doing the work. Coolify also expanded its API and MCP tools, making it easier to manage deployments and inspect security findings from other software or AI assistants.</p>\n<p><a href=\"https://github.com/coollabsio/coolify/releases/tag/v4.7.5\">Version 4.7.5</a> follows with smaller fixes for API-token settings and IPv6 backup connections. Not every improvement needs fireworks; it's rather nice when the everyday controls simply become more dependable.</p>\n<p>\n</p><h2><strong>What else is similar to it</strong></h2>\n<p><a href=\"https://github.com/Dokploy/dokploy\"><strong>Dokploy</strong></a> is probably the closest comparison. It also lets you deploy apps and databases to servers you control, with Docker Compose, backups, monitoring and templates for common services. It's worth comparing the dashboards and deployment workflows if you're choosing a self-hosted home for several projects.</p>\n<p><a href=\"https://github.com/caprover/caprover\"><strong>CapRover</strong></a> offers another straightforward route from an app to a running service. It's built around Docker, with its own web dashboard, HTTPS and app-management commands. It can be attractive if you want a simpler, established deployment approach.</p>\n<p>Services such as <a href=\"https://www.heroku.com/\">Heroku</a> or <a href=\"https://vercel.com/\">Vercel</a> take a different approach: you deploy to infrastructure operated by the provider. That's wonderfully convenient when you don't want to manage a server. Coolify gives you more say over where your software runs, while leaving server upkeep in your hands.</p>\n<p>The deciding question is surprisingly ordinary: <em>Do you want someone else to host the whole thing, or would you rather operate your own servers with a dashboard doing much of the repetitive work?</em></p>\n<h2><strong>Why it’s different</strong></h2>\n<p>Coolify's appeal isn't that it invented deployment. It's that it brings several jobs together in one place. Connect your code, choose how to build it, add your domain and deploy. Coolify can take care of the container, routing and HTTPS certificate, and show you what happened if a deployment fails.</p>\n<p>It can also manage databases and hundreds of ready-made services. That makes it handy for a small product with several moving parts: a website, an API, a database and perhaps an analytics tool. You can manage them together instead of maintaining a separate set of instructions for every service.</p>\n<p>A particularly reassuring part of the design is that the actual applications run as ordinary containers on your servers. Coolify is the management layer, not a special runtime your software must depend on forever. If you stop using the dashboard, those running containers don't suddenly evaporate.</p>\n<p>Of course, a tidy dashboard doesn't magically maintain the machine underneath. Your server still needs updates, sufficient memory and backups that can actually be restored. Coolify removes a great deal of deployment busywork; it doesn't remove ownership. For someone who likes controlling their own infrastructure, that's the attraction rather than the catch.</p>\n<h2><strong>How to get started</strong></h2>\n\n\n<ol>\n<li>Choose your route. With <a href=\"https://coolify.io/docs/start-with-self-hosted\">self-hosted Coolify</a>, you'll install the dashboard on a Linux server. With <a href=\"https://coolify.io/docs/start-with-cloud\">Coolify Cloud</a>, you'll create an account and connect a server you own. Cloud manages the dashboard, not the server where your app will run.</li>\n<li>For self-hosting, a spare Linux server is ideal for your first try. Coolify's starting requirement is <strong>2 CPU cores, 2 GB RAM and 10 GB free disk space</strong>, plus room for anything you deploy. You'll need SSH access as a user able to administer the server.</li>\n<li>You won't need a GitHub repository or even a domain for the first experiment. We'll deploy a ready-made Nginx webpage, so you can see the whole process work before adding your own code.</li>\n</ol>\n\n\n<ol>\n<li><strong>Self-hosted route:</strong> connect to your Linux server using SSH and follow the <a href=\"https://coolify.io/docs/start-with-self-hosted\">official installation guide</a>. Its installation command is <code>curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash</code>. It will print an address for the dashboard when it finishes. Open that address and create your administrator account promptly.</li>\n<li><strong>Coolify Cloud route:</strong> follow the <a href=\"https://coolify.io/docs/start-with-cloud\">Cloud setup guide</a> to sign up, connect your server using SSH and confirm Coolify can reach it. You can then follow the same deployment steps as self-hosted users.</li>\n<li>In the dashboard, open <strong>Servers</strong> and check that your server is connected and its proxy is running. The proxy is the part that sends visitors to the correct application; Coolify can start it from the server page.</li>\n<li>Create a project, add a new resource of type <strong>Docker Image</strong>, enter <code>nginx:alpine</code>, and set the exposed port to <code>80</code>. Press <strong>Deploy</strong>. Coolify should give you a generated address; open it to see the Nginx welcome page. That's your first application, running on your server.</li>\n</ol>\n\n\n<ol>\n<li><strong>Can't reach the self-hosted dashboard?</strong> Use the address printed at the end of installation, check that the server is reachable and that the dashboard's port is permitted by your firewall. The installer normally shows a URL using port <code>8000</code>.</li>\n<li><strong>Registration says the setup window closed?</strong> The first administrator account can be created during a short setup window. On the server, run <code>docker restart coolify</code> to reopen it, then create the account.</li>\n<li><strong>The Nginx app deployed but the link won't open?</strong> Check that the server's proxy is running, the container is healthy, and ports <code>80</code> and <code>443</code> are reachable. The <a href=\"https://coolify.io/docs/deploy-your-first-app\">first-app guide</a> walks through these checks.</li>\n<li><strong>Ready to deploy something important?</strong> Save the Coolify installation secrets and configure backups. For self-hosting, the file <code>/data/coolify/source/.env</code> contains keys needed to restore your Coolify instance. Back up your application data separately, whether you use self-hosted or Cloud.</li>\n</ol>\n\n\n<p><strong>Explore further:</strong> <a href=\"https://coolify.io/docs/choose-your-path\">Choose self-hosted or Cloud</a> · <a href=\"https://coolify.io/docs/start-with-self-hosted\">Install Coolify</a> · <a href=\"https://coolify.io/docs/deploy-your-first-app\">Deploy your first app</a> · <a href=\"https://github.com/coollabsio/coolify\">Coolify on GitHub</a> · <a href=\"https://github.com/coollabsio/coolify/releases/tag/v4.7.0\">What's new in 4.7</a>.</p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 35,
                        "name": "Own Your Infrastructure",
                        "slug": "own-your-infrastructure"
                    }
                ],
                "code_repository": "https://github.com/coollabsio/coolify",
                "programming_language": "PHP",
                "license": "Apache-2.0"
            }
        },
        {
            "id": "https://geekist.co/?post_type=geek_repo_cur&#038;p=5509",
            "url": "https://geekist.co/github/wpkernel-javascript-first-wordpress-framework/",
            "title": "WPKernel: the unfinished framework with a working engine",
            "summary": "WPKernel is still very early alpha. But its pipeline already powers Geekist projects, while its PHP AST toolkit shows what happens when code generation becomes structural.",
            "image": "https://img.geekist.co/wp-content/uploads/2026/11/wpkernel-official.png",
            "date_published": "2026-11-15T11:46:36Z",
            "date_modified": "2026-11-15T11:46:36Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/wpkernel/wpkernel\" title=\"wpkernel/wpkernel - Stars: 2\">Stars2</a><a href=\"https://github.com/wpkernel/wpkernel\" title=\"wpkernel/wpkernel - Forks: 1\">Forks1</a><a href=\"https://github.com/wpkernel/wpkernel\" title=\"wpkernel/wpkernel - Updated: 28d ago\">Updated28d ago</a><a href=\"https://github.com/wpkernel/wpkernel\" title=\"wpkernel/wpkernel - Language: TypeScript\">LanguageTypeScript</a><a href=\"https://github.com/wpkernel/wpkernel\" title=\"wpkernel/wpkernel - License: EUPL-1.2\">LicenseEUPL-1.2</a>\n<p>\n</p><h2><strong>What it is</strong></h2>\n<p>There's a peculiar moment in software development when the tool you're building becomes less interesting than the machinery you invented to build it. <a href=\"https://github.com/wpkernel/wpkernel\">WPKernel</a> is having one of those moments.</p>\n<p>We began with an ambitious idea: build modern WordPress products without constantly repeating the same intentions in PHP and JavaScript. Describe what a feature needs in TypeScript, let the tooling work out what belongs where, and use WordPress's own capabilities wherever possible. Resources, actions, jobs, blocks and events would have a consistent place in that picture.</p>\n<p>The complete WordPress framework is <strong>very early alpha and not working as a finished product</strong>. But two pieces developed a life of their own: <a href=\"https://github.com/wpkernel/wpkernel/tree/main/packages/pipeline\">the pipeline engine</a> and <a href=\"https://github.com/wpkernel/wpkernel/tree/main/packages/php-json-ast\">the PHP AST toolkit</a>. The pipeline has become part of every Geekist project. The framework may be unfinished, but the engineering beneath it is quite real.</p>\n<p>What's a pipeline? Picture preparing dinner. Sauce and meat can be prepared separately. Cooking has to wait for both. Serving has to wait for cooking. When someone burns the sauce, something has to decide what happens next. Our <a href=\"https://geekist.co/the-hidden-machine-inside-modern-tooling/\">Hidden Machine Inside Modern Tooling</a> article explores that exact idea with an interactive kitchen. It grew from the work behind WPKernel.</p>\n<h2><strong>What’s new</strong></h2>\n<p>The interesting progress has come from making the machinery useful in its own right, rather than polishing an unfinished WordPress framework.</p>\n<p><strong>A pipeline that understands dependencies.</strong> <code>@wpkernel/pipeline</code> reached <a href=\"https://github.com/wpkernel/wpkernel/blob/main/packages/pipeline/CHANGELOG.md\">version 2.0.0</a> in August 2026. Its original serial helper model evolved into a dataflow graph: a map of tasks and the results they depend on. Independent work can run together. A task that needs two earlier results waits for both, regardless of which finishes first.</p>\n<p>It also knows how to handle failed work. The engine can prepare changes, commit them in a predictable order, and coordinate compensating actions backwards when something goes wrong. That is more disciplined than a chain of scripts hoping for the best. The engine manages a run inside one process; recovery across restarts belongs to whatever application hosts it.</p>\n<p><strong>PHP code without the string gymnastics.</strong> <code>@wpkernel/php-json-ast</code> works with an <em>abstract syntax tree</em>, or AST. Think of it as code broken into meaningful pieces: functions, conditions, arguments and return statements. Its typed TypeScript builders can assemble those pieces, while its PHP-Parser bridge supports reading, changing and printing PHP source. The low-level builders are established; the broader authoring surface is still evolving.</p>\n<p>Neither package depends on the whole WPKernel vision coming together. That separation is precisely what makes them interesting.</p>\n<p>\n</p><h2><strong>What else is similar to it</strong></h2>\n<p>If you want to create a WordPress block today, the official <a href=\"https://github.com/WordPress/gutenberg/tree/trunk/packages/create-block\"><code>@wordpress/create-block</code></a> tool does exactly that. It creates a plugin with the necessary PHP, JavaScript and build tooling. It isn't trying to provide WPKernel's proposed application architecture.</p>\n<p><a href=\"https://github.com/10up/wp-scaffold\"><strong>10up WP Scaffold</strong></a> gives WordPress projects a ready-made starting structure for themes, plugins and assets. It solves the question of how to begin a project. WPKernel's experiment asks how the moving pieces inside it might be described, generated and coordinated.</p>\n<p><a href=\"https://github.com/nikic/PHP-Parser\"><strong>nikic/PHP-Parser</strong></a> is a foundation for the PHP AST work, not a rival. It turns PHP source into a tree that software can inspect or transform. WPKernel's toolkit builds typed TypeScript tools around that representation.</p>\n<p>The pipeline is different again. It's <strong>framework-independent</strong>; you can use <code>@wpkernel/pipeline</code> in a TypeScript project that has never heard of WordPress. There's no need to adopt an unfinished framework to benefit from its most mature engine.</p>\n<h2><strong>Why it’s different</strong></h2>\n<p>The idea behind WPKernel was to stop making developers express the same decision in several places. TypeScript knows what the application wants. PHP knows what WordPress expects. A dependable generation process could help them agree without leaving a trail of duplicated glue.</p>\n<p>Two questions sit at the centre of that process. <em>What has to happen before something else can happen?</em> That's the pipeline's job. <em>What does the PHP we're generating actually mean?</em> That's where the AST comes in. It is the difference between assembling a working machine from understood parts and gluing strings together until they look like source code.</p>\n<p>The pipeline has gone well beyond an architectural sketch: it now operates throughout Geekist's projects. The PHP AST is still developing its public authoring layer, but already has typed constructors and machinery for parsing and transforming PHP. Those are different levels of readiness, and both are worth understanding on their own merits.</p>\n<p>There's a nice irony in all this. We set out to build a WordPress framework and ended up building an engine we use for things that have nothing to do with WordPress. Sometimes the best thing a project produces isn't the thing on the label.</p>\n<h2><strong>How to get started</strong></h2>\n\n\n<ol>\n<li>Start with the ideas, not an installation. Read <a href=\"https://geekist.co/the-hidden-machine-inside-modern-tooling/\">The Hidden Machine Inside Modern Tooling</a> and play with its interactive kitchen. You can see what runs in parallel, what has to wait and what happens when the sauce goes wrong.</li>\n<li>Want to explore the actual engine? You'll need a little JavaScript or TypeScript and Node.js 20 or newer. The pipeline works in an ordinary project; a WordPress installation isn't required.</li>\n<li>The PHP AST is a separate, more specialised experiment. Some familiarity with PHP will help. You can explore its basic building blocks without attempting to set up the entire WPKernel framework.</li>\n</ol>\n\n\n<ol>\n<li>In a small practice project, install <code>@wpkernel/pipeline</code> with <code>npm install @wpkernel/pipeline</code>. Open the <a href=\"https://github.com/wpkernel/wpkernel/blob/main/packages/pipeline/README.md\">package's example</a>. It creates a greeting and some punctuation separately, then combines them into one message.</li>\n<li>Follow the connections. The first two tasks can run independently. The final task needs both outputs. That's a tiny dependency graph — and the same pattern powering the kitchen demonstration in Hidden Machinery.</li>\n<li>Curious about generating PHP? Install <code>@wpkernel/php-json-ast</code> in a TypeScript practice project and try the <a href=\"https://github.com/wpkernel/wpkernel/blob/main/packages/php-json-ast/README.md\">basic example</a>: <code>buildReturn(buildScalarString('Hello'))</code>. It describes a PHP return statement as structured data rather than a handwritten string.</li>\n<li>From there, browse the <a href=\"https://github.com/wpkernel/wpkernel\">WPKernel source</a> to see how the two ideas developed. The full framework is a work in progress; the standalone packages are the better place to experiment.</li>\n</ol>\n\n\n<ol>\n<li><strong>Finding older pipeline examples?</strong> The original helper-based API isn't the same as v2. For new code, import from <code>@wpkernel/pipeline</code> and use <code>createPipeline()</code> and <code>runPipeline()</code>. The older compatibility model lives under <code>@wpkernel/pipeline/v1</code>.</li>\n<li><strong>Expecting rollback to undo everything everywhere?</strong> The pipeline coordinates compensation during a running process. It isn't a durable job queue or a database transaction. Your application still decides how to recover after a restart.</li>\n<li><strong>Getting stuck with PHP AST examples?</strong> Begin with the low-level typed builders from its README. Parsing, printing and transforming complete PHP files involve the PHP bridge and additional dependencies.</li>\n<li><strong>Trying the full WPKernel starter?</strong> You'll encounter unfinished framework behaviour. For now, explore the pipeline and AST independently rather than expecting a complete WordPress development environment.</li>\n</ol>\n\n\n<p><strong>Explore further:</strong> <a href=\"https://geekist.co/the-hidden-machine-inside-modern-tooling/\">The Hidden Machine Inside Modern Tooling</a> · <a href=\"https://github.com/wpkernel/wpkernel\">WPKernel source</a> · <a href=\"https://github.com/wpkernel/wpkernel/tree/main/packages/pipeline\">Pipeline engine</a> · <a href=\"https://github.com/wpkernel/wpkernel/tree/main/packages/php-json-ast\">PHP AST toolkit</a>.</p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 36,
                        "name": "Modern WordPress Engineering",
                        "slug": "wordpress-engineering"
                    }
                ],
                "code_repository": "https://github.com/wpkernel/wpkernel",
                "programming_language": "TypeScript",
                "license": "EUPL-1.2"
            }
        },
        {
            "id": "https://geekist.co/?post_type=geek_repo_cur&#038;p=5507",
            "url": "https://geekist.co/github/openshell-agent-sandbox-permissions-security/",
            "title": "OpenShell: give AI agents a safe place to work",
            "summary": "OpenShell gives AI agents a controlled workspace with clear rules for files, websites and access keys. Here's how it works, what's new and how to try a sandbox.",
            "image": "https://img.geekist.co/wp-content/uploads/2026/11/openshell-official.png",
            "date_published": "2026-11-15T11:46:30Z",
            "date_modified": "2026-11-15T11:49:34Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/NVIDIA/OpenShell\" title=\"NVIDIA/OpenShell - Stars: 21.6k\">Stars21.6k</a><a href=\"https://github.com/NVIDIA/OpenShell\" title=\"NVIDIA/OpenShell - Forks: 2.1k\">Forks2.1k</a><a href=\"https://github.com/NVIDIA/OpenShell\" title=\"NVIDIA/OpenShell - Updated: 3d ago\">Updated3d ago</a><a href=\"https://github.com/NVIDIA/OpenShell\" title=\"NVIDIA/OpenShell - Language: Rust\">LanguageRust</a><a href=\"https://github.com/NVIDIA/OpenShell\" title=\"NVIDIA/OpenShell - License: Apache-2.0\">LicenseApache-2.0</a>\n<p>\n</p><h2><strong>What it is</strong></h2>\n<p>Imagine hiring an assistant to organise a folder of documents on your computer. You'd happily let them read that folder. But would you also give them your passwords, access to every other folder and permission to send files anywhere on the internet? Probably not. <a href=\"https://github.com/NVIDIA/OpenShell\">OpenShell</a> lets you set those kinds of boundaries for AI assistants.</p>\n<p>Some AI assistants can do much more than answer questions. These <strong>AI agents</strong> can open files, run software and connect to online services on your behalf. OpenShell provides a controlled workspace for them, called a <strong>sandbox</strong>. Think of it as giving the agent a room to work in, with specific doors it can and cannot open.</p>\n<p>You decide which files, programmes and websites an agent can use through a set of rules called a <strong>policy</strong>. OpenShell checks those rules outside the AI agent itself. That matters: a request to “please don't touch my private files” relies on the agent remembering and obeying you. A restriction enforced by the environment can block the action even when the agent tries it.</p>\n<p>OpenShell isn't a chatbot or a new AI model. It's the security layer underneath tools such as Claude Code, <a href=\"https://geekist.co/github/opencode-open-source-coding-agent-reviewable-workflow/\">OpenCode</a> and Codex. It's aimed at people running coding agents or other automation, especially when those agents need to work with real files and online accounts.</p>\n<h2><strong>What’s new</strong></h2>\n<p>The <a href=\"https://github.com/NVIDIA/OpenShell/releases/tag/v0.1.8\">OpenShell 0.1.8 release</a>, published on 10 November 2026, makes those boundaries more dependable.</p>\n<p><strong>Safer handling of access keys.</strong> Some online services need a secret token before they'll accept a request. OpenShell can hold that token on the trusted side of the workspace and add it only when a request is going to an approved service. Version 0.1.8 requires more explicit rules for unusual places those tokens might be sent, such as custom request headers or web addresses.</p>\n<p><strong>Fewer shortcuts around file rules.</strong> A shortcut inside a folder can point somewhere else on the computer. This release prevents a sandbox from starting when a file-access rule follows certain shortcuts through a writable workspace. That closes a subtle route around the intended boundary.</p>\n<p><strong>More predictable behaviour when things go wrong.</strong> The release fixes issues involving sandbox cleanup, failed database connections and diagnostic logs. Those may sound like background details, but they matter when an agent is meant to keep running without creating new problems for its operator.</p>\n<p>The project has also <a href=\"https://github.com/NVIDIA/OpenShell\">joined the Cloud Native Computing Foundation (CNCF)</a>, with its development moving towards the community-led <a href=\"https://github.com/ai-openshell\">ai-openshell</a> organisation. Its main NVIDIA repository remains the place to follow code and releases during that transition.</p>\n<p>\n</p><h2><strong>What else is similar to it</strong></h2>\n<p><a href=\"https://github.com/e2b-dev/E2B\"><strong>E2B</strong></a> provides isolated cloud computers where AI-generated code can run. It's handy when an application needs to start a temporary environment, execute code and collect the result. OpenShell puts more emphasis on controlling an agent's ongoing access to files, networks and credentials, with rules enforced outside that agent.</p>\n<p><a href=\"https://github.com/daytonaio/daytona\"><strong>Daytona</strong></a> also provides programmable environments for development and AI agents. It focuses on creating and managing those workspaces, with tools for files, commands and integrations. OpenShell's distinctive concern is what an agent is allowed to reach once it's running.</p>\n<p><a href=\"https://github.com/Infisical/infisical\"><strong>Infisical</strong></a> is a companion rather than a direct alternative. It helps teams manage sensitive credentials and permissions. OpenShell adds a separate layer by controlling which actions a running agent can actually take. Teams may use both.</p>\n<p>You can also run an agent in an ordinary Docker container. Docker provides isolation, but OpenShell adds agent-focused controls for outbound connections, approved services and credentials. The best fit depends on whether you simply need somewhere to run code or you need to govern what an increasingly independent agent can do.</p>\n<h2><strong>Why it’s different</strong></h2>\n<p>OpenShell has one particularly useful rule: <strong>access has to be allowed, not merely left unblocked</strong>. Suppose an agent needs to read a project and download a package. You can allow the project folder and the required download service without opening your whole computer and every internet destination.</p>\n<p>If the agent tries to contact another website, OpenShell can deny that connection and record what happened. An operator can review the request and decide whether to add a narrowly scoped rule. OpenShell even checks proposed rule changes for risky new permissions before they can be approved automatically.</p>\n<p>The separation of responsibilities is the clever bit. The agent concentrates on its task. A trusted component outside the agent makes the permission decisions and handles credentials for approved destinations. It means an unexpected instruction inside a document or webpage cannot simply persuade the underlying security rules to disappear.</p>\n<p>This is most useful when agents do real work: editing software, reaching business systems or running repeated tasks. For an occasional chat with an AI assistant, there's little reason to install a whole sandbox system. But once an agent can use tools on your behalf, the question changes from “Can it do this?” to “What exactly should it be allowed to do?” OpenShell gives you a practical way to answer.</p>\n<h2><strong>How to get started</strong></h2>\n\n\n<ol>\n<li>OpenShell is a tool for running agents, rather than an app you open and chat to. You'll need a computer with a supported setup: Linux, a Mac with Apple silicon, or Windows using WSL 2 (experimental). You'll also need a supported container or virtualisation system, such as Docker or Podman. The <a href=\"https://docs.nvidia.com/openshell/latest/about/installation\">official installation guide</a> walks through the options.</li>\n<li>For the first experiment, you <strong>don't need an AI account or a paid model</strong>. We'll start by creating an empty sandbox, just to see how a controlled workspace behaves.</li>\n<li>With your container system running, install the OpenShell command-line tool using the command in the <a href=\"https://docs.nvidia.com/openshell/latest/about/installation\">official instructions</a>: <code>curl -LsSf https://raw.githubusercontent.com/NVIDIA/OpenShell/main/install.sh | sh</code>. This installs the CLI and sets up a local gateway, which manages the sandboxes.</li>\n</ol>\n\n\n<ol>\n<li>Open a terminal and type <code>openshell --help</code>. If you see a list of commands, OpenShell is installed.</li>\n<li>Create your practice workspace with <code>openshell sandbox create --name demo</code>. The default image gives you a small Ubuntu environment with no AI agent installed. You should arrive at a terminal <em>inside</em> the sandbox.</li>\n<li>Try <code>pwd</code> or <code>ls</code> inside that sandbox. Now open a <strong>second terminal on your computer</strong> and run <code>openshell policy get demo --full</code>. You'll see the rules that control what the sandbox can reach.</li>\n<li>When you've finished, leave the sandbox shell with <code>exit</code>, then remove your practice workspace from your computer's terminal with <code>openshell sandbox delete demo</code>. Ready to try a real AI agent next? The <a href=\"https://docs.nvidia.com/openshell/latest/about/run-your-first-agent\">official first-agent tutorial</a> shows how to run OpenCode with an approved model provider and controlled access.</li>\n</ol>\n\n\n<ol>\n<li><strong>The command isn't recognised?</strong> Run <code>openshell --help</code> again after reopening your terminal. Check the installation instructions for your operating system if it still cannot be found.</li>\n<li><strong>The sandbox won't start?</strong> Make sure Docker, Podman or your chosen runtime is running. The <a href=\"https://docs.nvidia.com/openshell/latest/about/support-matrix\">support matrix</a> explains which combinations work, and <code>openshell sandbox list</code> can show what was created.</li>\n<li><strong>Something inside the sandbox cannot reach a website?</strong> That may be OpenShell doing its job. Network access is restricted until a policy allows it. The <a href=\"https://docs.nvidia.com/openshell/latest/tutorials/first-network-policy\">first network-policy tutorial</a> demonstrates how to inspect a denied request and grant only the access you intend.</li>\n<li><strong>Connecting a real agent asks for credentials?</strong> Use the <a href=\"https://docs.nvidia.com/openshell/latest/about/run-your-first-agent\">official provider setup</a>. OpenShell can store a credential separately and supply it only to an approved destination, instead of putting the secret directly into the agent's workspace.</li>\n</ol>\n\n\n<p><strong>Explore further:</strong> <a href=\"https://github.com/NVIDIA/OpenShell\">OpenShell on GitHub</a> · <a href=\"https://docs.nvidia.com/openshell/latest/about/overview\">How OpenShell works</a> · <a href=\"https://docs.nvidia.com/openshell/latest/about/run-your-first-agent\">Run your first agent</a> · <a href=\"https://docs.nvidia.com/openshell/latest/tutorials/first-network-policy\">Try a network policy</a> · <a href=\"https://github.com/NVIDIA/OpenShell/releases/tag/v0.1.8\">Release notes</a>.</p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 34,
                        "name": "Agent Security &amp; Isolation",
                        "slug": "agent-security-isolation"
                    }
                ],
                "code_repository": "https://github.com/NVIDIA/OpenShell",
                "programming_language": "Rust",
                "license": "Apache-2.0"
            }
        },
        {
            "id": "https://geekist.co/?post_type=geek_repo_cur&#038;p=5506",
            "url": "https://geekist.co/github/pageindex-vectorless-rag-document-retrieval/",
            "title": "PageIndex: find answers in long PDFs without getting lost",
            "summary": "PageIndex helps AI follow a document's chapters and sections to find relevant answers. See how it works, what's new, and how to try it with a PDF of your own.",
            "image": "https://img.geekist.co/wp-content/uploads/2026/11/pageindex.png",
            "date_published": "2026-11-15T11:46:24Z",
            "date_modified": "2026-11-15T11:46:24Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/VectifyAI/PageIndex\" title=\"VectifyAI/PageIndex - Stars: 40.4k\">Stars40.4k</a><a href=\"https://github.com/VectifyAI/PageIndex\" title=\"VectifyAI/PageIndex - Forks: 3.5k\">Forks3.5k</a><a href=\"https://github.com/VectifyAI/PageIndex\" title=\"VectifyAI/PageIndex - Updated: 3d ago\">Updated3d ago</a><a href=\"https://github.com/VectifyAI/PageIndex\" title=\"VectifyAI/PageIndex - Language: Python\">LanguagePython</a><a href=\"https://github.com/VectifyAI/PageIndex\" title=\"VectifyAI/PageIndex - License: MIT\">LicenseMIT</a>\n<p>\n</p><h2><strong>What it is</strong></h2>\n<p>Imagine a 300-page report containing exactly the answer you need. Searching for a word might turn up dozens of mentions. But if you could look at the table of contents and follow the right chapter, you'd find your answer much faster. <a href=\"https://github.com/VectifyAI/PageIndex\">PageIndex</a> teaches AI to follow that second route.</p>\n<p>PageIndex helps people ask questions about long documents, especially PDFs such as reports, research papers, contracts and technical manuals. First, it makes a map of a document's chapters and sections. Then an AI model uses that map to decide where to look, reads the relevant passages and forms an answer. You can follow references back to the pages it used.</p>\n<p>This belongs to a family of tools called <strong>retrieval-augmented generation</strong>, or <strong>RAG</strong>. Behind the intimidating name is a simple idea: give an AI the right information to read before it answers. Many RAG systems hunt for passages that sound similar to your question. PageIndex pays closer attention to the document's structure and the meaning of its sections.</p>\n<p>There's a <a href=\"https://app.pageindex.ai/\">PageIndex web app</a> for chatting with documents without programming. Developers can also use the open-source Python toolkit in their own apps. Its local version is designed for text-based PDFs; the cloud version can also process scanned pages, diagrams and image-rich documents.</p>\n<h2><strong>What’s new</strong></h2>\n<p><a href=\"https://github.com/VectifyAI/PageIndex/releases/tag/v0.6.0\">PageIndex 0.6.0</a> arrived on 14 November 2026. It brings the local and cloud versions closer together, so developers can use one familiar set of tools whether a document lives on their own machine or in PageIndex Cloud.</p>\n<p><strong>Preparing documents is quicker.</strong> Its Flash engine builds a map from a PDF's layout, including headings and trustworthy bookmarks. This reduces the work needed before you can start asking questions.</p>\n<p><strong>It's easier to connect to other AI tools.</strong> PageIndex now provides ways for developers to give their existing AI assistants access to document search. Cloud collections make it easier to group documents, while the developer can choose which compatible AI model answers the questions.</p>\n<p>The release also improves the costs associated with preparing and searching documents. For readers, the important outcome is simpler: add a document, ask a question and see which part of the document supports the answer.</p>\n<p>\n</p><h2><strong>What else is similar to it</strong></h2>\n<p><a href=\"https://github.com/infiniflow/ragflow\"><strong>RAGFlow</strong></a> is a broader platform for working with documents and AI. It handles processing, searching, chatting and agent workflows. It even supports PageIndex-style document structures. It's a useful direction when you want an entire document-search application rather than focus on the way relevant passages are located.</p>\n<p><a href=\"https://github.com/run-llama/llama_index\"><strong>LlamaIndex</strong></a> gives developers a wide range of building blocks for connecting AI to documents, databases and other information. PageIndex has a narrower speciality: using the organisation of a document to help find an answer.</p>\n<p>For a short PDF, you may not need either one. Uploading it directly to your preferred AI chatbot might already do the job. PageIndex becomes more interesting when a document is long, several sections matter, or you want a repeatable way to search a collection of reports.</p>\n<p>So the choice is less about which product has the biggest feature list and more about what you're trying to do: <em>chat about one file, run a complete document-search system, or build document retrieval into your own app</em>.</p>\n<h2><strong>Why it’s different</strong></h2>\n<p>PageIndex treats a document as something with a story and a structure, not just a pile of text. Imagine a company's annual report mentioning revenue in the introduction, regional results and financial notes. A simple search might find all three. PageIndex can consider the question, follow the document's headings and choose the section most likely to answer it.</p>\n<p>That can be particularly useful for long reports, legal contracts and technical manuals. If the answer depends on a note in another section, the document map gives the AI a way to follow that connection. Its page references also make it easier for you to inspect the original passage.</p>\n<p>It won't be the natural choice for every kind of information. A five-page guide doesn't need elaborate document navigation, while searching thousands of tiny notes is a different challenge from understanding a 200-page report. PageIndex is at its most interesting when the material has clear sections that help explain one another.</p>\n<p>For a first experiment, pick a PDF you know and ask a question whose answer you can find yourself. Then try one that needs two different sections. That small comparison makes the benefit much easier to see.</p>\n<h2><strong>How to get started</strong></h2>\n\n\n<ol>\n<li>Open the <a href=\"https://app.pageindex.ai/\">PageIndex web app</a> if you'd like to try it without writing code. Its sign-in screen offers Google, GitHub and email options.</li>\n<li>Choose a PDF with a clear title and a few sections, such as a public report or user manual. Start with a publicly available document so it's easy to follow along.</li>\n<li>If you're a developer and prefer to use PageIndex locally, have Python 3.10 or newer and access to an AI model provider ready. The <a href=\"https://pageindex.ai/docs/getting-started\">developer guide</a> explains the local and cloud setups.</li>\n</ol>\n\n\n<ol>\n<li><strong>In the web app:</strong> sign in and add your PDF to a document conversation. Ask something straightforward: <em>“Where does this report explain its main recommendations?”</em></li>\n<li>Ask a follow-up that needs a little more thought: <em>“Which section gives the total, and what does the next section say about it?”</em> Follow the references in the answer to see the original pages.</li>\n<li><strong>For developers:</strong> install the toolkit with <code>python -m pip install -U pageindex</code>. The <a href=\"https://pageindex.ai/docs/getting-started\">official Python example</a> shows how to configure your model, create a <code>PageIndexClient</code>, add a PDF with <code>submit_document()</code> and ask with <code>chat()</code>. Local indexing needs a model provider, but no PageIndex Cloud API key.</li>\n<li>Try asking the same question using ordinary PDF search. Notice whether you get the correct section and how easily you can check the answer.</li>\n</ol>\n\n\n<ol>\n<li><strong>Having trouble with a PDF?</strong> For local Python use, try a file with selectable text. Scanned pages and image-heavy PDFs are better suited to PageIndex Cloud, which includes text recognition.</li>\n<li><strong>Not getting the answer you expected?</strong> Mention a year, subject or chapter in the question. Check the referenced page against the original PDF.</li>\n<li><strong>Seeing a Python import error?</strong> Make sure the package was installed into the Python environment you're running. The <a href=\"https://pageindex.ai/docs/getting-started\">setup guide</a> shows the supported installation.</li>\n<li><strong>Getting a model or sign-in error?</strong> The web app uses its own account flow. Local Python requires a configured AI model provider; using PageIndex Cloud from code additionally needs a PageIndex API key.</li>\n</ol>\n\n\n<p><strong>Explore further:</strong> <a href=\"https://app.pageindex.ai/\">Try PageIndex online</a> · <a href=\"https://pageindex.ai/docs/getting-started\">Official getting-started guide</a> · <a href=\"https://github.com/VectifyAI/PageIndex\">Source repository</a> · <a href=\"https://github.com/VectifyAI/PageIndex/releases/tag/v0.6.0\">Release notes</a>.</p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 33,
                        "name": "Memory &amp; Retrieval",
                        "slug": "memory-retrieval"
                    }
                ],
                "code_repository": "https://github.com/VectifyAI/PageIndex",
                "programming_language": "Python",
                "license": "MIT"
            }
        },
        {
            "id": "https://geekist.co/?post_type=geek_repo_cur&#038;p=5504",
            "url": "https://geekist.co/github/opencode-open-source-coding-agent-reviewable-workflow/",
            "title": "OpenCode: an AI coding assistant you can work alongside",
            "summary": "OpenCode can explain a project, help plan changes and write code with you. Here's what makes it useful, what's new in version 2.3, and a friendly first-time guide.",
            "image": "https://img.geekist.co/wp-content/uploads/2026/11/opencode-icon.png",
            "date_published": "2026-11-15T11:46:18Z",
            "date_modified": "2026-11-15T11:46:18Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/anomalyco/opencode\" title=\"anomalyco/opencode - Stars: 227.0k\">Stars227.0k</a><a href=\"https://github.com/anomalyco/opencode\" title=\"anomalyco/opencode - Forks: 30.7k\">Forks30.7k</a><a href=\"https://github.com/anomalyco/opencode\" title=\"anomalyco/opencode - Updated: 1d ago\">Updated1d ago</a><a href=\"https://github.com/anomalyco/opencode\" title=\"anomalyco/opencode - Language: TypeScript\">LanguageTypeScript</a><a href=\"https://github.com/anomalyco/opencode\" title=\"anomalyco/opencode - License: MIT\">LicenseMIT</a>\n<p>\n</p><h2><strong>What it is</strong></h2>\n<p>Ever opened a project full of unfamiliar code and wondered where on earth to begin? <a href=\"https://github.com/anomalyco/opencode\">OpenCode</a> is an AI coding assistant that can look through a project with you, explain how it works, suggest improvements and help make changes. You ask questions in ordinary language. It works with the actual files, so you do not have to copy and paste every snippet into a chat window.</p>\n<p>The slightly technical name for this is a <strong>coding agent</strong>. Unlike a chatbot that only gives advice, an agent can use tools: it can inspect files, run commands and edit code. That's useful, but it also means its actions deserve your attention. OpenCode is available as a desktop app for Windows, macOS and Linux, or as a terminal interface (the text-based window developers use to run commands).</p>\n<p>OpenCode has two helpful ways of working: <strong>Plan</strong> is for examining a problem and discussing what to do; <strong>Build</strong> is for actually making changes. If you are learning, start with Plan and ask it to explain a small project before inviting it to edit anything.</p>\n<p>The software itself is open source and free. It can work with a choice of AI models, including free options; connecting a different provider may involve charges. You do not need to pick a complicated setup just to try it. <a href=\"https://opencode.ai/product\">The official product page</a> explains the available apps and model choices.</p>\n<h2><strong>What’s new</strong></h2>\n<p>OpenCode moves quickly, so dates matter. The most recent main release I verified was <a href=\"https://github.com/anomalyco/opencode/releases/tag/v2.3.0\">version 2.3.0, released on 13 November 2026</a>. It makes working on several tasks feel less like watching one long conversation scroll past.</p>\n<p><strong>Helpers can work in the background.</strong> OpenCode calls these <em>subagents</em>: smaller AI helpers working on parts of a larger job. They can now continue while the main conversation remains available, then report back when they finish. You can keep discussing the work instead of having to wait for each helper in turn.</p>\n<p><strong>Less clutter on screen.</strong> The terminal interface now groups its tool activity into collapsible summaries. That makes the answer easier to read; people who want to inspect each step can turn up the detail in settings. The desktop app also adds <strong>Jump to message</strong>, making it easier to find an earlier request in a long session.</p>\n<p>This is also part of the wider OpenCode 2 generation. Anyone moving from OpenCode 1 should check the <a href=\"https://opencode.ai/docs/migrate-v1\">official migration guide</a>: the command is still <code>opencode</code>, but plugins, server integrations and some configuration rules have changed.</p>\n<p>\n</p><h2><strong>What else is similar to it</strong></h2>\n<p><a href=\"https://github.com/cline/cline\"><strong>Cline</strong></a> is another open-source coding assistant. It has particularly strong editor integrations, including VS Code and JetBrains, as well as desktop and terminal options. It's worth exploring if you want an AI helper close to the editor you already use.</p>\n<p><a href=\"https://github.com/Aider-AI/aider\"><strong>Aider</strong></a> takes a more terminal-and-Git-centred approach. Git is the tool developers use to track changes to a project. Aider makes those changes easier to inspect and undo, and it can run linting and tests as part of its workflow.</p>\n<p><a href=\"https://github.com/OpenHands/OpenHands\"><strong>OpenHands Agent Canvas</strong></a> is a different sort of product: a control centre for running and automating coding agents. It can even run OpenCode as one of its backends. It makes more sense when you want to organise several agents or recurring tasks, rather than simply ask for help with one project.</p>\n<p>They're not a ranking from best to worst. A useful first question is: <em>Where do I want to work?</em> In my editor, in a terminal, with a desktop companion, or across several agents? That choice will tell you more than star counts.</p>\n<h2><strong>Why it’s different</strong></h2>\n<p>OpenCode's strength is how much choice it gives you without insisting on one particular AI model or one working style. You can use the desktop app, work directly in the terminal, switch between Plan and Build, or extend it with tools and integrations as your needs grow.</p>\n<p>For a newcomer, the nicest use case may be the simplest one: open a practice project and ask, <em>“Can you explain what these files do, in plain English?”</em> For an experienced developer, that same tool can help explore an unfamiliar codebase, prepare a change or coordinate several smaller tasks. It can grow with the user instead of demanding all the setup up front.</p>\n<p>There are two boundaries worth understanding. <strong>First, review changes:</strong> an AI can misunderstand a request, just as a person can. Plan mode is useful for discussing changes, but it is not a full security sandbox. The <a href=\"https://opencode.ai/docs/permissions\">permissions guide</a> explains how to require approval before commands or access to other folders. <strong>Second, consider privacy:</strong> the AI model you choose may receive parts of your project to answer you. Don't begin with passwords, customer data or a sensitive workplace repository.</p>\n<p>That is not a reason to avoid OpenCode. It's simply a good reason to start small, learn what it is doing, and give it more responsibility when you're comfortable.</p>\n<h2><strong>How to get started</strong></h2>\n\n\n<ol>\n<li>Choose your starting point. The <a href=\"https://opencode.ai/docs/\">desktop app</a> is friendlier if you prefer clicking through windows; the terminal version is there if you already use command-line tools. Download from the official OpenCode website.</li>\n<li>Prepare a small <strong>practice folder</strong> containing something simple, such as a text README and a tiny JavaScript file. Avoid private documents, passwords and work projects for your first experiment.</li>\n<li>If you chose the terminal version, install it with <code>npm install -g @opencode/cli</code> (requires Node.js). If you prefer not to use commands, the desktop download skips this step.</li>\n<li>You'll need an AI model to answer your questions. OpenCode offers free options, and also lets you connect other providers. Check whether the model you select has a price before you begin.</li>\n</ol>\n\n\n<ol>\n<li>Open OpenCode and select your practice folder. In the terminal, go to that folder and type <code>opencode</code>. The app should open a conversation connected to those files.</li>\n<li>Choose an AI model. In the terminal interface, type <code>/connect</code> to add a provider if needed and <code>/models</code> to choose a model. In the desktop app, follow its model or account controls.</li>\n<li>Select <strong>Plan</strong> mode before your first question. The terminal interface lets you switch modes with <code>Tab</code>. Try this: <em>“I'm new to this project. Please explain what the files do in everyday language. Don't change anything.”</em></li>\n<li>Read the explanation and ask follow-up questions. When you're ready for a first edit, switch to <strong>Build</strong> and try something tiny: <em>“Please add one sentence to the README explaining what this project is for.”</em> Look at what changed before moving on.</li>\n</ol>\n\n\n<ol>\n<li>No answer? Make sure a model is selected. In the terminal, try <code>/models</code>, then <code>/connect</code> if your provider isn't connected. Some providers also need an account or payment method.</li>\n<li>The terminal says <code>opencode: command not found</code>? Check that the installation finished and reopen the terminal. Or use the desktop app, which avoids this command-line setup.</li>\n<li>OpenCode asks to run something you don't recognise? You can stop and ask it to explain the command first. A request to “do nothing” is not a technical permission rule; use the <a href=\"https://opencode.ai/docs/permissions\">permissions settings</a> for stronger boundaries.</li>\n<li>Already installed OpenCode 1? Follow the <a href=\"https://opencode.ai/docs/migrate-v1\">OpenCode 2 migration instructions</a> before replacing it. Both versions use the <code>opencode</code> command, so it's worth checking which one you have.</li>\n</ol>\n\n\n<p><strong>Further reading:</strong> <a href=\"https://opencode.ai/docs/\">Official getting-started guide</a> · <a href=\"https://opencode.ai/docs/cli/providers/\">Connecting an AI model</a> · <a href=\"https://opencode.ai/docs/permissions\">Permissions and approvals</a> · <a href=\"https://github.com/anomalyco/opencode/releases/tag/v2.3.0\">What changed in OpenCode 2.3.0</a> · <a href=\"https://github.com/anomalyco/opencode\">Source code on GitHub</a>. <em>Information checked 15 November 2026.</em></p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 32,
                        "name": "Agent Engineering",
                        "slug": "agent-engineering"
                    }
                ],
                "code_repository": "https://github.com/anomalyco/opencode",
                "programming_language": "TypeScript",
                "license": "MIT"
            }
        },
        {
            "id": "https://geekist.co/the-precise-premise-of-a-promise/",
            "url": "https://geekist.co/the-precise-premise-of-a-promise/",
            "title": "The Precise Premise of a Promise",
            "summary": "A sigh, then an exercise that batters faith: Write of something never promised, as if promises were never made.",
            "date_published": "2026-11-15T03:40:04Z",
            "date_modified": "2026-11-17T03:22:10Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Wordsmith's Forge"
            ],
            "content_html": "<p><em>A sigh, then an exercise that batters faith:</em></p>\n<blockquote>\n<p><em>Write of something never promised, as if promises were never made.</em></p>\n</blockquote>\n<hr />\n<p>Baffling.</p>\n<p>Could one premise precisely a promise?</p>\n<p>Or maybe wonder how a future premises a precise possibility?</p>\n<p><em>A promise.</em></p>\n<p>Ahhh. The precise premise of a promise.</p>\n<p>Precise? There's nothing precise about a premise.</p>\n<p>Then what precisely is a promise?<br />If not merely a premise laced with possibility.</p>\n<p>No. A premise is a possibility?<br />Or. A possibility a premise?</p>\n<p><em>Precisely.</em></p>\n<p>How precisely does one suppose the premise of a promise if the preciseness of a promise was never premised?</p>\n<p>Possibility. Premise.</p>\n<p>One informs the other but... quintessentially misinforms altogether.</p>\n<p>And it does this...</p>\n<p>Precisely.</p>\n<p>Then where is there room for... a promise?</p>\n<p>What is a promise? If all but a glimmer of an uncertain future.</p>\n<p><em>Reassuring nonetheless.</em></p>\n<p>All we have are but meaningless promises.</p>\n<p>Rooted in the precision of the premise of possibility.</p>\n<p>Me writing this is one fulfilled.</p>\n<p>Precisely.</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 11,
                        "name": "The Wordsmith's Forge",
                        "slug": "the-wordsmiths-forge"
                    }
                ],
                "opening_quote": {
                    "context": "A sigh, then an exercise that batters faith:",
                    "text": "Write of something never promised, as if promises were never made."
                }
            }
        },
        {
            "id": "https://geekist.co/?p=5164",
            "url": "https://geekist.co/promises-vs-streams-dams-rivers-and-immigration-checkpoints/",
            "title": "Promises vs Streams: Dams, Rivers and Immigration Checkpoints",
            "summary": "How a simple Node.js image-streaming experiment led to a deeper understanding of data flow, backpressure and the cost of unnecessary completion boundaries.",
            "image": "https://img.geekist.co/wp-content/uploads/2026/11/promises-vs-streams-dams-rivers-and-checkpoints.avif",
            "date_published": "2026-11-07T06:43:52Z",
            "date_modified": "2026-11-15T11:23:57Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tame the Tech",
                "Beneath the Stack"
            ],
            "content_html": "<p><em>Or how an image loading in a browser eventually led to five terabytes a day, oil tankers, and a rather suspicious collection of encrypted SD cards.</em></p>\n<p>I can't remember exactly when I first encountered Node.js. It was early enough that asynchronous programming frequently meant nesting callbacks until the code resembled an archaeological excavation site. I wasn't using Node professionally. I was just playing with it, and one experiment involved streaming an image to a browser.</p>\n<p>The image appeared progressively, from top to bottom, as the bytes arrived. I was used to applications that waited and then presented the finished thing. Here was a browser doing useful work before the operation had finished. I was blown away!</p>\n<p>Before anyone rushes to explain that Apache could stream too: yes, we know. What fascinated me wasn't a server capability. It was the way I'd been thinking about work. Why did I keep treating <em>finished</em> as a prerequisite for <em>started</em>?</p>\n<p>I began organising Node applications around events, with named handlers I could actually follow rather than callbacks nesting into the Earth's crust. I didn't know anything about functional programming at the time. I just liked what happened when the data was allowed to move.</p>\n<h2>You're building a bloody dam again!</h2>\n<p>This eventually became a phrase I'd throw at fellow engineers: <em>“You're building a bloody dam again!”</em> Usually when somebody read an entire payload into memory just to do something that could have been done as it arrived. Lol.</p>\n<p>Think of a river. If we insist on filling a reservoir before using a single drop, we've turned a continuous flow into a batch. Sometimes collecting everything first is necessary. But if the job is to inspect, filter or transform what passes by, why make the whole river wait? That's the bloody dam I'm complaining about.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/2026/11/node-the-bloody-dam-full-reservoir-1024x512.avif\" alt=\"A vast reservoir is trapped behind a solid concrete dam while the riverbed downstream is nearly dry.\" /><figcaption>A reservoir full of data. Nothing useful moves downstream until the entire payload has arrived.</figcaption></figure>\n<figure><figcaption>Flow architecture<strong>The full reservoir</strong>Nothing useful leaves until the entire payload arrives</figcaption>\n\n\n01\nSOURCE\nIncoming data\n\n<p>→</p>\n\n02\nRESERVOIR\nBuffer entire input\n\n<p>→</p>\n\n03\nPROCESS\nOnly after EOF\n\n<p>→</p>\n\n04\nRELEASE\nAll at once\n\n\n\nSwipe to explore the flow →\n</figure>\n\nINTERACTIVE FIELD NOTES · 01\n<h3>Follow the data</h3>\n<p>Watch eight complete records move through the same pipeline. The difference is <em>when</em> we allow work to begin.</p>\n\n\n\n01 · INTAKE<strong>Read</strong><b>0</b>/8\n\n\n<p>  <i></i>→</p>\n02 · RECORD<strong>Validate</strong><b>0</b>/8\n\n\n<p>  <i></i>→</p>\n03 · MAP<strong>Transform</strong><b>0</b>/8\n\n\n<p>  <i></i>→</p>\n04 · OUTPUT<strong>Write</strong><b>0</b>/8\n\n\n\n\n<p>A complete record can be processed without waiting for the rest of the payload.</p>\n<p></p>\n<p>Conceptual illustration. We are comparing an explicit buffering decision with incremental record processing; a Promise does not itself buffer data.</p>\n\n\n\n<p></p>\n<p>Now picture airport immigration. Travellers arrive, an officer checks each passport, and each traveller moves on. Nobody waits for every flight of the day to land before opening the first passport. That's the useful checkpoint: validate one complete record, then let it through. If the counter can't keep up, the queue slows the arrivals. If there's more independent work than one counter can handle, we can open another.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/2026/11/node-immigration-incremental-checkpoint-1024x512.avif\" alt=\"Travellers pass through an airport immigration checkpoint individually, with a passport being inspected while cleared passengers continue onwards.\" /><figcaption>One traveller at a time. Validate the complete record, let it through, and keep the queue moving.</figcaption></figure>\n<figure><figcaption>Flow architecture<strong>The immigration counter</strong>Each complete record can be checked and passed onwards</figcaption>\n\n\n01\nSOURCE\nRecords arrive\n\n<p>→</p>\n\n02\nINSPECT\nValidate one record\n\n<p>→</p>\n\n03\nTRANSFORM\nDo useful work\n\n<p>→</p>\n\n04\nCONTINUE\nNext record\n\n\n\nSwipe to explore the flow →\n</figure>\n<p>That's really the difference. We can wait for everything to arrive, or start working as it comes in. Promises aren't the villain here. They tell us when a job has finished. Streams let us work while it's still happening. Quite often, we want both.</p>\n<p>Early Node made that distinction wonderfully visible. Its HTTP response API let us <code>write()</code> repeatedly and <code>end()</code> when we were done. Yet a familiar pattern in early web tooling was to collect all the <code>data</code> events into a buffer and hand it to a callback only at <code>end</code>. Here's the shape of it, from <a href=\"https://github.com/expressjs/express/blob/0.10.0/lib/express/http.js\">Express 0.10.0's HTTP client</a>:</p>\n\n<pre>res.on('data', function (chunk) {\n  buf += chunk;\n});\n\nres.on('end', function () {\n  callback(null, buf, res);\n});</pre>\n\n<p>Sometimes we really do need the complete response. Fair enough. But here the decision has already been made for us. Nobody gets to touch the data until the last chunk arrives. A perfectly good stream has become a waiting room.</p>\n<h2>Five terabytes. One M2.</h2>\n<p>It really, really, really shines with transform streams. I once had to turn terabytes of JSON logs into CSV for the BI team at DBS, while working on its <a href=\"https://www.dbs.com.sg/personal/marketplace/index.html\">marketplace platform</a>. Around <strong>5TB a day</strong>. The official route involved a military hierarchy of requests to commission high-end AWS machines. By the time those approvals arrived, I'd have missed the deadline.</p>\n<p>So I tried it on an M2. Believe it or not, I was sceptical myself. Then it worked. Not only did it work, the bloody thing was practically flying.</p>\n<p>The trick wasn't some exotic algorithm. It was refusing to treat five terabytes as one object. Read the input incrementally, identify complete records, validate and transform them, and keep moving. The output could branch: CSV for the BI team on one side, compressed archives for S3 on the other. No need to hold the whole dataset hostage while waiting for the last byte.</p>\n<figure><figcaption>Flow architecture<strong>Five terabytes, one pass</strong>Independent outputs without a five-terabyte working set</figcaption>\n\n\n01\nREAD\nJSON log stream\n\n<p>→</p>\n\n02\nFRAME\nComplete records\n\n<p>→</p>\n\n03\nBRANCH\nCoordinate consumers\n\n<p>→</p>\n\n↗   ↘\n\n04\nOUTPUT A\nCSV for BI\n\n\n05\nOUTPUT B\nCompressed S3 archive\n\n\n\n\nSwipe to explore the flow →\n</figure>\n<p>Of course, splitting a stream into two destinations needs a little care. What if S3 slows down while the CSV writer races ahead? Both branches need their own flow control and error handling. Get that right, though, and we can produce both outputs in one pass without swallowing the entire dataset first.</p>\n<p>When I tell other engineers this story, I often get a suspicious look. Five terabytes? On that machine? I understand. <em>I</em> didn't quite believe it until I watched it happen. We're so accustomed to equating large datasets with large fleets of hardware that we forget the distinction between the size of the <em>whole</em> dataset and the size of the <em>working set</em>.</p>\n<h2>Then someone gave me more cores</h2>\n<p>Later, at <a href=\"https://imcventures.vc/2021/10/15/imc-industrial-group-and-imc-ventures-to-test-chord-x-solutions-on-maritime-tranquility/\">Chord X</a>, I had to process terabytes of IoT data from oil tankers. Same shit, different toilet. Lol. This time there were more cores available, and Node.js clustering had entered the picture. Just when I thought I couldn't do much better than streaming, I could distribute independent transform workloads across worker processes.</p>\n<p>Each worker could stream and transform its own share of the data. Clustering gave us more workers, not some magical ability to divide one stream automatically. We still had to split the jobs sensibly. Once we did, though, the ET part of ETL was on steroids.</p>\n<figure><figcaption>Flow architecture<strong>More counters, not a bigger waiting room</strong>Partition jobs, then run independent transforms across workers</figcaption>\n\n\n01\nJOBS\nPartition input\n\n<p>→</p>\n\n\n02\nWORKER A\nTransform\n\n\n03\nWORKER B\nTransform\n\n\n04\nWORKER C\nTransform\n\n\n<p>→</p>\n\n05\nRESULT\nVerified outputs\n\n\n\nSwipe to explore the flow →\n</figure>\n<p>The funny part? Eventually my transform processes were waiting for jobs. Not because the transforms were broken, but because the reads and writes couldn't feed them fast enough. That genuinely took my breath away. I'd spent so much time worrying about processing terabytes that the processors were now waiting on the data. Oh man.</p>\n<h2>The SD-card express</h2>\n<p>And that's only half the tanker story. Every vessel had an Ubuntu server we'd installed, connected to roughly a dozen IoT sensors. We needed to get an enormous amount of data off those ships reliably. Internet access at sea was not exactly cooperating. Ngrok was an absolute pain.</p>\n<p>I could wait for a usable ngrok connection and SSH new server-side code onto the vessel. Old-school deployment. Lol. Oddly enough, sending code <em>to</em> the ship was manageable. Downloading terabytes <em>from</em> it was another matter entirely.</p>\n<p>So we went gloriously physical. Ship engineers, not software engineers, would plug in an empty terabyte-capacity SD-card device. The Ubuntu server detected an authorised device using public/private-key authentication, then streamed the data directly onto it, encrypted. The encryption was useful, of course, but I admit the spy-movie aspect amused me enormously. What was anyone going to do with terabytes of tanker sensor data anyway?</p>\n<p>The server pinged my dashboard back in Singapore. I could monitor the copy and WhatsApp the engineers with progress updates, telling them when to come back. I wanted to expose a little web page so they could see it themselves, but we didn't have the time. The dashboard and WhatsApp did the job.</p>\n<figure><figcaption>Flow architecture<strong>The SD-card express</strong>The physical transport layer was the network</figcaption>\n\n\n01\nAT SEA\nSensors → Ubuntu\n\n<p>→</p>\n\n02\nAUTHENTICATE\nAuthorised device\n\n<p>→</p>\n\n03\nSTREAM\nEncrypted SD card\n\n<p>→</p>\n\n04\nON LAND\nOffice verification\n\n<p>→</p>\n\n05\nANALYSE\nGrafana pipeline\n\n\n\nSwipe to explore the flow →\n</figure>\n<p>When the devices came back to the office, our local machines verified the data. Other engineers then transformed it into the Grafana stack for the data scientists. It was a data-delivery pipeline with a decidedly physical transport layer. Bare metal. No cloud. No nonsense. Fun as hell.</p>\n<p>And the bottleneck? The writes! There was something deeply entertaining about building fast streaming transforms only to find that the humble storage device was the one asking everyone else to slow down.</p>\n<h2>The river still needs floodgates</h2>\n<p>There's a difference between filling the reservoir and using its floodgates. The first makes everything wait. The second controls how quickly the water moves. And that's important, because streaming isn't about flinging data downstream as fast as possible and hoping for the best. What happens when the destination can't keep up? We need <em>backpressure</em>: the ability to stop pulling more data until the consumer has capacity.</p>\n\nINTERACTIVE FIELD NOTES · 02\n<h3>When the destination slows down</h3>\n<p>Turn up the input rate, choke the writer, then switch backpressure on and off. Notice what happens to the waiting queue.</p>\n\n\n\n\nIncoming records14/s\n<p></p>\n2/s20/s\n\n\nWriter capacity6/s\n<p></p>\n2/s20/s\n\nRespect backpressure?\n\n\n\n\nINPUT<i></i>BUFFER<i></i>WRITER\nWaiting records<strong><b>0</b> queued</strong>\n\n\nAccepted / sec<strong>14</strong>\nWritten / sec<strong>6</strong>\nSource held back<strong>0</strong>\n\n<p>Backpressure keeps the working queue bounded by slowing down intake when the writer cannot keep up.</p>\n\n\nSimulation: 0 of 12 seconds\n<p>Illustrative fixed-rate simulation. The buffer holds up to 24 records when backpressure is respected. Without flow control, the model tracks a growing backlog; it does not invent dropped records. Each animation step represents one simulated second.</p>\n\n\n<p></p>\n<p>Here's the small but important piece of Node that captures it:</p>\n\n<pre>for await (const chunk of source) {\n  if (!destination.write(chunk)) {\n    await once(destination, 'drain');\n  }\n}\ndestination.end();</pre>\n\n<p>When <code>write()</code> returns <code>false</code>, we wait for <code>drain</code> before consuming more. In production we'd generally prefer <code>pipeline()</code> for its coordination and error handling, but the principle is right there: regulate the flow instead of accumulating an ever-growing queue.</p>\n<p>We can also work on data immediately without showing anyone an unfinished result. For example, stream the transformed records into a temporary file, then rename it only when everything succeeds. <code>await pipeline()</code> tells us when that job is done. The processing was happening all along.</p>\n<p>And yes, sometimes we have to wait for a complete record. A JSON object might arrive in three chunks. We collect those three chunks, check the record and move on. That's one traveller at immigration, not an entire airport waiting for permission to open.</p>\n<h2>Back to that image</h2>\n<p>It's funny that all of this started with watching an image appear in a browser. No grand architecture diagram. No cloud budget. Just a small experiment that made me wonder why we so often wait for things to finish before doing anything useful.</p>\n<p>Whether it was bank logs or tanker sensors, the lesson was the same. Let the data move. Check and transform it along the way. Slow things down when the next stage can't keep up. Finishing a job matters, but that doesn't mean we have to wait until the end to start.</p>\n<p>I still laugh about the tanker system. We had encrypted SD cards travelling back to Singapore like props from a spy film, and a cluster of transform workers sitting around waiting for the storage devices. It was one helluva ride. And yes, it really did take my breath away.</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    }
                ],
                "rich_media": [
                    {
                        "title": "Follow the data",
                        "url": "https://geekist.co/promises-vs-streams-dams-rivers-and-immigration-checkpoints/#gk-flow-lab-5164",
                        "has_controls": true,
                        "description": "Watch eight complete records move through the same pipeline. The difference is when we allow work to begin."
                    },
                    {
                        "title": "When the destination slows down",
                        "url": "https://geekist.co/promises-vs-streams-dams-rivers-and-immigration-checkpoints/#gk-pressure-lab-5164",
                        "has_controls": true,
                        "description": "Turn up the input rate, choke the writer, then switch backpressure on and off. Notice what happens to the waiting queue."
                    }
                ],
                "references": {
                    "mentions_mcp": false,
                    "github_links": [
                        "https://github.com/expressjs/express/blob/0.10.0/lib/express/http.js"
                    ],
                    "public_product_links": [],
                    "public_products": []
                }
            }
        },
        {
            "id": "https://geekist.co/?p=5145",
            "url": "https://geekist.co/garmin-treadmill-running-accuracy-chatgpt-mcp/",
            "title": "My Garmin Disagreed With My Treadmill. So I Gave ChatGPT the Keys.",
            "summary": "Garmin treadmill distance wrong? Our free Garmin by geekist.co connects Garmin Connect to AI for workout analysis, running trends, activity corrections and structured workouts.",
            "image": "https://img.geekist.co/wp-content/uploads/2026/11/garmin_vs_treadmill_ai_run_correction.avif",
            "date_published": "2026-11-05T18:17:52Z",
            "date_modified": "2026-11-14T02:17:56Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tools of the Trade",
                "Tame the Tech"
            ],
            "content_html": "<p><em>The treadmill said <strong>15.1 km/h</strong>. My Garmin said <strong>12.3 km/h</strong>. Apparently, we'd been doing two completely different runs on the same machine.</em></p>\n<hr />\n<p>I was there. I ran it. My legs remember it rather well.</p>\n<p>And somehow that disagreement sent me down a rabbit hole that lasted a year and a half. Watches, apps, sensors, spreadsheets. All because I wanted the numbers from a run I'd actually completed.</p>\n<h2>From one watch to another… and another</h2>\n<p>This nonsense started in <strong>April 2025</strong>. Yes, really.</p>\n<p>First it was <a href=\"https://www.lifefitness.com/en-us/treadmills\">Life Fitness</a> treadmills, a <a href=\"https://www.mi.com/global/product/xiaomi-smart-band-9/\">Mi Band 9</a>, <a href=\"https://www.apple.com/health/\">Apple Health</a> and <a href=\"https://www.mapmyrun.com/\">MapMyRun</a>. The chest strap showed my heart rate beautifully on the treadmill screen. Export the workout, though, and apparently my heart had taken the day off.</p>\n<p>The treadmill knew how fast I was going. The chest strap knew what my heart was doing. Getting both into the same workout, however, seemed to require a diplomatic summit between devices that refused to speak to each other.</p>\n<p>Then came the older, stubbornly offline treadmills at <a href=\"https://www.fitnessfirst.com/sg/en/Home\">Fitness First</a>. We tried <a href=\"https://apps.apple.com/sg/app/ismoothrun/id410965399\">iSmoothRun</a>, more recording combinations and eventually an <a href=\"https://www.apple.com/apple-watch-series-11/\">Apple Watch Series 11</a>. Roughly <strong>S$1,200</strong> later, I returned the watch.</p>\n<p>Lovely watch, actually. But after spending that much money, I thought asking it to let me correct an indoor run wasn't particularly unreasonable.</p>\n<p>So we started looking at things to attach to shoes. <a href=\"https://www.stryd.com/us/en\">Stryd</a>, <a href=\"https://coros.com/us/coros-pod2\">COROS POD 2</a>, even <a href=\"https://npe.fit/products/runn\">NPE RUNN</a>, which attaches to the treadmill. Then came the smart-shoe archaeology: <a href=\"https://en.wikipedia.org/wiki/Nike%2B\">Nike+</a>, <a href=\"https://en.wikipedia.org/wiki/Adidas_miCoach\">Adidas miCoach</a> and assorted attempts to turn footwear into an information system.</p>\n<p>Think about that for a moment. We were considering buying a computer for my <em>shoe</em> because the treadmill and the watch couldn't agree on how far I'd run. Sisyphus, but with Bluetooth.</p>\n<h2>18 May. Two records. And a watch with opinions.</h2>\n\n<h3>The two runs</h3>\n\n\n      \n\n        <strong>3.03 km (PB)</strong>\n<p>Treadmill · Expected: <b>12:55</b> (4:16/km)</p>\n\n\n        Garmin recorded<br />\n        <strong>3.03 km at 4:48/km</strong>\n      \n\n\n      \n\n        <strong>1.00 km (PB)</strong>\n<p>Treadmill · Expected: <b>4:00</b> (15 km/h)</p>\n\n\n        Garmin recorded<br />\n        <strong>0.91 km at ~4:33/km</strong>\n      \n\n\n\n<p>On <strong>18 May 2026</strong>, I first ran <strong>3.03 km in 12:55</strong>, averaging about <strong>4:16/km</strong>. Then, after a break, I ran <strong>1 km in 4:00</strong>. That's 15 km/h. Two personal records, better than the ones I'd set at eighteen. More than two decades later! I don't think I need to explain how that felt.</p>\n<p>Garmin had other ideas. Both original recordings were wrong. For the <strong>3.03 km</strong> run, it reported <strong>4:48/km</strong> instead of <strong>4:16/km</strong>. Thirty-two seconds <em>added</em> to my pace for every kilometre. For the later <strong>1 km</strong>, the original FIT lap recorded <strong>907.62 m in 4:07</strong>, or about <strong>4:33/km</strong>. The treadmill had shown 1 km in 4:00. Two personal bests, neither recorded properly. Both activities have since been corrected in Garmin Connect.</p>\n<p>Garmin was still where I wanted my running history to live. It had the laps, pace, heart rate and everything else. I just wanted to correct the activity <em>there</em>. Not create another spreadsheet that politely disagreed with the original record forever.</p>\n<h2>So I gave ChatGPT the keys</h2>\n<p>So we built <strong>Garmin by geekist.co</strong>. One connection between Garmin Connect and ChatGPT, or another compatible AI assistant. Sign in to Garmin, complete verification if needed, and suddenly we can actually ask questions about the runs instead of playing detective with screenshots.</p>\n<p>Reading the data was the first bit of fun. We could inspect laps, heart-rate samples, personal records, effort, feeling and activity photos where Garmin had them. We could look at sleep, HRV, stress, steps, weight and Body Battery too. And instead of trying to remember what happened last Tuesday, we could ask for trends across weeks of running. Distance, pace, frequency, duration. The lot.</p>\n<p>Then came the part I really wanted: <em>writing back</em>. Correct supported activity details, add a manual run, import FIT, GPX or TCX files, or build a structured workout with the assistant. We can preview the workout before saving it. Changes need separate permission and confirmation, and deleting something needs explicit approval. I have spent far too much effort recording these runs to let an overeager assistant casually erase one.</p>\n<p>It's free. We can also compare Garmin with other sources, including Google Sheets, when a run needs a second opinion.</p>\n<p>The treadmill photograph is still my favourite example. Take a picture of the console and paste it into ChatGPT. The assistant can read the distance and time, compare the figures with Garmin, and propose a supported correction. I review the change before it's saved. But what started as an argument with a treadmill has turned into something much bigger. We've put the features, updates and feedback channel at <a href=\"https://garmin.geekist.co/\">garmin.geekist.co</a>.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/2026/11/garmin-treadmill-photo-in-chatgpt-workflow-1024x512.avif\" alt=\"Illustration of a ChatGPT conversation containing a photograph of treadmill running stats, a Garmin comparison and a review correction action.\" /><figcaption>Photograph the treadmill, attach it in ChatGPT, compare with Garmin, and review the proposed change. Illustrative mock-up, not an actual captured session.</figcaption></figure>\n<h2><a href=\"https://connect.garmin.com/modern/profile/35656634-8731-4c0c-abe4-b580692bb5e2\">Come run with me ↗</a></h2>\n<p>If you want to follow my runs and occasional ridiculous experiments, <a href=\"https://connect.garmin.com/modern/profile/35656634-8731-4c0c-abe4-b580692bb5e2\">come run with me on Garmin Connect</a>. I'd love to hear about the runs that sent other people down similarly ridiculous rabbit holes.</p>\n<p>Leave a comment with the watch and treadmill you use, what went missing and what you'd like to fix. Those stories are far more useful to us than guessing which feature to build next.</p>\n<p>Personally, I'd rather be running. :)</p>\n\n\n    <img src=\"https://geekist.co/wp-content/uploads/2026/11/garmin-product-logo.png\" alt=\"Garmin by geekist.co logo: a runner and connected data nodes\" width=\"68\" height=\"68\" />\n\n<p>Garmin</p>\nby<img src=\"https://geekist.co/wp-content/uploads/Geekist.co_.svg\" alt=\"Geekist.co\" width=\"113\" height=\"32\" />\n\n<p>    Free to use\n  </p>\n\n\n<p>Your Garmin data, in conversation</p>\n<h3>Get more from every run.</h3>\n<p>Your watch has recorded the details. Connect Garmin to your AI assistant and start asking better questions about them.</p>\n\n        <a href=\"https://garmin.geekist.co/\">Try Garmin by Geekist ↗</a>\n\n\n<p>What you can do</p>\n<p><strong>01</strong> Explore activities, laps and daily health</p>\n<p><strong>02</strong> Compare running trends and personal records</p>\n<p><strong>03</strong> Preview and approve running or cycling workouts</p>\n<p><strong>04</strong> Correct supported activities and import files</p>\n\n\n\n<p>It's free. Changes require your approval.</p>\n\n<p>Independently developed by Geekist. Not affiliated with or endorsed by Garmin.</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 6,
                        "name": "Tools of the Trade",
                        "slug": "tools-of-the-trade"
                    }
                ],
                "rich_media": [
                    {
                        "title": "The two runs",
                        "url": "https://geekist.co/garmin-treadmill-running-accuracy-chatgpt-mcp/#may-2026-running-records",
                        "has_controls": false,
                        "description": "Treadmill · Expected: 12:55 (4:16/km)"
                    },
                    {
                        "title": "Get more from every run.",
                        "url": "https://geekist.co/garmin-treadmill-running-accuracy-chatgpt-mcp/#garmin-mcp-product",
                        "has_controls": false,
                        "description": "Your watch has recorded the details. Connect Garmin to your AI assistant and start asking better questions about them."
                    }
                ],
                "references": {
                    "mentions_mcp": false,
                    "github_links": [],
                    "public_product_links": [
                        "https://garmin.geekist.co/"
                    ],
                    "public_products": [
                        {
                            "@type": "SoftwareApplication",
                            "name": "Garmin by geekist.co",
                            "url": "https://garmin.geekist.co/",
                            "description": "Your watch has recorded the details. Connect Garmin to your AI assistant and start asking better questions about them."
                        }
                    ]
                }
            }
        },
        {
            "id": "https://geekist.co/whats-today-called/",
            "url": "https://geekist.co/whats-today-called/",
            "title": "What’s today called?",
            "summary": "A dedication and plea to the begotten, Write as if it’s already forgotten.",
            "date_published": "2026-02-18T18:59:00Z",
            "date_modified": "2026-11-17T04:23:27Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Wordsmith's Forge"
            ],
            "content_html": "<p>A dedication and plea to the begotten, </p>\n<blockquote>\n<p><em>Write as if it’s already forgotten.</em></p>\n</blockquote>\n<hr />\n<p>It is Thursday. Is it not? A remembrance of a god. </p>\n<p>He might disagree, the limelight brought him nought.<br />Should’ve charged a fee, but… a god couldn’t be bought. </p>\n<p>Yet the measure of pleasure is a ledger of treasure untoward pressure for gesture.<br />And no. </p>\n<p>There is no account for the beggar, for ‘tis only to weather the temple of terror.<br />you know? </p>\n<p>god? Is it not God?<br />Who am I referring to… if not God?<br />There is a God. Is there a god?<br />Maybe send a sign? A nod? </p>\n<p>But none I know accepts a fee.<br />Oh. Oh. But yes.<br />There are those still tithing you see.<br />Beggar nonetheless.<br />Wait. Who begs. Not He. Not he.<br />I lose myself.. I confess.<br />Is not he just He. Or me?<br />Oh my head! Tis’ quite the mess… </p>\n<p><strong>What’s today called?</strong></p>\n<p>It is Thursday. Is it not? A remembrance of a god. </p>\n<p>Oh! He will agree! The lightning each time thunder brought.<br />A sound that makes one flee, a god? An afterthought? </p>\n<p>Yet to venture in pleasure is to only remember to gesture, no pressure<br />And lo!<br />There’s a throne for the swagger, ‘tis better together, if only ever…<br />A show! </p>\n<p>God? Are you there? You get that a lot?<br />If you are then is it not, all but odd?<br />a god caught, well, within the plot?<br />Did I ask? I think.. that you should nod? </p>\n<p>maybe not. </p>\n<p>But yet there is decree!<br />the book! just look! unless…<br />There are those just wanting you be<br />In robes, they dress and bless<br />The Father, the Son, the three.<br />One which the hand doth impress<br />A flex? That we, just take a knee?<br />A mind, that’s doomed to guess. </p>\n<p>What… </p>\n<p><strong>What’s today called?</strong></p>\n<p></p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 11,
                        "name": "The Wordsmith's Forge",
                        "slug": "the-wordsmiths-forge"
                    }
                ],
                "opening_quote": {
                    "context": "A dedication and plea to the begotten,",
                    "text": "Write as if it’s already forgotten."
                }
            }
        },
        {
            "id": "http://172.29.142.55/github/yt-dlp-an-audio-video-downloader/",
            "url": "https://geekist.co/github/yt-dlp-an-audio-video-downloader/",
            "title": "yt-dlp: the feature-rich downloader",
            "summary": "This project is a tool that helps you extract audio from video files and convert them into standalone audio files using FFmpeg. It’s useful for situations where…",
            "image": "https://img.geekist.co/wp-content/uploads/yt-dlp-square.svg",
            "date_published": "2025-12-02T12:36:05Z",
            "date_modified": "2026-11-15T11:49:45Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/yt-dlp/yt-dlp\" title=\"yt-dlp/yt-dlp - Stars: 208.0k\">Stars208.0k</a><a href=\"https://github.com/yt-dlp/yt-dlp\" title=\"yt-dlp/yt-dlp - Forks: 18.4k\">Forks18.4k</a><a href=\"https://github.com/yt-dlp/yt-dlp\" title=\"yt-dlp/yt-dlp - Updated: 2d ago\">Updated2d ago</a>\n\n<h2><strong>What it is</strong></h2>\n<p>yt-dlp is a small app that saves online videos or their sound to your computer. Paste a link from sites like YouTube and it fetches the file for you, so you can watch or listen offline without the website. It’s fast, reliable, and works on macOS, Windows, and Linux. </p>\n<h2><strong>What’s new</strong></h2>\n<p>Recent releases (late Sep 2025) brought lots of site-compatibility fixes and some house-keeping: a few old options were retired, defaults were tidied, and security patches from August were rolled in. In short: fewer errors on big sites, cleaner options, same speed. </p>\n\n<h2><strong>What else is similar to it</strong></h2>\n<p>Other video downloaders exist, like <a href=\"https://geekist.co/github/you-get-dumb-downloader-that-scrapes-the-web/\">you-get</a> for simple one-liner downloads, or GUI apps such as 4K Video Downloader for users who prefer buttons over command lines. For live streaming playback, <a href=\"https://geekist.co/github/streamlink-pipe-video-streams-to-your-player/\">Streamlink</a> is often mentioned, though its focus is on watching rather than saving. Have a look at our <a href=\"https://geekist.co/the-5-best-downloaders-for-videos-music-images-no-browser-needed/\">5 Best Downloaders</a> roundup for a broader view of the landscape. </p>\n<h2><strong>Why it’s different</strong></h2>\n<p>yt-dlp covers the widest range of video sites and gives you easy ways to grab just the audio (for podcasts or tracks), pick quality, and merge streams behind the scenes. It’s the “one tool that usually just works” for video. </p>\n<h2><strong>How to get started</strong></h2>\n<p>Choose a tab for what you need next. Work through the steps in order, then use the checks if you get stuck.</p>\n\n\n<ol>\n<li>Choose a video you have permission to save, and copy its page address.</li>\n<li>Open Terminal on a Mac, or PowerShell on Windows. The commands below are typed there.</li>\n<li>On a Mac with Homebrew, install with <code>brew install yt-dlp</code>. On Windows, use <code>winget install --source winget --id yt-dlp.yt-dlp</code>.</li>\n</ol>\n\n\n<ol>\n<li>Type <code>yt-dlp --version</code> and press Enter. A version number means the tool is ready.</li>\n<li>In a folder where you want the file saved, run <code>yt-dlp \"VIDEO_URL\"</code>, replacing VIDEO_URL with the copied address and keeping the quotes.</li>\n<li>Wait for the download to finish, then open the file from that folder. For audio conversion or merging some formats, install FFmpeg too.</li>\n</ol>\n\n\n<ol>\n<li>If the command is not found, close and reopen the terminal, then check the installation instructions for your operating system.</li>\n<li>If the site fails, update using your original installation method; sites change and not every link is supported.</li>\n<li>A video site’s rules and the creator’s rights still apply.</li>\n</ol>\n\n\n<p><a href=\"https://github.com/yt-dlp/yt-dlp/wiki/Installation\">Official setup instructions</a></p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 21,
                        "name": "Media Tools",
                        "slug": "media-tools"
                    }
                ],
                "code_repository": "https://github.com/yt-dlp/yt-dlp",
                "programming_language": "Python",
                "license": "Unlicense"
            }
        },
        {
            "id": "http://172.29.142.55/github/you-get-dumb-downloader-that-scrapes-the-web/",
            "url": "https://geekist.co/github/you-get-dumb-downloader-that-scrapes-the-web/",
            "title": "you-get: downloader that scrapes the web",
            "summary": "you-get is a free tool that lets you download videos from popular websites like YouTube and Vimeo without any ads or restrictions. It’s designed to be simple…",
            "image": "https://img.geekist.co/wp-content/uploads/logo.jpg",
            "date_published": "2025-12-02T12:36:04Z",
            "date_modified": "2026-11-15T11:49:55Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/soimort/you-get\" title=\"soimort/you-get - Stars: 56.8k\">Stars56.8k</a><a href=\"https://github.com/soimort/you-get\" title=\"soimort/you-get - Forks: 9.7k\">Forks9.7k</a><a href=\"https://github.com/soimort/you-get\" title=\"soimort/you-get - Updated: 1y ago\">Updated1y ago</a>\n\n<h2><strong>What it is</strong></h2>\n<p><a href=\"https://github.com/soimort/you-get\"><code>you-get</code></a> is a free tool that lets you download videos from popular websites like YouTube and Vimeo without any ads or restrictions. It’s designed to be simple and easy to use, making it accessible to anyone with basic computer skills. </p>\n<h2><strong>What’s new</strong></h2>\n<p>The project continues to ship fixes that keep sites working. Updates in 2025 include repairs for YouTube captions and other site changes so downloads don’t break when websites move the goalposts. </p>\n\n<h2><strong>What else is similar to it</strong></h2>\n<p>If you like the idea but want more options and control, <a href=\"https://geekist.co/github/yt-dlp-an-audio-video-downloader/\">yt-dlp</a>, offers deeper site support and advanced features. Desktop managers like JDownloader provide a graphical interface for batch jobs, while <a href=\"https://geekist.co/github/spotdl-download-spotify-playlists/\">spotDL</a> focuses purely on music. Each tool fills a niche, and you can explore them side by side in our <a href=\"https://geekist.co/the-5-best-downloaders-for-videos-music-images-no-browser-needed/\">5 Best Downloaders</a> guide. </p>\n<h2><strong>Why it’s different</strong></h2>\n<p><code>you-get</code> aims for “small and straightforward.” If you just want a quick download without lots of switches, it delivers.</p>\n<h2><strong>How to get started</strong></h2>\n<p>Choose a tab for what you need next. Work through the steps in order, then use the checks if you get stuck.</p>\n\n\n<ol>\n<li>Install Python, then open Terminal or PowerShell. On Windows, add Python to PATH when the installer offers it.</li>\n<li>Install the tool with <code>python -m pip install you-get</code>. On some Macs and Linux systems use <code>python3</code>.</li>\n<li>Copy the address of a supported video you have permission to save.</li>\n</ol>\n\n\n<ol>\n<li>Type <code>you-get --version</code> to check the installation.</li>\n<li>In your chosen download folder, run <code>you-get \"VIDEO_URL\"</code>, replacing the placeholder with the copied address.</li>\n<li>Wait for the command to finish and open the downloaded file in that folder.</li>\n</ol>\n\n\n<ol>\n<li>If the command is not recognised, reopen the terminal and check Python’s scripts folder is on PATH.</li>\n<li>Not every website works indefinitely; consult the project’s supported-sites list if the download fails.</li>\n<li>Some downloads need FFmpeg to combine media streams.</li>\n</ol>\n\n\n<p><a href=\"https://github.com/soimort/you-get\">Official setup instructions</a></p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 21,
                        "name": "Media Tools",
                        "slug": "media-tools"
                    }
                ],
                "code_repository": "https://github.com/soimort/you-get",
                "programming_language": "Python"
            }
        },
        {
            "id": "http://172.29.142.55/github/webpack-build-tool-and-module-bundler/",
            "url": "https://geekist.co/github/webpack-build-tool-and-module-bundler/",
            "title": "webpack: build tool and module bundler",
            "summary": "Webpack is a tool that helps make websites load faster and run more smoothly by bundling together multiple JavaScript files into smaller ones. This process…",
            "image": "https://img.geekist.co/wp-content/uploads/2026/08/webpack-icon-square-big.svg",
            "date_published": "2025-12-02T12:36:02Z",
            "date_modified": "2026-02-04T20:21:36Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/webpack/webpack\" title=\"webpack/webpack - Stars: 66.0k\">Stars66.0k</a><a href=\"https://github.com/webpack/webpack\" title=\"webpack/webpack - Forks: 9.6k\">Forks9.6k</a><a href=\"https://github.com/webpack/webpack\" title=\"webpack/webpack - Updated: 1d ago\">Updated1d ago</a>\n\n<h2><strong>What it is</strong></h2>\n<p>Webpack is a build tool and module bundler that takes all the disparate assets of a modern web application like JavaScript, CSS, images, fonts, even WASM and turns them into an optimised bundle that browsers can load efficiently. At its core, it builds a dependency graph from your entry points, understands how modules relate to each other, and compiles them into chunks that are served on demand. Features like code splitting, loaders, and plugins give you a high-granularity control over how assets are transformed, compressed, and delivered. It remains one of the most mature ecosystems for shaping how large front-end projects are structured and shipped. </p>\n<h2><strong>What’s new</strong></h2>\n<p>Webpack is still very much alive: the latest release,  continues to refine how it handles configuration, environments, and assets. Recent updates add a built-in <code>DotenvPlugin</code> plus a top-level dotenv option, so you can load environment variables without wiring extra plugins by hand, and introduce a <code>WebpackManifestPlugin</code> to generate manifest files directly from core. </p>\n<p>The same release tightens Webpack’s relationship with modern JavaScript runtimes. There is now first-class support for <code>import.meta.env</code>, <code>import.meta.dirname</code>, <code>import.meta.filename</code>, and <code>import.defer()</code>, along with handling of <code>import.meta.main</code> and better behaviour for <code>__dirname/__filename</code> in “universal” targets. This makes it easier to write code that feels closer to native ESM while still running through Webpack’s bundling pipeline. </p>\n<p>On the CSS side, Webpack’s CSS tooling has gained an <code>exportType</code> option (with link, text, and css-style-sheet modes) and support for composes in CSS modules, plus a series of fixes to reduce runtime overhead and clean up edge-case bugs. Recent 5.10x releases also add features like static analysis for dynamic imports, new with <code>{ type: \"bytes\" | \"text\" }</code> import forms, and an <code>extractSourceMap</code> option so you can pull source maps without extra loaders.  The net effect is: Webpack 5 in late 2025 is a stable, actively maintained line, gradually modernising around ESM, richer imports, and more predictable CSS behaviour rather than introducing a “Webpack 6.”</p>\n\n<h2><strong>What else is similar to it</strong></h2>\n<p>Several tools compete in the same problem space of bundling and build optimisation. Vite offers an ESM-native dev server with lightning-fast HMR, leaning on Rollup for production builds. esbuild focuses on extreme speed through Go-based compilation and minimal configuration. Parcel provides a “zero-config” experience with automatic transforms and parallel processing. Rollup itself still excels for libraries due to its cleaner output and focus on ESM bundles. Each alternative trades off Webpack’s depth of configurability for speed, simplicity, or convention-driven defaults. </p>\n<h2><strong>Why it’s different</strong></h2>\n<p>Webpack’s distinguishing trait is its extensibility. The loader and plugin systems allow you to customise almost any part of the build graph, from how files are parsed to how chunks are generated to how the final assets land in your deployment. This flexibility makes it especially suited to complex, enterprise-scale applications with unusual requirements or mixed asset types. While other tools prioritise speed, Webpack prioritises power: if there’s a transformation, optimisation, or workflow you can imagine, chances are someone has already built a plugin or you can write one yourself. It also continues to have the broadest compatibility story across legacy codebases, making it a reliable backbone for very large applications that can’t immediately migrate to newer tools. </p>\n<h2><strong>How to get started</strong></h2>\n<p>Choose a tab for what you need next. Work through the steps in order, then use the checks if you get stuck.</p>\n\n\n<ol>\n<li>Install Node.js and open Terminal or PowerShell. npm comes with Node.</li>\n<li>Create an empty practice folder and open the terminal in it; webpack is a developer tool that packages a project’s files.</li>\n<li>Run <code>npm init -y</code> to create a basic project record.</li>\n</ol>\n\n\n<ol>\n<li>Install the tools with <code>npm install --save-dev webpack webpack-cli</code>.</li>\n<li>Create a folder named <code>src</code> and a file inside it called <code>index.js</code>; put <code>console.log(\"Hello, webpack!\");</code> in that file.</li>\n<li>Run <code>npx webpack</code>. A generated <code>dist/main.js</code> file is the first bundled output.</li>\n</ol>\n\n\n<ol>\n<li>If npm is missing, reinstall or update Node.js and reopen the terminal.</li>\n<li>If webpack cannot find an entry file, check the path is exactly <code>src/index.js</code>.</li>\n<li>The official guide shows how to add an HTML page and a configuration file after this first bundle works.</li>\n</ol>\n\n\n<p><a href=\"https://webpack.js.org/guides/getting-started/\">Official setup instructions</a></p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 19,
                        "name": "Build Tool",
                        "slug": "build-tool"
                    }
                ],
                "code_repository": "https://github.com/webpack/webpack",
                "programming_language": "JavaScript",
                "license": "MIT"
            }
        },
        {
            "id": "http://172.29.142.55/github/streamlink-pipe-video-streams-to-your-player/",
            "url": "https://geekist.co/github/streamlink-pipe-video-streams-to-your-player/",
            "title": "streamlink: video streams ➞ your player",
            "summary": "Streamlink is a CLI utility which pipes video streams from various services directly into a video player you use.",
            "image": "https://img.geekist.co/wp-content/uploads/icon.svg",
            "date_published": "2025-12-02T12:36:00Z",
            "date_modified": "2026-11-15T11:50:01Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/streamlink/streamlink\" title=\"streamlink/streamlink - Stars: 11.9k\">Stars11.9k</a><a href=\"https://github.com/streamlink/streamlink\" title=\"streamlink/streamlink - Forks: 1.2k\">Forks1.2k</a><a href=\"https://github.com/streamlink/streamlink\" title=\"streamlink/streamlink - Updated: 2d ago\">Updated2d ago</a>\n\n<h2><strong>What it is</strong></h2>\n<p><a href=\"https://github.com/streamlink/streamlink\"><code>streamlink</code></a> is a CLI utility which pipes video streams from various services directly into a video player you use. </p>\n<h2><strong>What’s new</strong></h2>\n<p>v7.6.0’s release (Sept 2025) brings fresh site-plugin updates, fixes, and small deprecations, part of its steady cadence to keep major services (Twitch, YouTube, and more) working reliably. </p>\n\n<h2><strong>What else is similar to it</strong></h2>\n<p>While Streamlink is about watching live streams in your player, <a href=\"https://geekist.co/github/yt-dlp-an-audio-video-downloader/\">yt-dlp</a> and <a href=\"https://geekist.co/github/you-get-dumb-downloader-that-scrapes-the-web/\">you-get</a> are designed to save videos instead. VLC can open some network streams directly, and OBS Studio is better suited for capturing rather than viewing. To see how Streamlink fits among other download and playback tools, check our <a href=\"https://geekist.co/the-5-best-downloaders-for-videos-music-images-no-browser-needed/\">5 Best Downloaders</a>. </p>\n<h2><strong>Why it’s different</strong></h2>\n<p>It’s purpose-built for streaming: open the stream in a real media player with one command and skip the clutter of the site. </p>\n<h2><strong>How to get started</strong></h2>\n<p>Choose a tab for what you need next. Work through the steps in order, then use the checks if you get stuck.</p>\n\n\n<ol>\n<li>Install a media player such as VLC first; Streamlink sends the stream to a player instead of opening it in your browser.</li>\n<li>On a Mac with Homebrew run <code>brew install streamlink</code>. Other systems can follow the official installer instructions.</li>\n<li>Copy the page address of a supported live stream.</li>\n</ol>\n\n\n<ol>\n<li>Open Terminal or PowerShell and run <code>streamlink --version</code>.</li>\n<li>Run <code>streamlink \"STREAM_URL\" best</code>, replacing STREAM_URL with the copied address.</li>\n<li>Your player should open and start the stream. <code>best</code> asks Streamlink for the best available quality.</li>\n</ol>\n\n\n<ol>\n<li>If no player opens, check that VLC is installed and try selecting it in Streamlink’s player settings.</li>\n<li>If a stream fails, check that the source is supported and update Streamlink; providers sometimes change their sites.</li>\n<li>Try a lower quality if the connection cannot keep up.</li>\n</ol>\n\n\n<p><a href=\"https://streamlink.github.io/install.html\">Official setup instructions</a></p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 21,
                        "name": "Media Tools",
                        "slug": "media-tools"
                    }
                ],
                "code_repository": "https://github.com/streamlink/streamlink",
                "programming_language": "Python",
                "license": "BSD-2-Clause"
            }
        },
        {
            "id": "http://172.29.142.55/github/spotdl-download-spotify-playlists/",
            "url": "https://geekist.co/github/spotdl-download-spotify-playlists/",
            "title": "spotDL: download spotify playlists",
            "summary": "spotDL is a tool that helps you download your favorite Spotify playlists and songs from YouTube, along with their album art and metadata, so you can listen to..",
            "image": "https://img.geekist.co/wp-content/uploads/spotdl-logo.png",
            "date_published": "2025-12-02T12:35:59Z",
            "date_modified": "2026-11-15T11:50:09Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/spotDL/spotify-downloader\" title=\"spotDL/spotify-downloader - Stars: 26.8k\">Stars26.8k</a><a href=\"https://github.com/spotDL/spotify-downloader\" title=\"spotDL/spotify-downloader - Forks: 2.3k\">Forks2.3k</a><a href=\"https://github.com/spotDL/spotify-downloader\" title=\"spotDL/spotify-downloader - Updated: 22d ago\">Updated22d ago</a>\n\n<h2><strong>What it is</strong></h2>\n<p><a href=\"https://github.com/spotDL/spotify-downloader\"><code>spotDL</code></a> is a tool that helps you download your favorite Spotify playlists and songs from YouTube, along with their album art and metadata, so you can listen to them offline. Music lovers get access to their playlists without needing an internet connection, making it easier to enjoy music on-the-go or in areas with poor connectivity. By downloading the highest possible bitrate of each song, spotDL ensures that your music stays high-quality, even when stored locally. </p>\n<h2><strong>What’s new</strong></h2>\n<p>Recent v4 updates focused on stability and modern Python support, plus a handy sync mode that keeps a local folder in step with a playlist, adding new tracks and removing ones you’ve taken out, so your offline copy stays fresh. </p>\n\n<h2><strong>What else is similar to it</strong></h2>\n<p>Music lovers sometimes turn to <a href=\"https://geekist.co/github/yt-dlp-an-audio-video-downloader/\">yt-dlp</a>, for quick audio grabs, though it’s not built around Spotify. <a href=\"https://deemix.org/\">Deemix</a> (for Deezer) is another community favorite. They all aim to turn streaming music into personal collections. <br />For a comparison across categories – including images, streams, and general videos – see our <a href=\"https://geekist.co/the-5-best-downloaders-for-videos-music-images-no-browser-needed/\">5 Best Downloaders</a></p>\n<h2><strong>Why it’s different</strong></h2>\n<p>spotDL is built around Spotify first: paste a Spotify link and you get tagged, named, cover-art-ready tracks. The sync workflow makes ongoing playlist mirroring painless. </p>\n<h2><strong>How to get started</strong></h2>\n<p>Choose a tab for what you need next. Work through the steps in order, then use the checks if you get stuck.</p>\n\n\n<ol>\n<li>Install Python and open Terminal or PowerShell; on Windows choose “Add Python to PATH” during setup.</li>\n<li>Run <code>python -m pip install spotdl</code>. Some Macs and Linux systems use <code>python3</code> instead.</li>\n<li>Install FFmpeg for audio conversion: <code>spotdl --download-ffmpeg</code> installs a copy for spotDL.</li>\n</ol>\n\n\n<ol>\n<li>Open the folder where you want the files saved.</li>\n<li>Copy a Spotify track or playlist link and run <code>spotdl download \"SPOTIFY_URL\"</code>, replacing the placeholder.</li>\n<li>Check the terminal output and open the downloaded files in that folder. spotDL matches Spotify metadata to audio from other sources.</li>\n</ol>\n\n\n<ol>\n<li>If spotDL is not found, reopen the terminal and check Python’s scripts folder is on PATH.</li>\n<li>A missing or incorrect match can occur; check the output before relying on it. The project also recommends Deno for some YouTube downloads.</li>\n<li>Only download material you have permission to use.</li>\n</ol>\n\n\n<p><a href=\"https://github.com/spotDL/spotify-downloader/blob/master/docs/installation.md\">Official setup instructions</a></p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 21,
                        "name": "Media Tools",
                        "slug": "media-tools"
                    }
                ],
                "code_repository": "https://github.com/spotDL/spotify-downloader",
                "programming_language": "Python",
                "license": "MIT"
            }
        },
        {
            "id": "http://172.29.142.55/github/ollama-run-open-source-models-locally/",
            "url": "https://geekist.co/github/ollama-run-open-source-models-locally/",
            "title": "ollama: run open source models locally",
            "summary": "Ollama is an offline-first platform for running AI models locally or (recently) connected to the cloud. It prioritizes privacy and control by keeping data on…",
            "image": "https://img.geekist.co/wp-content/uploads/ollama.png",
            "date_published": "2025-12-02T12:35:57Z",
            "date_modified": "2026-02-04T20:21:39Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/ollama/ollama\" title=\"ollama/ollama - Stars: 187.1k\">Stars187.1k</a><a href=\"https://github.com/ollama/ollama\" title=\"ollama/ollama - Forks: 19.1k\">Forks19.1k</a><a href=\"https://github.com/ollama/ollama\" title=\"ollama/ollama - Updated: 3d ago\">Updated3d ago</a><a href=\"https://github.com/ollama/ollama\" title=\"ollama/ollama - Language: Go\">LanguageGo</a><a href=\"https://github.com/ollama/ollama\" title=\"ollama/ollama - License: MIT\">LicenseMIT</a>\n\n<h2><strong><strong>What it is</strong></strong></h2>\n<p><a href=\"https://github.com/ollama/ollama\"><code>ollama</code></a> is a project that makes artificial intelligence models easy to run on your own machine. It began in 2023 as a command-line tool aimed at developers who wanted to try models such as Llama without dealing with servers or complex setups. Over time it has matured into something broader: an API that imitates the style of OpenAI’s, a growing library of models you can pull down in seconds, and recently, a desktop app with a clean interface. </p>\n<p>What started as a niche tool for technically minded people has become one of the friendliest ways to experiment with AI locally. </p>\n<p><em>Visit the <a href=\"https://ollama.com/\">official site</a>.</em></p>\n\n<h2><strong>What’s new</strong></h2>\n<p>Ollama has stepped beyond the terminal with a clean desktop app for macOS and Windows, making it easy to install, run, and switch between models with a few clicks.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/ollama-desktop-app.avif\" alt=\"Ollama desktop app showing a dark window with the llama logo centred and a message input field at the bottom\" title=\"Ollama desktop app – chat window with model selection\" width=\"1138\" height=\"820\" /></figure>\n<p>Recent adds some practicality: you can now <a href=\"https://ollama.com/blog/new-app\">drag and drop PDFs, text, or code</a> into a chat, feed in images with <a href=\"https://ollama.com/blog/multimodal-models\">multimodal models like Gemma 3</a>, and even adjust the <a href=\"https://ollama.com/blog/new-app\">context window size</a> to handle larger documents. Performance gains continue quietly in the background (overlapping CPU/GPU work, faster flash-attention, and snappier chat switching) so things just feel quicker. </p>\n<p>The model library has grown too, with additions such as <em><a href=\"https://developers.googleblog.com/en/introducing-embeddinggemma/\">EmbeddingGemma</a></em> for semantic tasks, alongside the familiar Llama, Mistral, and Gemma families. </p>\n<p>Ollama is also experimenting with <a href=\"https://ollama.com/blog/turbo\">Turbo</a>, an early preview of their upcoming cloud inference service, currently free to try with GPT-OSS models. </p>\n<h2><strong>What else is similar to it</strong></h2>\n<p>There are other tools in this space. LM Studio offers a desktop app that looks and feels quite similar, with an easy way to download and try models. GPT4All is another approachable option, positioned as a privacy-first chatbot that works offline on ordinary laptops. At the other end of the spectrum is llama.cpp, a high-performance engine in C and C++ that underpins many of these friendlier interfaces, though it appeals more to tinkerers than casual users. </p>\n<h2><strong>Why it’s different</strong></h2>\n<p>Ollama’s appeal lies in its simplicity. You can be chatting to a model within minutes of downloading, and you don’t need a cloud account or an internet connection once the model is installed. Its app is clean, its command-line is clear, and its local API means you can point other software at it as though you were using a hosted service. The licence is MIT, which makes it open, adaptable and free to use. What makes this especially compelling is that Ollama has built up an ecosystem of integrations, so that frameworks like LangChain or Spring AI can work with it immediately. </p>\n<h2><strong>How to get started</strong></h2>\n<p>Choose a tab for what you need next. Work through the steps in order, then use the checks if you get stuck.</p>\n\n\n<ol>\n<li>Download Ollama for your operating system from its official website and open the app after installation.</li>\n<li>Choose a small local model first: models need storage and memory, and the first download can take a while.</li>\n<li>Open Terminal or PowerShell if you want to use the command line.</li>\n</ol>\n\n\n<ol>\n<li>Run <code>ollama run llama3.2</code> and wait for the model to download.</li>\n<li>At the prompt, type a question such as “Explain photosynthesis in two sentences.”</li>\n<li>A reply in the terminal means the model is running. Type <code>/bye</code> to leave the conversation.</li>\n</ol>\n\n\n<ol>\n<li>If the command is not found, restart the terminal after installing Ollama.</li>\n<li>If your machine slows down or runs out of memory, stop the model and choose a smaller one; model sizes and requirements vary.</li>\n<li>Local models and cloud-hosted models have different privacy and billing implications; check which one you selected.</li>\n</ol>\n\n\n<p><a href=\"https://docs.ollama.com/quickstart\">Official setup instructions</a></p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 18,
                        "name": "Local Inference",
                        "slug": "local-inference"
                    }
                ],
                "code_repository": "https://github.com/ollama/ollama",
                "programming_language": "Go",
                "license": "MIT"
            }
        },
        {
            "id": "http://172.29.142.55/github/next-js-a-full-stack-react-framework/",
            "url": "https://geekist.co/github/next-js-a-full-stack-react-framework/",
            "title": "next.js: a full-stack React framework",
            "summary": "Next.js is a tool that helps developers build fast and efficient web applications using the popular React framework. It streamlines the process of creating full…",
            "image": "https://img.geekist.co/wp-content/uploads/2026/08/next-js-dark.svg",
            "date_published": "2025-12-02T12:35:56Z",
            "date_modified": "2026-11-15T11:50:16Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/vercel/next.js\" title=\"vercel/next.js - Stars: 143.5k\">Stars143.5k</a><a href=\"https://github.com/vercel/next.js\" title=\"vercel/next.js - Forks: 32.8k\">Forks32.8k</a><a href=\"https://github.com/vercel/next.js\" title=\"vercel/next.js - Updated: 2d ago\">Updated2d ago</a>\n\n<h2><strong>What it is</strong></h2>\n<p>Next.js is a full-stack React framework that gives you routing, data-fetching, rendering, and build tooling in one opinionated package. Instead of wiring <a href=\"https://geekist.co/github/webpack-build-tool-and-module-bundler/\">Webpack</a>/Vite, routers, API layers and deployment glue yourself, you get a single abstraction that can do server-side rendering, static generation, incremental static regeneration, and client-side hydration from the same codebase. </p>\n<p>It leans on modern React features (Server Components, Suspense, Server Actions) and Rust-based tooling under the hood to keep builds fast while still supporting very large apps used by big companies in production. </p>\n<h2><strong>What’s new</strong></h2>\n<p>As of late 2025, the headline is Next.js 16 and the tail end of the 15.x line. Next 16 tightens the Turbopack story: configs move to a new turbopack block in next.config.js, and the framework nudges you away from older build/middleware conventions. The next lint command is deprecated in favour of using the ESLint CLI directly, and the older middleware pattern gives way to a proxy-based approach, with codemods to migrate existing apps. A number of previously experimental APIs lose their unstable_ prefixes as they stabilise. </p>\n<p>On the 15.x side, the most recent notable release, Next.js 15.5, brings Turbopack production builds (next build –turbopack) into beta, stabilises the Node.js runtime for middleware, and adds stronger TypeScript support around routes (typed routes, export validation, helpers). It also starts surfacing deprecation warnings in preparation for the 16 upgrade path and phases out next lint. </p>\n<p>Earlier 15.x releases introduced React 19 support, improvements to hydration error debugging, new caching semantics (uncached by default for fetch, GET Route Handlers and the client router cache), and deeper Turbopack integration for both dev and build workflows. </p>\n\n<h2><strong>What else is similar to it</strong></h2>\n<p>Next.js sits in the “full-stack React (or frontend) framework” space alongside a few close neighbours. Remix offers nested routing and a “web fundamentals first” approach with strong emphasis on HTTP semantics and progressive enhancement. </p>\n<p>Gatsby historically focused on content sites and static generation with a strong plugin ecosystem, though its role has shifted more towards maintaining existing sites than leading the cutting edge. RedwoodJS targets SaaS and startups with an opinionated full-stack story around React, GraphQL and Prisma. </p>\n<p>Outside the React world, Nuxt (Vue), SvelteKit (Svelte) and <a href=\"https://geekist.co/github/astro-a-web-framework-built-for-content-driven-sites/\">Astro</a> (content-first, multi-framework) solve similar “build full experiences, not just components” problems with different trade-offs around SSR, static output, and how much of the stack they own. </p>\n<h2><strong>Why it’s different</strong></h2>\n<p>Next.js stands out because of how much of the stack it unifies while still feeling like React. The App Router plus React Server Components gives you streaming, granular data-fetching and partial rendering without manually juggling APIs and client caches. Server Actions and Route Handlers let you colocate server logic with UI instead of scattering it across separate services or ad-hoc endpoints. </p>\n<p>Turbopack and the surrounding Rust-based tooling aim to preserve performance even as projects grow large, and Vercel’s hosting platform doubles down on this integration with zero-config deployment paths for most apps. </p>\n<p>Compared to more minimal meta-frameworks or bare bundlers, Next.js is intentionally “batteries included”: routing, rendering modes, asset optimisation, edge/middleware and deployment alignment are all designed to work together, which is why it’s become the default choice for many React teams building serious products. </p>\n<h2><strong>How to get started</strong></h2>\n<p>Choose a tab for what you need next. Work through the steps in order, then use the checks if you get stuck.</p>\n\n\n<ol>\n<li>Install a supported Node.js version from the official Node.js website; npm is included.</li>\n<li>Open Terminal or PowerShell and choose where to create a new project.</li>\n<li>Next.js is for building web applications, so the first result is a local example rather than an installed desktop app.</li>\n</ol>\n\n\n<ol>\n<li>Run <code>npx create-next-app@latest</code>. Choose a project name and accept the recommended options if you are unsure.</li>\n<li>Move into the new folder with <code>cd YOUR_PROJECT</code> and run <code>npm run dev</code>.</li>\n<li>Open the local address printed in the terminal; the starter page confirms the app is running.</li>\n</ol>\n\n\n<ol>\n<li>If the setup rejects Node.js, check the version required by the current Next.js installation guide and update Node.</li>\n<li>If the usual port is occupied, use the address printed by the development server.</li>\n<li>Press Ctrl+C to stop the local server when you are finished.</li>\n</ol>\n\n\n<p><a href=\"https://nextjs.org/docs/app/getting-started/installation\">Official setup instructions</a></p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 20,
                        "name": "Framework",
                        "slug": "framework"
                    }
                ],
                "code_repository": "https://github.com/vercel/next.js",
                "programming_language": "JavaScript",
                "license": "MIT"
            }
        },
        {
            "id": "http://172.29.142.55/github/langflow-ai-build-deploy-ai-agents/",
            "url": "https://geekist.co/github/langflow-ai-build-deploy-ai-agents/",
            "title": "langflow-ai: build & deploy AI-agents",
            "summary": "Langflow is a tool that lets you design AI applications by drawing them, instead of writing long streams of configuration or glue code. It started as a visual…",
            "image": "https://img.geekist.co/wp-content/uploads/2026/08/langflow-logo-color.svg",
            "date_published": "2025-12-02T12:35:54Z",
            "date_modified": "2026-02-04T20:21:40Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/langflow-ai/langflow\" title=\"langflow-ai/langflow - Stars: 156.7k\">Stars156.7k</a><a href=\"https://github.com/langflow-ai/langflow\" title=\"langflow-ai/langflow - Forks: 10.4k\">Forks10.4k</a><a href=\"https://github.com/langflow-ai/langflow\" title=\"langflow-ai/langflow - Updated: 3d ago\">Updated3d ago</a><a href=\"https://github.com/langflow-ai/langflow\" title=\"langflow-ai/langflow - Language: Python\">LanguagePython</a><a href=\"https://github.com/langflow-ai/langflow\" title=\"langflow-ai/langflow - License: MIT\">LicenseMIT</a>\n<h2><strong>What it is</strong></h2>\n<p>Langflow is a tool that lets you design AI applications by drawing them, instead of writing long streams of configuration or glue code. It started as a visual editor built on LangChain that helps people wire up language models, agents and data sources. Over time it has expanded so flows (the diagrams you draw) can become production tools, with built-in API or MCP servers. You can still use it locally, or host it, and it supports many models and vector databases. </p>\n<h2><strong>What’s new</strong></h2>\n<p>The latest <a href=\"https://docs.langflow.org/release-notes\">Langflow updates</a> focus squarely on usability: flexible theming that adapts across light and dark modes, refreshed component panels, and bundles like <em>JigsawStack</em> that tie together common operations. </p>\n<p>Data handling has become more structured, with updated DataFrame tools including a new “contains” filter and broader support in the Structured Output component. </p>\n<p>Switching between model providers is more seamless, and the UI continues to polish with small but welcome fixes to layout and export flows. </p>\n<p>It’s not just cosmetic, the framework is steadily making it easier to customize, wire up data, and build flows that look as good as they run. </p>\n<h2><strong>What else is similar to it</strong></h2>\n<p>If you look around, there are a few tools trying to solve similar problems. Flowise gives you a drag-and-drop builder for workflow and agent setups. Haystack Studio is more tuned to retrieval/use of documents (RAG) but offers visual tooling too. LangGraph Studio (from the LangChain ecosystem) focuses on graph-based agents and tracing. They all let you prototype fast, but each makes trade-offs in how visual vs how flexible vs how easy-to-deploy they are. </p>\n<h2><strong>Why it’s different</strong></h2>\n<p>Langflow stands out because the visual flows aren’t just demos: they can immediately become deployable APIs or MCP servers. You don’t draw something and then copy-past tons of code later. The architecture supports many model providers, vector stores, tools, and the “bundles” (groups of related components) mean less reinventing. Also, the licensing is open source (MIT), so organisations can adopt it without worrying about license costs. For someone non-technical, the promise is: sketch your idea, run it, share it, all without getting lost in backend complexity. </p>\n<h2><strong>How to get started</strong></h2>\n<p>Choose a tab for what you need next. Work through the steps in order, then use the checks if you get stuck.</p>\n\n\n<ol>\n<li>For the simplest route on Windows or macOS, download Langflow Desktop from the official site; the download page may ask for contact details.</li>\n<li>Install the app and open it. The first start may set up dependencies and take a few minutes.</li>\n<li>Alternatively, developers can install the Python package in an isolated environment; the official guide lists the prerequisites.</li>\n</ol>\n\n\n<ol>\n<li>In Langflow, create a new flow from the starter options.</li>\n<li>Add or configure a model component with the provider credentials it asks for, then connect it to the input and output components.</li>\n<li>Run a short test message in the playground. A response means the flow is connected.</li>\n</ol>\n\n\n<ol>\n<li>If the app cannot install its dependencies, check free disk space and follow its on-screen troubleshooting message.</li>\n<li>If a model fails, check the selected provider, credentials and any provider charges.</li>\n<li>Keep credentials out of screenshots and shared flow exports.</li>\n</ol>\n\n\n<p><a href=\"https://docs.langflow.org/get-started-installation\">Official setup instructions</a></p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 17,
                        "name": "Agent Runtime",
                        "slug": "agent-runtime"
                    }
                ],
                "code_repository": "https://github.com/langflow-ai/langflow",
                "programming_language": "Python",
                "license": "MIT"
            }
        },
        {
            "id": "http://172.29.142.55/github/gallery-dl-download-image-galleries-collections/",
            "url": "https://geekist.co/github/gallery-dl-download-image-galleries-collections/",
            "title": "gallery-dl: download image galleries",
            "summary": "gallery-dl is a free tool that helps you download image galleries from websites like Pixiv, Danbooru, and Mangadex with just a few commands. It’s available…",
            "image": "https://img.geekist.co/wp-content/uploads/png-transparent-github-repository-commit-version-control-github-angle-rectangle-logo-thumbnail-1.png",
            "date_published": "2025-12-02T12:35:52Z",
            "date_modified": "2026-02-04T20:21:41Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/mikf/gallery-dl\" title=\"mikf/gallery-dl - Stars: 20.5k\">Stars20.5k</a><a href=\"https://github.com/mikf/gallery-dl\" title=\"mikf/gallery-dl - Forks: 1.5k\">Forks1.5k</a><a href=\"https://github.com/mikf/gallery-dl\" title=\"mikf/gallery-dl - Updated: 3d ago\">Updated3d ago</a>\n\n<h2><strong>What it is</strong></h2>\n<p><a href=\"https://github.com/mikf/gallery-dl\"><code>gallery-dl</code></a> is a free tool that helps you download image galleries from websites like Pixiv, Danbooru, and Mangadex with just a few commands. It’s available on Windows, Linux, and macOS – easy to use regardless of your operating system. </p>\n<h2><strong>What’s new</strong></h2>\n<p>v1.30.8 (late Sep 2025) adds and updates site support and raises the minimum Python version, keeping downloads working as sites evolve. </p>\n\n<h2><strong>What else is similar to it</strong></h2>\n<p>Image-focused downloaders like RipMe or Bulk Image Downloader serve similar roles, and browser extensions such as DownThemAll! offer lighter-weight bulk saving, but none match gallery-dl’s breadth for galleries and collections. You’ll also find it featured in our <a href=\"https://geekist.co/the-5-best-downloaders-for-videos-music-images-no-browser-needed/\">5 Best Downloaders</a> list, which compares tools across music, video, and images. </p>\n<h2><strong>Why it’s different</strong></h2>\n<p>It’s tuned for bulk images: handles albums, artist pages, and forums with neat folder/file naming so large sets stay organized. </p>\n<h2><strong>How to get started</strong></h2>\n<p>Choose a tab for what you need next. Work through the steps in order, then use the checks if you get stuck.</p>\n\n\n<ol>\n<li>Choose an image gallery you are allowed to save and copy its address.</li>\n<li>Install Python if it is not already on your computer; on Windows, select the option to add Python to PATH.</li>\n<li>Open Terminal or PowerShell and install with <code>python -m pip install -U gallery-dl</code>. On some Macs and Linux systems use <code>python3</code> instead of <code>python</code>.</li>\n</ol>\n\n\n<ol>\n<li>Type <code>gallery-dl --version</code> to confirm the program is available.</li>\n<li>Move into a folder for your downloads, then run <code>gallery-dl \"GALLERY_URL\"</code>, replacing GALLERY_URL with the gallery address.</li>\n<li>Open the new download folder and check that the images are present.</li>\n</ol>\n\n\n<ol>\n<li>If the command is not found, reopen your terminal and check that Python’s scripts folder is on your PATH.</li>\n<li>A site may require a login or may no longer be supported; consult the project’s supported-site list and help before adding account details.</li>\n<li>Use only material you have permission to download.</li>\n</ol>\n\n\n<p><a href=\"https://github.com/mikf/gallery-dl\">Official setup instructions</a></p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 21,
                        "name": "Media Tools",
                        "slug": "media-tools"
                    }
                ],
                "code_repository": "https://github.com/mikf/gallery-dl",
                "programming_language": "Python",
                "license": "GPL-2.0"
            }
        },
        {
            "id": "http://172.29.142.55/github/astro-a-web-framework-built-for-content-driven-sites/",
            "url": "https://geekist.co/github/astro-a-web-framework-built-for-content-driven-sites/",
            "title": "astro: a web framework built for content-driven sites",
            "summary": "Astro is a website builder that helps developers create fast and efficient websites by splitting code into smaller chunks and caching frequently-used parts.",
            "image": "https://img.geekist.co/wp-content/uploads/44914786.png",
            "date_published": "2025-12-02T12:35:51Z",
            "date_modified": "2026-11-15T11:50:23Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "content_html": "<a href=\"https://github.com/withastro/astro\" title=\"withastro/astro - Stars: 64.0k\">Stars64.0k</a><a href=\"https://github.com/withastro/astro\" title=\"withastro/astro - Forks: 3.9k\">Forks3.9k</a><a href=\"https://github.com/withastro/astro\" title=\"withastro/astro - Updated: 3d ago\">Updated3d ago</a>\n\n<h2><strong>What it is</strong></h2>\n<p>Astro is a web framework built for content-driven sites: blogs, marketing pages, docs, and lightweight e-commerce. Instead of shipping a big JavaScript bundle by default, Astro renders pages to HTML and only hydrates the interactive “islands” that need JavaScript in the browser. </p>\n<p>You write components in React, Svelte, Vue, Solid, or plain HTML/MDX, and Astro stitches them together into fast, static or hybrid pages. </p>\n<p>With Astro 5, the framework leans into being a content hub: you can pull content from local files, headless CMSes, or APIs and treat it all as a single, type-safe content layer that feeds the site. </p>\n<h2><strong>What’s new</strong></h2>\n<p>Astro is currently in the 5.x line, and recent releases have focused on making large, content-heavy projects easier to manage and debug rather than introducing breaking changes. </p>\n<p>Astro 5.0 introduced the Content Layer, a unified way to load content from any source (files, CMS, APIs) into type-safe collections, plus Server Islands that combine cached static pages with dynamic, personalised regions. It also simplified prerendering and upgraded the toolchain to Vite 6 with better type-safe environment variables. </p>\n<p>The more recent Astro 5.13 release in August 2025 continues polishing the developer experience: experimental improvements to how environment variables are handled, tighter integration with Chrome DevTools workspaces (so you can edit Astro files directly from DevTools), and a stream of smaller quality-of-life updates. </p>\n<p>The ongoing 5.13.x patches through September 2025 refine behaviour around things like the image endpoint (better detection of remote paths) and component typings, while keeping upgrades low-friction for existing 5.x sites. </p>\n<h2><strong>What else is similar to it</strong></h2>\n<p>Astro lives in the same general space as frameworks like Next.js, SvelteKit, Nuxt, Gatsby, Hugo and Eleventy. They all let you build modern sites with some mix of static generation, server rendering and client interactivity. </p>\n<p><a href=\"https://geekist.co/github/next-js-a-full-stack-react-framework/\">Next.js</a> and SvelteKit lean more towards full web applications with rich routing and server logic. Hugo and Eleventy are closer to traditional static site generators with templating and content pipelines. Gatsby historically focused on GraphQL-centric content sourcing. </p>\n<p>They all help you ship content and pages, but differ in how much JavaScript they expect you to run in the browser and how “app-like” they want your site to be. </p>\n<h2><strong>Why it’s different</strong></h2>\n<p>Astro’s main bet is that most content sites don’t need a full SPA runtime. It renders HTML first, hydrates only the interactive components you opt into, and lets you mix multiple component frameworks in the same project. </p>\n<p>It makes Astro feel “content-first”: you organise collections, loaders and pages, and the framework handles how to render and ship it efficiently rather than pushing you into a full client-side app model. </p>\n<h2><strong>How to get started</strong></h2>\n<p>Choose a tab for what you need next. Work through the steps in order, then use the checks if you get stuck.</p>\n\n\n<ol>\n<li>Install a supported Node.js version from the official Node.js website; it includes npm.</li>\n<li>Open Terminal or PowerShell and choose a folder for a new website.</li>\n<li>This is a website-building tool: you will edit files, but the starter creates a working example for you.</li>\n</ol>\n\n\n<ol>\n<li>Run <code>npm create astro@latest</code> and answer the prompts to name the project and choose a starter.</li>\n<li>Move into the project folder with <code>cd YOUR_PROJECT</code>, replacing YOUR_PROJECT with the name you chose.</li>\n<li>Run <code>npm run dev</code>, then open the local address printed in the terminal. You should see the starter site.</li>\n</ol>\n\n\n<ol>\n<li>If npm is not recognised, reopen the terminal after installing Node.js and check <code>node --version</code>.</li>\n<li>If the address is already in use, open the new address Astro prints rather than assuming a particular port.</li>\n<li>Press Ctrl+C in the terminal to stop the local preview.</li>\n</ol>\n\n\n<p><a href=\"https://docs.astro.build/en/install-and-setup/\">Official setup instructions</a></p>",
            "_geekist": {
                "post_type": "geek_repo_cur",
                "topics": [
                    {
                        "id": 20,
                        "name": "Framework",
                        "slug": "framework"
                    }
                ],
                "code_repository": "https://github.com/withastro/astro",
                "programming_language": "TypeScript"
            }
        },
        {
            "id": "http://172.29.142.55/the-hidden-machine-inside-modern-tooling/",
            "url": "https://geekist.co/the-hidden-machine-inside-modern-tooling/",
            "title": "The Hidden Machine Inside Modern Tooling",
            "summary": "A Geekist Exploration of What Powers the Tools That Power Us Ever wondered how modern tooling just works™? In this post, we’ll explore the engine rooms behind the frameworks we lean on every day, and hopefully you’ll walk away with a clearer sense of the machinery hidden beneath the hood.",
            "image": "https://img.geekist.co/wp-content/uploads/prep-sauce-meat-cook-steak-scaled.avif",
            "date_published": "2025-11-27T02:37:11Z",
            "date_modified": "2026-11-14T02:17:58Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Beneath the Stack",
                "Uncategorized",
                "Tame the Tech"
            ],
            "content_html": "<p><strong>A Geekist Exploration of What <em>Powers</em> the Tools That <em>Power</em> Us</strong></p>\n<p>Ever wondered how modern tooling just works™? </p>\n<p>In this post, we’ll explore the engine rooms behind the frameworks we lean on every day, and hopefully you’ll walk away with a clearer sense of the machinery hidden beneath the hood. </p>\n\n<pre>→ collecting fragments…\n→ builder queue primed…\n● unexpected prose divergence…\n← rollback triggered…\n→ resuming author in safe mode…</pre>\n<p>Anyway… where were we? </p>\n<p>Ah yes, tooling. </p>\n<p>Every tool we use behaves as if there’s a small, overworked concierge living inside it. </p>\n<blockquote>\n<p>Doesn’t it? It’s like Charon in <em>John Wick</em>: impeccable service, absolute discretion, but if you mess up the config, you’re on your own. <em>And no one is going to watch your dog.</em></p>\n</blockquote>\n<figure><img src=\"https://geekist.co/wp-content/uploads/image.gif\" alt=\"Animated clip of John Wick petting his dog with the subtitle “Good dog”, illustrating an obedient build pipeline.\" width=\"498\" height=\"208\" /></figure>\n<p>You run <code>build</code>, and everything obediently runs</p>\n<ul>\n<li>TypeScript becomes JavaScript (that no one wants to read). </li>\n<li>Sass becomes CSS. </li>\n<li>Markdown transforms into HTML.</li>\n</ul>\n<p>But we rarely pause to ask the only question that actually matters: </p>\n<blockquote>\n<p><em>How does the tool know what to do first?</em></p>\n</blockquote>\n<p>Under the hood, something knows that the eggs get cracked before they get beaten… what must wait for the pan to heat, and what absolutely cannot be trusted unsupervised. </p>\n<p>That organising instinct is the heart of tooling, the thing most developers never look at because everything “just works” …until the day it doesn’t – at which point we’re staring into a screen lit up red, frantically searching StackOverflow to see whether anyone else has suffered the same catastrophe. </p>\n<p>But the secret is that all of these tools – and that’s regardless of branding, attitude, or celebrity endorsement – share a single machinery type. </p>\n<blockquote>\n<p>They all run on <em>pipelines</em>.</p>\n</blockquote>\n<p>If you prefer industry labels, there are plenty. </p>\n<p>ETL. Compiler passes. Cloud functions in a daisy chain. CI pipelines. Data pipelines. Build pipelines. Delivery pipelines. </p>\n<p>Every one of them is a different costume placed on the same underlying idea: a line of responsibilities, executed in order, passing artefacts forward. </p>\n<p>Once you start paying attention, you’ll see this structure everywhere. <a href=\"https://geekist.co/github/webpack-build-tool-and-module-bundler/\">Webpack’s</a> chaotic reputation hides a surprisingly strict internal order. <a href=\"https://geekist.co/github/next-js-a-full-stack-react-framework/\">Next.js</a> feels effortless because every part of it knows exactly when it’s allowed to run. <code>Nx</code> organises its world like someone colour-coding their entire life. Even the slightly smug modern tools (Astro comes to mind) depend on that exact same pattern.</p>\n<h2>So what exactly is a pipeline?</h2>\n<p>If you strip the utility (and perhaps the branding) away, what you’re left with is something surprisingly humble. A pipeline is nothing more than an <em>agreement</em>. </p>\n<p>A promise, really, that certain things happen before others. That’s it. That’s the whole magic trick. One step produces something. The next step consumes it. And the next one, and the next one, until you end up with something vaguely resembling the thing you asked for in the first place. </p>\n<p>A pipeline is the developer equivalent of mise en place. Everything has its place on the counter. Everything has a time when it enters the scene. </p>\n<p>Somewhere in the early chaos of build tooling, engineers probably realised that letting everything “just run whenever” was tantamount to a suicide pact. So the industry, in its infinite wisdom, invented the simplest salvation imaginable: “What if… we ran things… in order?” The fact that this worked, and continues to work, is a testament to how little we actually need. </p>\n<p>Because once you see one (or build one), it becomes almost laughably honest. It has no ego, no theatrics, and certainly no aspiring illusion of being an <em>AI-powered mastermind.</em></p>\n<p>It just walks down a list, tapping each little worker on the shoulder as if to say, “Your turn.” Some workers return tiny gifts. Others return fully formed artefacts. Some return nonsense. Some throw errors because they weren’t prepared, or they didn’t get the thing they were supposed to get, or they looked at your config and decided they refused to participate in this farce. </p>\n<p>The pipeline keeps going anyway. It doesn’t complain. It just does the work, probably a little resentful if it could feel anything at all. </p>\n<p>But they aren’t rigid. They’re not mechanical in the “factory in 1905” sense. They’re structured, yes, but they can be expressive. They can branch, converge, or negotiate. They can inspect their own state. They can retry. They can roll back. They can gossip about the work they’ve just done. They can whisper diagnostics into your console like a confessional booth for code. </p>\n<p>Heck, if you’d like they can even compute the number of “Hail Mary’s” you’d need for penance. </p>\n<p>If that sounds dramatic, it’s because modern tooling <em>is</em> dramatic. It’s theatre. You think you’re watching the play, but backstage there’s a frantic dance of actors hitting their marks. You only see the grace because someone else solved the panicking so you don’t have to. </p>\n<p>Knowing this lets you reason about tools you use, and now that the curtain has been pulled back, we can get a little closer to the heart of it. Because beneath the metaphors and the choreography, a pipeline is made up of only three things: </p>\n<p><em>the work to be done, the relationships between the pieces, and the direction everything flows.</em></p>\n<p>It’s a <em>map</em>. </p>\n<p>Let’s talk about that. </p>\n<h2>The Map, Not the Line</h2>\n<figure><img src=\"https://geekist.co/wp-content/uploads/prep-sauce-meat-cook-steak-scaled.avif\" alt=\"Pipeline diagram where Prep branches into Sauce and Meat, which combine during Cook before producing Steak.\" width=\"2560\" height=\"1396\" /></figure>\n<p>Most people picture a pipeline as a neat procession. A beginning, some middle steps, and an end. A queue of workers waiting for their turn to contribute something valid. The diagram above illustrates this intuition perfectly, and yet it still undersells what’s really happening. </p>\n<p>Because the real question isn’t <em>what happens first</em>. </p>\n<p>The real question is <strong>what decides</strong> what happens first. </p>\n<p>What chooses whether you make the sauce before the meat? Or whether both can proceed independently? What decides <em>when</em> they’re allowed to meet in the pan? </p>\n<p>Unlike cooking though, where the chef would probably get away with a misstep by calling it culinary improvisation, code needs something that resembles the <strong>laws of physics</strong> to get things right. Don’t panic. That too was a metaphor. </p>\n<p>Below the friendly surface of “run build” lives a system where every action is spatial, not sequential. <code>Sauce</code> and <code>Meat</code> don’t care about each other until the moment they absolutely have to. <code>Prep</code> doesn’t care about <code>Cooking</code>. <code>Cooking</code> can’t begin without both its dependencies completed in the correct order, with the correct output, and in the correct state.</p>\n<p>Yep. Well-done vs Medium-rare are both still states. </p>\n<p>Nothing moves until the things it depends on are done. Not because someone told it to wait, but because, in this little universe, <strong>waiting is the only possible choice</strong>. </p>\n\nINTERACTIVE FIELD NOTES\n<h3>Who gets to cook?</h3>\n<p>Prep unlocks Sauce and Meat independently. Cook needs both; Serve waits for Cook. Step through a run to see what proceeds and what waits.</p>\n\n<p>Prep → Sauce and Meat in parallel → Cook → Serve. If Sauce fails, Cook and Serve are blocked. In this example, cleanup removes Sauce’s partial work and compensates Meat; Prep has no lasting side effect to undo.</p>\n<p>Swipe sideways to explore the full map →</p>\n\n\n\n<strong>Prep</strong>Starts the runWaiting\n<strong>Sauce</strong>Needs PrepWaiting\n<strong>Meat</strong>Needs PrepWaiting\n<strong>Cook</strong>Needs Sauce and MeatWaiting\n<strong>Serve</strong>Needs CookWaiting\n\n\n<strong>Cleanup / compensation</strong>Runs only if needed; it is separate from the forward steps.Not needed\n<p>This static map explains the dependencies. Enable JavaScript to step through a successful run or a sauce failure and recovery.</p>\n\n\nChoose a scenario\n<p> Successful run Burn the sauce</p>\n\n<p>\n</p>\n\nWhat does rollback mean here?\n<p>In this illustrative design, Sauce may leave partial temporary work, Meat has a completed effect that can be compensated, and Prep leaves nothing to undo. Real systems need explicit recovery actions; some effects cannot be undone and cleanup can fail.</p>\n\n\n\n<p></p>\n<p>And that’s all well and good when everyone behaves. When the sauce is punctual, the meat is compliant, and the pan isn’t having an existential crisis. But the universe has opinions, and so do build steps. </p>\n<p>Which brings us to the inevitable moment, the one every kitchen, every toolchain, and every pipeline eventually meets: </p>\n<blockquote>\n<p>What happens when the Chef de Partie <strong>absolutely butchers</strong> the sauce?</p>\n</blockquote>\n<p>It’s a stupidly funny question, but it’s the one that finally exposes what a pipeline <em>really</em> is. All that order, all that choreography, all that discipline… it lasts exactly until step(s) refuse to hold up their end of the deal. </p>\n<p>Because here’s the reality: </p>\n<blockquote>\n<p><em>a pipeline isn’t held together by sequence. It’s held together by expectations.</em></p>\n</blockquote>\n<p>And when one step breaks its expectation, everything downstream loses its footing. The work can’t continue. The line doesn’t advance. The map hits a dead end. </p>\n<p>That’s the moment the system has to make a choice. And the way it responds to that choice is what separates a reliable tool from one that wrecks your day.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/image-1.gif\" alt=\"neo-the-problem-is-choice\" width=\"374\" height=\"249\" /></figure>\n<p>Do we barrel ahead and pretend nothing happened? Or do we admit the cook burned the sauce and figure out how to get back to a state that actually makes sense? </p>\n<p>That’s where rollbacks enter the story. </p>\n<h2>When the Map Has to Run Backwards</h2>\n<p>In the physical world, mistakes are usually permanent. You cannot un-crack an egg. You certainly cannot un-send that email to the entire company distribution list. </p>\n<p>But inside the pipeline? <strong>Time is negotiable.</strong></p>\n<p>A rollback is the tool’s way of admitting defeat with dignity. It is the digital equivalent of a magician failing a card trick, pausing, and suddenly holding a brand new deck as if nothing happened.</p>\n<p>It relies on a concept that database engineers have worshipped for decades, and frontend developers are just starting to appreciate: <strong>Atomicity.</strong></p>\n<blockquote>\n<p><em>“All or nothing.”</em></p>\n</blockquote>\n<p>See, a good pipeline treats a unit of work like a hostage exchange. Either everyone gets across the bridge safely, or nobody moves. If the CSS compiles but the JavaScript throws a syntax error, a good build tool doesn’t give you a half-broken site. It kills the process, scrubs the temporary files, and leaves your <code>dist/</code> folder exactly how it found it.</p>\n<p>It protects you from the “half-state” – the most dangerous place in software, the “Uncanny Valley” of code where everything looks fine until you actually try to use it. It’s when the database has the user’s new email address, but the authentication service still has the old password. It’s when the npm install finished, but the post-install script died, leaving your node_modules in a state of purgatory. </p>\n<p>In a kitchen, (sorry for the relentless kitchen analogies but it works irresistibly well here), you simply cannot <em>un-burn</em> food. You throw it out, curse under your breath, and start again with clean equipment. In a pipeline, the same thing happens in a more disciplined way: a new set of steps kick in whose only job is to walk the system back to a safe place.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/prep-failedcook-cleanup-prep-800x436.avif\" alt=\"Pipeline rollback diagram showing a failed Cook step triggering Cleanup and returning the workflow to Prep instead of Serve.\" width=\"800\" height=\"436\" /></figure>\n<p>Rollbacks prevent the half-state. They are the custodial staff coming in to mop up the mess so the guests (your users) don’t know a dish caught fire </p>\n<pre>try {\n  await prepareSauce();\n  await cookMeat();\n  await plateDish();\n} catch (fire) {\n  // The crucial step we often forget\n  await extinguishFire(); \n  await apologyToCustomer();\n  await restoreSanity();\n}</pre>\n<p>This is why <code>git</code> is so powerful (and terrifying). It is essentially a time machine built entirely out of rollbacks. When you mess up a merge, you aren’t fixing the code; you are rewinding reality to a point before you made the bad decision.</p>\n<h2>What This Changes (Even If You Never Touch a Pipeline API)</h2>\n<p>Once pipelines, maps, DAGs, rollbacks, half-states, and time-travelled merges click into place, it’s tempting to file the whole thing under “nice theory” and get back to shipping features. But this is exactly the sort of theory that changes how tools are read, debugged, and designed. </p>\n<p>Next time a build fails, it stops being “Vite is broken” or “Webpack hates me.” It becomes a specific node on a map refusing to deliver what everything downstream was expecting. That small reframing is often enough to move from vague frustration to concrete investigation. </p>\n<p>When a tool offers <code>--watch</code>, incremental builds, or cached tasks, the promise becomes clearer too. Under the marketing, those features are all variations of the same behaviour: reuse the parts of the map whose inputs haven’t changed, and rerun only the nodes whose world has shifted.</p>\n<p>It’s a graph with memory. </p>\n<p>It shifts the way you think about things you do every day, from just “a bunch of shell scripts” to modelling them as steps, dependencies, expectations, and recovery paths. Some failures are acceptable and can be retried. Some demand a rollback. Some must never leave the system in a half-state. But all of them? Design choices. </p>\n<p>So it’s not so much about the ability to drop “Directed Acyclic Graph” into casual conversation, although no one said you couldn’t, it’s the fact that the machinery is no longer an oracle; it is a system with very opinionated roads. </p>\n<h3>If You Want to Poke the Machine Itself</h3>\n<p>A developer can live an entirely productive life never once implementing a custom pipeline. </p>\n<p>Some readers, however, prefer to see the gears. </p>\n<p>For that purpose, there is a pipeline engine extracted into its own package: a TypeScript library originally built to drive WPKernel’s code-generation stack, but maintained as an independent module. On npm, it is marked as beta because the surrounding framework is still evolving, not because the core pipeline is a toy. </p>\n<p>The engine in that package already does the work described in this essay: it registers helpers, builds a dependency graph, resolves order, short-circuits on errors, and coordinates rollback sequences to avoid half-states. </p>\n<p>For anyone curious enough to inspect the internals, it starts here: </p>\n\n<pre>npm install @wpkernel/pipeline</pre>\n<p>We hope this shines some light into an otherwise dense topic. We deliberately stayed wide-angled with this piece to hopefully reach a larger audience, but there is much more under the surface. Registration mechanisms. The details of graph construction. How diagnostics are threaded through and cool mechanisms around sorting tasks. </p>\n<p>Those are stories for another day. </p>\n<p>For now, feel free to drop a comment or <a href=\"https://github.com/wpkernel/wpkernel\">star the repo</a> to stay updated! </p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 1,
                        "name": "Uncategorized",
                        "slug": "uncategorized"
                    },
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    }
                ],
                "rich_media": [
                    {
                        "title": "Who gets to cook?",
                        "url": "https://geekist.co/the-hidden-machine-inside-modern-tooling/",
                        "has_controls": true,
                        "description": "Prep unlocks Sauce and Meat independently. Cook needs both; Serve waits for Cook. Step through a run to see what proceeds and what waits."
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/?p=4009",
            "url": "https://geekist.co/as-if/",
            "title": "As If.",
            "summary": "A piece that asked to exist. Build a sentence that cannot escape itself.",
            "date_published": "2025-07-25T13:48:18Z",
            "date_modified": "2026-02-04T20:42:09Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Wordsmith's Forge"
            ],
            "content_html": "<p>A piece that asked to exist.  </p>\n<blockquote>\n<p><em>Build a sentence that cannot escape itself.</em></p>\n</blockquote>\n<hr />\n<p>What could be, </p>\n<p>if it could exist,  </p>\n<p>as if it were,  </p>\n<p>as existential as it is proverbial; yes faith, yes religion, </p>\n<p>as verbiage as it is literary; mock literacy, why don’t you, </p>\n<p>as factual as it is mythical; as if idiocy lives in isolation, </p>\n<p>as singular, or plural; but why, and who, keeps count, </p>\n<p>as desired, as is unwelcome; to care, but not caring, </p>\n<p>as needed as is unwanted, as riches is debt, </p>\n<p>as essential, as inconsequential; the difference between clothes and apparel,  </p>\n<p>as criticism, as praise, as all revolutions began in rebellion,  </p>\n<p>as ironic as that sounds; where one is cyclic, and the other is oblivion, </p>\n<p>as it could be, is, or were, or would, or should, but why, and what for, and when?</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 11,
                        "name": "The Wordsmith's Forge",
                        "slug": "the-wordsmiths-forge"
                    }
                ],
                "opening_quote": {
                    "context": "A piece that asked to exist.",
                    "text": "Build a sentence that cannot escape itself."
                }
            }
        },
        {
            "id": "https://geekist.co/?p=3978",
            "url": "https://geekist.co/part-time-agile-will-work-against-you/",
            "title": "Part-time Agile Will Work Against You",
            "summary": "Clean tickets, costly stand-ups, slow velocity. Part-time Agile drains teams and delivery. Discover what skipping rituals really costs.",
            "image": "https://img.geekist.co/wp-content/uploads/part-time-agile.avif",
            "date_published": "2025-07-16T22:39:37Z",
            "date_modified": "2026-02-04T21:25:43Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Beneath the Stack",
                "Tame the Tech"
            ],
            "content_html": "<p>LinkedIn rarely fails to entertain.</p>\n<p>This week’s showcase: A founder dismisses “clean tickets” as a sign of weak engineers, while another likens standups to overpriced rituals clung to out of habit.</p>\n<p>The thing that nagged at me was the fact that each of these posts fixated on a single Agile ritual and then preached about it like gospel.</p>\n<p>Everyone <em>thinks</em> it’s Agile because they’re doing their part. Fair enough.</p>\n<p>Everyone <em>knows</em> if you skip (or skimp on) even one ceremony, without something solid in its place, that you’re skating on thin ice.</p>\n<p>What I didn’t fully realize was that doing it wrong doesn’t just weaken the process, it <em>actively</em> makes things worse.</p>\n<p>So that’s what this article is about. We will cover a few things I’ve observed along the way, why it matters, and how (as you’ll soon see) things can spiral into theatre.</p>\n<hr />\n<h2>Clean Jira Tickets is a Problem</h2>\n<p>We begin with a founder who argues that the pursuit of “clean tickets” indicates an absence of product thinking.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/image-459x480.avif\" alt=\"LinkedIn post criticises engineers wanting “clean Jira tickets,” saying it avoids ambiguity, product thinking, and ownership. Argues startups need engineers who embrace messy, changing requirements and customer contradictions.\" /></figure>\n<p>It brought to mind how I’ve managed this exact point of friction before, so I chimed in:</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/image-1.avif\" alt=\"LinkedIn post argues backlog grooming should reduce ambiguity so agile teams can measure velocity without deciphering unclear stories.\" /></figure>\n<p>To be fair, not everyone missed the point. A few replies offered grounded and thoughtful responses, like Anna’s:</p>\n<blockquote>\n<p><em>“When I asked for clean Jira tickets as a senior engineer, I meant a clear explanation of the problem—and the business purpose behind tasks that seem to make no sense at all.”</em></p>\n</blockquote>\n<p>Precisely. Context is key here. In most cases, it’s the lack of context that leads to prolonged conversations, where team members are simply trying to understand the persona, the intent and/or the use case.</p>\n<p>That back-and-forth costs time, and if you’re doing things right, that would get flagged in Retrospective – which is exactly how the definition of a story starts to take shape.</p>\n<p>And that’s when <em>clean</em> just means <em>structured</em>.</p>\n<p>Further down the thread, Dimitra put it beautifully in metaphor:</p>\n<blockquote>\n<p><em>“If you ask for ‘food’ and you mean ‘meat’, but I give you ‘salad’, I’ve covered your requirement. But now I have to do it all again.”</em></p>\n</blockquote>\n<p>This is the cost of ambiguity, and with it, inevitable frustration. This brings me back to my original point about velocity. What does it really mean?</p>\n<p>Let’s unpack that.</p>\n<h3>The Mirage of Velocity</h3>\n<p>Velocity only becomes meaningful once a team has experienced Agile functioning as a complete, closed loop:</p>\n<p><em>A need is clarified, refined, prioritized, built, delivered, and reflected on – end to end.</em></p>\n<p>This is not an easy thing to accomplish, and many teams never actually get here – at least not in a quantifiable, measurable way.</p>\n<p>Why? Because this takes time. It doesn’t happen in a single sprint; in most cases, it can’t.</p>\n<p>Those early sprints are often riddled with ambiguity, but more than that, the team is still learning how to work with <em>each other</em>, and with everyone else involved in the product cycle. It only ever becomes measurable when you remove as many dynamic elements from the process as you can. Realistically, velocity is constantly distorted by forces that have nothing to do with productivity:</p>\n<ul>\n<li>Team members leave mid-sprint and new hires spend weeks ramping up.</li>\n<li>Bugs surface (or resurface) in production, demanding emergency fixes mid-sprint.</li>\n<li>Requirements arrive late, resolved mid-sprint, while the story was already being worked on.</li>\n</ul>\n<p>Work is now estimated before ambiguity is addressed, so the numbers start to spiral, ballooning tickets and planning inevitably loses precision. Sometimes, that means that a sprint valued at 45 story points was actually worth 23 points after clarification.</p>\n<p>This is dangerous, 45 becomes the new gold standard.</p>\n<p>Some teams refine <em>after</em> completing the task, but it should’ve been solved before the sprint began. Eventually, velocity becomes less about a <em>measure of delivery</em> and more a story you’d tell yourself to <em>feel in control</em>.</p>\n<p>What follows is actually very predictable: ceremonies are questioned and the value of grooming, retros, even stand-up is downgraded.</p>\n<p>The undercurrent of impatience silently brews.</p>\n<blockquote>\n<p>“We’ll figure it out as we go.”<br />“No need to over-process.”<br />“Let’s just build.”</p>\n</blockquote>\n<p>The worst part about it is that it looks like <em>pragmatism</em> and you start to convince yourself that it is <em>efficient</em>.</p>\n<p>More often than not, these are symptoms of burnout and the unravelling of a systemic failure in the process.</p>\n<p>Which brings us to the second post, where Agile gets <em>audited</em>, albeit, somewhat <em>angrily</em>.</p>\n<h2>The Cost of Clarifying</h2>\n<p>If clean tickets sparked moral panic, the daily standup got hit with a valuation.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/image-2-364x480.avif\" alt=\"LinkedIn post criticises daily standups as wasteful, sharing math on lost hours and costs. Argues the best teams skip standups and just ship.\" /><figcaption>(For brevity, this is an excerpt. The full post included a follow-up claim about high-performing teams avoiding standups entirely.)</figcaption></figure>\n<p>73 mins? I… I am lost for words here.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/image-3-480x338.avif\" alt=\"LinkedIn post says standups should be capped at 9 people, under 10 minutes, with larger teams using parallel scrums. Longer standups waste time.\" /></figure>\n<p>So how can the total duration of a standup, even if participants number at 12, stop at 5 or 10 minutes?</p>\n<p>You take it <em>offline</em>.</p>\n<p>Standup needs 3 things from each participant:</p>\n<ul>\n<li>What you did yesterday: What you started, completed or got stuck with.</li>\n<li>What you’re doing today: What your <em>perfectly productive day</em> is going to look like.</li>\n<li>Any impediments?: You state <em>what</em>, possibly <em>who</em> you need help with or from, but you <strong>never discuss it</strong>.</li>\n</ul>\n<p>That last bit is critical because that is exactly what offline means. Standup works marvelously when you quickly remove blockers by having conversations with relevant people before your day begins.</p>\n<p>That ideal day <em><strong>is</strong></em> the focus</p>\n<p>Otherwise, you’re making it clear you can’t proceed with <strong>clear reasons why.</strong></p>\n<p>Perhaps the person you need help from isn’t around or is busy.<br /><em>That’s why standup insists everyone is present</em>.</p>\n<p>Perhaps the requirements are ambiguous. <br /><em>That’s exactly what Backlog Refinement is for and it’s something to note for Retrospective.</em></p>\n<p>Either way, that transparency is context everyone needs. It’s indispensable.</p>\n<p>Abusing it is just sacrilegious.</p>\n<h2>The Real Cost is Disconnection</h2>\n<p>There’s a psychological side to Agile that’s massively underrated. But it’s there and it matters more than most people realize.</p>\n<p>Standup gives you trickled moments of pride when you report a completed task – and those small daily wins matter because they compound validation over time. It’s also a platform where you’re allowed to bother the right people for the right reasons. If you get told that what you <em>thought</em> was important – actually isn’t – that’s useful too.</p>\n<p>The clarity you get in Backlog Refinement builds confidence. You know what you’re doing and why. That kind of confidence is exactly what turns someone into the “senior dev” that earlier post so casually threw under the bus.</p>\n<p>Retrospectives matter for different reasons. They give you the opportunity to be heard and help you understand what <em>can</em> and <em>can’t</em> be worked on. In either case, that’s a critical pressure release valve every sprint cycle.</p>\n<p>That’s what ownership looks like. It’s the clarity to contribute with purpose.</p>\n<p>Because it’s <em>yours</em>.</p>\n<h2>When Agile Aligns</h2>\n<p>I’ll end with a short story about something you can’t really explain well in a résumé, but still stands as one of the greatest personal highlights of my career.</p>\n<p>I once conducted a Scrum Poker session with developers, loan specialists, program managers, and insurance folks, all working on a complex marketplace project for a bank.</p>\n<p>And the coolest thing happened: Every single one of them voted the same number for story points. Over and over. Story after story.</p>\n<p>No one said anything and I don’t think they noticed. But for me, it was one of the biggest (yet quietest) moments of alignment I’d ever experienced.</p>\n<p>Why?</p>\n<p>Because it worked so well, so seamlessly, that no one realized what they were doing perfectly.</p>\n<p>That’s the real win isn’t it?</p>\n<p>Silent, <em>flawless</em> alignment.</p>\n<hr />\n\n<h3>Are clean Jira tickets anti-Agile?</h3>\n<p>While some founders might dismiss them, “clean tickets” simply mean “structured” and clear. They are crucial for providing context, reducing ambiguity, and accurately measuring team velocity. Well-defined tickets help avoid confusion and wasted time in clarifying requirements.</p>\n<h3>Why is my Agile team’s velocity inconsistent or misleading?</h3>\n<p>Because it’s easily distorted by factors unrelated to true productivity. These include team changes (members leaving/joining), unexpected bugs requiring urgent fixes, or late-arriving requirement changes. True velocity is only measurable when the entire Agile loop (from clarification to delivery) is functioning smoothly, which takes time to achieve.</p>\n<h3>How can daily standups be effective and not a waste of time in Agile?</h3>\n<p>Keep them very brief (5-15 minutes max), even for larger teams. The focus should strictly be on: what was done yesterday, what will be done today, and potential impediments. All detailed discussions or problem-solving related to impediments must be taken “offline” immediately after the standup, involving only the relevant people.</p>\n<h3>What happens if Agile teams skimp on ceremonies like backlog grooming or retrospectives?</h3>\n<p>Skipping or “skimping” on Agile ceremonies like backlog grooming or retrospectives, without solid alternatives, <strong>makes things worse</strong> for the team. This leads to increased ambiguity, frustration, burnout, and a breakdown in the systemic process. It creates a false sense of pragmatism that ultimately undermines delivery and team morale.</p>\n<h3>What are the hidden psychological benefits of consistent Agile rituals?</h3>\n<p>Consistent Agile rituals offer significant psychological benefits. Daily standups provide small moments of pride and validation, backlog refinement builds confidence by clarifying purpose, and retrospectives offer a crucial pressure release valve, fostering a sense of being heard and contributing to team ownership.</p>\n\n<p></p>\n<p>While some founders might dismiss them, “clean tickets” simply mean “structured” and clear. They are crucial for providing context, reducing ambiguity, and accurately measuring team velocity. Well-defined tickets help avoid confusion and wasted time in clarifying requirements.</p>\n<p>\\n\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Why is my Agile team’s velocity inconsistent or misleading?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n\\n</p>\n<p>Because it’s easily distorted by factors unrelated to true productivity. These include team changes (members leaving/joining), unexpected bugs requiring urgent fixes, or late-arriving requirement changes. True velocity is only measurable when the entire Agile loop (from clarification to delivery) is functioning smoothly, which takes time to achieve.</p>\n<p>\\n\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How can daily standups be effective and not a waste of time in Agile?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n\\n</p>\n<p>Keep them very brief (5-15 minutes max), even for larger teams. The focus should strictly be on: what was done yesterday, what will be done today, and potential impediments. All detailed discussions or problem-solving related to impediments must be taken “offline” immediately after the standup, involving only the relevant people.</p>\n<p>\\n\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What happens if Agile teams skimp on ceremonies like backlog grooming or retrospectives?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n\\n</p>\n<p>Skipping or “skimping” on Agile ceremonies like backlog grooming or retrospectives, without solid alternatives, <strong>makes things worse</strong> for the team. This leads to increased ambiguity, frustration, burnout, and a breakdown in the systemic process. It creates a false sense of pragmatism that ultimately undermines delivery and team morale.</p>\n<p>\\n\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What are the hidden psychological benefits of consistent Agile rituals?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n\\n</p>\n<p>Consistent Agile rituals offer significant psychological benefits. Daily standups provide small moments of pride and validation, backlog refinement builds confidence by clarifying purpose, and retrospectives offer a crucial pressure release valve, fostering a sense of being heard and contributing to team ownership.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/?p=3648",
            "url": "https://geekist.co/the-5-best-downloaders-for-videos-music-images-no-browser-needed/",
            "title": "The 5 Best Downloaders for Videos, Music & Images (No Browser Needed)",
            "summary": "Remember downloading at 4KB/sec? These five modern tools are faster and don’t need a browser. Perfect for terminal nerds and nostalgia junkies alike.",
            "image": "https://img.geekist.co/wp-content/uploads/THE-5-BEST-MEDIA-DOWNLOADERS-2048x1308.avif",
            "date_published": "2025-07-15T19:05:26Z",
            "date_modified": "2026-02-04T21:35:51Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tame the Tech",
                "Tools of the Trade"
            ],
            "content_html": "<p>Before YouTube, Spotify, and Netflix dominated the internet, the only way we could get our hands on videos and music was to download them. Also, internet speeds weren’t ever measured in <strong>Mbps</strong> or <strong>Gbps</strong>.</p>\n<p>We downloaded on <strong><em>Kbps</em></strong>. Let that sink in for a moment.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/dialup-1-480x320.avif\" alt=\"A vintage Windows download dialog box showing a file with 0.49% completed and an estimated time left of 39 years.\" /></figure>\n<p>That meant a movie would take an entire day if you were lucky. If not, you’d wait a couple of days at least (and pray the landline didn’t start ringing!).</p>\n<p>When I was a teen, you could grab a pirated copy of just about anything via torrents or apps like Kazaa, LimeWire, or Napster, but those weren’t ever meant to last anyway.</p>\n<p>In this article, we’ll explore new ways to download videos, images, and music with the resurgence of some clever CLI tools and a little tinkering.</p>\n<p>You might have heard about <code>youtube-dl</code>, once the undisputed YouTube downloader, only to be dethroned by a newer tool called <code>yt-dlp</code>. But there are options available now. Some don’t even need you to download anything and instead allow you to directly stream media onto your favorite media app.</p>\n<p>Let’s take a look at five standout tools and the unique tricks each one brings to the table.</p>\n<h2>Download Everything With <code><code></code></code><a href=\"https://geekist.co/github/yt-dlp-an-audio-video-downloader/\">yt-dlp</a></h2>\n<p>Let’s start with the tool that took the crown from <code>youtube-dl</code>.</p>\n<p><code>yt-dlp</code> is what most folks (not just the cool kids who wear sunglasses indoors) reach for these days when they want to download videos from YouTube or pretty much any popular media site.</p>\n<p>It’s fast, reliable, supports thousands of platforms, and has so many flags you’ll spend more time reading flags than watching the actual video.</p>\n<p>Here’s are some quick install instructions (if you’re on macOS or Linux):</p>\n<pre>brew install yt-dlp\n# or for the hardcore\npip install -U yt-dlp</pre>\n<p>Now say you want to download an entire YouTube channel. That’s easy:</p>\n<pre>yt-dlp https://www.youtube.com/@beetlejuicearchives3490</pre>\n<p>Want just the audio in MP3?</p>\n<pre>yt-dlp -x --audio-format mp3 https://www.youtube.com/@beetlejuicearchives3490</pre>\n<p>Here’s where things get wild: <code>yt-dlp</code> also integrates with <code>SponsorBlock</code>. That means it can automatically skip over sponsored segments in videos. You don’t have to do anything fancy, just pass a flag:</p>\n<pre>yt-dlp --sponsorblock-remove sponsor https://www.youtube.com/watch?v=hH2I8rR07aM</pre>\n<figure></figure>\n<p>You can also sort and filter download formats with fine-grained control. Want only the highest-quality MP4 with AAC audio?</p>\n<pre>yt-dlp -f \"bv[ext=mp4][height&lt;=1080]+ba[ext=m4a]\" https://www.youtube.com/watch?v=xyz</pre>\n<p>All that and we’re still only just scratching the surface. It can handle playlists, metadata, cookies, rate-limits, and even merge video and audio streams with FFmpeg under the hood.</p>\n<p>That said, if you’re not into downloading anything and you just want to watch a video straight from the source, right inside your media player app, there’s a tool for that too!</p>\n<h2>Stream It Like You Stole It With <code><code></code></code><a href=\"https://geekist.co/github/you-get-dumb-downloader-that-scrapes-the-web/\">you-get</a></h2>\n<p>That’s exactly what <code>you-get</code> does. It pulls media from sites like YouTube, Vimeo, Twitter, and others, and streams it directly into apps like <code>MPV</code> or <code>VLC</code> without leaving the terminal.</p>\n<p>Here’s how to install it:</p>\n<pre>brew install you-get\n# or if you're managing Python packages manually\npip install -U you-get</pre>\n<p>Now, say you’ve found a video and just want it to play instantly:</p>\n<pre>you-get --player vlc https://www.youtube.com/watch?v=jNQXAC9IVRw</pre>\n<p>This hands the video off directly to <code>VLC</code>, and the stream begins, no file clutter and no fussing with browser extensions. Most of all, no more mystery files named <code>video_final_FINAL_v2(1).mp4</code> cluttering your desktop. You treat it like a streaming service shortcut.</p>\n<p>Of course, for the control-freaks among us, yes, you can still save the file.</p>\n<pre>you-get https://twitter.com/username/status/1234567890</pre>\n<p>Or inspect the available formats before deciding:</p>\n<pre>you-get -i https://vimeo.com/12345678</pre>\n<p>We’ll also cover a music-first workflow that keeps your Spotify playlists mirrored on disk automatically.</p>\n<p>Let’s take a look at <code>spotDL</code>.</p>\n<h2><strong>Sync Your Music Library With </strong><a href=\"https://geekist.co/github/spotdl-download-spotify-playlists/\">spotDL</a></h2>\n<p>If you want a music-first workflow that stays in sync with your playlists, spotDL is the right tool. Point it at a Spotify playlist (yours or public), and it fetches matching audio from YouTube/YouTube Music, writes proper metadata/cover art, and – crucially – keeps things updated with an incremental sync file.</p>\n<p>To install (pick one):</p>\n<pre># Recommended\npipx install spotdl\n# or:\npip install spotdl</pre>\n<p>Unlike the other tools here, spotDL does more than grab a single file: it mirrors whole playlists and keeps them in sync. That means the first command looks a little busier, but it’s because you’re creating a sync file that defines the playlist on disk. After that, updates are as simple as re-running one command.</p>\n<p>Initialize a playlist sync (creates a .spotdl file) and download:</p>\n<pre># Create a real sync file + download into ./dubstep-favourites/\nspotdl sync \"https://open.spotify.com/playlist/27uRJq4FVTL1zAZ8DdoZJr\" \n  --save-file dubstep-favourites.spotdl \n  --output \"dubstep-favourites/{artist} - {title}.{ext}\" \n  --m3u \"dubstep-favourites.m3u8\"</pre>\n<p>• <code>--save-file</code> creates a .spotdl sync file (must end with .spotdl).<br />• <code>--output</code> controls how filenames are written (here: “Artist – Title”).<br />• <code>--m3u</code> auto-generates a playlist file for media players.</p>\n<p>Think of this like “snapshotting” your Spotify playlist into a folder. That’s why you’d find the next command useful, it incrementally syncs this playlist to disk:</p>\n<pre>spotdl sync dubstep-favourites.spotdl \n  --output \"dubstep-favourites/{artist} - {title}.{ext}\" \n  --m3u \"dubstep-favourites.m3u8\"</pre>\n<p>Now it only pulls new/changed tracks. No need to re-enter the playlist URL.</p>\n<p><code>SpotDL</code> takes care of your music collection and keeps it neat, but what if you’re after something more immediate – like catching a Twitch stream as it happens, or saving a broadcast while you watch?</p>\n<p>That’s where <code>streamlink</code> comes in.</p>\n<h2>Stream Live or Save It With <a href=\"https://geekist.co/github/streamlink-pipe-video-streams-to-your-player/\">streamlink</a></h2>\n<p>Not everything you want to grab comes as a neat file with a download link. A lot of media online today (especially live events) is served as HLS or DASH streams. That’s where <code>streamlink</code> comes in.</p>\n<p>It supports a long list of services via maintained plugins (e.g. YouTube, Twitch, BBC iPlayer, Vimeo, TikTok). Use it when you’d rather play or capture the stream, rather than fully “download” via an extractor.</p>\n<p>You can install it with <code>pip</code> or <code>brew</code>:</p>\n<pre>brew install streamlink\n# or:\npipx install streamlink</pre>\n<p>Play a stream instantly:</p>\n<pre>streamlink \"https://www.youtube.com/watch?v=jNQXAC9IVRw\" best</pre>\n<p>The <code>best</code> keyword automatically picks the highest quality available, though you can choose 720p, 480p, or even audio if you want to save bandwidth.</p>\n<p>But why stop there? Why not record it while watching? Remember those old cable boxes that came with a built-in Harddisk that recorded your favorite TV show so you can watch it a hundred times over later (and bore the life out of your cat)?</p>\n<pre>streamlink --record \"~/Videos/{author}/{title}-{time:%Y%m%d%H%M%S}.ts\" \n  -p mpv \"https://twitch.tv/day9tv\" best</pre>\n<p>Yes. Yes, of course. You don’t need to <em>watch</em> it to have a copy:</p>\n<pre>streamlink --output \"~/Videos/{author}/{title}-{time:%Y%m%d%H%M%S}.ts\" \n  \"https://twitch.tv/day9tv\" best</pre>\n<p>But that would mean you might miss the stream going live at 11pm tonight, wouldn’t it? For that, there’s <code>at</code>:</p>\n<pre>brew install at\nbrew services start atd</pre>\n<p>👉 <em>macOS doesn’t ship with at/atd anymore; Apple moved to launchd. Homebrew’s <code>atd</code> gets you the classic one-shot scheduler back.</em></p>\n<p>And that means both you (and the cat) get your shut-eye at 11pm and still have a copy tucked away for later:</p>\n<pre>echo 'streamlink --record ~/Videos/{title}.ts https://twitch.tv/day9tv best' | at 23:00</pre>\n<blockquote>\n<p>💡 Want it to stop after 2 hours?</p>\n</blockquote>\n<pre>brew install coreutils   # provides `gtimeout` on macOS\necho 'gtimeout 7200 streamlink --record ~/Videos/{title}.ts https://twitch.tv/day9tv best' | at 23:00</pre>\n<p>And yep, it works for <code>yt-dlp</code> jobs too. So we’ve covered media downloads (YouTube with <code>yt-dlp</code>, Spotify with <code>spotDL</code>) and now live streams on demand with streamlink.</p>\n<p>What about images? Enter <code>gallery-dl</code>.</p>\n<h2>Download Images Like a Wizard With <code><code></code></code><a href=\"https://geekist.co/github/gallery-dl-download-image-galleries-collections/\">gallery</a><code><code></code></code><a href=\"https://github.com/mikf/gallery-dl\">-dl</a></h2>\n<p>If <code>yt-dlp</code> is the multitool for video, then <code>gallery-dl</code> is more like a precision instrument for images. It’s not just for generic image URLs either; it actually understands how full galleries work on sites like Twitter, Reddit, DeviantArt, Pixiv, Danbooru, and even Tumblr.</p>\n<p>Here’s the quick install:</p>\n<pre>brew install gallery-dl\n# or for the hardcore\npip install -U gallery-dl</pre>\n<p>Want to download every image from a specific Reddit post?</p>\n<pre>gallery-dl https://www.reddit.com/r/EarthPorn/comments/abc123</pre>\n<p>Or maybe you’ve found an artist’s full portfolio on Twitter?</p>\n<pre>gallery-dl https://twitter.com/username</pre>\n<p>You can even go full hacker mode and just extract the direct image URLs without downloading them:</p>\n<pre>gallery-dl --get-urls https://twitter.com/username/status/1234567890</pre>\n<p>This prints out the raw image links to your terminal so you can inspect and pass them into another script or tool. It’s great if you’re building an automation pipeline or if you just want to see what’s actually behind a page without committing to a full download.</p>\n<p>There’s full config support too. Want everything downloaded into folders named by artist and source? Done. Want to skip posts that don’t match a certain tag, language, or resolution? You can do that. It’s almost scary how much you can tweak.</p>\n<p>Here’s a taste of what a config file might look like (totally optional, but quite powerful):</p>\n<pre>{\n  \"base-directory\": \"~/Pictures/gallery\",\n  \"twitter\": {\n    \"cookies\": \"twitter-cookies.txt\",\n    \"username\": \"your_username\"\n  },\n  \"output\": {\n    \"mode\": \"tagged\"\n  }\n}</pre>\n<p>You might be collecting memes or just downloading reference material, whatever your image downloading needs are, <code>gallery-dl</code> handles it all surprisingly easy.</p>\n<hr />\n<p>Back in the day, apps like Kazaa and LimeWire made things feel easy. You searched, you clicked, and the download started (eventually).</p>\n<p>There was a kind of thrill to it, even though it was very likely the file turned out to be mislabeled or corrupted.</p>\n<p>These CLI tools might not have the glossy buttons or cartoonish logos, but for developers, tinkerers, and anyone who lives in the terminal, they’ve become indispensable. They’re faster and definitely more flexible.</p>\n<p>In many ways, they’re more reliable than anything we had back then.</p>\n<p>Hopefully you found something new in this lineup that you didn’t know you needed. If this kind of nerdy deep dive is your thing, consider subscribing. There are more posts like this already in the pipeline.</p>\n<hr />\n\n<h3>Can I keep a Spotify playlist mirrored locally and updated over time?</h3>\n<p>Use <code>spotDL</code>’s sync mode. Initialize with a playlist URL and a <code>.spotdl</code> file, then run <code>spotDL sync</code> whenever you want to pull changes.</p>\n<h3>What’s the best tool to EXTRACT audio from YouTube?</h3>\n<p><code>yt-dlp</code> is your best bet. It lets you extract audio in MP3 or other formats with a simple flag.</p>\n<h3>Can I stream videos ON MY DESKTOP without downloading?</h3>\n<p>Yes. That’s exactly what <code>you-get</code> is for. It hands off videos to your media player without saving any files.</p>\n<h3>Which tool should I use for image galleries?</h3>\n<p>Use <code>gallery-dl</code>. It’s built specifically for downloading from image-heavy sites like Twitter, Reddit, Pixiv, and DeviantArt.</p>\n<h3>What about live streams or sites that expose HLS/DASH?</h3>\n<p>Use <code>streamlink</code>. Pipe to VLC or record to disk with <code>--output</code> or <code>--record</code>.</p>\n<h3>Can I automate these tools in a script or scheduled tasks?</h3>\n<p>Absolutely. All five tools are terminal-based and script-friendly, but they deserve special mention:</p>\n<p>• <code>yt-dlp</code> and <code>gallery-dl</code> both support config files so you can bake in flags and never re-type them.</p>\n<p>• <code>spotDL</code> uses a <code>.spotdl</code>sync file. Just call <code>spotDL sync</code> in a cron job and you’re in-sync</p>\n<p>• <code>streamlink</code> pairs with schedulers like<code>at</code>. Combine with <code>gtimeout</code> so live streams start &amp; stop at the times you set.</p>\n<p>In short: yes, you can wrap them all in scripts, from one-liners in bash to recurring jobs in launchd or systemd.</p>\n\n<p></p>\n<p>Use <code>spotDL</code>’s sync mode. Initialize with a playlist URL and a <code>.spotdl</code> file, then run <code>spotDL sync</code> whenever you want to pull changes.</p>\n<p>\"}},{\"@type\":\"Question\",\"name\":\"What’s the best tool to EXTRACT audio from YouTube?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"</p>\n<p><code>yt-dlp</code> is your best bet. It lets you extract audio in MP3 or other formats with a simple flag.</p>\n<p>\"}},{\"@type\":\"Question\",\"name\":\"Can I stream videos ON MY DESKTOP without downloading?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"</p>\n<p>Yes. That’s exactly what <code>you-get</code> is for. It hands off videos to your media player without saving any files.</p>\n<p>\"}},{\"@type\":\"Question\",\"name\":\"Which tool should I use for image galleries?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"</p>\n<p>Use <code>gallery-dl</code>. It’s built specifically for downloading from image-heavy sites like Twitter, Reddit, Pixiv, and DeviantArt.</p>\n<p>\"}},{\"@type\":\"Question\",\"name\":\"What about live streams or sites that expose HLS/DASH?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"</p>\n<p>Use <code>streamlink</code>. Pipe to VLC or record to disk with <code>--output</code> or <code>--record</code>.</p>\n<p>\"}},{\"@type\":\"Question\",\"name\":\"Can I automate these tools in a script or scheduled tasks?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"</p>\n<p>Absolutely. All five tools are terminal-based and script-friendly, but they deserve special mention:</p>\n<p>• <code>yt-dlp</code> and <code>gallery-dl</code> both support config files so you can bake in flags and never re-type them.</p>\n<p>• <code>spotDL</code> uses a <code>.spotdl</code>sync file. Just call <code>spotDL sync</code> in a cron job and you’re in-sync</p>\n<p>• <code>streamlink</code> pairs with schedulers like<code>at</code>. Combine with <code>gtimeout</code> so live streams start &amp; stop at the times you set.</p>\n<p>In short: yes, you can wrap them all in scripts, from one-liners in bash to recurring jobs in launchd or systemd.</p>\n<p>\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 6,
                        "name": "Tools of the Trade",
                        "slug": "tools-of-the-trade"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/?p=4007",
            "url": "https://geekist.co/of-writing-or-something-like-it/",
            "title": "Of Writing, Or Something Like It",
            "summary": "Another task, Another ask: write with control, at first. Let it slip. Let the thought unravel, then into something ghostlike that still lingers long after it should have ended.",
            "date_published": "2025-05-22T20:22:00Z",
            "date_modified": "2026-11-17T04:23:34Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Wordsmith's Forge"
            ],
            "content_html": "<p><em>Another task, Another ask:</em></p>\n<blockquote>\n<p><em>write with control, at first. Let it slip. Let the thought unravel, then into something ghostlike that still lingers long after it should have ended.</em></p>\n</blockquote>\n<hr />\n<p>I would never start a sentence in control, certainly not in the opening line of the opening paragraph. No, not quite like who I am, or how I write.</p>\n<p>Oh? But that was quite loudly assertive! Just as much – dramatic, as it was insidious, in equal measure.</p>\n<p>Almost as if one was primed with identity, and then, callously, carelessly, <em>callus-ly</em> betrayed in the act of it.</p>\n<p>Of writing. An art, part in form of literary nuance, yet dominated by structure and logic; the penning down of words which, yet, needs the pen no longer.</p>\n<p>The act has transformed, but missed nonetheless. The feel of pen on paper on desk, on ink on wood upon wood, where each stroke’s preciseness – or lack thereof – is felt in subtle vibration through device to hand, and hand through to one’s mind, irking with satisfaction as their eyes witness the aftermath… the collateral, one might suppose.</p>\n<p>Penning is no more, some might say; not in the form most remember. But with that, we gain but at least one benefit:</p>\n<p>Coherence.</p>\n<p>In writing, I mean, but not so much in words, as I have all but so incoherently illustrated.</p>\n<p>m.</p>\n<p>That! That was exactly what I spoke of, the mark of permanence, damaged, one that couldn’t have possibly revealed itself no sooner than I had finished supposing the aftermath of incoherence. I broke cadence in the reveal, for now you know I spoke not of provenance, but of distaste; in the most tasteful manner of course.</p>\n<p>Still, I cannot think of a way better to describe unintended imprint… without a pen.</p>\n<p>So it shall stay. So that it haunts you as it does me.</p>\n<p>Like callus. The kind you would see on the hands of a teacher, after years of practice with chalk and its sniped landings on the top of one’s head.</p>\n<p>Now wouldn’t that be provenance?</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 11,
                        "name": "The Wordsmith's Forge",
                        "slug": "the-wordsmiths-forge"
                    }
                ],
                "opening_quote": {
                    "context": "Another task, Another ask:",
                    "text": "write with control, at first. Let it slip. Let the thought unravel, then into something ghostlike that still lingers long after it should have ended."
                }
            }
        },
        {
            "id": "http://172.29.142.55/?p=3464",
            "url": "https://geekist.co/you-can-blog-from-your-local-wordpress-site-on-iphone-heres-how/",
            "title": "Yes, you can Blog from your Localhost WordPress on iPhone.",
            "summary": "Access your local WordPress site from your iPhone using ZeroTier or Tailscale. Blog from anywhere securely, privately & with no cloud in sight",
            "image": "https://img.geekist.co/wp-content/uploads/tailscale-v-zerotier-wordpress-showdown.avif",
            "date_published": "2025-05-18T05:58:55Z",
            "date_modified": "2026-11-15T00:01:34Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tame the Tech",
                "Tools of the Trade"
            ],
            "content_html": "<p>Blogging is supposed to be simple. Write words. Hit publish. (And then maybe admire your cleverness.)</p>\n<p>But if you’re self-hosting WordPress locally, there’s nothing simple about it. You’re knee-deep in plugin madness &amp; static site exports and then you’re left wondering why Lighthouse is screaming murder at your LCP.</p>\n<p>My original plan was clean and logical. Get the stack running, wire up Cloudflare Pages, then post like a boss.</p>\n<p>Of course, <em>nothing</em> went according to plan, but those will need 3 more posts, so let’s not bore you.</p>\n<p>Instead, let me tell you how I’m writing this <em>right now</em> on my iPhone, all while WordPress is quietly sitting on my Mac behind <em>localhost.</em></p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/writing-directly-from-my-phone-722x800.\" alt=\"Writing directly from my iPhone\" title=\"Writing directly from my iPhone\" /></figure>\n<h2>Don’t quite get what I’m saying?</h2>\n<p>WordPress is installed locally on my Mac with no access to the outside world. But I still use it to write posts and build pages like normal. Then, using a plugin called Simply Static, I export the entire site and host it on Cloudflare Pages.</p>\n<p>The only issue with this workflow is the fact that it makes it nearly impossible to use the WordPress app on other device, because there is no way of discovering where your WordPress installation is located.</p>\n<p>So what’s the solution?</p>\n<p>There are two services that work perfectly for this. The first is <a href=\"https://www.zerotier.com/download/\">ZeroTier</a> and the second is <a href=\"https://tailscale.com/download\">Tailscale</a>. Both have a free tier that allows you to set up a private network mesh (think VPN) that you have complete control over. This means that your phone connects to a secure network that you can choose to add services to.</p>\n<p>And for this use case? It’s actually perfect.</p>\n<h2>Great. How do I get started?</h2>\n<p>The process is almost exactly the same for both services, so choose the service you want to use below.</p>\n\n\n<h3>Setting It Up with ZeroTier</h3>\n<p>Here’s how you can access your local WordPress site from your phone, even if it’s just on <code>localhost</code>.</p>\n<h4>1. Install ZeroTier on both devices</h4>\n<ul>\n<li>On your Mac, <a href=\"https://www.zerotier.com/download/\">download and install ZeroTier</a>.</li>\n<li>Do the same on your <strong>iPhone</strong> (it’s on the App Store).</li>\n<li>Once installed, both devices will get unique <strong>Node IDs</strong>.</li>\n</ul>\n<h4>2. Create a ZeroTier Network</h4>\n<ul>\n<li>Go to <a href=\"https://my.zerotier.com/\">my.zerotier.com</a> and sign in (GitHub login works).</li>\n<li>Click “Create a Network”.</li>\n<li>Copy the Network ID (you’ll need it in the next step).</li>\n</ul>\n<h4>3. Join the Network from each device</h4>\n<ul>\n<li>On your Mac:<br /><code>zerotier-cli join &lt;your-network-id&gt;</code> (or use the GUI if you prefer)</li>\n<li>On your iPhone:<br />Paste the Network ID into the app and tap <strong>Join Network</strong>.</li>\n<li>Go back to the ZeroTier dashboard and <strong>approve</strong> both devices under <strong>Members</strong>.</li>\n</ul>\n<h4>4. Find your Mac’s ZeroTier IP</h4>\n<ul>\n<li>Once connected, ZeroTier assigns your Mac a virtual IP like <code>10.x.x.x</code>.</li>\n<li>You’ll see this IP in the ZeroTier dashboard next to your Mac’s name.</li>\n</ul>\n<h4>5. Update WordPress to accept remote connections</h4>\n<ul>\n<li>Edit <code>wp-config.php</code> and add the following. Doing it this way allows WordPress to respond to both <code>localhost</code> (or whatever you set your local domain to) and IP addresses. This works out perfectly because, well, it’s on your local machine anyway.</li>\n</ul>\n<pre>define('WP_HOME', \"http://$host\");\ndefine('WP_SITEURL', \"http://$host\");</pre>\n<h4>6. Open the WordPress App on iPhone</h4>\n<ul>\n<li>Add the <strong>full IP address </strong>of your Mac and port like:<br /><code>10.x.x.x:8080</code></li>\n<li>Login with your WordPress credentials.</li>\n</ul>\n<p>💡 <em>Remember that you can’t use custom hosts here as your phone doesn’t know which address that host points to.</em></p>\n<p>That’s it! <strong>You’re In</strong> ®</p>\n\n\n<p>Setting It Up with Tailscale</p>\n<p>Want the same magic but using Tailscale instead of ZeroTier? The steps are nearly identical — just a bit more elegant thanks to its identity-based access and built-in DNS.</p>\n<h4>1. Install Tailscale on both devices</h4>\n<ul>\n<li>On your Mac, <a href=\"https://tailscale.com/download/\">download and install Tailscale</a>.</li>\n<li>On your iPhone, install the <a href=\"https://apps.apple.com/us/app/tailscale/id1475497147\">Tailscale app from the App Store</a>.</li>\n<li>Sign in on both devices with the same account (Google, GitHub, or Microsoft).</li>\n</ul>\n<h4>2. Authorise devices in your Tailscale admin panel</h4>\n<ul>\n<li>Go to <a href=\"https://login.tailscale.com/admin/machines\">login.tailscale.com/admin/machines</a>.</li>\n<li>You should see both your Mac and iPhone listed.</li>\n<li>Approve them if required (usually automatic).</li>\n</ul>\n<h4>3. Note your Mac’s Tailscale IP or MagicDNS name</h4>\n<ul>\n<li>Tailscale assigns your Mac a stable IP like <code>100.x.x.x</code>, or a <strong>MagicDNS name</strong> like:<br /><code>geekist-mac.local.tailnet-yourname.ts.net</code></li>\n<li>Either one works. MagicDNS is easier to remember (and you won’t need to hardcode IPs later).</li>\n</ul>\n<h4>4. Update WordPress to accept remote connections</h4>\n<p>Just like in the ZeroTier setup, edit <code>wp-config.php</code> with:</p>\n<pre>define('WP_HOME', \"http://$host\");\ndefine('WP_SITEURL', \"http://$host\");</pre>\n<p>Where <code>$host</code> can be either:</p>\n<ul>\n<li><code>100.x.x.x:8080</code> (Tailscale IP), or</li>\n<li><code>geekist-mac.local.tailnet-yourname.ts.net:8080</code> (MagicDNS)</li>\n</ul>\n<h4>5. Add your site to the WordPress app</h4>\n<ul>\n<li>Open the WordPress app on your iPhone.</li>\n<li>Choose <strong>“</strong>Add self-hosted site<strong>”</strong>.</li>\n<li>Enter the <strong>full address</strong> including port, e.g.:<br /><code>http://100.x.x.x:8080</code> or <code>http://geekist-mac.local.tailnet-yourname.ts.net:8080</code></li>\n<li>Login with your normal credentials.</li>\n</ul>\n<p>💡 <em>If you use MagicDNS, there’s no need to remember the IP address. </em></p>\n<p>It <strong>Just Works.</strong>™</p>\n\n\n<h2>Wait. So Which one to pick?</h2>\n<p>Honestly, it comes down to what kind of person you are.</p>\n<p>If you like seeing everything, ZeroTier will speak your language. It lets you name your networks, manually approve devices (and run a dashboard that feels like your own little ISP.)</p>\n<p>It feels wonderfully self-contained. The trade-off is that setup takes a little more intent.</p>\n<p>Tailscale, on the other hand, behaves more like something that’s already part of your system. You sign in &amp; it just works. Devices show up automatically, MagicDNS remembers the names for you, and you don’t have to click “approve” anywhere. If you’re the type who wants to forget you ever set it up, this one’s probably the better fit.</p>\n<p>Both are excellent, both are free for the use case we’ve talked about and both will let you blog from your phone like some sort of secret agent tunnelling into your own localhost.</p>\n<p>If you already use one of them for other projects, stick with it. If you’re starting fresh, try both. You’ll know within ten minutes which one feels right.</p>\n<hr />\n<p>Blogging from your phone doesn’t have to mean surrendering control to third-party platforms or cloud editors. With a simple mesh network setup and a local WordPress install, you can draft, edit &amp; publish your posts exactly how you want (<em>from wherever you are</em>).</p>\n<p>And whether you go with ZeroTier or Tailscale, it doesn’t matter much because the results are the same:</p>\n<p>Your blog, your rules, your environment. Private and under your control.</p>\n<hr />\n\n<h3>Can I access my local WordPress site from my phone?</h3>\n<p>Not directly. But by using a mesh VPN tool like Tailscale or ZeroTier, your phone or tablet can securely connect to your Mac’s localhost WordPress install and access it through the WordPress app.</p>\n<h3>Which is better: Tailscale or ZeroTier?</h3>\n<p>Both are excellent. Tailscale is easier to set up and manage thanks to MagicDNS and automatic device approval. ZeroTier offers more granular control and is great if you like tweaking network settings.</p>\n<h3>Will this work on mobile data or only Wi-Fi?</h3>\n<p>Well both. As long as your iPhone is connected to the internet and the VPN mesh, it will be able to reach your Mac from anywhere.</p>\n<h3>Is it safe to access WordPress over Tailscale or ZeroTier?</h3>\n<p>Yes. Both tools create encrypted peer-to-peer connections between your devices without exposing your WordPress site to the public internet. Your content stays private, and there’s no need to open firewall ports or rely on third-party tunnels.</p>\n\n<p></p>\n<p>Not directly. But by using a mesh VPN tool like Tailscale or ZeroTier, your phone or tablet can securely connect to your Mac’s localhost WordPress install and access it through the WordPress app.</p>\n<p>\\n\\n\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Which is better: Tailscale or ZeroTier?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n\\n\\n</p>\n<p>Both are excellent. Tailscale is easier to set up and manage thanks to MagicDNS and automatic device approval. ZeroTier offers more granular control and is great if you like tweaking network settings.</p>\n<p>\\n\\n\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Will this work on mobile data or only Wi-Fi?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n\\n\\n</p>\n<p>Well both. As long as your iPhone is connected to the internet and the VPN mesh, it will be able to reach your Mac from anywhere.</p>\n<p>\\n\\n\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Is it safe to access WordPress over Tailscale or ZeroTier?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n\\n\\n</p>\n<p>Yes. Both tools create encrypted peer-to-peer connections between your devices without exposing your WordPress site to the public internet. Your content stays private, and there’s no need to open firewall ports or rely on third-party tunnels.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 6,
                        "name": "Tools of the Trade",
                        "slug": "tools-of-the-trade"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/?p=3101",
            "url": "https://geekist.co/the-invisible-cdn-we-built-in-2012-for-dynamic-avatars/",
            "title": "The Invisible CDN We Built for Display Pics",
            "summary": "We built a dynamic display picture system in 2012 using X-Accel-Redirect and NGINX, serving fresh content with static-like speed, without a full CDN stack.",
            "image": "https://img.geekist.co/wp-content/uploads/pexels-photo-31670555-31670555.avif",
            "date_published": "2025-04-22T22:35:14Z",
            "date_modified": "2026-02-04T21:25:38Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Beneath the Stack",
                "Tame the Tech"
            ],
            "content_html": "<h2>We called them DPs back then. You might know them as profile pictures.</h2>\n\n<p>I found it by accident. </p>\n<p>Buried in an old project folder, long-forgotten PHP files still humming with logic that <em>somehow</em> still works today. And not just technically functional, but conceptually relevant. Maybe even ahead of its time. </p>\n<p>But to appreciate what it did exactly, you’d have to understand what it was trying to solve. </p>\n<h2>💫 The Problem</h2>\n<p>The application functioned as a social network, where profile pictures weren’t just aesthetic, they were identity. Display pictures (DPs) had to update fast, stay visible everywhere and somehow keep up with the user. That meant you couldn’t just serve a static image. You needed something smarter. Something dynamic. A system that could ensure the images remained current, even on posts written years earlier. </p>\n<h2>❖ The Existing Solutions</h2>\n<p>By 2012, the problem of dynamic DPs <em>seemed</em> solved. Facebook had cracked it. DPs changed and appeared instantly, even on years-old posts. But look under the hood and there was little public documentation on how it worked… Anywhere. The rest of us just had to piece it together ourselves. </p>\n<p>Most developer forums back then were still discussing crude options: </p>\n<ol>\n<li><strong>Serve via app</strong> – <code>image.php?user_id</code> (slow, uncacheable)</li>\n<li><strong>Save on disk</strong> – <code>uuid.jpg</code> in <code>/uploads/</code></li>\n<li><strong>Store in the DB</strong> – blobs in MySQL (don’t even) </li>\n<li><strong>Set up a CDN</strong> – but good luck managing keys, origins, headers (and bills)</li>\n</ol>\n<p>Each option had a fatal flaw. (1) and (2) made images fragile; if your app server went down, so did your photos and (3) was a storage disaster waiting to happen. </p>\n<p>(4) was the only viable answer if you were aiming for scale and speed. But it had problems of its own. Not just cost or abuse, but something more fundamental, <em>posterity</em>. </p>\n<p>You could save the DP with a new UUID every time it changed, but then you were back to serving outdated images in every previous post. If you overwrote the original instead, that meant dealing with CDN purges or versioning edge rules. </p>\n<p>In other words, (4) solved delivery but broke consistency. It was never a <em>set-and-forget</em> solution. You had to choose between real-time updates and the convenience of caching. </p>\n<p>That old code didn’t just sidestep the trade-offs. It answered the question that none of the others really solved: </p>\n<blockquote>\n<p><em>How do you serve dynamic content with static delivery confidence?</em></p>\n</blockquote>\n<p>That’s why <em>this</em> deserved to be found and <em>why it’s worth writing about.</em></p>\n<h2>✨ The Code That Solved It</h2>\n\n<pre>&lt;?php defined('SYSPATH') or die('No direct script access.');\n\n/**\n * A simple controller that returns the location of an avatar for a given user.\n * It sets nginx headers so it can redirect the request to serve the static file\n * instead of having PHP handle the file.\n *\n * @author Jason Nathan\n * @category RealtAsia\n * @package RT_Controller\n * @subpackage Avatar\n * @version 1.0\n * @copyright 2012 Realtasia Pte Ltd\n */\nclass Controller_Avatar extends Controller {\n\n  /**\n   * A simple method that retrieves a user by id, checks for an existing avatar\n   * or redirects to the default after checking user gender.\n   *\n   * @return Response The response headers\n   */\n  public function action_index() {\n    $url = '/s3/';\n    $b = $url . RT::BUCKET . '/avatars/';\n\n    $this-&gt;response-&gt;send_headers();\n    $id = trim($this-&gt;request-&gt;param('id'));\n    $size = (int) $this-&gt;request-&gt;param('size');\n    $user = Document::factory('user')-&gt;collection();\n\n    $u = $user-&gt;findOne(\n      ['_id' =&gt; new MongoID($id)],\n      ['info.gender' =&gt; 1, 'avatar' =&gt; 1]\n    );\n\n    if (Arr::get($u, 'avatar')) {\n      return $this-&gt;response-&gt;headers([\n        'X-Accel-Redirect' =&gt; $url .\n          str_replace($id, \"$id/$size\", $u['avatar'])\n      ]);\n    }\n\n    return $this-&gt;response-&gt;headers([\n      'X-Accel-Redirect' =&gt; $b .\n        ucfirst(substr($u['info']['gender'], 0, 1)) . $size . '.png'\n    ]);\n  }\n}</pre>\n<p>The real magic is in lines 38 – 48. </p>\n<p>What these lines do is subtle but powerful: they remove the burden of serving avatar images from your app entirely, while still keeping the image path dynamic. Instead of outputting the image directly, they instruct Nginx to take over, using <code>X-Accel-Redirect</code> to silently serve the right file from a protected internal path.</p>\n<p>It means your app can make smart decisions (like checking for a custom avatar or falling back to defaults), but still deliver the image at static-speed. No extra DB hits for repeat views. No CDN edge purges. No exposed URLs. Just one redirect header and the illusion of magic. </p>\n<p>And once that controller knew where to point, all it needed was a web server smart enough to step aside. Here’s the config we had in place for Nginx: </p>\n\n<pre>server {\n  root /home/manager/www/api;\n  index index.html index.htm index.php;\n\n  server_name api.realtasia.com;\n\n  location = /favicon.ico {\n    return 204;\n    access_log off;\n    log_not_found off;\n  }\n\n  location / {\n    try_files $uri $uri/ /index.php?$args;\n  }\n\n  # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000\n  location ~ .php$ {\n    fastcgi_split_path_info ^(.+.php)(/.+)$;\n    # NOTE: You should have \"cgi.fix_pathinfo = 0;\" in php.ini\n\n    # With php5-cgi alone:\n    # fastcgi_pass 127.0.0.1:9000;\n    # With php5-fpm:\n    fastcgi_pass unix:/var/run/php5-fpm.sock;\n    fastcgi_index index.php;\n    fastcgi_send_timeout 50m;\n    include fastcgi_params;\n    fastcgi_read_timeout 50m;\n    include fastcgi_params;\n  }\n\n  location /uploads {\n    autoindex off;\n  }\n\n  location ~* ^/s3/(.*?)/(.*) {\n    internal;\n    resolver 8.8.8.8;\n    access_log /var/log/nginx/s3.access.log;\n    error_log /var/log/nginx/s3.error.log;\n    set $download_uri $2;\n    set $download_host $1;\n    set $download_file http://$download_host/$download_uri;\n\n    proxy_set_header Host $download_host;\n    proxy_set_header Authorization '';\n    proxy_max_temp_file_size 0;\n    proxy_pass $download_file;\n  }\n}</pre>\n<p>Again, lines 37 – 49 did it all. </p>\n<p>This single Nginx block turned our PHP controller into a silent traffic conductor. Once the avatar logic ran, the controller simply passed along the correct file path using <code>X-Accel-Redirect</code>. Nginx intercepted the response and – without ever hitting disk, database or further PHP execution – proxied the request to its final destination.</p>\n<p>Because PHP never handled the image directly, the request path was highly cacheable. The controller itself benefitted from opcode caching (yes, even back then), so the logic overhead was negligible. Downstream, the avatar image retained its original headers, <em>including ETags</em>, ensuring that browser and CDN-level caching kicked in without disruption. This got us fewer hits, faster loads and almost zero strain on the app server. </p>\n<p>What that meant was: </p>\n<p>This wasn’t just a workaround. It was infrastructure thinking ahead of its time. We didn’t have edge functions or programmable CDNs. We had control over our stack, a clear understanding of the problem, and maybe a bit of ingenuity. Over a decade later, that invisible CDN still holds its ground. </p>\n<p>Turns out, when you design for posterity instead of trend, even your old PHP can age like wine. </p>\n<p>Questions? Shoot me up in the comments. </p>\n<blockquote>\n<p>Like this config? There’s a whole book of them.<br />Check out <strong><em><a href=\"https://geekist.co/nginx-by-example/\">Nginx by Example Vol. 1</a></em></strong> and make your server cry tears of joy.</p>\n</blockquote>\n<hr />\n\n<h3>How can I serve user profile pictures without exposing direct URLs?</h3>\n<p>Use a backend controller that returns internal redirect headers (like <code>X-Accel-Redirect</code>) instead of serving files directly. This masks file paths and prevents scraping or link sharing.</p>\n<h3>What is the best way to cache user avatars across posts and pages?</h3>\n<p>Proxy the avatar through Nginx with <code>X-Accel-Redirect</code>, preserve cache headers like ETags, and use consistent request paths so both CDN and browser caches can handle delivery.</p>\n<h3>How do I prevent stale profile pictures in cached pages?</h3>\n<p>Serve avatars via a dynamic route that always resolves to the latest image. By not tying image URLs to specific filenames or timestamps, all posts automatically reflect the current avatar.</p>\n<h3>Can I build my own CDN-like delivery system for free?</h3>\n<p>Yes. By combining Nginx internal redirects with local storage or cheap object storage (like Cloudflare R2), you can avoid external CDN fees and still get CDN-grade performance.</p>\n<h3>What’s the difference between X-Accel-Redirect and regular PHP image delivery?</h3>\n<p><code>X-Accel-Redirect</code> hands the request off to Nginx, bypassing PHP execution and allowing the web server to serve static files directly. This greatly improves performance and scalability.</p>\n\n<p></p>\n<p>Use a backend controller that returns internal redirect headers (like <code>X-Accel-Redirect</code>) instead of serving files directly. This masks file paths and prevents scraping or link sharing.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What is the best way to cache user avatars across posts and pages?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Proxy the avatar through Nginx with <code>X-Accel-Redirect</code>, preserve cache headers like ETags, and use consistent request paths so both CDN and browser caches can handle delivery.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How do I prevent stale profile pictures in cached pages?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Serve avatars via a dynamic route that always resolves to the latest image. By not tying image URLs to specific filenames or timestamps, all posts automatically reflect the current avatar.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Can I build my own CDN-like delivery system for free?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Yes. By combining Nginx internal redirects with local storage or cheap object storage (like Cloudflare R2), you can avoid external CDN fees and still get CDN-grade performance.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What’s the difference between X-Accel-Redirect and regular PHP image delivery?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p><code>X-Accel-Redirect</code> hands the request off to Nginx, bypassing PHP execution and allowing the web server to serve static files directly. This greatly improves performance and scalability.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/?p=2010",
            "url": "https://geekist.co/the-editorial-engine-a-technologists-pilgrimage/",
            "title": "The Editorial Engine: A Technologist’s Pilgrimage",
            "summary": "What if the reason you're not writing isn't discipline, but design? A technologist reflects on blogging, voice, and where it all begins.",
            "image": "https://img.geekist.co/wp-content/uploads/a-technologist-pilgrimage.avif",
            "date_published": "2025-04-15T21:44:35Z",
            "date_modified": "2026-11-15T00:01:05Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Geekery"
            ],
            "content_html": "<p>My journey with writing didn’t just begin. I must have started a hundred times over now, to the point that you could say, I’m somewhat of an <em>expert</em> at starting (and stopping, but we’ll ignore that for the moment) </p>\n<p>Some time last year, I stumbled upon some of my articles from more than 10 years ago and I thought.. <em>What happened?!</em></p>\n<p>It was almost alarming, first that I didn’t remember writing that much and second that I had articles in countless different database dumps, which were, I might add, thankfully archived and tucked away. </p>\n<p>So I thought about why I didn’t continue all those other times and I realised that it was <em>because</em> I was a developer, as ironical as that sounds. </p>\n<p>You see every time I started, I had to wrestle with the fact that I needed the site to look and feel <em>different</em>, and for the most part, I had nailed that. Just take a look at my <a href=\"https://github.com/jasonnathan/jasonnathan.meteor.com\">past years’</a> portfolio <a href=\"https://github.com/jasonnathan/www.jasonnathan.me\">sites</a> and you’d see that time was spent on how the sites looked and functioned, more than it ever was focused on writing. </p>\n<figure>\n<figure><img src=\"https://geekist.co/wp-content/uploads/jasonnathan-articles-iphone5-800x547.avif\" alt=\"Image of iphone render of the blog section in the 2016 portfolio site\" /><figcaption>Blog view 2016 portfolio site</figcaption></figure>\n<figure><img src=\"https://geekist.co/wp-content/uploads/react-overview-800x533.avif\" alt=\"Image of iphone render of the skills section in the 2016 portfolio site\" /><figcaption>Skills view 2016 portfolio site</figcaption></figure>\n</figure>\n<p>And so in December last year, I decided to start writing again but I wanted to focus on just that and wanted something simple, where I could use my own domain (hopefully for free) and was at least <em>half-decent</em> looking. </p>\n<p>This time I didn’t want a portfolio site, and I didn’t want to be cornered into creating content I didn’t care much for, especially for ones that only ever served to impress those that stumbled on my site. </p>\n<p>Enough, I thought, <em>words meant more.</em></p>\n<p>My research led me to <a href=\"https://hashnode.com/\">Hashnode</a> and <a href=\"https://www.blogger.com/\">Blogger</a>. Both fit my primary criteria about custom domains. </p>\n<p>I settled for Hashnode. Not because there was anything wrong with Blogger, mind you. I was writing in <a href=\"https://obsidian.md/\">Obsidian</a>, and Blogger didn’t support Markdown. (That was it!) I still can’t believe that alone decided it. </p>\n<p>I started sharing posts on Reddit and one of them crossed <a href=\"https://www.reddit.com/r/selfhosted/s/LCfFmmn5wJ\">125k views with over 230 shares</a>! </p>\n\n<blockquote><p><a href=\"https://www.reddit.com/r/selfhosted/comments/1hho3bm/smarter_subdomain_and_ssl_setup_with_nginx_a/\">Smarter Subdomain and SSL Setup with Nginx: A Hands-On Guide</a><br /> by<a href=\"https://www.reddit.com/user/chicagojango/\">u/chicagojango</a> in<a href=\"https://www.reddit.com/r/selfhosted/\">selfhosted</a></p></blockquote>\n<p></p>\n<p>That was a turning point, at least psychologically. Suddenly, what I wrote mattered more than anything I thought the site needed to be. It changed <em>why</em> I wrote, and how I <em>built</em> for writing. </p>\n<p>And so write I did. </p>\n<p>But most of all, I think the fact that it was a “flat” writing experience with no categories and strict topics to write about, or worse still, prematurely compartmentalizing posts to some preconceived idea of what the blog should be about – was exactly what I needed. No boxes. No buckets. Just a blank space and the thought, <em>what if I just wrote anyway?</em></p>\n\n<figure>\n<blockquote>\n<p><em>Don’t yet think about monetizing if you’re serious about writing.</em></p>\n</blockquote>\n</figure>\n\n<p>Most “<em>how to make money blogging</em>” guides tell you to find your niche market. I’d say, find your niche <em>voice</em> first. (Or <em>voices</em>, as it apparently is in my case.) </p>\n<p>A little perseverance has a funny way of bringing opportunities <a href=\"https://www.reddit.com/r/freelanceWriters/comments/1jgyzqd/first_gig_after_years_of_dabbling/\">when you least expect it</a>. </p>\n\n<blockquote><p><a href=\"https://www.reddit.com/r/freelanceWriters/comments/1jgyzqd/first_gig_after_years_of_dabbling/\">First Gig after years of Dabbling!</a><br /> by<a href=\"https://www.reddit.com/user/chicagojango/\">u/chicagojango</a> in<a href=\"https://www.reddit.com/r/freelanceWriters/\">freelanceWriters</a></p></blockquote>\n<p></p>\n<p>When it does come, it won’t be because you chased it. It’ll be because you stayed. </p>\n<p>My journey started grand, a post a day (or so I thought). I managed 12 articles in 12 days before that train screeched to a halt. Life got in the way. Quality too. I didn’t quite like the way I’d said things, but the articles were researched, so I left them be. </p>\n<p>Not daily, then, but two or three posts a week was enough for patterns to emerge. </p>\n<p>The subjects that <a href=\"https://geekist.co/cadence/\">got me up at night</a> – to write – began revealing themselves. Sure, Geekist is rather <em>self-incriminating</em> in that sense. One look at the name tells you something about the subject matter. </p>\n<p>But still, it’s a broad term and what exactly entailed “Geek” was what I needed to know. But that didn’t come with <em>planned</em> posts. </p>\n<p>It came with <em>written</em> posts. </p>\n<p>Even if you didn’t have the faintest clue what that is, write about anything. In fact, I’d argue that you should start with <em>everything</em>. </p>\n<p>Pick a name that means something to you, but leaves you room to wander. Anything to avoid that ridiculous thought: </p>\n<p><em>“Ah. I can’t write about that, this isn’t the place.”</em></p>\n<p>Well. Where else exactly? </p>\n<p>But let’s get back to what I had originally intended to say. Yes. I digress… <em>sometimes</em></p>\n<p>I outgrew Hashnode. It was simple and elegant, but the writing had grown into something that warranted a little method in the madness. </p>\n<p>And I did make that journey. From <em>Hashnode</em> to <em>Headless Hashnode &amp; Eleventy</em> and eventually <em>PayloadCMS</em>. Where did I end up?</p>\n<p>WordPress. Yep. WordPress. After all that.</p>\n<p>And here I am, writing this on my phone, using a WordPress client that had been available all along. Quite the pilgrimage, huh?</p>\n<p>Yeah… it’s just words again, but this time they mean a whole damn more. </p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 9,
                        "name": "The Geekery",
                        "slug": "the-geekery"
                    }
                ],
                "references": {
                    "mentions_mcp": false,
                    "github_links": [
                        "https://github.com/jasonnathan/jasonnathan.meteor.com",
                        "https://github.com/jasonnathan/www.jasonnathan.me"
                    ],
                    "public_product_links": [],
                    "public_products": []
                }
            }
        },
        {
            "id": "https://geekist.co/?p=2355",
            "url": "https://geekist.co/cadence/",
            "title": "Cadence",
            "summary": "An innocent request, at an unwittingly appropriate time; write a brief but disproportionately difficult attempt to rest…",
            "date_published": "2025-04-09T20:08:00Z",
            "date_modified": "2026-11-17T04:23:45Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Wordsmith's Forge"
            ],
            "content_html": "<p><em>An innocent request, at an unexpectedly appropriate time</em>:</p>\n<blockquote>\n<p><em>write a brief but disproportionately difficult attempt to rest…</em></p>\n</blockquote>\n<hr />\n\n<p>It would be a distinct brand of baffling, I’d say, to be given such a task no thirty minutes sooner than the unholy witching hour. </p>\n<p>Baffling, I’d say again, but I can’t say what more of; that it illuminates the rather embarrassing reality of how strikingly reflective the request is to current consequence, almost tangible - one might curiously propose, as if embodied within one’s physical self - or, that it serves to mock that very premise instead.</p>\n<p>One where the protagonist, you in this case, is secretly well aware of said witches looming in dark corners, patiently ready to reveal themselves within the sanctity of what brief period they’re mythically allowed to roam, unceremoniously, I might add - if it wasn’t at all a myth. </p>\n<p>Yet it would add character to a night, if I had the unwitting indulgence of encountering one.</p>\n<p>But I digress.</p>\n<p>Ah. Digression. </p>\n<p>A laughable epiphany; for it is that very trait that I possess that hath landed me in this awkward position with you.</p>\n<p>And the witches. </p>\n<p>It isn’t usually this entertaining, I’d say. It is conversely quite a bit louder. Senseless noise that might bury any semblance of hope somewhere deep between the belly and the nether area.</p>\n<p>As if I myself was not already in a very nether area of my own.</p>\n<p>But I should quickly address the ask, lest I lose you altogether, stuck in this endless depth of nether areas.</p>\n<p>Let’s think about this, nothing deep this time, I assure you, unless you count the appalling lack of one in slumber.</p>\n<p>I suppose there is this carousel of bed and sofa, oh no, I think it would be better labelled as musical chairs.</p>\n<p>The sofa usually wins.</p>\n<p>Otherwise there’s reading, hardly any writing, unless you count ruthless, and dare I say relentless, otherworldly and deliberate…<br /><em>(wait, there is one more adjective that escapes me at this moment). </em><br />No matter, as I was saying, this obnoxious, premeditated injection of a highly cognitive ask…<br /><em>(Blatant. That was what I was looking for. Darn it.)</em> <br />of a creative penning down of prose, no less, with witches for company.</p>\n<p>I lie. The witches have all left now, probably from the boredom, but more likely because they discovered an unexpected witness.</p>\n<p>Other times, I build musical symphonies in my head; yet there is danger in those attempts, and it depends on how exciting or mundane the result. I’d say with certainty that they are usually much more phenomenal, exponential only in relation to how much I need it not to be.</p>\n<p>Sigh. It occurred to me there is not much else left to say; and yet, after all those words, I haven’t actually had a chance to be explicit.</p>\n<p><em>About what.</em></p>\n<p>Such is cadence.</p>\n<p></p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 11,
                        "name": "The Wordsmith's Forge",
                        "slug": "the-wordsmiths-forge"
                    }
                ],
                "opening_quote": {
                    "context": "An innocent request, at an unexpectedly appropriate time:",
                    "text": "write a brief but disproportionately difficult attempt to rest…"
                }
            }
        },
        {
            "id": "https://geekist.co/?p=2360",
            "url": "https://geekist.co/chaos-cohere/",
            "title": "Chaos Cohere",
            "summary": "An ask, made whilst dissecting the chaotic beauty of a piece of political writing; write out a wandering reflection that lands on a sentence discussed: \"But how much control does he really have?\"",
            "date_published": "2025-04-09T17:08:00Z",
            "date_modified": "2026-11-17T04:23:53Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Wordsmith's Forge"
            ],
            "content_html": "<p><em>An ask, made whilst dissecting the chaotic beauty of a piece of political writing</em>:</p>\n<blockquote>\n<p><em>write out a wandering reflection that lands on the sentence discussed: “But how much control does he really have?”</em></p>\n</blockquote>\n<hr />\n\n<p>If perhaps the suggestion before me is that I should perform this exercise within the confines of the referenced article, then I must respectfully decline; for I am neither informed, nor do I <em>care enough</em> to be informed about political narratives, save the irony that it was I myself that introduced it to begin with.</p>\n<p>Suffice it to say, to find a voice in such matters, one must be in possession of the currency to have a voice in such matters.</p>\n<p>Still, if there is a remote possibility that the original request might tolerate a prose from a perspective so disparate, so disconnected from the former, that it can barely be called a tangent, then there just might be some semblance to progress in the endeavour. After all, none was mandated, as far as one could tell.</p>\n<p>The first order of business would be to assume - quite unremarkably - the gender of the one making the request, which in this specific case would work better as that of a man.</p>\n<p>And if such a notion could be entertained, then we might pivot to the fact that he cannot possibly have known how his request would pan out - nor could he have guessed the fact that I’m writing this response from a terribly inconvenient convenience; <em>a phone.</em></p>\n<p>But, then again, how much control does he really have?</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 11,
                        "name": "The Wordsmith's Forge",
                        "slug": "the-wordsmiths-forge"
                    }
                ],
                "opening_quote": {
                    "context": "An ask, made whilst dissecting the chaotic beauty of a piece of political writing:",
                    "text": "write out a wandering reflection that lands on the sentence discussed: “But how much control does he really have?”"
                }
            }
        },
        {
            "id": "https://geekist.co/?p=2107",
            "url": "https://geekist.co/neo-shouldve-picked-the-blue-pill/",
            "title": "Neo Should’ve Picked the Blue Pill",
            "summary": "A Sci-Fi fable of fat, fire & forgotten biology, where ketosis outshines carb culture & the machines that plugged into the wrong end.",
            "image": "https://img.geekist.co/wp-content/uploads/the-blue-pill.avif",
            "date_published": "2025-04-09T04:28:55Z",
            "date_modified": "2026-11-17T06:12:21Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Fables for Food"
            ],
            "content_html": "<h2>What if I told you… we burn better than we think?</h2>\n<p>If you think long and hard enough, for most of human history? </p>\n<p>We burnt fat. </p>\n<p>I don’t mean that metaphorically or philosophically. This is before food rituals even existed. Our ancestors built empires with it. They lit temples and survived sieges &amp; famines by taping into a secret stash that every one of them carried: </p>\n<p><em>Animal fat</em></p>\n<p>It came with labels a many. Tallow, lard, suet, even whale oil. Fat was a currency for survival. When a Roman army marched, their grease trail marked their route. When a Viking set out, his <a href=\"https://amzn.to/4j4R6Oa\">fat-packed stores</a><sup>1</sup> wrapped in cloth &amp; legend marked his fury. </p>\n<p>In the frigid lairs, Inuit tribes <a href=\"https://amzn.to/4lsFmqk\">powered their bodies</a><sup>2</sup> on a diet that modern dieticians would label as madness! But they weren’t concerned, they were warm; <em>they were alive</em>! </p>\n<p>And thus, the story of fat unfolds, not the one of decadence (which is really all too familiar), but rather, the one by design. </p>\n<blockquote>\n<p><em>Sugar is but a finicky flicker; fat a fiery forge.</em></p>\n</blockquote>\n<h2>The Science</h2>\n<p>You’ve likely read it all. You probably know by now. Still, if only to measure the <del>steaks</del> stakes, one must understand the alchemy. </p>\n<p>A molecule of <em>triglyceride</em> slips into the bloodstream, escorted with the ceremony of a royal guest. The liver, ever the master chemist, performs it’s incantations. Beta oxidation. Ketogenesis. A slight tingle behind the eyes. And then it happens. </p>\n<p><em>Fire in a new form.</em></p>\n<p>Ketone bodies emerge. <em>Acetoacetate</em>. <em>Beta-hydroxybutyrate</em>. But perhaps the most poetic of all? Acetone. </p>\n<p>Yes. Nail polish remover. </p>\n<p>You smell it, faintly, on your breath in the morning. That sharpness. That chemical ghost of your body burning its reserves, sending signals from the inside. </p>\n<p>A whisper of fire on your tongue, and no, it’s not the curry. </p>\n<p>Nor is it dysfunction. ‘Tis elegance. Evolution’s quiet contingency. When sugar is scarce. Burn slow. Burn clean. Don’t panic. </p>\n<p>Somewhere along the way, we forgot. From the tender age’s introduction to sweets, to the <em>Gluco-rush</em>, to the Crash. It’s <em>the Cycle</em> of life as we knew it. </p>\n<p>We invented breakfast cereals and energy bars, forgetting that our species once traversed deserts on camel milk and clumps of butter wrapped in leaves. Sugar became king. </p>\n<p>But fat was always <em>sovereign</em>. </p>\n<p>And then Hollywood came along and tried to plug us in. </p>\n<hr />\n<h2>The Science<em></em>Fiction</h2>\n<p>Let’s talk about <em>The Matrix</em>. That 1999 blend of leather &amp; latex and characters who wore shades like it was battle armor. </p>\n<p>It asked all the big questions. What is real? What is freedom? And, <em>bafflingly</em>, what if machines harvested humans to generate… electricity? </p>\n<p>Electricity. </p>\n<p>From our bodies. </p>\n<p>Sure. </p>\n<p>Now, let’s be kind and assume the machines had it rough. The average human brain outputs less electrical power than an LED bulb. (Not the fancy ones, the cheap ones at the back of the shelf) </p>\n<p>Meanwhile, the same human body contains around 100,000 kilocalories of stored fat, a biochemical goldmine, if you’re even halfway serious about harvesting energy. </p>\n<p>And if that energy did in fact come from humans, you wouldn’t bother with the cerebral cortex, you’d go straight for the subcutaneous treasure chest. </p>\n<p>They plugged into the <em>wrong end</em>. </p>\n<p>The brain emits thought. And thought demands the most complex of systems to sustain. </p>\n<p>The gut is where the real power plants were.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/2025/04/The-Matrix-Pod.avif\" alt=\"A futuristic person with orange orbs rising through her body, surrounded by wires in a glowing Matrix pod.\" width=\"1024\" height=\"1024\" /><figcaption>Digital artwork of a woman in a sci-fi chair with wires and orange glow, evoking themes of cybernetic augmentation.</figcaption></figure>\n<p>Had the machines understood metabolism, they’d have redesigned the pods. No cranial jacks. Just long tubes that siphoned short-chain fatty acids, fermented butyric acid, maybe even the odd ketone pulse. </p>\n<p>They’d have skipped the whole “simulate life” nonsense and gone full bioreactor. Keep the host in fasting, in a peaceful coma. Maintain low insulin. </p>\n<p>Humanity would’ve just sat there, blissfully ketotic, dreamlessly sipping away in sleep while our livers kept the world running. </p>\n<p>And it would’ve worked. We aren’t made to be <em>plugged in</em> but we’re sure as hell made to burn. </p>\n<p>Slowly. </p>\n<p>Elegantly. </p>\n<p>Like an oil lamp in a howling Nordic storm. </p>\n<p>The machines <em>got it wrong</em>. </p>\n<p>The Matrix didn’t fail because humans are rebellious. </p>\n<p>It failed because no one taught the machines to count calories. </p>\n<hr />\n<p><strong>Book References on Amazon </strong></p>\n\n\n\n\n<figure><img src=\"https://geekist.co/wp-content/uploads/2025/04/Fat-of-the-Land-e1744395393879.avif\" alt=\"Book cover for 'The Fat of the Land' by Vilhjalmur Stefansson, featuring a steak on slate.\" width=\"240\" height=\"340\" /><figcaption>Cover of ‘The Fat of the Land’ showing a seared steak with rosemary on a dark background.</figcaption></figure>\n<figure><img src=\"https://geekist.co/wp-content/uploads/An-early-Meal-e1744395485464.avif\" alt=\"Book cover for 'An Early Meal', a Viking Age cookbook.\" /><figcaption>Cover of ‘An Early Meal’ featuring a Viking ship on calm water at dusk.</figcaption></figure>\n\n\n\n\n<p><sup>1 </sup>An Early Meal – a Viking Age Cookbook &amp; Culinary Odyssey<br /><sup>2 </sup>The Fat of the Land </p>\n<p>*<em>these are affiliate links</em></p>\n<p>Related Posts.</p>\n\n<ul>\n<li>\n<figure><a href=\"https://geekist.co/how-to-roast-potatoes-in-an-air-fryer-a-gargantuan-task/\"><img src=\"https://img.geekist.co/wp-content/uploads/2026/11/air-fryer-roast-potatoes-golden-crispy.webp\" alt=\"How to Roast Potatoes in an Air Fryer. A Gargantuan Task.\" width=\"1536\" height=\"864\" /></a></figure>\n<h3><a href=\"https://geekist.co/how-to-roast-potatoes-in-an-air-fryer-a-gargantuan-task/\">How to Roast Potatoes in an Air Fryer. A Gargantuan Task.</a></h3>\nNovember 17, 2026\n\n<p>How to roast crispy, golden air-fryer potatoes with fluffy centres, a serving multiplier, adjustable spices and one gloriously sarcastic domestic encounter.</p>\n<p><a href=\"https://geekist.co/how-to-roast-potatoes-in-an-air-fryer-a-gargantuan-task/\">Read More</a></p>\n\n</li>\n<li>\n<figure><a href=\"https://geekist.co/grospel-of-croffee-the-parable-of-the-maidens-plea/\"><img src=\"https://img.geekist.co/wp-content/uploads/2025/03/the-book-of-brewvelations.avif\" alt=\"Grospel of Croffee: The Parable of the Maiden’s Plea\" width=\"1280\" height=\"720\" /></a></figure>\n<h3><a href=\"https://geekist.co/grospel-of-croffee-the-parable-of-the-maidens-plea/\">Grospel of Croffee: The Parable of the Maiden’s Plea</a></h3>\nMarch 23, 2025\n\n<p>Oat milk? In keto?! A poetic tale of forbidden flavour, almond betrayal, and the sacred union of cream. The Grospel deepens.</p>\n<p><a href=\"https://geekist.co/grospel-of-croffee-the-parable-of-the-maidens-plea/\">Read More</a></p>\n\n</li>\n<li>\n<figure><a href=\"https://geekist.co/croffee-anyone-or-kroffee-if-youre-so-inclined/\"><img src=\"https://img.geekist.co/wp-content/uploads/2025/03/free-photo-of-coffee-in-cup-in-overhead-view-1-scaled-e1744304142791.avif\" alt=\"Croffee anyone? Or Kroffee if you’re so inclined.\" width=\"1024\" height=\"683\" /></a></figure>\n<h3><a href=\"https://geekist.co/croffee-anyone-or-kroffee-if-youre-so-inclined/\">Croffee anyone? Or Kroffee if you’re so inclined.</a></h3>\nMarch 20, 2025\n\n<p>Ditch almond milk! Discover Croffee, the ultimate keto hack. A hilarious take on keto coffee alternatives &amp; plant-based myths.</p>\n<p><a href=\"https://geekist.co/croffee-anyone-or-kroffee-if-youre-so-inclined/\">Read More</a></p>\n\n</li>\n</ul>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 13,
                        "name": "Fables for Food",
                        "slug": "fables-for-food"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/?p=1996",
            "url": "https://geekist.co/the-architects-who-built-our-digital-foundation/",
            "title": "The Architects Who Built Our Digital Foundation",
            "summary": "Meet the pioneers who built AI, C, Unix, and Apollo software: 5 coding legends whose brilliance shaped the systems we still rely on today.",
            "image": "https://img.geekist.co/wp-content/uploads/the-architects.avif",
            "date_published": "2025-04-08T06:22:10Z",
            "date_modified": "2026-11-15T00:10:16Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Geekery"
            ],
            "content_html": "<p>Have you wondered who they were? Did you stop to think about our humble beginnings and what led us to where we are today? </p>\n<p>We did. So we went digging. And in true Geekist style, we bring you both the brilliance <em>and </em>blemishes. </p>\n<h2><a href=\"https://en.wikipedia.org/wiki/John_McCarthy_(computer_scientist)\">John McCarthy</a> – Creator of Lisp, Coiner of “Artificial Intelligence”</h2>\n\n\n<figure><img src=\"https://geekist.co/wp-content/uploads/2025/04/John_McCarthy_Stanford-e1744303038331.avif\" alt=\"A picture of John McCarthy, the creator of Lisp\" /></figure>\n\n\n<p>Alias: Father of AI<br />Langage: Lisp (1958)<br />Fav Operator: lambda<br />Special Abilities: Thinking decades ahead<br />Habitat: Stanford, whiteboards, parallel dimensions</p>\n\n\n\n<h3>What he was known for:</h3>\n<p>Hailed as the Father of AI. Yes, he coined the term <em>artificial intelligence</em> way back in <a href=\"https://legacy.cs.stanford.edu/memoriam/professor-john-mccarthy#:~:text=In%201958%2C%20John%20invented%20the,that%20programs%20meet%20their%20specifications\">1955</a>. Although not quite the version we’re panic-optimizing prompt tokens for today. </p>\n<p><strong>Wait. What? AI in 1955?</strong></p>\n<p>Yep. First computers: late 1940s.<br />McCarthy: AI, 1955. And not just that, he had a proposal for how to actually <em>build</em> it. </p>\n<p>Then came <strong>Lisp</strong> in 1958, a language purpose-built for AI (before AI was cool). Lisp wasn’t just inspired by math, <strong>it <em>was</em> math</strong>. McCarthy embedded <em>lambda calculus</em> directly into its syntax, making it one of the most important functional programming languages of all time. </p>\n<p>He also gave us <strong>Garbage Collection</strong> so programs could finally clean up after themselves, unlike most dev teams. </p>\n<p><em>Lisp even made it to space aboard a NASA craft. So yeah, it’s done more miles than your favourite JS framework.</em></p>\n<p>But McCarthy wasn’t done. In 1959, he proposed time-sharing. No, not the <a href=\"https://en.wikipedia.org/wiki/Timeshare\">property MLM craze</a>, but a radical idea where multiple users could interact with a single computer. That led to CTSS, then Multics, and eventually… Unix. </p>\n<p>Today’s servers? Containers? Cloud instances?<br />All direct descendants of that moment.</p>\n\n\n<h3>What he wasn’t known for:</h3>\n<p>Building things. </p>\n<p>Well. Besides Lisp. </p>\n<p>McCarthy was an idea man. He planted the seeds; others harvested the frameworks. </p>\n<p>And unlike the rockstar founders of tech lore, he wasn’t chasing the limelight. He kept so quiet, other people started getting credit for his ideas. </p>\n<p><em>Which, honestly, is kinda on-brand for someone who felt machines should do the thinking</em>…</p>\n\n\n\n\nDid you know?\n\n<p>McCarthy passed in 2011 (the same year as Steve Jobs and Dennis Ritchie.) Three titans. One quiet farewell to an era. </p>\n<p>And here’s another twist: before Lisp or AI, young John’s curiosity was lit by a banned Soviet children’s science book called <em>100,000 Whys</em>.</p>\n<p>His parents (pro-communist activists) got their hands on a translated version just for him. Of course they did.</p>\n<p>Imagine that: a banned book about science for kids… lighting the mind that would one day teach machines to reason.</p>\n\n\n\n\n\n<h3>Oral History Interview: John McCarthy</h3>\n<p><em>Recorded by the Computer History Museum (2007)</em></p>\n<figure>\n\n</figure>\n<p>Read the <a href=\"https://archive.computerhistory.org/resources/access/text/2012/10/102658149-05-01-acc.pdf\">full transcript</a></p>\n<blockquote>\n<p>The father of AI in his own words, on Lisp and the machines he hoped would think.<br /><em>If you only watch one interview on the roots of computing… this is it</em>.</p>\n</blockquote>\n\n\n\n\n\n\n\n\n<h2><a href=\"https://www.nokia.com/bell-labs/about/dennis-m-ritchie/\">Dennis MacAlistair Ritchie</a> – Creator of C, Co-Creator of Unix</h2>\n\n\n<figure><img src=\"https://geekist.co/wp-content/uploads/2025/04/Dennis_Ritchie_2011.avif\" alt=\"Dennis Ritchie in a suit, photographed in 2011.\" width=\"374\" height=\"481\" /><figcaption>Portrait of Dennis Ritchie, co-creator of Unix and the C programming language.</figcaption></figure>\n\n\n<p>Alias: dmr<br />Langage: C (1958)<br />Fav Symbol: *<br />Special Abilities: Making minimalism dangerous<br />Habitat: Bell Labs, quietly reshaping the world</p>\n\n\n\n<h3>What he was known for:</h3>\n<p>So he didn’t invent programming. <br />But he did invent the language that programming grew up in. That language? <strong>C</strong>. Created in 1972. </p>\n<p><em>If Lisp is Latin, C is Sanskrit.</em><br />(mind the poetry, not the fact) </p>\n<blockquote>\n<p>Unlike its modern cousins, C doesn’t hold your hand. It hands you a loaded pointer and says “good luck.”</p>\n</blockquote>\n<p>But before C, there was <strong>Unix</strong>, co-created in 1969 with Ken Thompson on a machine so small that would now fit in your electric toothbrush. </p>\n<p><strong>Unix: </strong>Linux? macOS? Windows kernels? Your phone? Your weighing machine?<br />All of it traces back to Ritchie. </p>\n<p>He also co-wrote <strong>“The C Programming Language”</strong> with Brian Kernighan, a book so influential, it’s known by initials alone: <strong>K&amp;R</strong>.<br />We’ll revisit that later when we talk about Thompson, but let’s just say: </p>\n<p><em>If CS had a holy book, this was Genesis.</em></p>\n\n\n<h3>What he wasn’t known for:</h3>\n<p>Publicity. </p>\n<p>Ritchie didn’t build companies. He didn’t give TED talks. He stayed at Bell Labs and kept writing software. </p>\n<p>When Steve Jobs died in 2011, the world mourned. When Ritchie died just days later, barely anyone noticed. <a href=\"https://www.wired.com/2011/10/thedennisritchieeffect/#:~:text=The%20tributes%20to%20Dennis%20Ritchie,But%20they%20should.\">Wired wrote about it</a>, but most people didn’t read it.</p>\n\n\n\n\nDid you know?\n\n<p>Ritchie never finished his PhD. He did start it, but never submitted his dissertation. Apparently, Harvard wasn’t going to give him one either. (Watch the video below for the details)</p>\n<p>He also had a thing for <strong>language</strong> in general. Not just computer languages.<br />Structure, brevity, meaning and that stuff mattered to him. You can feel it in C.</p>\n<p>His original Bell Labs homepage is still online, archived by Nokia: <a href=\"https://www.nokia.com/bell-labs/about/dennis-m-ritchie/\">https://www.nokia.com/bell-labs/about/dennis-m-ritchie/</a></p>\n\n\n\n\n\n<h3>Recreating Dennis Ritchie’s PhD Thesis</h3>\n<p><em>by Computerphile (2021)</em></p>\n<figure>\n\n</figure>\n<p>Discover the <a href=\"https://computerhistory.org/blog/discovering-dennis-ritchies-lost-dissertation/\">lost thesis</a> and the Ritchie family archive on the <a href=\"https://dmrthesis.net/\">tools used</a></p>\n<blockquote>\n<p>Professor Brailsford walks through Dennis Ritchie’s unfinished Harvard thesis: unearthing the machines, the source code, and the cultural silence around the man who quietly gave us Unix and C.</p>\n</blockquote>\n\n\n\n\n\n\n\n\n<h2><a href=\"https://en.wikipedia.org/wiki/Ken_Thompson\">Ken Lane Thompson</a> – Co-Creator of Unix, Inventor of B, Lover of Chess</h2>\n\n\n<figure><img src=\"https://geekist.co/wp-content/uploads/2025/04/Ken_Thompson_2019.avif\" alt=\"Ken Thompson seated in a chair, photographed in 2019.\" width=\"329\" height=\"349\" /><figcaption>Portrait of Ken Thompson, co-creator of Unix, seated in a casual setting.</figcaption></figure>\n\n\n<p>Alias: ken<br />Langage: B (precursor to C)<br />Fav Hobby: Writing software just to play chess<br />Special Abilities: Shipping systems before they’re fashionable<br />Habitat: Bell Labs, near a PDP</p>\n\n\n\n<h3>What he was known for:</h3>\n<p>Before C, there was B. And before Linux, there was <strong>Unix</strong>.<br />Ken Thompson co-created Unix in 1969, mostly to run games on a discarded PDP-7. You know, as one does. </p>\n<p>It started as a hobby, then turned into a full-blown operating system. He wrote the shell. The assembler. The I/O system and in typical Thompson fashion, he wrote it in 3 weeks! Because it just so happened that his wife and kids were out on holiday at the time. </p>\n<p>Later, he and Dennis Ritchie rewrote Unix in C and the rest is command-line history. </p>\n<p>He also built pipes: the thing that lets you string commands together and that led to <code>grep</code>, which led to a joke Kernighan once repeated onstage</p>\n<p><em>AT&amp;T ran a campaign with the slogan: ‘Reach out and <code>grep</code> someone.’</em></p>\n<p>Yes. They really printed that on a bumper sticker.</p>\n\n\n<h3>What he wasn’t known for:</h3>\n<p>Polish. </p>\n<p>Thompson didn’t care much for abstraction, he liked building things fast and raw. He just wanted it to run. He didn’t care much for ceremony, he just wanted to <em>get things done<strong>™</strong></em>. </p>\n<p>Not having any interest in being founder or CEO, not even a spokesperson. </p>\n<p><em>Not</em> causing international incidents,<em> more below</em>…</p>\n\n\n\n\nDid you know?\n\n<p>Ken Thompson once had his custom-built chess computer confiscated at the airport on his way to Moscow.</p>\n<p>Why? US authorities considered it a weapon!</p>\n<p>The machine, Belle, was so powerful for its time that it violated Cold War export laws.<br />The government seized it. Bell Labs had to pay a $600 fine to get it back.</p>\n<p>Thompson? He played more chess oh and yes – he <em>did</em> fly the MiG-29 while in Moscow.</p>\n\n\n\n\n\n<h3>Interview: Ken Thompson &amp; Brian Kernighan</h3>\n<p><em>by Vintage Computer Federation (2019)</em></p>\n<figure>\n\n</figure>\n<p>Read about the time he flew to Moscow to <a href=\"http://cs.bell-labs.co/who/ken/mig.html\">fly a MiG29</a></p>\n<blockquote>\n<p>They talk about Unix, grep, pipes, chess and how Thompson’s chess machine almost started a Cold War.</p>\n</blockquote>\n\n\n\n\n\n\n\n\n<h2><a href=\"https://en.wikipedia.org/wiki/Margaret_Hamilton_(software_engineer)\">Margaret Heafield Hamilton</a> – Apollo Code Commander, Software’s Unsung Engineer</h2>\n\n\n<figure><img src=\"https://geekist.co/wp-content/uploads/2025/04/500px-Margaret_Hamilton_-_restoration.avif\" alt=\"Margaret Hamilton standing beside printed Apollo guidance software code.\" width=\"500\" height=\"622\" /><figcaption>Historic photo of Margaret Hamilton beside the printed code that powered the Apollo mission.</figcaption></figure>\n\n\n<p>Alias: The First Software Engineer<br />Language: AGC Assembly<br />Fav Symbol: 1202<br />Special Abilities: Preventing mission failure<br />Habitat: MIT Instrumentation Lab, next to the lunar lander</p>\n\n\n\n<h3>What she was known for:</h3>\n<p>She led the team that wrote the <strong>onboard software for Apollo 11</strong>. The code that took humans to the moon (and brought them back.) </p>\n<p>When the <strong>1202 alarm</strong> flashed mid-descent, it wasn’t Mission Control that saved the day. It was her error-handling code that kicked in, cleared the noise, and let the mission proceed. </p>\n<p>No one panicked. Well. Except maybe the hardware. </p>\n<blockquote>\n<p>She didn’t write scripts. She wrote contingency plans. In assembly.</p>\n</blockquote>\n<p>She also coined the term <strong>software engineering</strong>. Because some folks on the NASA program didn’t even know what the term <em>software</em> even was! So she added the engineering hoping people would take it seriously. </p>\n<p>They didn’t. At first. Then she helped put humanity on the moon.</p>\n\n\n<h3>What she wasn’t known for:</h3>\n<p>Formal CS roots.. </p>\n<p>Yet she didn’t write code in garages. She did it in labs, leading teams, building fail-safes (and raising a child!) all at once. </p>\n<p>She didn’t “disrupt.” She delivered. And her code still stands as a masterclass in fault tolerance.</p>\n\n\n\n\nDid you know?\n\n<p>Before NASA, Hamilton worked in <strong>insurance</strong>.</p>\n<p>Her background in <strong>actuarial science</strong> trained her to expect failure and build systems that don’t.</p>\n<p>She let her daughter play with the mission simulator on weekends.<br />That simulator didn’t crash either.</p>\n<p>And yes, that towering stack of paper in the famous photo? It’s the full Apollo 11 source code. Printed. Line by line. By her team.</p>\n\n\n\n\n\n<h3>Interview: Software Pioneer Margaret Hamilton</h3>\n<p><em>by Christie’s | Apollo 11 Feature</em> (2019)</p>\n<figure>\n\n</figure>\n<p>Also watch Computer History Museum’s <a href=\"https://www.youtube.com/watch?v=6bVRytYSTEk\">Interview</a></p>\n<blockquote>\n<p>Margaret recounts how the Apollo software handled the “unhandleable” and why software engineering starts with expecting the worst.</p>\n</blockquote>\n\n\n\n\n\n\n\n\n<h2><a href=\"https://en.wikipedia.org/wiki/Alan_Kay\">Alan Curtis Kay</a> – Inventor of OOP, Architect of the Future That Wasn’t</h2>\n\n\n<figure><img src=\"https://geekist.co/wp-content/uploads/2025/04/Alan_Kay_and_the_prototype_of_the_Dynabook_3009206205.avif\" alt=\"Alan Kay holding a prototype of the Dynabook tablet.\" width=\"330\" height=\"219\" /><figcaption>Photograph of Alan Kay holding the early Dynabook concept device.</figcaption></figure>\n\n\n<p>Alias: Father of Personal Computing<br />Language: Smalltalk<br />Fav Concept: Message passing<br />Special Abilities: Inventing ideas 30 years too early<br />Habitat: Xerox PARC, teaching computers to teach kids</p>\n\n\n\n<h3>What he was known for:</h3>\n<p>He coined Object Oriented Programming. </p>\n<p><em>Then spent the next 30 years watching people do it wrong.</em></p>\n<p>OOP as we know it is not quite the version he had in mind. His vision didn’t have stuff like class hierarchies or abstract factories. So, not Java. In fact, Erlang is probably closer to Kay’s OOP than anything else is. </p>\n<p>He worked at Xerox PARC, where they <em>casually</em> invented: </p>\n<blockquote>\n<p>The GUI. The Mouse. Ethernet. And other-world, everything-OO.</p>\n</blockquote>\n<p>He also believed that children should learn programming. But not the boring syntax of it, more about exploration and play. </p>\n<p>That led to SmallTalk, Squeak and a bunch of other languages way before Scratch existed.</p>\n\n\n<h3>What he wasn’t known for:</h3>\n<p>Shipping products. </p>\n<p>He did build tools, tons of em’, but not for the market. He built them for minds. </p>\n<p>He wasn’t known for technical minimalism. Take Smalltalk. There’s nothing small about it. It’s a system, an environment and a language all rolled into one.</p>\n\n\n\n\nDid you know?\n\n<p>He nearly became a <strong>professional jazz guitarist</strong>, before turning to computing full-time.</p>\n<p>He built the Dynabook in the 1970s. A tablet. Before the internet even existed!</p>\n<p>His work danced between science fiction, music, and pedagogy (and confused the hell out of people who just wanted a faster compiler.)</p>\n\n\n\n\n\n<h3>Presentation by Alan Kay, “The Dynabook—Past Present and Future”</h3>\n<p><em>at ACM Conference </em>(1986)</p>\n<figure>\n\n</figure>\n<blockquote>\n<p>Alan Kay reflects on Dynabook, why GUI wasn’t the goal, and how the industry forgot what workstations were supposed to be.</p>\n<p>Also: dry humour, philosophical jabs and a masterclass in politely roasting everyone.</p>\n</blockquote>\n\n\n\n\n\n\n\n\n<h2>Special Mentions</h2>\n<ul>\n<li><strong><a href=\"https://en.wikipedia.org/wiki/Brian_Kernighan\">Brian Kernighan</a></strong><br />The “K” in <strong>K&amp;R C</strong> and the guy who made Unix readable. He didn’t invent C but he helped write its manual &amp; publish it to the world\n<p>Also: coined the term <strong>“Unix”</strong>, so technically, your terminal owes him a royalty. </p></li>\n<li><a href=\"https://en.wikipedia.org/wiki/J._C._R._Licklider\"><strong>J.C.R. Licklider</strong><br /></a>The original <strong>Internet prophet</strong>. Back in the ’60s, he imagined a world of connected computers, interactive graphics, and collaborative computing.\n<p>It was called the Intergalactic Computer Network, why didn’t that stick! </p></li>\n<li><strong><a href=\"https://en.wikipedia.org/wiki/Grace_Hopper\">Grace Hopper</a></strong><br />She gave us the first compiler, coined the term <strong>“debugging”</strong> (literally removing a moth) and believed code should read like English.\n<p>If you’ve used a high-level language, thank Grace for helping it exist. </p></li>\n<li><a href=\"https://en.wikipedia.org/wiki/Donald_Knuth\"><strong>Donald Knuth</strong><br /></a>Wrote <strong>The Art of Computer Programming</strong>, a book that’s 50% algorithm, 50% maths, and 100% flex.\n<p>Still not finished writing it. Still more prolific than all of us put together. </p></li>\n<li><a href=\"https://en.wikipedia.org/wiki/Ivan_Sutherland\"><strong>Ivan Sutherland</strong><br /></a>Built Sketchpad in 1963. A graphical interface before mice were even a thing.\n<p>It was so ahead of its time, it took another 30 years for UX designers to catch up.</p></li>\n</ul>\n<p>From Lisp to C and from moon landings to “time-sharing”. These weren’t just breakthroughs, hey were turning points in how we think about thinking. </p>\n<p>The legends we’ve met didn’t just write code, they redefined what code <em>was</em>, and what it <em>could be</em>. And they did all that without chasing trends. Without marketing or fame. All they cared about was to lay the tracks that the rest of us would ride for decades to come. </p>\n<p>Not all of them made it to the headlines, yet their work runs quietly and invisibly, under every <code>if</code>, every <code>fork</code> and every system reboot.</p>\n<hr />\n\n<h3>Who invented the term “Artificial Intelligence”?</h3>\n<p>John McCarthy did, back in 1955. His idea wasn’t today’s neural nets, but symbolic reasoning. Think logic professors, not toddlers with GPUs.</p>\n<h3>Why is Dennis Ritchie so important?</h3>\n<p>Because he built C and co-built Unix. That’s like inventing both the alphabet and the printing press. Your fridge, phone, and server still run on his legacy.</p>\n<h3>What did Ken Thompson invent?</h3>\n<p>Unix, the pipe operator, and B, which came before C. He also almost triggered a Cold War by taking a chess computer to Moscow.</p>\n<h3>Who coined “software engineering”?</h3>\n<p>Margaret Hamilton did while writing the Apollo mission software. People laughed. Her code didn’t crash.</p>\n<h3>What was Alan Kay’s real vision for OOP?</h3>\n<p>Messaging between objects, not inheritance trees. His dream was closer to Erlang than Java, and built for kids, not corporate frameworks.</p>\n\n<p></p>\n<p>John McCarthy did, back in 1955. His idea wasn’t today’s neural nets, but symbolic reasoning. Think logic professors, not toddlers with GPUs.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Why is Dennis Ritchie so important?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Because he built C and co-built Unix. That’s like inventing both the alphabet and the printing press. Your fridge, phone, and server still run on his legacy.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What did Ken Thompson invent?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Unix, the pipe operator, and B, which came before C. He also almost triggered a Cold War by taking a chess computer to Moscow.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Who coined “software engineering”?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Margaret Hamilton did while writing the Apollo mission software. People laughed. Her code didn’t crash.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What was Alan Kay’s real vision for OOP?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Messaging between objects, not inheritance trees. His dream was closer to Erlang than Java, and built for kids, not corporate frameworks.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 9,
                        "name": "The Geekery",
                        "slug": "the-geekery"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/grospel-of-croffee-the-parable-of-the-maidens-plea/",
            "url": "https://geekist.co/grospel-of-croffee-the-parable-of-the-maidens-plea/",
            "title": "Grospel of Croffee: The Parable of the Maiden’s Plea",
            "summary": "Oat milk? In keto?! A poetic tale of forbidden flavour, almond betrayal, and the sacred union of cream. The Grospel deepens.",
            "image": "https://img.geekist.co/wp-content/uploads/2025/03/the-book-of-brewvelations.avif",
            "date_published": "2025-03-23T11:38:47Z",
            "date_modified": "2026-11-14T01:22:45Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Fables for Food"
            ],
            "content_html": "<h2>Book of Brewvelations, Chapter 2</h2>\n<p>In the twilight of Keto Lent’s strict decree,<br />milk of the oat forbidden as flavours flee, </p>\n<p>There dwelled a woman of discipline and quiet rebellion.<br />The unshaken skeptic of the <em>Milk Substitute Deception.</em></p>\n<p>She had known many a milk that was but false,<br />yet endured countless cups of coffee pours. </p>\n<h3><strong>✨ <em>The Quest of the Cream</em></strong></h3>\n<p>Upon the break of every dawn, a ritual quite the same.<br />A cup. A pause. A plea. Another cry in vain. </p>\n<blockquote>\n<p>“Baby,” she whispered, voice like almond silk,<br />“If we can use two spoons of almond milk… can we not <em>try</em> oat instead?”</p>\n</blockquote>\n<p>And there he stood, Her Dravidian Knight.<br />Battle-scarred from kitchen war, with a tummy bulge – a show of might </p>\n<p>He looks into her eyes, he pauses, </p>\n<blockquote>\n<p><em>He stares</em></p>\n</blockquote>\n<p>he leans forward and says in but two words </p>\n<blockquote>\n<p><em>“<strong>Fruck Yes!</strong>”</em></p>\n</blockquote>\n<p>And so the maiden spoke, the silence broke, and thus; this Croffee quest awoke </p>\n<h3><strong>✨ <em>The Making of the Cream</em></strong></h3>\n<p>15 mils of heavy cream, <a href=\"https://geekist.co/croffee-anyone-or-kroffee-if-youre-so-inclined/\">like before</a>, his quest begins<br />30 mils of some oat gleam – sweet, but without the sin.<br />Treacherous is the alchemy that births milk worthy of a Queen </p>\n<p>A milk forbidden by the lords of macro law<br />But creamier and tastier than common lore </p>\n<p>Yet hidden in this balanced substance –<br />’tis lighter on sin than a nun’s conscience. </p>\n<h3><strong>✨ <em>The Moral of the Cream</em></strong></h3>\n<p>This was never just about coffee.<br />It was love. It was flavour.<br />It was the holy refusal to sip what tasted of water. </p>\n<p>The first taster.<br />The voice. The spark.<br />She whose plea did not just cream the cup – It crowned her,<br />unseen, unshaken: </p>\n<blockquote>\n<p><strong><em>First Lady of the Creamed Order.</em></strong></p>\n</blockquote>\n<p>And her Knight, he rides no longer for glory,<br />but for flavour.<br />For fat.<br />For Keto.<br /><strong>For story.</strong></p>\n<p><em>“Lo, for he did not chooseth the Croffee life. The Croffee life choseth him.”</em></p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 13,
                        "name": "Fables for Food",
                        "slug": "fables-for-food"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/croffee-anyone-or-kroffee-if-youre-so-inclined/",
            "url": "https://geekist.co/croffee-anyone-or-kroffee-if-youre-so-inclined/",
            "title": "Croffee anyone? Or Kroffee if you’re so inclined.",
            "summary": "Ditch almond milk! Discover Croffee, the ultimate keto hack. A hilarious take on keto coffee alternatives & plant-based myths.",
            "image": "https://img.geekist.co/wp-content/uploads/2025/03/free-photo-of-coffee-in-cup-in-overhead-view-1-scaled-e1744304142791.avif",
            "date_published": "2025-03-20T07:27:00Z",
            "date_modified": "2026-11-14T01:06:22Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Fables for Food"
            ],
            "content_html": "<h2>A keto tale of caffeine, coconut flashbacks, and divine dairy revelation.</h2>\n<blockquote>\n<p><em>And lo, the keto-faithful looked upon their overpriced almond milk and wept. But then, heavy cream was revealed unto them, and they knew it was good. And so Croffee was born, and the mornings were creamy and rich once more.</em></p>\n<p><em>Thus sayeth the UnHoly Grospel of Croffee.</em></p>\n</blockquote>\n\n\n<p>The Croffee meter</p>\n<h2>Make a Croffee</h2>\n<p>Start with a cup of coffee. Then tempt fate.</p>\n<strong>How many are we making?</strong>\n1\n\n\n\n\n\nHeavy cream15 ml\n<p></p>\n\nUnsweetened almond milk30 ml\n<p></p>\n\n\nCalories<strong>≈ 56</strong>\nTotal carbs<strong>≈ 0.8 g</strong>\n\n\nAll is well\n<p>Fifteen mils of cream. Thirty of almond milk. And peace was restored to the morning.</p>\n\n1 cup of prepared coffee\n<p>Cream and milk estimates only. Brands vary; 1 ml ≈ 1 g. <a href=\"https://www.ars.usda.gov/ARSUserFiles/80400525/Data/SR/SR28/reports/sr28fg01.pdf\">Cream</a> · <a href=\"https://www.dietaryguidelines.gov/sites/default/files/2024-09/DGAC-Meeting-5-Day-1-Slides.pdf\">Milk</a></p>\n<p><br />\n</p>\n<p>I think it’s becoming… No. Actually… it <em>has become</em> a standard now to ask ChatGPT or Gemini for answers. Simply because you get the fastest and yet probably the most relevant answers, shorter than if you were to Google it instead. </p>\n<p>So, like any normal person who woke up and decided to go keto for life, I asked ChatGPT if I could use milk in my coffee. </p>\n<p>“Nope,” it replied. “But almond milk is a great keto altern—” </p>\n<p>Good Lord, the rattling begins, not to mention the incessant need to bold every 3rd phrase of words it can. <em>I wish there were a switch that said ‘Short &amp; Sharp’ in ChatGPT.</em></p>\n<p>But I digress. Almond milk. So we check the stores, and gosh, the cartons were so <strong>damn expensive!?</strong></p>\n<p>Whatever. Almond milk it is then. If that’s what it took for keto. </p>\n<p>Two weeks into keto and stock runs out. No unsweetened almond milk anywhere! </p>\n<p>What!? </p>\n\n<p>💡</p>\n<p><em>For the record, I’m totally okay to have coffee without creamer. But my partner? She looks at a mug without creamer like it’s a hate crime. Not risking that kind of domestic unrest before 9am.</em> 🤪</p>\n\n<p>“Coconut milk!” says trusty ol’ ChatGPT this time (I’ll spare you the monologue). </p>\n<h3>Coconut Milk in Coffee?</h3>\n<p>If you grew up in Southeast Asia, or specifically in Singapore in the 80s and 90s, you’d have a distinct memory about coconut milk. Especially if you had to go down to the store to buy it. They didn’t sell coconut milk then. They sold desiccated coconut! </p>\n<p>Complete with a loud noisy machine out back and a bunch of coconut husks lying around where the friendly store owner sits on a stool and masterfully takes a crack at a coconut, feeds half onto the machine and out comes your pure white fluff, sealed in a bag en-route to Mom central, where the transformation begins.</p>\n<figure>\n\nhttps://www.youtube.com/watch?v=QDXdUUf18gM\n\n</figure>\n<h3>I loved it.</h3>\n<p>From grated coconut, to soaking it in water, to that final squeeze yielding a pure white liquid, ready to cook with. </p>\n<p>Now that you’ve got that picture in your head, try another one: </p>\n<p><em>Put that in your coffee?!</em></p>\n<p>(If you cringed a little, we’re on the same page. Otherwise, you should stop reading now. Close this tab and never come back!) </p>\n<p>Still here? Good. </p>\n<p>Okay, it doesn’t work that way anymore. The fluff is gone (except if you count the fancy marketing bits on the cartons), it’s now just coconut milk, unsweetened, low in carbs, perfectly drinkable. On that note, I have not seen a single picture of a coconut on the milk cartons like ever! They’re all over the coconut water cartons but never on the milk cartons. </p>\n<p>That’s something to think about, huh? </p>\n<p>Anyway, here’s the thing. Almond milk isn’t really Keto. It’s plant-based. That’s why it’s everywhere. Keto just borrowed it from the vegan tribe. </p>\n<p>But what keto is really about is fats, not so much where it’s sourced from. Almonds? That’s barely trying. Try chewing through a bowl of them and tell me that’s the fat bomb we’re all looking for. </p>\n<p>Anyway, I gave up on the milk section altogether and went to get some cheese. And then I stumbled on heavy cream. Wait, why the hell not? Why not just use fat directly? </p>\n<p>And why not indeed. As it turns out, heavy cream is definitely usable. It tastes awesome and you don’t have to use much at all. </p>\n<p>I’ve used 15ml (1 tbsp) of heavy cream (30-35%+ fat), and it was magical! Velvety, smooth, just the right kind of <em>decadent</em> to make you forget you’re technically dieting. </p>\n<p>And if you have a large mug to fill – or you’re truly missing some nutty undertones – you can add another 30ml (2 tbsps) of almond milk to it. Trust me, you’ll never look at almond milk the same way again. </p>\n<p>Close your eyes, pretend really hard, and if you’re lucky, it’ll taste like oat milk. </p>\n<h4><em>I wish</em></h4>\n<p>ChatGPT finally got something right though. Heavy Cream wins! I do that every morning now. And it’s the cheapest keto-friendly latte you can get. </p>\n<p>If we have Zoodles, why the hell can’t we have <strong>Croffee</strong>? </p>\n<p>Go forth, my fellow Geeks; spread the good Croffee word. Have some while you’re at it, and come right back here and share what it was like. </p>\n<p>And if anyone tries to stop you, just whisper: <em>“It is written… in the Grospel.”</em></p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 13,
                        "name": "Fables for Food",
                        "slug": "fables-for-food"
                    }
                ],
                "recipe": {
                    "@context": "https://schema.org",
                    "@type": "Recipe",
                    "@id": "https://geekist.co/croffee-anyone-or-kroffee-if-youre-so-inclined/#recipe",
                    "mainEntityOfPage": "https://geekist.co/croffee-anyone-or-kroffee-if-youre-so-inclined/",
                    "name": "Make a Croffee",
                    "recipeYield": "1",
                    "recipeIngredient": [
                        "1 cup of prepared coffee",
                        "Heavy cream: 15 ml",
                        "Unsweetened almond milk: 30 ml"
                    ],
                    "image": "https://img.geekist.co/wp-content/uploads/2025/03/free-photo-of-coffee-in-cup-in-overhead-view-1-scaled-e1744304142791.avif",
                    "keywords": "keto",
                    "recipeInstructions": [
                        {
                            "@type": "HowToStep",
                            "text": "Start with a cup of coffee. Then tempt fate."
                        }
                    ],
                    "author": {
                        "@type": "Person",
                        "name": "GuruGeek"
                    },
                    "datePublished": "2025-03-20T07:27:00Z"
                },
                "recipe_details": {
                    "ingredients": [
                        {
                            "id": "coffee",
                            "label": "cup of prepared coffee",
                            "mode": "serving-base"
                        },
                        {
                            "id": "cream",
                            "label": "Heavy cream",
                            "mode": "adjustable"
                        },
                        {
                            "id": "milk",
                            "label": "Unsweetened almond milk",
                            "mode": "adjustable"
                        }
                    ],
                    "dietary_classification": "keto",
                    "nutrition": {
                        "calories": {
                            "scope": "cream-and-milk-only",
                            "estimated": true,
                            "complete": false,
                            "provenance": {
                                "description": "Cream and milk estimates only. Brands vary; 1 ml ≈ 1 g. Cream · Milk",
                                "status": "inherited-unverified"
                            }
                        },
                        "carbs": {
                            "scope": "cream-and-milk-only",
                            "estimated": true,
                            "complete": false,
                            "provenance": {
                                "description": "Cream and milk estimates only. Brands vary; 1 ml ≈ 1 g. Cream · Milk",
                                "status": "inherited-unverified"
                            }
                        }
                    }
                },
                "rich_media": [
                    {
                        "title": "Make a Croffee",
                        "url": "https://geekist.co/croffee-anyone-or-kroffee-if-youre-so-inclined/",
                        "has_controls": true,
                        "description": "Start with a cup of coffee. Then tempt fate."
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/we-broke-the-web-can-webo-fix-it/",
            "url": "https://geekist.co/we-broke-the-web-can-webo-fix-it/",
            "title": "We Broke the Web. Now Comes the Rollback-olution™",
            "summary": "The web has come full circle. After 25 years of over-engineering, WebO+ revives the best of Web1, Web2, and Web3 - minus the complexity.",
            "image": "https://img.geekist.co/wp-content/uploads/2025/03/72ba3739-cecf-4fe6-8c7e-3490420b3885.avif",
            "date_published": "2025-03-17T04:25:22Z",
            "date_modified": "2026-02-04T21:25:30Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Geekery"
            ],
            "content_html": "<h2>It took us a quarter of a century to realize we weren’t looking for Web4.</h2>\n<p>Let’s be honest. The Web has gone through so many self-imposed revolutions, it looks a lot more like a badly managed startup. Pivoting. Perpetually. Forever rewriting its mission statement. But as a side-effect, it tends to generate buzzwords. A ton of them. So here’s another one: </p>\n<p><strong><em>WebO+</em></strong></p>\n<p>But let’s start at the beginning. We had Web1.0 – which wasn’t a term that was ever actually coined – but was known as the <em>read-only web</em>. Then Web2.0 came with all its interactivity and API-driven web apps. And finally, we met Web3. What’s next? </p>\n<p>I’d say that after 25 years of (re)inventing complexity, we don’t need Web4. We just need to fix Web2.0. But before we talk about the fix, let’s talk about how we broke it. </p>\n<h2>The Web. What Went Wrong?</h2>\n<p>It began as a beautifully simple thing. Somewhere out there, there was a computer that held a ton of webpages. And then, there were tons of computers – with tons of webpages – ready to serve any one who requested them. </p>\n<p>You would pick your favorite browser application (probably Netscape) and fire it up. And then you’d be greeted with AltaVista (depending on the year, it might even be Yahoo) and then you’d type in a search and Boom! </p>\n<p>But it wasn’t just a tool. It was a cultural moment. This old Yahoo! ad captures the vibe perfectly. </p>\n<p>%[https://www.youtube.com/watch?v=RguxFYvBFiE] </p>\n<p><em>This was one of my absolute favourites ads at the time!</em></p>\n<p>But something wasn’t right. The web was… boring. Sure, you could read stuff. But why couldn’t we have the same interactivity we had in games? Why couldn’t the Web feel alive? </p>\n<p>And why not? That’s when Web2.0 was born. </p>\n<h2>Web2.0: The Social &amp; API-Driven Web (Mid-2000s – 2020s)</h2>\n<p>Suddenly, web pages transformed from regular Wikipedia looking articles to full blown Web Applications. </p>\n<blockquote>\n<p>The term <strong>Web Application</strong> actually felt triumphant. No serious programmer at the time thought much about Web Developers. No one would dare call us <strong>Engineers</strong>. Very few even wanted to call us <strong>Programmers.</strong> You could almost hear them mutter under their breath: </p>\n<p>“What? JavaScript? PHP? Ewww…” </p>\n<p>Many thought we were “Java” fan boys and girls. Meanwhile, some of us made their salaries look cute.</p>\n</blockquote>\n<p>Then came the <strong>Buzzword Bonanza™</strong> – AJAX, JSONP, OAuth. Suddenly, the <strong>FrontEnd Engineer</strong> (oops, <em>developer</em>) was born. And just like that, frameworks exploded. Your Yahoo! wasn’t Yahoo anymore – literally. </p>\n<p>You could suddenly do more. You could talk! Err… chat! And guess what else? </p>\n<p><em>You could totally click on a Button and you wouldn’t have to wait a week for the page to reload!</em></p>\n<p>And it didn’t stop there. Buttons changed color, shapes moved, hover effects responded before you even clicked. The web came alive. Stuff glowed. Things got bolder. Move your mouse, and… something popped out! </p>\n<p><em>Oh, and in case you were wondering, yes, that’s totally where popups came from. At least until we invented pop-up blockers to fight back.</em></p>\n<p>It was a game changer: Skeuomorphic design, Zoomable User Interfaces (<a href=\"https://geekist.co/building-a-zoomable-ui-with-meteor-js-greensock/\">remember this?</a>) and of course, the rise of Social Media. </p>\n<p>The web became <strong>Live</strong>. <strong>Fun</strong>. <strong><em>Interactive</em></strong>. </p>\n<p>But beyond the flashy buttons, glowing elements and real-time interactions, something bigger was happening… </p>\n<p>Browsers weren’t just rendering cool effects; they were offloading serious computation from our servers to our users’ machines. Instead of relying on expensive, multi-core, memory-filled servers, we realized that every single user already had compute power at their fingertips. </p>\n<p>We went from the browser rendering pages to the browser rendering entire applications, <strong>full-blown, desktop-grade software.</strong> The browser became the new runtime; an OS inside an OS, shouldering the burden once meant for the backend. </p>\n<p><em>At this point, people were finally calling us Engineers. Well… no. We were calling ourselves Engineers. And loudly. And no one was arguing with us.</em></p>\n<p>It was a brilliant move. </p>\n<p>Until it wasn’t. </p>\n<h3>SEO took a NoseDive</h3>\n<p>Turns out, search engines didn’t sign up for this full-stack revolution. Google could read JavaScript, sure. But understand it? Not so much. Beyond that, performance tanked. I’m sure you’re saying, <em>“But wait. No it didn’t!”</em>. It did, but you probably didn’t feel it because we were graciously met with so much more compute power, much more than we ever did before </p>\n<p>Developers were shipping megabytes of JavaScript just to render something as simple as a list. What once took a single HTML file now required hydration, client-side loops, and API calls. It suddenly took tons of JS to make anything functional. In turn, that created new problems. Latency suffered. We had to figure out how to pre-render out static pages (remember PhantomJS anybody?). </p>\n<p>Then came React. </p>\n<p>Then came the first hydration issues. </p>\n<p>Then came Hydra. <s>Cut off one head, two shall take its place</s>… Sorry. Hydration Hell.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/hydra-marvel.avif\" alt=\"Red Skull from Marvel’s Captain America saying “Cut off one head, two more shall take its place”\" width=\"640\" height=\"296\" /><figcaption>Hydration bugs in React be like…</figcaption></figure>\n<p>And if that wasn’t enough, something even worse was happening behind the scenes. While we were drowning in hydration hell, large organisations were quietly harvesting our data – and selling it. How? They made shiny cool things we could use for free and made us accept terms no one bothered to read. </p>\n<p>The cracks weren’t just showing, they were splitting wide open. The web had become a bloated, exploitative mess, and no one knew where to start fixing it.. We needed something new… </p>\n<h2>Web3. The Decentralized, Crypto-Powered Web (2020s – Now)</h2>\n<p>Notice something? We got cooler. We dropped the <code>.0</code>. Just Web3. Clean. Minimalist. Sleek.</p>\n<p>Oh dear God, no. Not even close. </p>\n<p>At least we got new buzzwords! <em>Blockchain. Crypto. Smart Contracts. Decentralization. Tokens. Mining. NFTs.</em> You get the idea. Web3 came in hot, promising to fix the internet by removing central control and letting users own their data. And in many ways, it delivered – for finance, supply chains, trustless transactions and so much more. </p>\n<p>But that didn’t actually fix any of our Web2.0 architectural problems, no sir. In fact, people started slapping blockchain on everything. Suddenly, blogs needed tokens, APIs required smart contracts and even basic web apps were being rebuilt with decentralized infrastructure. So instead, it just added more to account for. </p>\n<p>At this point, we had truly outdone ourselves. In pushing the boundaries of technology, we didn’t just innovate,<em>we over-engineered everything.</em> And in the process, we gave an old word a brand-new meaning: </p>\n<p><em>Overkill.</em></p>\n<p>But. Finally. After years of over-complication, we hit The Great Reset. </p>\n<h2>WebO+. The ultimate Rollback-olution™ (2020s – Now)</h2>\n<p>It’s absurd how we’ve come full circle. We began with server-side rendering because that’s all we had. Then JavaScript evolved, and we pushed more work onto the client. Then came Internet Explorer, which we shall not speak of. Eventually, we decided that sending full HTML pages was too expensive – so we switched to sending JSON. Then, JSON was too big, so we optimized it with better compression. Then, in our pursuit of the ‘pristine’ server, we decided it should only speak one language – JSON (or protobuf) – while the client handled the heavy lifting. </p>\n<p>Then reality struck. We still needed server-side rendering for SEO, accessibility and performance. But instead of admitting the mistake, we Frankenstein’d a solution – client-based SSR. And after years of jumping through hoops, we arrived back where we started: <strong>Server-side Rendering.</strong></p>\n<p>The simple truth hit us: The <strong>original web had it right all along</strong>. We didn’t need a new paradigm. We needed to stop over-engineering everything. </p>\n<p>WebO+ isn’t about going backwards – it’s about correcting 25 years of misdirection. It takes the best parts of Web1, Web2, and Web3 and cuts out the nonsense.</p>\n<figure>\n<table>\n<thead>\n<tr>\n<th>Feature</th>\n<th>Web1</th>\n<th>Web2</th>\n<th>Web3</th>\n<th>WebO+</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Server-side HTML</td>\n<td>Yes</td>\n<td>Partial</td>\n<td>No</td>\n<td>Yes</td>\n</tr>\n<tr>\n<td>UI Rendering APIs</td>\n<td>No</td>\n<td>Yes</td>\n<td>Yes</td>\n<td>Optional</td>\n</tr>\n<tr>\n<td>SEO-Friendly</td>\n<td>Yes</td>\n<td>Partial</td>\n<td>Partial</td>\n<td>Yes</td>\n</tr>\n<tr>\n<td>Perf (Page Load)</td>\n<td>Yes</td>\n<td>Partial</td>\n<td>Heavy</td>\n<td>Yes</td>\n</tr>\n<tr>\n<td>Client JS</td>\n<td>No</td>\n<td>Yes</td>\n<td>Yes (dApps)</td>\n<td>Optional</td>\n</tr>\n</tbody>\n</table>\n</figure>\n<blockquote>\n<p>WebO+ is what Web1 would have been, if we had today’s hardware, compression, and smarter rendering.</p>\n</blockquote>\n<h3>What it does right.</h3>\n<p><em>Now this is assuming you still need a server to make API calls and you’re not generating static pages and serving them out of CDN.</em></p>\n<p>For starters, we’re back to the early 2000s where server-rendered, SEO-friendly pagination still matters, even though client-side tricks like pull-to-refresh make browsing smoother. </p>\n<p>But now, servers are more powerful, and compression is faster than ever. Instead of juggling JSON responses and complex client-side loops, the server just sends fully rendered HTML, and the browser drops it straight into the DOM. No extra processing, no unnecessary hydration, just fast, direct rendering. </p>\n<p>Yes, you can still use JS/TS on the backend, and yes, you can still reuse the same logic for both server-side and client-side rendering. But some tasks like click handlers and state changes must stay client-side. </p>\n<p>The difference? You don’t need to structure two separate component types anymore. Just sprinkle in client-side functionality where needed. </p>\n<p>Some frameworks, like Svelte, go further by allowing client-side logic within the same file, making the distinction seamless. </p>\n<p>And it’s not just Svelte. SSR is back across the board. Frameworks like Laravel, Next, Nuxt and SvelteKit have brought server rendering back into the mainstream, making it practical again: lean servers, fully rendered pages, instant loads. </p>\n<p>React now embraces SSR with Next.js and React Server Components (RSC), though hydration issues still make it more complex than traditional SSR. </p>\n<h3>A Small Aside, What Inspired this Article?</h3>\n<p>You see, I saw a video called <em>“Next.js Best Practices You can’t ignore”</em> and the first thing the author said was something along the lines of “Dude, are you using Page Router? Stop. Use App Router.” but he didn’t do much of a job elaborating. So curiously, I asked ChatGPT about it and this is the gist of what I got back: </p>\n<p><em>“Oh, App Router is like how we built websites in the late 90s and early 2000s.”</em></p>\n<p>And then. Something inside me broke. </p>\n<p>So I forced my partner to sit down and listen to me rant. I went on and on and finally ended with telling her what I would say to Devs at the time: </p>\n<blockquote>\n<p><em>It doesn’t matter if the server-side code is pristine gold if your client-side code looks like Medusa just woke up from a freggin’ hangover.</em></p>\n</blockquote>\n<p>She laughs. That’s something I guess. And the ranting made me feel better so before I go, there are some more things that need to be said. </p>\n<p>Frontend Development pushed browsers so damn far that they became full-fledged operating systems. _Chromebook anyone?_ </p>\n<p>It pushed GPUs to their limits. It pushed JS engines to the point where V8 became so powerful that it didn’t just optimize web performance – it gave birth to entire server-side ecosystems like Node.js &amp; Deno. (Yep. The same dude started both) </p>\n<p>Meanwhile, server-side computing kept getting stronger. But most of these BFFs were just sitting there, idling. So the push came from the frontend: “Wake up, server. We need you to do more.” </p>\n<p>We’re finally waking up to the fact that frontend wasn’t supposed to be doing all the heavy lifting. </p>\n<p>Finally. We are shifting back. So I’d say… </p>\n<ul>\n<li>Goodbye hydration hell. </li>\n<li>Goodbye unnecessary client-side API calls. </li>\n<li>Goodbye shipping 5MB of JavaScript just to render a list.</li>\n</ul>\n<p>And then I’ll say… </p>\n<ul>\n<li>Welcome back, server-rendered HTML. </li>\n<li>Welcome back, pre-rendered content. </li>\n<li>Welcome back universal UIs</li>\n</ul>\n<h3>🔥 Welcome to WebO+.</h3>\n<hr />\n\n<h3>What is WebO+?</h3>\n<p>WebO+ stands for <em>Web Original Plus™</em>, a tongue-in-cheek term for a return to simple, server-rendered, SEO-friendly websites with modern performance, compression, and just enough JavaScript to get by. Think Web1, upgraded for today.</p>\n<h3>Why did frontend take over backend responsibilities?</h3>\n<p>Because JavaScript frameworks evolved faster than server-side rendering techniques, and client machines got powerful enough to run full applications. We leaned on the browser so hard, it became an OS inside an OS.</p>\n<h3>Why is hydration a problem in web development?</h3>\n<p>Hydration refers to reattaching interactivity to server-rendered HTML on the client. It’s often slow, complex, and redundant, especially when the same logic had to run twice: once server-side, once client-side.</p>\n<h3>Is Web3 a replacement for Web2?</h3>\n<p>No. Web3 adds decentralization, crypto, and token-based models, but it doesn’t solve core architectural issues from Web2; like SEO, SSR, or performance. In fact, it often adds more layers of complexity.</p>\n<h3>What’s the best modern stack for WebO+?</h3>\n<p>Frameworks like SvelteKit, Laravel, and Next.js (if used right) make WebO+ possible by combining SSR with smart client-side interactivity. Bonus points if you keep JS optional and HTML sacred.</p>\n\n<p></p>\n<p>WebO+ stands for <em>Web Original Plus™</em>, a tongue-in-cheek term for a return to simple, server-rendered, SEO-friendly websites with modern performance, compression, and just enough JavaScript to get by. Think Web1, upgraded for today.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Why did frontend take over backend responsibilities?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Because JavaScript frameworks evolved faster than server-side rendering techniques, and client machines got powerful enough to run full applications. We leaned on the browser so hard, it became an OS inside an OS.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Why is hydration a problem in web development?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Hydration refers to reattaching interactivity to server-rendered HTML on the client. It’s often slow, complex, and redundant, especially when the same logic had to run twice: once server-side, once client-side.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Is Web3 a replacement for Web2?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>No. Web3 adds decentralization, crypto, and token-based models, but it doesn’t solve core architectural issues from Web2; like SEO, SSR, or performance. In fact, it often adds more layers of complexity.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What’s the best modern stack for WebO+?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Frameworks like SvelteKit, Laravel, and Next.js (if used right) make WebO+ possible by combining SSR with smart client-side interactivity. Bonus points if you keep JS optional and HTML sacred.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 9,
                        "name": "The Geekery",
                        "slug": "the-geekery"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/why-your-tech-stack-is-overrated-and-what-actually-matters/",
            "url": "https://geekist.co/why-your-tech-stack-is-overrated-and-what-actually-matters/",
            "title": "Why Your Tech Stack is Overrated (And What Actually Matters)",
            "summary": "The real challenge in 2025 isn't React Native vs. Native, it's building software that lasts. Here's what truly matters for future-proof development.",
            "image": "https://img.geekist.co/wp-content/uploads/why-your-tech-stack-is-overrated-and-what-actually-matters.avif",
            "date_published": "2025-03-07T18:22:50Z",
            "date_modified": "2026-02-04T21:25:30Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Thinking in Code",
                "Tame the Tech"
            ],
            "content_html": "<h2>Lessons from 2017 to 2025</h2>\n<h3>The Debate That Didn’t Matter</h3>\n<p>In 2017, everyone – including yours truly – was passionately caught up debating the virtues of <a href=\"https://www.inovex.de/de/blog/react-native-vs-native-development/\">React Native versus going fully Native</a>. I even penned a fiery rant about it <a href=\"https://geekist.co/hybrid-vs-native/\">here</a>, convinced I’d cracked the code myself on app development. </p>\n<p>But looking back now, it feels like we were totally arguing about who had the cooler shoes in primary school which as fun as it was at the time, was ultimately meaningless. The truth is, it wasn’t frameworks or flashy tech that determined success; it was something <em>far more mundane</em>. </p>\n<p>Real success hinged on fundamentals like <a href=\"https://www.archdaily.com/904882/understanding-and-using-architectural-scales\">choosing an architecture</a> that <a href=\"https://aosabook.org/en/v2/distsys.html\">scales</a>, keeping logic decoupled and resisting those tempting short-term optimisations that always seem clever until you’re buried under technical debt months later. </p>\n<p>Turns out, frameworks come and go, but good architecture? That sticks around. </p>\n<p><strong>What Actually Matters for Future-Proof Software</strong></p>\n<p>If I could distill the years between 2017 and today into a single insight, it’d be this: </p>\n<blockquote>\n<p>Frameworks fade; the way you structure your software endures.</p>\n</blockquote>\n<h3><strong>AI and Automation Changed Everything</strong></h3>\n<p>At the time, having <a href=\"https://naturaily.com/blog/react-native-things-to-know\">JavaScript run everywhere was groundbreaking</a>. Today, AI and automation have transformed the landscape completely. Debugging, for example, used to mean long nights hunting obscure errors. Now, AI-assisted tools help pinpoint common issues in minutes, making troubleshooting more efficient – but its far from perfect. </p>\n<p>Automated CI/CD pipelines have made updates effortless across every platform, no longer making deployment feel like a stressful space launch. Even components and tests can now be generated with AI, freeing developers from tedious, repetitive tasks to focus on higher-level design. </p>\n<p>The future doesn’t care if your stack is cool; it cares how quickly and reliably you can adapt. </p>\n<p><strong>Security Finally Gets Its Due</strong></p>\n<p>Security was still a hot topic then too but not many knew what exactly to do beyond the understood norms and it often felt like an afterthought – we built fast and hoped nothing was vulnerable. Today, security isn’t optional; it’s essential from day one. </p>\n<p>Modern threats, like AI-powered cyberattacks and vulnerabilities hidden deep in supply chains, weren’t even on our radar back then. <a href=\"https://developers.google.com/solutions/content-driven/data-storage/regulatory-compliance\">Regulatory compliance</a> now also demands that security be baked into the foundation of every application. Building resilient software isn’t about paranoia, (well it is slightly) it’s about responsibility and longevity. </p>\n<h3>AI in Coding went from Novelty to Necessity (Almost)</h3>\n<p><a href=\"https://siliconangle.com/2017/08/15/a-cloud-guru-uses-lambda-and-api-gateway-to-build-serverless-company-awssummit/\">AWS Lambda</a> and serverless computing? Pure Revolution. Today we have coding platforms that generate entire apps for you (It can, but the stuff it generates is quite rudimentary). I have never once thought (nor will I believe) that coding can be completely replaced by AI – yet! </p>\n<p>The reason I say this is because I have spent much more time debugging AI-generated code than I would my own. To start with, I wouldn’t have written many things the way it would, having learnt so much over the years, I structure things wildly different from the common scenarios that LLMs are trained with. But while AI-generated code still has a long way to go, its real value emerges elsewhere… </p>\n\n<figure><img src=\"https://geekist.co/wp-content/uploads/f67a9ecd-8ff9-4fb7-8a7d-dfd7763f5aa5-800x421.avif\" alt=\"Diagram showing AI-assisted code generation, debugging, and human strategy review, with annotations highlighting review and architectural importance\" width=\"800\" height=\"421\" /><figcaption>It’s not about the tools, it’s about what you do after the code is generated.</figcaption></figure>\n\n<p>Today, we have low-code and no-code tools that can generate prototypes in hours instead of weeks. And it is things like this that make AI shine. The heavy lifting, the project starters, the strategic overview. After that it becomes a companion at best. This converts developers into strategic architects, crafting scalable systems rather than wrestling with mundane details. If anything, these tools elevated our roles by freeing us from the busy work. </p>\n<p>Personally, I prefer using AI to handle specific parts of the code where structure or organisation can be enhanced, rather than relying on it entirely </p>\n<p>I’d say LLM generated code has a long way to go and even if it gets there, you’d still need humans in the mix – and by definition – these humans are likely coders themselves because who else is going to debug AI’s mistakes? </p>\n<p>I am hopeful though, and I am really looking forward to it because that means I can focus on things that really matter and leave the grunt-work to something else. </p>\n\n<p>💡 </p>\n<p>I’ll write about some of the tools I have reviewed in an upcoming article, giving you a better understanding on what’s out there now and how it can complement your workflow.</p>\n\n<h3>Microservices vs. Monoliths: Déjà Vu All Over Again</h3>\n<p>Just as 2017 had its React Native drama, today’s hot debate is “microservices or monolith?” It’s tempting to pick a side and argue until you’re blue in the face but here’s what history has taught us: </p>\n<blockquote>\n<p>Neither one is a silver bullet.</p>\n</blockquote>\n<p>Sure, a monolith might get your MVP out the door faster, but as complexity grows, it starts to feel like lugging around an increasingly heavy backpack. Microservices offer flexibility and modularity, but demand strict discipline to keep complexity in check. </p>\n<p><em>The trick is to build a monolith with the future in mind. Code structured around isolated business units or features stands the test of time.</em></p>\n<p>(Crap! That rhymed!) </p>\n<p>Practically speaking, your code should communicate through clearly defined interfaces – a common protocol if you will. This could be REST, GraphQL, or an event-driven architecture, depending heavily on your infrastructure, team expertise and available resources </p>\n<p>If each feature-driven section of your codebase can live and operate independently within your stack, transitioning from a monolithic structure to a standalone microservice becomes a surprisingly smooth process. </p>\n<p><strong>The Real Lesson is that The Framework Was Never the Point</strong></p>\n<p>I wasted way too many hours back then debating the merits of frameworks, only to realise years later how pointless it was. Winning arguments didn’t make software any better; understanding longevity did. </p>\n<p>Since then, I’ve been fortunate to lead numerous mobile development projects. One highlight was at Prudential, where we built federated React Native components used across various markets. The framework itself? Just a means, never the end. </p>\n<h3>A Final Thought, a Look Beyond Today’s Trends</h3>\n<p>When picking your tech stack today, don’t ask yourself, “Will this still be cool in 2025?” Instead, challenge yourself with, “Will this still be relevant in 2030?” If your answer depends heavily on a particular framework, you might already be falling behind. </p>\n<p>Remember, tech stacks are transient, but good architecture and thoughtful design decisions are timeless. </p>\n<hr />\n\n<h3>Is React Native still worth learning in 2025?</h3>\n<p>React Native is still viable for cross-platform apps, especially if you’re already invested in React. But don’t confuse learning it with betting your architecture on it. The framework helps, but clean abstractions matter more.</p>\n<h3>Will AI replace developers?</h3>\n<p>Not anytime soon. AI is great at boilerplate, scaffolding, and suggestions, but it lacks domain context, foresight, and architecture intuition. You still need a developer to shape systems, not just write syntax.</p>\n<h3>What’s the best way to future-proof your software?</h3>\n<p>Structure your app around isolated business domains, define clear interfaces, and avoid tight coupling. Whether you’re in a monolith or micro-services, this approach lets you adapt without rewrites.</p>\n<h3>How has DevOps changed since 2017?</h3>\n<p>CI/CD has become nearly frictionless thanks to mature pipelines, better tooling, and AI assistance. Deployments that once felt like NASA launches are now just merges. But automation has’t replaced judgement, it amplifies it.</p>\n<h3>What matters more than frameworks?</h3>\n<p>Design. Architecture. Separation of concerns. Your framework will age, your decisions won’t. Pick tech that supports your goals but never let it define them.</p>\n\n<p></p>\n<p>React Native is still viable for cross-platform apps, especially if you’re already invested in React. But don’t confuse learning it with betting your architecture on it. The framework helps, but clean abstractions matter more.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Will AI replace developers?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Not anytime soon. AI is great at boilerplate, scaffolding, and suggestions, but it lacks domain context, foresight, and architecture intuition. You still need a developer to shape systems, not just write syntax.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What’s the best way to future-proof your software?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Structure your app around isolated business domains, define clear interfaces, and avoid tight coupling. Whether you’re in a monolith or micro-services, this approach lets you adapt without rewrites.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How has DevOps changed since 2017?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>CI/CD has become nearly frictionless thanks to mature pipelines, better tooling, and AI assistance. Deployments that once felt like NASA launches are now just merges. But automation has’t replaced judgement, it amplifies it.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What matters more than frameworks?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Design. Architecture. Separation of concerns. Your framework will age, your decisions won’t. Pick tech that supports your goals but never let it define them.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 10,
                        "name": "Thinking in Code",
                        "slug": "thinking-in-code"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/sync-your-music-and-visuals-together-to-captivate-your-audience/",
            "url": "https://geekist.co/sync-your-music-and-visuals-together-to-captivate-your-audience/",
            "title": "Sync Music & Visuals Together to Captivate your Audience",
            "summary": "A breakdown of how precise timing between music and visuals enhances engagement, with a simple BPM calculator to keep everything in sync.",
            "image": "https://img.geekist.co/wp-content/uploads/2025/04/A-clean-and-modern-digital-artwork-depicting-a-structured-timeline-for-synchronizing-music-and-visuals.avif",
            "date_published": "2025-02-08T18:49:15Z",
            "date_modified": "2026-11-14T02:17:57Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Mind the Music",
                "The Geekery"
            ],
            "content_html": "<p>Imagine watching a video where every transition, every slide, every moment feels <em>effortless</em>. The visuals glide smoothly, perfectly timed to the rhythm of the music. </p>\n<p>In <a href=\"https://geekist.co/how-to-stay-on-beat-and-out-of-bars-musically-speaking/\"><em>How to Stay on Beat and Out of Bars (Musically Speaking)</em></a>, I explored why bars and time signatures matter in music. But what if I told you that <em>knowing your bars</em> also makes you better at video editing? </p>\n<p>Sure, visuals are everything in a video but nothing screams professionalism like how well it syncs to the music, or the rhythm – and that led to a video that garnered over <a href=\"https://www.tiktok.com/@thegeekist/video/7455196169564622087?is_from_webapp=1&amp;sender_device=pc&amp;web_id=7465721843812894226\">1.5k views on Tiktok</a>! </p>\n<h2>The Psychology of Synchronization</h2>\n<p>If you’ve ever watched a slideshow where slides seem to change at random, or a reel where the music <em>almost</em> syncs but is just a fraction off, you know the feeling, it’s like an itch you can’t scratch. This isn’t just an aesthetic issue. Studies on audiovisual synchrony show that well-timed transitions <strong>increase engagement and perceived quality</strong>. </p>\n<p>That’s because our brains naturally seek patterns, a concept explained by <a href=\"https://www.verywellmind.com/gestalt-laws-of-perceptual-organization-2795835\">Gestalt psychology’s principles of grouping and continuity</a>. </p>\n<p>When you watch a presentation-style video that’s <em>out of sync</em>, you either:<br />1. Power through because the content is <em>just</em> interesting enough to override the mild irritation…<br />2. Or – let’s be real – you nope out <em>immediately</em> because something <em>deeply</em> offends your brain’s sense of order. </p>\n<blockquote>\n<p>If you’ve ever felt personally attacked by bad timing, congratulations! You’ve just experienced a <strong>“geek breakdown”</strong> – which totally means you’re exactly where you belong.</p>\n<p>Welcome to <em>this</em> blog. We get you.</p>\n</blockquote>\n<h2>Case Study: My 1.5k views TikTok Experiment</h2>\n<p>That’s exactly what we wanted to avoid in our own content experiments at Geekist. So, when my partner suggested a short-form video to illustrate <a href=\"https://geekist.co/how-to-geek-out-over-latin-without-sounding-like-a-priest/\">Latin prefixes</a>, we knew we had to get the rhythm right. She suggested that we found visuals relating to a small set of prefixes and that we create slides to define each prefix. </p>\n<p>Brilliant! I thought. Here’s the result: </p>\n \n<h3>What’s happening there?</h3>\n<ul>\n<li>Each slide is exactly 4 seconds long and lasts 16 bars total (2 bars each slide) </li>\n<li>Notice the “beat drops” exactly when the slide with man playing percussions comes in? Did you feel the progression? </li>\n<li>The last slide, the “outro”, happens when the 16 bars complete and ends gracefully with a message to visit Geekist.co for more information.</li>\n</ul>\n\n<h3>The Planning Phase</h3>\n<p>I decided on <strong>8 slides + 1 outro</strong> so the video wouldn’t feel too draggy. At first, I tried <strong>3 seconds per slide</strong> (a total of <strong>27 seconds</strong>), but it felt rushed. So I bumped it up to <strong>4 seconds per slide</strong>, making the video <strong>36 seconds long</strong>. </p>\n<p>But how in the world do you calculate the <strong>BPM (beats per minute)</strong> of the song to use? </p>\n<p>Fret not, my fellow geeks, for here’s a nifty calculator just for you </p>\n\n\n    THE TIMING LAB\n<h3>Find your rhythm</h3>\n<p>Set your slide duration and a comfortable tempo range. We'll find a 4/4 beat that lines up with your edits.</p>\n\n\n\n\nSlide duration4 seconds\n<p>        </p>\n0.5 sec16 sec\n\n\nMinimum BPM90 BPM\n<p>        </p>\n40 BPM200 BPM\n\n\nMaximum BPM160 BPM\n<p>        </p>\n60 BPM260 BPM\n\n\n\n      YOUR TIMING MATCH\n<strong>120</strong>BPM\nBars per slide<strong>2</strong>\nBeats per slide<strong>8</strong>\n<p>Each slide lands neatly after two 4/4 bars.</p>\n\n\n\n    4/4 TIME SIGNATURE<br />\n    Changes update live. No account, no external calculator.<br />\n  \n\n\n<p></p>\n<p><em>For example, if you want a <strong>40-second</strong> video with <strong>10 slides</strong>, you’d need <strong>4 seconds per slide</strong>. That means a BPM of <strong>120</strong> (where every 4 seconds = 2 bars) would fit perfectly. Try adjusting the numbers in the calculator above to see what works for you.</em></p>\n<p>The min and max BPM in the form help keep the music <em>somewhat</em> relatable to a general audience. That said, if you’re determined to sync your slides to an <em>aggressive Dubstep drop</em>, go for it – just don’t blame me when your viewers start glitching in real life. </p>\n<p>And the rest is easy. If you landed on <strong>120 BPM</strong> like I did for my video, that’s the <em>Goldilocks zone</em> of tempos, and there’s an <em>endless</em> supply of tracks in that range. Seriously, if you can’t find a song at 120 BPM, you’re probably browsing in silent mode! </p>\n<h2>How to Apply This to Your Own Videos</h2>\n<ol>\n<li><strong>Define Your Pace</strong>: How long should your slides be? Create one slide and measure the time it takes. Try to use whole numbers – <em>3.5 seconds will be a nightmare to use!</em></li>\n<li><strong>Calculate the BPM</strong>: Use the form above to figure out the BPM of the song you need. Faster BPMs are better for more intense presentations <em>(e.g., action montages)</em> and slower BPMs are more reflective <em>(e.g., emotional narratives)</em>. </li>\n<li><strong>Map your visuals to the Beat</strong>: Every 1 or 2 bars should be a new slide. Your outro can be 1 bar (or maybe even half a bar) to avoid an abrupt stop. </li>\n<li><strong>Choose your background music</strong>: You can make a track (like I did in FL Studio) or choose a song from the list of services below.</li>\n</ol>\n<h2>Why All of This Matters</h2>\n<p>Timed transitions in PowerPoint/Keynote business presentations can <a href=\"https://varioproductions.com/2023/04/20/how-to-use-audio-and-visuals-to-enhance-your-presentation/\">keep audiences engaged</a>. </p>\n<p>For corporate videos, syncing animations and cutaways with music makes them look polished. Short form videos like in social media reels or YouTube Shorts benefit from seamless pacing too as it keeps viewers watching longer. </p>\n<p>And hey, even musicians and dancers rely on these very same principles to synchronize stage visuals with music, so you’re in good company. </p>\n<p>Below, you’ll find a short list of apps and sites that will help you in your music search. </p>\n<p>Have you ever tried syncing your visuals to a beat? Drop a comment below with your favorite techniques or share a video where you nailed the timing! </p>\n<p>We hope you enjoyed this article, do subscribe for more! </p>\n<hr />\n<h2>Where to find music to use for free</h2>\n<figure>\n<table>\n<thead>\n<tr>\n<th><strong>Name</strong></th>\n<th><strong>Search by BPM?</strong></th>\n<th><strong>Other Filters</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><a href=\"https://www.chosic.com/search-music-by-bpm/\">Chosic</a></td>\n<td>Yes</td>\n<td>Genre</td>\n</tr>\n<tr>\n<td><a href=\"https://www.soundstripe.com/\">Soundstripe</a></td>\n<td>Yes</td>\n<td>Mood, Genre, Key</td>\n</tr>\n<tr>\n<td><a href=\"https://www.premiumbeat.com/royalty-free/music-library\">PremiumBeat</a></td>\n<td>Yes</td>\n<td>Mood, Genre, Duration</td>\n</tr>\n<tr>\n<td><a href=\"https://www.youtube.com/audiolibrary\">YouTube Audio Library</a></td>\n<td>Yes</td>\n<td>Genre, Mood, Instrument, Duration</td>\n</tr>\n<tr>\n<td><a href=\"https://incompetech.com/music/\">Incompetech</a></td>\n<td>Yes</td>\n<td>Genre, Mood, Length</td>\n</tr>\n<tr>\n<td><a href=\"https://audionautix.com/\">Audionautix</a></td>\n<td>Yes</td>\n<td>Genre, Mood, Tempo</td>\n</tr>\n</tbody>\n</table>\n</figure>\n<p>Additionally, here are some tools and platforms that can assist in finding trending music:</p>\n<figure>\n<table>\n<thead>\n<tr>\n<th><strong>Name</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><a href=\"https://vidiq.com/blog/post/find-trending-tiktok-sounds/\">vidIQ Viral</a></td>\n<td>An app that curates trending sounds and music, allowing you to filter by track length and see which sounds are gaining popularity.</td>\n</tr>\n<tr>\n<td><a href=\"https://musically.com/2021/04/01/tools-trendtok-1-app-for-tiktok-trends-sounds/\">TrendTok</a></td>\n<td>An app that provides charts of songs and trends, including features like “Predicted to Rise” and “Trending Now,” helping creators identify emerging trends</td>\n</tr>\n<tr>\n<td><a href=\"https://tokchart.com/\">TokChart</a></td>\n<td>A website that tracks the most popular songs on TikTok, offering insights into trending and growing tracks.</td>\n</tr>\n<tr>\n<td><a href=\"https://soundcharts.com/streaming-charts-monitoring\">Soundcharts</a></td>\n<td>A platform that monitors streaming charts across various services, helping you keep track of music trends globally.</td>\n</tr>\n<tr>\n<td><a href=\"https://chartmetric.com/\">Chartmetric</a></td>\n<td>Provides data-driven analytics across platforms to help identify emerging music trends and promising artists.</td>\n</tr>\n</tbody>\n</table>\n</figure>\n<p><em>A small note about TikTok and Instagram</em></p>\n<ul>\n<li><strong>TikTok</strong>: Within the app, you can add sounds to your videos by tapping the ‘+’ button to create a new video, then selecting ‘Add Sound’ at the top. This opens TikTok’s sound library, where you can explore recommended and trending sounds. </li>\n<li><strong>Instagram</strong>: When creating a reel, tap the music icon to add audio. Instagram provides a list of trending songs and allows you to search for specific tracks.</li>\n</ul>\n<hr />\n\n<h3>What is BPM in video editing?</h3>\n<p>BPM (beats per minute) determines how fast or slow your background track feels. In video editing, it’s used to time transitions, cuts, and slides so they align with the rhythm, making the video feel smoother and more professional.</p>\n<h3>How many seconds is 1 bar at 120 BPM?</h3>\n<p>At 120 BPM, one bar (in 4/4 time) lasts exactly 2 seconds. That means every 4-second slide fits neatly into 2 bars of music, perfect for timing visual changes with the beat.</p>\n<h3>Why does my video feel out of sync with the music?</h3>\n<p>Even being half a second off per transition can disrupt flow. Align your visuals with bars or beats to maintain rhythm and reduce cognitive dissonance for viewers.</p>\n<h3>What’s a good BPM for corporate or presentation videos?</h3>\n<p>90 to 120 BPM is the sweet spot. It’s steady enough to feel professional, but not too slow that it drags or too fast that it overwhelms. Aim for clean energy, not rave night at the office.</p>\n<h3>Can I use any music in TikTok videos?</h3>\n<p>Yes, but only from TikTok’s approved music library unless you own the rights. TikTok auto-mutes copyrighted music if it isn’t from their built-in sound selection, especially for business accounts. Always pick your audio from the in-app catalogue for safe usage.</p>\n\n<p></p>\n<p>BPM (beats per minute) determines how fast or slow your background track feels. In video editing, it’s used to time transitions, cuts, and slides so they align with the rhythm, making the video feel smoother and more professional.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How many seconds is 1 bar at 120 BPM?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>At 120 BPM, one bar (in 4/4 time) lasts exactly 2 seconds. That means every 4-second slide fits neatly into 2 bars of music, perfect for timing visual changes with the beat.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Why does my video feel out of sync with the music?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Even being half a second off per transition can disrupt flow. Align your visuals with bars or beats to maintain rhythm and reduce cognitive dissonance for viewers.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What’s a good BPM for corporate or presentation videos?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>90 to 120 BPM is the sweet spot. It’s steady enough to feel professional, but not too slow that it drags or too fast that it overwhelms. Aim for clean energy, not rave night at the office.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Can I use any music in TikTok videos?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Yes, but only from TikTok’s approved music library unless you own the rights. TikTok auto-mutes copyrighted music if it isn’t from their built-in sound selection, especially for business accounts. Always pick your audio from the in-app catalogue for safe usage.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 9,
                        "name": "The Geekery",
                        "slug": "the-geekery"
                    },
                    {
                        "id": 12,
                        "name": "Mind the Music",
                        "slug": "mind-the-music"
                    }
                ],
                "rich_media": [
                    {
                        "title": "Find your rhythm",
                        "url": "https://geekist.co/sync-your-music-and-visuals-together-to-captivate-your-audience/#gk-bpm-636",
                        "has_controls": true,
                        "description": "Set your slide duration and a comfortable tempo range. We’ll find a 4/4 beat that lines up with your edits."
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/how-to-stay-on-beat-and-out-of-bars-musically-speaking/",
            "url": "https://geekist.co/how-to-stay-on-beat-and-out-of-bars-musically-speaking/",
            "title": "How to Stay on Beat and Out of Bars (Musically Speaking)",
            "summary": "An overview of bars, beats, and time signatures in music, explaining why certain rhythms feel natural and how they structure everything from classical piece",
            "image": "https://img.geekist.co/wp-content/uploads/how-to-stay-on-beat-and-out-of-bars-musically-speaking.avif",
            "date_published": "2025-01-02T16:00:00Z",
            "date_modified": "2026-10-30T12:59:59Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Mind the Music",
                "The Geekery"
            ],
            "content_html": "<h2>For Anyone Who’s Ever Wondered Why Songs Just… Work</h2>\n<p>My 11-year-old daughter asked me what a bar was one day, while we were working on a song. I had previously explained to her what it meant <em>technically</em> but she still didn’t quite understand the point of it and why it mattered. </p>\n<p>After thinking about for a while, I finally said, “A bar is like a sentence.” She perks up curiously. “How does it feel when someone starts a sentence and doesn’t complete it?” I asked. </p>\n<p>“Like you’re hanging?” she replied. “Exactly,” I said. But she wasn’t completely satisfied. She went on to ask why [I said that] transitions in music happen every 4 bars and that most choruses in pop music are exactly 8 bars long. </p>\n\n<p>💡</p>\n<p>My daughter aside, this also matters when you’re choosing (or creating) background music for your videos too but more on that in a later post. Do <a href=\"https://geekist.co/subscribe/\">subscribe for updates on that!</a></p>\n\n<p>That was a good question. The truth is, it really isn’t all that easy to explain that to a person with very little exposure to the technical aspects of music. But then I had an idea. </p>\n<h2>Poetry in music</h2>\n<p>I shared a simple poem with her: </p>\n<blockquote>\n<p><em>Roses are red, (1 bar) </em><br /><em>Violets are blue, (1 bar) </em><br /><em>Sugar is sweet, (1 bar) </em><br /><em>And so are you. (1 bar)</em></p>\n</blockquote>\n<p>I asked her to read out loud. Then I asked her to read it again but this time, only the first 3 lines. You should try that too… </p>\n<p><em>Did it feel incomplete? Of course it did… there was nothing to rhyme with blue!</em></p>\n<p>1 bar, by itself is like a sentence. You’d need at least two to make a rhyme: </p>\n<blockquote>\n<p><em>Jack and Jill (1 bar) </em><br /><em>Went up the Hill (1 bar)</em></p>\n</blockquote>\n<p>That works the same way in music. 1 bar works, 2 bars completes the cycle but if you stopped at 3, you’d very really feel like you’re <em>left</em> <em>hanging</em>. 4 is when you finally feel resolved, where it feels somewhat complete. </p>\n<p>And if you heard another 4 bars, your brain understands the pattern of the first 4 bars and anticipates the next 4 (almost as if you’re subconsciously singing along the second time round). It feels natural, giving the listener enough time to absorb the current idea before moving on to the next. And that is precisely why 8 bar choruses work perfectly. </p>\n<p>In a song, a chorus is usually an <em>emotional high point</em> and often the most memorable aspect of the song. Humans tend to gravitate towards even-numbered groupings (2, 4, 8), and 8 bars offer a satisfying symmetry that resonates with our innate sense of rhythm </p>\n<p>For our brains, bars work to chunk music up into manageable and repeatable <em>pieces</em>, making it easier to follow or dance along to. It builds patterns that create predictability and anticipation. </p>\n<h2>Wait. So what exactly is a bar?</h2>\n<p>A bar is a measure. A way to divide music into segments. It’s made up of beats. So in one measure, there are a number of beats. </p>\n<p>Typically, if you’re listening to a song and you counted <em>ONE-two-three-four</em>, you’ve made a bar! Count to four again, and there’s your next bar. Simple, right? </p>\n<p>Well… not quite. </p>\n<h2>Time Signatures (the Ruler of Music)</h2>\n<p>The number of beats in a bar depends on the <strong>time signature</strong> of the music. Think about a ruler. It’s got markings for centimetres (cm) and inches (in), and each system divides the ruler differently. For example, 1 cm is divided into 10 equal parts, while 1 inch is divided into 16 parts. </p>\n<p>Just as centimetres and inches divide length differently, time signatures divide beats differently. For example, a 4/4 bar has four beats, while a 3/4 bar has three. Most songs out there follow 4/4 signatures – also known as <strong>Common Time</strong>. </p>\n<p>Now that we understand how bars work in common time, let’s explore other time signatures that feel very different. </p>\n<h3>3/4 Timing – (The Waltz)</h3>\n<p>There’s really no other way to describe it. The best way to imagine it is to imagine a waltz. What this means is that you have 3 beats per bar (measure). You’d count it like this: </p>\n<blockquote>\n<p><em>ONE-two-three, ONE-two-three</em></p>\n</blockquote>\n<p>With a focus on the ONE as the downbeat. Another way is to count it <em>ONE-and-two-and-three-and</em></p>\n<p>Go ahead and try it, this is one of the most recognisable songs in 3/4 time.: </p>\n<p><strong>Que Sera, Sera by Doris Day</strong></p>\n\n<figure>\n\nhttps://open.spotify.com/track/4Ylqc711Eq763XbTAOABu3\n\n</figure>\n\n<p>But of course, 3/4 time signatures aren’t limited to Waltzes. Take a listen (and try counting) to the following: </p>\n<p><strong>My Favourite Things by Julie Andrews</strong></p>\n\n<figure>\n\nhttps://open.spotify.com/track/1iCHl2R7xoEsh7CvYe5Ej0\n\n</figure>\n\n<p>Did that work? Ready to take it up a notch? </p>\n<h3>6/8 Timing – (The Rolling 3 beats)</h3>\n<p>It doesn’t take a math genius to see that 6/8 is really just 3/4 when you factor it down and that’s why it isn’t immediately obvious. You’d usually find 6/8 time signatures in timeless (<em>pun intended</em>) ballads. </p>\n<p>While 3/4 flows like a waltz, 6/8 rolls forward in <em>pairs of three.</em> It is used when using 4 as a measure isn’t <em>quite enough</em>, where it doesn’t feel complete. There are many songs in this category, where a single “bar” needs to be just a little longer for it work. The way I like to count it is like this: </p>\n<blockquote>\n<p><em>ONE-and-a-two-and-a</em></p>\n</blockquote>\n<p>The best way to understand this rolling rhythm is to give it a go yourself. 6/8 isn’t just about the numbers; it’s about how it moves. It creates a sense of momentum, like climbing toward something triumphant. And there’s probably no better song to illustrate this than one that captures both the drama and the grandeur of the rhythm itself… </p>\n<p><strong>We are the Champions by Queen</strong></p>\n\n<figure>\n\nhttps://open.spotify.com/track/1lCRw5FEZ1gPDNPzy1K4zW\n\n</figure>\n\n<p>This next song isn’t easy to count after but it really does a good job illustrating why it needs 6 beats a measure. The extra beats in 6/8 give this song its rolling, dreamy quality, making it feel more romantic and timeless. </p>\n<p><strong>Can’t Help Falling in Love by Elvis Presley</strong></p>\n\n<figure>\n\nhttps://open.spotify.com/track/44AyOl4qVkzS48vBsbNXaC\n\n</figure>\n\n<h2>Okay, But I’m Not a Musician so why Should I Care?</h2>\n<p>Fair point! You don’t have to be a musician to appreciate this. Do you make videos? Like those reels or slideshows of family moments? Maybe you’ve been roped into creating a feature video for your kid’s birthday – or maybe your parents’ anniversary (cue the guilt-tripping.) </p>\n<p>Here’s the thing though: knowing your bars and time signatures can take that <strong>Pixel Perfect imagery</strong> and pair it with a <strong>Rhythm Refined</strong> backing track. Suddenly, your masterpiece not only looks incredible; it feels incredible too. </p>\n<p>And hey, if geeking out about this isn’t on-brand for <a href=\"https://geekist.co/\">Geekist.co</a>, then what is? </p>\n<hr />\n\n<h3>What is a “bar” in music?</h3>\n<p>A bar (or measure) is a segment of time defined by a set number of beats. Most pop music uses 4 beats per bar. Bars help structure music into predictable, digestible pieces that feel complete.</p>\n<h3>Why do most choruses last exactly 8 bars?</h3>\n<p>Because 8-bar sections strike a perfect balance between repetition and variety. Our brains love even-numbered groupings, and 8 bars give just enough time for a musical idea to land before it transitions.</p>\n<h3>What’s the difference between 3/4 and 6/8 time?</h3>\n<p>Both have a “triple” feel, but 3/4 feels like a dance (waltz), while 6/8 rolls forward in waves. 6/8 often sounds more dramatic or flowing, perfect for ballads and big emotional arcs.</p>\n<h3>How does understanding time signatures help with video editing?</h3>\n<p>Syncing visuals to music with proper bar alignment ensures emotional impact. Whether you’re cutting to the beat or building a transition, knowing time signatures helps you hit the right moments.</p>\n<h3>Is it necessary to know music theory to pick the right background track?</h3>\n<p>Not at all. But recognising patterns – like how a song builds every 4 or 8 bars – can help you intuitively select and cut tracks that feel polished and professional.</p>\n\n<p></p>\n<p>A bar (or measure) is a segment of time defined by a set number of beats. Most pop music uses 4 beats per bar. Bars help structure music into predictable, digestible pieces that feel complete.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Why do most choruses last exactly 8 bars?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Because 8-bar sections strike a perfect balance between repetition and variety. Our brains love even-numbered groupings, and 8 bars give just enough time for a musical idea to land before it transitions.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What’s the difference between 3/4 and 6/8 time?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Both have a “triple” feel, but 3/4 feels like a dance (waltz), while 6/8 rolls forward in waves. 6/8 often sounds more dramatic or flowing, perfect for ballads and big emotional arcs.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How does understanding time signatures help with video editing?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Syncing visuals to music with proper bar alignment ensures emotional impact. Whether you’re cutting to the beat or building a transition, knowing time signatures helps you hit the right moments.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Is it necessary to know music theory to pick the right background track?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Not at all. But recognising patterns – like how a song builds every 4 or 8 bars – can help you intuitively select and cut tracks that feel polished and professional.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 9,
                        "name": "The Geekery",
                        "slug": "the-geekery"
                    },
                    {
                        "id": 12,
                        "name": "Mind the Music",
                        "slug": "mind-the-music"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/wordpress-mvc-plugin-reboot-2024/",
            "url": "https://geekist.co/wordpress-mvc-plugin-reboot-2024/",
            "title": "Modern WordPress MVC Plugin (2024)",
            "summary": "Revisiting a 2010 MVC router for WordPress plugins, now updated for 2024 with middleware, validation and more. A lightweight, no-boilerplate alternative.",
            "image": "https://img.geekist.co/wp-content/uploads/wordpress-mvc-part-2.avif",
            "date_published": "2024-12-24T20:00:00Z",
            "date_modified": "2026-02-04T21:45:28Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tools of the Trade",
                "Tame the Tech"
            ],
            "content_html": "<h2>Thoughts on the simplicity of an older solution</h2>\n<h3>Revisiting the WordPress MVC Router: A 2024 Update</h3>\n<p>So I stumbled upon an old database dump of WordPress backups over the years and chanced a 2010 article I wrote that I thought was interesting. So I extracted, and decided to test everything out before I posted it on Geekist. </p>\n<p>I’ve got to say, it really did surprise me. Logic from some 15 years ago still worked! So I decided I’d push the <a href=\"https://github.com/theGeekist/2010-router-plugin-example\">code to a repo</a>, add some screenshots and give <a href=\"https://geekist.co/wordpress-mvc-plugin-development/\">the article</a> some well deserved love. </p>\n<p>Fast forward to today, so much has changed with plugin development in WordPress, It has matured with frameworks and best practices, yet I’d still say that the core idea of a lightweight, custom router remains quietly powerful. </p>\n<p>But let’s revisit this in the context of what’s available now. </p>\n<h3>The WordPress Plugin Framework Landscape</h3>\n<p>Here are a few notable frameworks and tools for WP plugin development </p>\n<ol>\n<li><a href=\"https://wppb.me/\">WP Plugin Boilerplate</a>:<br />A standardized, object-oriented foundation for WordPress plugin development. It’s built on best practices and helps developers maintain clean, modular code. </li>\n<li><a href=\"https://developer.wordpress.org/cli/commands/scaffold\">WP Scaffold</a>:<br />A command-line tool that generates boilerplate code for plugins and themes. It doesn’t enforce MVC but provides a solid starting point for structured development. </li>\n<li><a href=\"https://timber.github.io/docs/v2/\">Timber</a>:<br />It seems primarily focused on themes (templates), but Timber uses the MVC pattern and integrates with plugins to help structure admin interfaces. </li>\n<li><a href=\"https://pods.io/\">Pods Framework</a>:<br />From what I gather, it does magic with custom content types and has powerful tools for building admin interfaces, with hooks and filters that align well with MVC-inspired routing.</li>\n</ol>\n<h3>Why Revisit the Simple Router?</h3>\n<p>Because with more features, comes complexity and a steeper learning curve. Sometimes, all you need is a lightweight, no-frills solution. </p>\n<p><em>Also… there’s absolutely nothing close to creating the building blocks of your own reusable framework – especially for smaller or personal plugins.</em></p>\n<p>The beauty of the router I introduced in 2010 (and the updated one below) lies in its simplicity. It maps URLs to controllers &amp; methods and that gives you a great starting point to quickly structure plugins, avoid repetitive code and to scale functionality without introducing heavy dependencies. </p>\n<p>And no, it’s not gonna replace WP Plugin Boilerplate for sure, but hey, there is really nothing stopping you from using both. </p>\n<h3>Updated Simple Router for 2024</h3>\n<p>Let’s dive into the updated router for 2024, which now includes a middleware implementation, auth checks, input validation and exception handling. </p>\n<h4>The New Router Class</h4>\n\n<pre>class Router\n{\n  protected $middleware = [];\n  protected $middleware_instances = [];\n // ...other methods below\n}\n</pre>\n<p>So if we have a psuedo-MVC framework, it really does make sense to include some sort of middleware implementation. Here <code>$middleware</code> is a property holding defined middleware for the class and <code>$middleware_instances</code> hold instantiated instances. More on this later.</p>\n<h4>Constructor and Initial Setup</h4>\n\n<pre>public function __construct(\n  $route,\n  $default_controller,\n  $default_method,\n  $middleware = []\n) {\n  $this-&gt;middleware = $middleware;\n  $this-&gt;perform_auth_checks();\n\n  $try = $this-&gt;route_it($route, $default_method);\n\n  if ($try === false) {\n    $this-&gt;default_route_it(\n      $default_controller,\n      $default_method,\n      $route[2]\n    );\n  }\n}\n</pre>\n<p><code>$route</code>, in this case is an array consisting of the extracted <code>$_GET</code> variables, namely <code>‘page‘</code> and <code>‘action‘</code>. This is provided by <code>plugin.php</code> when this class is instantiated. We try the provided route, if not we fall back to the default route. We also have an optional array <code>$middleware</code> saved.</p>\n<h4>Route Handling</h4>\n<p>The <code>route_it</code> method determines which controller and method to execute based on the request.</p>\n\n<pre>public function route_it(\n  $controller,\n  $method,\n  $parameters = [],\n  $default_method\n) {\n  try {\n    $obj = class_exists($controller)\n      ? new $controller()\n      : false;\n    if (!$obj) {\n      return false;\n    }\n    $method_exists = method_exists($obj, $method);\n    $default_method_exists = !$method_exists\n      &amp;&amp; method_exists($obj, $default_method);\n    if (!$method_exists &amp;&amp; !$default_method_exists) {\n      return false;\n    }\n    $this-&gt;execute_middleware(\n      $controller,\n      $method_exists ? $method : $default_method,\n      $parameters\n    );\n    return $method_exists\n      ? $obj-&gt;$method($parameters)\n      : $obj-&gt;$default_method($parameters);\n  } catch (Exception $e) {\n    $this-&gt;handle_exception($e);\n  }\n  return false;\n}</pre>\n<p>We first check if a controller exists: </p>\n\n<pre>class_exists($controller);</pre>\n<p>then we check to see if the called action exists </p>\n\n<pre>method_exists($obj, $method);</pre>\n<p>or that at least that the default action (usually named <code>index</code>) exists</p>\n\n<pre>method_exists($obj, $default_method);</pre>\n\n<p>If none of the above checks out, we return <code>false</code>, otherwise we execute the defined middleware before passing control to the controller.</p>\n<h4>Middleware Execution</h4>\n<p>Middleware execution is optimized to reuse existing instances. </p>\n\n<pre>protected function execute_middleware(\n  $controller,\n  $method,\n  $parameters\n) {\n  foreach ($this-&gt;middleware as $key =&gt; $mw) {\n    if (!isset($this-&gt;middleware_instances[$key])) {\n      if (class_exists($mw)) {\n        $this-&gt;middleware_instances[$key] = new $mw();\n      } else {\n        throw new Exception(\"Middleware class $mw not found.\");\n      }\n    }\n\n    $middleware_instance = $this-&gt;middleware_instances[$key];\n\n    if (method_exists($middleware_instance, 'handle')) {\n      $middleware_instance-&gt;handle(\n        $controller,\n        $method,\n        $parameters\n      );\n    } else {\n      throw new Exception(\n        \"Middleware class $mw does not have a handle method.\"\n      );\n    }\n  }\n}\n</pre>\n<p>This is a simple way to ensure that we don’t instantiate all the middleware for each request and is included here to illustrate how this can be done. However, another great way to include this is within your plugin’s startup code itself. That way, your plugin’s first page load wouldn’t take too long if you have tons of middleware! </p>\n<h4>Fallback Route Handling</h4>\n<p>The <code>default_route_it</code> method handles fallback routes when the specified route fails.</p>\n\n<pre>public function default_route_it(\n  $controller,\n  $method = \"index\",\n  $parameters = []\n) {\n  try {\n    $obj = class_exists($controller)\n      ? new $controller()\n      : false;\n\n    if (!$obj) {\n      throw new Exception(\"Controller not found: $controller\");\n    }\n\n    $method_exists = method_exists($obj, $method);\n    if (!$method_exists) {\n      throw new Exception(\"There is no default '$method' method found in $controller\");\n    }\n\n    $this-&gt;execute_middleware(\n      $controller,\n      $method,\n      $parameters\n    );\n\n    $obj-&gt;$method($parameters);\n  } catch (Exception $e) {\n    $this-&gt;handle_exception($e);\n  }\n\n  return false;\n}\n</pre>\n<p>This method is pretty much the same as the 2010 version. The only difference is the added middleware execution. This method helps when your controllers have a default action (<code>index</code> in this case) and will be used as to display first page of the menu item that a controller handles</p>\n<h4>Authentication Checks</h4>\n<p>Basic authentication logic is enforced during construction: </p>\n\n<pre>protected function perform_auth_checks() {\n  if (!isset($_SESSION['user'])) {\n    throw new Exception(\"Unauthenticated access detected.\");\n  }\n}\n</pre>\n<p>This saves you the hassle of checking for an authenticated user within each controller and it serves as an example of how you can include mandatory checks for your plugin. </p>\n<h4>Exception Handling</h4>\n<p>The <code>handle_exception</code> method provides a standard mechanism for logging and displaying errors.</p>\n\n<pre>public function handle_exception(\n  $e\n) {\n  error_log($e-&gt;getMessage());\n  wp_die(\n    \"An error occurred: \" . $e-&gt;getMessage()\n  );\n}\n</pre>\n<p>The example above is rudimentary but you can expand on it to write to a log file, store a database entry (or even <code>Sentry</code>) when your plugin encounters exception.</p>\n<h4>How Do We Use This Exactly?</h4>\n<p>I’ll have to admit, the original post – back in 2010 – was a little abstract so I hope the screenshot above helps to clear things up. </p>\n\n<figure><img src=\"https://geekist.co/wp-content/uploads/5aca9558-89f8-456f-8dfc-e18b3ecd2e91.avif\" alt=\"Screenshot of a WordPress CRM plugin dashboard listing contacts with a request info debug section\" width=\"588\" height=\"469\" /><figcaption>Contacts dashboard view rendered by the index action of the Contacts controller.</figcaption></figure>\n\n<p>Each menu item on the left is a controller class you define. If you look at the URL, you’d see that <code>$_GET</code> variables list <code>page=CRM</code> with no action defined. So the page you see in the screenshot points to the <code>Contacts</code> controller class and the default <code>index</code> action. I am hoping to include a link to a GH repo with example code of this functionality some time soon, so do subscribe to the newsletter for updates. In the meantime, working code for the original router is still <a href=\"https://github.com/theGeekist/2010-router-plugin-example\">available here</a></p>\n<h3>Final Thoughts</h3>\n<p>I hope this article inspires you with at least one way of organizing your plugin code. If you have questions or thoughts, do share them in the comments! </p>\n<hr />\n\n<h3>How do I build a custom MVC router in WordPress?</h3>\n<p>You can build a lightweight MVC router by mapping GET parameters to controller classes and methods, optionally injecting middleware and fallbacks for missing actions.</p>\n<h3>What is the simplest way to add middleware in a WordPress plugin?</h3>\n<p>Define a list of middleware classes and call their handle methods before routing to controllers. Reuse instances for performance, especially on first page load.</p>\n<h3>Is there a plugin framework for WordPress that uses MVC?</h3>\n<p>Yes. While most frameworks like WP Boilerplate are structured, you can roll your own MVC logic or use tools like Timber (for themes) or Pods (for content types) that support MVC principles.</p>\n<h3>How does a fallback route work in WordPress MVC router?</h3>\n<p>If a controller or method isn’t found, the router falls back to a default controller and method, often ‘index’, ensuring graceful degradation and simpler plugin navigation.</p>\n<h3>Can I still use old WordPress plugin logic today?</h3>\n<p>Yes! With a bit of refactoring, logic from older WordPress plugins like custom routers can still work and scale today, especially for lightweight or personal plugins.</p>\n\n<p></p>\n<p>You can build a lightweight MVC router by mapping GET parameters to controller classes and methods, optionally injecting middleware and fallbacks for missing actions.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What is the simplest way to add middleware in a WordPress plugin?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Define a list of middleware classes and call their handle methods before routing to controllers. Reuse instances for performance, especially on first page load.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Is there a plugin framework for WordPress that uses MVC?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Yes. While most frameworks like WP Boilerplate are structured, you can roll your own MVC logic or use tools like Timber (for themes) or Pods (for content types) that support MVC principles.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How does a fallback route work in WordPress MVC router?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>If a controller or method isn’t found, the router falls back to a default controller and method, often ‘index’, ensuring graceful degradation and simpler plugin navigation.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Can I still use old WordPress plugin logic today?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Yes! With a bit of refactoring, logic from older WordPress plugins like custom routers can still work and scale today, especially for lightweight or personal plugins.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 6,
                        "name": "Tools of the Trade",
                        "slug": "tools-of-the-trade"
                    }
                ],
                "references": {
                    "mentions_mcp": false,
                    "github_links": [
                        "https://github.com/theGeekist/2010-router-plugin-example"
                    ],
                    "public_product_links": [],
                    "public_products": []
                }
            }
        },
        {
            "id": "http://172.29.142.55/4263-2/",
            "url": "https://geekist.co/the-tool-that-made-css-magical/",
            "title": "The Tool that made CSS Magical…",
            "summary": "A look back at Stylizer, a visual CSS editor that once made live styling intuitive, before frameworks took over and it faded into obscurity.",
            "image": "https://img.geekist.co/wp-content/uploads/retro-css-magic-2.avif",
            "date_published": "2024-12-23T20:00:00Z",
            "date_modified": "2026-02-04T21:25:44Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Where the User Begins",
                "Uncategorized",
                "Tame the Tech"
            ],
            "content_html": "<p>So there I was, about to drag the downloaded <a href=\"https://openrefine.org/\">OpenRefine</a> into my Applications folder when I stopped dead in my tracks! That logo – it couldn’t be… Stylizer? The logo that defined my pixel-perfect dreams back in the day? </p>\n<p>Hey, don’t take my word for it, have a look yourself! Here’s OpenRefine’s Logo: </p>\n\n\n\n<figure><img src=\"https://geekist.co/wp-content/uploads/1ba8914b-6b91-499c-9ece-34f3aa49b4fc.avif\" alt=\"OpenRefine Logo and Tagline – Open Source Data Cleanup Tool\" width=\"781\" height=\"277\" /><figcaption>OpenRefine’s blue diamond—open source, but visually aligned with Stylizer? </figcaption></figure>\n\n\n\n<p>And here’s Stylizer: </p>\n\n\n\n<figure><img src=\"https://geekist.co/wp-content/uploads/48f2e81e-5885-491d-be64-2bb50eaa1b71-800x322.avif\" alt=\"Banner showing Stylizer’s diamond logo and a thank you message for downloading the software\" width=\"800\" height=\"322\" /><figcaption>Stylizer’s gleaming diamond banner – now oddly familiar?</figcaption></figure>\n\n\n\n<p>Okay sure, it’s not exactly the same but it’s close enough. Anyway, I googled it and to my surprise, <a href=\"http://www.skybound.ca/\">Stylizer</a> still exists! </p>\n<p>Stylizer was my dream CSS buddy. Forget Dreamweaver – it was the industry standard (apparently it still is, depending on who you ask) – but it was nothing compared to Stylizer’s sleek interface and intuitive toolbar. Check this out: </p>\n<p>It worked across every browser, even ancient versions of Internet Explorer (may they rest in peace). And you could style in realtime too – much like you can edit CSS in the browser’s console – but you’re not writing any CSS, you’re using that toolbar above. </p>\n<h2>Okay, so what happened?</h2>\n<p>Well, to put it bluntly, LESS happened. Then SASS, SCSS, and PostCSS and the rest is history. There was suddenly a method in the CSS mayhem. Structure and reusability like nothing before. But that’s not all. </p>\n<p><em>CSS Animations happened too.</em></p>\n<p>And IMHO, that’s what killed Stylizer. Browsers were moving much faster than Skybound could keep up with. You see Stylizer worked directly with stylesheets. It created perfect CSS3 rules but writing CSS directly was going out of fashion. </p>\n<p>Bootstrap was taking over and it brought LESS along with it. But as I said earlier, without a way to add animations, Stylizer became yesterday’s news. You could technically still do it by hand coding it, but that simply wasn’t it’s appeal to start with. </p>\n<p>So yeah, this post is my little ode to Stylizer – the app that made my web pages sparkle and my heart sing. Here’s to the glory days and the joy of a tool way ahead of its time. </p>\n<p>Thank you Stylizer! </p>\n<hr />\n\n<h3>What happened to Stylizer CSS editor?</h3>\n<p>Stylizer fell out of favour as CSS preprocessors like LESS and SASS took over, adding structure, reusability, and animations that Stylizer couldn’t keep up with.</p>\n<h3>Is Stylizer still available?</h3>\n<p>Yes, Stylizer still exists at skybound.ca, but it’s no longer widely used in modern workflows dominated by preprocessors and browser dev tools.</p>\n<h3>Why did Stylizer lose popularity?</h3>\n<p>Stylizer relied on direct CSS editing and lacked support for modern workflows like CSS animations and preprocessors, making it obsolete as the web evolved.</p>\n<h3>Best alternatives to Stylizer for CSS editing?</h3>\n<p>Modern alternatives include browser dev tools, Visual Studio Code with live server plugins, and preprocessors like SASS or PostCSS for advanced styling.</p>\n<h3>Did Bootstrap kill Stylizer?</h3>\n<p>Indirectly, yes. Bootstrap and other frameworks pushed developers toward LESS and SASS, reducing the demand for GUI-based CSS tools like Stylizer.</p>\n\n<p></p>\n<p>Stylizer fell out of favour as CSS preprocessors like LESS and SASS took over, adding structure, reusability, and animations that Stylizer couldn’t keep up with.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Is Stylizer still available?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Yes, Stylizer still exists at skybound.ca, but it’s no longer widely used in modern workflows dominated by preprocessors and browser dev tools.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Why did Stylizer lose popularity?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Stylizer relied on direct CSS editing and lacked support for modern workflows like CSS animations and preprocessors, making it obsolete as the web evolved.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Best alternatives to Stylizer for CSS editing?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Modern alternatives include browser dev tools, Visual Studio Code with live server plugins, and preprocessors like SASS or PostCSS for advanced styling.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Did Bootstrap kill Stylizer?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Indirectly, yes. Bootstrap and other frameworks pushed developers toward LESS and SASS, reducing the demand for GUI-based CSS tools like Stylizer.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 1,
                        "name": "Uncategorized",
                        "slug": "uncategorized"
                    },
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 7,
                        "name": "Where the User Begins",
                        "slug": "where-the-user-begins"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/the-art-of-proxying/",
            "url": "https://geekist.co/the-art-of-proxying/",
            "title": "The Art of Proxying: Mastering Traffic Like a Pro",
            "summary": "A deep dive into advanced Nginx reverse proxy setups, covering WebSockets, gRPC, Layer 7 load balancing, and real-world traffic management strategies.",
            "image": "https://img.geekist.co/wp-content/uploads/the-art-of-proxying.avif",
            "date_published": "2024-12-22T16:59:09Z",
            "date_modified": "2026-02-04T21:45:29Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Beneath the Stack",
                "Tame the Tech"
            ],
            "content_html": "<h2>Advanced Solutions to Real-World Challenges in Traffic Management</h2>\n<p>Welcome back to the <a href=\"https://geekist.co/series/taming-nginx/\"><strong>Taming Nginx</strong></a> series! In this article, we’re diving into the art of reverse proxying. While many guides focus on the basics, this article is for those who want to push Nginx to its limits, we’ll explore advanced and peculiar use cases that can take your configuration to the next level. </p>\n<p>If you missed the earlier articles, here’s a quick recap: </p>\n<ul>\n<li><a href=\"https://geekist.co/smarter-defaults-for-subdomains-and-ssl/\">Smarter Defaults for Subdomains and SSL</a> – how to organise your subdomain configuration in Nginx. </li>\n<li><a href=\"https://geekist.co/building-the-foundation/\">Why Your Web Server Structure is Holding You Back</a> – a deep dive into common folder structures and the system I’ve settled on. </li>\n<li><a href=\"https://geekist.co/wildcard-ssl-and-beyond/\">Wildcard SSL and Beyond</a> – securing your web server with SSL, wildcard certificates, and mutual SSL. </li>\n<li>The Art of Proxying: Mastering Traffic Management Like a Pro – You are reading this now.</li>\n</ul>\n<p>This time, it’s all about the potential of Nginx as a reverse proxy. We’ll examine how each use case addresses real-world challenges and elevates your configurations. </p>\n<h3>Reverse Proxy Refresher</h3>\n<p>Here’s a quick primer on what a reverse proxy does: </p>\n<blockquote>\n<p>At its core, a reverse proxy sits between clients and backend servers, forwarding requests and responses while optionally performing additional tasks like SSL termination, caching or load balancing.</p>\n</blockquote>\n<p>If you’ve followed the earlier articles in this series, you’ll know that we redirect all HTTP traffic to HTTPS by default and wildcard SSL certificates are used to secure subdomains. The examples in this article build upon that foundation, assuming the same <code>ssl_params</code> file for shared SSL settings and no incoming requests to port 80.</p>\n<p>Also note that I’ve deliberately excluded mutual SSL here (since it was covered before), along with caching &amp; security – as I will talk about that in detail in the next article in the series. </p>\n<p>Let’s dive in! </p>\n<h3>1. Layer 7 Load Balancing with Sticky Sessions</h3>\n<p>Layer 7 of the OSI model, also known as the <a href=\"https://en.wikipedia.org/wiki/Application_layer\">Application Layer</a>, was formalized in the late 1970s to standardize communication across networked systems. Unlike lower layers that handle data transport and routing, Layer 7 focuses on the content and context of communication – think HTTP requests, email protocols and, yes, even Nginx configurations. </p>\n<p>Load balancing brings content-aware traffic handling into the mix. Beyond distributing connections evenly, it enables decisions based on application-specific information, like URLs, cookies or headers. Sticky sessions, for instance, solve the specific challenge of keeping user sessions tied to a single server. Think shopping carts or user logins, where consistency is key. </p>\n<h4>Configuration:</h4>\n\n<pre>upstream backend {\n    ip_hash;\n    server backend1.example.com;\n    server backend2.example.com;\n}\nserver {\n    listen 443 ssl;\n    server_name example.com;\n    include /etc/nginx/ssl_params;\n    location / {\n        proxy_pass http://backend;\n        proxy_set_header Host $host;\n        proxy_set_header X-Real-IP $remote_addr;\n    }\n}</pre>\n<h4>What’s going on here?</h4>\n<p>Hopefully, you weren’t expecting anything special here. The <code>ip_hash</code> directive uses the client’s IP address to generate a consistent hash value, which determines the target server within the upstream block. This method works as long as your client’s IP remains stable and makes short work of most session-dependent tasks like e-commerce or user dashboards.</p>\n<h3>2. Protocol Translation: WebSockets, gRPC and HTTP/2</h3>\n<p>Before the advent of WebSockets, we had to rely on hacks like long polling or frequent HTTP requests which – as you know probably know – are both inefficient and resource-intensive. </p>\n<p>Introduced in 2011 as part of the HTML5 specification, WebSockets offered a persistent, full-duplex communication channel over a single TCP connection, enabling true real-time interactivity by keep connections alive – allowing <em>servers</em> to push updates to <em>clients</em> as events occur. </p>\n<p>It transformed applications like chat, live notifications and collaborative tools, laying the groundwork for modern, highly interactive web experiences. </p>\n<p>With Nginx, integrating WebSockets into your stack becomes straightforward, bridging the gap between users and backend services. </p>\n<h4>WebSockets:</h4>\n\n<pre>server {\n    listen 443 ssl;\n    server_name example.com;\n    include /etc/nginx/ssl_params;\n    location /ws/ {\n        proxy_pass http://websocket_server;\n        proxy_http_version 1.1;\n        proxy_set_header Upgrade $http_upgrade;\n        proxy_set_header Connection \"upgrade\";\n    }\n}</pre>\n<h4>What’s going on here?</h4>\n<p>So the <code>proxy_pass</code> directive specifies the backend server or application that will handle WebSocket traffic. It allows Nginx to forward WebSocket requests from clients to the specified server.</p>\n<p>The <code>proxy_http_version 1.1</code> directive ensures that HTTP/1.1 is used for the connection, which is required for WebSocket compatibility.</p>\n<p>The <code>proxy_set_header Upgrade $http_upgrade</code> and <code>proxy_set_header Connection \"upgrade\"</code> directives manage the protocol upgrade from HTTP to WebSocket. These headers signal the backend server to switch protocols and maintain the WebSocket connection.</p>\n<p>Now let’s talk about gRPC (gRPC Remote Procedure Call) – a modern, high-performance framework developed by Google in 2015. Built on top of HTTP/2, it enables efficient, bi-directional streaming and multiplexing over a single connection, making it ideal for real-time and low-latency applications. </p>\n<h4>gRPC with HTTP/2:</h4>\n\n<pre>server {\n    listen 443 ssl;\n    server_name grpc.example.com;\n    include /etc/nginx/ssl_params;\n    http2 on; # Enable HTTP/2 for this server block\n    location / {\n        grpc_pass grpc://127.0.0.1:50051;\n    }\n}</pre>\n<h4>What’s going on here?</h4>\n<p>Not much! The <code>grpc_pass</code> directive is the heart of this configuration, forwarding gRPC traffic to the backend application listening on port 50051. Unlike HTTP/1.x, gRPC relies on HTTP/2, which enables multiplexed streams over a single connection.</p>\n<h3>3. API Gateway with Rate Limiting</h3>\n<p>APIs are the backbone of modern apps, powering everything from social networks to payment systems. But with great power comes great responsibility – or in this case, <em>great vulnerability</em>!. Left unchecked, APIs can fall victim to abuse, such as excessive requests or bot attacks, which can degrade performance for legitimate users. </p>\n<p>Rate limiting emerged as a solution to manage API traffic by setting limits on how often a client can make requests, it prevents overuse while ensuring fair access to backend services. In the early days, we had to rely on ad-hoc custom scripts or middleware to throttle requests. They worked of course but are usually resource-intensive and difficult to scale. </p>\n<p>Nginx, with its built-in rate limiting capabilities, simplifies this process. By integrating rate limiting directly into your reverse proxy configuration, you gain a powerful and efficient way to protect your APIs without reinventing the wheel. </p>\n<h4>Configuration:</h4>\n\n<pre>http {\n    limit_req_zone $binary_remote_addr zone=api_limit:10m rate=5r/s;\n    server {\n        listen 443 ssl;\n        server_name api.example.com;\n        include /etc/nginx/ssl_params;\n        location / {\n            limit_req zone=api_limit burst=10 nodelay;\n            proxy_pass http://backend_api;\n        }\n    }\n}</pre>\n<h4>What’s going on here?</h4>\n<p>The <code>limit_req_zone</code> directive defines a shared memory zone for tracking requests per IP. This shared memory allows Nginx to monitor how many requests each client sends over a specified time period.</p>\n<p>The <code>limit_req</code> directive works as a gatekeeper, allowing only a specific number of requests to pass through per second for each IP address. If the rate is exceeded, excess requests are either delayed (if configured) or dropped, protecting the backend from being overwhelmed. This setup provides a way to ensure fair resource usage while safeguarding backend performance.</p>\n<h3>4. Dynamic Upstream Selection</h3>\n<p>Dynamic upstream selection is a game-changer for anyone managing staging environments, multi-tenant applications or complex deployment workflows. Traditionally, handling such variability required maintaining multiple (and often redundant) server blocks – <em>you really don’t want to go there!</em>) </p>\n<p>But with Nginx’s <code>set</code> directive, you can conditionally route traffic based on factors like query parameters, headers or cookies.</p>\n<h4>Configuration:</h4>\n\n<pre>server {\n    listen 443 ssl;\n    include /etc/nginx/ssl_params;\n    location / {\n        set $upstream http://backend1;\n        if ($arg_env = \"staging\") {\n            set $upstream http://staging_backend;\n        }\n        proxy_pass $upstream;\n    }\n}</pre>\n<h4>What’s going on here?</h4>\n<p>The <code>set</code> directive is a powerful tool for dynamically assigning variable values based on specific conditions. In this configuration, <code>set</code> is used to determine the upstream server by inspecting the <code>arg_env</code> query parameter. If <code>arg_env</code> is set to “staging,” the request is routed to the staging backend; otherwise, it defaults to the production backend.</p>\n<p>This ability to assign variables conditionally streamlines complex routing scenarios, allowing configurations to remain concise, modular and readable. <code>set</code> can also be used for other creative use cases, like adjusting cache keys, generating custom headers or controlling feature flags.</p>\n<h3>5. Reverse Proxy with Backend Health Checks</h3>\n<p>How many times have you had a backend service go down and your frontend go berserk or present you with the infamous <code>502</code> gateway errors?</p>\n<p>Health checks provide an elegant solution to this problem – and Nginx comes with this built-in. If a server goes down, Nginx temporarily removes it from the upstream pool until it recovers. </p>\n<h4>Configuration:</h4>\n<pre>upstream backend {\n    server backend1.example.com;\n    server backend2.example.com;\n    server backend3.example.com backup;\n    health_check interval=5s rise=2 fall=3 timeout=2s;\n}\nserver {\n    listen 443 ssl;\n    include /etc/nginx/ssl_params;\n    location / {\n        proxy_pass http://backend;\n    }\n}</pre>\n\n<h4>What’s going on here?</h4>\n<p>The <code>health_check</code> directive steps in as your reverse proxy’s safety net. It continuously pings the upstream servers at intervals you define (here, every 5 seconds) to verify their responsiveness. If a server fails to respond correctly, it’s temporarily removed from the pool.</p>\n<p>But it doesn’t stop there. You can configure parameters like <code>rise</code> and <code>fall</code> to determine how many consecutive successes or failures are required for a server to be reinstated or deactivated respectively. This ensures that temporary blips don’t immediately mark a server as unhealthy but where persistent issues are handled gracefully.</p>\n<p>Your frontend remains resilient and cryptic error messages for users become a thing of the past. </p>\n<h3>What’s Next?</h3>\n<p>In this article, we’ve seen how Nginx’s reverse proxy capabilities extend far beyond the basics, enabling sophisticated traffic management and backend integrations. Whether it’s load balancing, dynamic routing or protocol translation, there’s always room to level up your configurations. </p>\n<p>Next, we’ll explore <strong>streaming and low-level protocol handling with Nginx’s</strong> <code>streams {}</code> block. If you’ve got questions, examples or clever configurations of your own, let’s chat in the comments below.</p>\n<blockquote>\n<p>If this proxy trick made you smile, wait till you meet the others.<br />Grab <strong><em><a href=\"https://geekist.co/nginx-by-example/\">Nginx by Example Vol. 1</a></em></strong> and start traffic-jitsu like a pro.</p>\n</blockquote>\n<hr />\n\n<h3>How to use Nginx as a reverse proxy?</h3>\n<p>Set up a server block with proxy_pass to your backend app. Nginx will forward client requests while handling SSL, headers, and more.</p>\n<h3>What is sticky session in Nginx?</h3>\n<p>Sticky sessions in Nginx use ip_hash to tie each client’s session to the same backend server that’s great for logins or shopping carts.</p>\n<h3>How to enable WebSocket support in Nginx?</h3>\n<p>Use proxy_http_version 1.1 and set Upgrade and Connection headers to support WebSocket protocol switching in reverse proxy mode.</p>\n<h3>How to rate limit API requests with Nginx?</h3>\n<p>Use limit_req_zone and limit_req directives to control how many requests per second a client can send which is perfect for protecting APIs.</p>\n<h3>How to route traffic to staging backend in Nginx?</h3>\n<p>Use the set directive with conditions like query params to dynamically assign upstream servers so there’s no need for multiple server blocks.</p>\n\n<p></p>\n<p>Set up a server block with proxy_pass to your backend app. Nginx will forward client requests while handling SSL, headers, and more.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What is sticky session in Nginx?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Sticky sessions in Nginx use ip_hash to tie each client’s session to the same backend server that’s great for logins or shopping carts.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How to enable WebSocket support in Nginx?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Use proxy_http_version 1.1 and set Upgrade and Connection headers to support WebSocket protocol switching in reverse proxy mode.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How to rate limit API requests with Nginx?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Use limit_req_zone and limit_req directives to control how many requests per second a client can send which is perfect for protecting APIs.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How to route traffic to staging backend in Nginx?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Use the set directive with conditions like query params to dynamically assign upstream servers so there’s no need for multiple server blocks.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/how-to-geek-out-over-latin-without-sounding-like-a-priest/",
            "url": "https://geekist.co/how-to-geek-out-over-latin-without-sounding-like-a-priest/",
            "title": "How to Geek Out Over Latin Without Sounding Like a Priest",
            "summary": "The ancient roots of prefixes like Sino- and Hispano-, why Latin lost its spark, and how nerds bring \"dead\" languages back to life",
            "image": "https://img.geekist.co/wp-content/uploads/how-to-geek-out-over-latin-without-sounding-like-a-priest.avif",
            "date_published": "2024-12-20T20:20:19Z",
            "date_modified": "2026-02-04T21:25:32Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Geekery"
            ],
            "content_html": "<p>Have you ever watched the news and heard a repo go <em>“The</em> <strong><em>Sino-American</em></strong> <em> relationship…”</em> or the <em>“The</em> <strong><em>Indo-Pacific</em></strong> <em>Economic Framework”</em> and wonder what in the world <code>Sino</code> or <code>Indo</code> meant and where it came from?</p>\n<p><em>Did you also think ‘Indo’ must have something to do with Indonesia?</em></p>\n<p>But if you finally concluded that you couldn’t care less anyway because it’s probably all a bunch of loaded politics, you wouldn’t be wrong at all. These terms come with a fair share of <em>ancient baggage</em>! Words like <em>Sino-American</em> or <em>Hispano-Caribbean</em> are linguistic time machines, rooted in <strong>Latin dominance, regional quirks, and a touch of empire-fuelled hubris.</strong></p>\n<p>Dust off your etymology hats! Let’s dive into some history… (err geekery) and explore why Latin’s enduring fingerprints are both fascinating and paradoxically lifeless. </p>\n<p><em>I’ll also throw in some nerd rage about accents and why priests are totally killing the vibes of ancient languages.</em></p>\n<h2>“Hispanic” and the Romance Conundrum</h2>\n<p>Let’s start with a classic brain-twister. The term <strong>Hispanic</strong> often evokes imagery of Latin America, spicy food, and telenovelas, yet it originates from Hispania, the Roman name for the Iberian Peninsula (Spain and Portugal). </p>\n<p>In fact, it is used distinctively in terms like Hispano-Roman, referring to the cultural and linguistic blend in Hispania under Roman rule. </p>\n<p><strong>But here’s the kicker:</strong> Spanish is a Romance language (as in, descended from Roman Latin), yet the term <em>Hispanic</em> often feels culturally divorced from Rome itself. </p>\n<p>💡<em>Did You Know?</em></p>\n<blockquote>\n<p>The Romans didn’t call their languages “Romance.” That label comes from the medieval Latin phrase <em>Romanice loqui</em> (“to speak in the Roman way”) which was used by medieval peasants to distinguish their proto-Spanish | proto-French | proto-Italian from the Latin monks still <a href=\"https://archives.collections.ed.ac.uk/subjects/25948\">writing epic</a> works of <a href=\"https://www.sourcebook.stanford.edu/texts-table\">poetry</a> that <a href=\"https://blogs.bl.uk/digitisedmanuscripts/2022/03/tall-tales.html\">no one could read</a> – because why not keep things inaccessible?</p>\n</blockquote>\n<h3>Okay cool. Languages and what not, but what about the Latin?</h3>\n<p>Yep, I’m getting there. Latin <a href=\"https://www.sanskritimagazine.com/vedic-culture/similarities-between-latin-and-sanskrit/\">is often compared to <strong>Sanskrit</strong></a> and similarly has its role as a “sacred language” preserved by institutions. But here’s where it gets nerdy: </p>\n<h4>Without Institutions:</h4>\n<p>Latin would have vanished like a bad beta app, leaving no trace of Cicero, Virgil, or the <em>veni vidi vici</em> memes we adore. It’s thanks to the Catholic Church (and their obsessive use of Latin in liturgy) that the language survived. </p>\n<p>In the same way, Sanskrit might have disappeared entirely were it not for its central role in Vedic rituals. The oral tradition kept texts like the <em>Rigveda</em> alive for centuries before they were even written down, but its preservation came with <a href=\"https://en.wikipedia.org/wiki/%C5%9Aruti\">strict recitation rules</a>. </p>\n<h4>With Institutions:</h4>\n<p>Latin got turned into a linguistic museum piece. Instead of lively orations in the Roman Forum, we now have priests reciting the Lord’s Prayer in monotones that lack color and human depth. </p>\n<p>Sanskrit’s use in modern rituals has reduced its vibrancy. Priests focus on tonal precision, chanting hymns in a robotic style to avoid errors that could “offend the gods.” This monotone delivery strips away any hint of conversational life, turning a once-vivid language into an aural algorithm. </p>\n<h3>What Did Classical Latin Sound Like?</h3>\n<p>If you’ve heard someone speak in Latin in modern times, you’d probably have wondered… <em>“Did Romans really sound this boring?”</em></p>\n<p><strong>No, they absolutely did not.</strong></p>\n<h4>Classical Latin</h4>\n<ul>\n<li>Think of a Roman senator speaking like an Italian opera singer:\n<ul>\n<li>Every syllable mattered. </li>\n<li>Hard consonants (e.g., <em>Caesar</em> = <em>KAI-sar</em>, not <em>SEE-zar</em>). </li>\n<li>Flowing vowels (<em>amicus</em> = <em>a-MEE-kus</em>).</li>\n</ul>\n</li>\n</ul>\n<p>Closest modern accent? <strong>Sardinian.</strong> It preserves many of the crisp consonants and vowels of ancient Latin, and its unique linguistic traits have earned it <a href=\"https://www.britannica.com/topic/Sardinian-language\">the nickname “a living fossil” of Classical Latin</a> – very unlike modern Ecclesiastical Latin. </p>\n<p>💡<em>Did You Know?</em></p>\n<blockquote>\n<p>Latin <em>vinum</em> (“wine”) was pronounced <em>WEE-num</em> in Classical Latin, but modern priests say <em>VEE-num</em>. Blame the medieval Italians for swapping the smooth Roman “w” for the sharper “v”. Still wondering how to pronounce BMW?</p>\n</blockquote>\n<h3>Sanskrit: Latin’s Spiritual Cousin</h3>\n<p>Sanskrit, like Latin, survives through religious institutions. And while priests chanting Vedic hymns might help put you in a higher state of consciousness, they’re still light-years away from the conversational Sanskrit of ancient India. Here’s why: </p>\n<ol>\n<li><strong>Precision Over Expression:</strong> Rituals demand accuracy. In Sanskrit, a single mispronounced syllable could offend a deity. </li>\n<li><strong>Regional Twists:</strong> Sanskrit chants are often delivered with accents influenced by local languages – e.g., Tamil Nadu’s rolling tones versus Uttar Pradesh’s sharpness.</li>\n</ol>\n<p>💡<em>Did You Know?</em></p>\n<blockquote>\n<p>In Sanskrit, the intonation system (<em>swara</em>) isn’t just decorative – it changes the meaning of words. Imagine accidentally asking for rain instead of blessings because you got your tone wrong. Oops!</p>\n</blockquote>\n<h3>Reviving the Dead (Languages)</h3>\n<p>There’s hope for Latin (and Sanskrit) enthusiasts: </p>\n<ol>\n<li><strong>Reconstruction Projects:</strong> Linguists are geeking out over ancient pronunciation rules to <a href=\"https://www.goodreads.com/book/show/246974.Vox_Latina\">recreate how Cicero</a> or <a href=\"https://en.wikipedia.org/wiki/Shiksha\">Vedic sages</a> <a href=\"https://youtu.be/_ZfWu58jQog\">might have sounded</a>. </li>\n<li><strong>Modern Clubs:</strong> Spoken Latin <a href=\"https://www.speaking-latin.net/\">meet-ups</a> are a thing. Yes, people <a href=\"https://www.meetup.com/Beginners-Latin-Club/\"><em>actually</em> debate</a> in Latin. Kinda like jousting for linguists. </li>\n<li><strong>AI Simulations:</strong> Imagine asking ChatGPT to <a href=\"https://www.yeschat.ai/gpts-9t55R6T8w9G-Cicero-the-Orator\">generate a speech in Cicero’s</a> authentic voice. Nerdy? Yes. But very cool.</li>\n</ol>\n<h3>Final Geek Thoughts</h3>\n<p>The prefixes we toss around today (<em>Sino-</em>, <em>Hispano-</em>, <em>Indo-</em>) are gateways to history, culture, and a fair bit of imperial ego. Yet, as we geek out over these terms, we’re also mourning what was lost: the accents, the emotion, and the humanity of languages that once shaped the world. </p>\n<p>So next time you hear Latin in a church or Sanskrit at a temple, take a moment to imagine what they sounded like in their prime – lively, expressive, and maybe even a little sassy. </p>\n<p><strong>Did you enjoy this geeky deep dive? Share your thoughts below, or better yet, learn some Latin and join the revival!</strong></p>\n<h3>The Geek’s Table of Linguistic Awesomeness</h3>\n<p>Here’s a snapshot of some commonly used prefixes and what they actually mean (<a href=\"https://en.wikipedia.org/wiki/Prefix\">because geeks love tables, right?</a>)..</p>\n<figure>\n<table>\n<thead>\n<tr>\n<td><strong>Term</strong></td>\n<td><strong>Meaning</strong></td>\n<td><strong>Earliest Mention</strong></td>\n<td><strong>Short Description</strong></td>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><strong>Sino-</strong><br /><em>From: Latin (Sinae)</em></td>\n<td>Relating to China<br /><em>Earliest Use: 19th century</em></td>\n<td>Ancient Chinese Empires<br /><em>Type: Geopolitical</em></td>\n<td>Used in contexts like Sino-American relations. </td>\n</tr>\n<tr>\n<td><strong>Anglo-</strong><br /><em>From: Latin (Anglii)</em></td>\n<td>Relating to England or English<br /><em>Earliest Use: 16th century</em></td>\n<td>Anglo-Saxons (5th century)<br /><em>Type: Geopolitical</em></td>\n<td>Used to describe English-speaking nations or cultures. </td>\n</tr>\n<tr>\n<td><strong>Franco-</strong><br /><em>From: Latin (Franci)</em></td>\n<td>Relating to France or French<br /><em>Earliest Use: 17th century</em></td>\n<td>Frankish Empire (5th century)<br /><em>Type: Geopolitical</em></td>\n<td>Used in discussions about French relations (e.g., Franco-German). </td>\n</tr>\n<tr>\n<td><strong>Russo-</strong><br /><em>From: Latin (Rutheni)</em></td>\n<td>Relating to Russia<br /><em>Earliest Use: 18th century</em></td>\n<td>Tsardom of Russia<br /><em>Type: Geopolitical</em></td>\n<td>Used for relations involving Russia, e.g., Russo-Japanese War. </td>\n</tr>\n<tr>\n<td><strong>Germano-</strong><br /><em>From: Latin (Germani)</em></td>\n<td>Relating to Germany<br /><em>Earliest Use: 18th century</em></td>\n<td>Germanic tribes<br /><em>Type: Geopolitical</em></td>\n<td>Refers to Germanic or modern German contexts. </td>\n</tr>\n<tr>\n<td><strong>Italo-</strong><br /><em>From: Latin (Italia)</em></td>\n<td>Relating to Italy<br /><em>Earliest Use: 19th century</em></td>\n<td>Ancient Rome<br /><em>Type: Geopolitical</em></td>\n<td>Used for Italy’s relations, e.g., Italo-German relations. </td>\n</tr>\n<tr>\n<td><strong>Ibero-</strong><br /><em>From: Greek (Iberia)</em></td>\n<td>Relating to the Iberian Peninsula<br /><em>Earliest Use: 18th century</em></td>\n<td>Ancient Iberians<br /><em>Type: Geopolitical/Cultural</em></td>\n<td>Refers to Spain and Portugal or their shared history and influence. </td>\n</tr>\n<tr>\n<td><strong>Hispano-</strong><br /><em>From: Latin (Hispania)</em></td>\n<td>Relating to Spain or Spanish-speaking<br /><em>Earliest Use: 19th century</em></td>\n<td>Roman Hispania<br /><em>Type: Geopolitical/Cultural</em></td>\n<td>Covers Spanish-speaking cultural or historical contexts. </td>\n</tr>\n<tr>\n<td><strong>Indo-</strong><br /><em>From: Greek (Indos)</em></td>\n<td>Relating to India or Indian subcontinent<br /><em>Earliest Use: 18th century</em></td>\n<td>Ancient India<br /><em>Type: Linguistic/Cultural</em></td>\n<td>Used in Indo-European languages, Indo-Aryan peoples, etc. </td>\n</tr>\n<tr>\n<td><strong>Turko-</strong><br /><em>From: Latin (Turcus)</em></td>\n<td>Relating to Turkey or Turkic peoples<br /><em>Earliest Use: 18th century</em></td>\n<td>Ottoman Empire<br /><em>Type: Geopolitical/Cultural</em></td>\n<td>Used for cultural or geopolitical contexts involving Turkey. </td>\n</tr>\n<tr>\n<td><strong>Nippo-</strong><br /><em>From: Japanese (Nihon)</em></td>\n<td>Relating to Japan<br /><em>Earliest Use: 19th century</em></td>\n<td>Tokugawa Japan<br /><em>Type: Geopolitical</em></td>\n<td>Refers to Japanese relations, e.g., Nippo-Korean relations. </td>\n</tr>\n<tr>\n<td><strong>Afro-</strong><br /><em>From: Latin (Afri)</em></td>\n<td>Relating to Africa<br /><em>Earliest Use: 19th century</em></td>\n<td>Ancient Africa<br /><em>Type: Geopolitical/Cultural</em></td>\n<td>Covers African relations, culture, and history (e.g., Afro-Asian). </td>\n</tr>\n<tr>\n<td><strong>Pan-</strong><br /><em>From: Greek (pan, “all”)</em></td>\n<td>Relating to broad groups<br /><em>Earliest Use: 19th century</em></td>\n<td>Various<br /><em>Type: Regional/Philosophical</em></td>\n<td>Used in unity movements, e.g., Pan-Africanism, Pan-Europeanism. </td>\n</tr>\n<tr>\n<td><strong>Arabo-</strong><br /><em>From: Latin (Arabus)</em></td>\n<td>Relating to Arab culture or peoples<br /><em>Earliest Use: 19th century</em></td>\n<td>Ancient Arabia<br /><em>Type: Geopolitical/Cultural</em></td>\n<td>Used for cultural exchanges, e.g., Arabo-Islamic civilisation. </td>\n</tr>\n<tr>\n<td><strong>Dravido-</strong><br /><em>From: Sanskrit (Dravida)</em></td>\n<td>Relating to Dravidian peoples<br /><em>Earliest Use: 19th century</em></td>\n<td>Ancient South India<br /><em>Type: Linguistic/Cultural</em></td>\n<td>Refers to Dravidian influences, often in historical or linguistic contexts. </td>\n</tr>\n<tr>\n<td><strong>Austro-</strong><br /><em>From: Latin (Auster)</em></td>\n<td>Relating to Austria or Australasia<br /><em>Earliest Use: 18th century</em></td>\n<td>Habsburg Austria<br /><em>Type: Geopolitical</em></td>\n<td>Refers to Austria (e.g., Austro-Hungarian Empire) or Australasia. </td>\n</tr>\n<tr>\n<td><strong>Helleno-</strong><br /><em>From: Greek (Hellas)</em></td>\n<td>Relating to Greek culture<br /><em>Earliest Use: 19th century</em></td>\n<td>Classical Greece<br /><em>Type: Cultural</em></td>\n<td>Refers to Hellenic traditions, often in the context of Hellenism.</td>\n</tr>\n</tbody>\n</table>\n</figure>\n<hr />\n\n<h3>What does Indo in Indo-European mean?</h3>\n<p>It refers to India, from the Greek word ‘Indos’ (not Indonesia). Indo-European covers languages from the Indian subcontinent to Europe.</p>\n<h3>Is Latin really a dead language?</h3>\n<p>Not quite. Latin survives in churches and schools, but its spoken form lost emotion and flair centuries ago.</p>\n<h3>How did Classical Latin sound?</h3>\n<p>Classical Latin was bold and musical. Think ‘KAI-sar’ not ‘SEE-zar’. Closest modern match? Sardinian.</p>\n<h3>Why do priests chant Latin in monotone?</h3>\n<p>To avoid ritual mistakes. Over time, emotion gave way to precision, turning Latin into a liturgical drone.</p>\n<h3>Is Sanskrit similar to Latin?</h3>\n<p>Yes. Both are ancient, rule-heavy, and preserved by religion. But like Latin, Sanskrit lost its conversational soul.</p>\n\n<p></p>\n<p>It refers to India, from the Greek word ‘Indos’ (not Indonesia). Indo-European covers languages from the Indian subcontinent to Europe.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Is Latin really a dead language?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Not quite. Latin survives in churches and schools, but its spoken form lost emotion and flair centuries ago.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How did Classical Latin sound?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Classical Latin was bold and musical. Think ‘KAI-sar’ not ‘SEE-zar’. Closest modern match? Sardinian.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Why do priests chant Latin in monotone?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>To avoid ritual mistakes. Over time, emotion gave way to precision, turning Latin into a liturgical drone.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Is Sanskrit similar to Latin?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Yes. Both are ancient, rule-heavy, and preserved by religion. But like Latin, Sanskrit lost its conversational soul.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 9,
                        "name": "The Geekery",
                        "slug": "the-geekery"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/cant-we-just-reset-aws/",
            "url": "https://geekist.co/cant-we-just-reset-aws/",
            "title": "Can’t we just reset AWS!?",
            "summary": "How a Stratocaster, chaotic AWS migration and calm leadership turned panic into progress. Empowerment, humour, and a reset button!",
            "image": "https://img.geekist.co/wp-content/uploads/2025/03/008ec7e7-4869-4447-9456-9a892111ba87.avif",
            "date_published": "2024-12-20T04:26:32Z",
            "date_modified": "2026-11-06T02:50:21Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tame the Tech",
                "Thinking in Code"
            ],
            "content_html": "<h2>Or how I learnt to stop worrying and start strumming a Stratocaster</h2>\n<p>There was this one time at a bank when I was brought in to help a senior dev and his sysadmin buddy solve a massive AWS migration issue. It was a porting exercise from our internal AWS setup to the bank’s heavily locked-down account. I’d never met these guys before, but technically, I was their boss. </p>\n<p>I walked in at 9 PM to find two highly flustered individuals wrestling with debugging, compiling, redoing, and checking logs in a state of sheer panic. They weren’t used to such a restricted AWS environment where they had little direct control. Meanwhile, the bank’s AWS-certified coordinator, who boasted a shiny “level 2” certification, was frantically “finding help” and acting as if he were the hero of the hour. Spoiler: he wasn’t. </p>\n<p>The first thing I noticed was a guitar. Specifically, a Stratocaster. The senior dev had brought it along, planning to hit a jam session after work. Instead, here he was, stuck at the client site, drowning in a sea of AWS policies and IAM roles. </p>\n<blockquote>\n<p>The thing that drew my attention to the Stratocaster was this thought I’ve been trying to validate for some time. </p>\n<p><em>It seemed that a ton of programmers were also musicians!</em></p>\n<p>There was my boss at the time, Francois, who was the head of engineering and had every 80’s synthesizer in his possession – that I can only ogle over. There was the CTO who was a DJ on the side (I had been a DJ for 10 years in my younger days) And now, I meet this Dev who owns a Strat – just like mine only in a different color!</p>\n</blockquote>\n<p>And so naturally, I couldn’t resist! “Hey! Is that a Strat? Wow! Can I play?” </p>\n<p>The dev and sysadmin looked at me like I had just sprouted a second head. Their expressions screamed, “Are you serious right now!?” But he said, “Sure, go ahead.” And so I did. I started strumming away, blissfully ignoring the chaos around me – or at least, that’s how it looked. </p>\n<p>Meanwhile, the two of them were losing their minds, firing off ten million questions at me in rapid succession. I just smiled and said, “Keep at it.” Then I kept playing the guitar. Ten minutes in, after quietly observing their workflow, I finally spoke up. </p>\n<p>“You’re solving one problem, and he’s solving another,” I said. “How do you know which fix worked and which one’s causing errors? It might feel like you’re slowing down, but just follow one simple rule: solve one problem at a time. No more, no less. Work together.” </p>\n<p>The disgruntled looks I got could’ve burned a hole in the back of my head. But they started doing it. One by one, they tackled problems. The questions they asked me became more focused, and I helped where it made sense. And when I wasn’t helping, I went back to the guitar. Slowly but surely, their spirits lifted, not just because they were solving things, but because they realised they could. They didn’t need me to swoop in and “fix it all.” I was just there as a safety net – or… maybe… <em>the emotional support guitarist</em></p>\n<p>But perhaps, the grandest moment of all; came about halfway through the exercise. The AWS-certified coordinator burst in and, in an exasperated tone, asked, </p>\n<p><em>“Can’t we just reset AWS?!”</em></p>\n<p>The dev and sysadmin looked up, puzzled. I started chuckling silently. Then the dev, taking his cue from me, asked, “You mean like a reset switch? Like the kind on a computer?” </p>\n<p>The coordinator nodded thoughtfully. “Yes.” </p>\n<p>Oh Lord, the laughter. We were rolling. Tears were shed. The tension melted away entirely. </p>\n<hr />\n<p>Looking back, it was one of those rare moments where everything just clicked. Not at first, though. When I walked in, I hadn’t the faintest clue what to do. I’d been sent to the frontlines like an officer with no battle plan. The atmosphere was suffocating. Management kept barging in, asking for updates, and probably sending everyone’s blood pressure through the roof. </p>\n<p>The guitar? That was my lucky break. It gave me an opening to set the tone. Management saw me playing and naturally stayed away, their sheer confusion outweighing their urge to micromanage. They left us alone because they probably thought, “The tech lead is here. Two grand a day! Things would be okay. Things <em>better be</em> okay!” </p>\n<p>For the devs, the guitar created a different kind of assurance. It signalled that everything wasn’t a five-alarm fire. That it was okay to pause, think, and solve problems methodically. The tension dialled down, and the safe space that emerged allowed them to focus. My role wasn’t to swoop in and save the day. It was to observe, provide support where needed, and keep the wolves at bay. </p>\n<p>By the end of it, they realised what my approach had been about all along. Hopefully, they spent a few days reflecting on it. The value wasn’t in me fixing anything; it was in creating an environment where they could fix it themselves. </p>\n<p>And I’ll admit, I felt pretty damn good about that. </p>\n<p>No one really knows how they’ll solve a problem until they’re standing in front of it. This was a learning experience for all of us. The guitar became a symbol, a sort of unspoken truth written on the wall: “It’s okay. The tech lead is here. There’s hope. (Erm… really?)\". I didn’t have a grand plan. I just wanted to calm things down. That alone made all the difference.</p>\n<p>I’d bet even AWS probably had a laugh at some point. </p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 10,
                        "name": "Thinking in Code",
                        "slug": "thinking-in-code"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/wildcard-ssl-and-beyond/",
            "url": "https://geekist.co/wildcard-ssl-and-beyond/",
            "title": "Nginx Wildcard SSL and Beyond",
            "summary": "A breakdown of SSL/TLS, Let's Encrypt, and Mutual SSL with Nginx, covering wildcard certs, Cloudflare integration, and advanced security configurations.",
            "image": "https://img.geekist.co/wp-content/uploads/2024/12/nginx-wildcard-ssl-and-beyond.avif",
            "date_published": "2024-12-19T19:08:16Z",
            "date_modified": "2026-02-04T21:45:29Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tame the Tech",
                "Beneath the Stack"
            ],
            "content_html": "<h2>Exploring SSL, Let’s Encrypt &amp; Cloudflare Integrations</h2>\n<p>This is the third article in the <a href=\"https://geekist.co/series/taming-nginx/\">Taming Nginx</a> series, where we explore creative ways to configure Nginx. In this article, we focus on securing your web server with SSL, wildcard certificates, and we touch on mutual SSL. </p>\n<p>So far, we’ve covered: </p>\n<ul>\n<li><a href=\"https://geekist.co/smarter-defaults-for-subdomains-and-ssl/\">Smarter Defaults for Subdomains and SSL</a> – how to organize your subdomain configuration in Nginx. </li>\n<li><a href=\"https://geekist.co/building-the-foundation/\">Why Your Web Server Structure is Holding You Back</a> – a deep dive into common folder structures and the system I’ve settled on. </li>\n<li>Wildcard SSL and Beyond – You are reading this now. </li>\n<li><a href=\"https://geekist.co/the-art-of-proxying\">The Art of Proxying: Mastering Traffic Management Like a Pro</a> – where we push Nginx to its limits with advanced and peculiar use cases in reverse proxying.</li>\n</ul>\n<p>It might be worth reading <a href=\"https://geekist.co/in-the-beginning-we-shared-whether-we-liked-it-or-not/\">In the Beginning… We Shared (whether we liked it or not!)</a> which is a light-hearted exploration of how self-hosting evolved over the decades. </p>\n<h3>What in the world is SSL and where did TLS come from?</h3>\n<p>SSL (Secure Sockets Layer) was introduced in the mid-1990s to secure internet communications but was deprecated in favour of TLS (Transport Layer Security), which is far more secure and efficient. While SSL versions are now obsolete, TLS 1.2 and 1.3 remain widely used, providing encryption, integrity, and authenticity. </p>\n<p><strong><em>Fun Fact:</em></strong> <em>“SSL” is still colloquially used to refer to TLS, even though SSL is no longer in use.</em></p>\n<p>Today, we have services like Cloudflare and Let’s Encrypt that have made securing your site or service so much easier. </p>\n<p>But this wasn’t always the case. In the early days of web hosting, you had to purchase certificates from providers at exorbitant prices, ranging from $100 to over $1,500 per year, depending on the reputation of the Certificate Authority! </p>\n<p>Thankfully, if you’re looking for the simplest way to secure your site today, <strong>Cloudflare</strong> offers an outstanding free solution. </p>\n<h3>Cloudflare</h3>\n<p>To be fair, when Cloudflare was first introduced, it didn’t yet issue certificates for your domain. That said, it was already a game-changer, excelling at protecting your site from DDoS attacks and offering useful 3rd party integrations like analytics. </p>\n<p>SSL wasn’t even part of the picture yet, but Cloudflare still stood out as a critical tool for website owners. </p>\n<p>The way it worked was simple: you’d buy a domain from a registrar of your choice, then point your domain’s name servers (NS Records) to Cloudflare. </p>\n<p>This allowed Cloudflare to act as your DNS provider and deliver its features seamlessly. </p>\n<p>Perhaps the biggest benefit? You didn’t have to pay a cent. And when Cloudflare introduced automated SSL provisioning, it added a layer of security that elevated its value to an entirely new level. </p>\n<p>At the time of this article, there’s still no service quite like it that offers so much – for free. </p>\n<h4>Getting Started with Cloudflare</h4>\n<p>Setting up Cloudflare for your domain is straightforward: </p>\n<ol>\n<li><strong>Sign Up</strong>: Create a free Cloudflare account. </li>\n<li><strong>Add Your Domain</strong>: Register your domain with Cloudflare and follow the step-by-step instructions to configure DNS settings. </li>\n<li><strong>Update Your Name Servers</strong>: Point your domain’s name servers (NS Records) to Cloudflare as directed during setup.</li>\n</ol>\n<p>And that’s it, really! Once you’ve completed the setup, you’ll have <strong>DDoS protection</strong> and <strong>SSL out of the box</strong>. However, Cloudflare offers a few options that are worth mentioning to get the most out of your configuration. </p>\n<p><strong>DNS Proxied vs. DNS Only</strong></p>\n<p>When a record is Proxied, traffic is routed through Cloudflare’s network, allowing it to leverage DDoS protection, caching, and SSL termination. On the other hand, a DNS Only record directs traffic straight to your origin server, completely bypassing Cloudflare. This is typically used for services like mail servers or anything that doesn’t work well with Cloudflare’s proxy. </p>\n<p>Cloudflare provides several SSL modes based on different security needs. </p>\n<p>The <em>Off</em> mode disables SSL entirely which not recommended unless you know what you’re doing. </p>\n<p>The <em>Flexible</em> option encrypts traffic between the browser and Cloudflare but leaves communication with the origin server unencrypted, making it less secure. </p>\n<p>The <em>Full</em> mode ensures encryption from end to end but does not validate the origin server’s certificate. Finally, Full (Strict) is the most secure setting, encrypting traffic end-to-end while also validating the origin server’s certificate. </p>\n<p>For a fully secure setup, always aim for <strong>Full (Strict)</strong> SSL mode if your origin server has a valid certificate (such as one issued by Let’s Encrypt or your own CA). While Cloudflare simplifies SSL for many scenarios, it’s worth knowing how to use Certbot to issue your own certificates, which we’ll dive into next. </p>\n<h3>Certbot</h3>\n<p>Let’s Encrypt revolutionized SSL provisioning by making certificates free and accessible to everyone. At the heart of this process is <code>certbot</code>, a powerful CLI tool that automates certificate issuance and renewal.</p>\n<p><strong><em>Fun Fact:</em></strong> <code>certbot</code><em>—the CLI tool—used to be known as</em> <code>letsencrypt</code> <em>and was really annoying to type out each time! The rebranding was more than welcome, not to mention its expanded capabilities.</em></p>\n<p>There are many tutorials on using Certbot to provision single-domain certificates, so this guide focuses on wildcard certificates. These simplify SSL management by covering all subdomains of a domain, making them ideal for scalable and dynamic setups. </p>\n<h4>Getting Started with Let’s Encrypt</h4>\n<p>Let’s set up Certbot on Ubuntu with Nginx to automate SSL provisioning. If your configuration differs, the <a href=\"https://certbot.eff.org/instructions\">Certbot interactive guide</a> is a great resource. We’ll focus on the basics: </p>\n\n<pre># Update your package list and install snapd (if not already installed)\nsudo apt update\nsudo apt install snapd\n\n# Install Certbot using snap\nsudo snap install --classic certbot\n\n# Verify Certbot installation\ncertbot --version\n\n# If certbot isn't found, create a symlink to the binary\nsudo ln -s /snap/bin/certbot /usr/bin/certbot\n\n# Allow Certbot to use plugins with root access\nsudo snap set certbot trust-plugin-with-root=ok\n\n# Install Certbot's Cloudflare DNS plugin\nsudo snap install certbot-dns-cloudflare</pre>\n<p><strong>To get a Cloudflare API Token:</strong></p>\n<p>→ <a href=\"https://dash.cloudflare.com/profile/api-tokens\">API Tokens in Cloudflare’s Dashboard</a> → <strong>Create Token</strong> → Use the <code>Edit zone DNS</code> template → Select the domain (zone) you want to manage → Copy the token and save it securely.</p>\n<p>On your machine, create a <code>cloudflare.ini</code> file:</p>\n\n<pre># Cloudflare API token used by Certbot\ndns_cloudflare_api_token = &lt;your token&gt;</pre>\n<p>Save the file in a secure location and set its permissions: </p>\n\n<pre># use sudo depending on where you save it.\nchmod 600 ./cloudflare.ini</pre>\n<p>And now it’s time to generate the wildcard certificate: </p>\n\n<pre>certbot certonly \n  --dns-cloudflare \n  --dns-cloudflare-credentials ~/.secrets/certbot/cloudflare.ini \n  -dns-cloudflare-propagation-seconds 60 \n  -d example.com \n  -d *.example.com</pre>\n<p>The command may take a minute due to the DNS propagation delay, but once complete, your certificates will be saved to: </p>\n<ul>\n<li><strong>Certificate:</strong> <code>/etc/letsencrypt/live/</code><a href=\"http://example.com/fullchain.pem\"><code>example.com/fullchain.pem</code></a></li>\n<li><strong>Private Key:</strong> <code>/etc/letsencrypt/live/</code><a href=\"http://example.com/privkey.pem\"><code>example.com/privkey.pem</code></a></li>\n</ul>\n<h4>Nginx Integration</h4>\n<p>Remember the handy <code>ssl_params</code> file from the <a href=\"https://geekist.co/smarter-defaults-for-subdomains-and-ssl/\">first article</a>? That’s where you’ll update the certificate paths with the locations generated above.</p>\n<p>To illustrate how this works, here’s a <strong>minimal example</strong> of an Nginx configuration for a subdomain: </p>\n\n<pre># File: /etc/nginx/sites-available/freebies.example.com\nserver {\n    listen 443 ssl;\n    listen [::]:443 ssl;\n    server_name freebies.example.com;\n    root /srv/freebies.example.com/;\n    index index.html;\n    # SSL Configuration is the same for every subdomains thanks the\n    # wildcard certificate\n    include /etc/nginx/ssl_params;\n    # Serve files and directories, or return 404\n    location / {\n        try_files $uri $uri/ =404;\n    }\n}</pre>\n<p>This example illustrates how the wildcard certificate makes SSL configuration consistent across subdomains. With this foundation in place, let’s take it a step further and explore enabling Mutual SSL for secure system-to-system communication. </p>\n<h3>Mutual SSL</h3>\n<p>Before APIs were everywhere, developers relied on simpler methods like API keys or IP whitelisting to secure system-to-system communication. Mutual SSL improves on this by verifying both the client and server using certificates, ensuring trust at the system level. </p>\n<p>It’s important to note that Mutual SSL verifies requests at the transport layer and does not replace user-level authentication methods like OAuth or passwords. </p>\n<h4>How to Do It with Nginx</h4>\n<p>Let’s take a hypothetical scenario where you want to establish Mutual SSL with two of your subdomains: </p>\n<ul>\n<li><a href=\"http://api.example.com/\"><code>api.example.com</code></a>: Your API service </li>\n<li><a href=\"http://client.example.com/\"><code>client.example.com</code></a>: Your WebApp that calls the API for data</li>\n</ul>\n<p>Since we’ve already created a wildcard certificate earlier for browser-level verification, that setup remains unchanged. Here, we’ll generate additional certificates specifically for Mutual SSL using OpenSSL: </p>\n<p><em>For a production-grade guide on setting this up, be sure to check out</em> <em>Nginx’s Documentation</em></p>\n\n<pre># Create a custom CA certificate and private key\nopenssl req -new -x509 -days 365 -nodes -out ca.crt -keyout ca.key\n# Generate a private key and CSR (Certificate Signing Request) for the client\nopenssl req -new -nodes -out client.csr -keyout client.key\n# Sign the CSR with the CA to create the client certificate\nopenssl x509 \n  -req \n  -in client.csr                # Input: Client CSR\n  -CA ca.crt                    # CA certificate\n  -CAkey ca.key                 # CA private key\n  -CAcreateserial               # Generate a serial number for the certificate\n  -out client.crt               # Output: Client certificate\n  -days 365                      # Valid for 365 days</pre>\n<p><strong>Server Configuration for</strong> <a href=\"http://api.example.com/\"><code>api.example.com</code></a></p>\n<p>Update the configuration for <a href=\"http://api.example.com/\"><code>api.example.com</code></a> to include Mutual SSL settings: </p>\n\n<pre># File: /etc/nginx/sites-available/api.example.com\nserver {\n    listen 443 ssl;\n    listen [::]:443 ssl;\n    server_name api.example.com;\n    root /srv/api.example.com/;\n    index index.html;\n    # Include wildcard certificate\n    include /etc/nginx/ssl_params;\n    # Mutual SSL settings\n    ssl_client_certificate /path/to/ca.crt;\n    ssl_verify_client on;\n    location / {\n        # Enforce client verification by leveraging ssl_verify_client\n        error_page 495 = /error/missing_or_invalid_client_cert;\n        try_files $uri $uri/ =404;\n    }\n    # Custom error for missing or invalid certificates\n    location = /error/missing_or_invalid_client_cert {\n        return 403 \"mTLS certificate missing or invalid\";\n    }\n}</pre>\n<p><strong>Client Configuration for</strong> <a href=\"http://client.example.com/\"><code>client.example.com</code></a></p>\n<p>To connect securely to the API, configure the <a href=\"http://client.example.com/\"><code>client.example.com</code></a> subdomain to use the generated certificates: </p>\n\n<pre># File: /etc/nginx/sites-available/client.example.com\nserver {\n    listen 443 ssl;\n    listen [::]:443 ssl;\n    server_name client.example.com;\n    root /srv/client.example.com/;\n    index index.html;\n    # Include wildcard certificate\n    include /etc/nginx/ssl_params;\n    # Configure Mutual SSL for outgoing requests to api.example.com\n    location /api/ {\n        proxy_pass https://api.example.com;\n        proxy_ssl_certificate /path/to/client.crt;\n        proxy_ssl_certificate_key /path/to/client.key;\n        proxy_ssl_trusted_certificate /path/to/ca.crt;\n    }\n}</pre>\n<h4>Verification Steps</h4>\n<p>Let’s make sure everything is configured correctly by testing NGINX and verifying the API endpoint. </p>\n\n<pre># Test the NGINX configuration for syntax errors\nsudo nginx -t\n# Reload NGINX to apply changes (use restart if significant changes were made)\nsudo service nginx reload # or restart\n# Verify the API with the client certificate and key\ncurl --cert /path/to/client.crt --key /path/to/client.key https://api.example.com</pre>\n<p>If everything is set up correctly, the <code>nginx -t</code> test should pass, and the <code>curl</code> command should return a valid response from the API. If something’s off, check Nginx’s <code>access.log</code> or <code>error.log</code> for SSL-related issues or misconfigurations.</p>\n<p>Finally, open <a href=\"http://client.example.com/\"><code>client.example.com</code></a> in your browser and ensure the WebApp loads without SSL warnings. No red screens? Perfect! Mutual SSL is up and running while keeping browser compatibility intact! </p>\n<p>I didn’t anticipate this article being so detailed, but I wanted to share a bit more depth compared to the usual guides out there. This wasn’t meant to be a quick copy-paste style tutorial so I hope you found it informative and useful. </p>\n<p>So far, we’ve explored three articles in the <a href=\"https://geekist.co/series/taming-nginx/\">Taming Nginx</a> series, and next up, we’ll dive into some Advanced Caching and Scaling Techniques. Stay tuned, and don’t forget to subscribe to the newsletter below to get the latest updates. </p>\n<p>Cheers! </p>\n<blockquote>\n<p>Like your SSL served wild and on a subdomain platter?<br /><strong><em><a href=\"https://geekist.co/nginx-by-example/\">Nginx by Example Vol. 1</a></em></strong> and make your server cry tears of joy.</p>\n</blockquote>\n<hr />\n\n<h3>What is the difference between SSL and TLS?</h3>\n<p>SSL was the original encryption protocol, but it’s now deprecated. TLS is the secure replacement, with versions 1.2 and 1.3 still in wide use today.</p>\n<h3>How to set up Cloudflare SSL for free?</h3>\n<p>Sign up for Cloudflare, add your domain, update your name servers, and choose Full (Strict) SSL mode for end-to-end encryption with certificate validation.</p>\n<h3>How do I generate a wildcard SSL with Certbot and Cloudflare?</h3>\n<p>Use Certbot with the Cloudflare DNS plugin and a valid API token to issue wildcard certificates. It automates the DNS challenge needed for verification.</p>\n<h3>How to set up mutual SSL in Nginx?</h3>\n<p>Generate your own CA, sign client certificates, and use ssl_verify_client with Nginx to require verification on the server and client side.</p>\n<h3>What is Full Strict SSL mode in Cloudflare?</h3>\n<p>Sometimes, yes. Presence, intuition, and creating a safe space for the team to Full (Strict) SSL encrypts traffic from browser to Cloudflare and from Cloudflare to your origin server, while verifying your origin has a valid certificate.</p>\n\n<p></p>\n<p>SSL was the original encryption protocol, but it’s now deprecated. TLS is the secure replacement, with versions 1.2 and 1.3 still in wide use today.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How to set up Cloudflare SSL for free?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Sign up for Cloudflare, add your domain, update your name servers, and choose Full (Strict) SSL mode for end-to-end encryption with certificate validation.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How do I generate a wildcard SSL with Certbot and Cloudflare?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Use Certbot with the Cloudflare DNS plugin and a valid API token to issue wildcard certificates. It automates the DNS challenge needed for verification.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How to set up mutual SSL in Nginx?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Generate your own CA, sign client certificates, and use ssl_verify_client with Nginx to require verification on the server and client side.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What is Full Strict SSL mode in Cloudflare?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Sometimes, yes. Presence, intuition, and creating a safe space for the team to Full (Strict) SSL encrypts traffic from browser to Cloudflare and from Cloudflare to your origin server, while verifying your origin has a valid certificate.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/building-the-foundation/",
            "url": "https://geekist.co/building-the-foundation/",
            "title": "Why Your Web Server Structure is Holding You Back (And How to Fix It)",
            "summary": "A practical look at organizing web server folders, from `/srv` structures to centralizing logs and configs designed for scalability and security.",
            "image": "https://img.geekist.co/wp-content/uploads/2024/12/why-your-web-server-structure-is-holding-you-back-and-how-to-fix-it.avif",
            "date_published": "2024-12-18T18:08:05Z",
            "date_modified": "2026-02-04T21:45:30Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tame the Tech",
                "Beneath the Stack"
            ],
            "content_html": "<h2>Best Practices for Folder Structures for your web server</h2>\n<p>In the previous <a href=\"https://geekist.co/smarter-defaults-for-subdomains-and-ssl/\">article</a>, I talked about how to manage your sub-domain setup with Nginx in a streamlined way. In this one, we’ll dive into common approaches to structuring folders on your server and share the system I’ve settled on. </p>\n<p>🔹 You’re reading the second article in the <a href=\"https://geekist.co/series/taming-nginx/\">Taming Nginx</a> series, where we refine conventions and make managing Nginx a seamless experience. </p>\n<p>Other Articles in This Series: </p>\n<ul>\n<li><a href=\"https://geekist.co/smarter-defaults-for-subdomains-and-ssl/\">Smarter Defaults for Subdomains and SSL</a> – how to organise your subdomain configuration in Nginx. </li>\n<li>Why Your Web Server Structure is Holding You Back (And How to Fix It) – You are reading this now. </li>\n<li><a href=\"https://geekist.co/wildcard-ssl-and-beyond/\">Wildcard SSL and Beyond</a> – where we explore how to secure your web server with SSL, wildcard certificates, and mutual SSL. </li>\n<li><a href=\"https://geekist.co/the-art-of-proxying\">The Art of Proxying: Mastering Traffic Management Like a Pro</a> – where we push Nginx to its limits with advanced and peculiar use cases in reverse proxying.</li>\n</ul>\n<p>Traditionally, most web roots are located within <code>/var/www/html</code>, a specific folder designated to house all files related to your web app. This directory is owned by <code>root:root</code>, requiring <code>sudo</code> privileges to make changes.</p>\n<p>This design choice seems intentional. By requiring <code>sudo</code> for every modification, you’re compelled to pause and think carefully about changes to this critical directory.</p>\n<p>Security plays a significant role here too: </p>\n<p><em>You don’t want to accidentally delete or corrupt your WordPress</em> <code>wp-config.php</code> <em>if you have a live site serving thousands of users!</em></p>\n<p>For my setup, I prefer using <code>/srv</code> as the root for my web projects. The <code>/srv</code> directory is explicitly designed for service-related data, making it ideal for hosting multiple applications or services. It promotes clarity and adheres to the Filesystem Hierarchy Standard (FHS).</p>\n<p>By keeping project files here, you ensure better organization and scalability. Be sure to secure sensitive files like <code>.bashrc</code> and <code>.ssh</code> to prevent accidental exposure to the web.</p>\n<p>The approach I’ll outline in this guide works equally well whether you choose <code>/srv</code>, <code>/home</code>, <code>/var/www</code>, or any other web root you’re comfortable with.</p>\n<blockquote>\n<p>Before we dive in, it’s worth mentioning that although this article is part of the <a href=\"https://geekist.co/series/taming-nginx/\">Taming Nginx</a> series, the folder structure principles discussed here apply universally. Whether you’re using Nginx, Apache, Lighttpd, or even Node.js, the organizational practices outlined will serve you well.</p>\n</blockquote>\n<h3>The problem with <code>/var/www/html</code></h3>\n<p>It’s the name! <code>html/</code> implies that all files here are only ever related to what you’re serving over https, but where do the project files go?</p>\n<p>Because of this, I’ve encountered numerous variations. Some folks clone an entire project repo directly into this location. Others might have the <code>.git</code> repo within their home directories and only the compiled files get dumped into <code>html/</code></p>\n<p>And very often you find yourself thinking, should I commit, pull, compile, then <code>sudo mv</code> the entire folder back into <code>/var/www/html</code> – or should I just make that <em>tiny little edit</em> to that one file.</p>\n<p><em>I’m fairly certain you’ve never done the latter! 😉</em></p>\n<p>In fairness though, this is why we have things like Github Actions and similar, just so you never have to think about <code>sudo</code>-ing anything and wreck your brain doing it.</p>\n<p>Also, as you’ll find in 99.9% of the tutorials out there, one still has to <code>sudo chgrp -R www-data /var/www/html</code> or sometimes even <code>chown</code> the whole thing just so your web server has access to it.</p>\n<p>If project files are also in this directory, that’s already a bad practice because it means that if an attacker managed to compromise security and get into the root of your site, they’d have access to all files located in it. </p>\n<p>But truthfully, attacks are generally far more advanced these days – although there are bots written specifically to exploit this security flaw that will visit your site every day! </p>\n<h3>What I do.</h3>\n<p>The way I see it? If you’re going to clone a repo anyway, just use <code>/srv</code>. Here’s what mine typically looks like:</p>\n\n<pre>/srv/: tree -L 1\n.\n├── auth.example.com\n├── blog.example.com\n├── downloads.example.com</pre>\n<p>In each directory, your web root can be named according to any convention you like. <code>webroot</code>, <code>public</code> or simply just <code>app</code>. This directory is what you <code>chgrp</code> to <code>www-data</code>.</p>\n<p>It’s worth mentioning that the web root is not always needed. Especially if you’re using <code>docker</code>  to manage the backend service.</p>\n<p>Even if you are using docker, containing them into subdomain directories has its benefits: </p>\n<ol>\n<li><code>/logs</code>: A central location for all the logs related to this app\n<ul>\n<li>Some apps have configurable log paths, and here’s where you’d want to see them.</li>\n<li>I’d also add Nginx’s <code>access</code> and <code>error</code> logs here too, but more on that in a bit.</li>\n</ul>\n</li>\n<li><code>/config</code>: A central location for all configuration files for this app\n<ul>\n<li>This is where your <code>toml</code>, <code>yaml</code>, <code>json</code> etc config files go</li>\n<li>For me, I’d add the <code>nginx.conf</code> here too</li>\n</ul>\n</li>\n</ol>\n<p>As mentioned, if using docker, you’d typically have a <code>docker-compose.yml</code> here. If not, you’d likely want to have some sort of <code>start</code> script – unless you are managing the service as a startup script – which is also a great practice.</p>\n<p>For added security, feel free to change the permissions and ownership of the files in the config directory so that only you have access to it but make sure that <code>nginx.conf</code> is still owned by the <code>www-data</code> group. Here’s a minimal example of what that looks like:</p>\n\n<pre># File: /srv/blog.example.com/config/nginx.conf\nserver {\n    listen 443 ssl http2;\n    listen [::]:443 ssl http2;\n    server_name blog.example.com;\n    # if using docker-compose, this will be mounted to the public \n    # root of container\n    root /srv/blog.example.com/app;\n    index index.html;\n    # Logging\n    access_log /srv/blog.example.com/logs/access.log;\n    error_log /srv/blog.example.com/logs/error.log;\n    # SSL Configuration\n    include /etc/nginx/ssl_common;\n    location ~* .(jpg|jpeg|png|gif|ico|css|js)$ {\n        expires max;\n        add_header Cache-Control \"public\";\n    }\n    # Serve files and directories, or return 404\n    location / {\n        # If using docker to serve your app, use your proxy\n        # configuration instead\n        try_files $uri $uri/ =404;\n    }\n}</pre>\n<p>And then all you have to do is: </p>\n\n<pre># Create a symlink to sites-enabled\nsudo ln -s /srv/blog.example.com/config/nginx.conf /etc/nginx/sites-enabled\n\n# test that your configuration works\nsudo nginx -t\n\n# reload the service\nsudo service nginx reload\n\n# check the status of the service\nsudo service nginx status\n\n# finally, curl your website to see that everything works\ncurl -L blog.example.com\ncurl -i https://blog.example.com</pre>\n<h3>Let’s break down the benefits of this approach</h3>\n<ol>\n<li>Your logs are centralized per app. If you’re running multiple services on a single machine, this becomes very helpful in locating the root of the problem. </li>\n<li>Docker Compose scenarios will probably still be related to a single public service offering. This structure can also transition well to more advanced setups, like multi-server environments, where directories can be synced or mirrored for scalability:\n<ul>\n<li>Rename the parent directory to something specific that makes sense for both services </li>\n<li>Split the docker compose file per service</li>\n</ul>\n</li>\n<li>Nginx configuration located here and symlinked to <code>sites-available</code> makes it easy to understand what’s going on and you still have the added benefit of enabling or disabling the service.</li>\n</ol>\n<p>There’s more you can do of course. You can symlink <code>sites-enabled</code> to the root directory too, just so you can quickly see what’s in there:</p>\n<p><code>sudo ln -s /etc/nginx/sites-enabled /srv</code></p>\n<p>If you feel creating directories like this becomes a chore for every domain, I’ve written a utility called <code>Skeletor</code> for this purpose:</p>\n<ul>\n<li><a href=\"https://github.com/seriouslyjs/skeletor\">Skeletor JS</a> : A cli tool written in Node.js. </li>\n<li><a href=\"https://github.com/theGeekist/skeletor\">Skeletor</a>: The same tool written in Rust.</li>\n</ul>\n<p>As I mentioned before, I’m in the second year of using <a href=\"https://my.racknerd.com/aff.php?aff=13317\">RackNerd as my super low-priced VPS</a>, so they are worth checking out! </p>\n<h4>Where we go from here:</h4>\n<p>If you read <a href=\"https://geekist.co/smarter-defaults-for-subdomains-and-ssl/\">the previous article</a> in the series <a href=\"https://geekist.co/series/taming-nginx/\">Taming Nginx</a>, you’d see how this one is a natural progression to the conventions described there. In the next article, we’ll explore SSL cert creation and renewal automation with <code>certbot</code> and <code>cloudflare</code>!</p>\n<p>I’d also be talking about <code>Skeletor</code> in detail in an upcoming post and hopefully, the Readme gives you enough context in the meantime.</p>\n<p>Hope this article gave you insight and creative ideas for folder organisation. Until next time, cheers! </p>\n<hr />\n\n<h3>Should I use /srv instead of /var/www?</h3>\n<p>/srv is a cleaner choice for hosting multiple web apps; it's meant for service data and avoids cluttering system folders like /var/www.</p>\n<h3>What’s wrong with using /var/www/html?</h3>\n<p>The html folder implies static files only, but many devs mix project code there, which risks accidental edits and poor security practices.</p>\n<h3>How to structure folders for Nginx sites?</h3>\n<p>Use one directory per subdomain under /srv, and split into /app, /logs, and /config. Symlink nginx.conf from /config to sites-enabled.</p>\n<h3>Where should Nginx logs go?</h3>\n<p>Put access and error logs in a /logs folder per app, e.g. /srv/blog.example.com/logs - keeps things clean and easy to debug.</p>\n<h3>How to link Nginx config from custom folder?</h3>\n<p>Just symlink the config: <code>sudo ln -s /srv/domain.com/config/nginx.conf /etc/nginx/sites-enabled</code>, then reload Nginx.</p>\n\n<p></p>\n<p>/srv is a cleaner choice for hosting multiple web apps; it's meant for service data and avoids cluttering system folders like /var/www.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What’s wrong with using /var/www/html?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>The html folder implies static files only, but many devs mix project code there, which risks accidental edits and poor security practices.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How to structure folders for Nginx sites?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Use one directory per subdomain under /srv, and split into /app, /logs, and /config. Symlink nginx.conf from /config to sites-enabled.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Where should Nginx logs go?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Put access and error logs in a /logs folder per app, e.g. /srv/blog.example.com/logs - keeps things clean and easy to debug.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How to link Nginx config from custom folder?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Just symlink the config: <code>sudo ln -s /srv/domain.com/config/nginx.conf /etc/nginx/sites-enabled</code>, then reload Nginx.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    }
                ],
                "references": {
                    "mentions_mcp": false,
                    "github_links": [
                        "https://github.com/seriouslyjs/skeletor",
                        "https://github.com/theGeekist/skeletor"
                    ],
                    "public_product_links": [],
                    "public_products": []
                }
            }
        },
        {
            "id": "https://geekist.co/smarter-defaults-for-subdomains-and-ssl/",
            "url": "https://geekist.co/smarter-defaults-for-subdomains-and-ssl/",
            "title": "Smarter Defaults for Subdomains and SSL",
            "summary": "Tame Nginx with smarter defaults! Learn how to simplify subdomains, SSL, and streamline your configs for secure…",
            "image": "https://img.geekist.co/wp-content/uploads/2025/03/46b5a441-5b8a-4169-8e0b-7d7e54e692c4.avif",
            "date_published": "2024-12-17T22:03:21Z",
            "date_modified": "2026-10-29T22:19:29Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tame the Tech",
                "Beneath the Stack",
                "Where the User Begins"
            ],
            "content_html": "<h2>A focused guide to streamlining global subdomains and SSL</h2>\n<p>Over the decades, I’ve developed a convention for working with Nginx that simplifies subdomains and SSL. While there’s no shortage of broad tutorials on Nginx, I’ve often wondered: <em>why are so many processes still so manual?</em></p>\n<p>More importantly, why aren’t Nginx’s defaults being exploited to their full potential? </p>\n<p>🔹 This is the first in the <a href=\"https://geekist.co/series/taming-nginx/\">Taming Nginx</a> series, where I’ll explore <strong>smarter, more intentional configurations</strong> that streamline workflows and enhance performance. </p>\n<p>In this article, we’ll focus on <strong>globally managed subdomains and SSL</strong>. </p>\n<p>Other Articles in This Series: </p>\n<ul>\n<li>Smarter Defaults for Subdomains and SSL – You are reading this now. </li>\n<li><a href=\"https://geekist.co/building-the-foundation/\">Why Your Web Server Structure is Holding You Back</a> – where I suggest a folder structure that I use to manage multiple domains and services. </li>\n<li><a href=\"https://geekist.co/wildcard-ssl-and-beyond/\">Wildcard SSL and Beyond</a> – where we explore how to secure your web server with SSL, wildcard certificates, and mutual SSL. </li>\n<li><a href=\"https://geekist.co/the-art-of-proxying\">The Art of Proxying: Mastering Traffic Management Like a Pro</a> – where we push Nginx to its limits with advanced and peculiar use cases in reverse proxying.</li>\n</ul>\n<p>Let’s skip the repetitive setups and turn Nginx into the efficient powerhouse it’s meant to be. </p>\n<p>In a typical nginx installation folder <code>/etc/nginx</code>, you’d find an <code>nginx.conf</code> file which specifies the <code>http</code> block.</p>\n<p>This is where all the magic of nginx happens. </p>\n<p><em>You’d also see an</em> <code>events</code> <em>block, but we’ll talk about that in future posts</em></p>\n<p>The <code>http</code> block is where global defaults are declared. Things like compression and which Nginx modules to load are defined here. As you’ll see, this file can get very verbose, very quickly.</p>\n<p>Fortunately, Nginx includes an <code>include</code> directive, which allows you to modularise configurations by including other files or folders.</p>\n<p>In almost every default Nginx configuration, you’ll see something like this near the end of the <code>http</code> block:</p>\n\n<pre>http {\n    # ...other directives\n    ##\n    # Virtual Host Configs\n    ##\n    include /etc/nginx/conf.d/*.conf;\n    include /etc/nginx/sites-enabled/*;\n}\n</pre>\n<p>Most tutorials gloss over this, but if you’re a discerning sort, you might notice some very specific details: </p>\n<ol>\n<li><code>include /etc/nginx/conf.d/*.conf;</code>: Notice how it’s loading any and all files in the <code>conf.d</code> directory that end with a <code>.conf</code> extension?</li>\n<li><code>include /etc/nginx/sites-enabled/*;</code>: Unlike <code>conf.d</code>, this one loads all files in <code>sites-enabled</code>, regardless of their extension.</li>\n</ol>\n<p>But why? And why in that order? </p>\n<p>Besides offering obvious flexibility in naming your domains, subdomains, or other server blocks, this order ensures that files in <code>conf.d</code> are loaded <strong>first</strong>.</p>\n<p>This is intentional, and it’s a good thing. </p>\n<p>Typically, <code>conf.d</code> is used to specify global or module-specific defaults, but it also opens up some creative possibilities – which I’ll illustrate below.</p>\n<p>The default HTTP config </p>\n<p>Now that we understand how <code>conf.d</code> is loaded first, let’s explore how it ties in to the <strong>default HTTP configuration</strong>.</p>\n<p>In a typical Nginx setup, you’ll find this file in <code>/etc/nginx/sites-enabled/default</code>. Look closely, and you’ll notice it’s actually a symbolic link to the original file in <code>/etc/nginx/sites-available/default</code>.</p>\n<p>This is by design – it allows you to easily load or unload configurations without permanently deleting the file. </p>\n<p>If you open this file in your editor, you’ll see it contains a mix of commented-out examples and configuration blocks. </p>\n<p>While these examples can be useful later, let’s start fresh: unlink it, back it up, and create a clean slate for our <strong>default</strong> config. </p>\n\n<pre># remove the symlink\nsudo unlink /etc/nginx/sites-enabled/default\n# backup the original file\nsudo mv /etc/nginx/sites-available/default /etc/nginx/sites-available/default.bak\n# create an empty configuration file\nsudo touch /etc/nginx/sites-available/default\n# link this new one back to sites-enabled\nsudo ln -s /etc/nginx/sites-available/default /etc/nginx/sites-enabled/default</pre>\n<p>Once you’ve done this, your <strong>default</strong> file is ready for a fresh configuration. And here’s where it might surprise you: </p>\n<p><em>My default configuration contains just one directive</em></p>\n\n<pre>server {\n    listen 80;\n    listen [::]:80;\n    server_name _;\n    # Redirect all HTTP requests to HTTPS with a 301 Moved Permanently response.\n    return 301 https://$host$request_uri;\n}</pre>\n<p>I use this minimalist configuration across every cloud machine, VM, and VPS server I set up. Here’s why: </p>\n<h3>Default to HTTPS, not HTTP</h3>\n<ol>\n<li>By redirecting all HTTP traffic to HTTPS, you no longer need to wonder if a subdomain is insecure -everything defaults to HTTPS, which is great practice. </li>\n<li>This eliminates the need to configure HTTP blocks for individual subdomains. Everything follows the same rule by default, saving time and reducing complexity. </li>\n<li>If you ever need an exception (e.g., for testing purposes), you can still use an <code>if</code> block within a specific server or location block to short-circuit routing for just that one subdomain.</li>\n</ol>\n<p>By making HTTPS the default and treating HTTP as an <strong>explicit exception</strong>, this approach ensures secure, intentional configurations with minimal effort. </p>\n<p><em>Wait – did I say</em> <code>if</code> <em>block?</em></p>\n<p>I did! And if that feels a bit hackish (don’t worry, purists), this is exactly why we talked about <code>conf.d</code>. You see, when HTTPS is your default, your brain is wired to treat HTTP traffic as an <strong>exception</strong>, just as it should be.</p>\n<p><em>Okay, that’s an easy fix, we’ll just create a new config in sites-available. Right?</em></p>\n<p>The obvious solution for an HTTP exception might look like this: </p>\n\n<pre># File: /etc/nginx/sites-available/blog.example.com\nserver {\n    listen 80;\n    listen [::]:80;\n    server_name blog.example.com;\n    location / {\n    # specify directives here.\n    }\n}</pre>\n<p>And this would work – as long as the server name (<a href=\"http://blog.example.com/\"></a>) loads <strong>before</strong> <code>default</code> alphabetically. But what happens if your subdomain is <a href=\"http://freebies.example.com/\"><code>freebies.example.com</code></a>?</p>\n<p>In that case, <code>default</code> is loaded <strong>first</strong> (alphabetically) and redirects all traffic to HTTPS before Nginx even evaluates <a href=\"http://freebies.example.com/\"><code>freebies.example.com</code></a>. This makes your HTTP exception ineffective.</p>\n<h3>The <code>conf.d</code> Solution</h3>\n<p>This is why HTTP exceptions belong in the <code>conf.d</code> folder. By placing them here, they are loaded <strong>before anything in</strong> <code>sites-enabled</code>, ensuring they take precedence over the default HTTPS redirect.</p>\n<p>For clarity, you can organise exceptions into a sub-directory within <code>conf.d</code>, like <code>http_exceptions</code>, and name the file to match the subdomain:</p>\n<p><code>/etc/nginx/conf.d/http_exceptions/</code><a href=\"http://freebies.example.com/\"><code>freebies.example.com</code></a><code>.conf</code></p>\n<p><strong>Example Configuration:</strong></p>\n\n<pre># File: /etc/nginx/conf.d/http_exceptions/freebies.example.com.conf\nserver {\n    listen 80;\n    listen [::]:80;\n    server_name freebies.example.com;\n    location / {\n        # Specify directives here\n    }\n}</pre>\n<p>By placing HTTP exceptions in <code>conf.d/http_exceptions</code>, you:</p>\n<ol>\n<li><strong>Ensure Proper Load Order</strong>: HTTP exceptions are processed before the default HTTPS redirect. </li>\n<li><strong>Align with the Convention</strong>: Deviations from the HTTPS default are treated as deliberate exceptions, and their placement in <code>conf.d</code> reflects their special status.</li>\n</ol>\n<h4>Why This Approach Rocks</h4>\n<p>This structure makes your configurations: </p>\n<ul>\n<li><strong>Predictable</strong>: HTTPS is the default. Anything in <code>conf.d/http_exceptions</code> stands out as intentional.</li>\n<li><strong>Modular</strong>: Exceptions are isolated, simplifying management without affecting <code>sites-enabled</code>.</li>\n<li><strong>Secure by Default</strong>: HTTP is an edge case, with everything else defaulting to secure HTTPS. </li>\n<li><strong>Easy to Identify</strong>: Remember nginx loads only <code>.conf</code> files here? This file is named <a href=\"http://freebies.example.com/\"><code>freebies.example.com</code></a><code>.conf</code> allowing you to make a distinction from the file named <a href=\"http://freebies.example.com/\"><code>freebies.example.com</code></a> in <code>sites-available</code></li>\n</ul>\n<p><em>Okay, then what’s in</em> <code>/etc/nginx/sites-available/</code><a href=\"http://freebies.example.com/\"><code>freebies.example.com</code></a>?</p>\n<p>Everything you need for your HTTPS site – but let’s start with a <strong>minimal setup</strong> for clarity </p>\n\n<pre>server {\n    listen 443 ssl http2;\n    listen [::]:443 ssl http2;\n    server_name freebies.example.com;\n    root /srv/freebies.example.com/;\n    index index.html;\n    # SSL Configuration\n    include /etc/nginx/ssl_params;\n    # Serve files and directories, or return 404\n    location / {\n        try_files $uri $uri/ =404;\n    }\n}</pre>\n<p>Yes, if you swapped <code>443</code> for <code>80</code> and removed <code>ssl</code>, it would look no different from a typical HTTP server block. That simplicity is deliberate and made possible with <code>include /etc/nginx/ssl_params;</code></p>\n<p><em>But isn’t specifying a separate file like</em> <code>ssl_params</code> overkill for a single domain?</p>\n<p>It certainly is – if you’re managing just one domain, but this setup is perfect for <strong>wildcard domain certificates</strong>, allowing you to scale efficiently across all your subdomains. Here’s what it looks like: </p>\n\n<pre># ssl_params for wildcard certs\nssl_certificate /etc/ssl/certs/example_com.crt;\nssl_certificate_key /etc/ssl/private/example_com.key;\nssl_protocols TLSv1.2 TLSv1.3;\nssl_prefer_server_ciphers on;\nssl_ciphers EECDH+AESGCM:EDH+AESGCM;\nssl_session_cache shared:SSL:10m;\nssl_session_timeout 10m;\nssl_stapling on;\nssl_stapling_verify on;\nresolver 8.8.8.8 1.1.1.1 valid=300s;\nresolver_timeout 5s;</pre>\n<h3>All the steps in a nutshell</h3>\n<ol>\n<li>Create a new <code>default</code> file in <code>sites-available</code> after backing up the old one and then symlink it to <code>sites-enabled</code></li>\n<li>Route all HTTP traffic to HTTPS using a single directive as described above in your new <code>default</code> file</li>\n<li>Create a global configuration file in <code>/etc/nginx/ssl_params</code> just like the one above and point to the location of your certificates</li>\n<li>Create individual <a href=\"http://subdomain.mydomain.com/\"></a> config files in <code>sites-available</code> for every sub-domain you need, ensuring that you symlink each one back to <code>sites-enabled</code></li>\n<li>Run <code>sudo nginx -t</code> to test everything</li>\n<li>Run <code>sudo service nginx reload (or restart)</code> followed by <code>sudo service nginx status</code> to ensure everything is running</li>\n<li>Finally, test your newly configured subdomain with <code>curl -L</code> <a href=\"http://subdomain.mydomain.com/\"><code>subdomain.mydomain.com</code></a> to make sure everything works! You can also verify headers with <code>curl -I</code>.</li>\n</ol>\n<p>In addition to <code>curl</code>, you can test your SSL configuration using online tools like <a href=\"https://www.ssllabs.com/ssltest/\">SSL Labs</a> to ensure your settings are secure and correctly configured.</p>\n<p>And that’s it! With this setup, you now have a flexible, scalable Nginx configuration that makes adding or removing subdomains a breeze. You no longer need to worry about HTTP traffic or SSL parameters, they’re managed centrally and follow best practices by default. </p>\n\n\n\n\n<figure><img src=\"https://geekist.co/wp-content/uploads/1746074660-480x368.avif\" alt=\"NGINX by Example book cover showing a green squid illustration on a white background.\" width=\"480\" height=\"368\" /><figcaption>Master NGINX with real-world patterns: SSL, subdomains, caching, load balancing and more.</figcaption></figure>\n\n\n\n\n\n<h3>If your subdomain setup feels smarter now….?</h3>\n\n\n<p>You’re going to love the rest. Dive into<br /><strong><em><a href=\"https://geekist.co/nginx-by-example/\">Nginx by Example Vol. 1</a></em></strong>,<br />your new config companion.</p>\n\n\n\n\n\n\n\n<p>This is just the beginning of the <a href=\"https://geekist.co/series/taming-nginx/\">Taming Nginx</a> series. I’ve added more to it since. </p>\n<ul>\n<li><a href=\"https://geekist.co/building-the-foundation/\">A simplified folder structure to use in your Linux machines</a></li>\n<li><a href=\"https://geekist.co/wildcard-ssl-and-beyond/\">Wildcard Certificates, Certbot &amp; Cloudflare and Mutual SSL with Nginx</a>. </li>\n<li><a href=\"https://geekist.co/the-art-of-proxying/\">Advanced Nginx topics like <strong>reverse proxying</strong>, <strong>caching</strong>, and <strong>rate limiting</strong></a>.</li>\n</ul>\n<hr />\n\n<h3>How to force HTTPS in Nginx by default?</h3>\n<p>Set a default server block that listens on port 80 and redirects all traffic to HTTPS using a 301 redirect. Keep it minimal and global.</p>\n<h3>Where should HTTP exceptions go in Nginx?</h3>\n<p>Put them in /etc/nginx/conf.d to ensure they load before the default HTTPS redirect. Load order matters for exceptions to work.</p>\n<h3>Why use conf.d and sites-enabled in Nginx?</h3>\n<p>conf.d is loaded first which is ideal for global configs and exceptions. sites-enabled holds standard domain configs via symlinks from sites-available.</p>\n<h3>How to organise subdomains in Nginx?</h3>\n<p>Use wildcard SSL, centralised ssl_params, and separate config files per subdomain in sites-available. Symlink each to sites-enabled.</p>\n<h3>What is ssl_params in Nginx?</h3>\n<p>ssl_params is a custom include file holding shared SSL settings – perfect for wildcard certs and simplifying subdomain management.</p>\n\n<p></p>\n<p>Set a default server block that listens on port 80 and redirects all traffic to HTTPS using a 301 redirect. Keep it minimal and global.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Where should HTTP exceptions go in Nginx?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Put them in /etc/nginx/conf.d to ensure they load before the default HTTPS redirect. Load order matters for exceptions to work.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Why use conf.d and sites-enabled in Nginx?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>conf.d is loaded first which is ideal for global configs and exceptions. sites-enabled holds standard domain configs via symlinks from sites-available.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"How to organise subdomains in Nginx?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Use wildcard SSL, centralised ssl_params, and separate config files per subdomain in sites-available. Symlink each to sites-enabled.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"What is ssl_params in Nginx?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>ssl_params is a custom include file holding shared SSL settings – perfect for wildcard certs and simplifying subdomain management.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 7,
                        "name": "Where the User Begins",
                        "slug": "where-the-user-begins"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/in-the-beginning-we-shared-whether-we-liked-it-or-not/",
            "url": "https://geekist.co/in-the-beginning-we-shared-whether-we-liked-it-or-not/",
            "title": "In the Beginning… We Shared (whether we liked it or not!)",
            "summary": "The history of hosting, from shared servers with shady neighbours to modern setups. A humour-filled deep dive into what went wrong and what works today.",
            "image": "https://img.geekist.co/wp-content/uploads/2024/12/in-the-beginning-8230-we-shared-whether-we-liked-it-or-not.avif",
            "date_published": "2024-12-16T18:34:08Z",
            "date_modified": "2026-10-30T12:56:48Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tame the Tech",
                "Beneath the Stack"
            ],
            "content_html": "<h2>And How AWS &amp; KVM Fixed It!</h2>\n<p>Let me tell you what hosting was like in the 90s’. Our options were pretty much binary. It was either “shared hosting” or “dedicated”. If you couldn’t afford dedicated, you were stuck with sharing your resources with potentially hundreds of other websites. </p>\n<p>There was no VPS, no cloud and certainly no click-to-scale option either. In fact, your scaling options were quite limited. You’d spin down your server, upgrade it, then spin it back up. </p>\n<p>And that would still be okay if it was dedicated hosting, but with shared it was a gamble. Your site’s performance was directly dependant on your server neighbour’s success story traffic-wise. </p>\n<p>No Seriously. </p>\n<p>Your blog about “Mama’s lasagna recipes” will mysteriously slow to a crawl every Sunday. Why? </p>\n<p><em>Because your neighbour’s ‘xxxsuperhotbabes . com’ was getting slammed</em></p>\n<p>And worse, if you shared the same IP block, search engines would flag you for suspicious activity if your neighbour was hosting a scam site! </p>\n<p>Some poor soul would come up in the forums and complain about how his <em>super premium</em> shared hosting plan on <code>exampleHost123 . com</code> offered crap service for the money.</p>\n<p>Forum members would help investigate and most of the time, some of us would discover his neighbours. </p>\n<p>We’d offer the best advice there was: Go back to the provider to ask to be hosted on a different rack or IP block. </p>\n<p>If this was available, most providers would accommodate the request. <a href=\"https://pro-webs.net/blog/2009/06/26/shared-hosting-bad-neighbors/\">Still this was a real problem</a> and many providers unwittingly took on the bad rep for allowing such questionable sites in the first place. </p>\n<p>But hey, high traffic meant more infrastructure, and no one was going to say no to higher paying customers. </p>\n<h3>Enter AWS and KVM: The First Disruptors</h3>\n<p>AWS came up first in ‘06 but was slow on the uptake. </p>\n<p>Partially because no one really believed that a glorified book store knew anything about hosting (of course they did – it was the world’s largest bookstore and more!) and because on-demand pricing was new and somewhat unpredictable. </p>\n<p>It was a new paradigm and no one really understood it. </p>\n<p>So when the Kernel-based Virtual Machine (KVM) came about a year later, it was more than welcome. </p>\n<p>It offered hardware based isolation (think mini dedicated servers), and came with traditional monthly or annual pricing + a battle tested route to server management and customization options. </p>\n<p><strong>But what really is the difference between KVM and the cloud? I mean really?</strong></p>\n<p>Ah, the age-old debate: KVM or the Cloud? Think of it as choosing between a Shelby GT500 (Eleanor, IYKYK) and a Tesla. </p>\n<p>The Shelby – a beast of raw power – was a pain to handle, with mysterious quirks and a near-taboo status. But oh, the satisfaction of the drive when you figure it all out! </p>\n<p>The Tesla, on the other hand, does everything for you, right down to reminding you to <a href=\"https://www.tesla.com/support/vehicle-safety-security-features#cabin-camera\">keep your eyes on the road</a>. </p>\n<p>Both get you places, but in <em>very</em> different ways. Let’s explore some of the arguments, shall we? </p>\n<ol>\n<li>Managed Infrastructure</li>\n</ol>\n<blockquote>\n<p>AWS takes care of everything: snapshots, backups, disaster recovery. Oh, and Identity and Access Management (IAM)? </p>\n<p>It’s like having a bouncer at your server’s front door, checking IDs and ensuring only the right people get in. </p>\n<p>It’s security, convenience, and peace of mind wrapped into one.</p>\n</blockquote>\n<p>Sure, IAM is great, but let’s not kid ourselves. Who needs a bouncer for a house party with three guests? KVM’s simpler admin and manager roles are perfectly fine for most setups. </p>\n<p>And backups? </p>\n<p>KVM providers have had that covered since the Jurassic era of shared hosting. Snapshot backups? Yep, got those too. </p>\n<p>DIY isn’t scary when it saves you a fortune. </p>\n<ol start=\"2\">\n<li>Ecosystem Integration</li>\n</ol>\n<blockquote>\n<p>Cloud machines integrate with everything: S3 for storage, RDS for databases, Lambda for serverless computing. No assembling required.</p>\n</blockquote>\n<p>For the most part KVM has that covered. Need a master/slave redundant database server? Spin up more KVM instances. </p>\n<p>I mean with providers like <a href=\"https://my.racknerd.com/aff.php?aff=13317\">Racknerd offering ridiculously low priced instances</a> – less than a buck a month, and with docker rescuing you from hair-pulling configuration mayhem, it really isn’t as difficult as you think. </p>\n<p>Still, if a hands-free dedicated managed database server is all you need now, you have more options. Digital Ocean has managed databases. </p>\n<p>In fact, <a href=\"https://m.do.co/c/7157b1229ba4\">here’s $200 in credits</a> for you on DO for a 6 month period. </p>\n<p>Where AWS really shone, was S3. And quite frankly it was revolutionary for it’s time. There was nothing like it. Your only option was to grab a dedicated machine with tons storage or pay a super premium price for a high end KVM instance. </p>\n<p>But that too has changed now. We have services like <strong>Wasabi</strong> and <strong>Cloudinary</strong> with generous free tiers and multiple integrations, not to mention free image optimizations and other goodies built in. </p>\n<p>Wasabi is a cheaper, S3-compatible storage solution with no egress fees, while Cloudinary offers image optimisations out of the box. </p>\n<ol start=\"3\">\n<li>Redundancy and Uptime</li>\n</ol>\n<blockquote>\n<p>With multi-availability zones and built-in failover, AWS keeps your services up and running no matter what. Add some DDoS protection, and you’re practically invincible.</p>\n</blockquote>\n<p>Wait. So KVM can’t handle redundancy? Well Yes and No. And the real answer lies in which provider you choose. </p>\n<p>Many enterprise-grade KVM hosts offer robust failover systems and DDoS protection. Sure, AWS automates it all, but at what cost? Your kidney? </p>\n<p>With KVM, you can achieve redundancy without needing Jeff Bezos-level funding – just a little planning and maybe an extra instance or two. Which brings me to the Elephant in the Server Room. </p>\n<ol start=\"4\">\n<li>Cost</li>\n</ol>\n<blockquote>\n<p>Cloud’s pay-as-you-go model lets you scale up and down dynamically. You’re only billed for what you use → super cost-effective!</p>\n</blockquote>\n<p>Is it, though? That pay-as-you-go pitch sounds great until your bill looks like you stood up, walked to the bar, and rang the bell. Oh dear God – how a little alcohol (or a surprise spike in resource usage) can really mess you up! </p>\n<h3>My experience</h3>\n<p>With all that said and if you asked me, the fundamental appeal of AWS wasn’t its backups, managed services, or even its redundancy. It was <strong>scalability</strong>. Infinite scalability, or so it seemed. </p>\n<p>And let me tell you, I fell for it. </p>\n<p>I was an early adopter, hopping on the AWS bandwagon in 2010. Here’s why: </p>\n<ul>\n<li>I had this shiny new app that I thought was going to blow everyone away. It felt like I was sitting on a rocket ship just waiting to launch. </li>\n<li>My biggest fear? <strong>Scalability.</strong> What if traffic exploded? What if the app actually became the next big thing? </li>\n<li>Enter AWS. Suddenly, I could scratch the itch of my over-engineering mind with the promise of infinite resources, and I worried less.</li>\n</ul>\n<p><strong>But here’s the hard truth:</strong></p>\n<ol>\n<li>Scaling Issues Are Rarely Real Problems<br />Most startups never hit traffic numbers high enough to test scalability. If you had a product launch, you’d also have a <strong>backup plan</strong> ready in case of high traffic. A single KVM instance would manage this just fine.\n<p>Scaling problems are what I call a “<strong>happy problem</strong>” – something to worry about <em>after</em> you’ve actually succeeded (with your backup in place of course!)</p></li>\n<li>It’s Not Fire-and-Forget<br />Scaling on AWS isn’t as magical as the marketing suggests. You don’t just “turn on” infinite scalability and forget about it.\n<p>There’s a learning curve to figuring out how to scale efficiently. Why else do newer services like ECS or Fargate even exist? Because traditional EC2 scaling isn’t as straightforward as AWS would have you believe.</p></li>\n<li>Cost vs Reality<br />Many of us end up looking at the bill and asking, “Sheesh, would a small KVM machine as a load balancer and two larger KVM instances serving traffic have been cheaper?” The answer is <em>often yes.</em></li>\n</ol>\n<p>So in retrospect, many of my earlier apps didn’t need AWS at all, but boy was it good to know it was there. </p>\n<p>Ultimately, its your decision to make. For me, I spun up an instance on <a href=\"https://my.racknerd.com/aff.php?aff=13317\">RackNerd</a> some two years ago and it has been up ever since. </p>\n<p>I host 2 domains on it, complete with DDoS protection, wildcard SSL certs and complete control over my <code>node|python|docker</code> services. The cost? $16.98 per year (I scored a sweet Black Friday deal and have been paying the same since!)</p>\n<p>Stay tuned for more articles about my setup – and if you stick around long enough, I’ll share how I’m running a super decent inference server with the setup above without costing a cent more </p>\n<hr />\n\n<h3>Is shared hosting bad?</h3>\n<p>It can be. Your site performance depends on server neighbours. And if one goes viral or shady, you suffer too.</p>\n<h3>KVM vs cloud hosting?</h3>\n<p>KVM gives you full control and predictable pricing. Cloud hosting adds automation and scalability, but often at a higher cost.</p>\n<h3>Is AWS worth it for small projects?</h3>\n<p>Not usually. Most apps don’t need that level of scale, and a cheap KVM setup often does the job for a fraction of the price.</p>\n<h3>Why is AWS so expensive?</h3>\n<p>It’s easy to rack up costs with dynamic scaling, storage, and data transfer. You pay for flexibility – sometimes more than you should.</p>\n<h3>When should I use cloud hosting?</h3>\n<p>Use cloud hosting when you expect real scale or need managed services. Otherwise, KVM is simpler, cheaper, and more than enough.</p>\n\n<p></p>\n<p>It can be. Your site performance depends on server neighbours. And if one goes viral or shady, you suffer too.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"KVM vs cloud hosting?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>KVM gives you full control and predictable pricing. Cloud hosting adds automation and scalability, but often at a higher cost.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Is AWS worth it for small projects?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Not usually. Most apps don’t need that level of scale, and a cheap KVM setup often does the job for a fraction of the price.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"Why is AWS so expensive?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>It’s easy to rack up costs with dynamic scaling, storage, and data transfer. You pay for flexibility – sometimes more than you should.</p>\n<p>\\n\\n\"}},{\"@type\":\"Question\",\"name\":\"When should I use cloud hosting?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"\\n\\n</p>\n<p>Use cloud hosting when you expect real scale or need managed services. Otherwise, KVM is simpler, cheaper, and more than enough.</p>\n<p>\\n\"}}]}</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/its-a-security-thing/",
            "url": "https://geekist.co/its-a-security-thing/",
            "title": "It’s a Security Thing.",
            "summary": "A high-stakes demo, MongoDB, and a critical mistake? Discover how I reset an entire database minutes before a VIP arrive and what happened after…",
            "image": "https://img.geekist.co/wp-content/uploads/2025/03/e57e12db-b884-48cc-926a-a98a15843c21-1.avif",
            "date_published": "2024-12-15T01:10:10Z",
            "date_modified": "2026-11-15T13:01:42Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tame the Tech",
                "Beneath the Stack"
            ],
            "content_html": "<p>My old Heardable Inc boss was formerly in TV production. Heardable, as you might have heard of, was a brand analytics company way ahead of its time. </p>\n<p>We were setting up a high-stakes professional <a href=\"https://www.youtube.com/watch?v=BqUhLWgfGXI\">YouTube interview with the Global CEO (David Sable)</a> of Y&amp;R (one of our incubators at the time), and we wanted to use this event to showcase our brand-new Heardable product – where I was CTO. </p>\n<p>Everything was set up, and we were awaiting the arrival of David and other important folks. </p>\n<p>I knew the app had a bug that required the Meteor Mongo DB to be reset to clear the cache before the demo. </p>\n<p>You see, the thing about Meteor &amp; Mongo is that in the early days of 2015, there was no way of telling their REPLs apart, Meteor’s shell looked almost exactly the same as Mongo’s shell. </p>\n<p>So instead of typing this in the <em>Meteor Shell</em>: </p>\n\n<pre>&gt; mongo reset</pre>\n<p>I typed this in the <em>Mongo Shell</em></p>\n\n<pre>&gt; mongo reset</pre>\n<p>Which. Well… It kinda… Uhm… Reset the entire DB. </p>\n<p><em>Seriously though, which part of the above looked bloody different to you??</em></p>\n<p>Right! I thought. Ten minutes to his arrival, and I just cleared out the DB. </p>\n<p>Golden. </p>\n<p>Okay, no problem, you got this. There’s a backup you did a couple days ago. Grab it and restore it and everything’s gonna be right as day. </p>\n<p>But there was one problem. </p>\n<p>My boss, whose account was going to be used for the demo, had changed her password after the backup, meaning she would have to “Reset Password” before the demo because the backup contained her older one. </p>\n<p>Damn, I thought. Why in the world would someone change a password for a non-production server? </p>\n<p>Two minutes to his arrival, and my boss walks in. </p>\n<p>“All good?” she asked. </p>\n<p>“Yes!” I said, “Just that… I need you to do something real quick… Can you reset your password?” </p>\n<p>“Now?!” she asked. “You kidding?”, she continues, in absolute disbelief and exasperation. </p>\n<p>Calmly, I said, “Francine? Yes. Now.” </p>\n<p>She reset the password, and Ron Hart (the CTO of DropSuite) walked in just as the drama was ending. </p>\n<p>“What’s going on?” he asked. “Nothing,” I said. “All good.” </p>\n<p>But Francine (my boss) couldn’t resist chiming in, “He just made me reset my password!” </p>\n<p>“Just a <em>security thing</em>…” I said, lying through my teeth. Ron didn’t say a word, but the look on his face said it all: </p>\n<p><em>Yeah, sure it is…</em></p>\n<p>Meanwhile, David Sable arrives, and Francine leaves my office. I couldn’t take the pressure and went out the back door for a smoke. </p>\n<p>Ron came out to join me. He lit himself a cigarette, looked out into the car park in the same direction I was facing – and without turning his head – took a puff and asked, </p>\n<p>“You f**ked up, didn’t ya?” </p>\n<p>I took a puff and said, “Yep.” </p>\n<p>He continues, in the same posture, “How bad?” </p>\n<p>I said, “Well. How’d you rate resetting the DB?” </p>\n<p>He replies, “Yep. Bad.” </p>\n<p>We’re still not facing each other, casually looking out into the distance. </p>\n<p>He takes another puff, then continues: “You fixed it?” </p>\n<p>I replied, after another puff, “Yeah, restored a backup from a couple days ago.” </p>\n<p>He pauses for a bit, thinking about it, then asks absurdly, </p>\n<p>“So you mean between the backup and today, she changed her password?” </p>\n<p>I replied, “Yeapp.” </p>\n<p>He then shrugs, puts out his cigarette, and declares, “Yep… totally a <em>security thing</em>… Let’s get back inside.” </p>\n<p>“Yep,” I said, putting out my cigarette. </p>\n<p>And as if it was nothing more than a smoke break, we walked inside to greet the VIPs and show off the new product demo. </p>\n<p>Reflecting on the chaos of that day, I realised something. Handling high-pressure situations like this didn't come from my technical skills. It came from DJing in clubs when I was younger.</p>\n<p>When you're DJing, the clock resets with every song. Play an uncharted genre and you might have just 30 seconds to figure out what comes next.</p>\n<p>Pick a track. Put in the CD. Cue it. Mix it in.</p>\n<p>All while convincing everyone that this was exactly what you intended.</p>\n<p>I've done all that with barely ten seconds to spare.</p>\n<p>In those moments, you're not just playing music. You're a freggin' time magician.</p>\n<p>Because the clock ain't gonna stop for no one.</p>\n<p>It's <em>what you do</em> in that time that matters.</p>\n<p>Right in the neck that was. Phew.</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/dynamic-capabilities-for-adaptable-systems/",
            "url": "https://geekist.co/dynamic-capabilities-for-adaptable-systems/",
            "title": "Dynamic Capabilities for Adaptable Systems",
            "summary": "Build better software with dynamic capabilities. Learn how to create adaptable and maintainable systems.",
            "image": "https://img.geekist.co/wp-content/uploads/dynamic-capabilities-for-adaptable-systems.avif",
            "date_published": "2024-10-04T03:15:28Z",
            "date_modified": "2026-10-29T22:49:58Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Beneath the Stack",
                "Tame the Tech",
                "Thinking in Code"
            ],
            "content_html": "<h2>Crafting Future-Proof Systems with Dynamic Configuration</h2>\n<p>In the fast-paced world of software development, where technologies evolve rapidly, we’re tasked with designing systems that stand the test of time. The need for adaptable systems remains as crucial as ever. One approach gaining momentum is the <strong>Dynamic Capabilities System</strong>, a powerful tool for creating adaptable and scalable software. </p>\n<p>But what exactly is it? Is it just <em>events</em> on steroids? A fancy term for <em>hooks</em> dressed in a tuxedo? Let’s dive into this concept and explore how it might revolutionise your software development process. </p>\n<h3>The Need for Flexibility</h3>\n<p>In the software industry, change is the only constant. One day you’re coding in peace, and the next, a new requirement demands immediate attention. Systems need to adapt quickly and scale gracefully as user bases grow, all while maintaining reliability and encouraging collaboration among teams. </p>\n<p>So, how do we achieve this level of adaptability? Enter the <strong>Dynamic Capabilities System</strong> – an abstraction layer that defines which features or actions (capabilities) are enabled or disabled within a system. It’s like having a control panel where you can toggle features on and off without modifying the underlying codebase. </p>\n<h3>Why Use a Capabilities System?</h3>\n<p>The Capabilities System offers several benefits: </p>\n<p><strong>Modularity</strong>: Components can be developed and maintained independently, similar to specialists in a team, each focusing on their area of expertise. </p>\n<p><strong>Configurability</strong>: Tailor your system to specific needs by enabling or disabling capabilities through configuration. </p>\n<p><strong>Extensibility</strong>: Introduce new capabilities seamlessly. Today it’s a basic app; tomorrow, it’s the next big thing – all without significant rework. </p>\n<p><strong>Adaptability</strong>: Adjust to changing requirements or expand functionality without extensive code changes. </p>\n<p>By embracing a Capabilities System, you’re setting your software up for success, ensuring it can adapt to new challenges effectively. </p>\n<p><em>Wait, Isn’t this all just Events (or Hooks)?</em></p>\n<p>Ah, the million-dollar question! If you’re thinking, “Hold on, isn’t this just like events or hooks?” you’re not wrong. While dynamic capabilities share some DNA with events and hooks, they’re not twins. Hooks and events allow developers to inject custom code or modify behaviour at specific points without altering the core codebase. In systems like WordPress, hooks enable you to add custom functionality. Event-driven architectures operate similarly, with components communicating by emitting and responding to events. </p>\n<p><em>So, What Makes Dynamic Capabilities Special?</em></p>\n<p>The Dynamic Capabilities System enhances these concepts with centralised lifecycle management. It orchestrates stages like <code>BEFORE_ACTION</code>, <code>ACTION</code>, and <code>AFTER_ACTION</code> for each capability, providing a structured and consistent processing flow.</p>\n<p>Unlike hooks and events, which can sometimes lead to uncoordinated behaviour, the Dynamic Capabilities System brings order by using a configurable capabilities schema that can be modified at runtime. </p>\n<p>Need to enable a feature on the fly? No problem. Want to disable something without redeploying? Easily done. </p>\n<p>A key feature is the graceful fallback mechanism. If an action occurs and no middleware is registered to handle it, the Core handles it by default, ensuring no action is left unprocessed. </p>\n<h3>Dynamic Lifecycle Management</h3>\n<p><strong>Core Lifecycle Creation</strong></p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/6352c92f-03df-4bcb-af2b-4d06a7e456c2-638x800.avif\" alt=\"Flow diagram showing capabilities configuration and middleware registering with a core, which manages actions and updates a shared state store through lifecycle events.\" width=\"638\" height=\"800\" /></figure>\n<p>At the heart of this system is the <strong>Core Lifecycle Manager</strong>, which generates lifecycle events based on your configuration, ensuring that every action goes through the proper stages. Middleware components register their capabilities with the Core, indicating which actions they can handle. </p>\n<p><strong>Example Capabilities Configuration:</strong></p>\n<pre>const capabilitiesConfig = {\n  CREATE: true,     // Full lifecycle: BEFORE_CREATE, CREATE, AFTER_CREATE\n  UPDATE: true,     // Full lifecycle: BEFORE_UPDATE, UPDATE, AFTER_UPDATE\n  DELETE: false,    // Simple action: DELETE (no BEFORE/AFTER)\n  COMPLETE: true,   // Full lifecycle: BEFORE_COMPLETE, COMPLETE, AFTER_COMPLETE\n  ERROR: false,     // Simple action: ERROR\n  PROGRESS: true,   // Full lifecycle: BEFORE_PROGRESS, PROGRESS, AFTER_PROGRESS\n};</pre>\n<p><strong>Lifecycle Generation:</strong></p>\n<pre>const createLifecycle = (capability, hasLifecycle) =&gt; {\n  // Creates an array representing the lifecycle stages \n  // for a capability.\n  const lifecycle = [`${capability}`];  // Base capability stage\n  if (hasLifecycle) {\n    lifecycle.unshift(`BEFORE_${capability}`);  // Add BEFORE stage\n    lifecycle.push(`AFTER_${capability}`);     // Add AFTER stage\n  }\n  return lifecycle;\n};\nconst lifecycleRegistry = {};\nObject.entries(capabilitiesConfig)\n    .forEach(([capability, hasLifecycle]) =&gt; {\n      // Iterates over capability configuration and builds \n      // lifecycle registry.\n      lifecycleRegistry[capability] = createLifecycle(\n        capability, hasLifecycle\n      );\n    });</pre>\n\n<p>With this setup, every action follows a defined path through its lifecycle stages. By decoupling lifecycle management from middleware, each component can focus on its specific responsibilities without concern for the overall process flow. Adjustments to the lifecycle can be made centrally, adding new stages or modifying existing ones without affecting individual middleware components. </p>\n<h3>Middleware Registration and Core Fallbacks</h3>\n<p>Middleware components handle specific capabilities and register themselves with the Core, indicating which actions they manage.. </p>\n<p><strong>For example:</strong></p>\n<pre>const middlewareRegistry = {};\nconst registerMiddleware = (middleware) =&gt; {\n  // Registers middleware capabilities in the registry.\n  middleware.capabilities.forEach((capability) =&gt; {\n    if (!middlewareRegistry[capability]) {\n     // Create array for capability if not exists\n      middlewareRegistry[capability] = [];  \n    }\n    // Add middleware ID to capability array\n    middlewareRegistry[capability].push(middleware.id);  \n  });\n};\nconst tasksMiddleware = {\n  id: \"tasks\",\n  capabilities: ['CREATE', 'UPDATE', 'COMPLETE', 'PROGRESS'],\n};\nconst errorsMiddleware = {\n  id: \"errors\",\n  capabilities: ['ERROR', 'UPDATE'],\n};\nregisterMiddleware(tasksMiddleware);\nregisterMiddleware(errorsMiddleware);</pre>\n\n<p><strong>Middleware Structure:</strong></p>\n<pre>const exampleMiddleware = {\n  id: \"middlewareId\",\n  capabilities: ['CAPABILITY1', 'CAPABILITY2'],\n  handleLifecycleEvent: (lifecycleEvent, action, store) =&gt; {\n    // Implement middleware logic for handling lifecycle events.\n    // This function receives the event type (lifecycleEvent), \n    // the action data, and potentially the application store \n    // (depending on implementation).\n  },\n};</pre>\n\n<p>But what happens if an action doesn’t have a middleware handler? Does it vanish into the ether? Not quite. The Core steps in to handle it, ensuring no action is left unprocessed. This safety net keeps the system running smoothly, even when not everything goes according to plan. </p>\n<h3>Comparing Architectural Patterns: From Tankers to Trawlers</h3>\n<p>To better understand the benefits and trade-offs of the dynamic capabilities approach, it’s helpful to compare it with other common architectural patterns. </p>\n<p><strong>Monolithic vs. Modular Architecture</strong></p>\n<p>Monolithic architectures, where all components are tightly coupled, can make maintenance and scalability challenging. Changes in one part of the system can have ripple effects elsewhere. In contrast, modular architectures promote separation of concerns, allowing components to be developed and maintained independently. The Dynamic Capabilities System is inherently modular, enhancing flexibility and making it easier to adapt to changing requirements. </p>\n<p><strong>Plugin Systems and Extensibility</strong></p>\n<p>Plugin architectures allow you to extend functionality without modifying the core system. The Capabilities System complements plugin architectures by providing a configuration-driven model where plugins can register their capabilities with the Core Lifecycle Manager, integrating seamlessly into the system’s lifecycle. </p>\n<p>This synergy allows plugins to be developed independently while participating in centralised control and dynamic configurability. </p>\n<p><strong>Microservices Architecture</strong></p>\n<p>Microservices break down applications into independent services that communicate over a network, offering scalability and fault isolation. The Dynamic Capabilities System can be integrated into a microservices architecture, enhancing modularity and adaptability across distributed systems. </p>\n<p>In a microservices environment, each service can implement its own set of capabilities, registering them with a distributed Core Lifecycle Manager or communicating capabilities across services. As long as all services <strong>speak the same language</strong> – adhering to agreed-upon communication protocols and data formats – the dynamic capabilities system can operate seamlessly across the cluster. </p>\n<h3>Why Dynamic Capabilities Might Be Your Software’s Best Friend</h3>\n<p>With dynamic capabilities, you can introduce new features without worrying about technical debt. The Core provides default handling until specialised middleware is ready, allowing for phased implementation. Unlike a fragile structure where adding or removing parts risks collapse, this system remains stable as it evolves. </p>\n<p>Need to change how a capability behaves? Adjust the lifecycle centrally, and the change propagates accordingly. Plus, with external systems listening in, building features like a control dashboard becomes straightforward. </p>\n<p>Middleware components operate independently, reducing the chance of conflicts. Multiple middleware can handle the same capability if needed, providing redundancy. It’s teamwork at its finest, without unnecessary complexity. </p>\n<p>The system is prepared to handle new capabilities without structural changes, scaling gracefully as your system grows. </p>\n<h3>Navigating the Dynamic Seas: Challenges and Opportunities</h3>\n<p><strong>Complexity in Coordination</strong></p>\n<p>Yes, there’s a learning curve in managing dependencies between middleware as the system grows. To keep things running smoothly, it’s essential to establish clear dependency definitions and possibly introduce an orchestration layer within the Core. This way, each middleware component knows its role, and the Core ensures they interact effectively. </p>\n<p><strong>Performance Overhead</strong></p>\n<p>The additional steps in the lifecycle might introduce some latency. However, by leveraging asynchronous processing and committing to regular optimisation, you can maintain high performance. Distributing non-critical functions to child processes is another strategy to consider. </p>\n<p><strong>Configuration Management</strong></p>\n<p>Misconfigurations can lead to unexpected behaviour – no one wants surprises in their software. To reduce the risk of human error, employing validation tools, centralised configuration management, and user-friendly interfaces is key. </p>\n<p><strong>Learning Curve</strong></p>\n<p>Implementing this architecture isn’t a trivial task – it requires effort and understanding. With comprehensive documentation, engaging training programs, and well-defined coding standards, you can make the transition more manageable for your team. </p>\n<h3>Tis’ the New Microservices “Monolith”?</h3>\n<p>As we sail towards the horizon of software development, you might wonder: <strong>Should we start building everything this way?</strong></p>\n<p>Before we all dive headfirst, it’s crucial to consider whether the dynamic capabilities system fits your specific needs. While it’s an exciting approach, it’s not the magic wand that turns every project into a masterpiece. </p>\n<p><strong>Considerations:</strong></p>\n<ul>\n<li><strong>System Size and Complexity:</strong> For large, complex systems, the modularity and flexibility can be a game-changer. For smaller projects, it might be like using a sledgehammer to crack a nut. </li>\n<li><strong>Rate of Change:</strong> If your system evolves faster than fashion trends, the ability to enable or disable features dynamically is invaluable. For static systems, the extra overhead may not be worth the hassle. </li>\n<li><strong>Team Expertise:</strong> Implementing this architecture requires a team comfortable with its concepts. If your team isn’t ready, it might lead to more headaches than benefits!</li>\n</ul>\n<p><strong>In Conclusion</strong></p>\n<p>The dynamic capabilities system offers a promising approach for certain scenarios, but it’s not the new default for all projects. Think of it as another valuable tool in your architectural toolbox. </p>\n<p>Remember, the best architecture is the one that fits your project’s unique needs and helps your team deliver value efficiently. Whether you adopt this system or stick with simpler methods, the goal is to build effective, maintainable software. </p>\n<p><strong>Happy coding, and may the arch be with you!</strong></p>\n<hr />\n<p><strong><em>Author’s Note:</em></strong> <em>The concepts discussed here are applicable across various domains and aren’t limited to any specific type of application. Whether you’re building a web service, a desktop application, or the next AI that definitely won’t become self-aware, the principles of modularity and dynamic capabilities can help you create software that stands the test of time.</em></p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    },
                    {
                        "id": 10,
                        "name": "Thinking in Code",
                        "slug": "thinking-in-code"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/?p=2367",
            "url": "https://geekist.co/the-eye-of-the-storm/",
            "title": "The Eye of the Storm",
            "summary": "'Tis a tale of two transformed. where she walked, roses filled with thorn, wherein winds cut through you like the norm. where he lived; torment took form.",
            "date_published": "2023-07-18T05:03:00Z",
            "date_modified": "2026-02-04T20:42:32Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Wordsmith's Forge"
            ],
            "content_html": "<p>‘Tis a tale of two transformed.<br />where she walked, roses filled with thorn,<br />wherein winds cut through you like the norm.<br />where he lived; torment took form. </p>\n<p>where her soul and his were reborn,<br />but soon she found she lost the warm<br />and tried to run outside the scorn.<br />alas, two souls fused; then re-formed. </p>\n<p>in the swarm she lay forlorn,<br />but love, love it kept them strong.<br />he tells her this will not prolong,<br />holds her hand, leads her along </p>\n<p>into the eye, of the storm. </p>\n<p></p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 11,
                        "name": "The Wordsmith's Forge",
                        "slug": "the-wordsmiths-forge"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/hybrid-vs-native/",
            "url": "https://geekist.co/hybrid-vs-native/",
            "title": "Hybrid vs. Native",
            "summary": "A deep dive into the Hybrid vs. Native debate, breaking down the myths around React Native, its real-world scaling potential, and why bad advice nearly…",
            "image": "https://img.geekist.co/wp-content/uploads/hybrid-vs-native.avif",
            "date_published": "2017-05-11T20:00:00Z",
            "date_modified": "2026-02-04T20:42:32Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Where the User Begins",
                "Tame the Tech",
                "Thinking in Code"
            ],
            "content_html": "<h2>Seriously, Are We Still Debating This?</h2>\n\n<p>💡</p>\n<p><em>This piece originated in 2017, back when React Native was still the cool kid on the block. It’s mostly preserved as is, with updated links to keep the references relevant. For a fresher take, check out my latest thoughts in </em><a href=\"https://geekist.co/why-your-tech-stack-is-overrated-and-what-actually-matters/\"><em>Why Your Tech Stack is Overrated (And What Actually Matters).</em></a></p>\n\n<p>For as long as mobile phones have been smart, developers have been locked in an eternal tug-of-war: Hybrid vs. Native. And just when we thought we’d figured it out, React Native has recently arrived, shaking up everyone’s carefully drawn battle lines. </p>\n<p>Here’s a quick story from my own trenches: </p>\n<p>Back when I was building an MVP for Speedoc – think Uber, but swap cars for house-call doctors – we were knee-deep in development hell with five separate apps: two for doctors, two for patients, and an admin app, because hey, why make it simple when complicated is available? </p>\n<p>Then came the unsolicited advice. You know, the kind where “experts” from a big local software house confidently declared: “React Native won’t scale! If you want performance, you must go native!” </p>\n<p>Ah yes, “must.” One of my favourite words. </p>\n<p>Let’s put aside the fact that Facebook has already shipped entire apps – like Ads Manager and parts of Marketplace – using React Native. I’d like to think that if anyone knew a thing or two about scaling, it was probably the multi-billion-dollar social media giant whose job it is to scale. </p>\n<p>But sure, let’s ignore all that. </p>\n<p>The confusion wasn’t just about whether React Native could scale. It was more fundamental. People were mixing up terms. </p>\n<p>Take Hybrid apps, for instance. “Just like native but easier!” Right? Well, not really. Hybrid apps (think Cordova, Ionic, or PhoneGap) are essentially web pages wearing a native disguise, awkwardly running inside WebViews. Native apps, meanwhile, were championed as the pure-bred thoroughbreds: Swift, Objective-C, Java – <em>languages developers talk about in hushed, reverent tones</em>. </p>\n<p>React Native, on the other hand, was misunderstood. It was dismissed as “just another hybrid gimmick,” when in reality, React Native apps render actual native components. JavaScript? Sure, but don’t confuse the language for the result. React Native is native, just sneakily so. </p>\n<p>At Speedoc, React Native wasn’t just an option, it was practically screaming to be picked. With a single codebase, we were delivering two patient apps, two doctor apps and even an admin interface without breaking a sweat. Well, maybe we broke a sweat (I most certainly did while working at Ahrefs!) but definitely fewer sweats than multiple native codebases would’ve caused. </p>\n<p>The backend was Meteor.js, which comes with their own <a href=\"https://blog.meteor.com/introducing-ddp-6b40c6aff27d\">realtime protocol</a> is a total lifesaver letting us replicate business logic across client and server. Throw in AWS Lambda (fancy, but a bit scary) and we had a scalable future-proof architecture on our hands. </p>\n<p>What baffled me most wasn’t React Native. It was the stubbornness of industry folks who insisted that “real apps must be native.” Here’s the reality check: React Native delivered <strong>90% of native performance at 10% of the headache and 10% of the cost</strong>. </p>\n<p>It unified teams, slashed bugs and accelerated releases. Sure, it had flaws, but so did native. No stack is flawless. You just pick the stack whose flaws hurt the least. For us, React Native’s minor bruises were preferable to native’s broken bones. </p>\n<p>The takeaway isn’t about winning a tech debate. It’s about recognizing bad advice when you hear it. And although it depends on a number of factors, it’s also about understanding your business requirements first, then choosing technology, not the other way around. </p>\n<p>Hybrid apps will always be around. Native has its niche. But React Native? It’s busy carving out the future.</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 7,
                        "name": "Where the User Begins",
                        "slug": "where-the-user-begins"
                    },
                    {
                        "id": 10,
                        "name": "Thinking in Code",
                        "slug": "thinking-in-code"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/remote-work-available-many-claim-it-but-few-mean-what-we-really-think/",
            "url": "https://geekist.co/remote-work-available-many-claim-it-but-few-mean-what-we-really-think/",
            "title": "Many claim Remote Work, but few mean what we really think.",
            "summary": "Remote work sounds great, but do employers really mean it? This post explores what true remote work looks like & how to make it work.",
            "image": "https://img.geekist.co/wp-content/uploads/2025/03/real-remote-work-2-scaled.avif",
            "date_published": "2016-12-03T20:00:00Z",
            "date_modified": "2026-02-04T20:42:33Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Beneath the Stack",
                "Tame the Tech"
            ],
            "content_html": "<p>💡</p>\n<p>This post was originally written in 2017 and has been preserved as-is for historical context. Links have been updated for relevance.</p>\n\n<p>Everyone seems to be talking about remote work these days, but let’s be honest, most employers still don’t fully grasp what it genuinely involves. Sure, they might claim they’re open to the idea, but once you start digging, you’d often find that their version of remote work barely scratches the surface. Many still cling to traditional management styles, believing that simply providing the option to work from home is enough to foster productivity and engagement. </p>\n<p>As a result, there’s a real risk you might feel lonely and unsupported, causing burnout and lower job satisfaction. </p>\n<p>Kinda defeats the the whole point doesn’t it? </p>\n<h3>The Employer’s Perspective on Remote Work</h3>\n<p>For some, remote work merely means allowing employees to occasionally work from home, perhaps when they’re mildly ill but still capable of productivity. Others view it as an earned privilege, reserved exclusively for long-standing employees or those transitioning into regional roles. Surprisingly, many employers still can’t fathom the idea of an employee working remotely from an entirely different country, unless it involves outsourcing. Clearly, despite the popularity of the term, misconceptions about remote work aren’t going anywhere – but you can help! </p>\n<h3>What Remote Work Actually Means</h3>\n<p>If you’re working remotely, you’re <strong>not</strong> on a casual arrangement. You’re just as responsible as your in-office colleagues – perhaps even more so. Here’s what remote work really looks like: </p>\n<p><strong>Show up. On time. Every time.</strong></p>\n<p>No one should feel like you’re “out of the loop” just because you’re not physically in the office. If you work across time zones, sync your availability with your team and compromise where needed. </p>\n<p><strong>Stay connected.</strong></p>\n<p>If Slack (or a similar tool) isn’t in place, <strong>suggest it</strong> and encourage usage. Make sure there’s always an easy way for your boss and team to reach you. </p>\n<p><strong>Help provide the tools your company needs.</strong></p>\n<p>A good video conferencing tool is <strong>non-negotiable</strong>. (If you’re still dealing with clunky Skype calls, push for an upgrade.) Depending on your work, tools like TeamViewer or remote desktop solutions might also be essential. </p>\n<p><strong>Respect working hours but be flexible.</strong></p>\n<p>If your team is in another timezone, make an effort to match their core hours for collaboration. Otherwise, work within your own time zone while ensuring maximum overlap with key team members. </p>\n<p><strong>Eliminate doubts about your commitment.</strong></p>\n<p>Be the <strong>first</strong> to show up on calls. Attend all communal activities remotely if possible. Over-communicate if necessary (visibility matters!). </p>\n<h3>Don’t Be Discouraged by Uninformed Employers</h3>\n<p>The truth is, many companies still don’t fully grasp the idea of remote work. It’s not yet mainstream (hopefully, we’ll get there soon), but in the meantime, ask the right questions during interviews. </p>\n<p>Don’t just ask: <strong>“Are you guys okay with remote work?”</strong> That’s too easy to say yes to. Instead, ask: <strong>“How does remote work function in your company?”</strong> and dig deeper. </p>\n<ul>\n<li>Are there established workflows? </li>\n<li>Are remote workers part of daily meetings? </li>\n<li>Do they have remote leadership, or is everyone in charge still in an office? </li>\n<li>What’s their policy on promotions for remote employees?</li>\n</ul>\n<p>These answers will tell you whether remote work is just a checkbox on a job listing or an actual part of the company’s culture. </p>\n<h3>Tools for a Smooth Remote Work Experience</h3>\n<p>Here’s a quick list of tools you’ll likely need to succeed remotely: </p>\n<ul>\n<li><strong>Communication &amp; Collaboration:</strong> <a href=\"https://slack.com/\">Slack</a>, <a href=\"https://www.microsoft.com/en-sg/microsoft-teams/free\">Microsoft Teams (new!)</a>, <a href=\"https://discord.com/\">Discord</a></li>\n<li><strong>Video Conferencing:</strong> <a href=\"https://www.zoom.com/\">Zoom</a>, <a href=\"https://meet.google.com/\">Google Hangouts</a>, <a href=\"https://whereby.com/\">Appear.in (new!)</a></li>\n<li><strong>Project Management:</strong> <a href=\"https://trello.com/\">Trello</a>, <a href=\"http://Asana.com/\">Asana</a>, <a href=\"https://basecamp.com/\">Basecamp</a>, <a href=\"https://www.atlassian.com/software/jira\">Jira</a></li>\n<li><strong>Remote Access:</strong> <a href=\"https://www.teamviewer.com/\">TeamViewer</a>, <a href=\"https://anydesk.com/\">AnyDesk</a>, <a href=\"https://remotedesktop.google.com/\">Chrome Remote Desktop</a></li>\n<li><strong>File Sharing:</strong> <a href=\"https://drive.google.com/\">Google Drive</a>, <a href=\"https://www.dropbox.com/\">Dropbox</a>, <a href=\"https://onedrive.live.com/\">OneDrive (formerly SkyDrive)</a></li>\n</ul>\n<h3>The Future of Remote Work</h3>\n<p>We’re not quite there yet but remote work <strong>is</strong> gaining ground. Hopefully, in a few years, it won’t just be something companies claim to offer but that it would be a real, viable option for most jobs. Until then, keep pushing for it, set the standard for professionalism and prove that remote work isn’t about convenience but that it’s very much about productivity and results. </p>\n<p>Good luck! May we all work remotely one day. 🙂</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/cheaper-free-web-hosting-in-singapore/",
            "url": "https://geekist.co/cheaper-free-web-hosting-in-singapore/",
            "title": "Cheaper (free?) Web Hosting in Singapore",
            "summary": "Affordable web hosting in Singapore: AWS Free Tier, DigitalOcean ($5/month), and Cloudflare for security & speed. Get more for less!",
            "image": "https://img.geekist.co/wp-content/uploads/cheaper-free-web-hosting-in-singapore.avif",
            "date_published": "2016-12-03T20:00:00Z",
            "date_modified": "2026-02-04T20:42:34Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Where the User Begins",
                "Beneath the Stack",
                "Tame the Tech"
            ],
            "content_html": "<p>💡</p>\n<p><em>This was originally written in 2016 and is preserved as-is except of renewing or removing broken links &amp; media. Stay tuned to a newer version in 2025!</em></p>\n\n<p>So, you’ve decided to host your own website or service, and naturally, you check out local hosting providers. Then you see the prices. And promptly spill your coffee. </p>\n<p>Yep. Hosting in Singapore is expensive. It’s not just the hosting itself (our own <strong>.sg</strong> and <strong>.com.sg</strong> domain prices start at <strong>$50 and up</strong>!) and that’s before you even get into storage, bandwidth or any of the extras. Compared to hosting options available internationally, it just feels like we’re being taken for a ride. </p>\n<p>But don’t worry. I’ve done the legwork so here’s a guide to cheap (and sometimes free) hosting solutions that will save you from paying a fortune while still getting a decent setup. I’ve tried to ensure that I only list the stuff I think will last, but as you know these things change rapidly. So they might be relevant now, but you’d need to revisit this in future. </p>\n<h2>Amazon Web Services (AWS)</h2>\n<p>Alright, let’s start with the big guns. </p>\n<p><a href=\"https://aws.amazon.com/free/\">Amazon Web Services (AWS)</a> offers a <strong>free tier</strong>, which is arguably one of the best deals around if you know what you’re doing. The catch? </p>\n<blockquote>\n<p><em>You need to be tech-savvy.</em></p>\n</blockquote>\n<p>Setting up an EC2 instance and managing your own infrastructure isn’t exactly beginner-friendly, and Amazon’s pricing structure can be daunting. But if you’re willing to roll up your sleeves, AWS provides free-tier usage for <strong>12 months</strong>, including: </p>\n<ul>\n<li><strong>750 hours/month</strong> of a t2.micro instance (enough to run a basic site 24/7). </li>\n<li><strong>5GB of free storage on Amazon S3</strong> (perfect for storing website assets). </li>\n<li><strong>1 million API calls per month</strong> via AWS Lambda (serverless functions!).</li>\n</ul>\n<p>Will AWS always offer this free tier? Who knows. But by the time they pull the plug, let’s just assume your site is already making millions and you won’t mind the extra cost. <em>(That’s how it works, right?)</em></p>\n<h2>DigitalOcean – The $5 Powerhouse</h2>\n<p>If AWS is too complicated, <a href=\"https://www.digitalocean.com/\">DigitalOcean (DO)</a> <strong>is a fantastic alternative</strong>. While not free, their starter plan is <strong>just $5 per month</strong>, and that gets you: </p>\n<ul>\n<li><strong>1 CPU core</strong></li>\n<li><strong>512MB RAM</strong></li>\n<li><strong>20GB SSD storage</strong></li>\n<li><strong>1TB bandwidth</strong></li>\n</ul>\n<p>For that price, you’ll find exactly 0 local providers that would offer hosting. </p>\n<p>I’ve personally used DO for projects at Heardable, running high-performance applications that scaled effortlessly. You get full control over your server, predictable pricing, and a community packed with tutorials to help you set things up. </p>\n<p>Need more power? Unlike AWS, scaling up is straightforward. You won’t have to play guessing games with complex pricing tables. </p>\n<h2>What About Domains?</h2>\n<p>Both AWS and DigitalOcean <strong>do not sell domains</strong>. But that’s not an issue because you can buy your domain from any provider and point it to your server. Personally, I use <a href=\"https://dynadot.com/\">DynaDot</a> (reliable, reasonable prices), but <a href=\"https://godaddy.com/\">GoDaddy</a> frequently runs insane promos where you can grab a <strong>.com for $1.99</strong>. </p>\n<p>Just avoid getting roped into unnecessary upsells, GoDaddy loves pushing premium add-ons <em>that you don’t need</em>! </p>\n<h2>Managing Your Domain. Cloudflare to the Rescue</h2>\n<p>Setting up your domain isn’t just about buying one; you’ll need to manage DNS settings, ensure security, and optimise performance. For that, <a href=\"https://www.cloudflare.com/\">Cloudflare is a no-brainer.</a></p>\n<p>Cloudflare is completely free and gives you: </p>\n<ul>\n<li><strong>DNS management</strong> (super fast and easy to use). </li>\n<li><strong>DDoS protection</strong> (helps keep your site from getting taken down by malicious attacks). </li>\n<li><strong>CDN caching</strong> (loads your website faster for visitors around the world). </li>\n<li><strong>Free SSL certificates</strong> (because having a padlock in the address bar is important these days).</li>\n</ul>\n<p>Whether you host on AWS, DigitalOcean, or anywhere else, using Cloudflare is one of the best things you can do for your site. </p>\n<h2>Are There Other Free or Cheap Hosting Options?</h2>\n<p>Yes. Plenty. </p>\n<p>There are shared hosting providers offering low-cost solutions, but they often come with caveats—limited storage, forced ads, or questionable reliability. Still, if you’re running a simple personal blog or a portfolio site, they might be worth considering. Here are I’ve found: </p>\n<ul>\n<li><strong>000WebHost</strong> (free but with forced branding and limited uptime). </li>\n<li><a href=\"https://byet.host/\"><strong>ByetHost</strong></a> (free, but you get what you pay for). </li>\n<li><strong>InfinityFree</strong> (another free shared hosting option).</li>\n</ul>\n<p>However, if you’re serious about uptime and performance, I’d stick to DigitalOcean or AWS Free Tier. </p>\n<h2>Final Thoughts</h2>\n<p>Hosting in Singapore is expensive, but thankfully, you’re not limited to local options. With AWS (if you’re tech-savvy), DigitalOcean (for the best bang-for-buck VPS hosting), and Cloudflare (for domain management and security), you can host a professional website for free (or nearly free) without compromising on quality. </p>\n<p>While things change fast in tech, these providers have been solid in 2016 and should continue to be reliable for the foreseeable future. </p>\n<p>And if you ever find cheaper, better hosting in Singapore, do let me know… because until then, I’m keeping my money where the value is. </p>\n<h2>Bonus: Quick Comparison</h2>\n<figure>\n<table>\n<thead>\n<tr>\n<th>Provider </th>\n<th>Cost </th>\n<th>Pros </th>\n<th>Cons</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><strong>AWS Free Tier</strong></td>\n<td>Free (for 12 months) </td>\n<td>Extremely powerful, full control </td>\n<td>Complicated setup, pricing after 12 months </td>\n</tr>\n<tr>\n<td><strong>DigitalOcean</strong></td>\n<td>$5/month </td>\n<td>Easy setup, predictable pricing, scalable </td>\n<td>Not free, self-managed VPS </td>\n</tr>\n<tr>\n<td><strong>Cloudflare</strong></td>\n<td>Free </td>\n<td>DNS, security, CDN, free SSL </td>\n<td>No actual hosting (just management) </td>\n</tr>\n<tr>\n<td><strong>000WebHost</strong></td>\n<td>Free </td>\n<td>Completely free hosting </td>\n<td>Ads, downtime, unreliable </td>\n</tr>\n<tr>\n<td><strong>ByetHost</strong></td>\n<td>Free </td>\n<td>No forced ads </td>\n<td>Limited resources, slow </td>\n</tr>\n<tr>\n<td><strong>GoDaddy Domains</strong></td>\n<td>$1.99+ </td>\n<td>Frequent promotions </td>\n<td>Expensive renewals, upsells</td>\n</tr>\n</tbody>\n</table>\n</figure>\n<p>Yep! So there’s your cheat sheet to cheap (or free) web hosting. Hope this saves you some money!</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 7,
                        "name": "Where the User Begins",
                        "slug": "where-the-user-begins"
                    },
                    {
                        "id": 8,
                        "name": "Beneath the Stack",
                        "slug": "beneath-the-stack"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/how-to-ssr-with-apollostack-and-meteor-react-router-ssr/",
            "url": "https://geekist.co/how-to-ssr-with-apollostack-and-meteor-react-router-ssr/",
            "title": "How to SSR with `apollostack` and `meteor-react-router-ssr`",
            "summary": "Learn how to set up SSR with Apollo and Meteor-React-Router-SSR, handling initial state hydration, preRender hooks, and routing tweaks.",
            "image": "https://img.geekist.co/wp-content/uploads/2025/03/a552d87e-1cc0-4972-a004-9da84651aaf8-1.avif",
            "date_published": "2016-11-17T20:00:00Z",
            "date_modified": "2026-11-15T12:33:28Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Geekery",
                "Tools of the Trade",
                "Tame the Tech"
            ],
            "content_html": "<p>💡</p>\n<p><em>Originally written in 2016, when Meteor was still a solid choice for full-stack JavaScript. Preserved as is, with updated links where needed.</em></p>\n\n<p>Wiring up meteor with Apollo and adding a router was easy enough, but getting server-side rendering and populating the client with an initial state was quite challenging. </p>\n<p>The documentation at <a href=\"http://dev.apollodata.com/\">dev.apollodata.com</a> is <em>fairly</em> extensive but ridiculous to navigate. The sidebar is filled with menu items that only appear as you scroll – making it impossible to locate <em>that</em> piece of information that you were sure you read somewhere. It would really help if they had an option to search too.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/ca3b452e-4a8d-426f-b887-f85f978c6683-800x600.avif\" alt=\"Captain Jean-Luc Picard from Star Trek performing a facepalm, expressing frustration\" /><figcaption>When the docs sidebar expands only after you scroll—and that one crucial link vanishes into oblivion.</figcaption></figure>\n<p>After piecing in bits and bytes from all over the place,  I am writing this in the hope that it might make your life a little easier if you were after the same thing. First, I had to hack <code>meteor-react-router-ssr</code> and move <code>preRender</code> down so it runs after the <code>wrapperHook</code>. I also added <code>app</code> as an argument. (See below)</p>\n<p>Here’s how my isomorphic <code>index.jsx</code> looks after that:</p>\n<pre>import React from 'react';\nimport { Meteor } from 'meteor/meteor';\n/*\n* Had to hack server.jsx in meteor-react-router-ssr to move the  \n* `preRender` hook so it runs after `wrapperHook` and I had to \n* give it {app} as an extra  argument.\n*/\nimport { ReactRouterSSR } from 'meteor/jasonnathan:react-router-ssr';\nimport ReactHelmet from 'react-helmet';\nimport AppRoutes from '/imports/routes.jsx';\nimport ApolloClient, { createNetworkInterface } from 'apollo-client';\nimport { getDataFromTree } from &amp;amp;quot;react-apollo/server&amp;amp;quot;;\nlet client, initialState,\n  url = &amp;amp;quot;localhost&amp;amp;quot;,\n  opts = {\n    ssrMode: Meteor.isServer\n  };\n// relevant for apollo when a client-side query is made\nif (Meteor.isClient &amp;amp;amp;&amp;amp;amp; process.env.NODE_ENV === 'production') {\n  url = &amp;amp;quot;public-url.com&amp;amp;quot;;\n}\n// setup apollo's networkInterface\nopts.networkInterface = createNetworkInterface({\n  credentials: 'same-origin', \n  uri: `http://${url}:3000/graphql`\n});\nconst rehydrateHook = state =&amp;amp;gt; initialState = state;\nconst wrapperHook = app =&amp;amp;gt; {\n  opts.initialState = initialState;\n  client = new ApolloClient(opts);\n  return { app };\n};\n// the preRender is simpler. All it needed was the `app` argument\nconst preRender = (req, res, app) =&amp;amp;gt; \n  Promise.await(getDataFromTree(app));\n// dehydrating in a way that is apollo friendly. \n// Queries &amp;amp;amp; mutations need to be removed\nconst dehydrateHook = () =&amp;amp;gt; ({\n  apollo: { \n    data: client.store.getState().apollo.data \n  }\n});\nconst htmlHook = html =&amp;amp;gt; {\n  const h = ReactHelmet.rewind();\n  return html.replace(\n    '', '' + h.title + h.base + h.meta + h.link + h.script\n  );\n};\n// the weirdest thing - wrapperHook in clientOptions - \n// inferring it only runs on the client\nconst clientOptions = { wrapperHook, rehydrateHook };\nconst serverOptions = { htmlHook, preRender, dehydrateHook };\nReactRouterSSR.Run(AppRoutes(), clientOptions, serverOptions);</pre>\n\n<pre>import React from 'react';\nimport { Meteor } from 'meteor/meteor';\n/*\n* Had to hack server.jsx in meteor-react-router-ssr to move the  \n* `preRender` hook so it runs after `wrapperHook` and I had to \n* give it {app} as an extra  argument.\n*/\nimport { ReactRouterSSR } from 'meteor/jasonnathan:react-router-ssr';\nimport ReactHelmet from 'react-helmet';\nimport AppRoutes from '/imports/routes.jsx';\nimport ApolloClient, { createNetworkInterface } from 'apollo-client';\nimport { getDataFromTree } from \"react-apollo/server\";\nlet client, initialState,\n  url = \"localhost\",\n  opts = {\n    ssrMode: Meteor.isServer\n  };\n// relevant for apollo when a client-side query is made\nif (Meteor.isClient &amp;amp;&amp;amp; process.env.NODE_ENV === 'production') {\n  url = \"public-url.com\";\n}\n// setup apollo's networkInterface\nopts.networkInterface = createNetworkInterface({\n  credentials: 'same-origin', \n  uri: `http://${url}:3000/graphql`\n});\nconst rehydrateHook = state =&amp;gt; initialState = state;\nconst wrapperHook = app =&amp;gt; {\n  opts.initialState = initialState;\n  client = new ApolloClient(opts);\n  return { app };\n};\n// the preRender is simpler. All it needed was the `app` argument\nconst preRender = (req, res, app) =&amp;gt; \n  Promise.await(getDataFromTree(app));\n// dehydrating in a way that is apollo friendly. \n// Queries &amp;amp; mutations need to be removed\nconst dehydrateHook = () =&amp;gt; ({\n  apollo: { \n    data: client.store.getState().apollo.data \n  }\n});\nconst htmlHook = html =&amp;gt; {\n  const h = ReactHelmet.rewind();\n  return html.replace(\n    '', '' + h.title + h.base + h.meta + h.link + h.script\n  );\n};\n// the weirdest thing - wrapperHook in clientOptions - \n// inferring it only runs on the client\nconst clientOptions = { wrapperHook, rehydrateHook };\nconst serverOptions = { htmlHook, preRender, dehydrateHook };\nReactRouterSSR.Run(AppRoutes(), clientOptions, serverOptions);</pre>\n<p>And here’s the modified portion of react-router-ssr: </p>\n\n<pre>// from line 190      \n// if (serverOptions.preRender) {\n//   serverOptions.preRender(req, res);\n// }\n//...\nglobal.__STYLE_COLLECTOR_MODULES__ = [];\nglobal.__STYLE_COLLECTOR__ = '';\nrenderProps = {\n  ...renderProps,\n  ...serverOptions.props\n};\nfetchComponentData(serverOptions, renderProps);\n  let app;\n  if (typeof clientOptions.wrapperHook === 'function') {\n     app = clientOptions.wrapperHook(app);\n  }\n    // preRender moved after wrapperHook\n  if (serverOptions.preRender) {\n    serverOptions.preRender(req, res, app);\n  }</pre>\n<p>That’s it! You can grab a copy of the modified <code>meteor-react-router-ssr</code> from <a href=\"https://github.com/jasonnathan/meteor-react-router-ssr\">here</a></p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 6,
                        "name": "Tools of the Trade",
                        "slug": "tools-of-the-trade"
                    },
                    {
                        "id": 9,
                        "name": "The Geekery",
                        "slug": "the-geekery"
                    }
                ],
                "references": {
                    "mentions_mcp": false,
                    "github_links": [
                        "https://github.com/jasonnathan/meteor-react-router-ssr"
                    ],
                    "public_product_links": [],
                    "public_products": []
                }
            }
        },
        {
            "id": "https://geekist.co/this-is-a-wordpress-blog-what-well-kinda/",
            "url": "https://geekist.co/this-is-a-wordpress-blog-what-well-kinda/",
            "title": "This is a WordPress Blog. What? Well.., kinda",
            "summary": "Using WordPress.com as a headless CMS with GraphQL and React-Apollo to power a custom website. A practical approach to WordPress APIs.",
            "image": "https://img.geekist.co/wp-content/uploads/this-is-a-wordpress-blog-what-well-kinda.avif",
            "date_published": "2016-10-29T20:00:00Z",
            "date_modified": "2026-10-29T22:00:59Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tame the Tech",
                "Tools of the Trade"
            ],
            "content_html": "<p>💡</p>\n<p><em>Originally written in 2016, when WordPress APIs were gaining traction for headless CMS setups. Preserved as is, with updated links where needed. A 2025 follow-up is on the way!</em></p>\n\n<p>WordPress is convenient, as much as I hate to admit it, it is. I’m not using WordPress as my primary website because it is loaded with way more stuff then you’d probably ever need to use. To be fair, it needs to cater to as many use cases as possible (hence a CMS).</p>\n<p>However, if all you need is to write a bunch of articles and you intend to code up your own website, then <a href=\"https://developer.wordpress.com/docs/api/console/\">WordPress.com’s API</a> might just be your answer…</p>\n<p>I write these articles on <a href=\"http://WordPress.com\">WordPress.com</a> and use <a href=\"https://jasonnathan.wordpress.com/work/graphql\">GraphQL to query</a> the endpoints. I wire up the everything using <code>react-apollo</code>, add some styles and, well here we are. (You are reading this on my website aren’t you?)</p>\n<p>I wish I found time to clean every thing up and publish little packages for you guys to use 🙁</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 6,
                        "name": "Tools of the Trade",
                        "slug": "tools-of-the-trade"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/5-steps-to-your-tech-startup-mvp/",
            "url": "https://geekist.co/5-steps-to-your-tech-startup-mvp/",
            "title": "5 Steps to your tech startup MVP",
            "summary": "Launching your startup? Learn the 5 key steps to build a solid MVP: focus, prototype, and choose the right tech stack for success!",
            "image": "https://img.geekist.co/wp-content/uploads/2025/03/46b226cf-103d-40c9-ac67-ef76619b75ac-1.avif",
            "date_published": "2016-08-21T20:00:00Z",
            "date_modified": "2026-10-29T22:55:00Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Tame the Tech",
                "Tools of the Trade"
            ],
            "content_html": "<p>💡</p>\n<p><em>This post was written in 2016 and is preserved as-is except that the links have been updated or removed. I’ll be writing a follow-up post about this topic but the content here remains very relevant, even today</em></p>\n\n<p>I’ve met with many people who have an idea for a startup but have very little information about what to do next. If you haven’t acquired funding, then a MVP will definitely help but even if you have, this next bit is still very relevant.</p>\n<p>This list is sorted in an order that many people seem to think in. They ask questions starting on the top first and eventually dig deeper as they move along. I chose to use the same order so it may be easier to understand why something is important.</p>\n<h3>1. Decide which platform(s) you need to support.</h3>\n<p>If you’re targeting mobile devices, you can’t stop at deciding which OS (Android, iOS) etc. You will also need to decide which version(s) of the OS to support. Older versions generally have more bugs, older hardware and lack many features. If you have the expertise to do it, then follow the trend of <em>current + last two versions</em>. For example:</p>\n<ul>\n<li>Android 7 (6 &amp; 5) </li>\n<li>iOS 10 (9 &amp; 8)</li>\n</ul>\n<p>While we’re on mobile apps, there’s a common sentiment in the industry about <a href=\"https://geekist.co/articles/startups/hybrid-vs-native-the-age-old-debate-revisited\">hybrid vs. native</a> apps where the former is less performant &amp; easier to develop than the latter. With the popularity of Facebook’s React &amp; React Native, a native app is marginally more work that a hybrid app. Also, modern browsers, techniques and packages can make a hybrid application’s performance difference somewhat negligible and fairly unnoticeable depending on your product.</p>\n<p>Choose based on your budget and resources available to you. If you have access to a web based developer, chances are he’d have little trouble moving into hybrid development</p>\n<p>It doesn’t get easier if you’ve got a browser (or web) application. Not only are there more browsers than there are mobile operating systems, there are also different versions of the same browser per OS. Have a look at <a href=\"http://caniuse.com/#comparison\">CanIUse</a> to have an idea. Again, if you can, the trend is also <em>current + last 2 version</em></p>\n<p>Do you really need to support all these versions?</p>\n<h3>2. Know your target audience.</h3>\n<p>Ever wonder why it is one of the very first questions a potential investor will ask you? It isn’t only because they want to know how much money your idea can generate but also to calculate how much it will cost to develop your idea.</p>\n<p>It is important to find out who your <strong>first</strong> customers will be. The number of these people depends on your application. If it’s a B2B offering, chances are you’d need to know who your first 10-100 customers are.</p>\n<p>If it’s a trendy B2C offering, you’d be looking at your first 200-500 customers. Think about who they’d be, what they are like and how they would best use your product.</p>\n<p>The demographics of <em>first</em> customers will greatly help in deciding.</p>\n<h3>3. Identify your core feature (and strip everything else out).</h3>\n<p>A lot of startups begin with one idea that quickly turns into twenty different features, mostly out of fear that the product won’t feel “complete” enough. This is a common mistake.</p>\n<p>Your MVP should focus strictly on your core, killer feature – the single, unique thing that solves your customer’s primary problem. Anything beyond that should go onto your “future ideas” list. Keep it lean at first because this saves your budget, development time, and sanity.</p>\n<p>Did I mention time and money? <strong>I cannot stress this enough!</strong></p>\n<p>Besides, extra features might confuse your initial audience or, worse yet, distract you from delivering something genuinely valuable. Remember, it’s far better to do one thing brilliantly than ten things mediocrely.</p>\n<h3>4. Sketch, prototype, and validate quickly.</h3>\n<p>Before you spend weeks or months coding, grab pen and paper or any rapid prototyping tool like <em>InVision</em>, <a href=\"https://balsamiq.com/\">Balsamiq</a>, <a href=\"https://www.sketch.com/\">Sketch</a> (pick your favourite poison) and sketch out exactly how your app should work. Don’t get fancy; stick-figure sketches are perfectly fine.</p>\n<p>Now, put these sketches in front of your potential customers. Remember the ones you identified in step 2?</p>\n<blockquote>\n<p><em>Get brutally honest feedback.</em></p>\n</blockquote>\n<p>The quicker you validate your assumptions, the less likely you’ll waste valuable resources building the wrong thing. This rapid-feedback loop will save you from painful pivots down the line.</p>\n<p>Remember: prototypes aren’t about <em>perfection</em>, they’re about <em>clarity</em> and <em>validation</em>.</p>\n<h3>5. Decide how you’ll build it (your tech stack).</h3>\n<p>By now, you’ve figured out your platform, audience, and core functionality. Next up: deciding exactly what technologies you’ll use. Your choice of tech stack can impact everything from initial development speed, scalability, ongoing costs, and even hiring down the line.</p>\n<p>Choosing your tech stack depends largely on your existing team or access to talent. Some of the most flexible and widely used options today include <a href=\"https://nodejs.org/\">Node.js</a> for backend development (ideal for rapid development and scalability), <a href=\"https://react.dev/\">React</a> or <a href=\"https://angular.io/\">Angular</a> for frontend web applications, and <a href=\"https://reactnative.dev/\">React Native</a> or <a href=\"https://developer.apple.com/swift/\">Swift</a> / <a href=\"https://developer.android.com/kotlin\">Kotlin</a> for mobile apps.</p>\n<p>Avoid falling into the latest-trend trap. Evaluate your choices based on maintainability, hiring potential, community support, and available resources.</p>\n<p>Seriously, you’ll thank yourself later!</p>\n<p>And there you have it: 5 critical steps to bring clarity to your MVP journey. While every startup’s path is unique, following this approach can help you avoid common pitfalls and ensure you’re building something your customers actually need.</p>\n<p>Remember, at this stage, agility is everything. Keep listening to your users, refine your idea quickly, and don’t hesitate to pivot if your data points in a new direction. With focus, feedback, and a bit of grit, you’re already ahead of most.</p>\n<p>Good luck! And happy building!</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 6,
                        "name": "Tools of the Trade",
                        "slug": "tools-of-the-trade"
                    }
                ]
            }
        },
        {
            "id": "https://geekist.co/building-a-zoomable-ui-with-meteor-js-greensock/",
            "url": "https://geekist.co/building-a-zoomable-ui-with-meteor-js-greensock/",
            "title": "Building a Zoomable UI with Meteor.js & Greensock",
            "summary": "An exploration of Zoomable User Interfaces (ZUIs) with Meteor.js and Greensock & a unique responsive UI design technique",
            "image": "https://img.geekist.co/wp-content/uploads/2016/12/jasonnathan_article-1.avif",
            "date_published": "2015-01-03T20:00:00Z",
            "date_modified": "2026-11-15T12:33:46Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "The Geekery",
                "Where the User Begins",
                "Tame the Tech"
            ],
            "content_html": "<p>💡</p>\n<p><em>This article was originally published in January 2015 and reflects the tools, techniques, and trends of that time. It showcases the implementation of a Zoomable User Interface (ZUI) using Meteor.js and Greensock’s GSAP library, along with LESS for layout styling. The screenshots and examples, along with the narrative, remain intentionally unaltered to preserve the authenticity of the original work so it reflects the web development landscape of 2015.</em></p>\n\n<p>In the journey through web user interfaces and experiences, I had always wondered if there was a way to present a UI with all of the content and information visible, just tucked away within different portions of the viewport until needed. </p>\n<p>Sounds messy? I thought so too. So I did some research out of curiosity and stumbled upon a few techniques. One such technique was a <strong>Zoomable User Interface</strong> or <strong>ZUI</strong> as it’s commonly known (think Google Maps) and one such website that implemented it was <a href=\"http://2011.beercamp.com/\">beercamp</a>.</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/2025/04/a3553b44-38a1-4495-9a26-98456843668c-800x498.avif\" alt=\"Poster for Beercamp at SXSW 2011, with bold stylised fonts and event details.\" title=\"Beercamp at SXSW 2011\" /></figure>\n<p>I decided to create one of my own, using Greensock’s awesome <a href=\"https://greensock.com/gsap\">GSAP</a> library.  So, together with designer, Daniel, who designed the look and layout, I set out to rework jasonnathan.com to a cool new site featuring ZUI. I decided to give CSS frameworks a miss this time, the design was simple and I wanted to use <a href=\"https://www.w3.org/TR/css-flexbox-1/\">FlexBox</a>. I did however, <a href=\"https://github.com/jasonnathan/jasonnathan.meteor.com/tree/version-stitch/client/less\">import a few LESS</a> files to get quickly started for the project. </p>\n<p>My first attempt was complete disaster! I wanted the site responsive so I tried to create a fluid layout where elements adjusted itself to spread out over the viewport. It worked, but it simply did not have the same feel as the original design. I then settled with a fixed ratio. Using a simple <code>LESS</code> <code>mixin</code> and <code>vh</code>, <code>vw</code> units for measure, I wrote:</p>\n\n<pre>/* This version is adapted from http://stackoverflow.com/a/24894523/382536 to  \n* constrain width to 100% height instead.\n*\n* param {Number} @x - width\n* param {Number} @y height\n*/\n.viewportRatio(@x, @y) {\n  @height:100vh;\n  @width: (@x * 100vh / @y);\n  @max-height:( @y / @x * 100vw);\n  @max-width: 100vw;\n}\n//usage\n#constrainContainer{ \n/** or body, aspect ratio is 3:4 */\n  .viewportRatio(3, 4);\n  height: @height;\n  width: @width;\n  max-height: @max-height;\n  max-width: @max-width;\n  position:relative;\n}\n.Page{\n  position:absolute;\n  top:0;\n  left:0;\n  right:0;\n  bottom:0;\n}\n#contact{\n  /* 1/3 of total area*/\n  transform:scale(.3333);\n}\n#works{\n  /* 1/6 of total area  */\n  transform:scale(.1111);\n}</pre>\n<p>The second attempt, while it was super simple to implement, was just not cross-browser friendly enough. Another disaster. In the end, I opted for a mostly absolutely positioned layout – another first for me in web design. (Perhaps, I should have had a quick look at <a href=\"https://github.com/philipwalton/flexbugs\">Flexbugs</a> or even tried some <a href=\"https://gist.github.com/jayj/4012969\">LESS</a> <a href=\"https://github.com/ProLoser/Flexbox.less\">Mixins</a>!). Add some skeuomorphic juicy bits and I ended up with:</p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/9beb2889-4a4a-4a6f-84f3-129ab2cddf33.avif\" alt=\"Screenshot of a zoomable portfolio homepage with the name Jason, links to mobile developer and designer profiles, and a navigation ribbon\" title=\"Jason’s Zoomable User Interface Showcase\" /></figure>\n<p>With the exception of the top header, it’s a standard 3-column layout with the middle column left empty to show the scaled-down pages. I wanted markup to be as simple as possible too. I created a single container with constrained proportions using the <code>LESS</code> <code>mixin</code> above and each subsequent page was absolutely positioned inside it.</p>\n\n<pre>&lt;!--The master layout for a zoomable user interface. --&gt;\n&lt;nav&gt;\n  &lt;ul&gt;\n    &lt;li&gt;&lt;a href=\"#start\" id=\"startMenu\"&gt;Start&lt;/a&gt;&lt;/li&gt;\n    &lt;li&gt;&lt;a href=\"#contact\" id=\"contactMenu\"&gt;Links&lt;/a&gt;&lt;/li&gt;\n    &lt;li&gt;&lt;a href=\"#works\" id=\"worksMenu\"&gt;Works&lt;/a&gt;&lt;/li&gt;\n  &lt;/ul&gt;\n&lt;/nav&gt;\n&lt;div id=\"constrainContainer\"&gt;\n  &lt;div class=\"Page\" id=\"start\"&gt;&lt;/div&gt;\n  &lt;div class=\"Page\" id=\"contact\"&gt;&lt;/div&gt;\n  &lt;div class=\"Page\" id=\"works\"&gt;&lt;/div&gt;\n&lt;/div&gt;</pre>\n<p>Now, I just had to add some GSAP goodness… 🙂 </p>\n\n<pre>/**\n* This was written in Meteor JS, these globals are directly accessible thanks\n* to Meteor's Smart Packages\n* \n* @globals _, $, TimelineLite, TweenLite\n* \n*/\n  _Animation = {\n    tl: new TimelineLite,\n    /**\n     * A simple helper method that removes .active class from menu items and\n     * adds it to given element.\n     * \n     * @param {Object} elementToAdd - jQuery object\n     */\n    removeActive: function(elementToAdd) {\n      $(\"#mainNav a\").each(function() {\n        return $(this).removeClass('active');\n      });\n      return elementToAdd &amp;amp;&amp;amp; elementToAdd.addClass('active');\n    },\n    /**\n     * Another helper method that builds an options object for Tweenlite\n     * \n     * @params {Object} params - a hash of options\n     * @return {Object} TweenLite\n     */ \n    tw: function(element, scale) {\n      // we add a 1.1 second total animation time\n      return TweenLite.to(element, 1.1, {\n        scale: scale,\n        force3D: true, // force hardware accelerated animations if possible\n        ease: Power4.easeIn\n      });\n    },\n    /**\n     * Animation for Start Page\n     * \n     * returns {Object} _Animation - self\n     */ \n    start: function(element) {\n      var self = this;\n      // remove active class from all other menus and add one for this one  \n      self.removeActive(element);\n      // add each tween to the timeline, scales to 1\n      self.tl.add(self.tw(\"#start\", 1))\n        // scales to 1/3 of original scale\n        .add(self.tw(\"#contact\", .3333), \"-=1.1\") \n        // scales to 1/6 of original scale        \n        .add(self.tw(\"#works\", .1111), \"-=1.1\");\n      return self;\n    },\n    /**\n     * Animation for Contact Page\n     * \n     * returns {Object} _Animation - self\n     */     \n    contact: function(element) {\n      var self = this;\n      // remove active class from all other menus and add one for this one  \n      self.removeActive(element);\n      // now the start page scales to 7.5\n      self.tl.add(self.tw(\"#start\", 7.5))\n        // scales to original scale since it is in view now\n        .add(self.tw(\"#contact\", 1), \"-=1.1\") \n        // scales to 1/3 of original scale        \n        .add(self.tw(\"#works\", .3333), \"-=1.1\");\n      return self;\n    },\n    /**\n     * Animation for Works Page\n     * \n     * returns {Object} _Animation - self\n     */       \n    works: function(element) {\n       var self = this;\n      // remove active class from all other menus and add one for this one  \n      self.removeActive(element);\n      // now the start page scales to 7.5\n      self.tl.add(self.tw(\"#start\", 7.5))\n        // scales to 7.5\n        .add(self.tw(\"#contact\",  7.5), \"-=1.1\") \n        // scales to original scale since it is in view now   \n        .add(self.tw(\"#works\", 1), \"-=1.1\");\n      return self;\n    }\n  }\n// Meteor's startup function called when DOM is loaded  \nMeteor.startup(function(){\n  /**\n   * The click handler for the menu items\n   */ \n   _.each(['#start', '#contact', '#works'], function(item){\n     // create a jQuery Object. Menu items are just appended with 'Menu'\n     var element = $(item + \"Menu\");\n     element.on('click', function(e){\n       e.preventDefault();\n       // check if a method is defined\n       if(_Animation[item] &amp;amp;&amp;amp; typeof _Animation[item] === 'function'){\n         // call the method, giving the parent Object as context\n         return _Animation[item].call(_Animation, element);\n       }\n     });\n   });  \n})</pre>\n<p>To mimic beercamp’s easing, I chose the easing method above. It was close enough. I would still like to go back to it and get it right when I have the time. </p>\n<p><strong><em>Edit</em></strong>*: I have changed the easing and you can see the changes in the repository* </p>\n<p>That’s it! In my next post, I will talk about SEO techniques I adopted for the site and why it was deliberately made with very little content. </p>\n<p>Do have a look at the completed source on <a href=\"https://github.com/jasonnathan/jasonnathan.meteor.com\">Github</a>.</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 7,
                        "name": "Where the User Begins",
                        "slug": "where-the-user-begins"
                    },
                    {
                        "id": 9,
                        "name": "The Geekery",
                        "slug": "the-geekery"
                    }
                ],
                "references": {
                    "mentions_mcp": false,
                    "github_links": [
                        "https://github.com/jasonnathan/jasonnathan.meteor.com/tree/version-stitch/client/less",
                        "https://github.com/philipwalton/flexbugs",
                        "https://github.com/ProLoser/Flexbox.less",
                        "https://github.com/jasonnathan/jasonnathan.meteor.com"
                    ],
                    "public_product_links": [],
                    "public_products": []
                }
            }
        },
        {
            "id": "https://geekist.co/wordpress-mvc-plugin-development/",
            "url": "https://geekist.co/wordpress-mvc-plugin-development/",
            "title": "WordPress MVC Plugin Development",
            "summary": "Build a WordPress MVC plugin with custom routing, controller logic, and clean structure. Ideal for devs modernising WP admin tools.",
            "image": "https://img.geekist.co/wp-content/uploads/2025/03/8c86ea90-ad86-4600-a9b6-d9b38a33b8ed.avif",
            "date_published": "2010-09-28T20:00:00Z",
            "date_modified": "2026-11-14T23:58:36Z",
            "authors": [
                {
                    "name": "GuruGeek"
                }
            ],
            "tags": [
                "Where the User Begins",
                "Tame the Tech",
                "Tools of the Trade"
            ],
            "content_html": "<h2>A Simple Router for WordPress Plugins</h2>\n\n<p>💡</p>\n<p>This article was originally published in 2010 and was deliberately preserved as it was written for WordPress 3.0, released in June 2010, when custom post types and menus were introduced. It still works for WordPress 6.7.1 in 2024, and you can find the updated article <a href=\"https://geekist.co/wordpress-mvc-plugin-reboot-2024/\">here</a></p>\n\n<p>I was working on creating a simple CRM plugin for WordPress. My first plugin yet. I needed something lightweight and very specific to my work in real estate. After some searching, I didn’t find anything suitable- unsurprisingly.</p>\n<p>So, I set out to make this plugin. I divided the functionality into two parts. The first: basic CRM functions to view contacts, reminders, opportunities, etc. The second: advanced features like syncing, auto-reminder templates, and automated emails.</p>\n<p>After creating my first single-handed website with Kohana 2.4, I realised the importance of an administrative backend – not just any admin panel, but something apt for managing the site AND adding new functionality.</p>\n<p>ere's where I learnt the point of CMSes, really only because I hate tiresome learning curves, and eventually – because I was already using it: WordPress.</p>\n<p>Don’t get me wrong; I absolutely LOVE Kohana and am already trying to master Kohana 3, but that’s a topic for another day. Before I digress further from this (intended short!) introduction, let's better get started.</p>\n<p>I’ve grown too comfortable with the MVC approach, where URL segments map to methods in a controller. After dissecting a few plugins, I realised WordPress doesn’t really have a straightforward router to decide which method or function runs. So, I decided to create a utility class to handle routing. It wouldn’t change how the URLs look but would at least know what to run automatically.</p>\n<h3>The Router Class</h3>\n\n<pre>class Router\n{\n  /**\n   * Sets up the routing logic based on provided controller, method, and arguments.\n   * Falls back to defaults if specific routes are unavailable.\n   *\n   * @param array $route [controller, method, args]\n   * @param string $default_controller Default controller to use\n   * @param string $default_method Default method to use\n   */\n  public function __construct($route, $default_controller, $default_method)\n  {\n    // Attempt specified route, fallback to defaults if it fails\n    $try = $this-&amp;gt;route_it($route, $default_method);\n    if ($try === false) {\n      $this-&amp;gt;default_route_it(\n        $default_controller,\n        $default_method,\n        $route[2]\n      );\n    }\n  }\n  /**\n   * Attempts to execute the specified route (controller, method, args).\n   *\n   * @param array $route [controller, method, args]\n   * @param string $default_method Default method to fallback to\n   * @return mixed\n   */\n  public function route_it($route, $default_method)\n  {\n    $controller = $route[0];\n    $method = $route[1];\n    $parameters = $route[2] ?? null;\n    $obj = is_object($controller) &amp;amp;&amp;amp; ($controller instanceof $controller)\n      ? $controller\n      : (class_exists($controller) ? new $controller() : false);\n    if (!$obj) {\n      return false;\n    }\n    return method_exists($obj, $method)\n      ? $obj-&amp;gt;$method($parameters)\n      : (method_exists($obj, $default_method)\n          ? $obj-&amp;gt;$default_method($parameters)\n          : false);\n  }\n  /**\n   * Fallback to default controller and method if routing fails.\n   *\n   * @param string $controller Default controller\n   * @param string $method Default method\n   * @param mixed $parameters Optional arguments\n   * @return mixed\n   */\n  public function default_route_it($controller, $method, $parameters = null)\n  {\n    $obj = is_object($controller) &amp;amp;&amp;amp; ($controller instanceof $controller)\n      ? $controller\n      : (class_exists($controller) ? new $controller() : false);\n    if (!$obj) {\n      return false;\n    }\n    return method_exists($obj, $method)\n      ? $obj-&amp;gt;$method($parameters)\n      : false;\n  }\n}</pre>\n<p>Of course, this is a very basic class. We could probably enhance with error and/or exception or autoload classes in the include path but I this is the basic idea behind the router.</p>\n<h3>Using the Router in the Parent Controller</h3>\n<p>I decided the respective controllers would be defined in the <code>$_GET['page']</code> variable since that’s how WordPress admin navigates plugin pages. The method would come from <code>$_GET['action']</code>. Finally, the remaining <code>$_GET</code> variables would be the arguments.</p>\n<p>Here’s how it might look:</p>\n\n<pre>class CRM\n{\n  public function __construct()\n  {\n    // Initialize the request handler for routing plugin functionality\n    $request_handler = [$this, 'request_handler'];\n    // Add main menu and submenu entries for the plugin\n    add_menu_page(\n      'MY CRM',\n      'MY CRM',\n      4,\n      '?page=CRM',\n      $request_handler\n    );\n    add_submenu_page(\n      '?page=CRM',\n      'Contacts',\n      'Contacts',\n      4,\n      '?page=CRM',\n      $request_handler\n    );\n    add_submenu_page(\n      '?page=CRM',\n      'Opportunities',\n      'Opportunities',\n      4,\n      '?page=CRM_Opportunities',\n      $request_handler\n    );\n    add_submenu_page(\n      '?page=CRM',\n      'Reminders',\n      'Reminders',\n      4,\n      '?page=CRM_Reminders',\n      $request_handler\n    );\n  }\n  /**\n   * Processes incoming requests and invokes the router.\n   */\n  public function request_handler()\n  {\n    // Determine the controller from the \"page\" parameter\n    $controller = $_GET['page'];\n    // Default to \"index\" if no action is specified\n    $action = $_GET['action'] ?? 'index';\n    // Check if the request is for the current class\n    if ($controller == get_class($this)) {\n      $controller = $this;\n    }\n    // Extract additional parameters from GET variables\n    $params = $_GET;\n    unset($params['page'], $params['action']);\n    // Define the route for the router\n    $route = [$controller, $action, $params];\n    // Route the request using the Router class\n    $router = new Router($route, $this, 'index');\n  }\n  /**\n   * Default method when no specific action is specified.\n   */\n  public function index($args = null)\n  {\n    echo \"Welcome to My CRM.......\";\n  }\n}\nclass CRM_Opportunities\n{\n  /**\n   * Displays the opportunities page.\n   */\n  public function index($args = null)\n  {\n    echo \"The Opportunities Page\";\n  }\n  /**\n   * Handles the \"edit\" action for opportunities.\n   */\n  public function edit($args)\n  {\n    if ($_POST &amp;amp;&amp;amp; !empty($args['id'])) {\n      // Process data for editing an opportunity\n    }\n  }\n  /**\n   * Handles the \"delete\" action for opportunities.\n   */\n  public function delete($args)\n  {\n    // Logic to delete an opportunity\n  }\n}</pre>\n<h3>Example</h3>\n<p>If WordPress admin points to:</p>\n\n<pre>wp-admin/admin.php?page=CRM</pre>\n<p>The <code>CRM</code> controller runs, and since no action is specified, it defaults to the <code>index()</code> method.</p>\n<p>If the URL is:</p>\n\n<pre>wp-admin/admin.php?page=CRM_Opportunities&amp;amp;action=edit&amp;amp;id=1</pre>\n<p>The <code>CRM_Opportunities</code> controller loads, and the <code>edit()</code> method runs with the <code>id</code> argument.</p>\n<p><strong>Here are some screenshots:</strong></p>\n<figure><img src=\"https://geekist.co/wp-content/uploads/7e2ba504-2f7d-44f2-8360-46d9acbc57ee.avif\" alt=\"Screenshot of a WordPress admin CRM plugin interface showing the Add Contact form with name and email fields\" title=\"Add Contact - WordPress MVC Plugin Example (Controller: Contacts, Action: Add)\" /></figure>\n\n<figure><img src=\"https://geekist.co/wp-content/uploads/5aca9558-89f8-456f-8dfc-e18b3ecd2e91.avif\" alt=\"Screenshot of a WordPress CRM plugin dashboard listing contacts with a request info debug section\" title=\"Contacts Dashboard – WordPress MVC Plugin Overview (Controller: Contacts, Action: Index)\" /></figure>\n\n<h3>Closing Thoughts</h3>\n<p>You’ll still need to sanitize input and clean POST data, but this should give you an idea of implementing a simple router for controllers in plugin development.</p>\n<p>Let’s discuss in the comments!</p>",
            "_geekist": {
                "post_type": "post",
                "categories": [
                    {
                        "id": 5,
                        "name": "Tame the Tech",
                        "slug": "tame-the-tech"
                    },
                    {
                        "id": 6,
                        "name": "Tools of the Trade",
                        "slug": "tools-of-the-trade"
                    },
                    {
                        "id": 7,
                        "name": "Where the User Begins",
                        "slug": "where-the-user-begins"
                    }
                ]
            }
        }
    ],
    "_geekist": {
        "generator": "Geekist Article Knowledge",
        "knowledge_revision": "a95c22049820cafee484fcba9c9d7212818e379304c74aaa61db4fab57a3663f",
        "issues": []
    }
}
