# scaling Scaling is the ability to use available processing power on multiprocessor systems or service a large number of clients, including through scalable servers and distributed configurations. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Holy Moly uses one modular connector for flat-pack furniture DevFeed: [Holy Moly uses one modular connector for flat-pack furniture]() Original publisher: [Read original article]() Author: JC Torres Published: 2026-09-17T16:20:03Z Content type: article Language: en Sources: [Yanko Design]() Topics: [Hardware](), [scaling](), [locking]() Tags: [cabinets](), [concept-designs](), [connectors](), [design](), [flat](), [furniture](), [furniture-cabinets-concept-designs-perforated](), [hardware](), [hooks](), [locking](), [perforated](), [scaling]() ### AI overview The Holy Moly Cabinet replaces assorted flat-pack furniture fasteners with one clover-shaped connector that can serve as a door pull, leg, hinge, or shelf bracket. Its perforated steel panels allow components to be repositioned, stacked, and expanded using the same hardware. ### Source excerpt Holy Moly Is the Swiss Army Knife of Flat-Pack Furniture Hardware Most flat-pack furniture ships with a plastic bag full of different screws, dowels, and brackets, each one doing exactly one job and nothing else. The... ## Session revocations at scale DevFeed: [Session revocations at scale]() Original publisher: [Read original article]() Author: Llew Vallis Published: 2026-07-22T00:00:01Z Content type: article Language: en Sources: [Canva Engineering]() Topics: [sessions](), [Cookies](), [Authorization](), [Caching](), [MySQL](), [scaling](), [gateway](), [Redis](), [reliability]() Tags: [backend](), [caching](), [cookies](), [gateway](), [mysql](), [permissions](), [redis](), [reliability](), [scaling](), [security](), [sessions]() ### AI overview Canva describes how it manages session revocations for hundreds of millions of users. The system keeps revocations in memory for fast gateway checks, while MySQL handles refresh-time lookups; the article explains how loading the cache during deployments created database load and discusses evaluating Redis as a caching solution. ### Source excerpt How Canva keeps hundreds of millions of user sessions fast and secure ## Our Droidcon US 2026 Picks - Sam Hill DevFeed: [Our Droidcon US 2026 Picks - Sam Hill]() Original publisher: [Read original article]() Published: 2026-07-14T00:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Mobile](), [multiplatform](), [Kotlin](), [kotlin-native](), [AI Development](), [Artificial Intelligence](), [Rust](), [Testing](), [Gradle](), [scaling]() Tags: [2026](), [ai](), [ai-development](), [android](), [droidcon](), [gradle](), [ios](), [js](), [kmp](), [kotlin](), [kotlin-multiplatform](), [kotlin-native](), [multiplatform](), [rust]() ### AI overview Touchlab previews selected Droidcon USA 2026 talks covering AI and cross-platform mobile development, Kotlin Native project structures, KMP integration with Rust, migration decisions, and mobile testing. ### Source excerpt With Droidcon right around the corner, here are the talks we are most excited about ## Scaling a distributed cache: Why consistent hashing is mandatory DevFeed: [Scaling a distributed cache: Why consistent hashing is mandatory]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-05-17T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [consistent hashing](), [distributed-systems](), [Caching](), [sharding](), [scaling](), [Database](), [Memcached](), [Redis]() Tags: [caching](), [consistent-hashing](), [database](), [distributed](), [distributed-cache](), [distributed-systems](), [memcached](), [redis](), [scaling](), [sharding]() ### AI overview The article explains why modulo-based cache sharding can remap nearly every key when a node fails, causing a large cache miss surge and database overload. It presents consistent hashing on a fixed ring as a way to limit movement to keys assigned to the failed node, and notes that virtual nodes improve distribution across physical cache nodes. ### Source excerpt Sharding a cache with hash(key) modulo N means the denominator changes when a node dies, remapping nearly every key. Dropping from five nodes to four invalidates about 80 percent of the cache instantly and routes that miss storm straight at the primary database. Consistent hashing maps nodes and keys onto a fixed ring so only the dead node's keys move, and virtual nodes fix the uneven distribution a handful of physical nodes would otherwise produce. ## AI Strategy, Customer Value, and Innovation: A Conversation with Alexander Osterwalder DevFeed: [AI Strategy, Customer Value, and Innovation: A Conversation with Alexander Osterwalder]() Original publisher: [Read original article]() Author: David Pereira Published: 2026-04-30T07:56:48Z Content type: opinion Language: en Sources: [Untrapping Product Teams]() Topics: [Artificial Intelligence](), [AI Strategy](), [scaling](), [Users]() Tags: [ai](), [ai-strategy](), [models](), [scaling]() ### AI overview David Pereira summarizes a conversation with Alexander Osterwalder about AI strategy, innovation, customer value, protecting competitive moats, synthetic users, project selection, evidence, and scaling. The discussion argues that AI adoption does not replace strategic goals or conversations with real customers. ### Source excerpt AI is changing many things, not everything. ## Five Lessons from My Journey as a Platform Product Manager at REA DevFeed: [Five Lessons from My Journey as a Platform Product Manager at REA]() Original publisher: [Read original article]() Author: Sree Pradeep Published: 2026-03-20T00:31:53Z Content type: opinion Language: en Sources: [REA Group]() Topics: [internal developer platform](), [Platform Engineering](), [Developer Platform](), [scaling](), [reliability](), [Availability]() Tags: [availability](), [deploy](), [developer](), [infrastructure](), [internal-developer-platform](), [latency](), [life-at-rea](), [platform](), [platform-engineering](), [reliability](), [tech]() ### AI overview A platform product manager at REA shares lessons from working on the company's Internal Developer Platform. The article argues that platform success depends not only on infrastructure expertise but also on understanding engineers, simplifying complexity, building trust, and measuring platform impact despite imperfect metrics. ### Source excerpt Five Lessons from My Journey as a Platform Product Manager at REA When I started my journey in platform engineering, I worked on REA's Internal Developer Platform with the aim of giving engineers a fast, safe and simple way to build, deploy and run applications in production. I thought success meant mastering infrastructure, APIs, scaling and reliability. ## Swizec Teller on JS-Craft DevFeed: [Swizec Teller on JS-Craft]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-03-16T00:00:00Z Content type: article Language: en Sources: [Swizec Teller]() Topics: [scaling]() Tags: [craft](), [engineering](), [remote](), [remote-work](), [startup]() ### AI overview An interview with Daniel from JS-Craft about priorities, writing as an engineering skill, startup decisions, remote work, and lessons from Scaling Fast. ### Source excerpt Daniel from JS-Craft talks with Swizec Teller about priorities, writing, startup engineering, and Scaling Fast. ## AI in Investment Management: 2026 Outlook (Part II) DevFeed: [AI in Investment Management: 2026 Outlook (Part II)]() Original publisher: [Read original article]() Author: Emily Majewski Published: 2026-01-21T15:55:26Z Content type: opinion Language: en Sources: [Two Sigma Engineering]() Topics: [Artificial Intelligence](), [AI Models](), [LLMs](), [scaling](), [Compression]() Tags: [2026](), [ai](), [frontier-ai](), [llms](), [models]() ### AI overview Two Sigma leaders discuss how AI may change quantitative investment management, emphasizing productivity improvements, workflow integration, and the use of internal context. The article also highlights a shift toward efficiency, specialized architectures, neural compression, and improved model interpretability. ### Source excerpt The post AI in Investment Management: 2026 Outlook (Part II) appeared first on Two Sigma. ## Place good startup bets DevFeed: [Place good startup bets]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-01-14T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [scaling](), [Shopify](), [Database]() Tags: [core](), [equity](), [sales](), [scaling](), [shopify]() ### AI overview The author reflects on career and startup decisions, including regretting that he declined Shopify before its IPO. He argues that good bets limit downside, preserve upside, and are evaluated using factors such as problem interest, market access and growth, market size, unfair advantage, and early traction. ### Source excerpt You can't win every bet. Your goal is to be a little more right than wrong and keep playing ## Building, Scaling and Thinking in the Age of AI with Chip Huyen DevFeed: [Building, Scaling and Thinking in the Age of AI with Chip Huyen]() Original publisher: [Read original article]() Author: Zach Wilson Published: 2025-08-25T13:03:24Z Content type: article Language: en Sources: [DataExpert.io Newsletter]() Topics: [Artificial Intelligence](), [scaling]() Tags: [ai](), [building](), [scaling]() ### AI overview An article about building, scaling, and thinking in the age of AI, featuring Chip Huyen. ### Source excerpt Building, Scaling and Thinking in the Age of AI ## Scaling Server Sent Events - Intro to SSE and scaling guide DevFeed: [Scaling Server Sent Events - Intro to SSE and scaling guide]() Original publisher: [Read original article]() Author: Pranshu Raj Published: 2025-06-29T07:01:27Z Content type: tutorial Language: en Sources: [Pranshu Raj - blog on backend systems, performance and sidequests]() Topics: [Server-sent events (SSE)](), [scaling](), [HTTP](), [WebSocket]() Tags: [guide](), [scaling](), [sse]() ### AI overview A tutorial on Server-Sent Events (SSE), covering its HTTP-based server-to-client update model, event-stream format, browser EventSource support, and considerations for horizontal scaling and state handling. ### Source excerpt Understanding SSE and it's use cases, advantages over other realtime protocols, how to deploy it at scale. ## Rethinking Leadership in B2B SaaS: Lessons from Self-Managing Organizations DevFeed: [Rethinking Leadership in B2B SaaS: Lessons from Self-Managing Organizations]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2025-06-27T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Software as a service](), [scaling](), [structure](), [trust]() Tags: [b2b](), [collaboration](), [culture-leadership-decision-making-delegation-organizational-design](), [founders](), [leadership](), [saas](), [scaling](), [self-organizing](), [teams](), [trust]() ### AI overview An opinion article applies lessons from self-managing organizations such as Buurtzorg and Viisi to B2B SaaS teams. It argues that trust can be supported by clear roles, peer accountability, and shared expectations, and that role-based structures may help teams experiment and operate with less founder involvement. ### Source excerpt Rethinking Leadership in B2B SaaS: Lessons from Self-Managing Organizations Two months ago, I joined the Corporate Rebels Masterclass - a hands-on exploration of how pioneering companies like Buurtzorg, Haier, Viisi, and others approach leadership, structure, and collaboration. These aren't companies tinkering at the edges. They've built entire systems that challenge our default assumptions about how work should be organized. ## Building Scalable Mobile Projects at Android Makers 2025 DevFeed: [Building Scalable Mobile Projects at Android Makers 2025]() Original publisher: [Read original article]() Author: Cyril Mottier Published: 2025-04-10T08:37:01Z Content type: opinion Language: en Sources: [Cyril Mottier Blog]() Topics: [Mobile](), [scaling](), [builds](), [build times](), [maintenance]() Tags: [2025](), [build-times](), [builds](), [maintenance](), [mobile](), [scaling]() ### AI overview The article introduces a keynote on scaling mobile projects as codebases, contributor counts, and complexity grow. It highlights strategies for maintaining fast build times, reusable code, clear ownership, and resilient project structure. ### Source excerpt Edit - Aug 4: adding link to the video on YouTube I recently gave a keynote called "Building Scalable Mobile Projects: Fast Builds, High Reusability and Clear Ownership" at Android Makers 2025 in Paris. Here was the abstract. Every successful project eventually faces the challenges of scaling: an ever-growing codebase, an increasing number of contributors, and rising complexity. Without proper measures, this can lead to slow build times, a cluttered codebase, maintenance difficulties, code duplication, and even dead code--ultimately jeopardizing the company's ability to deliver value. ## Understanding and scaling Raft DevFeed: [Understanding and scaling Raft]() Original publisher: [Read original article]() Published: 2025-04-04T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Raft](), [consensus algorithm](), [distributed-systems](), [scaling](), [CockroachDB](), [Databases]() Tags: [cockroachdb](), [consensus-algorithm](), [databases](), [distributed-systems](), [raft](), [replication](), [scaling]() ### AI overview This tutorial explains the Raft consensus algorithm, including leader election, log replication, safety guarantees, and the network cost of consensus. It also introduces the Multi-Raft pattern for scaling distributed databases by splitting data into ranges with independent Raft groups. ### Source excerpt . [Understanding and Scaling Raft](understanding-and-scaling-raft-cover... ## Scaling Technology with Architectural Principles DevFeed: [Scaling Technology with Architectural Principles]() Original publisher: [Read original article]() Author: Shane Gibb Published: 2025-01-08T01:18:36Z Content type: article Language: en Sources: [REA Group]() Topics: [scaling](), [Software Engineering](), [Development](), [Continuous Deployment (CD)](), [maintenance](), [Design system](), [CI/CD]() Tags: [code](), [continuous-deployment](), [continuous-integration](), [design-system](), [engineering](), [maintenance](), [scaling](), [tech]() ### AI overview REA Group describes how architectural principles developed through 25 years of growth guide its software engineering practices, including decision-making, system resilience, team agility, platform reuse, and continuous deployment. ### Source excerpt REA Group, a global company with 1,000+ digital product builders, developed architectural principles from 25 years of growth. ## Piloting Kotlin Multiplatform is Easy. Scaling is Hard. - Kevin Galligan DevFeed: [Piloting Kotlin Multiplatform is Easy. Scaling is Hard. - Kevin Galligan]() Original publisher: [Read original article]() Published: 2024-08-07T00:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [scaling](), [Mobile](), [multiplatform](), [Development]() Tags: [development](), [kmp](), [kotlin](), [kotlin-multiplatform](), [mobile](), [multiplatform](), [scaling](), [swift](), [xcode]() ### AI overview The article explains why scaling Kotlin Multiplatform is more difficult than initial experimentation for native mobile teams. It argues that teams need to use KMP in feature development, reconsider library publishing and repository organization, and adopt an approach tailored to native Android and iOS teams. ### Source excerpt When native mobile teams explore KMP, getting started is pretty easy. The difficulty emerges when they try to scale. To get the most out of KMP for your team, and for KMP as a platform to succeed, we need to make scaling easy as well. ## KMP Team Adoption for Native Mobile: Workflow and Management Guidance DevFeed: [KMP Team Adoption for Native Mobile: Workflow and Management Guidance]() Original publisher: [Read original article]() Published: 2024-07-19T16:24:40Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [multiplatform](), [scaling](), [Mobile](), [Development](), [Kotlin](), [cross-platform]() Tags: [kmp](), [kotlin](), [management](), [mobile](), [native](), [scaling](), [teams](), [technology](), [workflow]() ### AI overview This article introduces the challenges teams face when adopting Kotlin Multiplatform for native mobile development. It argues that although KMP is stable and capable of sharing business logic, existing tooling and sample structures are largely designed for individual developers, making team-scale adoption difficult without new approaches and guidance. ### Source excerpt KMP for native mobile is mature technology. Best practice guidance for how teams should apply it is not. KMP has amazing potential, but presents unique workflow and management problems. Understanding these problems, and having a plan, is critical. ## Scaling Temporal: The basics DevFeed: [Scaling Temporal: The basics]() Original publisher: [Read original article]() Author: Rob Holland Published: 2023-05-23T08:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [scaling](), [Kubernetes](), [Monitoring](), [MySQL](), [Grafana](), [Prometheus]() Tags: [clusters](), [configuration](), [cpu](), [grafana](), [kubernetes](), [load-testing](), [memory](), [metrics](), [monitoring](), [mysql](), [performance](), [prometheus](), [scaling](), [temporal-concepts]() ### AI overview This tutorial explains a load-measure-scale-repeat process for scaling a self-hosted Temporal Cluster. It covers monitoring bottlenecks, Kubernetes resource management, Temporal shard configuration, polling optimization, and persistence sizing, using MySQL, Prometheus, and Grafana. ### Source excerpt A simple introduction to scaling Temporal Clusters with load testing and metrics ## ATOM (A Touch of Multiplatform) Episode #6 - Touchlab DevFeed: [ATOM (A Touch of Multiplatform) Episode #6 - Touchlab]() Original publisher: [Read original article]() Published: 2023-05-10T14:57:01Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Mobile](), [scaling](), [iOS](), [jetbrains]() Tags: [atom](), [jetbrains](), [kotlin](), [kotlin-multiplatform](), [mobile](), [mobile-development](), [multiplatform](), [podcast](), [scaling](), [thoughts]() ### AI overview Episode 6 of the A Touch of Multiplatform podcast discusses Josh Shin's path into mobile development and Volley's approach to adopting and scaling Kotlin Multiplatform, with particular attention to iOS. ### Source excerpt Welcome to episode 6 of A Touch of Multiplatform (ATOM)! This is our podcast dedicated to Kotlin Multiplatform technology in production and produced for you by JetBrains and Touchlab. In this episode of A Touch of Multiplatform, we sat down to talk with Volley's Josh Shin (along with special guest Suzu the cat). Josh talks about his own path into mobile development and about how Volley has approached adopting and scaling Kotlin Multiplatform, especially from the iOS side of things. ## Happy without hierarchies: Who cares for employee happiness if there are no hierarchies? DevFeed: [Happy without hierarchies: Who cares for employee happiness if there are no hierarchies?]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-03-04T06:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [scaling](), [structure](), [context]() Tags: [culture-employee-happiness-psychological-safety-organizational-design](), [leadership](), [scaling](), [structure](), [team](), [work]() ### AI overview An opinion article about supporting employee happiness in companies that avoid traditional hierarchies. It argues that employees should take responsibility for expressing their needs, while peers and the company provide trust, support, coaching, and guidance. ### Source excerpt Happy without hierarchies: Who cares for employee happiness if there are no hierarchies? Working with different clients has the benefit of discovering many contexts and with that, different perspectives, observations, and questions. ## Guidance for Scaling - Reversible vs. Irreversible Decisions DevFeed: [Guidance for Scaling - Reversible vs. Irreversible Decisions]() Original publisher: [Read original article]() Author: Map Published: 2021-12-29T21:30:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [scaling](), [Product Management]() Tags: [founders](), [growth](), [hiring](), [leadership](), [philosophies](), [scaling]() ### AI overview The article advises founders to empower newly hired functional leaders instead of micromanaging them. It recommends clearly communicating priorities and distinguishing reversible decisions from irreversible ones while scaling a business. ### Source excerpt Was having a conversation with a founder earlier today and the topic of hiring functional leaders came up. I offered one of my common pieces of advice which was don't hold the reins too tightly once you hire them. It's something I see happen over and over to first time founders. You hire a new VP of Product and then still continue to oversee so much of the product process yourself. It is understandable, it's your baby, you've spent years building it to this point, they don't love it the same way you do. The likely outcome is your new VP of product won't find success. They'll feel they're not able to execute on a vision of their own. They'll feel micromanaged. Even the smallest decisions they'll feel aren't fully theirs and get second guessed. Perhaps you could do it better, that's not necessarily the question. What you're focused on is growing and scaling, this is the reason you hired them. So how do you do this without the business careening off tracks? Well first, empower them to make decisions, but beyond that there are a few things you can do so you feel more comfortable entrusting them with their functional area. Communication is key First, clearly communicate your priorities and thought process. This doesn't mean tell them what to do, but priorities... Bob Iger states it as "You have to convey your priorities clearly and repeatedly. In my experience, it's what separates great managers from the rest". I couldn't immediately find the reference, but recall reading that he started each week with his execs communicating his top 5 priorities across the company. This gives you a line of sight into the leadership's thinking. This could be as simple as: I'm worried about our pipeline for next year I'm worried about retention and how it affects long term growth I'm worried that we have the tech stack to scale for next 3 years Something similar to that last one came up in the conversation, which led us down a brief conversation of reversibles and irreversibles. In product ## Searching for RH Counterexamples -- Scaling Up DevFeed: [Searching for RH Counterexamples -- Scaling Up]() Original publisher: [Read original article]() Published: 2021-02-16T09:00:00Z Content type: article Language: en Sources: [Jeremy Kun]() Topics: [Mathematics](), [hashing](), [scaling](), [sha256](), [hash](), [Database]() Tags: [architecture](), [disk-space](), [hashing](), [mathematics](), [performance](), [postgres](), [programming](), [refactor](), [riemann-hypothesis](), [scaling](), [sha256](), [software]() ### AI overview This article describes scaling a search for counterexamples to the Riemann Hypothesis. It focuses on reducing storage by keeping deterministic SHA-256 summaries instead of every witness value and refactoring the application into a worker architecture. ### Source excerpt We're ironically searching for counterexamples to the Riemann Hypothesis. Setting up Pytest Adding a Database Search Strategies Unbounded integers Deploying with Docker Performance Profiling Last time we made the audacious choice to remove primary keys from the RiemannDivisorSums table for performance reasons. To help with that, we will do two things in this post Reduce the storage footprint of the whole application (it was 60 GiB when it crashed, and we got up to 84 prime factors). ## Deep Dive into Maglev, Google's Load Balancer DevFeed: [Deep Dive into Maglev, Google's Load Balancer]() Original publisher: [Read original article]() Published: 2020-05-24T00:00:00Z Content type: article Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Google](), [consistent hashing](), [scaling](), [Software](), [Availability](), [Hardware]() Tags: [consistent-hashing](), [deep-dive](), [distributed](), [google](), [hardware](), [health](), [load-balancer](), [performance](), [scaling](), [software]() ### AI overview This article explains Maglev, Google's software load balancer, and summarizes design choices that support operation at Google's scale. It covers commodity hardware, distributed scale-out architecture, connection-tuple routing, line-rate traffic handling, Direct Server Return, Maglev hashing, reduced cross-thread synchronization, and backend health tracking. ### Source excerpt I recently heard about Maglev, the load balancer that Google uses in front of most of its services. I wanted to get a short gist on the matter to understand the reason why Google had to create its own load balancer and the optimizations that they took in order to actually run a load balancer at Google's scale... ## Why I love building developer products DevFeed: [Why I love building developer products]() Original publisher: [Read original article]() Author: Map Published: 2019-03-12T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Software](), [coding](), [systems](), [scaling](), [service]() Tags: [developer](), [developer-products](), [opinions](), [philosophies](), [product](), [scaling](), [software](), [systems]() ### AI overview An opinion piece explains why the author enjoys building developer-focused products. It highlights the potential for software and systems to improve life at scale, the challenge of serving skeptical developers, and the author's personal familiarity with developer-product work. ### Source excerpt For much of my career I've been focused on building out developer or data focused products with the customer in some form or fashion being a developer on the other end. I fully realize now that I'm destined to spend the rest of my career in that space, either that or trying my hand at wine making. There are a few things that I personally find rewarding about the space that I've shared with a number of people individually lately and thought I would share more broadly. First, software really is eating the world. Often developers and entrepeurs ask about what they could build that would be a good business. The reality is about anything that has not been modernized to as a service and improved with software could be. We have far less developers in the world than we need to execute on all the ways we could improve products and life. To me what is interesting is the last part of that last sentence. It is not that the market for developers is huge, which I do believe it is. It more that when we automate with systems we can get amazing economies of scale. I know folks that reminisce and talk about how we're more stressed being always connected and such and that in the old days people got out and worked the fields and enjoyed the sun. They also absolutely physically exhausted their bodies in the process. The ability to make life better at scale is an interesting one and often done through systems we develop. The second reason is the challenge and the reward. Developers are notoriously tough critics. If it feels/smells like marketing then they have an allergic reaction, and that is probably because much of it is done poorly. If they experience really positive/great marketing they latch on more than the average person. Most developers are by nature a bit skeptical... for some reason this resonates with me. But, I've found they are the largest/biggest supporters once they're excited about something. Personally I'd rather folks more critical and then have a few diehard fans than a [Next page]()