# tech stack Published articles for tech stack. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 5 Raspberry Pi Projects I Stopped Using and Why DevFeed: [5 Raspberry Pi Projects I Stopped Using and Why]() Original publisher: [Read original article]() Author: Patrick Fromaget Published: 2026-08-19T05:00:00Z Content type: article Language: en Sources: [RaspberryTips]() Topics: [Pi-hole](), [Jellyfin](), [Virtual Private Network](), [browser](), [Network](), [Playback]() Tags: [article](), [browser](), [dns](), [jellyfin](), [network](), [playback](), [plex](), [quick-tips](), [raspberry-pi](), [tech](), [tech-stack]() ### AI overview The article explains why the author stopped using several Raspberry Pi projects, including Plex, Pi-hole, and OpenVPN. It describes switching from Plex to Jellyfin for media and music, from Pi-hole to Brave's built-in ad blocker, and from OpenVPN to WireGuard because these alternatives better fit the author's needs. ### Source excerpt I've tested and written about countless Raspberry Pi projects on RaspberryTips, and I usually focus on what makes them worth using. But over the years, I've also changed my mind about a few projects I once used regularly. Popular services like Plex, Pi-Hole, OpenVPN, MotionEye and Samba are no longer part of my tech stack.... ## The 9 best tools for your early-stage startup tech stack in 2026 DevFeed: [The 9 best tools for your early-stage startup tech stack in 2026]() Original publisher: [Read original article]() Author: Alan McGlinchey Published: 2026-08-04T08:00:51Z Content type: article Language: en Sources: [The Intercom Blog]() Topics: [Software](), [Artificial Intelligence](), [migration](), [Claude](), [systems](), [Claude Code]() Tags: [ai](), [ai-tools](), [aws](), [best-practices](), [claude-code](), [code](), [customer-engagement](), [fin](), [growth](), [how-to](), [hubspot](), [integrations](), [migration](), [partner](), [pricing](), [startup](), [startup-advice](), [startups](), [stripe](), [tech](), [tech-stack](), [technology-stack](), [tools]() ### AI overview A guide to choosing a foundational technology stack for early-stage startups, emphasizing scalable, AI-powered tools, manageable costs, integrations, and problem-focused selection. ### Source excerpt Learn how to create a foundational tech stack for your high growth and early-stage startup - starting with these top tools. ## When is the right time to adopt an IDP? DevFeed: [When is the right time to adopt an IDP?]() Original publisher: [Read original article]() Author: Trevor Garcia Published: 2026-07-30T10:13:18Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Platform Engineering](), [Developer experience](), [DevOps](), [sdlc](), [Product Management](), [Tooling]() Tags: [article](), [best-practices](), [developer](), [developer-experience](), [developer-portal](), [devops](), [engineering](), [idp](), [internal-developer-portal](), [management](), [organizational](), [platform](), [platform-engineering](), [sdlc](), [software-development](), [tech-stack](), [tooling](), [tools]() ### AI overview This article explains when organizations should consider adopting an internal developer portal (IDP). It identifies scaling challenges such as operational overhead, cognitive overload, duplicated tools, unclear ownership, and inconsistent tooling. It also describes how DevOps, platform engineering, and product management practices can support an IDP that improves developer experience, standardizes tooling, and consolidates organizational knowledge. ### Source excerpt Organizations have to consider a lot of details before adopting an IDP, and it can be hard to know when is the right time. ## You Don't Need to Build It to Design It DevFeed: [You Don't Need to Build It to Design It]() Original publisher: [Read original article]() Author: Humayun Tanwar Published: 2026-07-06T11:05:34Z Content type: tutorial Language: en Sources: [Mindorks - Medium]() Topics: [systems](), [data-architecture](), [Latency](), [Requirements]() Tags: [business](), [code](), [compliance](), [data-architecture](), [design](), [latency](), [machine-learning](), [patterns](), [requirements](), [software-engineering](), [systems](), [tech-stack](), [technology]() ### AI overview This article explains why solutions engineers can contribute meaningfully to system design without writing the implementation. It connects integration scoping, data ownership, real-time communication choices, and failure handling to core design concepts, then presents five questions about scale, constraints, dependencies, failure tolerance, and success criteria. ### Source excerpt System design is one of those topics that feels like it belongs exclusively to engineers who write the code. The diagrams, the architecture reviews, the database choices , it all looks like backend territory from the outside. You're Already Doing This Solutions engineers sit at an interesting intersection. You're deep enough in the technical conversation to understand how systems connect, and close enough to the customer to understand what they actually need from those systems. That combination gives you a view that's genuinely useful in design conversations, and one that's worth developing deliberately. When you scope an integration and map which system owns which data, that's data architecture. When you recommend a webhook approach over polling because the customer needs real-time updates, that's a latency and reliability trade-off. When you ask a customer how they handle failures before a build starts, that's systems thinking. The formal vocabulary of system design is mostly a structured way of describing what you're already doing in the field. Building that vocabulary, and understanding the patterns underneath it, makes it easier to contribute in technical conversations, ask the right questions earlier, and connect your field experience to the broader design decisions being made around you. The Five Questions That Structure Any Design Good design conversations don't start with a diagram. They start with these. Scale. What volume are you designing for, not today but at the ceiling that changes the architecture? A thousand requests a day is a different system from a thousand per second. That number changes your database choice, whether you need a queue, and how retries need to behave. Constraints. What's already fixed? Existing tech stack, compliance requirements, vendor contracts. Every real system gets built inside constraints. Name them before drawing anything. Dependencies. What does this system talk to, and what talks to it? Systems that look simple in a conv ## Tech Stack I used to build my coding platform (algomaster.io) DevFeed: [Tech Stack I used to build my coding platform (algomaster.io)]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-03-22T05:01:59Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [Development](), [Next.js](), [React](), [TypeScript](), [Supabase](), [web applications](), [stripe](), [OpenAI](), [Vercel](), [Content Management System](), [Authentication](), [Serverless]() Tags: [authentication](), [browser](), [cms](), [coding](), [frontend](), [full-stack](), [next-js](), [open-source](), [openai](), [payments](), [react](), [tech-stack]() ### AI overview The author explains the technology stack used to build AlgoMaster.io, an interactive software engineering interview preparation platform. The platform uses Next.js with React and TypeScript, Vercel, Supabase, Payload CMS, Stripe, and AI-related services including OpenAI, Whisper, and pgVector. The article also describes the platform's architecture and the author's rationale for choosing Next.js. ### Source excerpt In September 2024, I started building AlgoMaster.io from scratch after quitting my job at Amazon. ## Wise Tech Stack (2025 update) DevFeed: [Wise Tech Stack (2025 update)]() Original publisher: [Read original article]() Author: Milon James Published: 2025-02-12T13:34:08Z Content type: article Language: en Sources: [Wise Engineering - Medium]() Topics: [Development](), [Mobile](), [Web](), [Tuist](), [Storybook](), [Testing](), [build performance]() Tags: [build-times](), [caching](), [data](), [engineering](), [mobile](), [next-js](), [platform](), [storybook](), [swift](), [swift-package-manager](), [tech](), [tech-stack](), [testing](), [tuist](), [update](), [web](), [xcode](), [xcodegen]() ### AI overview Wise's 2025 technology update describes its web, iOS, and Android engineering stack, including Next.js-based web applications, Storybook visual testing, migration from Xcodegen to Tuist, adoption of Swift Package Manager, and Android development across a large Gradle repository. ### Source excerpt Wise Engineering As of the financial year 2025, Wise supports 15.6 million active customers, moving approximately GBP 36 billion across borders each quarter. Approximately 65% of our transfers arrive instantly, and our Wise Platform facilitates payments for banks, financial institutions and enterprises globally. This success is driven by our technology-first approach, robust architecture, and dedicated engineering teams. Photo by Randy Fath on UnsplashHow we work at Wise Wise has more than 850 engineers working across key global locations, organised into independent squads and tribes. These teams are empowered to innovate and make decisions independently, fostering transparency, trust, and collaboration. This article follows our Tech Stack 2022 to cover the most recent improvements in Wise's tech stack that enable us to achieve our mission of money without borders -- instant, convenient, transparent and eventually free. Moving money with WiseOur web and mobile applications Our web applications are built using CRAB (a Wise-specific abstraction on top of the popular Next.js framework) and comprises of 40 distinct apps, each handling specific product functions making deployments safer and more manageable. One of the biggest changes has been in our testing methodology. We've adopted Storybook for visualising individual React components during development. Storybook pairs really well with Chromatic which captures snapshots after each change and can highlight the visual differences in the component. These snapshots are very effective for catching visual regressions during code changes which helps us prevent bugs from reaching our customers. Wise mobile app: faster, smarter, and more efficient Our iOS engineers have upgraded our infrastructure by migrating 250+ Xcode modules from Xcodegen to Tuist and switching from Cocoapods to Swift Package Manager (SPM), unlocking improvements in caching for builds. The team also improved flexibility, reducing zero-change build times from 2 ## React Tech Stack \[2025\] DevFeed: [React Tech Stack \[2025\]]() Original publisher: [Read original article]() Author: Robin Wieruch Published: 2024-12-09T05:50:46Z Content type: tutorial Language: en Sources: [Robin Wieruch]() Topics: [React](), [Next.js](), [Astro](), [Web Development](), [Software as a service]() Tags: [2025](), [astro](), [development](), [next-js](), [react](), [react-tech-stack-2025](), [saas](), [tech-stack]() ### AI overview A 2025 guide to a React tech stack for full-stack applications and SaaS products. It recommends Next.js as the main React framework, with Astro as an optional choice for a separate landing page, and discusses React Server Components and Server Functions. ### Source excerpt Popular React Tech Stack for Full-Stack Applications in 2025 to create your product (i.e. SaaS) ... ## Choosing a technology stack for a full-stack to-do list side project DevFeed: [Choosing a technology stack for a full-stack to-do list side project]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2024-11-06T00:00:00Z Content type: article Language: en Sources: [Jeroen Mols]() Topics: [Learning](), [Go Language](), [Back end](), [Ruby](), [Ruby on Rails](), [JavaScript]() Tags: [backend](), [blogs](), [full-stack](), [go](), [golang](), [javascript](), [learning](), [playwright](), [ruby-on-rails](), [side-project](), [svelte](), [tech-stack](), [typescript]() ### AI overview The article examines technology choices for a full-stack to-do list side project. It compares NodeJS, Ruby on Rails, and Go for the backend, and explains why the author chose Go after considering asynchronous JavaScript, Rails' batteries-included approach, and Go's static typing, concurrency, compilation speed, and performance. ### Source excerpt One of my main drivers for this side project was to make all technology choices myself. To do that effectively, I would have to consider the pros and cons of different options and frankly learn many new things. ## Building a faster, smarter, Chromebook experience with the best of Google technologies DevFeed: [Building a faster, smarter, Chromebook experience with the best of Google technologies]() Original publisher: [Read original article]() Author: Chromium Blog (noreply@blogger.com) Published: 2024-06-12T18:55:00Z Content type: article Language: en Sources: [Chromium Blog]() Topics: [Google AI](), [Android](), [Linux](), [Kernel](), [Frameworks](), [Google]() Tags: [ai](), [android](), [chromebook](), [developers](), [devices](), [gemini](), [google](), [google-ai](), [innovation](), [kernel](), [linux](), [none](), [security](), [software](), [tech-stack](), [updates]() ### AI overview ChromeOS plans to incorporate substantial portions of the Android stack, including the Android Linux kernel and Android frameworks, to deliver Google AI features and other innovations faster. The change is intended to simplify engineering and improve interoperability among Chromebooks, phones, and accessories while preserving ChromeOS security, user experience, and management capabilities. ### Source excerpt ChromeOS will soon be developed on large portions of the Android stack to bring Google AI, innovations, and features faster to users. Over the last 13 years, we've evolved ChromeOS to deliver a secure, fast, and feature-rich Chromebook experience for millions of students and teachers, families, gamers, and businesses all over the world. With our recent announcements around new features powered by Google AI and Gemini, Chromebooks now give us the opportunity to put powerful tools in the hands of more people to help with everyday tasks. To continue rolling out new Google AI features to users at a faster and even larger scale, we'll be embracing portions of the Android stack, like the Android Linux kernel and Android frameworks, as part of the foundation of ChromeOS. We already have a strong history of collaboration, with Android apps available on ChromeOS and the start of unifying our Bluetooth stacks as of ChromeOS 122. Bringing the Android-based tech stack into ChromeOS will allow us to accelerate the pace of AI innovation at the core of ChromeOS, simplify engineering efforts, and help different devices like phones and accessories work better together with Chromebooks. At the same time, we will continue to deliver the unmatched security, consistent look and feel, and extensive management capabilities that ChromeOS users, enterprises, and schools love. These improvements in the tech stack are starting now but won't be ready for consumers for quite some time. When they are, we'll provide a seamless transition to the updated experience. In the meantime, we continue to be extremely excited about our continued progress on ChromeOS without any change to our regular software updates and new innovations. Chromebooks will continue to deliver a great experience for our millions of customers, users, developers and partners worldwide. We've never been more excited about the future of ChromeOS. Posted by Prajakta Gudadhe, Senior Director, Engineering, ChromeOS & Alexander Kusche ## How Realtor.com Achieved Technological and Cultural Transformation with GraphQL DevFeed: [How Realtor.com Achieved Technological and Cultural Transformation with GraphQL]() Original publisher: [Read original article]() Author: Ishwari Lokare Published: 2024-04-23T16:14:56Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [API](), [Architecture & Design](), [Microservices]() Tags: [api](), [apollo-federation](), [events](), [graphql](), [microservices](), [resiliency](), [tech-stack]() ### AI overview Realtor.com's GraphQL adoption journey focused on simplifying its technology stack and unifying APIs with GraphQL and Apollo Federation. The article describes the technical, organizational, and communication practices used to support the transition and scale the platform. ### Source excerpt Realtor.com is a trusted real estate listing platform that connects buyers and realtors for a seamless experience when renting, buying, or selling properties. At GraphQL Summit 2023, Suzy Julius and Cabe Waldrop -- SVP of Product and Engineering and Principal Engineer at Realtor.com -- discussed the company's GraphQL journey to simplify its tech stack and scale without compromising performance. ## Alaska Airlines reaches new heights with the help of variables DevFeed: [Alaska Airlines reaches new heights with the help of variables]() Original publisher: [Read original article]() Author: Caitlin Lee Published: 2024-04-16T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [User interface design](), [Accessibility](), [Sketch](), [Digital signage]() Tags: [airline](), [browser](), [collaboration](), [components](), [design](), [features](), [figma](), [mobile](), [prototyping](), [real-time](), [standards](), [tech-stack](), [tools]() ### AI overview Alaska Airlines uses Figma variables and its Auro design system to maintain consistent experiences across its website, mobile interfaces, digital signage, and kiosks. The change saved designers an average of 11 hours per week and improved documentation, collaboration, and consistency between design and engineering. ### Source excerpt By leveraging advanced design system features like variables, Alaska Airlines takes the experience of air travel to a new level. ## How Gradual Technology-Stack Complexity Can Harm Startup Productivity DevFeed: [How Gradual Technology-Stack Complexity Can Harm Startup Productivity]() Original publisher: [Read original article]() Author: Marcus Kohlberg Published: 2023-09-12T00:00:00Z Content type: opinion Language: en Sources: [Encore Updates]() Topics: [Development](), [Library](), [Framework](), [web applications]() Tags: [complexity](), [development](), [framework](), [libraries](), [productivity](), [services](), [startup](), [tech-stack]() ### AI overview This commentary uses the boiling-frog metaphor to examine how incremental additions of features, libraries, services, and dependencies can turn a simple startup technology stack into a complex system. It argues that this complexity can reduce team productivity, slow changes, increase production risk, and create significant business costs. ### Source excerpt How to Cope When Your Tech Stack is a Hot Mess of Complexity ## Avoiding The Classic Mid-Level Developer Trap DevFeed: [Avoiding The Classic Mid-Level Developer Trap]() Original publisher: [Read original article]() Author: Richard Donovan Published: 2023-08-19T09:12:22Z Content type: opinion Language: en Sources: [The Modern Software Developer]() Topics: [Development](), [Job](), [Software Engineering](), [Learning]() Tags: [career](), [developer](), [job-titles](), [junior](), [learning](), [software-developer](), [tech-stack]() ### AI overview The article examines the ambiguity of the mid-level developer role and describes a "Mid-Level Developer Trap" that can lead to lost focus, demotivation, stalled learning, and job dissatisfaction. It characterizes mid-level developers as having experience with their tech stack, partial self-sufficiency, awareness of their capabilities, and the ability to research problems and seek help. ### Source excerpt Welcome back to The Modern Software Developer. ## How Figma draws inspiration from the gaming world DevFeed: [How Figma draws inspiration from the gaming world]() Original publisher: [Read original article]() Author: Alice Ching Published: 2023-05-03T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Game engine](), [systems](), [User Experience](), [Web]() Tags: [engineering](), [figma](), [gaming](), [graphics](), [real-time](), [tech-stack]() ### AI overview Figma Engineering Manager Alice Ching explains how Figma and FigJam draw inspiration from video game engines. The article compares their collaborative, creative interfaces and technical architecture with game-engine systems such as graphics rendering, controls, multiplayer collaboration, physics, and animation. ### Source excerpt Engineering Manager Alice Ching discusses the parallels between developing gaming interfaces and building Figma and FigJam, and why our tech stack is more similar to a game engine's tech stack than a web stack. ## Promotions.fyi launches company-specific career guides for software engineers DevFeed: [Promotions.fyi launches company-specific career guides for software engineers]() Original publisher: [Read original article]() Author: Rahul Pandey Published: 2023-02-24T15:49:09Z Content type: release Language: en Sources: [Alex Chiou]() Topics: [Web app](), [TypeScript](), [Next.js](), [Tailwind CSS](), [Cloud](), [Firebase](), [Firestore](), [Retool](), [stripe]() Tags: [developer](), [firebase](), [firestore](), [low-code](), [next-js](), [tech](), [tech-stack]() ### AI overview The article announces promotions.fyi, a service offering company-specific guides on performance reviews and promotions for software engineers. It also outlines Taro's technology stack, including TypeScript, Next.js, Kotlin, Swift, Firebase, Firestore, Retool, Stripe, and Vercel, and explains the team's preference for developer speed over compute efficiency. ### Source excerpt Plus, the tech stack behind Taro ## Wise Tech Stack (2022 edition) DevFeed: [Wise Tech Stack (2022 edition)]() Original publisher: [Read original article]() Author: pavel dionisev Published: 2022-12-07T08:04:11Z Content type: article Language: en Sources: [Wise Engineering - Medium]() Topics: [Back end](), [Microservices](), [Java](), [Spring Boot](), [Front end](), [Mobile](), [API](), [Kotlin](), [Next.js](), [Development]() Tags: [backend](), [frontend](), [java](), [jvm](), [kotlin](), [microservices](), [mobile](), [next-js](), [platform](), [spring-boot](), [tech](), [tech-stack]() ### AI overview Wise describes its 2022 technology stack, including microservices across backend, frontend, and mobile applications. Most backend services run on the JVM using Spring Boot and Java or Kotlin, while customer-facing applications use a framework built on Next.js. ### Source excerpt Intro Two years passed since our last tech stack post. TransferWise became Wise and Wise became a public company. We've opened more offices in more locations and remote work was never as common. We faced more regulatory scrutiny, went through multiple audits, and proved to the world and our customers that we are trustworthy, and still laser focused on helping money move without borders. We kept going, kept opening new routes and launching new products, all in the new paradigm. Most importantly, we did it without slowing down, introducing extra complexity or bureaucracy to our processes. In this blog post we'll share how we achieved it. Photo by Sean Stratton on UnsplashProduct: Backend Microservices, Frontend, mobile and API Our product is at the core of what we do and it roughly consists of customer-facing frontend and mobile applications, and complex backend machinery that works under the hood to support our mission: money without borders -- instant, convenient, transparent and eventually free. It is not a small task. Luckily, we have more than 700 engineers forming approximately 100 teams that are very good at solving the problems that arise. Our stack follows that structure. We use microservices in backend, frontend and our mobile apps are also modularised to a small chunks owned by specific teams. Most of our over 600 backend services are running on JVM, use Spring Boot and written in Java or, sometimes, Kotlin. Early on we decided to encourage anyone to contribute to any service we have. To achieve that we needed to reduce the entry barrier, so common language as a foundation worked really well. Sticking to industry standard allows us to tap into a wide and diverse pool of engineers that can join us on our mission. Common, compatible runtime also enabled us to work on standardisation, and building tools and libraries that support each engineer: standardised observability, security, service-to-service communications and more. We abstracted a lot of underlying in ## How We Built Shopify Party DevFeed: [How We Built Shopify Party]() Original publisher: [Read original article]() Author: Daniel Beauchamp Published: 2022-06-14T14:00:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [Unity](), [WebGL](), [3D](), [browser](), [Web](), [Three.js]() Tags: [3d](), [browser](), [games](), [shopify](), [tech-stack](), [unity](), [web](), [webgl]() ### AI overview This article explains how Shopify Party, a browser-based internal tool for remote social interaction, was designed and built. It covers the project's 3D avatar-based spaces, non-prescriptive gameplay, easy joining and leaving, simple controls, and browser delivery using Unity WebGL. ### Source excerpt Shopify Party is a browser-based internal tool that we built to make our virtual hangouts more fun. With Shopify's move to remote, we wanted to explore how to give people a break from video fatigue and create a new space designed for social interaction. Here's how we built it. ## What's new in Svelte: May 2022 DevFeed: [What's new in Svelte: May 2022]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2022-05-01T00:00:00Z Content type: news Language: en Sources: [Svelte blog]() Topics: [Svelte](), [JavaScript](), [vs-code](), [Netlify](), [Vercel](), [Content Management System]() Tags: [docs](), [javascript](), [netlify](), [news](), [svelte](), [tech-stack](), [tutorial](), [updates](), [vercel](), [vs-code]() ### AI overview A May 2022 Svelte update covering new Svelte and SvelteKit features, language-tool improvements, breaking changes, deployment support for Netlify Edge Functions and the Vercel build output API, and community showcase projects. ### Source excerpt With yesterday's Svelte Summit behind us, we've got a lot of news to share! Check out all of the recordings on the Svelte Society YouTube Channel and the rest of this month's updates below... What's new in Svelte The element lets you render an element of a dynamically specified type. This is useful, for example, when rendering rich text content from a CMS. Check out the docs or the tutorial for more info (3.47.0)! Language Tools updates svelte:element and sveltekit:reload are now supported Invalid Svelte import paths will now be automatically detected - see PR for getting back the old behavior (#1448) source.sortImports lets you sort imports without deleting unused imports (#1338) Hovering over HTML attributes will now show HTML hover info instead of the TS hover info - resulting in much more useful information (#1447) In VS Code, you can now wrap existing blocks of code in control flow tags using the Insert Snippet command (#1373) What's new in SvelteKit Files and directories can now be named __tests__ and __test__ in the routes directory (#4438) Netlify Edge Functions (#4657) and the Vercel build output API (#4663) are now supported Custom load dependencies, array of strings representing URLs the page depends on, are now available when loading routes (Docs, #4536) Breaking Changes Validators are now called "matchers" (Docs, #4358) __layout.reset has been replaced by named layouts - which have much configurability for shared layout elements (Docs, #4388) Prerendering is now skipped for rel="external" links (#4545) maxage is now cache in LoadOutput (#4690) Community ShowcaseApps & Sites built with Svelte polySpectra AR lets you prototype faster 3D Printing with seamless AR file handoffs (video demo) Pixel Art Together is a free multiplayer pixel art editor powered by Liveblocks Tooling Manager lets you compare your JavaScript tech stack against industry standard boilerplates Easy Portfolio generates a portfolio based on your GitHub profile FLOAT is ## Did I Break You? Reverse Dependency Verification DevFeed: [Did I Break You? Reverse Dependency Verification]() Original publisher: [Read original article]() Published: 2021-05-25T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Reverse Dependencies](), [Back end](), [Tooling](), [Finagle](), [Microservice](), [Rails](), [Ruby](), [Architecture & Design](), [Documentation](), [Data Science](), [Mobile](), [PWA]() Tags: [analysis](), [automation](), [backend](), [collaboration](), [configuration](), [dependency](), [development](), [engineering](), [framework](), [jvm](), [microservices](), [rails](), [reverse-dependencies](), [ruby](), [tech-stack](), [testing](), [tooling](), [verification](), [web-development]() ### AI overview SoundCloud describes how its evolving technology stack and team autonomy created fragmentation across languages, frameworks, processes, and documentation. It presents Golden Paths as opinionated, reusable recommendations that simplify development while preserving flexibility, including a JVM backend path built around Finagle and supporting tooling. ### Source excerpt SoundCloud was founded 13 years ago, and throughout its history, the company and much of its tech stack has changed. We started with a... ## Ask a Developer: Your Questions Answered DevFeed: [Ask a Developer: Your Questions Answered]() Original publisher: [Read original article]() Author: Ankia Wolf Published: 2020-03-20T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Programming](), [Job](), [Frameworks](), [Go Language](), [JavaScript](), [PHP](), [Angular](), [React](), [Python](), [Vue.js](), [R](), [Open Source]() Tags: [angular](), [backend](), [developer](), [engineering-culture](), [frameworks](), [full-stack](), [github](), [go](), [hackathons](), [interviewing](), [javascript](), [kotlin](), [open-source](), [php](), [python](), [q-a](), [react](), [requirements](), [tech](), [tech-stack](), [vue]() ### AI overview A trivago developer Q&A covers opportunities for React developers, interview expectations, ways for newcomers to contribute, full-stack requirements, and the company's technology stack. It identifies Kotlin, Go, and PHP for backend work; JavaScript for frontend; Python and R for data science; and Angular, React, Vue, and Melody as JavaScript frameworks. ### Source excerpt We recently hosted a Q&A on our trivago tech Twitter and Life at trivago Instagram page,... ## Make Great Decisions Quickly with TOMASP DevFeed: [Make Great Decisions Quickly with TOMASP]() Original publisher: [Read original article]() Author: Djoume Salvetti Published: 2019-10-22T19:47:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Architecture & Design](), [Flutter](), [Google]() Tags: [architecture](), [blog-post](), [flutter](), [google](), [leadership](), [opinion](), [software-architecture](), [tech-stack]() ### AI overview This developer article introduces TOMASP, a simple framework for making complex, high-impact decisions quickly and consistently. It illustrates the framework through a technical lead's decision about whether to rewrite a mobile app using Flutter, while considering architecture, team experience, leadership support, and project risks. ### Source excerpt We're naturally bad at making complex decisions. I'll show you how you can consistently make great decisions using a simple framework called TOMASP. ## E-Commerce at Scale: Inside Shopify's Tech Stack - Stackshare.io DevFeed: [E-Commerce at Scale: Inside Shopify's Tech Stack - Stackshare.io]() Original publisher: [Read original article]() Author: Kir Shatrov Published: 2018-08-08T15:30:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [Production Engineering](), [Rails](), [Scalability](), [Ruby](), [Monitoring](), [Architecture & Design](), [incident]() Tags: [incident](), [infrastructure](), [monitoring](), [production](), [production-engineering](), [ruby](), [scalability](), [shopify](), [tech-stack]() ### AI overview The article examines how Shopify operates a large-scale, multi-channel commerce platform. It describes the Production Engineering department, shared responsibility for monitoring and incident response, scalability practices for unpredictable flash-sale traffic, and Shopify's long-lived Ruby on Rails codebase. ### Source excerpt 9 minute read Before 2015, we had an Operations and Performance team. Around this time, we decided to create the Production Engineering department and merge the teams. The department is responsible for building and maintaining common infrastructure that allows the rest of product development teams to run their code. Both Production Engineering and all the product development teams share responsibility for the ongoing operation of our end user applications. This means all technical roles share monitoring and incident response, with escalation happening laterally to bring in any skill set required to restore service in case of problems.