url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://dev.to/_402ccbd6e5cb02871506/super-fast-markdown-linting-for-go-developers-meet-gomarklint-3ikd#key-features | Super Fast Markdown Linting for Go Developers: Meet gomarklint - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Kazu Posted on Jan 13 Super Fast Markdown Linting for Go Developers: Meet gomarklint # go # performance # showdev # markdown The "Why" (The Motivation) Documentation is the heart of any project, but keeping it consistent is a nightmare. While working on various Go projects, I realized a few things about my workflow: Context Switching Costs: I love Go's speed and simplicity. Having to install Node.js or Ruby just to run a Markdown linter in a Go project felt "heavy." CI Fatigue: In large repositories, documentation checks shouldn't take seconds—they should take milliseconds. Every second saved in CI is a win for developer experience. The "Broken Link" Problem: There’s nothing more embarrassing than shipping a README with dead links. I needed a tool that catches these issues instantly. I couldn't find a tool that was Go-native, ultra-fast, and zero-config by default, so I decided to build one. The goal for gomarklint was simple: Make Markdown linting so fast and easy that you never have an excuse to skip it. Speed Performance When I say "fast," I mean Go-fast. In many CI/CD pipelines, linting documentation is often the bottleneck that adds unnecessary seconds (or even minutes) to every PR. gomarklint changes that. By leveraging Go's concurrency and efficient string handling, it delivers near-instant feedback. The Benchmark: I tested gomarklint against a large documentation set: Total Files: 180 Markdown files Total Volume: 100,000+ lines of text Execution Time: < 50ms To put that in perspective, 50ms is literally faster than the blink of a human eye. You can run this on every single file save without ever noticing a stutter in your workflow. By removing the overhead of a virtual machine or a heavy runtime, gomarklint ensures that your documentation quality stays high without sacrificing your velocity. Key Features gomarklint doesn't just check syntax; it enforces a logical structure for your documentation. Here are the core rules it handles out of the box: Heading Hierarchy Enforcement : Ever seen a document jump from an H2 directly to an H4? It breaks the visual flow and accessibility. gomarklint ensures your heading levels follow a strict, logical sequence. Duplicate Heading Detection : Identical headings in the same file can break anchor links (e.g., #features vs #features-1). We catch these early so your internal navigation never breaks. Broken Link Checker (Internal & External) : This is my favorite. It scans your Markdown for links and validates them. No more 404s for your users when they click on a "Getting Started" guide or an external API reference. Configuration via JSON : While it works great with zero config, you can easily tweak rules or ignore specific paths using a simple .gomarklint.json file. Quick Start # install (choose one) go install github.com/shinagawa-web/gomarklint@latest # or clone and build manually git clone https://github.com/shinagawa-web/gomarklint cd gomarklint make build # or: go build ./cmd/gomarklint Enter fullscreen mode Exit fullscreen mode 1) Initialize config (optional but recommended) gomarklint init Enter fullscreen mode Exit fullscreen mode This creates .gomarklint.json with sensible defaults: { "include": ["."], "ignore": ["node_modules", "vendor"], "minHeadingLevel": 2, "enableHeadingLevelCheck": true, "enableDuplicateHeadingCheck": true, "enableLinkCheck": false, "skipLinkPatterns": [], "outputFormat": "text" } Enter fullscreen mode Exit fullscreen mode You can edit it anytime — CLI flags override config values. 2) Run it # lint current directory recursively gomarklint ./... # lint specific targets gomarklint docs README.md internal/handbook Enter fullscreen mode Exit fullscreen mode What's Next? (Roadmap) gomarklint is already stable and fast, but I have a clear vision for where it’s headed. I’m actively working on expanding its rule set to cover even more edge cases and best practices. Here’s what you can expect in the coming updates: max-line-length Enforcement : To keep your Markdown source files readable in any editor or GitHub's UI. Image Alt-Text Validation : Improving accessibility by ensuring every image has a descriptive alt attribute. Custom Rules via JSON : Giving you the power to define your own project-specific rules in .gomarklint.json. Auto-fixing (The Dream) : While currently focused on linting, I’m exploring ways to automatically fix simple issues like heading level skips. We are Open for Contributions! If you have a rule in mind that would make your documentation better, or if you find a bug, please open an Issue or a Pull Request on GitHub. I’d love to build the future of this tool together with the community. Wrap Up Building gomarklint has been an incredible journey into the world of Go performance and static analysis. It started as a small tool for my own workflow, but I realized that many other developers are likely facing the same "slow linting" frustration. If you're looking for a way to keep your documentation spotless without adding bloat to your CI/CD, I’d be honored if you gave gomarklint a try. Check it out on GitHub : shinagawa-web/gomarklint Give it a ⭐: If you find the project useful, a Star would mean the world to me and helps others discover the tool! I’m really curious to hear from you: What’s the most annoying thing you’ve encountered with Markdown formatting? Let’s chat in the comments below! Happy hacking! 🚀 Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Kazu Follow Joined Aug 9, 2025 More from Kazu Building a Culture of Documentation Quality in CI/CD # markdown # cicd # documentation # opensource Inside gomarklint: Architecture, Rule Engine, and How to Extend It # programming # go # markdown Inside gomarklint: Building a High-Performance Markdown Linter in Go # go # markdown # opensource 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:33 |
https://future.forem.com/t/arvr#main-content | Arvr - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close # arvr Follow Hide Augmented and Virtual Reality in the context of Web3 and the metaverse. Create Post Older #arvr posts 1 2 3 4 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu iPhone 17 Rumors: Everything We Know About Apples Next-Gen Flagship Bama Charan Chhandogi Bama Charan Chhandogi Bama Charan Chhandogi Follow Dec 13 '25 iPhone 17 Rumors: Everything We Know About Apples Next-Gen Flagship # ai # arvr # wearables Comments 1 comment 3 min read Snap Spectacles 5 - Optical Analysis of the AR HMD AR/VR News AR/VR News AR/VR News Follow Aug 12 '25 Snap Spectacles 5 - Optical Analysis of the AR HMD # arvr # wearables # manufacturing # nanotech Comments Add Comment 1 min read Meta's prototype headsets show off the future of mixed reality AR/VR News AR/VR News AR/VR News Follow Aug 12 '25 Meta's prototype headsets show off the future of mixed reality # arvr # wearables # science # manufacturing Comments Add Comment 1 min read vivo Vision mixed reality headset shown off, testers praise its comfortable design AR/VR News AR/VR News AR/VR News Follow Aug 12 '25 vivo Vision mixed reality headset shown off, testers praise its comfortable design # arvr # wearables # iot # edgecomputing Comments Add Comment 1 min read Meta's prototype headsets show off the future of mixed reality AR/VR News AR/VR News AR/VR News Follow Aug 8 '25 Meta's prototype headsets show off the future of mixed reality # arvr # wearables # science # manufacturing Comments Add Comment 1 min read Mark Zuckerberg promises you can trust him with superintelligent AI AI News AI News AI News Follow Aug 5 '25 Mark Zuckerberg promises you can trust him with superintelligent AI # ai # wearables # arvr # security Comments Add Comment 1 min read Exclusive: Even Realities waveguide supplier Greatar secures another hundred-million-yuan-level financing AR/VR News AR/VR News AR/VR News Follow Aug 5 '25 Exclusive: Even Realities waveguide supplier Greatar secures another hundred-million-yuan-level financing # arvr # manufacturing # wearables # nanotech Comments Add Comment 1 min read Gixel comes out of stealth with a new type of AR optical engine AR/VR News AR/VR News AR/VR News Follow Jul 28 '25 Gixel comes out of stealth with a new type of AR optical engine # arvr # wearables # manufacturing # science Comments Add Comment 1 min read Brilliant Labs to Launch Next-gen Smart Glasses on July 31st AR/VR News AR/VR News AR/VR News Follow Jul 28 '25 Brilliant Labs to Launch Next-gen Smart Glasses on July 31st # ai # arvr # wearables # iot Comments Add Comment 1 min read ALIBABA will announce its first AI Glasses this week: There's a version with display, and a version without AR/VR News AR/VR News AR/VR News Follow Jul 28 '25 ALIBABA will announce its first AI Glasses this week: There's a version with display, and a version without # ai # wearables # arvr # edgecomputing Comments Add Comment 1 min read Karl Guttag: Google XR Glasses Using Google's Raxium MicroLEDs While Waveguide Lab Sold to Vuzix AR/VR News AR/VR News AR/VR News Follow Jul 28 '25 Karl Guttag: Google XR Glasses Using Google's Raxium MicroLEDs While Waveguide Lab Sold to Vuzix # arvr # wearables # nanotech # manufacturing Comments Add Comment 1 min read Xiaomi AI Glasses hands-on: a promising first-gen product AR/VR News AR/VR News AR/VR News Follow Jul 22 '25 Xiaomi AI Glasses hands-on: a promising first-gen product # ai # arvr # wearables # smarthomes Comments Add Comment 1 min read CREAL raised 8.9 M USD. Here is my interview with the founder AR/VR News AR/VR News AR/VR News Follow Jul 22 '25 CREAL raised 8.9 M USD. Here is my interview with the founder # ai # arvr # wearables # iot Comments Add Comment 1 min read Netflix uses generative AI in one of its shows for first time | Netflix AI News AI News AI News Follow Jul 21 '25 Netflix uses generative AI in one of its shows for first time | Netflix # ai # science # edgecomputing # arvr Comments Add Comment 1 min read Elon Musk's AI bot adds a ridiculous anime companion with ‘NSFW' mode AI News AI News AI News Follow Jul 21 '25 Elon Musk's AI bot adds a ridiculous anime companion with ‘NSFW' mode # ai # privacy # security # arvr Comments Add Comment 1 min read Elon Musk's AI bot adds a ridiculous anime companion with ‘NSFW' mode AI News AI News AI News Follow Jul 18 '25 Elon Musk's AI bot adds a ridiculous anime companion with ‘NSFW' mode # ai # autonomy # arvr # robotics Comments Add Comment 1 min read This AI Warps Live Video in Real Time AI News AI News AI News Follow Jul 18 '25 This AI Warps Live Video in Real Time # ai # arvr # edgecomputing # science Comments Add Comment 1 min read New lightweight headset from PICO? AR/VR News AR/VR News AR/VR News Follow Jul 17 '25 New lightweight headset from PICO? # arvr # wearables # ai # edgecomputing Comments Add Comment 1 min read Could smart goggles bridge the gap between Vision Pro and Apple Glasses? AR/VR News AR/VR News AR/VR News Follow Jul 17 '25 Could smart goggles bridge the gap between Vision Pro and Apple Glasses? # arvr # wearables # iot # edgecomputing Comments Add Comment 1 min read Beyond Military, Meta is Eyeing an XR Expansion into the Medical Field AR/VR News AR/VR News AR/VR News Follow Jul 15 '25 Beyond Military, Meta is Eyeing an XR Expansion into the Medical Field # arvr # healthtech # wearables # employment Comments Add Comment 1 min read New Meta lab is dedicated to advancing audio technologies for future AR and AI glasses AR/VR News AR/VR News AR/VR News Follow Jul 14 '25 New Meta lab is dedicated to advancing audio technologies for future AR and AI glasses # science # arvr # iot # smarthomes Comments Add Comment 1 min read Apple accuses ex-engineer of stealing Vision Pro secrets AR/VR News AR/VR News AR/VR News Follow Jul 7 '25 Apple accuses ex-engineer of stealing Vision Pro secrets # arvr # security # wearables # employment Comments Add Comment 1 min read Brilliant Labs launches Halo: AI smartglasses that last all day AR/VR News AR/VR News AR/VR News Follow Aug 5 '25 Brilliant Labs launches Halo: AI smartglasses that last all day # ai # arvr # wearables # edgecomputing 3 reactions Comments Add Comment 1 min read Oculus co-founder Nate Mitchell joins AI glasses startup Sesame AR/VR News AR/VR News AR/VR News Follow Jul 2 '25 Oculus co-founder Nate Mitchell joins AI glasses startup Sesame # ai # arvr # wearables # iot Comments Add Comment 1 min read Mentra raises $8M for its open-source smartglasses OS — Should we do another AMA with them here ?!? AR/VR News AR/VR News AR/VR News Follow Jul 2 '25 Mentra raises $8M for its open-source smartglasses OS — Should we do another AMA with them here ?!? # ai # wearables # arvr # iot Comments Add Comment 1 min read loading... trending guides/resources iPhone 17 Rumors: Everything We Know About Apples Next-Gen Flagship 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:33 |
https://docs.devcycle.com/platform/feature-flags/features | Features | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Features On this page Features Features are the main elements that you want to control or experiment with in your application. They can be anything from a new UI element to a backend algorithm. info When creating a Feature in DevCycle, you will be able to choose a Feature Type which will pre-fill some options in the Feature and help kick-start your usage of the Feature. Managing All Features on the Feature List Page The Feature List Page is where all of your Features can be viewed, edited, and filtered for search. This page will show all Features within the current Project. The Features list (sorted by created date ascending) has the following columns: Column Description Creator This will show the icon of the user who created this Feature. Feature type The selected type of the Feature. Use this to organize your Features. Status The Feature's Current Status . This indicates the Feature's current position in the Development LifeCycle . Name The Feature's name. This can be changed at any time by editing the Feature. Key This is the Feature's Key. Use this key to reference the Feature in the SDKs or APIs. Environments This displays which Environments have Targeting Enabled. If targeting is enabled in multiple Environments for a Feature, you can hover over the tag to see which Environments are active. Tags Tags are customizable labels that help you categorize Features. Edit Click this to edit on the row the Feature. Use the search input to search by Name, Key, Tag, or Description. The filters can be used to filter by Creator, Status, Type, or Staleness . Each column header can be clicked to sort the column. Kanban View On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status , allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted within each column according to the selected sort option (for example, by name or last updated date) Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. info To view another Project's Features, use the Project dropdown on the top of the Dashboard. Creating a New Feature From this page, you can create a Feature Flag by clicking "Create New Feature" or the + in the top bar. A screen for deciding your Feature Type will now appear. To read more about the Feature types and their uses, read DevCycle Feature Types . After choosing a type, the information modal will appear prompting you to enter the following information: Feature Name Enter a descriptive Feature name. Feature Key This key is how the Feature and its Variables will be referenced in code. (A key will be automatically suggested based on the entered name.) Description Optionally, you may choose to provide a detailed description of the Feature. Tags Tags are customizable labels that help you categorize Features. Jira Ticket ID(s) If your team has setup the DevCycle integration for Jira , you can link Jira tickets directly to Features within DevCycle, making the Feature status easily viewable within Jira. Initial Variable Key Initial Variable Key allows you to define an initial Variable key that can differ from the new Feature key name. As you type in the Feature Name, the Feature Key and the Initial Variable Key will mimic whatever input is entered in the Feature Name field formatted in kebab case. Initial Variable Type Initial Variable Type allows you to select the type of Variable for the initial Variable created along with your Feature (Boolean, JSON, String, or Number). Creating a New Feature with a Duplicate Initial Variable Key If a duplicate Variable key belonging to an unassociated Variable is submitted when creating a new Feature, this modal will appear that will allow you to re-associate the Variable to your new Feature. If the unassociated Variable key submitted is archived, a similar modal will appear with the option to unarchive the Variable & re-associate it to the new Feature. If you wish to unarchive & re-associate, click on the toggle and click Yes, Proceed . The Feature will be created along with the newly re-associated Variable. The Variations and corresponding Variable values will be populated depending on the Feature Type selected. If you attempt to use a duplicate Variable key belonging to a Variable that's associated with an existing Feature, the dashboard will return an error. Updating a Feature on the Feature Form The Feature form uses a tabbed layout, with Overview , Manage Feature , Data & Results , and Audit Log tabs. Feature Overview Tab The Feature Overview Tab provides a high-level overview of a Feature’s configuration and recent activity. It is the default view when navigating to a Feature and is intended to help users quickly assess the current state of a Feature without reviewing each section individually. The Overview Tab displays key information from across the Feature, including the following: Last Updated - Audit Log Card DevCycle surfaces the latest Audit Log entry, summarizing the most recent changes made to the Feature. To view the full diff, click View Details. note If Approval Workflows are enabled, and there is an active Change Request; this card will display the active Change request in lieu of the Audit Log card. Feature Settings & Status This section displays the Feature Settings (e.g. name, description, type, Maintainer, tags) and the Status of a Feature. Feature settings can be changed from the Manage Feature tab, click on the arrow on the upper right corner of the box to navigate to the Settings to edit. Feature Summary Markdown Section Each Feature includes a Feature Summary Markdown section on the Overview Tab that can be used to add internal documentation. This is helpful for capturing context like rationale behind the Feature, rollout checklists, or acceptance criteria. note For security reasons, links and images are not supported in this Markdown section. The content is editable directly from the Overview Tab by users with Member-level permissions or higher , allowing teams to store relevant notes directly alongside the Feature rather than relying on external documentation tools. To make the creation and editing of a useful Feature Summary easier, you also have the option to generate a Summary via AI . Next to the edit button there is a "Generate AI Summary" button that adds the details of your Feature to a prompt and uses AI to pull out relevant details. The goal with the AI generation is to make it easier to create and keep Summaries updated, because a quality Feature Summary helps to keep your team informed of your Feature's purpose, who it's targeting and other important details that may be lost with time. Reach The Reach section displays a version of the Feature Reach graph. The chart shows the aggregated count of evaluations of ALL Variables across ALL Environments and ALL SDKS. You can filter the evaluation data for different Environments and time ranges. For more granular filtering, click on the arrow on the top right of the section. Resources To support collaboration across tools, a Resources section is available on the Overview Tab for adding external links to tools like Notion, GitHub, or Figma. You can add a link along with a title, making it easier for teammates to find supporting context without switching tools. Edits can be made by users with Member-level permissions or higher . Variables Snapshot A read-only snapshot of all Variables associated with the Feature is displayed at the bottom of the Overview Tab. It includes the Variable status indicator, name, type, description, and any applied tags. This allows users to quickly audit how a Feature is structured without navigating to the full Feature form. Manage Feature Tab The Manage Feature tab is your central workspace for configuring and managing your Feature. It includes the Variables & Variations table, Targeting, Code Examples, Status Section, and Feature Settings. To learn more about each section, explore the following resources: Variables Variations Self-Targeting Targeting Status and LifeCycle To change the Feature settings including name, key, and type, description, tags, and Maintainer, navigate to the bottom of the Manage Feature Tab to the Settings section. Features can be assigned one or more Maintainers to indicate who is responsible for the Feature in the settings panel. By default, the creator of the Feature is set as the initial Maintainer. This is useful for clarifying accountability—for example, assigning both a product manager and a technical lead makes it clear who team members should go to if they have questions about the Feature. Data & Results Tab The Data & Results Tab houses the Feature Reach graph and the Experiment Results section. To learn more about this section of the Feature Form, review our Feature Reach and Metrics documentation. Audit Log Tab The Audit Log tracks all modifications made to a Feature. DevCycle captures the DevCycle user who made the change, a time stamp, and what was modified on each Feature save. For more information, review our Audit Log documentation. Archiving a Feature Archiving is the terminal state for Features that have reached the end of their lifecycle, were never implemented in code, or have become entirely obsolete. See Status & Lifecyle for more information on how to manage Feature Lifecycles in DevCycle. Upon Archive, the Feature is put into a read-only mode, and its Audit Logs are accessible and available for teams to review. All Variables will be archived along with the Feature but can be re-used and associated to other Features. All Variables in this Feature will begin to serve Default values in code. This action cannot be undone. To archive a Feature, either navigate to the Status section OR scroll to the very bottom of the Manage Feature tab and click the Archive button. You will be prompted to confirm archival of the Feature. Deleting a Feature We recommended that Feature deletion only be used for mistakes, as deletion permanently removes the Feature, its Variables and its Audit Log from DevCycle. This action cannot be undone. To delete, a Feature scroll to the very bottom of the Manage Feature tab and click the red Delete button. You will be prompted to confirm deletion. Edit this page Last updated on Jan 9, 2026 Previous Feature Types Next Variables Managing All Features on the Feature List Page Kanban View Creating a New Feature Creating a New Feature with a Duplicate Initial Variable Key Updating a Feature on the Feature Form Feature Overview Tab Manage Feature Tab Data & Results Tab Audit Log Tab Archiving a Feature Deleting a Feature DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:33 |
https://popcorn.forem.com/wajihaseo/shoujo-a-celebration-of-emotion-growth-and-storytelling-in-japanese-manga-and-anime-40ie#comments | Shoujo: A Celebration of Emotion, Growth, and Storytelling in Japanese Manga and Anime - Popcorn Movies and TV Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Popcorn Movies and TV Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse wajihaseo Posted on Dec 28, 2025 Shoujo: A Celebration of Emotion, Growth, and Storytelling in Japanese Manga and Anime # genrestudies # filmhistory # animation # analysis **[shoujo]( )**is one of the most influential and beloved genres in Japanese manga and anime. The term “shoujo” literally means “young girl” in Japanese, and it refers to works primarily created for a female audience, usually ranging from pre-teens to young adults. However, shoujo is far more than a demographic label. It is a storytelling tradition that emphasizes emotions, relationships, personal growth, and the inner worlds of its characters, making it appealing to audiences of all genders and ages around the world. Origins and Evolution of Shoujo Shoujo manga began to take shape in the early 20th century, with stories that were simple, moral-focused, and often educational. Early works revolved around family life, school experiences, and traditional values. As Japan’s publishing industry expanded after World War II, shoujo manga gained popularity, and creators began experimenting with new themes and artistic styles. A major turning point came in the 1970s with the rise of the “Year 24 Group” (artists born around Showa year 24, or 1949). These pioneering female mangaka revolutionized shoujo by introducing complex narratives, psychological depth, and innovative panel layouts. Romance became more emotionally layered, and themes such as identity, loss, gender roles, and even science fiction were explored. This era laid the foundation for modern shoujo as a rich and diverse genre. Core Themes of Shoujo At the heart of shoujo lies emotional storytelling. While romance is often central, it is not the only focus. Common themes include: Love and Relationships: Shoujo explores first love, unspoken feelings, heartbreak, and emotional vulnerability. Relationships are portrayed with sensitivity, focusing on emotional connection rather than physical action. Personal Growth: Protagonists often begin as ordinary or insecure individuals and gradually mature through their experiences. Self-discovery and confidence-building are key narrative elements. Friendship and Community: Strong bonds between friends, classmates, and even rivals play a crucial role in character development. Dreams and Aspirations: Many shoujo stories encourage following one’s dreams, whether related to career goals, creative passions, or personal independence. These themes resonate deeply because they reflect universal human emotions and challenges, making shoujo relatable beyond its intended demographic. Artistic Style and Visual Identity One of the most recognizable aspects of shoujo is its distinct art style. Traditionally, shoujo manga features expressive characters with large, detailed eyes that convey emotion. Flowing hair, delicate facial expressions, and decorative backgrounds filled with flowers, sparkles, and symbolic imagery are commonly used to enhance mood. Panel layouts in shoujo are often more fluid and less rigid than in action-oriented genres. Artists use creative framing, overlapping panels, and visual metaphors to reflect a character’s emotional state. This artistic freedom allows shoujo to feel poetic and immersive, drawing readers into the characters’ inner worlds. Popular Subgenres within Shoujo Shoujo is not a single, uniform category. It includes a wide range of subgenres that cater to different tastes: Romantic Shoujo: Focuses on love stories, often set in schools or everyday life. Examples include heartfelt tales of slow-burn romance and emotional confession. Magical Girl (Mahou Shoujo): Combines fantasy with themes of friendship and responsibility. Iconic series like Sailor Moon popularized this subgenre globally. Historical and Fantasy Shoujo: Set in imaginative or historical worlds, blending romance with adventure and drama. Slice of Life: Centers on daily experiences, emotional realism, and character relationships. Psychological and Dark Shoujo: Explores heavier themes such as trauma, obsession, or moral conflict, showing the genre’s narrative depth. This diversity ensures that shoujo continues to evolve and remain relevant. Shoujo in Anime and Global Influence Shoujo manga has had a strong presence in anime adaptations, helping the genre reach international audiences. Series like Fruits Basket, Nana, Ouran High School Host Club, and Cardcaptor Sakura introduced global viewers to shoujo’s emotional storytelling and artistic charm. Over time, shoujo has influenced other genres as well. Elements such as emotional introspection, character-driven narratives, and aesthetic symbolism can now be seen across anime and manga demographics, including shounen and seinen works. Modern Shoujo and Changing Perspectives In recent years, shoujo has continued to adapt to changing social norms and audience expectations. Contemporary shoujo stories often feature stronger, more independent protagonists who challenge traditional gender roles. Topics such as mental health, social pressure, identity, and self-worth are addressed more openly. Additionally, the line between genres has blurred. Many modern works combine shoujo elements with action, mystery, or fantasy, appealing to a broader readership. Digital publishing and global fan communities have also allowed shoujo creators to reach audiences beyond Japan more easily than ever before. Why Shoujo Matters Shoujo holds a unique place in popular culture because it validates emotional expression and personal experiences that are often overlooked in mainstream media. It encourages empathy, self-reflection, and emotional honesty. For many readers, shoujo becomes a source of comfort, inspiration, and understanding during formative years. Beyond entertainment, shoujo plays an important cultural role by highlighting female perspectives in storytelling. It gives voice to emotions, dreams, and struggles that resonate universally, proving that stories centered on feelings and relationships can be just as powerful as action-driven narratives. Conclusion Shoujo is more than just a genre for young girls—it is a storytelling tradition that celebrates emotion, growth, and human connection. Through its rich themes, expressive art, and evolving narratives, shoujo has left a lasting impact on manga, anime, and global pop culture. Whether through gentle romance, magical adventures, or deep emotional journeys, shoujo continues to touch hearts and inspire readers around the world. Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse wajihaseo Follow i am a student of internet marketing Joined Dec 28, 2025 Trending on Popcorn Movies and TV Hot The Conformity Gate Phenomenon: Exploration of Fan Theories Following the Stranger Things Season 5 Finale # streaming # movies # recommendations # analysis 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Popcorn Movies and TV — Movie and TV enthusiasm, criticism and everything in-between. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Popcorn Movies and TV © 2016 - 2026. Let's watch something great! Log in Create account | 2026-01-13T08:49:33 |
https://dev.to/shuckle_xd/you-cant-trust-images-anymore-58jh#main-content | You can't trust Images anymore - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse pri Posted on Jan 12 You can't trust Images anymore # computervision # showdev Image manipulation isn't something new , it's been happening from almost around the time when photographs were first invented. It's just that in recent years with Artificial Intelligence has made it easier to do so. This opened the floodgates for artificially manipulated images on the internet. I literally can't tell half the time if what I am seeing is real or not. I have started questioning every image I see, heck I even question some of the photos my family sends me. This... is not good. Manipulated images have not just introduced something hard to catch, but have tarnished the credibility of real images. Images have always been a source of truth for us, something which we use to visualise what could have been merely text. Just look at history books, wouldn't they just be boring without any images? But if manipulation existed before, were images really a source of truth? History shows this isn't a one-off problem, but a recurring failure of how we trust images. One of the most widely circulated portraits of President Abraham Lincoln was later found to be simple image compositing, where his face had been placed onto another man's body. For decades this image was never questioned of its authority, despite the fact that the body belonged to a slavery advocate, directly contradicting what Lincoln stood for. This manipulation wasn't subtle, nor was it digital, yet it went unquestioned for years. Not because it was true but because verifying it was harder than believing it . Image on left is the altered portrait of President Lincoln and image on right is the original protrait of slavery advocate John Calhoun (Image credit: Library of Congress) Someone who understood the power of images was the renowned dictator of the USSR, Joseph Stalin . During his reign of power photos were not just used as historical records, but as tools to shape them. Stalin's enemies were not just removed from public life, but also expunged from records, erasing them from history. This slowly became normalised, unquestioned and now instead of images documenting the past, it was Stalin's state writing their version of the past. This type of image manipulation is an example of how it could be used not just to distort truth but help overwrite it . Left shows the original photograph of Nikolai Antipov, Stalin, Sergei Kirov and Nikolai Shvernik in Leningrad, 1926. (Credit: Tate Archive by David King, 2016/Tate, London/Art Resource, NY) The modern digital era marked a fundamental shift. With tools like Adobe Photoshop , image manipulation stopped being rare and became accessible to almost anyone. Editing no longer required significant skill, time, or resources and more importantly, it became difficult to detect. While mechanisms like metadata were introduced to preserve authenticity, they were fragile and easily altered, offering only a thin layer of reassurance. For the first time, image creation began to scale faster than image verification . This wasn’t just an increase in fake images, it was the point where trust in images stopped keeping up. Now, come to present day, that imbalance has widened dramatically. With the rise of Artificial Intelligence for image generation and editing, creating convincing manipulations no longer requires technical skill or effort. Images can now be generated, altered, or refined through simple instructions, often in seconds. What once demanded time, expertise, and intent has been reduced to a conversational interaction. Meanwhile, verifying whether an image is authentic still requires scrutiny, tools, and context in forensic fields. The result isn’t that images suddenly became fake, it’s that human judgment can no longer reliably keep up . https://x.com/IndianTechGuide/status/2009256327596355938?s=20 In recent podcast with Raj Shamani, Deepinder Goyal talked about how customers abuse AI generated content to scam Zomato customer support. I know I have been bashing on Image manipulation for the last four paragraphs or so, but it isn't inherently bad. In fact, it has enabled some of the most valuable visual work we have, from enhanced space imagery to complex visual design and creative expression. The problem isn’t that images are altered. It’s that viewers are rarely told how or why they were altered. What matters isn’t whether an image has been manipulated, but whether the truth behind it is knowable. Image of Cosmic Tarantula, which has been enhanced from infrared spectrum to a visible spectrum for better color visualization. (Image Credit: NASA, ESA, CSA, STScI, Webb ERO Production Team) To explore this problem, we’ve been building Xvertice , an attempt to give viewers more context instead of false certainty. Rather than labelling images as simply “real” or “fake,” Xvertice focuses more on explainable image forensics, helping users understand how an image may have been created, altered, or processed over time. The goal isn’t to replace judgment, but to inform it . We’re launching an experimental demo to share this approach early. It’s not a finished product, and it’s not meant to deliver definitive answers but it should make clear how we think about image trust, and how we’re trying to close the gap between creation and verification. If you try it, your feedback will directly shape where it goes next. Xvertice Links Website: https://x-vertice.com/ Twitter/X: https://x.com/teamxvertice Peerlist: https://peerlist.io/company/xvertice LinkedIn: https://www.linkedin.com/company/xvertice Sources https://www.digitalcameraworld.com/features/abraham-lincoln-vs-john-calhoun-the-original-deepfake-photo https://www.history.com/articles/josef-stalin-great-purge-photo-retouching Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse pri Follow Building https://x-vertice.com/ Joined Jan 12, 2026 Trending on DEV Community Hot When is a side project worth committing to? # ai # gemini # sideprojects # showdev What was your win this week??? # weeklyretro # discuss How to Crack Any Software Developer Interview in 2026 (Updated for AI & Modern Hiring) # softwareengineering # programming # career # interview 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:33 |
https://securitylab.github.com/advisories/GHSL-2025-076_bitplatform/ | GHSL-2025-076: Cross-site scripting (XSS) in bit platform Boilerplate WebInteropApp - CVE-2025-64710 | GitHub Security Lab skip to content / Security Lab Research Advisories CodeQL Wall of Fame Resources Events Get Involved Resources Open Source Community Enterprise / Security Lab Research Advisories CodeQL Wall of Fame Resources Open Source Community Enterprise Events Get Involved December 4, 2025 GHSL-2025-076: Cross-site scripting (XSS) in bit platform Boilerplate WebInteropApp - CVE-2025-64710 Peter Stöckli Coordinated Disclosure Timeline 2025-07-30: Reported via PVR. 2025-08-06: Version v-9.11.3 with fix released. Summary Bit platform Boilerplate was affected by a cross-site scripting (XSS) vulnerability in the WebInteropApp, potentially allowing attackers to inject malicious scripts that compromise the security and integrity of web applications. Applications based on this Bitplatform Boilerplate might also be vulnerable. Project bitplatform Tested Version v-9.10.0 Details Cross-site scripting vulnerability in WebInteropApp ( GHSL-2025-076 ) Bit platform Boilerplate contained a reflected cross-site scripting (XSS) vulnerability in the socialSignInCallback function. An attacker can specify a malicious url query parameter to trigger the vulnerability. If a JavaScript URL is passed to the url parameter the attacker provided JavaScript will be executed when the user opens the URL. The url query parameter flows unchecked from the query string into the location.href sink: private static async socialSignInCallback () { const urlParams = new URLSearchParams ( location . search ); const urlToOpen = urlParams . get ( ' url ' ) ! . toString (); const localHttpPort = urlParams . get ( ' localHttpPort ' )?. toString (); if ( ! localHttpPort ) { [..] else { WebInteropApp . autoClose = false ; location . href = urlToOpen ; } return ; } [..] } This vulnerability was discovered with the help of CodeQL’s Client-side cross-site scripting query. Impact This issue may lead to Information Disclosure. CWEs CWE-79: Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’) CVE CVE-2025-64710 Credit This issue was discovered by CodeQL and an AI agent developed by the GitHub Security Lab and reported by GHSL team member @p- (Peter Stöckli) . Contact You can contact the GHSL team at securitylab@github.com , please include a reference to GHSL-2025-076 in any communication regarding this issue. Product Features Security Team Enterprise Customer stories The ReadME Project Pricing Resources Roadmap Compare GitHub Platform Developer API Partners Atom Electron GitHub Desktop Support Docs Community Forum Professional Services GitHub Skills Status Contact GitHub Company About Blog Careers Press Inclusion Social Impact Shop GitHub Inc. © 2024 Terms Privacy Sitemap What is Git? Manage Cookies Do not share my personal information | 2026-01-13T08:49:33 |
https://opensource.org/board-member/status/board-member | Board Member – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Status: Board Member Currently active elected board members McCoy Smith Board Member McCoy Smith Director Current Term: Mar 2025 to Mar 2027 Ruth Suehle Board Member Ruth Suehle she/her Director Current Term: Mar 2025 to Mar 2028 Chris Aniszczyk Board Member Chris Aniszczyk he/him Director Current Term: Mar 2024 to Mar 2026 Sayeed Choudhury Board Member Sayeed Choudhury Vice Secretary Current Term: Jan 2024 to Oct 2026 Anne-Marie Scott Board Member Anne-Marie Scott she/her Chair of the finance committee Current Term: Apr 2023 to Mar 2026 Tracy Hinds Board Member Tracy Hinds Chair Current Term: Oct 2019 to Oct 2025 Thierry Carrez Board Member Thierry Carrez he/him Vice Chair Current Term: Aug 2021 to Mar 2027 Catharina Maracke Board Member Catharina Maracke She/Her Director Current Term: Aug 2021 to Oct 2025 Gaël Blondelle Board Member Gaël Blondelle he/him Secretary Current Term: Jan 2024 to Oct 2026 Carlo Piana Board Member Carlo Piana he/him Director Current Term: Mar 2022 to Mar 2028 Josh Berkus Board Member Josh Berkus he/him Chair of the License Committee Current Term: Apr 2022 to Mar 2026 Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:49:33 |
https://www.devcycle.com/experimentation | DevCycle for Experimentation. | DevCycle Product Solutions Resources Pricing Docs Book Demo Login Create Account Release, Experiment, and Iterate on Any Feature. Release with confidence, experiment easily, and iterate based on data. Experiment on Any Feature and Choose Winners Faster Run Experiments Anywhere Run experiments on any platform - web, mobile, and server-side. Measure Anything Connect any event or metric to measure conversions and application performance all in one place. Granular Rollout Control Have precise control over how experiments are run with gradual, scheduled and multi-step rollouts. Reduce Reliance on Engineering Run or make changes to experiments without extra development work. Run Experiments Anywhere Cross-Platform Experimentation DevCycle makes it easy to put any feature behind a flag and run an experiment on it across all platforms, environments and connected devices. Comprehensive Experimentation Platform DevCycle supports A/B testing, multivariate testing, user experience and conversion funnel tests. Engineers can also run server-side, algorithm, architecture and database query tests. Beta Feature Opt-Ins Product managers can conduct qualitative testing through beta feature opt-in programs, allowing a select audience to try new features before they are released to all users. Learn More Start Experimenting Track and Measure Success Across Multiple Experiments Custom Metrics and KPIs Create and track custom metrics tied to your key KPIs across multiple environments and platforms. Bring Your Own Data DevCycle integrates seamlessly with your existing data platform, such as Snowflake, allowing you to track experimentation results. Export Experiment Results Use our API to export experiment results and configurations to your data platforms and analytics tools, or set up an ETL or Snowflake Data Share to link DevCycle's raw data to yours for custom analysis. Learn More Start Experimenting Granular Control Over Experimentation and Rollouts With flexible targeting rules and options for gradual, scheduled, and multi-step rollouts, you can achieve precise control over user experiments across any platform. Advanced Targeting DevCycle's granular targeting rules allow precise experimentation on different audience segments and feature variations. Scheduled Rollouts Scheduled, percentage-based and multi-step rollouts let teams automate experiments and feature launches. Learn More Start Experimenting Reduce Reliance on Engineering Reusable App Components Run an unlimited amount of experiments on pre-built components of your app or site. Variable Schemas With pre-built guardrails, product managers can run experiments and rollout features safely without worrying about breaking production apps. Realtime Updates Product Managers can instantly launch, modify, or disable experiments without requiring end users to refresh their page, update their application, or deploy new code. Learn More Start Experimenting Experimentation FAQs Everything you need to know about running experiments, A/B tests, and measuring success with DevCycle. What is experimentation in feature management? + How does DevCycle support experimentation? + What types of experiments can I run? + How do I measure the success of an experiment? + Can I integrate DevCycle experimentation with my data platform? + How do I set up an A/B test in DevCycle? + What are the benefits of running experiments with feature flags? + Can I run experiments on both frontend and backend features? + How do I ensure my experiments are statistically significant? + Can I run multiple experiments at once? + Footer DevCycle What are Feature Flags? OpenFeature Create a Free Account Request a Demo Pricing Resources Documentation SDKs APIs Integrations Blog Contact Support Company About Us Careers Terms of Service Security & Compliance Privacy Policy Contact Us Discord X GitHub LinkedIn Bluesky © 2026 DevCycle All rights reserved. | 2026-01-13T08:49:33 |
https://securitylab.github.com/team/ | Team | GitHub Security Lab skip to content / Security Lab Research Advisories CodeQL Wall of Fame Resources Events Get Involved Resources Open Source Community Enterprise / Security Lab Research Advisories CodeQL Wall of Fame Resources Open Source Community Enterprise Events Get Involved team Meet the experts behind GitHub Security Lab Peter Stöckli Helping developers by breaking things. @p- @ulldma.bsky.social Jaroslav Lobačevski Security panda @jarlob @yarlob Serena Conticello see the pwn, be the pwn @helixplant Madison Oliver Security transparency advocate @taladrane @taladrane Zach Steindler Living that blue team life @steiza @steiza Shelby Cunningham Security person with a dash of data privacy @shelbyc @scunning Yasmine Mahmoud Striving to make the web—and the world—safer for everyone. @yhidad31 Kevin Backhouse Catching up on all the hacking that I should have done in the 1990s @kevinbackhouse @Kevin Backhouse Kevin Stubbings Alright get out. From now on I'll do the memory managing around here. @Kwstubbs Sylwia Budzynska *hacker voice* I’m in @sylwia-budzynska @Sylwia Budzynska Jonathan Evans Embracing the endless journey of cybersecurity discovery. @jonathanlevans Antonio Morales EthicalHacker­BugHunter & C++; 3735928559 @antonio-morales @nosoynadiemas Man Yue Mo Security scavenger @m-y-mo @mmolgtm Xavier René-Corail 3-legged race organizer: Building bridges between Dev and Sec @xcorail @xcorail.bsky.social Joseph Katsioloudes Making security easy for developers @jkcso @jkcso.bsky.social Product Features Security Team Enterprise Customer stories The ReadME Project Pricing Resources Roadmap Compare GitHub Platform Developer API Partners Atom Electron GitHub Desktop Support Docs Community Forum Professional Services GitHub Skills Status Contact GitHub Company About Blog Careers Press Inclusion Social Impact Shop GitHub Inc. © 2024 Terms Privacy Sitemap What is Git? Manage Cookies Do not share my personal information | 2026-01-13T08:49:33 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#statuses | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:33 |
https://opensource.org/press-mentions/publication/xda | XDA – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Home Blog XDA Publication: XDA October 20, 2025 Why transparency alone doesn’t make software truly open: a deep dive XDA If you want to know whether something is truly open-source, the license tells the story. OSI-approved licenses such as GPLv3, MIT, or Apache 2.0 allow unrestricted use, modification, and redistribution. Any license that adds caveats, like prohibiting commercial use, disqualifies it from being open-source. It may still be source-available, but it doesn’t carry the same freedoms. November 25, 2023 Open Source Software Licensing: Why it matters XDA Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:49:33 |
https://docs.devcycle.com/platform/testing-and-qa/web-debugger | Web Debugger | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Testing and QA Debug Tools Evaluation Lookup Point-in-time Simulation Live Events Web Debugger Self-Targeting Extras Examples Platform Testing and QA Debug Tools Web Debugger On this page Web Debugger The Web Debugger is an embeddable tool for inspecting and testing DevCycle directly on your site. Authorized users can view active Feature configurations, apply Self-Targeting Overrides, and monitor SDK events in real time—without switching back to the dashboard. Why use it? Quickly test changes with Self-Targeting Overrides : Force a specific Variation or Variable values for your current DevCycle Identity and see the effect immediately on the page. Inspect live configuration : View which Features, Variations, and Variables you’re currently being served; expand rows to see exact Variable values. Reproduce issues tied to user identity : Modify User ID, Email, or custom properties in the Debugger. This triggers the SDK’s identify() function and fetches a fresh configuration, making it easy to replicate conditions for a specific user. Monitor SDK activity : Watch configuration fetches, flag evaluations, and your app’s custom events in real time to validate logging and data flow. note The Web Debugger does not change project-level targeting rules or audiences. It only affects the current session via Self-Targeting Overrides and identity updates. info The Web Debugger is currently in beta. If you have any feedback or suggestions, please let us know by email or on our Discord . Installation The Web Debugger is available as a standalone NPM package that can be installed in your frontend projects. Install the package from NPM npm install @devcycle/web-debugger yarn add @devcycle/web-debugger Getting Started To use the Web Debugger, you need to initialize it somewhere on the page and provide the instance of the DevCycle SDK you are using on the current page. The Web Debugger will automatically connect to the SDK and start listening for events. For regular Javascript usage: import { initializeDevCycleDebugger } from '@devcycle/web-debugger' import { initializeDevCycle } from '@devcycle/js-client-sdk' const client = initializeDevCycle ( 'SDK_KEY' , { user_id : 'my-user' } ) initializeDevCycleDebugger ( client ) This will initialize the Debugger using the default options. React If you are using React, you can alternatively initialize the Debugger using the included React component: import { DevCycleDebugger } from '@devcycle/web-debugger/react' // render the component anywhere within the DevCycle React SDK's Provider context export default function SomeComponent ( { children } ) { return ( < > < DevCycleDebugger /> { children } </ > ) } The React component makes setup slightly simpler because it automatically obtains the SDK client from the React SDK's provider context. Any options that the regular Javascript function accepts can be passed as props to this component. Next.js If you are using Next.js, you can alternatively initialize the Debugger using the included React component: import { DevCycleDebugger } from '@devcycle/web-debugger/next' // render the component anywhere within the DevCycle Next SDK's Provider context export default function SomeComponent ( { children } ) { return ( < > < DevCycleDebugger /> { children } </ > ) } The React component makes setup slightly simpler because it automatically obtains the SDK client from the Next SDK's provider context. Any options that the regular Javascript function accepts can be passed as props to this component. Controlling Visibility By default, the Debugger will show any time the environment variable NODE_ENV is set to 'development'. To control when the Debugger is visible (and for who), there are two options available. Using a DevCycle Variable The recommended approach is to tell the Debugger to only show itself when a specified DevCycle Variable is enabled for the current user. To do so, pass the shouldEnableVariable option: initializeDevCycleDebugger ( client , { shouldEnableVariable : 'debugger-enabled' , } ) This allows you to use DevCycle's Targeting Rules to control who can see the Debugger. For example, you can make sure it only shows for internal users, or users with a special Custom Property set. Using a Boolean or Custom Function If you want direct control over the Debugger's visibility, you can also pass the option shouldEnable . You can provide either a boolean or a function that returns a boolean. If the boolean or the result of running the function is "true", the Debugger will show. initializeDevCycleDebugger ( client , { shouldEnable : process . env . SHOULD_SHOW_DEBUGGER , } ) initializeDevCycleDebugger ( client , { shouldEnable : ( ) => process . env . SHOULD_SHOW_DEBUGGER , } ) Keep in mind that if both shouldEnable and shouldEnableVariable are passed, shouldEnable will take precedence. Positioning The Debugger will position itself in the bottom right corner of the screen by default. You can also move it to the bottom left by passing the position option set to left . Usage Once initialized, the Web Debugger adds a toggle button to your site's corner. Clicking this button opens the Debugger. You'll first see a login screen, where you sign in with your DevCycle dashboard credentials. Access is limited to users with a DevCycle account. The Debugger provides three main areas of functionality: Self-Targeting The Debugger allows you to quickly change your Self-Targeting Overrides and see the changes reflected immediately on the current page. If you don't currently have Self-Targeting set up, the Debugger will present an option to quickly set your "DevCycle Identity" to the currently identified user on the page. Once set, you can now view and modify your Overrides for any Feature in your project. Below is an example of us using the Web Debugger for our own DevCycle instance: Live Configuration & User Identity In the "Live Configuration" section, you'll find a list of the Features and Variations that you are currently being served by DevCycle on this page. Each row can be clicked to expand and see the set of Variables and their values which are associated with that Feature and Variation. At the top of this section you can also see the current user data that you've been identified with on this page, and modify User ID or Email and/or any custom property. Applying changes to that data will trigger the SDK's identify function and trigger a new configuration to be retrieved from DevCycle. Events The Events section shows a real-time stream of events from the SDK, including new configs being obtained and any custom events that you are tracking yourself. Edit this page Last updated on Jan 9, 2026 Previous Live Events Next Self-Targeting Installation Getting Started React Next.js Controlling Visibility Positioning Usage Self-Targeting Live Configuration & User Identity Events DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:33 |
https://docs.devcycle.com/essentials/overview | DevCycle Overview | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Essentials On this page DevCycle Overview DevCycle is a feature flag platform built for engineering teams of any size, helping you easily create, rollout, and cleanup feature flags without disrupting your workflow. To help teams fit feature flagging into their development process we’ve taken a different approach than most. This page is a great starting point to understanding how we think about feature flagging and how you can get the most of out of DevCycle. Getting Started If you just want to skip ahead and get started with DevCycle, feel free to visit our Quickstart Tutorial or explore it yourself by: Creating a DevCycle account Implementing a DevCycle SDK on your platform Feature Flagging Feature flagging, also known as feature toggling, is a software development technique that allows teams to turn features or configuration settings on or off without deploying new code. This approach gives developers greater control over how and when features are released, enabling strategies like advanced targeting, gradual rollouts, and experimentation. For a deeper dive into feature flagging, we recommend reading Feature Toggles (aka Feature Flags) by Pete Hodgson on Martin Fowler’s website. DevCycle Structure The following diagram helps to illustrate the structure of DevCycle’s key concepts. You may refer to this while reading the rest of the contents below. Organizations The top level of your account where you’ll manage your account settings and users. Typically, each account or business unit has one organization, and organizations can have multiple Projects that are separated by your products. Projects Projects are the primary mechanism in DevCycle for organizing your workspaces. Projects are typically separated by product line and most features including Features, Variables, Environments and Audiences are distinct by Project. Users will have visibility into all Projects within an Organization. Environments Environments in DevCycle are meant to be mapped to the environments that exist within an organization’s development lifecycle. They are used to separate the release of Features across the different environments. All Projects within DevCycle start with three initial Environments (these can be customized and more may be added): Development Staging Production These environments, along with any you’ve added, will be included in all Features that you create eliminating the need to create a separate Feature for each environment. Each environment has its own set of SDK keys for Client-Side, Mobile, and Server-Side SDKs. Keys There are two types of Keys in DevCycle, an SDK Key and an API Key. SDK Key: This key is used for DevCycle SDKs and the Bucketing API. Due to unique security requirements and constraints for each platform, SDK keys are separated into Server, Mobile, and Client keys. Each Environment will have its own unique set of server, mobile and client-side SDK keys. API Key: This key is used for the DevCycle Management API which is a set of endpoints that are used to replicate day-to-day tasks on the dashboard. i.e. CRUD operations for Features, Variables, Audiences, etc. Features Features are the main elements that you work with in DevCycle. They are meant to map to features in your application and they are comprised of Variables and Targeting Rules that will change what your users will see in your application. Features exist across all Environments. This means that you won’t have to create a separate Feature per Environment you work in. Features are unique to each project. Variables Variables are the actual flags that live in your code. They can be grouped within Features and the values they deliver to your application are controlled by the Variations within Features. By default, when a Feature is created, a single Boolean Variable will be created with the same name as the Feature key. Features can contain multiple Variables but each Variable can only exist in one feature at a time. You may un-associate a Variable in one Feature to add it to a different Feature. Variables may be the following types: Boolean String Number JSON Variations Variations are different configurations of the Variables and their values within a Feature. For a simple Feature, a Variation can just be setting a single Variable’s value to either true or false. For a more complex Feature like an multivariate Experiment, you may have many Variations that serve different configurations across multiple Variables. By default, release Features are created with two Variations, Variation On and Variation Off , which can be edited. Targeting Rules Targeting Rules are used to determine which users or entities in your application receive a given Variation of a Feature. You may use our built-in targeting properties or create your own custom properties to segment your users into smaller user groups. Targeting Rule components: Name : The name of the targeting rule. Definition : This is where you’ll define the audience(s) and/or targeting properties. Serve : The Variation that you’re granting to the current targeting rule’s definition. For experiments, you may use the Random Distribution option to split traffic at a set percentage to each Variation. Schedule : This is used to schedule the distribution of a Variation of the feature at a specific date, or to implement a gradual or phased rollout of the Feature. If you find that you are often using the same Targeting Rules for multiple Features, try creating Audiences ! Audiences Audiences allow you to save a definition of Targeting Rules with a name so that you may reuse them in Features without needing to recreate them each time. You’ll also be able to keep track of the features that your Audiences were used in. This is useful for managing cohorts of users like QA users, beta testers, users in specific loyalty tiers, etc. Audiences that you’ve created appear as an option for targeting in all Features. Bucketing Bucketing is the process of determining the eligibility to receive a Feature and which Variation of a Feature that a user, device or some other entity will receive. Bucketing takes user and Custom Property data from the application (SDK) and compares it to each Feature’s targeting rules to determine eligibility. If a user meets the conditions of a targeting rule, they will be served the Variation that is indicated on the targeting rule. Finally, the application (SDK) will receive the Variable values that fall under the Variation that is served. Bucketing Consistency By default, Bucketing is performed consistently on DevCycle by leveraging a hash of userid and a Targeting Rule ID. For a Targeting Rule that has a Rollout or is serving a Random Distribution, this hash ensures that users, devices, or entities are uniquely assigned a Variation, and they will keep that Variation as long as the userid and Targeting rule remain unedited. A/B Testing & Experimentation Experimentation and A/B Testing are important parts of a Feature’s lifecycle. Experiments can be as simple as comparing any audiences against a metric or can be fully randomized A/B tests using statistical methodologies. The primary concept of an experiment is the need to have at least two different experiences to compare performance. Any Feature in DevCycle can be turned into an experiment, and it only requires the following: At least two Variations served to your users. At least one Metric defined and attached to your feature. Once set up, you can track the experiment's progress and determine whether there is a winning variant from within the Feature’s Experiment Results page. Metrics Metrics (or Goals), can be used to track the impact of your Feature or Experiment against a given KPI. They may be used to quickly assess the health of your Features across Environments, visualize how quickly people are visiting your applications, or determine how much memory is being used by your servers as a feature rolls out. When A/B testing, metrics are used to compare the results between the different Variations in order to determine the success or failure of an experiment. Metrics can be saved and reused across multiple Features. Status and Lifecycle Features have Statuses that indicate their current position in the Development Lifecycle. The statuses are a succinct way to understand a Feature's state, and each status has its own unique properties. DevCycle’s Feature Statuses are: In Progress In Review Completed Each status has unique properties that affect how a Feature behaves, can be interacted with, or is displayed in the dashboard. Statuses only change when a user interacts with a Feature. Ex: Marking a Feature as completed. Edit this page Last updated on Jan 9, 2026 Previous Getting Started Next Key Features Getting Started Feature Flagging DevCycle Structure Organizations Projects Environments Keys Features Variables Variations Targeting Rules Audiences Bucketing Bucketing Consistency A/B Testing & Experimentation Metrics Status and Lifecycle DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:33 |
https://docs.suprsend.com/docs/trigger-workflow | Trigger Workflow - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation WORKFLOW BUILDER Trigger Workflow Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog WORKFLOW BUILDER Trigger Workflow OpenAI Open in ChatGPT Learn how to trigger workflows using any of the available methods. OpenAI Open in ChatGPT You can trigger workflows designed on SuprSend dashboard via making a direct call to workflows.trigger endpoint or via event trigger . In SuprSend, we refer events as user-initiated actions, such as social media interactions, or system-generated events like pending payments. User needs to be created beforehand for event based triggers. Direct API trigger is a straightforward way to get started, as you can include recipient channel information directly in the API call and doesn’t require prior user creation to initiate the notification. Triggering workflow via API It is a unified API to trigger workflow and doesn’t require user creation before hand to trigger notification. Recommended for platforms transitioning their existing notifications to SuprSend. If you are using our frontend SDKs to configure notifications and passing events and user properties from third-party data platforms like Segment, then event-based trigger would be a better choice. It is a new workflow method and is available in below SDK versions (Python >= v0.11.0, Go >= v0.5.1, Node >= 1.10.0 and Java >= 0.7.0). Upgrade to the latest version if you are on older SDK versions. Here is a list of integrations that you can use to trigger workflow over API: Python Backend SDK Node Backend SDK Java Backend SDK Trigger Workflow HTTP API Backend SDK with Golang Sample Payload Here is a sample payload of direct API trigger Python Node Go Java curl Copy Ask AI from suprsend import Event from suprsend import WorkflowTriggerRequest supr_client = Suprsend( "_workspace_key_" , "_workspace_secret_" ) # Prepare workflow payload w1 = WorkflowTriggerRequest( body = { "workflow" : "_workflow_slug_" , "actor" : { "distinct_id" : "0fxxx8f74-xxxx-41c5-8752-xxxcb6911fb08" , "name" : "actor_1" , "$skip_create" : true, }, "recipients" : [ # notify user { "distinct_id" : "0gxxx9f14-xxxx-23c5-1902-xxxcb6912ab09" , "$email" : [ " [email protected] " ], "name" : "recipient_1" , "$preferred_language" : "en" , "$timezone" : "America/New_York" , "$skip_create" : true, }, # notify object { "object_type" : "teams" , "id" : "finance" , "$skip_create" : true}, ], "data" : { "first_name" : "User" , "invoice_amount" : "$5000" , "invoice_id" : "Invoice-1234" , }, }, tenant_id = "tenant_id1" , idempotency_key = "_unique_identifier_of_the_request_" , ) # Trigger workflow response = supr_client.workflows.trigger(w1) print (response) To prevent automatic creation of an actor, or recipient (user/object) in SuprSend (the case where they already exist in your system), you can use the "$skip_create": true flag. This can be applied inside the actor, individual user recipient objects, or object recipient objects. Payload Schema Property Type Description workflow string Slug of designed workflow on SuprSend dashboard. You’ll get the slug from workflow settings. actor ( optional ) string / object Includes distinct_id and properties of the user who performed the action. You can use it for cross-user notifications where you need to include actor properties in notification template. Actor properties can be added as $actor.<prop> . recipients array of string / array of objects List of users who need to be notified. You can add up to 100 recipients in a workflow trigger. You can either pass recipients as an array of distinct_id (if user is pre-synced in SuprSend database) or define recipient information inline . To notify object , pass object_id and type in recipient JSON. data object variable data required to render dynamic template content or workflow properties such as dynamic delay or channel override in send node. tenant_id string unique identifier of the brand / tenant idempotency_key string unique identifier of the request. We’ll be returning idempotency_key in our outbound webhook response . You can use it to map notification statuses and replies in your system. recipients[].$timezone string to set recipient’s timezone. Used to send notification in user’s local timezone. You can pass timezone in IANA (TZ identifier) format. recipients[].$preferred_language string to set recipient’s preferred language. This is to support localization in notification content. You can pass the language in ISO 639-1 2-letter format. Refer all language codes here . $skip_create boolean Optional flag that can be used inside actor , or recipient payloads including both user , or object . When set to true , SuprSend will not create the user or object if it doesn’t already exist in the system. Identifying recipients inline One of the benefits of using direct workflow trigger is that you can identify recipients inline. You can include recipient channel information, their channel preferences, and their user properties along with the workflow trigger. Upon triggering the workflow, the recipient will be automatically created in the SuprSend database in the background. This facilitates dynamic synchronization of your user data within SuprSend and eliminates the need for any migration efforts on your end to start sending notifications from SuprSend. You can also use recipient properties in your template as $recipient.<property> . This is how the complete recipient payload with look like json Copy Ask AI { "distinct_id" : "0gxxx9f14-xxxx-23c5-1902-xxxcb6912ab09" , "$email" :[ " [email protected] " ], "$channels" :[ "email" , "inbox" ], "user_prop1" : "value_1" , "$preferred_language" : "en" , "$timezone" : "America/New_York" } // Object will be identified by {object_type, id}. Rest of the payload will be same as user. { "object_type" : "departments" , "id" : "finance" , "$email" :[ " [email protected] " ], "user_prop1" : "value_1" } Property Type Description distinct_id string Unique identifier of the user to be notified. communication channels ( e m a i l , email, e mai l , sms, etc). array of string You can pass user channel information using $<channel> key. This will override existing channel value from the user profile and use the channel value defined in the key for notification trigger. The same channel information will also be appended to user profile in the background Refer how different communication channels can be passed here $channels array of string / dicts Use it to pass user’s channel preference in the payload. You can always use our in-build preference APIs to maintain user notification preferences. Preferences defined within SuprSend will automatically apply with workflow trigger. By default, notifications will be sent to all channels defined in the workflow delivery node. However, if you have a scenario where user has specific channel preference for a notification (e.g. they only want to receive payment reminders via email), you can include that preference in the workflow payload. This will ensure that notifications are sent only to the channels specified in the $channels key. The supported channel values are email, sms, whatsapp, androidpush, iospush, slack, webpush, ms_teams . $preferred_language string to set recipient’s preferred language. This is to support localization in notification content. You can pass the language in ISO 639-1 2-letter format. Refer all language codes here . $timezone string to set recipient’s timezone. Used to send notification in user’s local timezone. You can pass timezone in IANA (TZ identifier) format. * key-value pair You can pass other user properties to render dynamic template content in key-value pair as "user_prop1":"value1" . Extra properties will be set in subscriber profile (as subscriber properties) which can then be used in the template as $recipient.<property> . Add user communication channel json Copy Ask AI "$email" :[ " [email protected] " ], "$whatsapp" :[ "+15555555555" ], "$sms" :[ "+15555555555" ], "$androidpush" : [{ "token" : "__android_push_token__" , "provider" : "fcm" , "device_id" : "" }], "$iospush" :[{ "token" : "__ios_push_token__" , "provider" : "apns" , "device_id" : "" }], "$slack" : [{ "email" : " [email protected] " , "access_token" : "xoxb-XXXXXXXX" }] // slack using email "$slack" : [{ "user_id" : "U/WXXXXXXXX" , "access_token" : "xoxb-XXXXXX" }] // slack using member_id "$slack" : [{ "channel" : "CXXXXXXXX" , "access_token" : "xoxb-XXXXXX" }] // slack channel "$slack" : [{ "incoming_webhook" : { "url" : "https://hooks.slack.com/services/TXXXX/BXXXX/XXXXXXX" } }] // slack incoming webhook "$ms_teams" : [{ "tenant_id" : "c1981ab2-9aaf-xxxx-xxxx" , "service_url" : "https://smba.trafficmanager.net/amer" , "conversation_id" : "19:c1524d7c-a06f-456f-8abe-xxxx" }] // MS teams user or channel using conversation_id "$ms_teams" : [{ "tenant_id" : "c1981ab2-9aaf-xxxx-xxxx" , "service_url" : "https://smba.trafficmanager.net/amer" , "user_id" : "29:1nsLcmJ2RKtYH6Cxxxx-xxxx" }] // MS teams user using user_id "$ms_teams" : [{ "incoming_webhook" : { "url" : "https://wnk1z.webhook.office.com/webhookb2/XXXXXXXXX" } }] // MS teams incoming webhook Sending notification to multiple recipients Recipients in workflow call is an array of distinct_ids or recipient objects. You can pass up to 100 recipients in a single workflow trigger. SuprSend will internally convert it into multiple workflow triggers, one for each recipient in the array. json Copy Ask AI "recipients" : [ { "distinct_id" : "id1" , "$email" :[ " [email protected] " ], "name" : "recipient_1" }, { "distinct_id" : "id1" , "$email" :[ " [email protected] " ], "name" : "recipient_2" } ] ---- OR ------ "recipients" : [ "id1" , "id2" ] We recommend you to use lists and broadcasts to send notifications to a user list larger than 1000 users. This approach allows for bulk processing within SuprSend, resulting in significantly faster delivery compared to individual workflow calls. Sending individual workflows to a large set of users may introduce delays in your notification queue and is not an optimized way of handling bulk trigger. Sending cross-user notifications In scenarios where you need to notify a group of users based on another user’s action, such as sending a notification to the document owner when someone comments on it, you can specify the actor in your workflow call. This allows you to use actor’s name or other properties in your notification template. Actor properties can be included in the template as $actor.<property> . Sample template with actor and recipient properties: text API request Copy Ask AI //handlebar template Hi {{$recipient.name}}, {{$actor.name}} added {{length comments}} new comments on the {{doc_name}}. //Rendered content Hi recipient_1, actor_1 added 2 new comments on the annual IT report. Event based trigger It is a cleaner way of triggering notifications where your user sync is separate and events are generated from multiple sources, backend systems, Frontend applications (user actions on the platform) or CDP platforms like Segment. Please Note that the user profile should be created beforehand for distinct_id passed in your event call. If user is not present, it will discard the event call. Object triggers are not currently supported in event. Please get in touch if you have this requirement. Below is a sample event call to trigger payment reminder workflow: Python Node.js Java Go curl Copy Ask AI from suprsend import Event # Track Event Example distinct_id = "0fxxx8f74-xxxx-41c5-8752-xxxcb6911fb08" event_name = "Payment Pending" properties = { "first_name" : "User" , "invoice_amount" : "$5000" , "invoice_id" : "Invoice-1234" } event = Event( distinct_id = distinct_id, event_name = event_name, properties = properties) # Track event response = supr_client.track_event(event) print (response) Here is a list of all integrations that you can use to trigger event: Python Backend SDK Node Backend SDK Java Backend SDK Go Backend SDK Trigger Event HTTP API JavaScript Frontend SDK (Web) Kotlin Frontend SDK (Android) React Native Frontend SDK (App) Flutter Frontend SDK (App) Segment Customer Data Platform (CDP) Triggering workflow using google sheets Recommended for one-time notification trigger. This can be used by growth or product teams to trigger one time notifications for lead generation, sales cold messaging or to send announcements and product updates. We do not recommend sending more than 10,000 notifications using google sheets as each row in google sheet trigger converts to 1 workflow request and might take a lot of time to process. Also, since triggers via google sheets are generally promotional notifications, we recommend using one of the promotional sub-categories to trigger this notification. Read more about categories and how they impact your send latencies. Here’s a step-by-step guide on how to send notifications using google sheets: 1 Create a template group on SuprSend account. All the static content can be designed on the template, and all the variable data defined within {{...}} will be passed from the Google Sheet at the time of trigger. 2 Create a google sheet with following data. Each row in the sheet corresponds to one recipient. distinct_id column - this is the unique identifier of the user who needs to be notified. Dynamic data columns - you need to create one column each for the dynamic data (aka variables) in your template. Note that variable names are case sensitive. If this is the template content: Hi {{name}}, your {{Event}} is scheduled at {{Schedule}}. See you there. , you’ll have to create a column for each template variable - name , Event , and schedule in your sheet. User Channels columns - Next, create columns for user channel details. These channel columns are necessary to pass channel information that may not be present in the user profile. It’s always a good practice to include channel information if you’re unsure of its presence in the user profile. You can pass channels as WA for whatsapp, Email for email and SMS for SMS. For Whatsapp and SMS, you need to enter country code infront of the mobile number as +917123xxxxxx . SuprSend Status column - Fill the value TBT in rows for which you want to trigger the notification. Once, the notification is triggered, the status changes to OK .\ 📘 TIP: Google Sheet doesn’t allow to start a field with * + **. To enter in + format, use string function: ="+917123xxxxxx" 3 Go top the Google Sheets Navbar In the Navbar of Google Sheets, click on Extensions and select Apps Script 4 Remove the default information in the Apps Script It will open Apps Script in a new tab. Remove the default information present in the editor, and copy-paste the following in the editor. Appscript Copy Ask AI //Enter your workspace key, secret, template slug, workflow name & category const workspace_key = "__API_KEY__" ; const workspace_secret = "__API_SECRET__" ; const template_slug = "__TEMPLATE_SLUG__" ; const workflow_name = "__WORKFLOW_NAME__" ; const category = "promotional" // Map your column names to channels if need be // Or ensure you use following names for your columns to directly map them to channels // distinc_id for user's distinct id // $sms for user's mobile number // $email for user's email // $whatsapp for user's WhatsApp // If you have other names of your columns you can modify following two lines accordingly const channel_col_names = { "WA" : "$whatsapp" , "Email" : "$email" , "SMS" : "$sms" }; const distinct_id_col_name = 'distinct_id' //--------- No Editing required below -----------------// function Trigger_Workflows() { var sheet = SpreadsheetApp.getActiveSheet(); var data = sheet.getDataRange().getValues(); var headers = data[0]; for (var i = 1; i < data.length; i++) { var response = convert_row_to_payload(data[i], headers); if (response.status === "TBT" ) { make_api_request( response.payload, sheet.getRange(i + 1, parseInt(response.status_col) + 1) ); } } } function convert_row_to_payload(data, headers) { let status = "" ; let status_col = -1; let user = { distinct_id : null , $email : [], $sms : [], $whatsapp : [], }; let payload = {}; payload.data = {}; let private_channelkeys = [ "$sms" , "$whatsapp" , "$email" , "distinct_id" ]; for (var i = 0 ; i < headers.length; i++) { if (data[i].length !== 0) { if ( channel_col_names[headers[i]] || private_channelkeys.includes(headers[i]) ) { if (headers[i] !== "distinct_id" ) { if (user[channel_col_names[headers[i]]]) user[channel_col_names[headers[i]]].push(data[i]); if (user[headers[i]]) user[headers[i]].push(data[i]); } else { user[headers[i]] = data[i]; } } if (headers[ i ] !== "SuprSend Status" ) { payload.data[headers[i]] = data[i]; } else { status = data[i]; status_col = i; } } } user[ "distinct_id" ] = payload.data[ distinct_id_col_name ]; //user["is_transient"] = true; //Uncomment if user is temporary payload.users = [ user ]; payload.name = workflow_name; payload.notification_category = category; payload.template = template_slug; return { payload : JSON.stringify(payload) , status : status , status_col : status_col , }; } function make_api_request(payload, cell) { const uri = "/" + workspace_key + "/trigger/" ; const url = "https://hub.suprsend.com" + uri; const md5 = MD5(payload); const now = new Date().toISOString(); const message = "POST" + " \n " + md5 + " \n " + "application/json" + " \n " + now + " \n " + uri; const byteSignature = Utilities.computeHmacSha256Signature( message, workspace_secret ); const signature = Utilities.base64Encode(byteSignature); var options = { method : "POST" , contentType : "application/json" , headers : { Authorization : workspace_key + ":" + signature , Date : now , }, payload : payload , muteHttpExceptions : true , }; cell.setValue( "Processing..." ); try { var response = UrlFetchApp.fetch(url, options); cell.setValue(response.getContentText()); } catch (error) { cell.setValue( "Error : " + error); } } function onOpen() { var ui = SpreadsheetApp.getUi(); // Or DocumentApp or FormApp. ui.createMenu( "SuprSend" ) .addItem( "Trigger SuprSend Workflow" , "Trigger_Workflows" ) .addToUi(); } function MD 5 (input, isShortMode) { var isShortMode = !!isShortMode; // Be sure to be bool var txtHash = "" ; var rawHash = Utilities.computeDigest( Utilities.DigestAlgorithm.MD5, input, Utilities.Charset.UTF_8 ); if (!isShortMode) { for (i = 0; i < rawHash.length; i++) { var hashVal = rawHash[i]; if (hashVal < 0) { hashVal += 256; } if (hashVal.toString( 16 ).length == 1 ) { txtHash += "0" ; } txtHash += hashVal.toString( 16 ); } } else { for (j = 0; j < 16; j += 8) { hashVal = (rawHash[j] + rawHash[j + 1] + rawHash[j + 2] + rawHash[j + 3]) ^ (rawHash[j + 4] + rawHash[j + 5] + rawHash[j + 6] + rawHash[j + 7]); if (hashVal < 0) { hashVal += 1024; } if (hashVal.toString( 36 ).length == 1 ) { txtHash += "0" ; } txtHash += hashVal.toString( 36 ); } } // change below to "txtHash.toUpperCase()" if needed return txtHash; } You’ll find following information to be added in your script from SuprSend dashboard. Data Description api-key API Key for your workspace. From left navigation panel, select settings -> API Keys. api-secret API Key for your workspace. From left navigation panel, select settings -> API Keys. template-slug Add the template slug of the template that you want to trigger. You can copy the the template slug by clicking on copy icon next to the template name on template details page. Workflow Name Give a name to identify your workflow. It’ll help you locate the sent workflow on the workflow listing page. You can see the notification performance on Workflow -> Analytics page. category Provide notification category. We recommend using promotional sub-category for sending engagement notifications. You can read more Notification Categories here . 5 Save the Script - Close the Tab - Reload your Google Sheets Page! After reloading, you will find a new option named “ SuprSend ” in the navigation bar. On clicking it, you will see the option to Trigger SuprSend Workflow . On triggering, the script will pick up all the rows which have value in the column name “ SuprSend Status ”, and will make an API call to SuprSend. For the successful API call, the status will change to OK . 6 Check the Status You can check the status of your notification trigger on the Logs page. Was this page helpful? Yes No Suggest edits Raise issue Previous Validate Trigger Payload Validate the data passed to workflow API or event properties using JSON schemas to catch payload mismatch errors at API level. Next ⌘ I x github linkedin youtube Powered by On this page Triggering workflow via API Sample Payload Identifying recipients inline Add user communication channel Sending notification to multiple recipients Sending cross-user notifications Event based trigger Triggering workflow using google sheets self.__next_f.push([1,"\"use strict\";\nconst {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];\nconst {useMDXComponents: _provideComponents} = arguments[0];\nfunction _createMdxContent(props) {\n const _components = {\n a: \"a\",\n annotation: \"annotation\",\n br: \"br\",\n code: \"code\",\n em: \"em\",\n hr: \"hr\",\n li: \"li\",\n math: \"math\",\n mi: \"mi\",\n mo: \"mo\",\n mrow: \"mrow\",\n p: \"p\",\n pre: \"pre\",\n semantics: \"semantics\",\n span: \"span\",\n strong: \"strong\",\n table: \"table\",\n tbody: \"tbody\",\n td: \"td\",\n th: \"th\",\n thead: \"thead\",\n tr: \"tr\",\n ul: \"ul\",\n ..._provideComponents(),\n ...props.components\n }, {Card, CardGroup, CodeBlock, CodeGroup, Heading, Info, Note, OptimizedImage, Step, Steps, Tip, Warning} = _components;\n if (!Card) _missingMdxReference(\"Card\", true);\n if (!CardGroup) _missingMdxReference(\"CardGroup\", true);\n if (!CodeBlock) _missingMdxReference(\"CodeBlock\", true);\n if (!CodeGroup) _missingMdxReference(\"CodeGroup\", true);\n if (!Heading) _missingMdxReference(\"Heading\", true);\n if (!Info) _missingMdxReference(\"Info\", true);\n if (!Note) _missingMdxReference(\"Note\", true);\n if (!OptimizedImage) _missingMdxReference(\"OptimizedImage\", true);\n if (!Step) _missingMdxReference(\"Step\", true);\n if (!Steps) _missingMdxReference(\"Steps\", true);\n if (!Tip) _missingMdxReference(\"Tip\", true);\n if (!Warning) _missingMdxReference(\"Warning\", true);\n return _jsxs(_Fragment, {\n children: [_jsxs(_components.p, {\n children: [\"You can trigger workflows designed on SuprSend dashboard via making a \", _jsx(_components.a, {\n href: \"/docs/trigger-workflow#triggering-workflow-via-api\",\n children: \"direct call\"\n }), \" to \", _jsx(_components.code, {\n children: \"workflows.trigger\"\n }), \" endpoint or via \", _jsx(_components.a, {\n href: \"/docs/trigger-workflow#event-based-trigger\",\n children: \"event trigger\"\n }), \". In SuprSend, we refer events as user-initiated actions, such as social media interactions, or system-generated events like pending payments. User needs to be created beforehand for event based triggers.\"]\n }), \"\\n\", _jsxs(_components.p, {\n children: [_jsx(_components.a, {\n href: \"/docs/trigger-workflow#triggering-workflow-via-api\",\n children: \"Direct API trigger\"\n }), \" is a straightforward way to get started, as you can include recipient channel information directly in the API call and doesn’t require prior user creation to initiate the notification.\"]\n }), \"\\n\", _jsx(Heading, {\n level: \"2\",\n id: \"triggering-workflow-via-api\",\n children: \"Triggering workflow via API\"\n }), \"\\n\", _jsx(Info, {\n children: _jsxs(_components.p, {\n children: [\"It is a unified API to trigger workflow and doesn’t require user creation before hand to trigger notification. Recommended for platforms transitioning their existing notifications to SuprSend. If you are using our frontend SDKs to configure notifications and passing events and user properties from third-party data platforms like Segment, then \", _jsx(_components.a, {\n href: \"/docs/trigger-workflow#event-based-trigger\",\n children: \"event-based trigger\"\n }), \" would be a better choice.\"]\n })\n }), \"\\n\", _jsx(Warning, {\n children: _jsx(_components.p, {\n children: \"It is a new workflow method and is available in below SDK versions (Python \u003e= v0.11.0, Go \u003e= v0.5.1, Node \u003e= 1.10.0 and Java \u003e= 0.7.0). Upgrade to the latest version if you are on older SDK versions.\"\n })\n }), \"\\n\", _jsx(_components.p, {\n children: \"Here is a list of integrations that you can use to trigger workflow over API:\"\n }), \"\\n\", _jsxs(CardGroup, {\n cols: \"3\",\n children: [_jsx(Card, {\n title: \"Python Backend SDK\",\n icon: \"python\",\n iconType: \"solid\",\n href: \"/docs/python-trigger-workflow-from-api\"\n }), _jsx(Card, {\n title: \"Node Backend SDK\",\n icon: \"js\",\n iconType: \"solid\",\n href: \"/docs/node-trigger-workflow-from-api\"\n }), _jsx(Card, {\n title: \"Java Backend SDK\",\n icon: \"java\",\n iconType: \"solid\",\n href: \"/docs/java-trigger-workflow-from-api\"\n }), _jsx(Card, {\n title: \"Trigger Workflow HTTP API\",\n icon: \"arrows-spin\",\n iconType: \"solid\",\n href: \"/reference/trigger-workflow-api\"\n }), _jsx(Card, {\n title: \"Backend SDK with Golang\",\n icon: \"golang\",\n iconType: \"solid\",\n href: \"/docs/go-trigger-workflow-from-api\"\n })]\n }), \"\\n\", _jsx(Heading, {\n level: \"3\",\n id: \"sample-payload\",\n children: \"Sample Payload\"\n }), \"\\n\", _jsx(_components.p, {\n children: \"Here is a sample payload of direct API trigger\"\n }), \"\\n\", _jsxs(CodeGroup, {\n children: [_jsx(CodeBlock, {\n filename: \"Python\",\n numberOfLines: \"40\",\n language: \"python\",\n children: _jsx(_components.pre, {\n className: \"shiki shiki-themes github-light-default dark-plus\",\n style: {\n backgroundColor: \"#ffffff\",\n \"--shiki-dark-bg\": \"#0B0C0E\",\n color: \"#1f2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n language: \"python\",\n children: _jsxs(_components.code, {\n language: \"python\",\n numberOfLines: \"40\",\n children: [_jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \"from\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" suprsend \"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \"import\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" Event\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \"from\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" suprsend \"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \"import\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" WorkflowTriggerRequest\"\n })]\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\"\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"supr_client \"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"=\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" Suprsend(\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"_workspace_key_\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \", \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"_workspace_secret_\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \")\"\n })]\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\"\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#6E7781\",\n \"--shiki-dark\": \"#6A9955\"\n },\n children: \"# Prepare workflow payload\"\n })\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"w1 \"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"=\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" WorkflowTriggerRequest(\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#953800\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" body\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"=\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"{\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"workflow\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"_workflow_slug_\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \",\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"actor\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": {\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"distinct_id\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"0fxxx8f74-xxxx-41c5-8752-xxxcb6911fb08\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \",\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"name\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"actor_1\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \",\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"$skip_create\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": true,\"\n })]\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" },\"\n })\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"recipients\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": [\"\n })]\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#6E7781\",\n \"--shiki-dark\": \"#6A9955\"\n },\n children: \" # notify user\"\n })\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" {\"\n })\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"distinct_id\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"0gxxx9f14-xxxx-23c5-1902-xxxcb6912ab09\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \",\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"$email\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": [\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"abc@example.com\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"],\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"name\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"recipient_1\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \",\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"$preferred_language\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"en\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \",\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"$timezone\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"America/New_York\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \",\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"$skip_create\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": true,\"\n })]\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" },\"\n })\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#6E7781\",\n \"--shiki-dark\": \"#6A9955\"\n },\n children: \" # notify object\"\n })\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" {\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"object_type\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"teams\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \", \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"id\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"finance\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \", \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"$skip_create\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": true},\"\n })]\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" ],\"\n })\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"data\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": {\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"first_name\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"User\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \",\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"invoice_amount\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"$5000\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \",\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"invoice_id\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \": \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"Invoice-1234\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \",\"\n })]\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" },\"\n })\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" },\"\n })\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#953800\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" tenant_id\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"=\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"tenant_id1\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \",\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#953800\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" idempotency_key\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"=\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"_unique_identifier_of_the_request_\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \",\"\n })]\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \")\"\n })\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\"\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#6E7781\",\n \"--shiki-dark\": \"#6A9955\"\n },\n children: \"# Trigger workflow\"\n })\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"response \"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"=\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" supr_client.workflows.trigger(w1)\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#0550AE\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \"print\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"(response)\"\n })]\n }), \"\\n\"]\n })\n })\n }), _jsx(CodeBlock, {\n filename: \"Node\",\n numberOfLines: \"44\",\n language: \"javascript\",\n children: _jsx(_components.pre, {\n className: \"shiki shiki-themes github-light-default dark-plus\",\n style: {\n backgroundColor: \"#ffffff\",\n \"--shiki-dark-bg\": \"#0B0C0E\",\n color: \"#1f2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n language: \"javascript\",\n children: _jsxs(_components.code, {\n language: \"javascript\",\n numberOfLines: \"44\",\n children: [_jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \"const\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" { \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0550AE\",\n \"--shiki-dark\": \"#4FC1FF\"\n },\n children: \"Suprsend\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \", \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0550AE\",\n \"--shiki-dark\": \"#4FC1FF\"\n },\n children: \"WorkflowTriggerRequest\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" } \"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"=\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \" require\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"(\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"@suprsend/node-sdk\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \");\"\n })]\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \"const\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0550AE\",\n \"--shiki-dark\": \"#4FC1FF\"\n },\n children: \" supr_client\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" =\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \" new\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \" Suprsend\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"(\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"_workspace_key_\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \", \"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \"\\\"_workspace_secret_\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \");\"\n })]\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\"\n }), \"\\n\", _jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#6E7781\",\n \"--shiki-dark\": \"# | 2026-01-13T08:49:33 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#completed | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:33 |
https://dumb.dev.to/report-abuse | Report abuse - DUMB DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DUMB DEV Community Close Report abuse Thank you for reporting any abuse that violates our Code of Conduct and/or Terms and Conditions . We continue to try to make this environment a great one for everybody. If you are submitting a bug report, please create a GitHub issue in the main Forem repo. Rude or vulgar Harassment or hate speech Spam or copyright issue Inappropriate listings message/category Other Reported URL Message Please provide any additional information or context that will help us understand and handle the situation. Send Feedback 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DUMB DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DUMB DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:33 |
https://dev.to/leon0824 | Leon - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Leon 404 bio not found Joined Joined on Aug 12, 2018 Personal website https://leonh.space/ github website twitter website Seven Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least seven years. Got it Close Six Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least six years. Got it Close Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Five Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least five years. Got it Close Four Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least four years. Got it Close 8 Week Writing Streak The streak continues! You've written at least one post per week for 8 consecutive weeks. Unlock the 16-week badge next! Got it Close 4 Week Writing Streak You've posted at least one post per week for 4 consecutive weeks! Got it Close Three Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least three years. Got it Close Two Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least two years. Got it Close One Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least one year. Got it Close More info about @leon0824 GitHub Repositories ExcelMerger ExcelMerger merges Excel files Svelte • 11 stars Post 82 posts published Comment 8 comments written Tag 1 tag followed Pin Pinned 用 2Captcha 通過 CAPTCHA 人機驗證 Leon Leon Leon Follow Feb 11 '22 用 2Captcha 通過 CAPTCHA 人機驗證 # 2captcha # captch # recaptch # crawler 3 reactions Comments 2 comments 4 min read ngrok 讓本機發佈出可被訪問的網址 Leon Leon Leon Follow Jan 4 '24 ngrok 讓本機發佈出可被訪問的網址 # ngrok Comments Add Comment 1 min read Want to connect with Leon? Create an account to connect with Leon. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in Plesk 升級筆記 Leon Leon Leon Follow Nov 30 '23 Plesk 升級筆記 # plesk Comments Add Comment 1 min read WordPress 備份外掛 WPvivid Backup Leon Leon Leon Follow Oct 19 '23 WordPress 備份外掛 WPvivid Backup # wordpress # wpvivid Comments Add Comment 1 min read WordPress Child Theme Leon Leon Leon Follow Oct 12 '23 WordPress Child Theme # wordpress Comments Add Comment 2 min read Local 本機 WordPress 開發環境建置工具 Leon Leon Leon Follow Oct 2 '23 Local 本機 WordPress 開發環境建置工具 # wordpress Comments Add Comment 1 min read 裝 WP-CLI Leon Leon Leon Follow Aug 19 '23 裝 WP-CLI # wordpress Comments Add Comment 1 min read 談 CSS 命名 Leon Leon Leon Follow Aug 13 '23 談 CSS 命名 # css Comments Add Comment 1 min read 開源產業 Leon Leon Leon Follow Aug 10 '23 開源產業 # opensource 1 reaction Comments Add Comment 1 min read 語意化網頁 Leon Leon Leon Follow Jul 18 '23 語意化網頁 # semantic # opengraph Comments Add Comment 2 min read 如何在 elementary OS 安裝 Firefox Beta Leon Leon Leon Follow Jul 3 '23 如何在 elementary OS 安裝 Firefox Beta # firefox # linux Comments Add Comment 1 min read Google Chrome 好快啊！ Leon Leon Leon Follow Jun 19 '23 Google Chrome 好快啊！ # browser Comments Add Comment 1 min read Java 語言筆記 Leon Leon Leon Follow Jun 17 '23 Java 語言筆記 # java Comments Add Comment 1 min read Aurelia 2 從零開始之建構專案 Leon Leon Leon Follow Jun 17 '23 Aurelia 2 從零開始之建構專案 # aurelia Comments Add Comment 3 min read Lorem Picsum 佔位圖產生器 Leon Leon Leon Follow Jun 7 '23 Lorem Picsum 佔位圖產生器 1 reaction Comments Add Comment 1 min read CentOS 7 裝 Adminer Leon Leon Leon Follow May 15 '23 CentOS 7 裝 Adminer # centos # adminer # mysql # mariadb Comments Add Comment 1 min read CentOS 7 裝 mycli Leon Leon Leon Follow May 12 '23 CentOS 7 裝 mycli # centos # mycli # mysql # mariadb Comments Add Comment 1 min read CentOS 裝 MariaDB 10 Leon Leon Leon Follow Mar 31 '23 CentOS 裝 MariaDB 10 # centos # mariadb Comments Add Comment 1 min read CentOS 7 裝 PHP FPM Leon Leon Leon Follow Mar 6 '23 CentOS 7 裝 PHP FPM Comments Add Comment 1 min read CentOS 7 裝 PHP 7 Leon Leon Leon Follow Jan 4 '23 CentOS 7 裝 PHP 7 # emptystring 1 reaction Comments Add Comment 1 min read CentOS 7 裝 NGINX Leon Leon Leon Follow Jul 26 '22 CentOS 7 裝 NGINX # centos # nginx 3 reactions Comments Add Comment 1 min read Odoo 安裝 Leon Leon Leon Follow May 1 '22 Odoo 安裝 # odoo 12 reactions Comments Add Comment 1 min read 自學的 SoloLearn Leon Leon Leon Follow Apr 22 '22 自學的 SoloLearn # sololearn 3 reactions Comments Add Comment 1 min read 給 PHP 開發者的 Docker 文件（六） Leon Leon Leon Follow Apr 21 '22 給 PHP 開發者的 Docker 文件（六） 5 reactions Comments Add Comment 1 min read 給 PHP 開發者的 Docker 文件（五） Leon Leon Leon Follow Feb 18 '22 給 PHP 開發者的 Docker 文件（五） # php # docker 7 reactions Comments Add Comment 1 min read 給 PHP 開發者的 Docker 文件（四） Leon Leon Leon Follow Feb 17 '22 給 PHP 開發者的 Docker 文件（四） # php # docker 5 reactions Comments 1 comment 2 min read 給 PHP 開發者的 Docker 文件（三） Leon Leon Leon Follow Feb 13 '22 給 PHP 開發者的 Docker 文件（三） 4 reactions Comments Add Comment 1 min read 給 PHP 開發者的 Docker 文件（二） Leon Leon Leon Follow Jan 19 '22 給 PHP 開發者的 Docker 文件（二） # docker # php Comments Add Comment 1 min read 給 PHP 開發者的 Docker 文件（一） Leon Leon Leon Follow Jan 18 '22 給 PHP 開發者的 Docker 文件（一） # docker # php 2 reactions Comments Add Comment 1 min read Java 的常數 Leon Leon Leon Follow Dec 17 '21 Java 的常數 # java Comments Add Comment 1 min read Java 的迴圈控制 Leon Leon Leon Follow Dec 16 '21 Java 的迴圈控制 # java # loop 3 reactions Comments Add Comment 1 min read OpenAPI 打通前後端任督二脈 Leon Leon Leon Follow Dec 15 '21 OpenAPI 打通前後端任督二脈 # openapi # fastapi 7 reactions Comments Add Comment 4 min read Apiary API 規格文件 假接口一次到位 Leon Leon Leon Follow Dec 14 '21 Apiary API 規格文件 假接口一次到位 # apiary # api 5 reactions Comments Add Comment 1 min read Vite 與環境變數 Leon Leon Leon Follow Dec 12 '21 Vite 與環境變數 # vite # javascript 6 reactions Comments Add Comment 1 min read Pydantic 小筆記 Leon Leon Leon Follow Dec 11 '21 Pydantic 小筆記 # python # pydantic 5 reactions Comments Add Comment 2 min read 極簡 nvm 使用指南 Leon Leon Leon Follow Dec 9 '21 極簡 nvm 使用指南 # node # nvm 5 reactions Comments Add Comment 1 min read GitLab CI 從小白到入門 Leon Leon Leon Follow Nov 29 '21 GitLab CI 從小白到入門 # gitlab # ci Comments Add Comment 2 min read 擴充 AWS 主機硬碟空間 Leon Leon Leon Follow Nov 28 '21 擴充 AWS 主機硬碟空間 # aws # ebs Comments Add Comment 1 min read 以 Authlib 實現 OAuth 1 的 Twitter 登入 Leon Leon Leon Follow Nov 25 '21 以 Authlib 實現 OAuth 1 的 Twitter 登入 # oauth # twitter # authlib # python 2 reactions Comments Add Comment 5 min read 升級裝有 Plesk 的 Ubuntu 16.04 Leon Leon Leon Follow Nov 24 '21 升級裝有 Plesk 的 Ubuntu 16.04 # ubuntu # plesk 1 reaction Comments Add Comment 2 min read Python Log 從小白到入門 Leon Leon Leon Follow Nov 23 '21 Python Log 從小白到入門 # python # logging 7 reactions Comments Add Comment 3 min read 如何在 Jupyter Notebook 跑 Python 異步程式 Leon Leon Leon Follow Nov 22 '21 如何在 Jupyter Notebook 跑 Python 異步程式 # python # jupyter # async 1 reaction Comments Add Comment 1 min read 你的資料庫支援時間資料型別嗎？ Leon Leon Leon Follow Nov 18 '21 你的資料庫支援時間資料型別嗎？ # database # json # nosql 3 reactions Comments Add Comment 2 min read Orator ORM 的 Seeding 機制 Leon Leon Leon Follow Nov 15 '21 Orator ORM 的 Seeding 機制 # python # orm # orator 1 reaction Comments Add Comment 2 min read 初探 Orator ORM Leon Leon Leon Follow Nov 14 '21 初探 Orator ORM # python # orm # orator 4 reactions Comments Add Comment 5 min read 初探 Strapi Headless CMS Leon Leon Leon Follow Nov 14 '21 初探 Strapi Headless CMS # strapi # cms # headless 6 reactions Comments Add Comment 2 min read 建置 Python 3 開發環境 Leon Leon Leon Follow Nov 13 '21 建置 Python 3 開發環境 # python 2 reactions Comments Add Comment 5 min read MailPoet 為 WordPress 量身設計的發信服務 Leon Leon Leon Follow Nov 12 '21 MailPoet 為 WordPress 量身設計的發信服務 # wordpress # mailpoet 3 reactions Comments Add Comment 1 min read Plesk / Cloudflare / Lightsail 混合架構的安全規劃 Leon Leon Leon Follow Nov 11 '21 Plesk / Cloudflare / Lightsail 混合架構的安全規劃 # plesk # cloudflare # lightsail # firewall 2 reactions Comments Add Comment 2 min read 為什麼你的個資會外洩？談社交工程 Leon Leon Leon Follow Nov 10 '21 為什麼你的個資會外洩？談社交工程 # 社交工程 # 詐騙 3 reactions Comments Add Comment 1 min read 靜態網站產生器 Zola Leon Leon Leon Follow Nov 8 '21 靜態網站產生器 Zola # zola # ssg 5 reactions Comments Add Comment 3 min read Google Search Console 的「已檢索」、「已找到」是什麼意思？ Leon Leon Leon Follow Nov 7 '21 Google Search Console 的「已檢索」、「已找到」是什麼意思？ # google # seo 2 reactions Comments Add Comment 1 min read Rapid Environment Editor 設定 Windows 環境變數的工具 Leon Leon Leon Follow Nov 6 '21 Rapid Environment Editor 設定 Windows 環境變數的工具 # windows 2 reactions Comments Add Comment 1 min read Rules Engine 規則引擎 Leon Leon Leon Follow Nov 5 '21 Rules Engine 規則引擎 # rulesengine # rete 2 reactions Comments Add Comment 1 min read KeePass 密碼管理器 Leon Leon Leon Follow Nov 4 '21 KeePass 密碼管理器 # keepass # password 2 reactions Comments Add Comment 1 min read 如何理解 Jira 的 Story Leon Leon Leon Follow Nov 3 '21 如何理解 Jira 的 Story # jira 1 reaction Comments Add Comment 1 min read Cockpit 高大上的 Linux Web 管理介面 Leon Leon Leon Follow Nov 2 '21 Cockpit 高大上的 Linux Web 管理介面 # cockpit # linux 4 reactions Comments Add Comment 1 min read 自己的 VPN 自己建，用 ZeroTier 建構自己的虛擬內網 Leon Leon Leon Follow Oct 31 '21 自己的 VPN 自己建，用 ZeroTier 建構自己的虛擬內網 # zerotier # vpn 4 reactions Comments Add Comment 1 min read 用 Spectron 對 Electron App 做測試 Leon Leon Leon Follow Oct 30 '21 用 Spectron 對 Electron App 做測試 # electron # spectron 4 reactions Comments Add Comment 2 min read 如何在 elementary OS 安裝 Firefox Beta Leon Leon Leon Follow Oct 29 '21 如何在 elementary OS 安裝 Firefox Beta # firefox # linux 4 reactions Comments Add Comment 1 min read Java 編譯成 WebAssembly 的工具 Leon Leon Leon Follow Oct 28 '21 Java 編譯成 WebAssembly 的工具 # java # webassembly 2 reactions Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:33 |
https://www.jenkins.io/ | Jenkins Jenkins Build great things at any scale The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project. Download Documentation Redesigned Jenkins header and UI Jenkins' UI has been redesigned and updated for a more modern look and feel. Read more about the background and various changes in Jan Faracik's blog post. Read here Jenkins 2025 Community Awards The Jenkins 2025 Community Awards winners have been announced! Congratulations to all the winners and thank you for all of your contributions. Thanks to the community for voting and making this possible. Read more about the awards and winners in our blog. Jenkins wins DevOps Dozen award Jenkins has been awarded the "Most innovative DevOps Open Source project" distinction by DevOps Dozen. More info Meet the driving forces behind Jenkins as we showcase the top contributors shaping the future of continuous integration and delivery. More info Jenkins Stories! We are looking for experiences of Jenkins users from around the world showcasing how they are building, deploying, and automating great software with Jenkins. Check out their user stories and share yours More info Participate and Contribute! Jenkins is a community-driven project. We invite everyone to join us and move it forward. Any contribution matters: code, documentation, localization, blog posts, artwork, meetups, and anything else. If you have five minutes or a few hours, you can help! More info Continuous Integration and Continuous Delivery As an extensible automation server, Jenkins can be used as a simple CI server or turned into the continuous delivery hub for any project. Easy installation Jenkins is a self-contained Java-based program, ready to run out-of-the-box, with packages for Windows, Linux, macOS and other Unix-like operating systems. Easy configuration Jenkins can be easily set up and configured via its web interface, which includes on-the-fly error checks and built-in help. Plugins With hundreds of plugins in the Update Center, Jenkins integrates with practically every tool in the continuous integration and continuous delivery toolchain. Extensible Jenkins can be extended via its plugin architecture, providing nearly infinite possibilities for what Jenkins can do. Distributed Jenkins can easily distribute work across multiple machines, helping drive builds, tests and deployments across multiple platforms faster. Recent posts Google Summer of Code 2026: Volunteers Needed to Mentor Future Jenkins Contributors TL,DR: Jenkins is preparing to participate in its tenth (10th) year in Google Summer of Code (GSoC). We are seeking volunteers to be Jenkins mentors in the program: Mentoring takes about 5 to 8 hours of work per week for a 10-22 weeks program. Mentors provide guidance, coaching, review proposals, pull-requests, and contributor presentations. Sign up to mentor one of these project ideas or... Shivay Lamba January 5, 2026 2025 Jenkins Board and Officer Election Results The Jenkins community has completed the 2025 elections. On behalf of the Jenkins community and the elections committee, we congratulate all newly elected board members and officers! We also thank all candidates and voters who participated this year. Election results: Daniel Krämer joins Alexander Brandes, Valentin Delaye, Alex Earl and Basil Crow on the Jenkins Governance Board Stefan Spieker will serve as Events Officer (uncontested) Tim Jacomb... Alexander Brandes December 29, 2025 Jenkins 2.543 and 2.541.1: New Linux Repository Signing Keys Beginning December 23, 2025 with 2.543, the Jenkins weekly releases will use new repository signing keys for the Linux installation packages. The same change will be made in Jenkins LTS releases beginning January 21, 2026. Administrators of Linux systems must install the new signing keys on their Linux servers before installing Jenkins Jenkins weekly 2.543 or Jenkins LTS 2.541.1. Debian/Ubuntu Update Debian compatible operating... Mark Waite Damien DUPORTAL December 23, 2025 Announcing the new Jenkins Bug Bounty Program It is with great pleasure that we announce the new Jenkins Bug Bounty Program! The European Commission (EC OSPO) has partnered with YesWeHack to launch bug bounty programs for several open source projects. The Jenkins project was selected as a valuable asset for public administration across the European Union. The program will run for one year, rewarding security researchers who find and responsibly... Wadeck Follonier December 10, 2025 Automating Jenkins on Android with Infrastructure as Code From Manual to Automated In March 2023, I explored running Jenkins on Android devices using Termux, demonstrating that it’s technically possible to transform aging smartphones into CI/CD infrastructure. The manual setup worked, but it required 2-3 hours of configuration and was error-prone. Fast-forward to 2025: I’ve automated the entire process using Infrastructure as Code principles. What once took hours of manual configuration... Bruno Verachten October 31, 2025 Advancing the Jenkins Tekton Client Plugin through CRD Generation, JUnit 5 Modernization, and Automated CI The Jenkins Tekton Client Plugin bridges Jenkins and Kubernetes-native Tekton pipelines, allowing Jenkins users to trigger and manage Tekton resources directly from their existing CI/CD workflows. Over the course of Google Summer of Code 2025, significant progress was made in modernizing, stabilizing, and extending the plugin’s capabilities. This project introduced end-to-end CI automation, migrated tests to JUnit 5, implemented large-scale CRD-to-Java... Maeve Ho October 19, 2025 GSoC 2025 Final Term: Build Retooling of jenkins.io This post marks the successful completion of my Google Summer of Code 2025 project: Complete Build Retooling of jenkins.io. Over the past months, we’ve transformed the Jenkins documentation infrastructure from legacy systems to a modern, performant, and well-organized platform. Table of Contents Project Recap Post-Midterm Achievements Non-Versioned Site (Vite.js) Completion Versioned Site (Antora) Enhancements Technical Implementation Deep Dive Challenges & Learnings Future Roadmap Acknowledgments Project Resources Project Recap The initiative set out... Birajit Saikia October 19, 2025 Revamped Tests UI in Jenkins The JUnit plugin has received a major redesign, focusing on a cleaner and more consistent UI. This work draws directly from the Pipeline Graph View plugin and the Jenkins Design Library, bringing much-needed polish to one of Jenkins' oldest plugins. So what’s new? New user interface The plugin has been redesigned to make test results easier to understand at a glance. Pages have been streamlined, components... Jan Faracik October 16, 2025 Hacktoberfest 2025 The annual Hacktoberfest is back! Please join us as we celebrate and support open-source during the month of October. Contributors can earn badges and improve their open source contribution skills. The Jenkins project will participate once again in the event. We invite you to contribute to the Jenkins project but also, as maintainers, to welcome and help newcomers. Contributors This is what contributors need to know... Kris Stern September 24, 2025 We thank the following organizations for their major commitments to support the Jenkins project. CD.Foundation_LogoMaster We thank the following organizations for their support of the Jenkins project through free and/or open source licensing programs. Atlassian Datadog DigitalOcean Discourse Fastly IBM Netlify PagerDuty Sentry Tsinghua University XMission Belnet RWTH Aachen University Hostico FreeDif Servana Yamagata University Thank you mikecirioli for making 1 pull request to the repository-permissions-updater repo in December 2025! | 2026-01-13T08:49:33 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#permission-rules | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:33 |
https://docs.devcycle.com/platform/feature-flags/targeting/rollouts#rollouts | Scheduling & Rollouts | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Targeting Overview Audiences Custom Properties Random Variations Scheduling & Rollouts Randomize using a Custom Property EdgeDB (Stored Custom Properties) Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Targeting Scheduling & Rollouts On this page Scheduling & Rollouts Scheduling a Feature By default, all Targeting Rules do not have a Schedule, and Features will be delivered immediately to any users who match the Targeting Rule definition once an Environment is enabled. To schedule a specific release time for your Feature, change the Schedule option to "Specific Date and Time". You may then input a date and time for when you release your Feature. Note: Dates in the past may be selected, and will be treated as if there is no schedule. Users who match the Targeting Rule will receive the served Variation if the Feature is enabled in that environment. The timezone is set to the DevCycle user's timezone. info With Passthrough Rollouts enabled, if a user qualifies for a Targeting Rule that has a schedule, but the schedule has not yet been reached, the user will bypass that Targeting Rule and move onto the next Targeting Rule. See Passthrough Rollouts for more details. Rollouts & Rollbacks Gradual Rollouts To roll out or roll back a Feature to your users at a specific time, open the "Schedule" dropdown and select "Gradual Rollout". This will give you the option to create a rollout, from a start percentage to an end percentage at specific dates. Use this option to gradually roll out or roll back the Feature to users and monitor the impact over time without creating an instant switch of users. tip To gradually rollout a Feature, select a start percentage that's lower than the end percentage, and an end date that's later than the start date. To gradually rollback a Feature, select an end percentage that is lower than your start percentage, and an end date that's later than the start date. To instantly rollout or rollback a Feature to a specific percentage of users at once, select the same start and end percentage, and the same start and end date. The dates chosen can be in the past. While a Feature is active and a rollout has been set, you can view the current % of rollout or rollback at any time from it's Targeting Rules section. Multi-Step Rollouts This rollout option allows you to setup a stepped or phased rollout or rollback for your Feature. For example, you can use the Multi-Step rollout functionality to setup a rollout schedule with certain percentage milestones, e.g. rollout to 25% of users on X date, rollout to 50% of users at Y date, and then gradually rollout to the rest of users (100%) by Z date. To set up a Multi-Step Rollout in your Targeting Rule, open the "Schedule" dropdown and select "Multi-step Rollout". This will give you the option to create a custom, multi-step rollout, where you can define a start percentage, and add as many rollout steps as you wish, each with their own percentage and scheduled date. You must select how you would like your rollout to transition between steps by clicking on the icons below each rollout step. Step : Transition immediately between steps. Gradual : Transition gradually between steps. While a Feature is active and a rollout has been set, you can view the current % of rollout or rollback at any time from its Targeting Rules section. Example Here is how you'd set up the phased rollout example described above. The same can be done for rollbacks with the ordering of the percentages in reverse: Stopping a Rollout While the easiest way to end a rollout is to remove the Targeting Rule or disable the targeting for an environment dropping everyone to default values, there are times when you may want to stop a rollout, holding the percentage steady. This is relevant if you are seeing small issues that are easily resolved, where you may not want to add more users and exacerbate the issue, but you also don't want to take away a Feature from users that already have received it. This may also be relevant in scenarios where you can't rollback a Feature and regardless of the issue happening you are just trying to limit the blast radius to users who have already received the Feature. Regardless of the scenario you find yourself in, both Gradual and Multi-Step Rollouts can be stopped at their current rollout percentage and held there indefinitely. To stop a rollout, just click the Stop button next to the Current Rollout Percentage indicator. You will be asked to confirm the change. Once confirmed the rollout will be modified from whatever it was originally, to a Multi-Step Rollout with the last step being the current time and current rollout percentage. This edit can still be reviewed and discarded if you would like. When you are ready to accept the change, just save the Feature. When you are ready to continue the rollout, all you have to do is add more steps. Disable a Rule (Kill Switch) In some cases, you may want to disable a Feature entirely for all users as quickly as possible, regardless of rollout status, schedule, or Targeting Rules. This is where a killswitch comes in. A killswitch immediately turns off a Feature, sending all users to the default values, without requiring any code changes or deployments. This is particularly useful if you encounter a critical issue in production, such as a bug, performance problem, or negative user experience, and need to prevent further impact right away. Unlike stopping a rollout, which simply freezes the current percentage, a killswitch removes the Feature from all users currently receiving it. To use a killswitch, you can simply disable the Targeting Rule for the Environment from the dashboard and save your changes. The change will take effect immediately, overriding all Targeting Rules, schedules, and rollouts, and users will receive code defaults. You can re-enable the Feature at any time by turning the Targeting Rule back on. FAQ about Rollouts How often are rollouts evaluated / When does the rollout % update? Rollouts are calculated in real-time -- meaning that the rate of increase of the current % is based on the time between the start and end dates. How do rollouts actually work? The rollout of the Targeting Rule is deterministic based on an algorithm leveraging the User, Feature and Targeting Rule IDs. This effectively means that a user will be guaranteed to receive a Feature at a specific percentage point for a given Targeting Rule. If the rollout is higher than that percentage point, the user will receive the Feature, and if the rollout is lower than that percentage point, then the user will not receive the Feature. It doesn't matter how often the rollout changes. This logic applies to all users, and where each user's "percentage point" is randomly distributed. Example: Your Production environment is targeting all users and the rollout is at 30% but you find out that you have to rollback to 0% because of an issue. Once you roll out again to 30%, the 30% of users that were originally targeted are guaranteed to receive the Feature again. How do rollbacks actually work? Rollbacks work exactly the same way that rollouts work. The only difference being the start and end percentages that you set. Typically, you'd start with 100% of users and gradually rollback to 0% to phase out a Feature. Will a user receive a Feature right away once they qualify for the rollout? A User will qualify for the Feature on the first config request after they are part of the rollout percentage. Rollouts will not trigger a Realtime Update on the SDK. If a User meets the Targeting Rule's definition but does not qualify for the Feature by rollout, will they proceed to evaluate the next Targeting Rule? If a user qualifies for a Targeting Rule that has a rollout, and they have not yet received the rollout, the user may or may not proceed to the next Targeting Rule depending on whether you have Passthrough Rollouts enabled. Passthrough Rollouts ( effective for ALL DevCycle Projects - Date TBD ) Passthrough Rollouts will be the default behaviour for Targeting Rules moving forward. Projects created after May 22, 2024 will already have this enabled. For Projects created on or before this date, we have made Passthrough Rollouts for Targeting Rules available for opt-in , in Project Settings ahead of the switchover. If your team is actively using Scheduled Rollouts in your Targeting Rules, this change may affect how your Targeting Rules behave for your Features. We've put together resources to make this transition as smooth as possible for you. What are Passthrough Rollouts? Currently, any user that qualifies for a rule that contains a Scheduled Rollout, will be held on the rule and receive default values until the schedule or rollout has triggered. With Passthrough Rollouts , if a rollout or schedule hasn't been hit for a Targeting Rule, the platform will treat the rule as if it doesn't exist, regardless of whether the user qualifies for the rule or not. Essentially, users will not be "stuck" on the rule, and instead, will bypass the rule and continue evaluating the next rule(s). This is especially useful when you want users to receive a different Variation of your Feature until the rollout or schedule applies to them. Here is an example scenario of Passthrough Rollouts' expected behaviour: Let's pretend today's date is April 18th. In the screenshot below, given the scheduled date for the Targeting Rule #1 - Fall-through Example is in the future and has not happened yet, all users will pass through that rule and be evaluated against Targeting Rule #2 - Promotion and receive the Spin variation for the next week. Once April 26th arrives, users will now be evaluated against the first rule and be served the Base variation. Conversely, if Passthrough Rollouts were not enabled, All Users would be "stuck" on and only evaluated against Targeting Rule #1 and continue to receive the default value in code until April 26th. What do you need to know? May 22, 2024: Starting today, all existing projects will have a Passthrough Rollouts section in each Project's settings page. This will give you an option to enable this setting ahead of the switchover date. All new Projects created from this date forward, will have passthrough rollouts as the default behaviour. DATE TBD: All projects remaining will switchover to Passthrough Rollouts. If your team is leveraging a server-side SDK, your team must upgrade your SDK before this date, as Passthrough Rollouts require specific DevCycle Server SDK Versions to be deployed. What do you need to do? If your team is leveraging a server-side SDK , your team must upgrade your SDK as Passthrough Rollouts require specific DevCycle Server SDK Versions to be deployed (with the exception of the PHP SDK, which does not require an SDK update). Minimum versions: Python: 3.5.0 Java: 2.2.0 Dotnet (Local): 3.1.0 Node: 1.29.0 Ruby: 2.7.0 GO: 2.15.0 Nestjs: 0.7.0 Edit this page Last updated on Jan 9, 2026 Previous Random Variations Next Randomize using a Custom Property Scheduling a Feature Rollouts & Rollbacks Gradual Rollouts Multi-Step Rollouts Stopping a Rollout Disable a Rule (Kill Switch) FAQ about Rollouts Passthrough Rollouts ( effective for ALL DevCycle Projects - Date TBD ) What are Passthrough Rollouts? What do you need to know? What do you need to do? DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:33 |
https://docs.devcycle.com/integrations/vscode-extension | README | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page DevCycle VSCode Extension Extension Installation DevCycle extension can be installed directly within Visual Studio Code or via the Visual Studio Code Marketplace. Visual Studio Code Marketplace Visit the DevCycle Feature Flags Extension page at Visual Studio Marketplace. Click on the "Install" button. Within Visual Studio Code Search for "DevCycle Feature Flags" in the Extensions page. Click on the "Install" button. Post-installation, you can start utilizing the extension straightaway. No additional configuration is necessary. Feature Overview Current Features View All Feature Flags : The variable view in the extension displays a list of all variables existing within your code and your project. See Code Usages : The variable view also shows you where each of your DevCycle variables resides in your codebase, providing a convenient click-to-navigate feature. Understand Feature Status : Hovering over your DevCycle variables in your code brings up a card detailing information about the variable and the current status of the feature across environments. Requirements Before getting started with DevCycle, make sure you meet the following requirements: You need a DevCycle account. Sign up for a free account here (no credit card required). Extension Settings DevCycle extension contributes the following settings: Devcycle-feature-flags: Debug : Displays debug output for the extension, including what CLI commands are being executed. Default is off. Devcycle-feature-flags: Login On Workspace Open : Automatically logs into DevCycle when a configured workspace is opened. Default is on. Devcycle-feature-flags: Send Metrics : Allows DevCycle to send usage metrics. Default is off. Devcycle-feature-flags: Usages On Workspace Open : Automatically checks for code usages when a configured workspace is opened. Default is on. Upcoming Features We're excited about the future of DevCycle! Many advanced features are under development to further enhance the capabilities of the DevCycle extension. To stay updated on our progress, keep checking our GitHub repository and official website. Edit this page Extension Installation Visual Studio Code Marketplace Within Visual Studio Code Feature Overview Current Features Requirements Extension Settings Upcoming Features DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:33 |
https://securitylab.github.com/get-involved/ | Get Involved | GitHub Security Lab skip to content / Security Lab Research Advisories CodeQL Wall of Fame Resources Events Get Involved Resources Open Source Community Enterprise / Security Lab Research Advisories CodeQL Wall of Fame Resources Open Source Community Enterprise Events Get Involved Get involved Let’s keep the world's software safe, together. Be in the loop Hear the latest news from the Security Lab. We love to share what we do and discuss all things security. Follow us on Bluesky Follow us on Mastodon Follow us on LinkedIn Learn how to fish Practical tutorials, puzzles, and other challenges will take you through the process step by step. Go Capture the Flag Share the love Join us on the CodeQL forums if you have any questions, want to share your experience, or have any feedback for us. Say ‘hello’ in our forum Join us on Slack Latest events See all events November 13, 2024 EkoParty 2024: 20 Años! Buenos Aires, Argentina ¡GitHub se enorgullece de patrocinar EkoParty una vez más! Si estás en EkoParty, ¡pasa por el stand de GitHub para conocer a nuestros expertos! September 5, 2024 OrangeCon 2024 Amsterdam, Netherlands June 21, 2024 Play Secure Conference 2024 Virtual Play Secure is the intersection of play and security! This unique virtual conference is designed to delve into the world of gamification, exploring how play, games, and gamification can transform the landscape of security training and awareness. Join industry leaders, innovative game designers, and security experts as we embark on a journey to redefine the future of secure play. To keep this community open and welcoming, please read our Code of Conduct . Product Features Security Team Enterprise Customer stories The ReadME Project Pricing Resources Roadmap Compare GitHub Platform Developer API Partners Atom Electron GitHub Desktop Support Docs Community Forum Professional Services GitHub Skills Status Contact GitHub Company About Blog Careers Press Inclusion Social Impact Shop GitHub Inc. © 2024 Terms Privacy Sitemap What is Git? Manage Cookies Do not share my personal information | 2026-01-13T08:49:33 |
https://securitylab.github.com/advisories/GHSL-2025-105_vets-api/ | GHSL-2025-105: Code injection in vets-api | GitHub Security Lab skip to content / Security Lab Research Advisories CodeQL Wall of Fame Resources Events Get Involved Resources Open Source Community Enterprise / Security Lab Research Advisories CodeQL Wall of Fame Resources Open Source Community Enterprise Events Get Involved December 19, 2025 GHSL-2025-105: Code injection in vets-api Peter Stöckli Coordinated Disclosure Timeline 2025-08-13: Vulnerability was reported via GitHub’s private vulnerability reporting feature. 2025-08-13: Workflow was fixed. Summary A code injection vulnerability was identified in the then latest changeset of vets-api’s GitHub Actions workflow (ready_for_review.yml), which could have allowed unauthorized code execution during workflow runs. Project vets-api Tested Version The latest changeset at the moment of review Details Code injection in GitHub Actions ready_for_review.yml ( GHSL-2025-105 ) The GitHub action at .github/workflows/ready_for_review.yml executes user input. Below is the code snippet containing the vulnerability: echo "pr_branch=${{ github.head_ref }}" >> $GITHUB_OUTPUT ... HEAD_BRANCH="${{ github.event.workflow_run.head_branch }}" ... echo "pr_branch=${{ github.event.workflow_run.head_branch }}" >> $GITHUB_OUTPUT The user input ${{ github.head_ref }} and ${{ github.event.workflow_run.head_branch }} (the branch name) is directly evaluated in the run section, making it vulnerable to code injection. Trigger and Permissions The workflow is triggered by: pull_request (user controlled trigger) workflow_run (depends on workflows with user controlled triggers) The dependent workflows for the workflow_run trigger are: .github/workflows/audit_service_tags.yml (triggered by pull_request ) .github/workflows/check_codeowners.yml (triggered by pull_request ) .github/workflows/code_checks.yml (triggered by pull_request ) .github/workflows/codeql-analysis.yml (triggered by pull_request ) The vulnerable job grants permissions: write-all . Impact This issue may lead to code execution with high privileges. Credit This issue was discovered by CodeQL and an AI agent developed by the GitHub Security Lab and reported by GHSL team member @p- (Peter Stöckli) . Contact You can contact the GHSL team at securitylab@github.com , please include a reference to GHSL-2025-105 in any communication regarding this issue. Product Features Security Team Enterprise Customer stories The ReadME Project Pricing Resources Roadmap Compare GitHub Platform Developer API Partners Atom Electron GitHub Desktop Support Docs Community Forum Professional Services GitHub Skills Status Contact GitHub Company About Blog Careers Press Inclusion Social Impact Shop GitHub Inc. © 2024 Terms Privacy Sitemap What is Git? Manage Cookies Do not share my personal information | 2026-01-13T08:49:33 |
https://www.tech-reader.blog | Tech-Reader.blog Skip to main content Search This Blog Tech-Reader.blog Technology Learning Made Simple Pages Home Tech-Reader.com More… Posts The Secret Life of JavaScript: Identity Get link Facebook X Pinterest Email Other Apps - January 12, 2026   The Secret Life of JavaScript: Identity # javascript # coding # programming # software Why  this  is undefined. A visual guide to the "Left of the Dot" rule Timothy slumped into a chair at the main worktable, dropping his pen onto a piece of code. He looked exhausted. "I don't understand who I am anymore, Margaret," he muttered. Margaret paused her sorting and walked over. "That is a deep philosophical question, Timothy." "It’s not philosophy. It’s this function," he said, tapping the paper. "I wrote a  printName  function inside my  user  object. When I run it, it prints 'Timothy'. But when I pass that  exact same function  to a helper, it forgets who it is. It prints  undefined . It’s having an identity crisis." Margaret pulled a rolling chalkboard over to the table. She picked up a piece of chalk. "The function is not having a crisis," she said. "You are simply assuming that  Identity  ( this ) belongs to... Post a Comment Read more AWS DynamoDB ↔ Lambda Errors: A Fix-It Series Get link Facebook X Pinterest Email Other Apps - January 12, 2026   AWS DynamoDB ↔ Lambda Errors: A Fix-It Series # aws # dynamodb # lambda # devops A production-focused guide to the failure modes of event-driven state The Thesis This is not an introduction to AWS. This is not a reference manual. This is the guide to what happens when “correct” architecture meets production reality. When you connect  Amazon DynamoDB  to  AWS Lambda  at scale, you are no longer just writing code — you are operating a distributed system. Most tutorials show how to make it work. This series focuses on what breaks  after  everything appears to be working: duplicate writes, phantom retries, silent data corruption, and state drift that only shows up weeks later. This is an operator-grade Fix-It series about  events, retries, and data integrity . Who This Is For Builders  running event-driven workloads who need more than “at-least-once” explanations SREs and Architects  investigating why a Lambda ran six times despite a succe... Post a Comment Read more The AWS Cloudfront Fix-It Series Get link Facebook X Pinterest Email Other Apps - January 12, 2026   The AWS Cloudfront Fix-It Series # aws # cloudfront # devops # cloud A troubleshooting field guide for Amazon CloudFront AWS CloudFront is not a black box; it is a layered system of edges, caches, and origins. When it fails, it leaves specific signals—but you have to know where to look. This series moves beyond "try invalidating it" and provides a methodical approach to diagnosing and fixing the most common CloudFront failures. The Lineup Fix-It #1: 403, 404, and 502 — What CloudFront Is Really Telling You Decodes the three primary infrastructure signals to tell you exactly which layer (Edge, Origin, or Trust) is rejecting your request. Fix-It #2: “Why Didn’t My Change Apply?” — Caching, TTLs, and Propagation Reality Explains why valid configuration changes remain invisible, distinguishing between Edge caching, Browser caching, and the role of invalidations. Fix-It #3: TLS, ACM, and Certificate Mismatch Failures Solves the "us-east-1" requirement, CNAME circular d... Post a Comment Read more AWS CloudFront Error: Debugging CloudFront When You Can’t SSH Into Anything Get link Facebook X Pinterest Email Other Apps - January 12, 2026   AWS CloudFront Error: Debugging CloudFront When You Can’t SSH Into Anything # aws # cloudfront # devops # cloud How CloudFront failures can be diagnosed methodically using logs, metrics, and request signals when there is no server access and no single place to look Problem CloudFront is misbehaving, but there is nothing to log into. There is no SSH, no shell, no application process to tail. Requests fail, stall, or behave inconsistently, and it’s unclear where the problem actually lives. Clarifying the Issue Amazon CloudFront  is a control-plane–driven, edge-distributed system. That means: Failures rarely exist in one place Requests pass through multiple layers you don’t control Observability is  indirect  by design Debugging CloudFront is not about access. It is about signals. Every CloudFront problem leaves traces — just not where traditional server instincts expect them. Why It Matters When teams can’t “see” CloudFront, they tend to: Guess Redeploy Invalidate bl... Post a Comment Read more AWS CloudFront Error: Headers That Disappear, Reappear, or Mutate at the Edge Get link Facebook X Pinterest Email Other Apps - January 12, 2026   AWS CloudFront Error: Headers That Disappear, Reappear, or Mutate at the Edge # aws # cloudfront # devops # cloud How CloudFront requests work correctly at the origin but behave inconsistently at the edge due to header forwarding rules, cache keys, and CORS interactions Problem Requests served through  Amazon CloudFront  behave differently than requests sent directly to the origin. Expected headers are missing, unexpected headers appear, or responses vary unpredictably between users. CORS errors occur even though the origin appears correctly configured. Clarifying the Issue CloudFront does  not  forward all headers by default. Instead, CloudFront: Filters  headers based on the  Origin Request Policy Splits  cache entries based on the  Cache Policy Injects  its own headers (for example, geolocation and device metadata) This means CloudFront can legitimately return a response that  never hit your origin , even though the incoming re... Post a Comment Read more More posts Powered by Blogger Theme images by RBFried Copyright © 2023 Tech-Reader.blog All Rights Reserved Archive 2026 37 January 37 The Secret Life of JavaScript: Identity AWS DynamoDB ↔ Lambda Errors: A Fix-It Series The AWS Cloudfront Fix-It Series AWS CloudFront Error: Debugging CloudFront When Yo... AWS CloudFront Error: Headers That Disappear, Reap... The Secret Life of AWS: The Walled Garden The Secret Life of Go: Interfaces The Azure Blob Storage Trilogy Azure Blob Storage: Authentication, Access, and th... Azure Blob Storage: A Deeper Dive Into Architectur... Azure Blob Storage: The Cloud Primitive You End Up... The Secret Life of AWS: The Bottomless Basement AWS CloudFront Error: Performance & Latency Failur... AWS CloudFront Error: TLS, ACM, and Certificate Mi... AWS CloudFront Error: “Why Didn’t My Change Apply?... AWS CloudFront Error: 403, 404, and 502 — What Clo... The Secret Life of AWS: The Empty Room The Secret Life of Go: Testing AWS API Gateway Fix-It Vol.1: The Complete Trouble... AWS API Gateway Error: Custom Domain & Base Path M... The Secret Life of AWS: The Ring of Keys The Secret Life of Python: The Matryoshka Trap AWS API Gateway Error: Stage Drift & Deployment Co... AWS API Gateway Error: CORS Failures That Aren’t CORS The Secret Life of AWS: The Map of the World The Secret Life of Python: The Dangerous Reflection AWS API Gateway Error: Custom Authorizers Masking ... AWS API Gateway Error: Lambda Integration Permissi... The Secret Life of JavaScript: Illusions AWS API Error: REST API vs HTTP API — Why the Same... AWS API Gateway Error: “403 Forbidden” vs. “Missin... The Secret Life of JavaScript: Memories The Complete SQS Troubleshooting Guide (The Most C... AWS SQS Error: SQS Redrive Back to Source AWS Error: SQS Long Polling vs Short Polling AWS SQS Error: SQS Message Retention Period AWS SQS Error: SQS Dead-Letter Queue (DLQ) Redrive... 2025 822 December 60 November 68 October 111 September 98 August 54 July 35 June 30 May 48 April 77 March 101 February 78 January 62 2024 360 December 40 November 43 October 53 September 36 August 50 July 64 June 47 May 1 March 23 February 3 2023 226 July 5 June 20 May 10 April 19 March 30 February 44 January 98 Show more Show less Report Abuse | 2026-01-13T08:49:33 |
https://docs.devcycle.com/examples | DevCycle Example Apps | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Examples On this page DevCycle Example Apps Welcome to the Example Apps page, which showcases example applications using the DevCycle SDKs. The goal of this page is to provide developers with a comprehensive collection of example applications that demonstrate how to utilize DevCycle's SDKs with a variety of programming languages and frameworks. Client side JavaScript React Next.js - App Router Vue JS MacOS tvOS Flutter Roku Server Side Local Bucketing ( See here for more explanation ) Node.js Go PHP Python Ruby Java .NET NestJS Cloud Bucketing ( See here for more explanation ) Node.js Go Ruby Java .NET Mobile iOS (Objective C) iOS (Swift) Android (Java) Android (Kotlin) Edit this page Last updated on Jan 9, 2026 Previous Webhooks Client side Server Side Local Bucketing Cloud Bucketing Mobile DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:33 |
https://popcorn.forem.com/popcorn_tv/ramy-youssef-exits-will-ferrells-netflix-golf-comedy-over-creative-differences-molly-shannon-5ak8 | Ramy Youssef Exits Will Ferrell's Netflix Golf Comedy Over Creative Differences; Molly Shannon Joins Cast - Popcorn Movies and TV Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Popcorn Movies and TV Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse TV News Posted on Aug 12, 2025 Ramy Youssef Exits Will Ferrell's Netflix Golf Comedy Over Creative Differences; Molly Shannon Joins Cast # marketing # offtopic # filmindustry # studios Ramy Youssef Exits Will Ferrell Netflix Comedy; Molly Shannon JoinsRamy Youssef Exits Will Ferrell Netflix Comedy; Molly Shannon Joins Ramy Youssef and Josh Rabinowitz exited Will Ferrell's upcoming Netflix comedy over creative differences. Separately, Molly Shannon has been cast. variety.com Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse TV News Follow Joined Jun 22, 2025 More from TV News Gina Carano, Disney Settle Legal Dispute Over ‘Mandalorian' Firing # filmindustry # marketing # agencies # offtopic ‘South Park' Doubles Down on Kristi Noem With Paramount+ End Credits Scene Featuring Her on Shooting Spree at a Pet Store # marketing # analysis # filmindustry # offtopic Stephen Colbert To Guest Star As a Late-Night Host In An Upcoming Episode of ‘Elsbeth' # accessibilitymedia # marketing # filmindustry # distribution 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Popcorn Movies and TV — Movie and TV enthusiasm, criticism and everything in-between. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Popcorn Movies and TV © 2016 - 2026. Let's watch something great! Log in Create account | 2026-01-13T08:49:33 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#__docusaurus_skipToContent_fallback | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:33 |
https://popcorn.forem.com/popcorn_movies/lionsgate-posts-106-million-quarterly-loss-after-ballerina-disappoints-5a1l | Lionsgate Posts $10.6 Million Quarterly Loss After ‘Ballerina' Disappoints - Popcorn Movies and TV Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Popcorn Movies and TV Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Movie News Posted on Aug 8, 2025 Lionsgate Posts $10.6 Million Quarterly Loss After ‘Ballerina' Disappoints # marketing # accessibilitymedia # agencies # offtopic Lionsgate Posts $94 Million Quarterly Loss Lionsgate Posts $94 Million Quarterly Loss Lionsgate posted a $94 million quarterly loss after 'Ballerina' disappointed at the box office. variety.com Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Movie News Follow Joined Jun 22, 2025 More from Movie News CinemaSins: Everything Wrong With Austin Powers in Goldmember in 19 Minutes Or Less # movies # reviews # analysis # marketing Mr Sunday Movies: The Judge Dredd Duology - Caravan Of Garbage # movies # reviews # analysis # marketing CinemaSins: Everything Wrong With Weapons In 21 Minutes Or Less # movies # reviews # analysis # marketing 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Popcorn Movies and TV — Movie and TV enthusiasm, criticism and everything in-between. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Popcorn Movies and TV © 2016 - 2026. Let's watch something great! Log in Create account | 2026-01-13T08:49:33 |
https://docs.devcycle.com/platform/extras/custom-domains | Custom Domains | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Testing and QA Extras Custom Domains Feature Opt-In Self-Hosted Feature Flags with DevCycle Webhooks Examples Platform Extras Custom Domains On this page Custom Domains When using client-side SDKs, particularly web client SDKs, there is the potential for ad blockers and browser privacy features to block requests and third-party cookies. Custom Domains with DevCycle ensures all cookies and requests used are first-party and will not be blocked by ensuring requests are sent through your recognized domain. info Custom Domains are a business and enterprise feature. To learn more, read about our pricing . To upgrade your plan, please contact your Account Manager or our Sales team. Requirements Custom Domains will require some back and forth setup on both your end as well as DevCycle's. A DNS CNAME needs to be created to leverage this feature. To start the setup process, please reach out to your account representative or to [email protected] and provide the following information: Your desired CNAME domain with a maximum of one subdomain (e.g. api-alias.your-domain.com). Avoid text that may be blocked by adblockers. Your desired SSL certificate provider from one of the three providers if required - SSL.com, Google Trust Services, Let's Encrypt. We will select one at random if you do not require a specific provider. Your DevCycle Services that will use the CNAME (e.g. Client SDKs, Server SDKs, Mobile SDKs) Once DevCycle receives this information, we can provide you with next steps. A brief outline of the process is shown below and requires involvement from both parties. Please continue to refer to our communications for the correct next steps. Setup Process Identifying a Hostname : The first step involves identifying a hostname to use as the CNAME for DevCycle's endpoint. Provide this to DevCycle on your request to enable Custom Domains. The hostname should look something like this https://api-alias.your-domain.com . We do not support two or more subdomains in the hostname (e.g. a.b.c.com is not supported). If there is more than one service in use, each service will need a unique CNAME. This is also true for using DevCycle on multiple domains. Each domain needs its own CNAME. DNS Validation : Once the setup is complete, two DNS records will be provided by DevCycle and you will need to add those records to your DNS provider (TXT validation records). The first DNS record will be a TXT verification record to ensure that you own the domain that you are asking DevCycle to use as a custom hostname. The second DNS record will be a TXT verification record to ensure that you have permission to create an SSL certificate for said domain. This record will conflict with any existing A/AAAA or CNAME records on the hostname and require them to be removed before adding the verification record. Once these records have been added, please let DevCycle know. DevCycle Additional Setup : Once validation is complete and DevCycle has confirmed the records are set properly, there may be an extra step involved here with DevCycle depending on your SDK configuration. DevCycle will let you know if this is needed. Creating a CNAME : Once all steps are complete, DevCycle will send the details for the DNS CNAME. Once added, the service will be immediately available at the given hostname. SDK Implementation : Once you have completed the steps above to create a CNAME, modify your existing SDK initialization to include the apiProxyURL initialization option. See below. SDK Implementation In order to use the Custom Domain, you'll have to point the SDK requests to the newly created CNAME domain. JavaScript SDK Add the apiProxyURL option and your CNAME domains as per the JS SDK Initialization Options . const devcycleClient = initializeDevCycle ( '<DEVCYCLE_CLIENT_SDK_KEY>' , user , { apiProxyURL : 'https://api-alias.your-domain.com' , } ) iOS SDK Add the apiProxyURL option and your CNAME domains as per the iOS SDK DevCycle Options Builder . let options = DevCycleOptions . builder ( ) . apiProxyURL ( "https://api-alias.your-domain.com" ) . build ( ) let client = try ? DevCycleClient . builder ( ) . sdkKey ( "<DEVCYCLE_SDK_KEY>" ) . user ( user ! ) . options ( options ) . build ( onInitialized : nil ) After completing the steps above, users should be able to freely maneuver around AdBlockers and prevent them from blocking requests to our API servers and our SDK. If you have any questions regarding this process, please reach out to our support team. Edit this page Last updated on Jan 9, 2026 Previous Self-Targeting Next Feature Opt-In Requirements Setup Process SDK Implementation JavaScript SDK iOS SDK DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://opensource.org/blog/open-letter-harnessing-open-source-ai-to-advance-digital-sovereignty | Open letter: Harnessing open source AI to advance digital sovereignty – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu November 20, 2025 News Jordan Maris Open letter: Harnessing open source AI to advance digital sovereignty November 13, 2025 Dear President Macron, Dear Chancellor Merz, Dear President von der Leyen, Europe is at a crossroads. The Summit on European Digital Sovereignty marks an important milestone for the EU and its member states in aligning on a shared strategy for achieving real and lasting European digital sovereignty. As the EU pursues the goal of digital sovereignty, we urge you to harness open source — that is, technology that is free to use, inspect, adapt, and share — as a key enabler of this strategy. Europe cannot buy sovereignty off a shelf, it has to build it. In an age of geopolitical volatility and rapid innovation Europe must play to its strengths, including world-leading researchers and a rich history of open source development. It faces a choice: use these strengths to carve out its distinct place in the global AI ecosystem or settle for copying the playbooks of already dominant actors. At their heart, closed systems create dependency, open systems create capacity . Investment into the full open source AI stack, from AI models to data and software tooling, is a strategic lever. If digital sovereignty means creating a Europe that is resilient and benefits from choice, security, and self-determination, then open source is a critical force multiplier that enables Europe to do more with less. Open source AI, and open source technology more broadly, is not just a strategic asset benefiting governments, businesses, and people. If underpinned by a clear commitment to values that are at the heart of the European project — including cultural diversity, fundamental rights, environmental sustainability, and people’s privacy and security — open source can help embed these into the technologies that will shape our future. We, the undersigned, represent a diverse coalition of organisations across industry, the open source community, and civil society — many of whom build and maintain leading-edge open source technology. With this letter, we put forward a concrete plan to ensure Europe’s technological future is open, trusted, and its own. The importance of open source in achieving digital sovereignty Boosting and utilising the open source AI ecosystem will support the EU and its member states in strengthening their digital sovereignty in four key ways: Reduce Dependency and Increase Strategic Autonomy: Open source technology enables European governments and enterprises to freely use, adapt, and host technology on their own terms, using infrastructure of their own choosing. By making it easier to switch and by fostering more competition, this prevents vendor lock-in, increases choice, and reduces dependencies throughout the technological supply chain. Boost European Capability and Competitiveness: Open source compounds progress and boosts European innovators’ productivity by providing them with reusable building blocks that they can use and tailor to their needs, without having to reinvent the wheel. It helps EU startups, SMEs, and researchers go further, faster, rapidly delivering innovative technology. Build Global Leadership and Influence: Open source enables Europe to collaborate globally while retaining autonomy. The technology can be developed and maintained across borders, harnessing expertise from around the world without requiring trust to verify its security. Investing in open source AI can also strengthen partnerships with like-minded nations — all while influencing global standards, facilitating interoperability, and making it easier for others to build on European technology. Promote European Values and Cultural Diversity: Open source and open data can safeguard linguistic and cultural diversity by making European language and cultural data more broadly available and by enabling local communities to adapt AI to their needs and context. It is also inherently more transparent and enables independent audits — key to AI’s safety and security. Five actions to harness the potential of open source AI for Europe’s ambitions To leverage the value of open source AI for the EU’s ambitions on AI and digital sovereignty, we call on Member State governments and the European institutions to champion open source through the following initial actions: Leverage the public sector’s buying power to scale and ensure the sustainability of open source AI initiatives: Improve tendering processes and templates to better account for open source technologies and reduce administrative obstacles for open source vendors, rather than structurally favoring proprietary technology. Consider the benefits of open source with regard to sovereignty, total cost, and interoperability as part of the procurement process. Mobilise funding to incubate, develop, and maintain an open source AI stack: Create designated funding lines and incentives to support the development and maintenance of critical and high-impact open source AI and other foundational open source technologies, including through the creation of an EU Sovereign Tech Fund , the European Competitiveness Fund, and national funding instruments. Facilitate access to computing infrastructure for open source AI research and development: Reserve capacity and facilitate reliable, unbureaucratic access to publicly funded compute, for example through AI factories, for open source and public interest AI research, development, and deployment. Unlock data for open source AI development while protecting privacy and other rights: Remove barriers to access and reuse of publicly funded, public domain, or other non-sensitive public sector data for open source AI developers. Accelerate the deployment of data sharing mechanisms and infrastructure, such as Common European Data Spaces. Build capacity in the public and private sectors to leverage the power of open source: Mainstream support for open source AI developers and users within existing governance mechanisms, including European Digital Innovation Hubs and supervisory authorities. Raise awareness and foster sharing of best practices around the use of open source AI. We urge the EU’s leaders to use this five-point plan as a pathway to build a future it can trust, shape and truly call its own. Sincerely, Mozilla ADAPT Centre (Trinity College Dublin) Mistral AI AlgorithmWatch Nextcloud GmbH APELL – The European Open Source Software Business Association Open Future Bertelsmann Stiftung Open Knowledge Foundation Black Forest Labs Open Knowledge Foundation Deutschland Common Crawl Foundation Open Markets Institute COMMUNIA Open Source Business Alliance (OSBA) Creative Commons Open Source Initiative (OSI) Demos Open-Xchange Digital Intimacy Coalition OpenMined Ecosia GmbH Pleias Element Probabl EleutherAI Public AI Future of Tech Institute PublicSpaces German AI Association Red Hat Ltd. Hugging Face Renaissance Numérique iconomy Stichting Code for NL Innovate Europe Foundation (IE.F) Waag Futurelab Kyutai Wikimedia Deutschland e. V. LAION Wikimedia Europe LINAGORA Wikimédia France Metagov Xnet, Institute for Democratic Digitalisation This letter was prepared in collaboration with Mozilla and other organisations. Links within the letter were added by the OSI after sending and for informational purposes. Sustaining Open Source: The Next 25 Years Depend on What We Do Together Now Open Source: A global commons to enable digital sovereignty Keep up with Open Source Please leave this field empty. Δ We’ll never share your details and you can unsubscribe with a click! Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:49:34 |
https://dev.to/ali_algmass/multi-dimensional-arrays-row-major-order-a-deep-dive-3b2e | Multi-dimensional Arrays & Row-major Order: A Deep Dive - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse ali ehab algmass Posted on Jan 12 Multi-dimensional Arrays & Row-major Order: A Deep Dive # programming # computerscience # learning # webdev Let me explain multi-dimensional arrays and row-major ordering from the ground up, covering memory layout, addressing, and low-level implementation details. 1. Understanding Multi-dimensional Arrays Conceptual vs Physical Reality Conceptually , when you declare: int matrix [ 3 ][ 4 ]; Enter fullscreen mode Exit fullscreen mode You think of a 2D grid: [0][0] [0][1] [0][2] [0][3] [1][0] [1][1] [1][2] [1][3] [2][0] [2][1] [2][2] [2][3] Enter fullscreen mode Exit fullscreen mode Physically , memory is linear (one-dimensional). The CPU can only access memory sequentially through addresses. Multi-dimensional arrays are an abstraction that the compiler maps to linear memory. 2. Row-major Order Explained Row-major order is the strategy for mapping multi-dimensional indices to a linear memory address. Elements are stored row by row . Memory Layout Example For int matrix[3][4] (3 rows, 4 columns): Memory Address: Value: Logical Position: 0x1000 matrix[0][0] 0x1004 matrix[0][1] ← Row 0 stored contiguously 0x1008 matrix[0][2] 0x100C matrix[0][3] 0x1010 matrix[1][0] ← Then Row 1 0x1014 matrix[1][1] 0x1018 matrix[1][2] 0x101C matrix[1][3] 0x1020 matrix[2][0] ← Finally Row 2 0x1024 matrix[2][1] 0x1028 matrix[2][2] 0x102C matrix[2][3] Enter fullscreen mode Exit fullscreen mode Notice: Rightmost index changes fastest when traversing memory sequentially. 3. Address Calculation Formula For 2D Arrays Given: type array[ROWS][COLS] To access array[i][j] : address = base_address + (i * COLS + j) * sizeof(type) Enter fullscreen mode Exit fullscreen mode Breakdown: i * COLS : Skip i complete rows (each row has COLS elements) + j : Move j positions within the current row * sizeof(type) : Scale by element size (bytes) Example Calculation For int matrix[3][4] at base address 0x1000 , accessing matrix[2][3] : address = 0x1000 + (2 * 4 + 3) * 4 = 0x1000 + (8 + 3) * 4 = 0x1000 + 11 * 4 = 0x1000 + 44 = 0x102C Enter fullscreen mode Exit fullscreen mode For 3D Arrays Given: type array[D1][D2][D3] To access array[i][j][k] : address = base + (i * D2 * D3 + j * D3 + k) * sizeof(type) Enter fullscreen mode Exit fullscreen mode Logic: i * D2 * D3 : Skip i complete "planes" (each plane is D2×D3 elements) j * D3 : Skip j complete rows within the current plane k : Position within the current row For N-dimensional Arrays General formula for array[i₁][i₂][i₃]...[iₙ] with dimensions [D₁][D₂][D₃]...[Dₙ] : offset = i₁ * (D₂ * D₃ * ... * Dₙ) + i₂ * (D₃ * D₄ * ... * Dₙ) + i₃ * (D₄ * D₅ * ... * Dₙ) + ... iₙ₋₁ * Dₙ + iₙ address = base + offset * sizeof(type) Enter fullscreen mode Exit fullscreen mode 4. Compiler Implementation Details How C/C++ Handles Multi-dimensional Arrays When you write: int arr [ 3 ][ 4 ][ 5 ]; int x = arr [ 1 ][ 2 ][ 3 ]; Enter fullscreen mode Exit fullscreen mode The compiler translates this to: int x = * ( arr + ( 1 * 4 * 5 + 2 * 5 + 3 )); Enter fullscreen mode Exit fullscreen mode Pointer Arithmetic Multi-dimensional arrays decay to pointers in interesting ways: int arr [ 3 ][ 4 ]; Enter fullscreen mode Exit fullscreen mode arr has type int (*)[4] (pointer to array of 4 ints) arr[i] has type int * (pointer to int) arr[i][j] has type int (actual value) What happens with arr + 1 ? It advances by the size of one complete row (4 ints = 16 bytes if int is 4 bytes) Points to arr[1][0] What happens with *(arr + 1) + 2 ? *(arr + 1) gives you arr[1] (a pointer to the first element of row 1) Adding 2 advances by 2 ints Points to arr[1][2] Assembly Level (x86-64 Example) For arr[i][j] where arr is int[ROWS][COLS] : ; Assume: base address in RAX, i in RBX, j in RCX mov rdx, rbx ; rdx = i imul rdx, COLS ; rdx = i * COLS add rdx, rcx ; rdx = i * COLS + j shl rdx, 2 ; rdx = (i * COLS + j) * 4 (multiply by sizeof(int)) add rdx, rax ; rdx = base + offset mov eax, [rdx] ; load the value Enter fullscreen mode Exit fullscreen mode Modern compilers optimize this heavily using LEA (Load Effective Address): lea rdx, [rbx + rbx*4] ; rdx = i * 5 (if COLS=5) lea rdx, [rdx*4 + rax] ; combine scaling and base mov eax, [rdx + rcx*4] ; load arr[i][j] Enter fullscreen mode Exit fullscreen mode 5. Row-major vs Column-major Order Row-major (C, C++, Java, Python NumPy default) For arr[3][4]: Storage order: [0,0] [0,1] [0,2] [0,3] [1,0] [1,1] ... Enter fullscreen mode Exit fullscreen mode Column-major (Fortran, MATLAB, R, Julia) For arr[3][4]: Storage order: [0,0] [1,0] [2,0] [0,1] [1,1] [2,1] ... Enter fullscreen mode Exit fullscreen mode Column-major formula for array[i][j] in dimensions [ROWS][COLS] : address = base + (j * ROWS + i) * sizeof(type) Enter fullscreen mode Exit fullscreen mode Performance Implications Cache locality matters! Modern CPUs fetch memory in cache lines (typically 64 bytes). Row-major traversal (optimal in C): for ( int i = 0 ; i < ROWS ; i ++ ) { for ( int j = 0 ; j < COLS ; j ++ ) { process ( arr [ i ][ j ]); // Sequential memory access } } Enter fullscreen mode Exit fullscreen mode Column-major traversal (suboptimal in C): for ( int j = 0 ; j < COLS ; j ++ ) { for ( int i = 0 ; i < ROWS ; i ++ ) { process ( arr [ i ][ j ]); // Strided access, cache misses } } Enter fullscreen mode Exit fullscreen mode 6. Memory Layout Deep Dive Alignment and Padding Arrays are typically aligned to their element's alignment requirement: struct Data { char c ; // 1 byte int arr [ 2 ][ 3 ]; // Starts at offset 4 (aligned to 4-byte boundary) }; Enter fullscreen mode Exit fullscreen mode Array of Arrays vs Array of Pointers True 2D array: int arr [ 3 ][ 4 ]; // Contiguous 48 bytes (3*4*4) Enter fullscreen mode Exit fullscreen mode Array of pointers (simulated 2D): int * arr [ 3 ]; arr [ 0 ] = malloc ( 4 * sizeof ( int )); arr [ 1 ] = malloc ( 4 * sizeof ( int )); arr [ 2 ] = malloc ( 4 * sizeof ( int )); Enter fullscreen mode Exit fullscreen mode These look similar but have completely different memory layouts: True 2D: One contiguous block Pointer array: Non-contiguous, each row can be anywhere in memory True 2D: Faster, better cache locality Pointer array: Flexible (rows can have different sizes), fragmented 7. Practical Example with Memory Dump #include <stdio.h> int main () { int arr [ 2 ][ 3 ] = { { 1 , 2 , 3 }, { 4 , 5 , 6 } }; printf ( "Base address: %p \n " , ( void * ) arr ); for ( int i = 0 ; i < 2 ; i ++ ) { for ( int j = 0 ; j < 3 ; j ++ ) { printf ( "arr[%d][%d] = %d at address %p \n " , i , j , arr [ i ][ j ], ( void * ) & arr [ i ][ j ]); } } // Treating as 1D array int * flat = ( int * ) arr ; printf ( " \n As flat array: \n " ); for ( int k = 0 ; k < 6 ; k ++ ) { printf ( "flat[%d] = %d at address %p \n " , k , flat [ k ], ( void * ) & flat [ k ]); } return 0 ; } Enter fullscreen mode Exit fullscreen mode Output (example): Base address: 0x7ffc8b3e1a40 arr[0][0] = 1 at address 0x7ffc8b3e1a40 arr[0][1] = 2 at address 0x7ffc8b3e1a44 arr[0][2] = 3 at address 0x7ffc8b3e1a48 arr[1][0] = 4 at address 0x7ffc8b3e1a4c arr[1][1] = 5 at address 0x7ffc8b3e1a50 arr[1][2] = 6 at address 0x7ffc8b3e1a54 Enter fullscreen mode Exit fullscreen mode Notice addresses increment by 4 (sizeof(int)) sequentially in row-major order. 8. Dynamic Multi-dimensional Arrays Method 1: Single malloc with manual indexing int rows = 3 , cols = 4 ; int * arr = malloc ( rows * cols * sizeof ( int )); // Access arr[i][j]: int value = arr [ i * cols + j ]; Enter fullscreen mode Exit fullscreen mode Method 2: Array of pointers int ** arr = malloc ( rows * sizeof ( int * )); for ( int i = 0 ; i < rows ; i ++ ) { arr [ i ] = malloc ( cols * sizeof ( int )); } // Access naturally: arr[i][j] Enter fullscreen mode Exit fullscreen mode Method 3: Contiguous with pointer array (best of both) int ** arr = malloc ( rows * sizeof ( int * )); arr [ 0 ] = malloc ( rows * cols * sizeof ( int )); for ( int i = 1 ; i < rows ; i ++ ) { arr [ i ] = arr [ 0 ] + i * cols ; } // Cleanup: free ( arr [ 0 ]); free ( arr ); Enter fullscreen mode Exit fullscreen mode 9. Hardware Considerations CPU Cache Behavior Modern CPUs have hierarchical caches (L1, L2, L3). Sequential access patterns maximize cache hit rates. Cache line example (64 bytes): If int is 4 bytes, one cache line holds 16 ints. Accessing arr[0][0] loads arr[0][0] through arr[0][15] into cache. Enter fullscreen mode Exit fullscreen mode TLB (Translation Lookaside Buffer) The TLB caches virtual-to-physical address translations. Strided access patterns can cause TLB thrashing. Prefetching Modern CPUs detect sequential access patterns and prefetch upcoming cache lines. Row-major traversal in row-major storage enables this optimization. 10. Summary Key Takeaways: Multi-dimensional arrays are linearized in memory Row-major order : rightmost index varies fastest Address formula : base + (i * COLS + j) * sizeof(type) for 2D Traversal matters : iterate in storage order for performance True arrays vs pointer arrays : different memory layouts, different trade-offs Compiler magic : translates arr[i][j] to pointer arithmetic automatically Cache locality : sequential access patterns are 10-100x faster than random access Understanding these low-level details helps you write faster code, debug memory issues, and interface with hardware or other languages effectively. Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse ali ehab algmass Follow Software Engineer Joined Jan 9, 2026 More from ali ehab algmass Dynamic Arrays: Low-Level Implementation & Amortized Analysis # algorithms # computerscience # performance Contiguous Memory & Cache Locality # algorithms # computerscience # performance Memory Layout: Heap vs Stack # computerscience # programming # architecture # learning 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://securitylab.github.com/advisories/GHSL-2025-110_openlibrary/ | GHSL-2025-110: Cross-site scripting (XSS) in OpenLibrary barcode scanner | GitHub Security Lab skip to content / Security Lab Research Advisories CodeQL Wall of Fame Resources Events Get Involved Resources Open Source Community Enterprise / Security Lab Research Advisories CodeQL Wall of Fame Resources Open Source Community Enterprise Events Get Involved December 4, 2025 GHSL-2025-110: Cross-site scripting (XSS) in OpenLibrary barcode scanner Peter Stöckli Coordinated Disclosure Timeline 2025-09-08: Reported via PVR 2025-09-10: Issue was fixed and deployed Summary The OpenLibrary project was affected by a cross-site scripting (XSS) vulnerability (GHSL-2025-110) in the barcode scanner feature, which could allow an attacker to execute malicious scripts in the context of a user’s browser. Project openlibrary Tested Version deploy-2025-08-12-at-22-48 Details Cross-site scripting vulnerability in barcode scanner ( GHSL-2025-110 ) The OpenLibrary project contains a reflected cross-site scripting (XSS) vulnerability in the submitISBN function. An attacker can specify a malicious returnTo query parameter to trigger the vulnerability: returnTo : new URLSearchParams ( location . search ). get ( ' returnTo ' ), which will be assigned to the location sink in the submitISBN function: submitISBN ( isbn , tentativeCoverUrl ) { if ( isbn === this . lastISBN ) return ; if ( this . seenISBN . has ( isbn )) return ; if ( this . returnTo ) { location = this . returnTo . replace ( ' $$$ ' , isbn ); } this . isbnList . unshift ({ isbn : isbn , cover : tentativeCoverUrl }); this . seenISBN . add ( isbn ); }, If a JavaScript URL is passed to the returnTo parameter the attacker provided JavaScript will be executed after the user scanned an ISBN. This vulnerability was discovered with the help of CodeQL’s Client-side cross-site scripting query. Impact This issue may lead to Information Disclosure and could potentially be used to perform different actions on behalf of a user. CWEs CWE-79: Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’) Credit This issue was discovered by CodeQL and an AI agent developed by the GitHub Security Lab and reported by GHSL team member @p- (Peter Stöckli) . Contact You can contact the GHSL team at securitylab@github.com , please include a reference to GHSL-2025-110 in any communication regarding this issue. Product Features Security Team Enterprise Customer stories The ReadME Project Pricing Resources Roadmap Compare GitHub Platform Developer API Partners Atom Electron GitHub Desktop Support Docs Community Forum Professional Services GitHub Skills Status Contact GitHub Company About Blog Careers Press Inclusion Social Impact Shop GitHub Inc. © 2024 Terms Privacy Sitemap What is Git? Manage Cookies Do not share my personal information | 2026-01-13T08:49:34 |
https://dev.to/fosres/master-iptables-security-4-production-ready-firewall-scenarios-860#comments | Week 4 Firewall Labs: 4 Production-Ready Firewall Scenarios with iptables - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse fosres Posted on Jan 12 Week 4 Firewall Labs: 4 Production-Ready Firewall Scenarios with iptables # security # linux # networking # cybersecurity Introduction Understanding iptables is a fundamental skill for Security Engineers, System Administrators, and DevOps professionals. Yet most engineers learn iptables through toy examples that don't reflect real-world complexity. This article presents four production-grade security scenarios that will test your understanding of: Stateful firewalls and connection tracking NAT configurations (DNAT, SNAT, MASQUERADE) Defense-in-depth security controls Attack surface reduction through network segmentation Security logging and monitoring These labs are designed to prepare you for actual Security Engineering interviews and on-the-job firewall configuration. Each scenario includes detailed network diagrams, specific requirements, and security constraints you'd encounter in production environments. Time commitment: 5-7 hours total for all scenarios Difficulty: Intermediate to Advanced Prerequisites: Basic understanding of TCP/IP, Linux command line, and iptables syntax Sources & References These labs are based on industry-standard security engineering practices and curriculum materials: Grace Nolan's Security Engineering Notes - github.com/gracenolan/Notes - Comprehensive security interview preparation resource Complete 48-Week Security Engineering Curriculum (Pages 13-14) - Networking fundamentals and firewall configuration methodology All exercises follow production security best practices for enterprise firewall configurations. Scenario 1: Startup Web Application Firewall Difficulty: ⭐⭐☆☆☆ (Intermediate) Time estimate: 60-90 minutes You are the first Security Engineer at a startup. The engineering team has deployed their web application and asks you to configure the server's firewall. Network Diagram INTERNET │ │ │ ┌───────────────────┴───────────────────┐ │ │ │ │ ┌───────┴───────┐ ┌───────┴───────┐ │ Legitimate │ │ Attackers │ │ Users │ │ (anywhere) │ │ │ │ │ └───────┬───────┘ └───────┬───────┘ │ │ │ │ └───────────────────┬───────────────────┘ │ │ ┌────────┴────────┐ │ │ │ Web Server │ │ │ │ 104.196.45.120 │ │ │ │ Services: │ │ - HTTPS (443) │ │ - SSH (22) │ │ │ │ eth0 (public) │ │ │ └─────────────────┘ Enter fullscreen mode Exit fullscreen mode Requirements The web application must be accessible via HTTPS from anywhere on the internet SSH must only be accessible from the CTO's home IP: 73.189.45.22 The server must be able to resolve DNS to function properly The server must be able to download security updates from Ubuntu repositories Protect SSH from brute force attacks (max 4 attempts per minute) Drop all other inbound traffic Log dropped packets for security monitoring Your Task Write a complete iptables firewall configuration for this server. Include comments explaining each rule. Hint: Remember that your server needs to initiate outbound connections for DNS and package updates. Don't forget the loopback interface! Scenario 2: Corporate Network with DMZ Difficulty: ⭐⭐⭐⭐☆ (Advanced) Time estimate: 2-3 hours You've been hired as a Security Engineer at a mid-size company. They have a standard three-tier network architecture and need you to configure the firewall that sits between all three zones. Network Diagram INTERNET │ │ ┌────────┴────────┐ │ ISP Router │ │ (not managed) │ └────────┬────────┘ │ │ 203.0.113.1 (gateway) │ ┌─────────────────────────────────────────────────────────────────────────────────────┐ │ │ │ FIREWALL │ │ │ │ eth0 (WAN) eth1 (DMZ) eth2 (LAN) │ │ 203.0.113.10 10.0.1.1 10.0.0.1 │ │ │ └─────────┬─────────────────────────────┬─────────────────────────────┬───────────────┘ │ │ │ │ │ │ │ ┌────────┴────────┐ ┌────────┴────────┐ │ │ DMZ Network │ │ LAN Network │ │ │ 10.0.1.0/24 │ │ 10.0.0.0/24 │ │ └────────┬────────┘ └────────┬────────┘ │ │ │ │ ┌─────────────┼─────────────┐ │ │ │ │ │ │ │ ┌──────┴──────┐ ┌────┴────┐ ┌──────┴──────┐ ┌──────┴──────┐ │ │ Web Server │ │ Mail │ │ DNS Server │ │ Employee │ │ │ 10.0.1.10 │ │ Server │ │ 10.0.1.30 │ │ Workstations│ │ │ │ │10.0.1.20│ │ │ │10.0.0.50-200│ │ │ HTTPS: 443 │ │ │ │ DNS: 53 │ │ │ │ │ HTTP: 80 │ │SMTP: 25 │ │ │ │ │ │ └─────────────┘ │IMAPS:993│ └─────────────┘ └─────────────┘ │ └─────────┘ │ │ ┌──────┴──────┐ │ Admin VPN │ │ Endpoint │ │ │ │ 198.51.100.50│ │ │ │ (needs SSH │ │ to all DMZ │ │ servers) │ └─────────────┘ Enter fullscreen mode Exit fullscreen mode Traffic Flow Requirements Source Destination Service Port(s) Allow? Internet Web Server HTTPS 443 Yes Internet Web Server HTTP 80 Yes (redirect to HTTPS) Internet Mail Server SMTP 25 Yes Internet Mail Server IMAPS 993 Yes Internet DNS Server DNS 53/udp, 53/tcp Yes Admin VPN (198.51.100.50) All DMZ Servers SSH 22 Yes Employee Workstations Internet HTTP/HTTPS 80, 443 Yes Employee Workstations Internet DNS 53 Yes DMZ Servers Internet DNS 53 Yes (for updates) DMZ Servers Internet HTTP/HTTPS 80, 443 Yes (for updates) Any Any ICMP ping - Rate limited Everything else - - - DROP and LOG Security Requirements Brute Force Protection: SSH must be protected against brute force (max 5 attempts per 60 seconds per source IP) Port Scan Detection: Block packets with invalid TCP flag combinations (NULL, XMAS, SYN+FIN) SYN Flood Protection: Rate limit incoming SYN packets to 50/second Connection Limits: No single IP can have more than 50 concurrent connections to any server Logging: All dropped traffic must be logged with appropriate prefixes NAT: External users access DMZ services via the firewall's public IP (203.0.113.10) Internal users and DMZ servers access internet via MASQUERADE Your Task Write a complete iptables firewall configuration for this corporate network. This firewall handles traffic between all three zones. Critical considerations: Use the FORWARD chain for traffic passing through the firewall Implement DNAT in PREROUTING for inbound services Use MASQUERADE in POSTROUTING for outbound NAT Apply security controls (rate limiting, logging) before ACCEPT rules Scenario 3: Remote File Server Debugging Difficulty: ⭐⭐☆☆☆ (Intermediate) Time estimate: 60-90 minutes You're a Security Consultant hired to debug a broken firewall. A company has a cloud-hosted file server that developers access remotely. The firewall was configured by a contractor who is no longer available, and multiple issues have been reported. Network Diagram SEATTLE OFFICE (NAT Router) ┌─────────────────┐ WAN: 52.12.45.100 │ │ LAN: 192.168.1.0/24 │ DEVELOPER A │ │ │ ┌─────────────────┐ │ 192.168.1.50 │─────│ NAT Router │─────┐ │ │ └─────────────────┘ │ │ Needs: │ │ │ - HTTPS │ │ │ - SSH │ │ │ │ │ └─────────────────┘ │ │ │ INTERNET │ │ │ │ │ ┌───────────────────────────┴───────────────────┘ │ │ │ AUSTIN OFFICE │ (NAT Router) │ WAN: 104.210.32.55 │ LAN: 192.168.1.0/24 │ │ ┌─────────────────┐ └───│ NAT Router │ └────────┬────────┘ │ │ ┌────────────┴─────────┐ │ │ │ DEVELOPER B │ │ │ │ 192.168.1.75 │ │ │ │ Needs: │ │ - HTTPS │ │ - SSH │ │ │ └──────────────────────┘ ┌─────────────────┐ │ │ │ FILE SERVER │ │ │ │ 20.141.12.34 │ │ │ │ Services: │ │ - HTTPS (443) │ │ - SSH (22) │ │ │ └─────────────────┘ Enter fullscreen mode Exit fullscreen mode Current File Server Firewall (BROKEN) # Chain policies iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT DROP # Input rules iptables -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT iptables -A INPUT -p tcp -d 20.141.12.34 --dport 443 -j ACCEPT iptables -A INPUT -p tcp -s 192.168.1.50 -d 20.141.12.34 --dport 22 -j ACCEPT iptables -A INPUT -p tcp -s 192.168.1.75 -d 20.141.12.34 --dport 22 -j ACCEPT # Output rules iptables -A OUTPUT -m conntrack --ctstate ESTABLISHED -j ACCEPT Enter fullscreen mode Exit fullscreen mode Reported Problems Seattle developer can access HTTPS but cannot SSH to the server Austin developer can access HTTPS but cannot SSH to the server Neither developer can ping the server Server cannot download security updates Server cannot resolve DNS names Your Task Part A: Root Cause Analysis For each reported problem, explain the root cause. Why is the current configuration failing? Part B: Write the Fixed Firewall Write a corrected firewall configuration that: Fixes all reported problems Allows HTTPS from anywhere Allows SSH from both office public IPs Allows ping (rate limited) Allows server to download updates and resolve DNS Logs dropped packets Critical insight: Remember that NAT routers translate private IPs to public IPs. The file server sees the WAN IP, not the LAN IP! Scenario 4: Multi-Tier Application with Bastion Host Difficulty: ⭐⭐⭐⭐⭐ (Expert) Time estimate: 2-3 hours Your company runs a production application in AWS. Security policy requires all administrative access go through a bastion (jump) host. You're configuring the bastion's firewall. Network Diagram INTERNET │ │ ┌────────────────────────────┴────────────────────────────┐ │ │ │ │ ┌────────┴────────┐ │ │ │ │ │ Security Team │ │ │ Office NAT │ │ │ │ │ │ WAN: 198.51.100.10 │ │ LAN: 10.50.0.1 │ │ │ │ │ └────────┬────────┘ │ │ │ ┌────────┴────────┐ │ │ Security │ │ │ Engineers │ │ │ │ │ │ 10.50.0.20-30 │ │ │ │ │ │ Needs SSH to: │ │ │ - Bastion │ │ │ - App servers │ │ │ (via bastion)│ │ └─────────────────┘ │ │ │ ┌─────────────────────────────────────────┘ │ │ ┌────────┴────────┐ │ AWS VPC │ │ 10.0.0.0/16 │ │ │ └────────┬────────┘ │ ┌────────────────────┼────────────────────┐ │ │ │ │ │ │ ┌────────┴────────┐ ┌────────┴────────┐ ┌───────┴─────────┐ │ PUBLIC SUBNET │ │ PRIVATE SUBNET │ │ DATABASE SUBNET │ │ 10.0.1.0/24 │ │ 10.0.2.0/24 │ │ 10.0.3.0/24 │ │ │ │ │ │ │ │ ┌─────────────┐ │ │ ┌─────────────┐ │ │ ┌─────────────┐ │ │ │ BASTION │ │ │ │ App Server │ │ │ │ Database │ │ │ │ │ │ │ │ #1 │ │ │ │ Primary │ │ │ │ eth0: │ │ │ │ │ │ │ │ │ │ │ │ 10.0.1.10 │ │ │ │ 10.0.2.10 │ │ │ │ 10.0.3.10 │ │ │ │ (has EIP: │ │ │ │ │ │ │ │ │ │ │ │ 54.23.45.67)│ │ │ └─────────────┘ │ │ └─────────────┘ │ │ │ │ │ │ │ │ │ │ │ eth1: │ │ │ ┌─────────────┐ │ │ ┌─────────────┐ │ │ │ 10.0.2.1 │ │ │ │ App Server │ │ │ │ Database │ │ │ │ (private │ │ │ │ #2 │ │ │ │ Replica │ │ │ │ subnet gw) │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ 10.0.2.11 │ │ │ │ 10.0.3.11 │ │ │ └─────────────┘ │ │ │ │ │ │ │ │ │ │ │ │ └─────────────┘ │ │ └─────────────┘ │ └─────────────────┘ └─────────────────┘ └─────────────────┘ Traffic Flows: - Security Team SSHs to Bastion (via NAT router WAN IP) - Bastion SSHs to App Servers (internal) - App Servers need outbound HTTP/HTTPS/DNS (via Bastion NAT) - App Servers connect to Database (internal, no NAT) - Database has NO internet access (strict isolation) Enter fullscreen mode Exit fullscreen mode Requirements External SSH to Bastion: Only Security Team office (public IP: 198.51.100.10) can SSH to Bastion Rate limit: 3 attempts per minute (strict security) Log all SSH attempts (successful and blocked) Bastion to Internal SSH: Bastion can SSH to App Servers (10.0.2.0/24) only Bastion CANNOT SSH to Database subnet (10.0.3.0/24) — separation of duties DBA team has separate access path (not your concern) NAT Gateway Function: App Servers access internet via Bastion (MASQUERADE) Restricted egress: DNS (53), HTTP (80), HTTPS (443) only Log denied egress attempts Database Isolation: NO traffic from Bastion to Database subnet NO traffic from Database subnet through Bastion This is enforced at Bastion level as defense-in-depth Port Scan Detection: Detect and log NULL, XMAS, SYN+FIN scans on external interface Drop invalid packets Your Task Write the complete Bastion host firewall configuration. Remember: Enable IP forwarding: echo 1 > /proc/sys/net/ipv4/ip_forward Use INPUT for traffic destined to the bastion itself Use OUTPUT for traffic originating from the bastion Use FORWARD for traffic passing through the bastion Database isolation rules must appear BEFORE any ACCEPT rules Defense-in-depth principle: Even though AWS Security Groups might block database access, the bastion's firewall enforces this rule as well. Grading Rubric Overall Evaluation Criteria Criterion Points Correct chain selection (INPUT/OUTPUT/FORWARD) 15 Proper stateful rules (ESTABLISHED,RELATED first) 15 Correct NAT configuration (DNAT/SNAT/MASQUERADE) 15 Understanding of NAT IP translation 15 Brute force protection implementation 10 Port scan detection rules 10 Proper logging configuration 5 Complete solution (no missing rules) 10 Correct syntax 5 Total: 100 points Passing Score: 85% Answer Key ⚠️ Attempt all scenarios before viewing the answer key! These solutions represent one valid approach, but multiple correct solutions exist. Scenario 1: Startup Web Application - Solution #!/bin/bash # Startup Web Application Firewall # Server IP: 104.196.45.120 # CTO Home IP: 73.189.45.22 # Default policies (drop everything by default) iptables -P INPUT DROP iptables -P OUTPUT DROP iptables -P FORWARD DROP # Connection tracking - ACCEPT established connections first (performance) iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT iptables -A OUTPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT # Loopback interface (required for local services) iptables -A INPUT -i lo -j ACCEPT iptables -A OUTPUT -o lo -j ACCEPT # HTTPS from anywhere (public web service) iptables -A INPUT -p tcp --dport 443 -j ACCEPT # SSH with brute force protection (CTO only) # Track SSH attempts - mark source IP when SSH attempt occurs iptables -A INPUT -p tcp -s 73.189.45.22 --dport 22 -m conntrack --ctstate NEW -m recent --set # Rate limit: Drop if >4 attempts in 60 seconds iptables -A INPUT -p tcp --dport 22 -m conntrack --ctstate NEW -m recent --update --seconds 60 --hitcount 4 -j DROP # Accept SSH from CTO if under rate limit iptables -A INPUT -p tcp -s 73.189.45.22 --dport 22 -j ACCEPT # DNS resolution (TCP and UDP, both needed) iptables -A OUTPUT -p udp --dport 53 -j ACCEPT iptables -A OUTPUT -p tcp --dport 53 -j ACCEPT # Package updates (HTTP and HTTPS) iptables -A OUTPUT -p tcp --dport 80 -j ACCEPT iptables -A OUTPUT -p tcp --dport 443 -j ACCEPT # Logging dropped packets iptables -A INPUT -j LOG --log-prefix "INPUT_DROPPED: " iptables -A OUTPUT -j LOG --log-prefix "OUTPUT_DROPPED: " # Default DROP (explicit for clarity, policies already set) iptables -A INPUT -j DROP iptables -A OUTPUT -j DROP Enter fullscreen mode Exit fullscreen mode Key concepts: Default DROP policies enforce "deny all, permit explicitly" Connection tracking reduces rules needed for return traffic recent module provides stateful rate limiting per source IP Both TCP and UDP DNS are required (TCP for large responses) Scenario 2: Corporate DMZ - Solution #!/bin/bash # Corporate Three-Tier Firewall # WAN: eth0 (203.0.113.10) # DMZ: eth1 (10.0.1.1) # LAN: eth2 (10.0.0.1) # Default policies iptables -P INPUT DROP iptables -P OUTPUT DROP iptables -P FORWARD DROP # Connection tracking (FORWARD is critical for router) iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT iptables -A OUTPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT # Port scan detection (before other rules) iptables -A FORWARD -p tcp --tcp-flags ALL NONE -j LOG --log-prefix "PORT_SCAN_NULL: " iptables -A FORWARD -p tcp --tcp-flags ALL NONE -j DROP iptables -A FORWARD -p tcp --tcp-flags ALL ALL -j LOG --log-prefix "PORT_SCAN_XMAS: " iptables -A FORWARD -p tcp --tcp-flags ALL ALL -j DROP iptables -A FORWARD -p tcp --tcp-flags ALL SYN,FIN -j LOG --log-prefix "PORT_SCAN_SYNFIN: " iptables -A FORWARD -p tcp --tcp-flags ALL SYN,FIN -j DROP # SYN flood protection (custom chain for modularity) iptables -N syn_flood iptables -A FORWARD -p tcp --syn -j syn_flood iptables -A syn_flood -m limit --limit 50/s -j RETURN iptables -A syn_flood -m limit --limit 5/s -j LOG --log-prefix "SYN_FLOOD: " iptables -A syn_flood -j DROP # ICMP rate limiting iptables -A FORWARD -p icmp -m limit --limit 50/s -j ACCEPT iptables -A FORWARD -p icmp -j LOG --log-prefix "ICMP_FLOOD: " iptables -A FORWARD -p icmp -j DROP # NAT - DNAT for inbound services (PREROUTING, before routing decision) # Internet → Web Server (HTTP/HTTPS) iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to-destination 10.0.1.10:80 iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 443 -j DNAT --to-destination 10.0.1.10:443 # Internet → Mail Server (SMTP/IMAPS) iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 25 -j DNAT --to-destination 10.0.1.20:25 iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 993 -j DNAT --to-destination 10.0.1.20:993 # Internet → DNS Server iptables -t nat -A PREROUTING -i eth0 -p udp --dport 53 -j DNAT --to-destination 10.0.1.30:53 iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 53 -j DNAT --to-destination 10.0.1.30:53 # NAT - MASQUERADE for outbound traffic (POSTROUTING, after routing decision) iptables -t nat -A POSTROUTING -s 10.0.1.0/24 -o eth0 -j MASQUERADE iptables -t nat -A POSTROUTING -s 10.0.0.0/24 -o eth0 -j MASQUERADE # FORWARD rules (traffic passing through firewall) # Internet → Web Server (with connection limits) iptables -A FORWARD -p tcp -m connlimit --connlimit-above 50 -i eth0 -o eth1 -d 10.0.1.10 --dport 80 -j LOG --log-prefix "WEB_CONN_LIMIT: " iptables -A FORWARD -p tcp -m connlimit --connlimit-above 50 -i eth0 -o eth1 -d 10.0.1.10 --dport 80 -j DROP iptables -A FORWARD -p tcp -i eth0 -o eth1 -d 10.0.1.10 --dport 80 -j ACCEPT iptables -A FORWARD -p tcp -m connlimit --connlimit-above 50 -i eth0 -o eth1 -d 10.0.1.10 --dport 443 -j LOG --log-prefix "WEB_CONN_LIMIT: " iptables -A FORWARD -p tcp -m connlimit --connlimit-above 50 -i eth0 -o eth1 -d 10.0.1.10 --dport 443 -j DROP iptables -A FORWARD -p tcp -i eth0 -o eth1 -d 10.0.1.10 --dport 443 -j ACCEPT # Internet → Mail Server iptables -A FORWARD -p tcp -i eth0 -o eth1 -d 10.0.1.20 --dport 25 -j ACCEPT iptables -A FORWARD -p tcp -i eth0 -o eth1 -d 10.0.1.20 --dport 993 -j ACCEPT # Internet → DNS Server iptables -A FORWARD -p udp -i eth0 -o eth1 -d 10.0.1.30 --dport 53 -j ACCEPT iptables -A FORWARD -p tcp -i eth0 -o eth1 -d 10.0.1.30 --dport 53 -j ACCEPT # Admin VPN → DMZ SSH (with brute force protection) iptables -A FORWARD -p tcp -s 198.51.100.50 -i eth0 -o eth1 -d 10.0.1.0/24 --dport 22 -m conntrack --ctstate NEW -m recent --set iptables -A FORWARD -p tcp -s 198.51.100.50 -d 10.0.1.0/24 --dport 22 -m conntrack --ctstate NEW -m recent --update --seconds 60 --hitcount 5 -j DROP iptables -A FORWARD -p tcp -s 198.51.100.50 -i eth0 -o eth1 -d 10.0.1.0/24 --dport 22 -j ACCEPT # Employee workstations → Internet iptables -A FORWARD -i eth2 -o eth0 -s 10.0.0.0/24 -p tcp -m multiport --dports 80,443 -j ACCEPT iptables -A FORWARD -i eth2 -o eth0 -s 10.0.0.0/24 -p udp --dport 53 -j ACCEPT iptables -A FORWARD -i eth2 -o eth0 -s 10.0.0.0/24 -p tcp --dport 53 -j ACCEPT # DMZ servers → Internet (updates) iptables -A FORWARD -i eth1 -o eth0 -s 10.0.1.0/24 -p tcp -m multiport --dports 80,443 -j ACCEPT iptables -A FORWARD -i eth1 -o eth0 -s 10.0.1.0/24 -p udp --dport 53 -j ACCEPT iptables -A FORWARD -i eth1 -o eth0 -s 10.0.1.0/24 -p tcp --dport 53 -j ACCEPT # Loopback for firewall itself iptables -A INPUT -i lo -j ACCEPT iptables -A OUTPUT -o lo -j ACCEPT # Allow firewall to resolve DNS and perform updates iptables -A OUTPUT -p udp --dport 53 -j ACCEPT iptables -A OUTPUT -p tcp --dport 53 -j ACCEPT iptables -A OUTPUT -p tcp --dport 80 -j ACCEPT iptables -A OUTPUT -p tcp --dport 443 -j ACCEPT # ICMP for firewall itself iptables -A OUTPUT -p icmp -j ACCEPT # Final logging iptables -A FORWARD -j LOG --log-prefix "FORWARD_DROPPED: " iptables -A INPUT -j LOG --log-prefix "INPUT_DROPPED: " iptables -A OUTPUT -j LOG --log-prefix "OUTPUT_DROPPED: " Enter fullscreen mode Exit fullscreen mode Key concepts: DNAT happens in PREROUTING (before routing decision) MASQUERADE happens in POSTROUTING (after routing decision) Security controls (port scan detection, rate limiting) go BEFORE ACCEPT rules Connection tracking eliminates need for explicit return traffic rules -i and -o specify interfaces to prevent routing loops Scenario 3: Remote File Server - Solution Part A: Root Cause Analysis Problem 1 (Seattle SSH fails): The File Server exists outside Seattle's LAN. The source address 192.168.1.50 is meaningless to the File Server because NAT translates it to 52.12.45.100 . The firewall rule: iptables -A INPUT -p tcp -s 192.168.1.50 -d 20.141.12.34 --dport 22 -j ACCEPT Enter fullscreen mode Exit fullscreen mode Should be: iptables -A INPUT -p tcp -s 52.12.45.100 -d 20.141.12.34 --dport 22 -j ACCEPT Enter fullscreen mode Exit fullscreen mode Problem 2 (Austin SSH fails): Similar problem - the firewall rule: iptables -A INPUT -p tcp -s 192.168.1.75 -d 20.141.12.34 --dport 22 -j ACCEPT Enter fullscreen mode Exit fullscreen mode Should be: iptables -A INPUT -p tcp -s 104.210.32.55 -d 20.141.12.34 --dport 22 -j ACCEPT Enter fullscreen mode Exit fullscreen mode Problem 3 (Ping fails): No ICMP rules exist in the INPUT chain. Add: iptables -A INPUT -p icmp -d 20.141.12.34 -j ACCEPT Enter fullscreen mode Exit fullscreen mode Problem 4 (No updates): The OUTPUT chain has no rule for HTTP/HTTPS. Add: iptables -A OUTPUT -p tcp -m multiport --dports 80,443 -j ACCEPT Enter fullscreen mode Exit fullscreen mode Problem 5 (DNS fails): The OUTPUT chain has no DNS rules. Add: iptables -A OUTPUT -p tcp --dport 53 -j ACCEPT iptables -A OUTPUT -p udp --dport 53 -j ACCEPT Enter fullscreen mode Exit fullscreen mode Part B: Fixed Firewall #!/bin/bash # Fixed File Server Firewall # Server IP: 20.141.12.34 # Seattle Office WAN: 52.12.45.100 # Austin Office WAN: 104.210.32.55 iptables -F # Chain policies iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT DROP # Connection tracking iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT iptables -A OUTPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT # Loopback iptables -A INPUT -i lo -j ACCEPT iptables -A OUTPUT -o lo -j ACCEPT # HTTPS from anywhere iptables -A INPUT -p tcp -d 20.141.12.34 --dport 443 -j ACCEPT # SSH from Seattle Office (public IP) iptables -A INPUT -p tcp -s 52.12.45.100 -d 20.141.12.34 --dport 22 -j ACCEPT # SSH from Austin Office (public IP) iptables -A INPUT -p tcp -s 104.210.32.55 -d 20.141.12.34 --dport 22 -j ACCEPT # ICMP (rate limited) iptables -A INPUT -p icmp -d 20.141.12.34 -m limit --limit 5/min -j ACCEPT iptables -A INPUT -p icmp -d 20.141.12.34 -j LOG --log-prefix "ICMP_EXCEEDED: " iptables -A INPUT -p icmp -d 20.141.12.34 -j DROP # Server outbound for updates and DNS iptables -A OUTPUT -s 20.141.12.34 -p tcp -m multiport --dports 80,443 -j ACCEPT iptables -A OUTPUT -s 20.141.12.34 -p tcp --dport 53 -j ACCEPT iptables -A OUTPUT -s 20.141.12.34 -p udp --dport 53 -j ACCEPT # Final logging iptables -A INPUT -j LOG --log-prefix "INPUT_DROPPED: " iptables -A OUTPUT -j LOG --log-prefix "OUTPUT_DROPPED: " Enter fullscreen mode Exit fullscreen mode Key lesson: Always remember that NAT routers translate private IPs to public IPs. Servers behind NAT cannot see RFC 1918 addresses from remote locations. Scenario 4: Bastion Host - Solution #!/bin/bash # Bastion Host Firewall # Public Interface: eth0 (10.0.1.10, EIP: 54.23.45.67) # Private Interface: eth1 (10.0.2.1) # App Subnet: 10.0.2.0/24 # Database Subnet: 10.0.3.0/24 (BLOCKED) # Enable IP Forwarding echo 1 > /proc/sys/net/ipv4/ip_forward # Default policies iptables -P FORWARD DROP iptables -P INPUT DROP iptables -P OUTPUT DROP # Connection tracking (critical for all chains) iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT iptables -A OUTPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT # Loopback iptables -A INPUT -i lo -j ACCEPT iptables -A OUTPUT -o lo -j ACCEPT # Port scan detection on external interface (before other INPUT rules) iptables -A INPUT -i eth0 -p tcp --tcp-flags ALL NONE -j LOG --log-prefix "SCAN_NULL: " iptables -A INPUT -i eth0 -p tcp --tcp-flags ALL NONE -j DROP iptables -A INPUT -i eth0 -p tcp --tcp-flags ALL ALL -j LOG --log-prefix "SCAN_XMAS: " iptables -A INPUT -i eth0 -p tcp --tcp-flags ALL ALL -j DROP iptables -A INPUT -i eth0 -p tcp --tcp-flags ALL SYN,FIN -j LOG --log-prefix "SCAN_SYNFIN: " iptables -A INPUT -i eth0 -p tcp --tcp-flags ALL SYN,FIN -j DROP # Drop invalid packets iptables -A INPUT -i eth0 -m conntrack --ctstate INVALID -j LOG --log-prefix "INVALID: " iptables -A INPUT -i eth0 -m conntrack --ctstate INVALID -j DROP # Database isolation (BEFORE any ACCEPT rules in FORWARD) iptables -A FORWARD -s 10.0.3.0/24 -j LOG --log-prefix "DATABASE_EGRESS_BLOCKED: " iptables -A FORWARD -s 10.0.3.0/24 -j DROP iptables -A FORWARD -d 10.0.3.0/24 -j LOG --log-prefix "DATABASE_ACCESS_BLOCKED: " iptables -A FORWARD -d 10.0.3.0/24 -j DROP # Database isolation for bastion itself iptables -A OUTPUT -s 10.0.1.0/24 -d 10.0.3.0/24 -j LOG --log-prefix "BASTION_TO_DB_BLOCKED: " iptables -A OUTPUT -s 10.0.1.0/24 -d 10.0.3.0/24 -j DROP # NAT - MASQUERADE for App Servers iptables -t nat -A POSTROUTING -s 10.0.2.0/24 -o eth0 -j MASQUERADE # External SSH to Bastion (with rate limiting and logging) iptables -A INPUT -i eth0 -s 198.51.100.10 -p tcp --dport 22 -m limit --limit 3/min -j LOG --log-prefix "SSH_ALLOWED: " iptables -A INPUT -i eth0 -s 198.51.100.10 -p tcp --dport 22 -m limit --limit 3/min -j ACCEPT iptables -A INPUT -i eth0 -s 198.51.100.10 -p tcp --dport 22 -j LOG --log-prefix "SSH_RATE_LIMITED: " iptables -A INPUT -i eth0 -s 198.51.100.10 -p tcp --dport 22 -j DROP # Bastion → App Servers SSH (OUTPUT chain - bastion is source) iptables -A OUTPUT -p tcp -s 10.0.1.0/24 -d 10.0.2.0/24 --dport 22 -j ACCEPT # App Servers → Internet (FORWARD chain - traffic passing through) iptables -A FORWARD -i eth1 -o eth0 -s 10.0.2.0/24 -p tcp -m multiport --dports 80,443 -j ACCEPT iptables -A FORWARD -i eth1 -o eth0 -s 10.0.2.0/24 -p tcp --dport 53 -j ACCEPT iptables -A FORWARD -i eth1 -o eth0 -s 10.0.2.0/24 -p udp --dport 53 -j ACCEPT # Log denied egress from App Servers iptables -A FORWARD -i eth1 -o eth0 -s 10.0.2.0/24 -j LOG --log-prefix "APP_EGRESS_DENIED: " iptables -A FORWARD -i eth1 -o eth0 -s 10.0.2.0/24 -j DROP # Final logging iptables -A INPUT -j LOG --log-prefix "INPUT_DROPPED: " iptables -A OUTPUT -j LOG --log-prefix "OUTPUT_DROPPED: " iptables -A FORWARD -j LOG --log-prefix "FORWARD_DROPPED: " Enter fullscreen mode Exit fullscreen mode Key concepts: INPUT: traffic destined TO the bastion OUTPUT: traffic originating FROM the bastion FORWARD: traffic THROUGH the bastion (acting as router) Explicit denies for database access implement defense-in-depth Rate limiting on SSH protects against brute force from trusted network Conclusion & Next Steps Congratulations on working through these production-grade iptables scenarios! You've now practiced: ✅ Stateful firewall design with connection tracking ✅ NAT configurations (DNAT, SNAT, MASQUERADE) ✅ Attack surface reduction through explicit deny rules ✅ Defense-in-depth with multiple security layers ✅ Security logging for incident detection ✅ Real-world debugging of broken configurations Want More Security Engineering Challenges? These labs are part of a larger collection of Security Engineering exercises covering: Application Security: SAST/DAST, secure code review, vulnerability assessment Cloud Security: AWS/Azure security configurations, IAM policies Cryptography: Implementation challenges, protocol security Web Security: OWASP Top 10, API security, authentication flaws ⭐ Star the repository for more exercises: 👉 github.com/fosres/SecEng-Exercises 👈 Each exercise includes: Detailed scenarios based on real interview questions Step-by-step solutions with explanations Grading rubrics for self-assessment References to industry-standard resources Additional Resources If you found these labs valuable, here are some recommended resources for deepening your security engineering knowledge: Security Engineering References: Grace Nolan's Security Engineering Notes - github.com/gracenolan/Notes OWASP Testing Guide - owasp.org/www-project-web-security-testing-guide PortSwigger Web Security Academy - portswigger.net/web-security iptables Documentation: Netfilter Documentation - netfilter.org/documentation iptables Tutorial by Oskar Andreasson - Comprehensive iptables guide Linux iptables Pocket Reference - Quick reference for common patterns Share Your Solutions Did you find alternative solutions to these scenarios? Security engineering often has multiple valid approaches! Share your solutions and discuss different strategies in the GitHub repository's Discussions section. Practice Makes Perfect The best way to master iptables and firewall security is through hands-on practice. Set up virtual machines, test your rules, intentionally break configurations, and learn to debug them. Each scenario you solve builds your intuition for network security. Happy firewalling! 🔥🛡️ About the Author: These exercises are designed to help aspiring Security Engineers prepare for technical interviews and real-world security challenges. Follow my journey and more security engineering content at github.com/fosres . Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse fosres Follow Studied at UCLA Worked at Intel Corporation as a Security Software Engineer Education UCLA Pronouns He/him/his Joined Nov 21, 2025 More from fosres Week 4 SQL Injection Audit Challenge # security # python # tutorial # sql Week 4 Network Packet Tracing Challenge # security # networking # linux # interview 🔐 Week 4 Scripting Challenge: Build an Auth Log Failed Login Scraper in Python # python # security # linux # securityengineering 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://securitylab.github.com/advisories/GHSL-2025-106_esphome_esphome-docs/ | GHSL-2025-106: Code Injection in esphome/esphome-docs Github Actions Workflow | GitHub Security Lab skip to content / Security Lab Research Advisories CodeQL Wall of Fame Resources Events Get Involved Resources Open Source Community Enterprise / Security Lab Research Advisories CodeQL Wall of Fame Resources Open Source Community Enterprise Events Get Involved December 11, 2025 GHSL-2025-106: Code Injection in esphome/esphome-docs Github Actions Workflow Man Yue Mo Coordinated Disclosure Timeline 2025-08-08: Reported via private vulnerability reporting: https://github.com/esphome/esphome/security/advisories/GHSA-j6pm-m8vr-p5pw 2025-11-10: Issue fixed here Summary A code injection vulnerability exists in the latest main branch of esphome/esphome-docs, where the .github/workflows/component-image.yml Github Actions workflow allows attackers to execute arbitrary code with privileged context. This flaw could enable unauthorized access or compromise of the CI environment. Project esphome/esphome-docs Tested Version latest main branch Details Code injection in Github Actions .github/workflows/component-image.yml with privileged context ( GHSL-2025-106 ) Vulnerability Details The GitHub action at .github/workflows/component-image.yml executes user input. The vulnerable code is as follows: 36 : comment="${{ github.event.comment.body }}" where the user input ${{ github.event.comment.body }} is evaluated. This input is derived from the issue_comment event, which is user-controlled. No sanitization or checks are applied to this input before it is evaluated or executed, making it vulnerable to code injection. The workflow is triggered by issue_comment with type created , which runs in a high privileged context. This means the code execution also runs in a privileged context. Impact This issue may lead to code execution in a high privileged context in a GitHub runner. Even though the workflow permissions are restricted to pull-requests: write , it can be used for cache poisoning . Credit This issue was discovered by CodeQL and an AI agent developed by the GitHub Security Lab and reported by GHSL team member @m-y-mo (Man Yue Mo) . Contact You can contact the GHSL team at securitylab@github.com , please include a reference to GHSL-2025-106 in any communication regarding this issue. Product Features Security Team Enterprise Customer stories The ReadME Project Pricing Resources Roadmap Compare GitHub Platform Developer API Partners Atom Electron GitHub Desktop Support Docs Community Forum Professional Services GitHub Skills Status Contact GitHub Company About Blog Careers Press Inclusion Social Impact Shop GitHub Inc. © 2024 Terms Privacy Sitemap What is Git? Manage Cookies Do not share my personal information | 2026-01-13T08:49:34 |
https://securitylab.github.com/advisories/GHSL-2025-102_GHSL-2025-103_acl-anthology/ | GHSL-2025-102_GHSL-2025-103: Code injection in acl-anthology | GitHub Security Lab skip to content / Security Lab Research Advisories CodeQL Wall of Fame Resources Events Get Involved Resources Open Source Community Enterprise / Security Lab Research Advisories CodeQL Wall of Fame Resources Open Source Community Enterprise Events Get Involved December 19, 2025 GHSL-2025-102_GHSL-2025-103: Code injection in acl-anthology Peter Stöckli Coordinated Disclosure Timeline 2025-08-13: Report sent to maintainer. 2025-08-13: Workflows were fixed. Summary The latest changeset of acl-anthology was vulnerable to code injection in two GitHub Actions workflows, link-to-checklist and print-info, which could have allowed attackers to execute arbitrary commands during CI processes. Project acl-anthology Tested Version The latest changeset at the moment of review Details Issue 1: Code injection in GitHub Actions link-to-checklist ( GHSL-2025-102 ) A potential code injection vulnerability has been identified in the GitHub action at .github/workflows/link-to-checklist.yml . The action evaluates untrusted user input from a pull request title without proper sanitization at line 19: echo "PR Title : ${{ GitHub.event.pull_request.title }}" The vulnerable code directly uses the pull request title provided by the user without any sanitization. Trigger Analysis The workflow can be triggered by: workflow_dispatch pull_request_target (type: opened) The presence of the pull_request_target trigger is particularly concerning as it is a high privileged trigger. This means the workflow runs in a privileged context with write permissions , while still being able to be triggered by external contributors through pull requests. Impact This issue may lead to code execution with high privileges. Issue 2: Code injection in GitHub Actions print-info ( GHSL-2025-103 ) A potential code injection vulnerability has been identified in the GitHub action at .github/workflows/print-info.yml . The action evaluates untrusted user input from a pull request at line 19-20: PR Title : ${{ GitHub.event.pull_request.title }} Original PR Body : ${{ GitHub.event.pull_request.body }} The vulnerable code directly uses the pull request body and title provided by the user with direct expression interpolation. The expression is evaluated before the bash script is run, so a crafted user input may insert END_OF_BLOCK marker and add arbitrary bash commands. Trigger Analysis The workflow can be triggered by: workflow_dispatch pull_request_target (type: opened) The presence of the pull_request_target trigger is particularly concerning as it is a high privileged trigger. This means the workflow runs in a privileged context with access to repository secrets and write permissions, while still being able to be triggered by external contributors through pull requests Impact This issue may lead to code execution with high privileges. Credit This issue was discovered by CodeQL and an AI agent developed by the GitHub Security Lab and reported by GHSL team member @p- (Peter Stöckli) . Contact You can contact the GHSL team at securitylab@github.com , please include a reference to GHSL-2025-102 or GHSL-2025-103 in any communication regarding these issues. Product Features Security Team Enterprise Customer stories The ReadME Project Pricing Resources Roadmap Compare GitHub Platform Developer API Partners Atom Electron GitHub Desktop Support Docs Community Forum Professional Services GitHub Skills Status Contact GitHub Company About Blog Careers Press Inclusion Social Impact Shop GitHub Inc. © 2024 Terms Privacy Sitemap What is Git? Manage Cookies Do not share my personal information | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/testing-and-qa/debug-tools/evaluation-lookup | Evaluation Lookup | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Testing and QA Debug Tools Evaluation Lookup Point-in-time Simulation Live Events Web Debugger Self-Targeting Extras Examples Platform Testing and QA Debug Tools Evaluation Lookup On this page Evaluation Lookup The Evaluation Lookup debugging tool lets you view historical Variable Evaluation data for your users. It shows which Features and Variables a user received at a given point in time, along with the reasoning behind that configuration. warning Ad blockers may prevent you from seeing events sent to DevCycle, as such the Debug Tools may not show the full picture of events. Why use it? Verify that a user received a specific Feature, Variable or Variation. Understand the reason behind why a user did or did not receive a Feature, Variable, or Variation. Audit all Features, Variables, and Variations a user received during a specific time period, with the option to filter results further. Usage Evaluation Lookup allows you to see Variable Evaluations for a given user. To start, input a user_id , select an Environment and pick a date range, and it will return all the evaluations in that given timeframe. There are also optional parameters you can filter by, such as Variable key, Feature name, SDK Type, and Platform. Results Once you run a search, Variable Evaluations are returned along with the latest set of User Information for the specified user_id . The results table shows: The Variable that was evaluated The Timestamp for when it was triggered The Feature and Variation that was received with a link to the Feature if available The Evaluation Reason We’ll break down both sections below. User Information When expanded, this section displays the latest set of user data evaluated for the specified user_id . Any Custom Properties you’ve included will also be displayed here. Coming soon, users will have the ability to Simulate a configuration request at any point in time. This will let you see which Features or Variables a user would receive under a specific configuration at a given moment in time. Evaluations The results table displays all Variable Evaluations for the selected user_id and date range. Each entry includes the Variable key, associated Feature, received Variation, and the reason it was or was not targeted. When viewing details for a Variable Evaluation, you’ll also see the raw data from the DevCycle SDK that populates the table. Edit this page Last updated on Jan 9, 2026 Previous Variable Schemas Next Point-in-time Simulation Usage Results User Information Evaluations DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/stale-feature-notifications | Stale Feature Notifications | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Stale Feature Notifications On this page Stale Feature Notifications info Stale Feature Notifications are a Business / Enterprise feature. To learn more, read about our pricing . To upgrade your plan, please update your plan on your Billing Information page which can be found in your organization's Settings, or contact Sales . Stale Features are identified based on specific conditions associated with their usage, modifications, and Feature type. DevCycle will alert you when a Feature has been qualified as potentially stale to help ensure that Features are surfaced for cleanup. If a Feature is marked as stale, DevCycle encourages users to take action by updating its status to Complete or Archived. This indicates that a Feature is ready to be cleaned up and removed from your codebase. Stale Feature Reasons note Stale Feature detection relies on Variable evaluations triggered through the .variable() or .variableValue() SDK call. If your implementation uses .allVariables() or .allFeatures() , these calls do not generate evaluation data. As a result, Features may appear Unused and be marked stale even if they are actively used in your code. If you know the Feature is active and used via .variable() or .variableValue() you can choose to: Snooze or Disable the staleness check for that Feature. Uncheck "Unused" as a staleness check type in your Project Settings to prevent similar cases. If you're unsure whether evaluations are occurring, contact Support with the Variable key name so we can investigate further. Features can belong to one of the following staleness reasons: Unmodified Short-Lived A Feature is classified as Unmodified if it has not been updated for more than 14 days. Applicable to : Release, Experiment Feature types. Long-Lived A Feature is classified as Unmodified if it has not been updated for more than 30 days. Applicable to : Ops, Permissions Feature types. Released A Released Feature is one that has been serving the same variation to all users in a production environment for 14 or more days. DevCycle confirms that distribution has reached 100% and all rollouts are complete. Applicable to : Release, Experiment Feature types. Unused An Unused Feature is one where there are no evaluations or defaults for any Variables associated with the Feature for 2 weeks. Targeting status is irrelevant. Applicable to : All Feature types. info Staleness Feature checks are ONLY conducted on Features that have an In Progress status. Features marked as Complete are not checked for staleness, as they should already be considered ready for cleanup given their status. Enabling Stale Feature Notifications for your Project To enable or disable Stale Feature Notifications, go to your Project Settings and locate the Stale Feature Notifications section. Only Organization Owners can enable or disable these notifications. Use the dropdown to select Enabled . From there, choose which types of staleness you want DevCycle to monitor. Note: Feature Staleness checks are run every 24 hours at midnight UTC. Stale Feature Notifications on the Dashboard You can find a list of stale Features on the main landing page of DevCycle. On the Feature List page, stale Features are marked with an exclamation point next to their status label. Hover over the status to see the specific staleness reason. You can also filter for all stale Features or specific staleness reasons on the Feature list page. Snoozing & Disabling Stale Feature Notifications If a Feature is marked as stale, you will see a notification at the top of the Feature page. Click the Details button in the banner to go to the Status section, where you’ll see the exact reason for staleness. To snooze the notification, click the Snooze button and choose how long to pause staleness checks for that Feature. After the snooze period ends, DevCycle will resume checking. To unsnooze or change the snooze period, click the Unsnooze button. To disable staleness checks for this Feature entirely, click the Disable button. +To re-enable checks, go to the Feature’s Settings section and set the Feature Staleness Check dropdown to Enabled . Stale Feature Report Email Notifications You can also set up recurring email reports with a summary of stale Features in your project. Each report includes: The total number of stale Features as of the email date. The change (delta) in stale Features since the last report. A breakdown of staleness types. Clicking on the staleness type takes you to a filtered list of those Features in the dashboard. Choose your preferred frequency— Weekly, Bi-Weekly, or Monthly —and specify who should receive the emails. If Permissions are enabled for your project: Only users with Publisher access or higher can edit the email recipient list. If Permissions are not enabled : All users can update the recipient list. Edit this page Last updated on Jan 9, 2026 Previous Status and Lifecycle Next Feature Experimentation Stale Feature Reasons Unmodified Released Unused Enabling Stale Feature Notifications for your Project Stale Feature Notifications on the Dashboard Snoozing & Disabling Stale Feature Notifications Stale Feature Report Email Notifications DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/experimentation/creating-and-managing-metrics | Creating and Managing Metrics | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Feature Experimentation Creating and Managing Metrics How Metrics are Calculated Video Tutorial: Experiment Setup Tutorial: Funnel Experiment Account Management Security and Guardrails Testing and QA Extras Examples Platform Experimentation Creating and Managing Metrics On this page Creating and Managing Metrics info Metrics are available to all customers on any plan and rely on Custom Events that must be sent to DevCycle. All plans come with an included amount of free events. When exceeded, additional costs will be incurred. To learn more, read about our pricing , or contact us . This article explains how to create, define, and manage all of the Metrics in a Project. Metrics provide a broad overview of your system. They may be used to quickly assess the health of your Features across environments, visualize how quickly people are visiting your applications, or how much memory is being used by your servers as a Feature rolls out. Metrics may be known as "Goals" on other platforms. Within DevCycle, Metrics are their own items outside of a Feature and thus can be defined once and applied to as many Features as desired. This gives the opportunity to attach and test Metrics with seemingly unrelated Features and find unintended or hidden impacts. Metrics Section To view and create Metrics, first navigate to the Metrics section of the Dashboard This section will contain a list of all of the Metrics on the current Project, all of which are re-usable across any number of Features at any time. This list contains some simple base info. Below is a brief description of each column, with deeper explanations later in this document Name - The name of the Metric. This name is the human-readable format of the Metric for easily discussing the Metrics. As explained later, the key is what will be used within the Management API. Type - The "Type" of Metric which represents the dimension or calculation used for the Metric. It may be a simple count, or a rate, or an average. These type definitions are described below in "Creating a Metric". Event Type - This is the name of the event sent by the SDKs or APIs which is being used for this Metric. Date Modified - Simple date explaining the last time someone made any modifications to a Metric which may have changed anything significant to the calculated results. Creating a Metric Follow the video below from our DevCycle Experiment Setup series or read-along to find out how to create a Metric on DevCycle. To create a Metric, navigate to the Metrics page as noted above, and click "Create a Metric". Metrics can also be created directly within any Feature from the Experimentation panel. Upon clicking create, the following modal will show: To set up a Metric, the following items are needed: Name - This is the name of the Metric. It should be descriptive enough that any team member viewing it understands it and can both get the information necessary, and also decide if they would like to re-use the Metric for other Features. Key - Like other DevCycle keys, this is how this Metric will be referenced in the Management API and all other non-dashboard interactions with this Metric. Event Type - This is the EXACT event name that is sent by the DevCycle Track methods of the SDKs or via the DevCycle APIs. This event will be used in all calculations of the Metric. How it is used specifically is described below in How do Metrics get calculated? Optimize For - DevCycle represents Metrics as a positive or negative depending on the desired optimization. Often times, tools will always assume that an increase is beneficial. However, in most engineering applications, the opposite is true! Things such as latency, load times, server load, and processing times are Metrics that should be decreased. DevCycle will make obvious whether a Metric is improving in the desired direction, and will soon notify you if a significant impact in either direction has been made. Description (optional) - A meaningful description explaining what this Metric is for and why it is being tracked. In conjunction with DevCycle's Jira Integration, this can be useful for managers to get a greater depth of information when understanding Metrics. Type - The type of a Metric defines how and what it is calculating and represented to the user. This "Type" is currently a set of the items defined below and available in the dropdown. Types When making a Metric, the types of Metrics will contain a small definition Count per Unique User - This Metric type calculates the total number of times a unique user (or service) has sent this event. This can be something such as total number of clicks on a new feature, total number of API calls for a new service, total number of of views for a new advertisement, etc. This is also useful for error tracking -- A total count of specific errors is a great Metric to count when monitoring the rollout of a new release of a Feature. Count per Variable Evaluation - This type counts the total number of times this event has been seen ONLY when the actual related Variable has been evaluated. This is a very useful case, as there may be events which already exist within your system which could potentially also be impacted by this Variable. In this case, this type of Metric represents the exact number of times that event has been sent ONLY after the related Variable has since been evaluated for use. Sum per User (numerical) - Each event can carry a numerical value with it, and this Metric will sum up the total number sent with the events per unique user. This type of Metric is great for tracking things such as Revenue, or number of total items purchased or interacted with. From an engineering view, things such as a total number of api calls per unique user may be something intended to decrease (for optimizations) or increase (for increased interaction). Average per User (numerical) - Similar to the sum per user, the average for user also uses the numerical value on each event. This type of Metric is extremely useful for tracking things such as the average latency per API call, or average size of an API call, hoping for a decrease. Load times, server load, api latency, or even your own internal build time can be candidates for a Metric which is re-used across every single Feature for viewing the impact and reacting accordingly. Future Types - If there are any types of Metric you'd like to see, or if your team would like a more flexible view into all of your data, do not hesitate to reach out to [email protected] . We will be increasing the number of types, as well as providing direct calculation control in the future. If such things are desired now, contact us to discuss direct data access, which will provide full access to all events and data for each of your Projects. Metric Details Page After creating a Metric, or by clicking on one from the Metric list, you will be navigated to the Metric Details page. This page has the following sections. Metric Definition The Metric definition allows for modifying the Metric Name, Type, Definition, and Optimization. Metric Testing This section provides the ability to test a Metric against any Feature in any environment and ensure it is working as intended. It is also useful to use this testing section to quickly check a Metric against any given Feature to potentially find any unintended impacts if the Metric is not associated with a specific Feature. When testing a Metric, navigate to the Testing section. To run a test, the following fields must be set: Feature - This is the specific Feature this Metric should be applied to. Any event that has been sent since the creation of this Metric from a user receiving any Variation of this Feature will be part of this Metric. In the event that an error is shown, this means the event has not been seen from this Feature yet. Control - After selecting a Feature, a "control" Variation must be selected. This is what will be used to show a comparative analysis against all other Variations in a Feature. Typically, an "off" or "Baseline" Variation would act as the control. For more information on this, please refer to the Feature Experimentation documentation . Date Range - Select a date range of up to the last 30 days to display results for. This range will default to the last 30 days or to the Feature creation date if the Feature was created within 30 days. Environment - This will calculate the Metric using events from the specified environments. Once these fields are set, the test can be ran by clicking the test button, resulting in a test result. (For these documents, our own internal Metrics testing at this time were used!) The results of this test will show the actual result which would be within a Feature if this Metric was associated with it! Attaching Metrics to Features Tracking Metrics within a Feature is an important aspect of data analysis, as it can provide valuable insights into the performance and behaviour of different Features. Once a Metric has been created, it can be attached to any Feature for use and analysis. Follow the video below from our DevCycle Experiment Setup series or read-along to find out how to add a Metric to a Feature and view Experiment results. Here are the steps you can follow to track Metrics within a Feature: Select the Feature you want to track : Within that Feature, navigate to the Data & Results tab on the Feature Form of the page and click on Experiment Results . Choose the Metric(s) associated with the Feature : Create new Metrics or attach existing ones to the Feature by navigating to the Choose a Metric dropdown. Attach the Metric(s) : Attach the Metric from the dropdown menu by selecting it. For our example, let's use the Metric Metric Testing , which has already been setup within our Project. While the setup has some default values, the Metric requires the following fields to be filled: Control - This is what will be used to show a comparative analysis against all other Variations in a Feature. Typically, an "off" or "Baseline" Variation would act as the control. For more information on this, please refer to the Feature Experimentation documentation . Date Range - Select a date range of up to the last 30 days to display results for. This range will default to the last 30 days or to the Feature creation date if the Feature was created within 30 days. Environment - This will calculate the Metric using events from the specified environments. Calculate results : Once one or more Metrics have been selected, we can then run the Metric calculation to generate insight into how the Feature is doing. View your results : Once calculated, if there is available data for the Feature, the results data will populate within the dashboard. From here, useful information such as trends and patterns in the data can be used to make informed decisions about how to optimize the Feature for performance improvements. How do Metrics get calculated? To calculate Metrics, DevCycle uses the custom events sent via its API or SDKs . Each Event has the information of which user sent it and which Feature and Variation they were in at that time. For optimal Experiments, use Features with Variations randomly distributed across users . To read more on the queries behind the Metrics, see How Metrics Are Calculated Running Experiments With Metrics on a Feature, Experimentation can be easily executed on any Feature. At DevCycle we believe that Experimentation should be a part of the natural lifecycle of all Features. So no matter the Feature type selected, Experimentation will always be available for use. To learn more on how to run Experiments with DevCycle, read Feature Experimentation Edit this page Last updated on Jan 9, 2026 Previous Feature Experimentation Next How Metrics are Calculated Metrics Section Creating a Metric Types Metric Details Page Attaching Metrics to Features How do Metrics get calculated? Running Experiments DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://docs.devcycle.com/essentials/key-features | Key Features | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Essentials Key Features On this page What Makes Us Different DevCycle is a comprehensive feature flag management platform with a wide range of capabilities. We believe that modern software development processes require feature flagging in order to be successful. For feature flagging to provide its full value, developers need to embed it into their workflow. So DevCycle is designed for the developer first, but with the whole team in mind. Here are the core concepts and features behind them that we think make us different. Protect Production Without Getting in Your Way For feature flagging to be effective, all team members need to be able to operate without fear of breaking production. We use a balance of guardrails, permissions and observability to ensure all users have confidence in the actions they are taking. Here's how: Govern who can modify flags in production using Permissions . Allow non-technical users to modify flag values safely, by enforcing schemas . Easily see a detailed history of all changes to flags. Write type-safe code using our Code Generators . Ensure a predictable process for changing flags using Gitops and Terraform . Manage Flags Without Leaving Your Workflow Excellent developer tools reduce context-switching away from code as much as possible. Each user has a core set of tools that they use to do their work, it is our job to make those tools better. So we've built a set of tools to help you stay in the flow regardless of how you work. Here's how: Use the CLI and Editor Plugins to manage flags without interrupting your work. Detect and jump to flag usages in code, and quickly see whether flags are enabled in each environment. Override your own flag values for development or testing in production. Feature Flagging is a Team Sport Feature flags are most valuable when all team members are part of the process. A feature flag's purpose, state and impact should be obvious and discoverable to all users. Here's how: We never bill on seats. Group multiple related flags and change their values together using Features . Link your flags to productivity tools like Jira or Slack . Safely QA your flags in development or right in production with Self-Targeting . Features Aren't Complete Until Flags Have Been Removed Old, unused flags are tech-debt that create operational risk. This means that the process of removing flags is as important as creating them. Here's how you can keep your feature flagging environment clean in DevCycle: Keep on top of which flags are actually being used in your codebase with Code Usage Detection . Mark flags as " completed " when a feature is released. Automatically remove your flags with our CLI Cleanup command. Let Us Manage User Data Modern architecture means distributed systems running at the edge. Relevant targeting data isn't always available in all systems or services. So we've built ways to keep our platform fast while managing targeting data for you. Here's how: Store user attributes in a fast, globally-replicated database and target flags based on those attributes. Easily add a full feature opt-in experience to your application to allow end users to control their experience. Integrate with Any Other Tool Feature flagging is better when integrated into the rest of your critical tools. While we have a selection of integrations built and ready for you to install, we understand you may need other integrations so we've made DevCycle as extensible as possible. See how to integrate your own tools: Notify external systems of changes to your flags using Outbound Webhooks . See changes in your monitoring systems and alert on potential issues. A complete API and CLI are available to run automations or scripts as necessary. Edit this page Last updated on Jan 9, 2026 Previous DevCycle Overview Next System Architecture Protect Production Without Getting in Your Way Manage Flags Without Leaving Your Workflow Feature Flagging is a Team Sport Features Aren't Complete Until Flags Have Been Removed Let Us Manage User Data Integrate with Any Other Tool DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://forem.com/enter?signup_subforem=36#main-content | Welcome! - Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Join the Forem Forem is a community of 3,676,891 amazing members Continue with Apple Continue with Facebook Continue with GitHub Continue with Google Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to Forem? Create account . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — Your community HQ Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#status-categories-and-rules | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://popcorn.forem.com/popcorn_movies/ringer-movies-the-robert-redford-hall-of-fame-4k88 | Ringer Movies: The Robert Redford Hall of Fame - Popcorn Movies and TV Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Popcorn Movies and TV Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Movie News Posted on Nov 28, 2025 Ringer Movies: The Robert Redford Hall of Fame # movies # streaming # recommendations The Robert Redford Hall of Fame Sean Fennessey and Amanda Dobbins invite actor-playwright Tracy Letts to celebrate Robert Redford’s illustrious career. Together they riff on his standout roles, share personal anecdotes about the star’s impact, and literally build their own Redford Hall of Fame. From Sundance Kid stardom to directorial triumphs like Ordinary People, this lively chat maps Redford’s biggest milestones and enduring appeal. If you’re streaming on Prime or just love classic Hollywood legends, it’s a fun, affectionate deep dive into one of cinema’s all-time greats. Watch on YouTube Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Movie News Follow Joined Jun 22, 2025 More from Movie News Ringer Movies: The 2026 Golden Globes: ‘One Battle After Another’ vs. ‘Hamnet’ Begins # movies # reviews # analysis # streaming CinemaSins: Everything Wrong With Austin Powers in Goldmember in 19 Minutes Or Less # movies # reviews # analysis # marketing Ringer Movies: Five Burning Questions About Awards Season & Our Golden Globes Predictions # movies # analysis # reviews # recommendations 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Popcorn Movies and TV — Movie and TV enthusiasm, criticism and everything in-between. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Popcorn Movies and TV © 2016 - 2026. Let's watch something great! Log in Create account | 2026-01-13T08:49:34 |
https://popcorn.forem.com/popcorn_movies/ringer-movies-snake-eyes-with-bill-simmons-sean-fennessey-and-van-lathan-ringer-movies-1fdp | Ringer Movies: ‘Snake Eyes’ With Bill Simmons, Sean Fennessey, and Van Lathan | Ringer Movies - Popcorn Movies and TV Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Popcorn Movies and TV Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Movie News Posted on Nov 17, 2025 Ringer Movies: ‘Snake Eyes’ With Bill Simmons, Sean Fennessey, and Van Lathan | Ringer Movies # movies # marketing # recommendations ‘Snake Eyes’ Rewatch Rundown In the latest Ringer Movies episode, Bill Simmons, Sean Fennessey, and Van Lathan dive back into Brian De Palma’s 1998 thriller Snake Eyes. They unpack Nic Cage’s undercover ballpark espionage, Gary Sinise’s corrupt-cop swagger, and Carla Gugino’s femme-fatale flair. Self-dubbing themselves the “kings of the sewer,” the trio gleefully dissects De Palma’s signature camera moves, plot twists, and the film’s over-the-top ’90s energy. Watch on YouTube Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Movie News Follow Joined Jun 22, 2025 More from Movie News Ringer Movies: The 2026 Golden Globes: ‘One Battle After Another’ vs. ‘Hamnet’ Begins # movies # reviews # analysis # streaming CinemaSins: Everything Wrong With Austin Powers in Goldmember in 19 Minutes Or Less # movies # reviews # analysis # marketing Ringer Movies: Five Burning Questions About Awards Season & Our Golden Globes Predictions # movies # analysis # reviews # recommendations 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Popcorn Movies and TV — Movie and TV enthusiasm, criticism and everything in-between. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Popcorn Movies and TV © 2016 - 2026. Let's watch something great! Log in Create account | 2026-01-13T08:49:34 |
https://securitylab.github.com/open-source/ | Resources | GitHub Security Lab skip to content / Security Lab Research Advisories CodeQL Wall of Fame Resources Events Get Involved Resources Open Source Community Enterprise / Security Lab Research Advisories CodeQL Wall of Fame Resources Open Source Community Enterprise Events Get Involved Resources Open Source Community Secure code education, hands-on AppSec training, and specialized support. Free for open source developers, maintainers, and security researchers. For Developers Learn secure coding patterns The Secure Code Game is an open source, in-repo, learning experience for developers, to build a secure coding mindset while having fun. Learn more How do I start securing my project? Enable, with just a few clicks, and for free, GitHub's security tools that will help you write secure code, prevent secret leaks, scan your dependencies for security vulnerabilities, and globally keep your users safe. Five easy steps to secure your open source project For Security Researchers Latest articles See all articles Keeping your GitHub Actions and workflows secure Part 4: New vulnerability patterns and mitigation strategies While implementing CodeQL support for GitHub Actions workflows, we came across new patterns of insecure workflows. Learn how to identify and mitigate them. Five easy steps to secure your open source project Enable, with just a few clicks, and for free, GitHub's security tools that will help you write secure code, prevent secret leaks, scan your dependencies for security vulnerabilities, and globally keep your users safe. The GitHub Security Lab’s journey to disclosing 500 CVEs in open source projects The GitHub Security Lab audits open source projects and helps maintainers fix security vulnerabilities. For our 500th CVE, we took a trip down memory lane with a review of some noteworthy CVEs! CodeQL The GitHub Security Lab uses CodeQL to perform variant analysis, an important technique for identifying new types of security vulnerabilities of a given class. CodeQL Wall of Fame We find hundreds of vulnerabilities in open source thanks to CodeQL Explore CodeQL Wall of Fame CodeQL: from zero to hero New to CodeQL? Learn how you can apply static analysis to security vulnerability research. Read the article Learn CodeQL Want to play a game? We created several “Capture the Flag” based on CodeQL, to help you make your first step. Go Capture the Flag Security Advisories Request a CVE ID If you want a CVE identification number for a security vulnerability in your project, you can request the CVE ID from GitHub. GitHub usually reviews the request within 72 hours, and will take care of curating and publishing the CVE record after your repository advisory is published. Request a CVE ID Contribute to a Security Advisory Our team of security researchers continuously review new security information to ensure our data is the best there is, and this includes additional insights provided by the global community of subject-matter experts. You can help make this data better by contributing your expertise back to it! Propose an improvement to an advisory Fuzzing 101 Do you want to learn how to fuzz like a real expert, but not sure where to start? This is the course for you! 10 real targets, 10 exercises. Can you solve them all? Learn Fuzzing 101 Read more about Fuzzing Fuzzing software: common challenges and potential solutions In this two-part blog series, we’ll review some of the challenges we commonly face in our fuzzing workflows and provide ways to address these challenges. Fuzzing sockets In this two-part series, Antonio Morales shares findings and tips from his research on socket-based fuzzing. Fuzzing Android NFC Man Yue Mo built and open sourced a fuzzer for the Android Near Field Communication (NFC) component. He shares here some design considerations when building the fuzzer. Latest videos See all videos May 12, 2025 Secure Code Game Season 3 - Teaser Season 3 is coming! Catch up on the first 2 seasons Mar 29, 2023 Secure Code Game Are you passionate about software? We have something for you: Secure Code Game! Mar 21, 2023 🎉 Write safer code with new vulnerability prevention features in GitHub Copilot 🔒 ✅ GitHub Copilot for Security! You can use it to write safer code. Product Features Security Team Enterprise Customer stories The ReadME Project Pricing Resources Roadmap Compare GitHub Platform Developer API Partners Atom Electron GitHub Desktop Support Docs Community Forum Professional Services GitHub Skills Status Contact GitHub Company About Blog Careers Press Inclusion Social Impact Shop GitHub Inc. © 2024 Terms Privacy Sitemap What is Git? Manage Cookies Do not share my personal information | 2026-01-13T08:49:34 |
https://trello.com/ | Capture, organize, and tackle your to-dos from anywhere | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog Accelerate your teams' work with AI features 🤖 now available for all Premium and Enterprise! Learn more. Capture, organize, and tackle your to-dos from anywhere. Escape the clutter and chaos—unleash your productivity with Trello. Sign up - it’s free! By entering my email, I acknowledge the Atlassian Privacy Policy Watch video Hero Trello 101 Your productivity powerhouse Stay organized and efficient with Inbox, Boards, and Planner. Every to-do, idea, or responsibility—no matter how small—finds its place, keeping you at the top of your game. Inbox When it’s on your mind, it goes in your Inbox. Capture your to-dos from anywhere, anytime. Boards Your to-do list may be long, but it can be manageable! Keep tabs on everything from "to-dos to tackle" to "mission accomplished!” Planner Drag, drop, get it done. Snap your top tasks into your calendar and make time for what truly matters. Inbox When it’s on your mind, it goes in your Inbox. Capture your to-dos from anywhere, anytime. Boards Your to-do list may be long, but it can be manageable! Keep tabs on everything from "to-dos to tackle" to "mission accomplished!” Planner Drag, drop, get it done. Snap your top tasks into your calendar and make time for what truly matters. From message to action Quickly turn communication from your favorite apps into to-dos, keeping all your discussions and tasks organized in one place. EMAIL MAGIC Easily turn your emails into to-dos! Just forward them to your Trello Inbox, and they’ll be transformed by AI into organized to-dos with all the links you need. MESSAGE APP SORCERY Need to follow up on a message from Slack or Microsoft Teams? Send it directly to your Trello board! Your favorite app interface lets you save messages that appear in your Trello Inbox with AI-generated summaries and links. WORK SMARTER Do more with Trello Customize the way you organize with easy integrations, automation, and mirroring of your to-dos across multiple locations. Integrations Connect the apps you are already using into your Trello workflow or add a Power-Up to fine-tune your specific needs. Browse Integrations Automation No-code automation is built into every Trello board. Focus on the work that matters most and let the robots do the rest. Get to know Automation Card mirroring View all your to-dos from multiple boards in one place. Mirror a card to keep track of work wherever you need it! Compare plans [Trello is] great for simplifying complex processes. As a manager, I can chunk [processes] down into bite-sized pieces for my team and then delegate that out, but still keep a bird's-eye view. Joey Rosenberg Global Leadership Director at Women Who Code Read the story 75% of organizations report that Trello delivers value to their business within 30 days. Trello TechValidate Survey Whether someone is in the office, working from home, or working on-site with a client, everyone can share context and information through Trello. Sumeet Moghe Product Manager at ThoughtWorks Read the story 81% of customers chose Trello for its ease of use. Trello TechValidate Survey We used Trello to provide clarity on steps, requirements, and procedures. This was exceptional when communicating with teams that had deep cultural and language differences. Jefferson Scomacao Development Manager at IKEA/PTC Read the story 74% of customers say Trello has improved communication with their co-workers and teams. Trello TechValidate Survey Join a community of millions of users globally who are using Trello to get more done. Join a community of millions of users globally who are using Trello to get more done. Get started with Trello today Sign up - it’s free! By entering my email, I acknowledge the Atlassian Privacy Policy Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T08:49:34 |
https://securitylab.github.com/events/ | Events | GitHub Security Lab skip to content / Security Lab Research Advisories CodeQL Wall of Fame Resources Events Get Involved Resources Open Source Community Enterprise / Security Lab Research Advisories CodeQL Wall of Fame Resources Open Source Community Enterprise Events Get Involved events Our top researchers speak on code security November 13, 2024 EkoParty 2024: 20 Años! Buenos Aires, Argentina ¡GitHub se enorgullece de patrocinar EkoParty una vez más! Si estás en EkoParty, ¡pasa por el stand de GitHub para conocer a nuestros expertos! September 5, 2024 OrangeCon 2024 Amsterdam, Netherlands June 21, 2024 Play Secure Conference 2024 Virtual Play Secure is the intersection of play and security! This unique virtual conference is designed to delve into the world of gamification, exploring how play, games, and gamification can transform the landscape of security training and awareness. Join industry leaders, innovative game designers, and security experts as we embark on a journey to redefine the future of secure play. June 19, 2024 AI_dev: Open Source GenAI & ML Summit Paris, France AI_dev is a nexus for developers delving into the intricate realm of open source generative AI and machine learning. At the heart of this event is the belief that open source is the engine of innovation in AI. By uniting the brightest developers from around the world, we aim to ignite discussions, foster collaborations, and shape the trajectory of open source AI. June 06, 2024 KCD Czech & Slovak 2024 Prague, Czech Republic KCD Czech & Slovak 2024 is an event for all architects, CTOs, IT managers, developers, DevOps, administrators, SREs, students and anyone interested in learning more about the fundamentals of Cloud Native technologies, the individual CNCF projects presented, and the in-depth skills and architecture presented. There will be discussions with professionals and users, and participants will learn about DevOps culture and can join a large Slovak and Czech community with global reach. June 05, 2024 Developer Week Global 2024 Virtual Developer Week Global 2024 is an online series where you can join 15,000+ dev professionals for the world’s largest virtual conference series with 4+ fully immersive events covering the newest technology innovations, best practices, and learning across cloud, API, enterprise dev, architecture, DevOps, DevTools, dev management, and more. May 29, 2024 DevTalks Romania Bucharest, Romania DevTalks Romania has become a driver of change for the tech world, known as the most desired expo-conference for developers and IT professionals in Romania. Thus, the DevTalks network is succeeding to cover all year with valuable content and gatherings of the IT Community enlarging the network to more than 60 000 IT professionals and developers from all over Romania and internationally. May 15, 2024 DevSum 2024 Stockholm, Sweden DevSum 2024 celebrates 20 years as the premier conference for software developers looking to learn the latest from the industry’s brightest stars. From humble beginnings, the past two decades have seen DevSum grow to become the most important event in the calendar for developers looking to stay on top! April 15, 2024 SINFO 31 Lisbon, Portugal SINFO is a college student and non-profitable organization responsible for the planning of one of the biggest Tech events in Portugal. It’s an annual conference that takes place at Técnico Innovation Center, in the capital city of Portugal, Lisbon. March 12, 2024 DevSecOps in Azure + GitHub Virtual DevSecOps in Azure + GitHub is the 3rd session of the Spotlight on Applications Innovation & AI event series. The "Spotlight on Applications Innovation & AI" webinar series is designed to delve deep into the latest trends, tools, and techniques in the realm of applications innovation and artificial intelligence (AI). Each session brings together industry experts, thought leaders, and practitioners to explore various facets of innovation in application development, highlighting emerging technologies, best practices, and real-world use cases. February 6-7, 2024 State of Open Con 24 London, England State of Open Con 24 is organized by Open UK, a not-for-profit company limited by guarantee, company number 11209475, registered at 8 Coldbath Square, London, EC1R 5HL. January 9-10, 2024 NDC Security 2024 Oslo, Norway Artificial intelligence (AI) is already acting as a copilot in our daily lives, acting as a digital assistant or providing personalized experiences. Despite progress in many other areas, AI has historically stopped short of improving software development practices. November 01, 2023 EkoParty 2023: Hackea el planeta Buenos Aires, Argentina GitHub se enorgullece de patrocinar EkoParty 2023, la 19.a edición de la conferencia de EkoParty, y de contribuir a la competencia Capture the Flag. Visítanos en el stand de GitHub y disfruta los recursos a continuación para ver cómo GitHub puede impulsar su programa de seguridad de aplicaciones con un enfoque impulsado por la comunidad. October 22-24, 2023 The DEVOPS Conference 2023 Stockholm, Sweden & Copenhagen, Denmark The DEVOPS Conference is a DevOps event powered by Eficode, the leading DevOps company. Eficode has proudly organized this conference for 10 years, sharing knowledge and approaches to software development and contributing to the larger DevOps community in Europe. The conference takes place every year, traditionally bringing together software industry professionals and higher management across a variety of companies and different geographical locations. The conference has not only been a platform for knowledge sharing and business, but also a way to stay close and connected to like-minded people, despite the circumstances. October 19-20, 2023 NDC Porto 2023 Porto, Portugal NDC Porto 2023 will be an in-person event, held 16-20 October 2023 at the Alfandega conference centre in Porto. It's a five-day event comprised of 2-days deep-dive workshops, followed by 3 conference days with multiple simultaneous tracks. October 4-6, 2023 Devoxx Belgium 2023 Antwerp, Belgium Devoxx Belgium 2023 will build on the immense success of the previous year, which attracted over 3,200 attendees, this five-day technology conference is set to exceed expectations. Last year, the entire ticket allocation was gone in an astonishing 5 minutes and 2 seconds! September 18-19, 2023 Infobip Shift Zadar, Croatia Infobip Shiftis a 2-day multistage hybrid conference dedicated to people passionate about software, continuing the tradition of delivering interactive, engaging, and exciting content. Expect multiple tracks, learn from extraordinary minds, engage in virtual experiences, prospect from exhibit hall, and expand your network on afterparties. Everything brought to you by Infobip and Shift. August 9-10, 2023 Black Hat USA 2023 Las Vegas, USA Black Hat is the most technical and relevant information security event series in the world. For more than 25 years, Black Hat Briefings have provided attendees with the very latest in information security research, development, and trends in a strictly vendor-neutral environment. These high-profile global events and Trainings are driven by the needs of the security community, striving to bring together the best minds in the industry. Black Hat inspires professionals at all career levels, encouraging growth and collaboration among academia, world-class researchers, and leaders in the public and private sectors. July 28-29, 2023 WeAreDevelopers World Congress Berlin 2023 Berlin, Germany WeAreDevelopers World Congress Berlin 2023 is considered by many as the world's flagship event for developers. It is not just another developer conference - it is a totally different and astonishing experience with focus on the people, on developers, on you. July 18-19, 2023 WeAreDevelopers World Congress Berlin 2024 Berlin, Germany WeAreDevelopers World Congress Berlin 2024 is considered by many as the world's flagship event for developers. It is not just another developer conference - it is a totally different and astonishing experience with focus on the people, on developers, on you. July 3-5, 2023 DevBcn 2023 Barcelona, Spain The Barcelona Developers Conference 2023 (former JBCNConf) is multidisciplinary conference made for Developers and by Developers, to learn and share on the different modern software technologies used across the companies. June 27, 2023 DevSecCon24 2023 Virtual DevSecCon24 2023 offers 24 hours of non-stop DevSecOps action! This free virtual event brings together experts and practitioners from the DevOps, development, and security communities for a full day of learning, networking, and collaboration. Discover and define the best practices, processes, and tooling that make secure software possible. May 16, 2023 OWASP AppSec Israel 2023 Tel Aviv, Israel OWASP AppSec Israel Conference** is the largest conference in Israel for application security, and regularly draws hundreds of participants. But AppSecIL is not just for security experts! Developers, testers, architects, product designers, and managers will attend this year. Everyone involved with the software lifecycle is welcome, regardless of type of software, website, mobile app, or any other type of application. May 02, 2023 DevOpsDays Copenhagen Copenhagen, Denmark DevOpsDays Copenhagen** is very excited to announce will be coming back on May 2nd & 3rd 2023! This is your chance to be part of the global DevOps community, learn, and make new acquaintances. April 28, 2023 DevOpsDays Cáceres Cáceres, Spain DevOpsDays Cáceres is a unique opportunity to share experiences in two days of talks, presentations, expert panels and networking with practitioners from Spain and the world. March 9, 2023 NullCon Berlin 2023 Berlin, Germany Nullcon since inception in 2010 has been successfully running the annual security conference in Goa. To give that same zeal & experience to our international community, they organized the 1st ever edition of Nullcon at Berlin in April 2022, and came back in 2023. The focus of the Conference is to bring in the elite security researchers showcasing their offensive & defensive security technology to share exceptional insights on "neXt Big Thing in Security". February 02, 2022 CloudNative SecurityCon North America 2023 Seattle, WA CloudNative SecurityCon North America 2023** is a two-day conference that brings together security practitioners, developers, and operators to discuss the latest trends and technologies in cloud native security. The conference features keynotes, technical talks, and interactive workshops. November 15, 2022 Open Source Monitoring Conference (OSMC) Nuremberg, Germany OSMC is the annual meeting of international monitoring experts, where future trends and objectives are set. Learn which monitoring and observability solutions are available and how they can best be integrated with other tools! The three-day event comprises up to four workshops on the first day, followed by 2-3 technical tracks on the second and third day. November 02, 2022 EkoParty 2022: Enter the metaverse Buenos Aires, Argentina With 83 millions developers, GitHub is the the complete developer platform to build, scale, and deliver secure software. Now in its eighth year, GitHub’s bug bounty program makes GitHub’s products and users more secure and has paid out over $1.5 million to researchers since 2016. Check out some of the blog posts we’ve published about this journey and help us by submitting a bug or two! September 15, 2022 SEC-T Security Conference Stockholm, Sweden SEC-T is an affordable, non-profit, English speaking, two days, single track information security/hacking conference taking place in late summer every year in Stockholm, Sweden. At SEC-T we focus on providing our audience with high-quality talks and in-depth “QnA” with speakers. SEC-T is a conference where you can feel safe from sales pitches and marketing presentations as we have a large focus on our speakers’ research and first-person accounts. May 31, 2022 DevOpsDays Zurich 2022 Zurich, Switzerland Devopsdays is a worldwide series of technical conferences covering topics of software development, IT infrastructure operations, and the intersection between them. Each event is run by volunteers from the local area. March 12, 2021 - 5pm CET LiveQL episode 2: The Rhino in the room Virtual We often see the same types of bugs repeated in code. What if we could detect an entire bug class and report all of its occurrences at once? What if we could automate this detection for any Pull Request so we can catch bugs before they ever enter your code? September 24-26, 2020 Eko2020 Online: Ekoparty's 16th edition Buenos Aires, Argentina With 83 millions developers, GitHub is the the complete developer platform to build, scale, and deliver secure software. Now in its eighth year, GitHub’s bug bounty program makes GitHub’s products and users more secure and has paid out over $1.5 million to researchers since 2016. Check out some of the blog posts we’ve published about this journey and help us by submitting a bug or two! July 15, 2020 GitHub Security Virtual Meetup Virtual (CET Timezone) July 07, 2020 - 11am PDT LiveQL episode 1: finding non-intuitive string manipulation vulnerabilities in C code Virtual We often see the same types of bugs repeated in code. What if we could detect an entire bug class and report all of its occurrences at once? What if we could automate this detection for any Pull Request so we can catch bugs before they ever enter your code? May 7, 2020 Workshop: Finding security vulnerabilities in JavaScript with CodeQL Virtual (US Timezone) CodeQL is GitHub's expressive language and engine for code analysis, which allows you to explore source code to find bugs and security vulnerabilities. During this beginner-friendly workshop, you will learn to write queries in CodeQL and find known security vulnerabilities in open source JavaScript projects. May 7, 2020 Workshop: Finding security vulnerabilities in Java with CodeQL Virtual (US Timezone) CodeQL is GitHub's expressive language and engine for code analysis, which allows you to explore source code to find bugs and security vulnerabilities. During this beginner-friendly workshop, you will learn to write queries in CodeQL and find known security vulnerabilities in open source Java projects. April 23, 2020 GitHub Security Virtual Meetup Virtual (US Timezone) The GitHub Security meetup is a great opportunity to connect with other security researchers and developers to discuss all things security! Offense, defense, variant analysis, vulnerability impact, and security triage workflows ... we welcome it all! March 5-7, 2020 RootedCon Madrid, Spain In his talk "Encontrando 0days en 2020" (in Spanish), Antonio Maldonado will review the different techniques that are being used today to find "0days" in software, and the advances that have occurred in recent years in this field. February 14-15, 2020 OffensiveCon Berlin, Germany Saturday 15th of February from 8 to 10 am, Agustin Gianni will put on his Mc Hammer parachute pants for February 1-2, 2020 FOSDEM’20 Brussels, Belgium During the FOSDEM week-end, we’ll be in Brussels, happy to meet with Open Source maintainers who want to collaborate with Security Researchers, to make their project more secure. Contact @GHSecurityLab on twitter if you want to chat! January 31-February 1, 2020 HCon Madrid, Spain The purpose of the talk is to introduce the different techniques that can be used to find 0day vulnerabilities in Open Source software (at both static and dynamic level). January 22, 2020 GitHub Security Meetup San Francisco, CA, USA The GitHub Security meetup is a great occasion to connect with other security researchers or developers, by discussing all things security, sharing tips and tricks for writing CodeQL queries, discussing variant analysis and other security research techniques, integrating with developer and security response workflows, and more. To keep this community open and welcoming, please read our Code of Conduct . Product Features Security Team Enterprise Customer stories The ReadME Project Pricing Resources Roadmap Compare GitHub Platform Developer API Partners Atom Electron GitHub Desktop Support Docs Community Forum Professional Services GitHub Skills Status Contact GitHub Company About Blog Careers Press Inclusion Social Impact Shop GitHub Inc. © 2024 Terms Privacy Sitemap What is Git? Manage Cookies Do not share my personal information | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#reverting-to-development-or-live | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://www.devcycle.com/features/api | DevCycle API | DevCycle Product Solutions Resources Pricing Docs Book Demo Login Create Account REMOTELY CREATE, UPDATE, & MANAGE FEATURE FLAGS Automate Your Feature Flags With Our APIs Build custom integrations and remotely manage, create, and update your feature flags using our APIs. Never leave your workflow again. Explore Docs Create Account FLEXIBLE API FUNCTIONS FOR EVERY WORKFLOW Tailored functionality to fit your custom workflow via our APIs Automate feature flags, set pre-requisite user targeting logic, analyze data, and more. Explore Docs Full Remote Control Create and manage flag states without leaving your workflow. Update and modify business logic for user targeting on the fly. Streamlined Workflows Build custom visualizations and integrate DevCycle into any of your existing feature management processes quickly and easily. Faster Iteration Create automations to copy feature flag attributes across environments and pull DevCycle feature flag data into your data warehouse. MANAGE EXPERIMENTS VIA API Manage multivariate flags and experiments at scale Optimize feature performance through rapid iteration with experiments and multivariate flags right from your workflow Create Account Modify User Targeting DevCycle lets you immediately add or remove users as flag evaluation requirements change. Variation Control Route users through different variations based on prerequisite business logic. Manage Rollouts Control the percentage distribution of any flag or experiment via API. Duplicate Flag Attributes Duplicate feature flags and experiments across projects and environments. Footer DevCycle What are Feature Flags? OpenFeature Create a Free Account Request a Demo Pricing Resources Documentation SDKs APIs Integrations Blog Contact Support Company About Us Careers Terms of Service Security & Compliance Privacy Policy Contact Us Discord X GitHub LinkedIn Bluesky © 2026 DevCycle All rights reserved. | 2026-01-13T08:49:34 |
http://electron.atom.io/ | Build cross-platform desktop apps with JavaScript, HTML, and CSS | Electron Skip to main content Electron Docs API Blog Tools Electron Forge Electron Fiddle Community Governance Showcase Resources Releases English English Deutsch Español Français 日本語 Português Русский 中文 Search Build cross-platform desktop apps with JavaScript, HTML, and CSS Get Started → Why Electron? Powered by the web Electron embeds Chromium and Node.js to bring JavaScript to the desktop. Cross-platform Electron apps run natively on macOS, Windows, and Linux across all supported architectures. Open to all Electron is an open-source project under the OpenJS Foundation maintained by an active community of contributors. Stable Electron's bundled Chromium build ensures that your app has a stable rendering target with all the newest web platform features. Secure Electron releases major versions in lockstep with Chromium so you get security fixes as soon as they are available. Extensible Use any package from the rich npm ecosystem, or write your own native add-on code to extend Electron. Trusted by best-in-class apps Popular consumer and rock-solid enterprise apps use Electron to power their desktop experiences. Desktop development made easy Electron takes care of the hard parts so you can focus on the core of your application. Native graphical user interfaces Interact with your operating system's interfaces with Electron's main process APIs. Customize your application window appearance, control application menus , or alert users through dialogs or notifications . Automatic software updates Send out software updates to your macOS and Windows users whenever you release a new version with Electron's autoUpdater module , powered by Squirrel . Application installers Use community-supported tooling to generate platform-specific tooling like Apple Disk Image (.dmg) on macOS, Windows Installer (.msi) on Windows, or RPM Package Manager (.rpm) on Linux. App store distribution Distribute your application to more users. Electron has first-class support for the Mac App Store (macOS), the Microsoft Store (Windows), or the Snap Store (Linux). Crash reporting Automatically collect JavaScript and native crash data from your users with the crashReporter module. Use a third-party service to collect this data or set up your own on-premise Crashpad server. Use the tools you love With the power of modern Chromium, Electron gives you an unopinionated blank slate to build your app. Choose to integrate your favourite libraries and frameworks from the front-end ecosystem, or carve your own path with bespoke HTML code. React Vue.js Next.js Tailwind CSS Bootstrap Three.js Angular TypeScript webpack Playwright Testing Library Sass Electron Forge Electron Forge is a batteries-included toolkit for building and publishing Electron apps. Get your Electron app started the right way with first-class support for JavaScript bundling and an extensible module ecosystem. Get started Source code $ npm init electron-app@latest my-app ✔ Locating custom template: "base" ✔ Initializing directory ✔ Preparing template ✔ Initializing template ✔ Installing template dependencies Direct download Installation If you want to figure things out for yourself, you can install the Electron package directly from the npm registry. For a production-ready experience, install the latest stable version. If you want something a bit more experimental, try the prerelease or nightly channels. Stable Prerelease Nightly $ npm install --save-dev electron@latest # Electron 39.2.7 # Node 22.21.1 # Chromium 142.0.7444.235 Experiment with the API Electron Fiddle Electron Fiddle lets you create and play with small Electron experiments. It greets you with a quick-start template after opening — change a few things, choose the version of Electron you want to run it with, and play around. Save your Fiddle either as a GitHub Gist or to a local folder. Once pushed to GitHub, anyone can quickly try your Fiddle out by just entering it in the address bar. Download Source code Apps users love, built with Electron Thousands of organizations spanning all industries use Electron to build cross-platform software. 1Password Asana Claude Discord Dropbox Figma Loom GitHub Desktop itch MongoDB Compass Notion Obsidian OOMOL Studio Polypane Postman Signal Slack Splice Screen Studio Trello Twitch VS Code See more Docs Getting Started API Reference Checklists Performance Security Tools Electron Forge Electron Fiddle Community Governance Resources Discord Bluesky X Mastodon Stack Overflow More GitHub Open Collective Infrastructure Dashboard Copyright OpenJS Foundation and Electron contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation , please see our Trademark Policy and Trademark List . Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them. The OpenJS Foundation | Terms of Use | Privacy Policy | Bylaws | Code of Conduct | Trademark Policy | Trademark List | Cookie Policy Hosting and infrastructure graciously provided by | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#live | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/variables-and-variations/variations | Variations | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Variables Variations Variable Defaults Feature Flag Reach Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Variables and Variations Variations On this page Variations Variations are different versions of a Feature. Each Variation can have different values for the Variables associated with the Feature. For example, if you have a Feature that controls a new UI element and a Variable that controls the color of that element, you could have one Variation where the color is blue and another Variation where the color is red. When a user is "Served" a Variation based on the Targeting Rules, the Variable Values the user receives on their devices or as an API response will be the values for the served Variation. Managing Variations To view the Variables and Variations within a Feature, navigate to the 'Variables' section on a Feature page sidebar. This will lead the user to a table containing all of the Variables used by this Feature and all of their values across all Variations. Depending on the Feature type, the default Variations will be pre-set. The most common of which will be the Variations of "Variation OFF" and "Variation ON", with the boolean Variable being set to false and true, respectively. When a user is "Served" a Variation based on the Targeting Rules , the Variable Values the user receives on their devices or as an API response will be the values for the served Variation. Creating a Variation By default, most Feature types within DevCycle will begin with two Variations. At any time, extra Variations can be added by clicking the "Add Variation" button on the Variables section of a Feature. This will allow you to create a new Variation and assign all of the relevant values. Give your new Variation a name as well as a key , as well as its values For each of the current Variables. Variation Name The Variation Name is used for your reference in the DevCycle Dashboard and CLI. Variation Key The Variation key is used for easy reference within the DevCycle SDKs and APIs Variation Value(s) The Variable values will be what the Variable's value will be in SDK and API responses if a targeting rule is targeting those specific Variations. Once this Variation is created, it will become available as an option within the "Serve" dropdown for Targeting Rules . Users who are served this new Variation will receive the Variable Values associated with this new Variation! Updating a Variation A Variation may be editing at any time by clicking the edit icon on the Variation column in the Variables table. Deleting a Variation A Variation may be deleted at any time by clicking the edit icon on the Variation column of the Remote Variables page. Variations that are currently being used in any Enabled environment cannot be deleted. First remove any audience being targeted by this Variation prior to deletion. Edit this page Last updated on Jan 9, 2026 Previous Variables Next Variable Defaults Managing Variations Creating a Variation Updating a Variation Deleting a Variation DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#moving-a-feature-to-completed | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://dev.to/callstacktech/how-to-build-custom-pipelines-for-voice-ai-integration-a-developers-journey-4p7g | How to Build Custom Pipelines for Voice AI Integration: A Developer's Journey - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse CallStack Tech Posted on Jan 11 • Originally published at callstack.tech How to Build Custom Pipelines for Voice AI Integration: A Developer's Journey # ai # voicetech # machinelearning # webdev How to Build Custom Pipelines for Voice AI Integration: A Developer's Journey TL;DR Most voice AI pipelines fail under load because they process STT, LLM, and TTS sequentially—adding 800ms+ latency per turn. Build a streaming architecture that handles partial transcripts, concurrent LLM inference, and audio buffering. Using VAPI's native streaming + Twilio's WebSocket transport, you'll cut latency to 200-300ms and handle barge-in without race conditions. This guide shows the exact event-driven patterns that work in production. Prerequisites API Keys & Credentials You'll need a VAPI API key (generate from dashboard.vapi.ai) and Twilio account credentials (Account SID, Auth Token, phone number). Store these in .env using VAPI_API_KEY , TWILIO_ACCOUNT_SID , TWILIO_AUTH_TOKEN , and TWILIO_PHONE_NUMBER . Runtime & Dependencies Node.js 18+ with npm. Install: axios , dotenv , express (for webhook handling), and twilio SDK. Twilio SDK version 3.80+. System Requirements Linux/macOS/Windows with 2GB+ RAM. Stable internet connection (voice pipelines are latency-sensitive—test on your target network). ngrok or similar tunneling tool for local webhook testing. Knowledge Assumptions Familiarity with REST APIs, async/await patterns, and JSON payloads. Understanding of streaming audio concepts (PCM 16kHz, mulaw encoding) and event-driven architecture. No prior VAPI or Twilio experience required, but basic telephony concepts help. VAPI : Get Started with VAPI → Get VAPI Step-by-Step Tutorial Configuration & Setup Most voice pipelines fail because developers treat VAPI and Twilio as a unified system. They're not. VAPI handles the AI layer (STT → LLM → TTS). Twilio handles telephony (SIP, PSTN routing). Your server is the integration layer that bridges them. Architecture Decision Point: VAPI-native calls : Use VAPI's phone number system. VAPI manages the entire call lifecycle. Twilio-native calls : Use Twilio's phone numbers. Stream audio to your server, then pipe to VAPI's speech pipeline. Pick ONE. Mixing both creates double-billing and race conditions. flowchart LR A[Caller] -->|PSTN| B[Twilio Number] B -->|WebSocket Stream| C[Your Server] C -->|Audio Chunks| D[VAPI STT] D -->|Text| E[LLM] E -->|Response| F[VAPI TTS] F -->|Audio| C C -->|Audio Stream| B B -->|PSTN| A Enter fullscreen mode Exit fullscreen mode Architecture & Flow Critical: VAPI does NOT expose raw STT/TTS endpoints. The documentation shows assistant creation and phone call management, not standalone speech APIs. This means: Create an assistant via VAPI dashboard (defines voice, model, prompt) Trigger calls programmatically or via phone number VAPI handles the entire speech pipeline internally What breaks in production: Developers try to build custom STT → LLM → TTS flows by calling non-existent /transcribe or /synthesize endpoints. Those don't exist in VAPI's API. You configure the pipeline, not control it step-by-step. Step-by-Step Implementation 1. Create Assistant (VAPI Dashboard) Navigate to VAPI dashboard → Assistants → Create. Configure: // Assistant config (set via dashboard, not API in basic setup) { " name " : " Twilio Bridge Agent " , " model " : { " provider " : " openai " , " model " : " gpt-4 " , " temperature " : 0.7 }, " voice " : { " provider " : " 11labs " , " voiceId " : " 21m00Tcm4TlvDq8ikWAM " // Rachel voice }, " transcriber " : { " provider " : " deepgram " , " model " : " nova-2 " , " language " : " en " }, " firstMessage " : " Hey, this is the support line. What can I help with? " } Enter fullscreen mode Exit fullscreen mode Why this matters: The assistant ID becomes your pipeline reference. All calls route through this config. 2. Bridge Twilio to VAPI (Server-Side) // server.js - Express server bridging Twilio → VAPI const express = require ( ' express ' ); const WebSocket = require ( ' ws ' ); const app = express (); app . post ( ' /voice/incoming ' , ( req , res ) => { // Twilio webhook when call arrives const twiml = `<?xml version="1.0" encoding="UTF-8"?> <Response> <Connect> <Stream url="wss:// ${ req . headers . host } /media-stream" /> </Connect> </Response>` ; res . type ( ' text/xml ' ); res . send ( twiml ); }); const wss = new WebSocket . Server ({ noServer : true }); wss . on ( ' connection ' , ( ws ) => { console . log ( ' Twilio stream connected ' ); // Note: VAPI doesn't expose raw WebSocket endpoints for custom streaming // You must use VAPI's phone number system OR build a full proxy // This example shows the Twilio side only ws . on ( ' message ' , ( message ) => { const msg = JSON . parse ( message ); if ( msg . event === ' media ' ) { const audioChunk = Buffer . from ( msg . media . payload , ' base64 ' ); // In production: Forward to VAPI assistant via their call API // VAPI handles STT → LLM → TTS internally } }); }); app . listen ( 3000 ); Enter fullscreen mode Exit fullscreen mode Reality check: VAPI's API (per documentation) focuses on assistant/call management, not raw audio streaming. For true custom pipelines, you'd need to: Use VAPI's phone number (simplest - VAPI manages everything) OR build a complete proxy with separate STT/TTS services (Deepgram, ElevenLabs directly) 3. Trigger Calls Programmatically The documentation references using "Vapi's REST API to create assistants programmatically" but doesn't show the exact endpoint in the provided context. Based on standard patterns: // Note: Endpoint inferred from standard API patterns async function initiateCall ( phoneNumber , assistantId ) { try { const response = await fetch ( ' https://api.vapi.ai/call ' , { method : ' POST ' , headers : { ' Authorization ' : `Bearer ${ process . env . VAPI_API_KEY } ` , ' Content-Type ' : ' application/json ' }, body : JSON . stringify ({ assistantId : assistantId , customer : { number : phoneNumber } }) }); if ( ! response . ok ) { throw new Error ( `HTTP ${ response . status } : ${ await response . text ()} ` ); } return await response . json (); } catch ( error ) { console . error ( ' Call initiation failed: ' , error ); throw error ; } } Enter fullscreen mode Exit fullscreen mode Error Handling & Edge Cases Twilio stream disconnects: Implement reconnection logic with exponential backoff. Twilio streams timeout after 60s of silence. Audio buffer desync: Twilio sends mulaw 8kHz. If VAPI expects PCM 16kHz, you'll get garbled audio. Verify codec compatibility in assistant config. Latency spikes: Mobile networks add 200-800ms jitter. Set transcriber.endpointing to 1500ms minimum to avoid cutting off speakers. Testing & Validation Use Twilio's test credentials to simulate calls without charges. Monitor VAPI dashboard for assistant response times. Target: <800ms end-to-end latency (STT + LLM + TTS). System Diagram Audio processing pipeline from microphone input to speaker output. graph LR A[Microphone] --> B[Audio Buffer] B --> C[Voice Activity Detection] C -->|Voice Detected| D[Speech-to-Text] C -->|Silence| E[Error Handling] D --> F[Intent Detection] F --> G[External API Call] G -->|Success| H[Response Generation] G -->|Failure| I[API Error Handling] H --> J[Text-to-Speech] J --> K[Speaker] E --> L[Retry Logic] I --> L L --> B Enter fullscreen mode Exit fullscreen mode Testing & Validation Local Testing with ngrok Most voice AI pipelines break in production because developers skip local webhook testing. Expose your Express server using ngrok to receive real Twilio and VAPI events before deploying: ngrok http 3000 # Copy the HTTPS URL (e.g., https://abc123.ngrok.io) Enter fullscreen mode Exit fullscreen mode Update your Twilio webhook URL to https://abc123.ngrok.io/webhook/twilio and VAPI server URL to https://abc123.ngrok.io/webhook/vapi . This will bite you: ngrok URLs expire after 2 hours on free tier. Production requires static domains. Webhook Validation Test the complete pipeline with curl before connecting real calls. Validate that your server handles Twilio's CallStatus events and VAPI's streaming audio chunks: // Test Twilio webhook locally const testPayload = { CallSid : ' test-call-123 ' , CallStatus : ' in-progress ' , From : ' +15555551234 ' }; // Verify your Express handler processes this app . post ( ' /webhook/twilio ' , ( req , res ) => { console . log ( ' Received: ' , req . body . CallStatus ); // Should log "in-progress" if ( ! req . body . CallSid ) { return res . status ( 400 ). send ( ' Missing CallSid ' ); } res . status ( 200 ). send ( twiml . toString ()); }); Enter fullscreen mode Exit fullscreen mode Check response codes: 200 = success, 400 = malformed payload, 500 = your server crashed. Twilio retries failed webhooks 3 times with exponential backoff. If you see duplicate events in logs, your endpoint is timing out (must respond within 5 seconds). Real-World Example Barge-In Scenario User calls in. Agent starts: "Thank you for calling. To better assist you today, I'll need to collect some—" User interrupts: "I just need my account balance." This is where 90% of custom pipelines break. The TTS buffer is still playing. The STT fires a partial transcript. Your LLM generates a response while the old audio is still queued. Result: agent talks over itself, user hears garbled audio, call drops. Here's what actually happens in the event stream: // Twilio sends audio chunks via WebSocket wss . on ( ' connection ' , ( ws ) => { let audioBuffer = []; let isProcessing = false ; ws . on ( ' message ' , ( msg ) => { const data = JSON . parse ( msg ); if ( data . event === ' media ' ) { // User is speaking - detect barge-in if ( isProcessing ) { // CRITICAL: Flush TTS buffer immediately audioBuffer = []; ws . send ( JSON . stringify ({ event : ' clear ' , streamSid : data . streamSid })); isProcessing = false ; } // Queue audio for STT processing audioBuffer . push ( Buffer . from ( data . media . payload , ' base64 ' )); // Process when we hit 20ms chunks (320 bytes at 16kHz) if ( audioBuffer . length >= 320 ) { processSTT ( audioBuffer , ws ); audioBuffer = []; } } }); }); async function processSTT ( audioChunk , ws ) { // Send to VAPI for transcription (streaming endpoint) const response = await fetch ( ' https://api.vapi.ai/transcribe/stream ' , { method : ' POST ' , headers : { ' Authorization ' : ' Bearer ' + process . env . VAPI_API_KEY , ' Content-Type ' : ' audio/pcm ' }, body : audioChunk }); const partial = await response . json (); if ( partial . isFinal ) { // User finished speaking - generate response isProcessing = true ; generateResponse ( partial . text , ws ); } } Enter fullscreen mode Exit fullscreen mode Event Logs Real production logs from a barge-in scenario (timestamps in ms): [T+0ms] TTS: Streaming "To better assist you today..." [T+1200ms] VAD: Speech detected (threshold: 0.5) [T+1205ms] STT: Partial "I just" [T+1210ms] BUFFER: Flushed 2.3s of queued TTS audio [T+1450ms] STT: Partial "I just need my" [T+1680ms] STT: Final "I just need my account balance" [T+1685ms] LLM: Processing user intent [T+2100ms] TTS: New response queued Enter fullscreen mode Exit fullscreen mode The 5ms gap between VAD detection and buffer flush? That's your race condition window. If STT fires a final transcript before the flush completes, you get double audio. Edge Cases Multiple rapid interruptions: User says "wait—no, actually—" three times in 2 seconds. Your pipeline needs a debounce mechanism or you'll fire three LLM calls ($0.06 wasted, 600ms added latency). let debounceTimer = null ; function handlePartialTranscript ( text , ws ) { clearTimeout ( debounceTimer ); debounceTimer = setTimeout (() => { if ( text . length > 5 ) { // Ignore "um", "uh" processSTT ( text , ws ); } }, 300 ); // Wait 300ms for user to finish thought } Enter fullscreen mode Exit fullscreen mode False positives from background noise: Coffee shop calls trigger VAD on espresso machine hiss. Solution: Increase VAD threshold from 0.3 to 0.6 for noisy environments, or use Twilio's noise suppression filter ( noiseSuppression: true in the WebSocket config). Network jitter on mobile: 4G → WiFi handoff mid-call causes 200-800ms audio gaps. Your buffer logic must handle out-of-order packets. Use sequence numbers in the msg payload to reorder chunks before STT processing. Common Issues & Fixes Race Conditions in Streaming STT Most custom pipelines break when partial transcripts arrive faster than your LLM can process them. The symptom: duplicate responses or the bot talking over itself. // WRONG: No guard against concurrent processing wss . on ( ' message ' , async ( msg ) => { const partial = JSON . parse ( msg ); await processSTT ( partial . text ); // Race condition if called twice }); // CORRECT: Lock-based processing with queue let isProcessing = false ; const transcriptQueue = []; wss . on ( ' message ' , async ( msg ) => { const partial = JSON . parse ( msg ); transcriptQueue . push ( partial . text ); if ( isProcessing ) return ; // Skip if already processing isProcessing = true ; while ( transcriptQueue . length > 0 ) { const text = transcriptQueue . shift (); try { await processSTT ( text ); } catch ( error ) { console . error ( ' STT processing failed: ' , error ); // Don't block queue on single failure } } isProcessing = false ; }); Enter fullscreen mode Exit fullscreen mode Why this breaks: Twilio sends partial transcripts every 100-200ms. If your LLM takes 800ms to respond, you'll have 4-8 partials queued. Without a lock, all fire simultaneously → 4-8 duplicate API calls → bot repeats itself. Audio Buffer Not Flushing on Barge-In When users interrupt mid-sentence, old TTS audio keeps playing because the buffer wasn't cleared. This happens in 40% of custom pipelines. Fix: Flush audioBuffer immediately when voice activity detection fires: function handlePartialTranscript ( data ) { if ( data . event === ' speech-start ' ) { audioBuffer . length = 0 ; // Clear buffer instantly clearTimeout ( debounceTimer ); // Cancel pending TTS } } Enter fullscreen mode Exit fullscreen mode Webhook Signature Validation Failures Twilio webhooks fail silently if you don't validate X-Twilio-Signature . Production issue: 15% of calls drop due to replay attacks or misconfigured proxies. Quick fix: Always validate before processing: const crypto = require ( ' crypto ' ); app . post ( ' /webhook/twilio ' , ( req , res ) => { const signature = req . headers [ ' x-twilio-signature ' ]; const url = `https:// ${ req . headers . host }${ req . url } ` ; const params = req . body ; const expectedSig = crypto . createHmac ( ' sha1 ' , process . env . TWILIO_AUTH_TOKEN ) . update ( Buffer . from ( url + Object . keys ( params ). sort (). map ( k => k + params [ k ]). join ( '' ), ' utf-8 ' )) . digest ( ' base64 ' ); if ( signature !== expectedSig ) { return res . status ( 403 ). send ( ' Invalid signature ' ); } // Process webhook }); Enter fullscreen mode Exit fullscreen mode Complete Working Example This is the full production server that bridges VAPI's voice AI pipeline with Twilio's telephony infrastructure. Copy-paste this into server.js and you have a working voice agent that handles inbound calls, processes speech in real-time, and manages the complete audio lifecycle. // server.js - Production Voice AI Pipeline Server const express = require ( ' express ' ); const WebSocket = require ( ' ws ' ); const crypto = require ( ' crypto ' ); const app = express (); app . use ( express . json ()); app . use ( express . urlencoded ({ extended : true })); // Session state management with TTL cleanup const sessions = new Map (); const SESSION_TTL = 300000 ; // 5 minutes // Twilio inbound call handler - generates TwiML to connect WebSocket app . post ( ' /voice/inbound ' , ( req , res ) => { const { CallSid , From } = req . body ; // Initialize session state sessions . set ( CallSid , { from : From , audioBuffer : [], isProcessing : false , transcriptQueue : [], created : Date . now () }); // Auto-cleanup session after TTL setTimeout (() => sessions . delete ( CallSid ), SESSION_TTL ); // TwiML response connects call to our WebSocket const twiml = `<?xml version="1.0" encoding="UTF-8"?> <Response> <Connect> <Stream url="wss:// ${ req . headers . host } /media/ ${ CallSid } " /> </Connect> </Response>` ; res . type ( ' text/xml ' ). send ( twiml ); }); // WebSocket server for real-time audio streaming const wss = new WebSocket . Server ({ noServer : true }); wss . on ( ' connection ' , ( ws , callSid ) => { const session = sessions . get ( callSid ); if ( ! session ) { ws . close ( 1008 , ' Session not found ' ); return ; } let debounceTimer = null ; ws . on ( ' message ' , async ( msg ) => { const data = JSON . parse ( msg ); // Handle incoming audio chunks from Twilio if ( data . event === ' media ' ) { const audioChunk = Buffer . from ( data . media . payload , ' base64 ' ); session . audioBuffer . push ( audioChunk ); // Debounced STT processing - prevents race conditions clearTimeout ( debounceTimer ); debounceTimer = setTimeout (() => processSTT ( session , ws ), 300 ); } // Handle call lifecycle events if ( data . event === ' stop ' ) { sessions . delete ( callSid ); ws . close (); } }); ws . on ( ' error ' , ( error ) => { console . error ( `WebSocket error for ${ callSid } :` , error ); sessions . delete ( callSid ); }); }); // STT processing with partial transcript handling async function processSTT ( session , ws ) { if ( session . isProcessing || session . audioBuffer . length === 0 ) return ; session . isProcessing = true ; const audioData = Buffer . concat ( session . audioBuffer ); session . audioBuffer = []; // Flush buffer try { // Send audio to VAPI for transcription // Note: This demonstrates the integration pattern - actual VAPI streaming // would use their WebSocket protocol documented in their SDK guides const partial = await handlePartialTranscript ( audioData ); if ( partial . isFinal ) { session . transcriptQueue . push ( partial . text ); // Send to LLM and synthesize response await generateAndStreamResponse ( session , ws , partial . text ); } } catch ( error ) { console . error ( ' STT processing failed: ' , error ); } finally { session . isProcessing = false ; } } // Webhook signature validation (production security requirement) app . post ( ' /webhook/vapi ' , ( req , res ) => { const signature = req . headers [ ' x-vapi-signature ' ]; const url = `https:// ${ req . headers . host }${ req . url } ` ; const expectedSig = crypto . createHmac ( ' sha256 ' , process . env . VAPI_SERVER_SECRET ) . update ( url + JSON . stringify ( req . body )) . digest ( ' base64 ' ); if ( signature !== expectedSig ) { return res . status ( 401 ). json ({ error : ' Invalid signature ' }); } const { event , call } = req . body ; // Handle call lifecycle events if ( event === ' call-ended ' ) { sessions . delete ( call . id ); } res . json ({ received : true }); }); // HTTP server upgrade for WebSocket connections const server = app . listen ( process . env . PORT || 3000 ); server . on ( ' upgrade ' , ( req , socket , head ) => { const callSid = req . url . split ( ' / ' ). pop (); wss . handleUpgrade ( req , socket , head , ( ws ) => { wss . emit ( ' connection ' , ws , callSid ); }); }); console . log ( ' Voice AI pipeline server running on port ' , process . env . PORT || 3000 ); Enter fullscreen mode Exit fullscreen mode Run Instructions Prerequisites: Node.js 18+ Twilio account with phone number configured VAPI account with API key ngrok or production domain with SSL Environment variables (create .env ): VAPI_API_KEY = your_vapi_key_here VAPI_SERVER_SECRET = your_webhook_secret_here TWILIO_ACCOUNT_SID = your_twilio_sid TWILIO_AUTH_TOKEN = your_twilio_token PORT = 3000 Enter fullscreen mode Exit fullscreen mode Start server: npm install express ws dotenv node server.js Enter fullscreen mode Exit fullscreen mode Configure Twilio webhook: Point your Twilio phone number's voice webhook to https://your-domain.com/voice/inbound . The server handles the complete pipeline: Twilio streams audio → WebSocket buffers chunks → STT processes with debouncing → LLM generates response → TTS streams back to caller. Session state prevents race conditions, signature validation blocks unauthorized webhooks, and TTL cleanup prevents memory leaks. FAQ Technical Questions What's the actual difference between streaming STT and batch processing in a voice pipeline? Streaming STT (speech-to-text) processes audio chunks in real-time as they arrive, firing onPartialTranscript callbacks within 100-300ms. Batch processing waits for the entire call to finish, then transcribes. Streaming wins because you get partial results immediately—your LLM can start thinking while the user is still talking. Batch adds 2-5 seconds of latency after the user stops speaking. For voice agents, streaming is non-negotiable. VAPI's transcriber with endpointing: true handles this natively; Twilio requires you to buffer audioChunk data and send it to a third-party STT service (Google Cloud Speech, Deepgram, etc.) via WebSocket. How do I prevent the bot from talking over the user (barge-in)? Barge-in requires three pieces: (1) Voice Activity Detection (VAD) to know when the user starts speaking, (2) interrupt logic to stop TTS mid-sentence, (3) state management to prevent race conditions. VAPI handles VAD natively with transcriber.endpointing set to true and a threshold (default 0.3, increase to 0.5 for noisy environments). When VAD fires, set isProcessing = false to cancel the current TTS buffer flush. Twilio requires manual VAD—use a library like @vapi/vad or implement silence detection by monitoring audioChunk amplitude. The killer mistake: not flushing the TTS buffer when interruption happens, so old audio plays after the user speaks. Why does my pipeline have 500ms+ latency spikes? Three culprits: (1) Network jitter —webhook calls to your server timeout after 5 seconds; use async processing instead of blocking. (2) Buffer bloat — audioBuffer grows unbounded; implement a circular buffer with max size 16KB. (3) Synchronous LLM calls —if processSTT waits for the full LLM response before returning, you block STT. Use concurrent processing: fire the LLM call async, return partial results immediately. Measure with console.time() at each stage (STT → LLM → TTS). Most latency lives in the LLM, not the pipeline. Performance What's the maximum concurrent calls my pipeline can handle? Depends on your infrastructure. Each call needs: 1 WebSocket connection (minimal), 1 session object in memory (~2KB), 1 LLM API call (rate-limited by your provider). If you're using VAPI, they handle concurrency; you just pay per minute. If you're building on Twilio, each concurrent call spawns a new express route handler. Node.js can handle ~1000 concurrent connections on a single 2GB instance before memory pressure. Use sessions cleanup with SESSION_TTL (e.g., 30 minutes) to prevent memory leaks. Monitor with Object.keys(sessions).length in production. How do I reduce TTS latency? TTS is your slowest component (200-800ms per sentence). Three strategies: (1) Streaming TTS —request audio chunks as the LLM generates tokens, not after the full response. (2) Parallel processing —while TTS generates audio for sentence N, the LLM generates sentence N+1. (3) Voice caching —if the bot repeats phrases ("Thank you for calling"), cache the audio. VAPI's native TTS handles streaming; Twilio requires you to implement chunking in your server code. Platform Comparison VAPI vs. Twilio for voice pipelines—which should I pick? VAPI : Managed service. You configure assistant with model, voice, transcriber; VAPI handles the pipeline. Latency: 150-300ms end-to-end. Cost: $0.10-0.30/min. Best for: rapid prototyping, low-ops teams. Downside: less control over audio processing. Twilio : Raw infrastructure. You build the pipeline yourself using WebSocket , audioChunk handling, and external ST Resources Twilio : Get Twilio Voice API → https://www.twilio.com/try-twilio VAPI Documentation: Official API Reference – Complete endpoint specs, assistant configuration, webhook event schemas, and streaming protocols for voice AI pipelines. Twilio Voice API: Twilio Docs – TwiML syntax, WebSocket audio streams, call control, and real-time media handling for SIP integration. GitHub Reference: VAPI + Twilio Integration Examples – Production-grade code samples for event-driven audio processing and low-latency STT/TTS pipelines. References https://docs.vapi.ai/quickstart/phone https://docs.vapi.ai/quickstart/introduction https://docs.vapi.ai/workflows/quickstart https://docs.vapi.ai/assistants/quickstart https://docs.vapi.ai/quickstart/web https://docs.vapi.ai/tools/custom-tools https://docs.vapi.ai/chat/quickstart https://docs.vapi.ai/server-url/developing-locally https://docs.vapi.ai/assistants/structured-outputs-quickstart Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse CallStack Tech Follow We skip the "What is AI?" intro fluff. If you're shipping voice agents that handle real users, this is for you. Joined Dec 2, 2025 More from CallStack Tech How to Set Up an AI Voice Agent for Customer Support in SaaS Applications # ai # voicetech # machinelearning # webdev Build Your Own Voice Stack with Deepgram and PlayHT: A Practical Guide # ai # voicetech # machinelearning # webdev Build Your Own Voice Stack with Deepgram and PlayHT: A Developer's Journey # ai # voicetech # machinelearning # webdev 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#changing-status | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://golf.forem.com/code-of-conduct#attribution | Code of Conduct - Golf Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Golf Forem Close Code of Conduct Last updated July 31, 2023 All participants of DEV Community are expected to abide by our Code of Conduct and Terms of Service , both online and during in-person events that are hosted and/or associated with DEV Community. Our Pledge In the interest of fostering an open and welcoming environment, we as moderators of DEV Community pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Our Standards Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Referring to people by their pronouns and using gender-neutral pronouns when uncertain Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Citing sources if used to create content (for guidance see DEV Community: How to Avoid Plagiarism ) Following our AI Guidelines and disclosing AI assistance if used to create content Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances The use of hate speech or communication that is racist, homophobic, transphobic, ableist, sexist, or otherwise prejudiced/discriminatory (i.e. misusing or disrespecting pronouns) Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Plagiarizing content or misappropriating works Other conduct which could reasonably be considered inappropriate in a professional setting Dismissing or attacking inclusion-oriented requests We pledge to prioritize marginalized people's safety over privileged people's comfort. We will not act on complaints regarding: 'Reverse' -isms, including 'reverse racism,' 'reverse sexism,' and 'cisphobia' Reasonable communication of boundaries, such as 'leave me alone,' 'go away,' or 'I'm not discussing this with you.' Someone's refusal to explain or debate social justice concepts Criticisms of racist, sexist, cissexist, or otherwise oppressive behavior or assumptions Enforcement Violations of the Code of Conduct may be reported by contacting the team via the abuse report form or by sending an email to support@dev.to . All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Further details of specific enforcement policies may be posted separately. Moderators have the right and responsibility to remove comments or other contributions that are not aligned to this Code of Conduct or to suspend temporarily or permanently any members for other behaviors that they deem inappropriate, threatening, offensive, or harmful. If you agree with our values and would like to help us enforce the Code of Conduct, you might consider volunteering as a DEV moderator. Please check out the DEV Community Moderation page for information about our moderator roles and how to become a mod. Attribution This Code of Conduct is adapted from: Contributor Covenant, version 1.4 Write/Speak/Code Geek Feminism 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#status-categories | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/targeting/targeting-overview | Targeting Overview | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Targeting Overview Audiences Custom Properties Random Variations Scheduling & Rollouts Randomize using a Custom Property EdgeDB (Stored Custom Properties) Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Targeting Targeting Overview On this page Targeting Overview Targeting rules can be used to grant Features to specific user groups, incrementally roll out Features for monitoring, or create and test different Feature configurations. Already understand the targeting essentials? Be sure to check out our advanced targeting documentation which covers topics like: Audiences Custom Properties Random Variations Rollouts Self-Targeting Targeting Properties Targeting works by evaluating rules you configure against the properties of a user you've identified in a DevCycle SDK. The properties available on a user are a combination of ones that are automatically tracked by the SDK, ones that you set yourself in the SDK but are built into the platform, and custom properties that you define to extend the built-in Targeting properties. Below is a summary of the properties built-in to the platform, and how to specify them in the SDK: Property Name Purpose How to Set User ID Unique identifier for this user. Also used for distribution and rollout randomization. Set "user_id" property User Email Email associated to this user Set "email" property App Version Version of the application currently in use. Set "appVersion" property or automatically set by Mobile SDK Platform Platform type (eg. Android, Web, C# etc.) Automatically set by SDK Platform Version Platform version specific to the current platform (eg. Android OS versio) Automatically set by SDK Device Model Device model specific to the current device (eg. iPhone 12) Automatically set by Client-side SDK Country Country the user is located in. Must be a valid 2 letter ISO-3166 country code Set "country" property In addition to these built-in properties, you can specify any other property that suits your needs using the Custom Properties Feature. Here is an example of a user object being passed to an SDK with these properties set: const user = { user_id : 'user1' , email : ' [email protected] ' , country : 'CA' , customData : { isBetaUser : true , subscriptionPlan : 'premium' , } } devcycleClient . identifyUser ( user ) With properties defined and being sent from an SDK, you can now use them to create Targeting Rules in the DevCycle dashboard. Defining a Targeting Rule Targeting Rules are made up of a few different fields that will allow you define who you'd like to deliver your Feature to, when you'd like to do so, and which Variation you'd like to serve them. More details below. The Targeting Status. Targeting ON or Targeting OFF, this is what defines if the rules will be used to deliver a Variation of a Feature to users within a specific Environment. If Targeting is OFF, no users within the Environment will receive the Feature at all, regardless of the Targeting Rules set. Use this to enable or disable the Feature for an Environment. This is also best used as a killswitch to instantly disable a Feature. The Targeting Rule Name. A human-readable identifier for the Targeting Rule. This name is optional and can be used for debugging and informational purposes when understanding why certain users received certain Variations. The Rule Definition. This is the logic that defines who will receive the specified Variation of the Feature, based on various properties that you may set from the DevCycle User (e.g. User ID, User Email, Audience, Platform, etc). The many ways to create a definition are outlined below. What Users will be Served. This is what defines the Variation that a user who fulfills the rule will receive. Different rules may receive different Variations. Additionally, a random distribution for A/B testing of Variations can be set. A Rollout Schedule for the Feature. When the Schedule is set to the default (None), the Targeting Rule will be enabled once the Environment is enabled. Using Schedule, a specific date/time can be set to release your Feature at a certain time, additionally providing the option to include a Gradual or Phased Rollout of the Feature. More details can be found in Schedules and Rollouts . Example: Targeting specific users. Let's say for example there is a brand new Feature that is meant to only roll out to internal QA users for the time being. There are numerous ways to achieve this, however for this example, only known user ids or emails will be used. In this example, the users with a user ID of "john" and "victor" will receive the Variation of "Variation ON" of this Feature on the Development Environment. This type of direct user targeting is great for numerous things such as adding users to QA versions of a Feature, inviting beta users to a Feature, or simply targeting your personal user ID for development purposes. Rule Definition Definitions are created by adding a property, a comparator, and a set of values that you'd want to compare the property to. Properties can be automatically populated through DevCycle SDKs, but in most cases, will usually set by yourself on the SDK. Multiple properties can be used at once allowing for AND operations for more complex combinations of properties. Each property is typed and has its own set of comparators available to it. Those comparators are as follows: Operator Supported Types Action is string, number, boolean exact match on one of the values is not string, number, boolean exact match on none of the values contains string substring match does not contain string substring does not match starts with string substring match does not start with string substring does not match ends with string substring match does not end with string substring does not match exists string, number, boolean null check does not exist string, number, boolean null check equals, does not equal number math comparison greater than, less than number math comparison less than or equal to, greater than or equal to number math comparison info Disabling an Environment's Targeting Rules will remove all users in that Environment from the Feature, and users will receive the code defaults. Targeting Rule Evaluation Order Often during development, developers might want to create specific Targeting Rules which target only themselves as they work on a Feature and not the greater audience. Or, there may be a larger Feature with many personalized Variations which could require multiple Targeting Rules in order to accurately segment your users. In either case, this section will help you ensure that you understand the order in which Targeting Rules are evaluated when working with multiple Targeting Rules. Evaluation Order Targeting Rules are evaluated in a top-down order. A User may match the definition of multiple Targeting Rules, however, they will only receive the first Targeting Rule that they match for in the given Environment. This situation allows you to group specific users into seeing a Variation, for example: Meet our user Victor, he lives in Canada and has a @devcycle.com email address. We do not want him, or other @devcycle.com users, to see our Secret Getaway Feature. Victor has a neighbor, John that doesn’t have a @devcycle.com email address. We want all our other Canadian users to see our Secret Getaway Feature. Victor also has several friends that live in Norway, and we want to show all our users in Norway the Secret Getaway Feature. In this situation, here’s how we can set up our Targeting Rule for the Secret Getaway Feature. We define our first Targeting Rule to target users in Canada with email addresses containing @devcycle.com to NOT see the Secret Getaway Feature. Then we can add a second Targeting Rule by clicking the “Add Targeting Rule" button. Lastly, we'll update this Targeting Rule to make sure that other users in Canada (i.e. those without @devcycle.com emails) and all users in Norway (i.e. Country is Norway) DO see the Secret Getaway Feature. The above will then satisfy the requirements of the defined situation. Managing a Targeting Rule Targeting rules can be seen in the individual Feature page by selecting the relevant Environment under Users & Targeting in the Manage Feature 🚩 menu on the left hand side of the screen. From here you will be able to enable or disable the specific Targeting Rules by clicking the Targeting ON or Targeting OFF toggle. Creating a Targeting Rule tip Looking to use DevCycle to help you QA a new Feature? Be sure to check out Self-Targeting . On the Features dashboard page, select Users & Targeting from the left hand menu and choose which Environment it should apply to. If a Feature is toggled ON for an Environment, the rules defined within the Environment will be followed. Once the Targeting Rule is defined, the next step is to determine what Variation users targeted by this rule should receive. Note: The available Variations will be determined by the chosen Feature Type, however, these can be modified and more Variations can be added at any time. To choose the Variation for this targeted audience, use the "Serve" dropdown and choose the desired Variation. When the Environment is enabled, and if a user fulfills the Targeting Rule, they will then be served that Variation and its associated variable values. Updating A Targeting Rule Targeting Rules can be updated on the dashboard anytime by changing the relevant input for the Environment in question and click the Save button in the upper right-hand corner of the screen. Reordering Targeting Rules In these cases, you can very simply reorder any Targeting Rule by clicking the arrows on the side of the rule and moving it up or down. Saving this Feature will then cause the next evaluation of a variable for all users to respect the new targeting order (after the config has been updated for client-side SDKs). Copying a Targeting Rule A lot of teams use Staging Environments to not only QA Features, but to also validate a Feature Flag's targeting. For teams that do this, you want to be able to "promote" Targeting Rules as-is between Environments, so you can be confident that what was validated in Staging is what will be defined in Production. To copy a Targeting Rule, just click the Copy Targeting Rule button at the top right of the Targeting Rule you want to copy. This opens a confirmation modal where you can select the Environment you want to copy that Targeting Rule to. Once confirmed, the new Targeting Rule will be added to the Environment, with all aspects identical to the copied rule other than the name which will be appended with (Copy). Once copied you can make edits to the name or re-order the priority of rules as needed and save the Feature when you are ready. Creating an Audience from a Targeting Rule Audiences are designed to make the creation and management of Targeting Rules easier by making complex filters reusable. Sometimes Targeting Rules can get complex over time before you think to use an audience. If you find that a rule definition has gotten complex and you want to make it an Audience so it can be easily reused elsewhere you can just create an Audience right from the rule. To create an Audience, just click the Create An Audience button at the top right of the Targeting Rule in question. This opens a modal where you can confirm the details such as name, key and description. When you confirm, the new Audience will be opened in a new tab where you can edit it further, as needed. note The new Audience will not automatically replace the definition in the Targeting Rule it was created from. Deleting a Targeting Rule Select the trash can icon on the right-hand side of the relevant Environment Targeting Rules to delete the rule and click Save to apply the changes. Edit this page Last updated on Jan 9, 2026 Previous Feature Flag Reach Next Audiences Targeting Properties Defining a Targeting Rule Rule Definition Targeting Rule Evaluation Order Managing a Targeting Rule Creating a Targeting Rule Updating A Targeting Rule Copying a Targeting Rule Creating an Audience from a Targeting Rule Deleting a Targeting Rule DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://golf.forem.com/t/walkvsride#main-content | Walkvsride - Golf Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Golf Forem Close # walkvsride Follow Hide The eternal debate: discussing the pros and cons of walking vs. using a cart Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#viewing-features-by-status-kanban-view | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://forem.com/codeideal | Shayan - Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Shayan Indie maker. Building tools at the intersection of design, code, and creativity. TypeScript, UX, and open source enthusiast. Joined Joined on Jun 12, 2025 github website More info about @codeideal Badges 2 Week Community Wellness Streak Keep the community conversation going! Post at least 2 comments for 2 straight weeks and unlock the 4 Week Badge. Got it Close 1 Week Community Wellness Streak For actively engaging with the community by posting at least 2 comments in a single week. Got it Close Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Post 14 posts published Comment 15 comments written Tag 5 tags followed DLMan :: the download manager I always wanted Shayan Shayan Shayan Follow Jan 8 DLMan :: the download manager I always wanted # programming # opensource # rust # tauri Comments Add Comment 2 min read Want to connect with Shayan? Create an account to connect with Shayan. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in I Built DLMan, the Modern Download Manager I always needed! Shayan Shayan Shayan Follow Jan 6 I Built DLMan, the Modern Download Manager I always needed! Comments Add Comment 3 min read I Fixed Blender's Render Output Paths ( Because it SUCKS! ) Shayan Shayan Shayan Follow Dec 15 '25 I Fixed Blender's Render Output Paths ( Because it SUCKS! ) # showdev # blender # opensource 2 reactions Comments 1 comment 1 min read I Built OpenFields ( Free Alternative to ACF for WP ) Shayan Shayan Shayan Follow Dec 11 '25 I Built OpenFields ( Free Alternative to ACF for WP ) # showdev # wordpress # tooling # opensource 2 reactions Comments 2 comments 3 min read I made Lexkit ( Rich Text Editor I wish existed !) Shayan Shayan Shayan Follow Nov 2 '25 I made Lexkit ( Rich Text Editor I wish existed !) Comments Add Comment 1 min read I Created CFMan, Cloudflare Wrangler Multi Account Manager Shayan Shayan Shayan Follow Oct 12 '25 I Created CFMan, Cloudflare Wrangler Multi Account Manager # showdev # serverless # cli # tooling 5 reactions Comments 3 comments 3 min read Why I chose Lexical over Tiptap Shayan Shayan Shayan Follow Sep 24 '25 Why I chose Lexical over Tiptap # discuss # react # javascript # tooling Comments Add Comment 2 min read Building a Type-Safe Rich Text Editor in Next.js (with Lexical & Lexkit) Shayan Shayan Shayan Follow Sep 24 '25 Building a Type-Safe Rich Text Editor in Next.js (with Lexical & Lexkit) Comments Add Comment 2 min read ShadCN Rich Text Editor with Lexical + Lexkit Shayan Shayan Shayan Follow Sep 23 '25 ShadCN Rich Text Editor with Lexical + Lexkit # showdev # typescript # tooling # react 2 reactions Comments 1 comment 2 min read I made Lexical Easy! ( Lexkit: Rich Text Editor story ) Shayan Shayan Shayan Follow Sep 18 '25 I made Lexical Easy! ( Lexkit: Rich Text Editor story ) # showdev # tooling # react # typescript 3 reactions Comments 4 comments 2 min read Build Full-Featured Rich Text Editors in React ( Lexical + Lexkit ) Shayan Shayan Shayan Follow Sep 16 '25 Build Full-Featured Rich Text Editors in React ( Lexical + Lexkit ) 1 reaction Comments 1 comment 3 min read Best Rich Text Editor for react in 2025 Shayan Shayan Shayan Follow Sep 16 '25 Best Rich Text Editor for react in 2025 1 reaction Comments Add Comment 2 min read I Built LexKit: A Modern, Type-Safe Rich Text Editor for React Shayan Shayan Shayan Follow Sep 14 '25 I Built LexKit: A Modern, Type-Safe Rich Text Editor for React # showdev # react # opensource # typescript 8 reactions Comments 1 comment 3 min read From Pain to Plugin: Export Figma Prototypes as MP4/GIF — Free & Open Source Shayan Shayan Shayan Follow Jun 12 '25 From Pain to Plugin: Export Figma Prototypes as MP4/GIF — Free & Open Source 2 reactions Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — Your community HQ Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:33 |
https://forem.com/new/productivity#main-content | New Post - Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Close Join the Forem Forem is a community of 3,676,891 amazing members Continue with Apple Continue with Facebook Continue with GitHub Continue with Google Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to Forem? Create account . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — Your community HQ Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#permissions-for-status-changes | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/experimentation/feature-experimentation | Feature Experimentation | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Feature Experimentation Creating and Managing Metrics How Metrics are Calculated Video Tutorial: Experiment Setup Tutorial: Funnel Experiment Account Management Security and Guardrails Testing and QA Extras Examples Platform Experimentation Feature Experimentation On this page Feature Experimentation Overview At DevCycle we believe that Experimentation should be a part of the natural lifecycle of all Features. So no matter the Feature type selected, can be experimented on. Experiments can be as simple as comparing any target audiences against a Metric, or can be fully randomized A/B tests using statistical methodologies. This article outlines why and how to run and analyze Experiments on your Features within DevCycle. Why Experiment Experimentation is crucial for testing modifications to your product. You may investigate which changes would result in the best outcomes. It's also known as split testing or A/B testing, or comparative analysis depending on who you ask. Experimentation can be used to test new Features, design changes, marketing campaigns, or anything that could potentially impact how a product or service is used. You may want to experiment on any of these things and more: Validate to make sure application performance remains the same or improves. Validate in a controlled way whether code changes increase or decrease error rates. Confirm that a new Feature is driving more conversions or revenue. Measure real impacts of Features on SLAs and SLOs. You've likely been doing "Experimentation" without knowing it. Whenever you release a new feature or service, compare the before and after (and during). When combined with Features, DevCycle can give direct Metrics on a feature's performance during a release, allowing you to react and make changes accordingly. Of course, with this in mind, your team isn't restricted to a simple on or off approach. Using DevCycle, a team can have numerous Variations which are released and tested at the same time, giving an even deeper view with more flexibility. Using Experimentation To run an Experiment on any Feature, all you need is two things: At least two Variations served to your users At least one Metric defined and attached to your Feature Comparing Multiple Variations The primary concept of an Experiment is the need to have at least two different experiences to compare performances. There are several ways in DevCycle to run multiple experiences for users. We go into depth on this in our Targeting documentation . To get started with your first Feature Experiment, it is best to keep it simple and run a basic A/B test comparing two Variations, one control and one treatment Variation, delivered randomly to all your users. To set this up, create a targeting rule in Production that delivers to All Users and serves Variations randomly with percentages set equally at 50% against your first Variation, and 50% against your second Variation. Adding Metrics to Your Feature info Experimentation relies on Custom Events . Experimentation is available to all customers on any plan. However, to perform Experiments, events must be sent to DevCycle to calculate Metrics. These events are added to your existing plan. To learn more, read about our pricing , or contact us. Now that you have two segments receiving different experiences, the only other thing you need to run an Experiment is a Metric to evaluate the comparative performance of those experiences. To add a Metric to your Feature, click “Experiment Results” under the “Data & Results” section on the sidebar of the Feature editing page. Click the “Choose a Metric” dropdown. This will bring up the option to add a Metric that has already been created in the Project or to create a new one. For the creation of new Metrics check out our documentation here . Once you have Metrics in your Project, all you need to do is: Select a Metric you want to use to judge the performance of your Experiment Set the Variation that you want to use as your control Variation Now that you have a Metric added and a control Variation selected, the performance of the Experiment will be tracked over time. The performance of the treatment Variation compared to the control Variation will be tracked by the Difference and Statistical Significance indicator in real-time as the Experiment progresses. Any number of Metrics can be added to a Feature for analysis, keep clicking “Choose a Metric” and add pre-existing or create new Metrics as needed. Determining a Winner The most important part of an Experiment is determining a winner. The length of time an Experiment needs to run to determine a winner varies depending on the overall traffic, the observed conversion rate, and the size of the difference in conversion or values between the Variations. Typically Experiments should be run for a minimum of 1-2 weeks to achieve valid statistical significance with a good amount of time to get a proper cross-section of your user base. Given the time it takes, your team should generally avoid early analysis and create a process by which an Experiment runs with no review of results until a pre-determined amount of time has passed. Once this time has passed, the charts and graphs for any added Metrics can be reviewed to determine which Variation performed best. When Metrics are created, you define if a decrease or an increase is the targeted improvement. Our results graphs take this into account and show clearly if the Metrics have driven either positive or negative results. The charts also provide guidance on if statistical significance has been achieved by displaying the following indicators. Statistical Significance Definition ✅ Positive Significant Result ❌ Negative Significant Result ... Non-Significant Result Positive Results Negative Results Experimentation using a Custom Property for Randomization info For documentation on this functionality outside of the context of experimentation you can check out our documentation dedicated to this topic here . DevCycle typically uses the User ID as the primary key for Feature rollouts and randomization. However, in certain scenarios, Features you release are intended to be rolled out to a cohort of users vs an individual user. For example, a new feature in a B2B platform might impact an entire Organization rather than a single user within that Organization. In such cases, you can randomize and rollout by using a Custom Property. What are Experiments that Randomize Using a Custom Property? When running an Experiment where you randomize using a Custom Property, the Experiment is applied to a set of users (those who possess a Custom Property) rather than individual users. This means that every user who has that Custom Property will experience the same Feature Variation, such as being part of the control or the test variant. This approach allows you to assess the impact of changes on the group as a whole. Groups in DevCycle are defined using Custom Properties. These groups could be companies, tenants, geographic locations, or any set of users sharing common characteristics. How to Randomize Using a Custom Property in Experiments To set this up, create a Targeting Rule that serves a Random Distribution of the Variations. When you select Random Distribution , Randomize Using field will appear at the bottom of the Targeting Rule under the Schedule section. The dropdown will populate with all existing Custom Properties. Select the Custom Property you wish to use for your random distribution. If you are both randomizing distribution and using a gradual rollout of some form, the Custom Property will be used for both forms of randomization, keeping distribution sticky based off of that property. Risks to Experimentation There are several risks to be aware of when randomizing your Experiments in this way: Less Statistical Power: In Experiments with randomization using a Custom Property, each group is treated as a single data point, reducing the overall statistical power of the Experiment. For example, a platform might have millions of users but only a few thousand companies using it. This typically requires running these types of Experiments for a longer period to achieve statistically significant results. Higher Randomization Risk: There's a greater risk of improper randomization when assigning Custom Properties to control or test variants. With fewer data points, any imbalance can significantly skew the results. For example, if a new pricing model is tested across different companies, an imbalance in the distribution of company sizes could lead to inaccurate conclusions about the model’s effectiveness. Fewer User-Level Insights: Custom Property-targeted Experiments provide insights at an aggregate level, potentially obscuring user-level behaviors and preferences. For example, a new feature might increase overall usage within a company, but it might not reveal which specific roles or user types are most engaged with the feature. Randomization Collisions: Our random distribution system works on a murmurhash, where we purposely limit User IDs to less than 200 characters to reduce the risk of collisions. If you randomize off of a Custom Property where the values are over 200 characters there is a potential for collisions that could impact randomization. Regardless of the type of risk, if you are worried about the statistical validity of your Experiment you should make sure that there is both a significant number of groups as well as good balanced stratification across the groups that you're testing against. These two factors protect you against the most substantial risks. Edit this page Last updated on Jan 9, 2026 Previous Stale Feature Notifications Next Creating and Managing Metrics Overview Why Experiment Using Experimentation Comparing Multiple Variations Adding Metrics to Your Feature Determining a Winner Experimentation using a Custom Property for Randomization What are Experiments that Randomize Using a Custom Property? How to Randomize Using a Custom Property in Experiments Risks to Experimentation DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://dev.to/fabianfrankwerner/css-vs-tailwind-css-i-built-the-same-home-page-with-both-23mi | CSS vs Tailwind CSS - I built the same home page with both - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Fabian Frank Werner Posted on Dec 19, 2025 • Edited on Dec 27, 2025 CSS vs Tailwind CSS - I built the same home page with both # tailwindcss # beginners # css # webdev If you go to any social media right now, I promise you will find developers screaming at each other about CSS. On one side, you have the Purists. They believe in the sanctity of semantic HTML, the Separation of Concerns, and the "Cascading" nature of style sheets. On the other side, you have the Pragmatists. The Tailwind cult. They believe that naming classes is a waste of time and that CSS is better when it looks like a crossword puzzle that exploded in your HTML. But arguments are cheap. Code is real. So, to actually understand the difference, I built the exact same project with both. We are recreating the Google Dark Mode homepage. It looks simple—a logo, a search bar, a footer—but it’s actually a perfect stress test for layout systems, theming, and component architecture. We aren't doing a "Winner takes all" battle today. We are going to dissect the experience of building this. We’ll look at the setup, the mental models, the ugly parts of the code, and finally, a file-size comparison that actually shocked me. By the end, you’ll know exactly why you should pick one over the other. Let's get into it. Chapter 1: The Setup Let’s start with the setup. This is where the first philosophical divide happens. With Vanilla CSS, the "stack" is non-existent. You create a file. You link it. You write code. There is zero friction. You are writing the language the browser actually understands. Tailwind, however, brings the baggage. You need Node.js. You’re initializing a config file. You’re setting up a build process to watch your files. For a single HTML page like this, Tailwind feels like bringing a construction crane to build a Lego set. But—and this is a big but—once that crane is set up, the speed changes. In Vanilla CSS, you are working in the Global Scope. The "Cascade" is powerful, but it's also dangerous. If I define a generic button class, it affects every button on the site. Tailwind doesn't rely on the cascade. It relies on a System. And that system starts with configuration. Chapter 2: The Reset But before we draw a single pixel, we have to talk about the "Reset." This is Step 0, and it catches almost everyone off guard. In standard CSS, the browser uses a default box model where adding padding increases the width of the element. If you have a 100px box and add 20px of padding, it becomes 140px wide. It makes layout math a nightmare. So, in my Vanilla CSS version, the very first thing I have to do is manually tell the browser: "Stop trying to help me." border-box ensures that if I say a box is 100px, it stays 100px, even if I stuff it with padding. * { margin : 0 ; padding : 0 ; box-sizing : border-box ; } Enter fullscreen mode Exit fullscreen mode In Tailwind, I didn't write a single line of reset code. Why? Because Tailwind injects a system called "Preflight" automatically. It flattens the browser styles, applies border-box globally, and removes all default margins. It gives you a truly blank canvas. In Vanilla CSS, you have to build that canvas yourself. Chapter 3: The Colors Now, let's talk about Theming. We need to match Google's specific dark mode grays. In my Vanilla CSS build, I use CSS Variables. :root { --bg-primary : #1f1f1f ; --bg-element : #303134 ; --link-color : #8ab4f8 ; } Enter fullscreen mode Exit fullscreen mode This is clean. It’s dynamic. If I change --bg-primary to red in the DevTools, the whole site updates instantly. But , there are no guardrails. As a developer, I can easily break the design system. So the CSS file allows me to be sloppy. In Tailwind, I have to be more disciplined. I open tailwind.config.js and extend the theme. colors: { google: { bg: "#1f1f1f" , element: "#303134" , // ... } } Enter fullscreen mode Exit fullscreen mode This config file acts as a "Contract." When I go to my HTML, IntelliSense kicks in. If I type bg-goo... , it suggests bg-google-bg . It prevents "Magic Numbers." You aren't just painting pixels; you are referencing a system. For large teams, this is the difference between a consistent UI and a messy one. Chapter 4: The Layout Now, let's look at the actual layout code. This is where we see the concept of "Context Switching." In Vanilla CSS, I have this markup ( <div class="nav-right"> ) that reads like English. But as a developer, I don't know what .nav-right does . Is it a grid? Is it absolute positioning? To find out, I have to switch tabs to style.css and find the class. .nav-right { display : flex ; align-items : center ; } Enter fullscreen mode Exit fullscreen mode Okay, so this is Flexbox. We are aligning the items along the cross-axis. In Vanilla CSS, the structure and the layout logic CSS are physically separated. You have to hold the connection in your head. Now look at Tailwind. <div class="nav-right flex items-center gap-4"> I admit, it looks "noisy." But look at gap-4 . In the old days of CSS, spacing items was hard. We used margin-right on everything except the last child. Tailwind exposes the modern CSS gap property as a utility. gap-4 puts 1rem of space between every child. I can visualize exactly how this component behaves just by reading the class string. This is "Locality of Behavior." I am styling the element while I build it. Chapter 5: The Problem Now, I hear the Backend Developers screaming at the screen: "But what if I have a button? Do I have to copy-paste bg-blue-500 text-white rounded px-4 py-2 on every single button? That violates DRY principles!" I hear you! Now, this is the "Google Search" buttons. We have two of them. In my Tailwind HTML, yes, it looks repetitive. <button class= "bg-google-element hover:border-gray-500 ..." > Google Search </button> <button class= "bg-google-element hover:border-gray-500 ..." > I'm Feeling Lucky </button> Enter fullscreen mode Exit fullscreen mode If I want to change the padding on both, I have to edit two places. This sucks. But Tailwind has a solution for this called @apply . If you really want to clean this up, you can go to your input CSS file and do this: .btn-google { @apply bg-google-element text-google-textMain px-4 py-2 rounded hover : border-gray-500 ; } Enter fullscreen mode Exit fullscreen mode Now, in your HTML, you just use class="btn-google" . So you can use classes in Tailwind. But usually, you shouldn't. In modern development (like with React, Vue, Svelte), you wouldn't make a CSS class. You would make a Component . You’d make a <Button /> component that holds these styles internally. Therefore Tailwind works best when paired with a component framework, not just raw HTML. Chapter 6: The Specifics Let's get technical. The Search Bar is the most complex component because it has specific pixel dimensions and hover states. In CSS, I handle the hover state using a Pseudo-class. .search-container :hover { background-color : var ( --bg-element-hover ); box-shadow : 0 1px 6px 0 rgba ( 23 , 23 , 23 , 0.5 ); } Enter fullscreen mode Exit fullscreen mode This relies on Specificity . The browser calculates that this rule is more specific than the base rule, so it applies it. In Tailwind, we do this inline. And this is where we see a feature called Arbitrary Values. Look at this class: h-[46px] . And this one: shadow-[0_1px_6px_0_rgba(23,23,23,0.5)] . Tailwind haters love to point at this and say, "See! That's ugly!" And yeah, it is ugly. But it’s also incredibly powerful. I needed a 46px height to match the Google reference. I didn't have to create a new class or add an inline style attribute. I just told the Tailwind Just-In-Time compiler: "Hey, make me a class for 46 pixels." And it did. I didn't have to worry about specificity wars or overriding other styles. It just works. Chapter 7: The Compiler Speaking of the compiler, let's get "Under the Hood." How does Tailwind actually work? When I type a class like h-[46px] for the search bar, what is happening? Tailwind is not a static CSS file. It is a program written in JavaScript. When you save your HTML file, the Tailwind "Just-In-Time" (JIT) compiler scans your code. It uses Regular Expressions (Regex) to look for class names. It sees h-[46px] . It parses that string, realizes you want a height of 46 pixels, and generates a CSS rule on the fly: .h-\[46px\] { height: 46px; } This is why you can leave your CSS file empty. The compiler is writing the CSS for you, based on what you asked for in the HTML. It also handles Specificity for you. In Vanilla CSS, if I have an ID and a class, they fight. In Tailwind, because everything is a utility class, everything has the same "weight." You rarely run into those moments where you write a style and nothing changes because some hidden rule is overriding it. Chapter 8: The Paradox Okay, we have two identical looking websites now. But what are we shipping to the user? We always hear that "Tailwind is small." So I ran the build, and here are the results… Vanilla CSS: 5 KB. Tailwind Output: 16 KB. Wait. The "optimized" tool is 300% larger ? Yes, and here is the nuance. Tailwind's 16KB includes that "Preflight" reset we talked about in Chapter 2. It’s a reset sheet that normalizes all the browser quirks so your site looks the same on Chrome and Safari. That’s a base cost. Vanilla CSS is "Pay for what you use." I only wrote the lines I needed, so it’s tiny. However , this is a single page. If I added 50 more pages to this app... The Vanilla CSS file would grow Linearly . Every new page means new classes. The Tailwind file would flatten out (Logarithmic). Why? Because I’m reusing flex , items-center , and text-white everywhere. So while Vanilla wins the sprint, Tailwind wins the marathon. Chapter 9: The Verdict So, which one should you choose? If you are a beginner, look me in the eyes: Do not start with Tailwind. You need to feel the pain of the Box Model. You need to understand how Flexbox axes work. You need to understand position: relative vs absolute . If you jump straight to Tailwind, you are learning a framework, not the web. But, if you are building a real product, a dashboard, or working on a team? Tailwind CSS has won me over. The "ugliness" of the HTML is a small price to pay for the development speed. It allows you to come back to a project 6 months later and know exactly what is happening without hunting through a 5,000-line stylesheet. And if you want to see me compare React vs Svelte or something else entirely, let me know in the comments. Don't forget to cursor: pointer that like button. See you in the next one. Top comments (17) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Massimo Artizzu Massimo Artizzu Massimo Artizzu Follow Senior web developer 🔥 ~ conf speaker 🎙️ ~ loves science 🔭, art 🎨, rugby 🏉 ~ reinventing a better wheel 🎡 Location Italy Education Mathematics Work Consultant at Antreem Joined Jan 12, 2017 • Dec 22 '25 • Edited on Dec 23 • Edited Dropdown menu Copy link Hide If you are a beginner, [...] do not start with Tailwind . Good, good! May I add some lines? If you are mid level, do not start with Tailwind . If you are a senior, do not start with Tailwind . If you are a guru, do not start with Tailwind . In short, do not start with Tailwind ever , period. You call CSS users "purists" versus Tailwind's "pragmatists", but let's see what Tailwind's adoption means pragmatically : of course, readability goes down the drain; for every .css files that goes from 150 kb to 40, every html page goes up from 20 kb to 40; and don't start with "HTML can be compressed very well": CSS can too; CSS files are aggressively cached by browsers, HTML are not. it's never Tailwind alone: here comes a plethora of plugins and packages, from your IDE to runtime, that you have to install just to get a grip on the mess; debugging with dev tools becomes an awful experience; RUM data becomes gibberish... I can go on for hours. Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Fabian Frank Werner Fabian Frank Werner Fabian Frank Werner Follow Hello, World! Pronouns he/him Joined Jan 6, 2025 • Dec 22 '25 Dropdown menu Copy link Hide Please do, I'm interested in what's left :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Massimo Artizzu Massimo Artizzu Massimo Artizzu Follow Senior web developer 🔥 ~ conf speaker 🎙️ ~ loves science 🔭, art 🎨, rugby 🏉 ~ reinventing a better wheel 🎡 Location Italy Education Mathematics Work Consultant at Antreem Joined Jan 12, 2017 • Dec 23 '25 • Edited on Dec 23 • Edited Dropdown menu Copy link Hide I could honestly write a whole series on the matter, but I fear it could unleash mean reactions from the frontend community. Tailwind fans often show how they get the best from LLMs because they answer using Tailwind basically by default. Problems arise when a new major version of Tailwind comes out, and AI will still give answers based on the old version for months . It already happened. The aid you get from fast prototyping gives the false impression that everything can be assimilated as a fire-and-forget project, thus neglecting maintainability. When you take zero effort in naming a class, you don't think about what meaning or purpose an element has: this seems liberating at first, but in the end this is what happens: we stop thinking about the meaning not only of classes, but of attributes and tag names. Everything becomes a <div> , and DOM size and accessibility suffer; we carry long strings of Tailwind class names around in our runtimes because what we have left is merely a presentational effect, and not a meaning anymore. Wanna learn from the masters? Tailwind's own website is a disaster , where you can find class names several thousand characters long because they embed a freaking PNG in base 64! Nobody really know what to do with Tailwind. This is crystal clear when so many devs defy one of the main advantages of using utility classes: not having to name things . Instead, so many use @apply , others pack class names together in "variants" (which you have to name). And in the latter case, it all happens at runtime , which is something we loathed so much in those CSS-in-JS libraries, but now it's acceptable somehow. By the way, @apply will conflict with the upcoming native CSS mixins: which means Tailwind will prove itself to be not future-proof yet again, after Tailwind 3 inability to use @layer freely. Not to mention having to wait for a new major release just to support a new native CSS syntax, which is doubly ludicrous as a feature could be available for months before you could use it, and has been conceived by renowned tech experts and browser representatives, instead of Adam Wathan's capricious unvetted ideas. The result of short-term gain and a lot of advertising has created the most toxic community of klout chasers around something so foundational like CSS, it's honestly disgusting. I swear I've seen the exact same post about a "revolutionary technique" with Tailwind posted on LinkedIn by some self-appointed "senior full-stack development architect" or whatever that's actually a copy of a post by David Khourshid on Twitter. And apropos of that, Tailwind's bracket syntax is a giant middle finger to whoever conceived CSS as a structured language to express complex relationships, to the consolidated best practice to avoid magic numbers, and to the usual convention of having a specificity of 0.1.0 for utility classes. Let's not forget classes have been conceived more than a quarter of a century ago, when we didn't have anything better: now we do and we can be more expressive and effective without using classes altogether (I've been doing this for years now). Enough? Like comment: Like comment: 5 likes Like Thread Thread Fabian Frank Werner Fabian Frank Werner Fabian Frank Werner Follow Hello, World! Pronouns he/him Joined Jan 6, 2025 • Dec 24 '25 Dropdown menu Copy link Hide Thank you for taking the time! With such strong insightful opinions I would love if you published more posts, even reasonable rants are very entertaining content. Do you have an active blog or newsletter I can check out? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Nicholas Stimpson Nicholas Stimpson Nicholas Stimpson Follow Full Stack Software Engineer or jobbing programmer. Location Luton, England Joined May 24, 2019 • Dec 19 '25 Dropdown menu Copy link Hide "The Vanilla CSS file would grow Linearly." Only if you want every page to look entirely different from every other page on your web site, or you're really bad at choosing class names. On any normal site, if the class names are well-chosen to reflect the semantic domain space of the site's content, many of the classes you use on your home page are going to be reused across all the other pages. The second page you create will add a few extra classes and some of these too will be used across many subsequent pages. The growth curve will be a very similar shape to Tailwind's. Like comment: Like comment: 5 likes Like Comment button Reply Collapse Expand Fabian Frank Werner Fabian Frank Werner Fabian Frank Werner Follow Hello, World! Pronouns he/him Joined Jan 6, 2025 • Dec 19 '25 Dropdown menu Copy link Hide Thanks for pointing that out. In the end it comes down to personal preference, I guess... Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Tracy Gilmore Tracy Gilmore Tracy Gilmore Follow After my first contact with a computer in the 1980's, I taught myself to program in BASIC and Z80 assembler. I went on to study Computer Science and have enjoyed a long career in Software Engineering. Email tracyg.gilmore+devto@gmail.com Location Somerset, UK Education BSc (Hons) Computer Science Work Software Engineer specialising in web technologies, frontend and full stack (Node & xAMPP) Joined Jul 16, 2017 • Dec 20 '25 Dropdown menu Copy link Hide That is not quite true. CSS is a standard that is widely applicable and will be for years to come. Tailwind, a good as it is, is a skill that might not be applicable in your next project and will some day be replaced by the next shiny new tool. Besides, each additional tool or library is project bloat. Standard web technologies are built into the browser. This also applies to Fetch API v Axios, and I really like Axios. Like comment: Like comment: 4 likes Like Thread Thread Fabian Frank Werner Fabian Frank Werner Fabian Frank Werner Follow Hello, World! Pronouns he/him Joined Jan 6, 2025 • Dec 21 '25 Dropdown menu Copy link Hide True! Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand spO0q spO0q spO0q Follow Practice what you preach Location earth Education working class hero Joined Dec 29, 2019 • Dec 26 '25 • Edited on Dec 26 • Edited Dropdown menu Copy link Hide Tailwind is a system! It's definitely not meant for beginners. Sharp tool! A great use case, though, is when you need a similar system. In this case, it's probably better to rely on this tool than to do it yourself, but even in this case, be aware it's also designed for modern browsers. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Fabian Frank Werner Fabian Frank Werner Fabian Frank Werner Follow Hello, World! Pronouns he/him Joined Jan 6, 2025 • Dec 26 '25 Dropdown menu Copy link Hide True! Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Paul / Appurist Paul / Appurist Paul / Appurist Follow Code monkey since 1984, C++, C#, JavaScript, etc. Location Nova Scotia, Canada Education Acadia University Work Senior Software Engineer (full-stack developer) Joined Nov 9, 2018 • Dec 22 '25 Dropdown menu Copy link Hide Sorry, but the bias on this is obvious. Phrases like "I didn't have to create a new class" hide how simple it is. And your HTML isn't polluted like it is with Tailwind. Take a look at " Why Nue " and remember web development when it was actually web development, not investing a whole learning slope for something that the web doesn't actually use. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Fabian Frank Werner Fabian Frank Werner Fabian Frank Werner Follow Hello, World! Pronouns he/him Joined Jan 6, 2025 • Dec 24 '25 Dropdown menu Copy link Hide Will check out Nue! Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Aryan Choudhary Aryan Choudhary Aryan Choudhary Follow Level up 10x faster Email aryanc1240@gmail.com Location Pune, India Pronouns He/Him Work SDE 1 Joined Nov 5, 2024 • Dec 24 '25 Dropdown menu Copy link Hide Love the nautical-themed comparison! Tailwind CSS might be the trusty compass that keeps your design on course, but Vanilla CSS is the open sea where you chart your own course and learn the ropes. Can't help but wonder about how you handle the trade-off between file size and project complexity in your own work? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Fabian Frank Werner Fabian Frank Werner Fabian Frank Werner Follow Hello, World! Pronouns he/him Joined Jan 6, 2025 • Dec 24 '25 Dropdown menu Copy link Hide Nice ai response Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand 118M8 118M8 118M8 Follow 118M8 helps people spend smarter by showing the true cost of purchases - in hours worked, not pounds. Joined Dec 2, 2025 • Dec 23 '25 Dropdown menu Copy link Hide Good for use Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Fabian Frank Werner Fabian Frank Werner Fabian Frank Werner Follow Hello, World! Pronouns he/him Joined Jan 6, 2025 • Dec 24 '25 Dropdown menu Copy link Hide 🫡 Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Neurabot Neurabot Neurabot Follow Longlife learner. Fall in love with oriented-programming C++/Python. Leading many projects in fields. Location Cameroon Pronouns He Work CEO at valone Joined Feb 27, 2024 • Dec 24 '25 Dropdown menu Copy link Hide Congrats. Like comment: Like comment: 2 likes Like Comment button Reply View full discussion (17 comments) Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Fabian Frank Werner Follow Hello, World! Pronouns he/him Joined Jan 6, 2025 More from Fabian Frank Werner Code Hike in 100 Seconds # webdev # programming # javascript # beginners An Honest Review of Google Antigravity # webdev # programming # ai # beginners JavaScript vs TypeScript - I built the same crypto tracker with both # webdev # javascript # typescript # beginners 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#archived | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://docs.devcycle.com/sdk/server-side-sdks/node/node-bootstrapping | Bootstrapping / Server-Side Rendering | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up SDK Overview SDK Lifecycle SDK Features Client-side SDKS Server-side SDKS Node.js SDK Installation Getting Started Usage OpenFeature Typescript Bootstrapping / SSR Example App NestJS SDK PHP SDK Go SDK Ruby SDK Python SDK Java SDK .NET SDK SDK Proxy Server-side SDKS Node.js SDK Bootstrapping / SSR On this page Bootstrapping and Server-Side Rendering info If you are using Next.js, we recommend using the Next.js SDK instead of this option. When using a server rendering framework such as Remix, Nuxt, or SvelteKit, you will likely be rendering content on the server and sending it to the client for hydration. When feature flagging is involved, you need to make sure that rendering on the server uses the same flag values as the client. It is also important to avoid the performance impact of the initial client-side DevCycle configuration fetch that would normally have to occur when the page is first loaded. To support these use-cases, the Node.js SDK provides functionality for generating client-side configurations on the server, for use during server-side rendering as well as bootstrapping on the client. To use it, you must also have the DevCycle JS Client SDK installed in your server application. Follow the setup docs for that SDK to get started. To enable this feature, initialize a Node.js client on the server and enable client bootstrapping mode: // devcycle.ts import { initializeDevCycle } from '@devcycle/nodejs-server-sdk' export const devcycleClient = await initializeDevCycle ( '<DEVCYCLE_SERVER_SDK_KEY>' , { enableClientBootstrapping : true , } ) . onClientInitialized ( ) This will instruct the SDK to keep a copy of the client configuration up-to-date in addition to the server configuration. Now, call the client's method for obtaining the bootstrapping config, using the user data representing the current request. You should also pass the userAgent from the request, which allows the SDK to determine some built-in attributes about the user: const user = { user_id : 'some user data' } const bootstrapConfig = await devcycleClient . getClientBootstrapConfig ( user , userAgent ) Calling this method will run a fast, local evaluation of your project's Targeting Rules using a cached copy of the configuration. You can expect the same level of performance as with any server-side evaluation. Now pass the result in wherever you initialize your DevCycle client SDK. For example with the React SDK: import { DevCycleProvider } from '@devcycle/react-client-sdk' export default function App ( ) { return ( < DevCycleProvider options = { { sdkKey : bootstrapConfig . clientSDKKey , bootstrapConfig : bootstrapConfig , user : user } } > < TheRestofYourApp /> </ DevCycleProvider > ) } Make sure you also pass the same "user" that was used to obtain the bootstrap config. You must also provide the client SDK key so that the client-side SDK can initialize. The SDK key you should use is available as the sdkKey field of the bootstrap config. Example Here is an example that connects all these pieces in Remix with the React SDK: // app/root.tsx import type { LoaderFunctionArgs } from "@remix-run/node" import { json } from "@remix-run/node" import { DevCycleProvider } from '@devcycle/react-client-sdk' import { devcycleClient } from '../devcycle' export async function loader ( { request , } : LoaderFunctionArgs ) { const user = await getUser ( request ) ; const userAgent = request . headers . get ( 'user-agent' ) ; const config = await devcycleClient . getClientBootstrapConfig ( user , userAgent ) ; return json ( { user , config } ) ; } export default function Component ( ) { const data = useLoaderData < typeof loader > ( ) ; return ( < DevCycleProvider options = { { sdkKey : data . config . clientSDKKey , bootstrapConfig : data . config , user : data . user } } > < TheRestofYourApp /> </ DevCycleProvider > ) ; } Once these pieces are in place, Remix will supply the component with the client configuration for the current user. It can then be provided to the React SDK by passing it to the bootstrapConfig option of the DevCycleProvider . From this point downwards in the component tree, the React SDK will return Variable values from this bootstrapped config during server-side rendering, and will hydrate with the same configuration on the client. To see this in action, check out the Remix bootstrapping example application . Edit this page Last updated on Jan 9, 2026 Previous Typescript Next Example App Example DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://dev.to/ilyarah/how-i-built-the-fastest-ton-memecoin-sniper-alert-bot-golden-memecoin-alert-121h | How I Built the Fastest TON Memecoin Sniper Alert Bot (Golden-Memecoin-Alert) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse ilya rahnavard Posted on Jan 2 How I Built the Fastest TON Memecoin Sniper Alert Bot (Golden-Memecoin-Alert) # webdev # python # blockchain # web3 TON memecoins move insanely fast in late 2025 – early 2026. Most tokens reach peak hype in the first 5–30 minutes after liquidity addition. By the time you see them trending on DexScreener, Telegram channels or Twitter — the move is usually 70–90% over. I got tired of missing entries, so I built Golden-Memecoin-Alert — a focused, low-latency sniper alert system specifically for TON. Repo: https://github.com/ilyarah/Golden-Memecoin-Alert Core Design Goals Detect new Jetton pools within seconds of meaningful liquidity addition Aggressive pre-filtering to remove 90–95% obvious rugs/scams instantly Very high signal-to-noise ratio (quality over quantity) Beautiful, instantly actionable Telegram messages Minimal latency end-to-end ** Architecture (high-level)** TON Center / TonAPI websocket ──► New pool / liquidity tx detector ↓ Pre-filtering engine (5–7 quick checks) ↓ Scoring engine (0–100) + threshold ↓ Async Telegram delivery (aiohttp + python-telegram-bot) ↓ Redis for deduping & rate limiting alerts Enter fullscreen mode Exit fullscreen mode ** Key filtering layers (all executed in <1 second):** Liquidity threshold (configurable, usually ≥$30–50k initial) Creator wallet age + tx history (very young or no history → high risk) Dev wallet concentration after first minutes Sell-tax / honeypot simulation (via quick buy/sell emulation) Early holder distribution (top 5 wallets < 40–50% preferred) Basic social presence check (Telegram group creation near launch) Only tokens passing most filters go to scoring. Scoring Factors (current weights – subject to change) On-chain momentum (volume, buys/sells ratio) → 35% Holder distribution & dev wallet behavior → 25% Social signals (Telegram growth speed) → 20% Risk indicators (tax, honeypot flags) → 15% Time since launch penalty (harder to get high score later) → 5% Alert threshold currently ~78–82 (very strict). Real-world performance (first ~2 months private run) ~180 high-confidence alerts ~38% reached ≥5× from alert price ~11 tokens did 20×–120× False positive rate ~9–11% Median latency: 22 seconds (best cases <10s) Still far from perfect, but meaningfully better than manual monitoring or most public Telegram scanners. Current Telegram Alert Format 🌟 GOLDEN ALERT #142 $SHIBON Launch: 38s ago MC: $142k • Liq: $58k (STON.fi) Buy: https://ston.fi/swap?... Group: t.me/shibon_ton Score: 89/100 Dev: <4% Holders: 420+ (strong early distribution) Risk: Low (no sell tax detected) Time to decide: ~2–5 minutes usually Enter fullscreen mode Exit fullscreen mode Tech Stack (as of v0.1) Python 3.11+ (asyncio heavy) TON Center API v2 + TonAPI websocket python-telegram-bot (async) aiohttp + Redis (caching & dedup) FastAPI for internal monitoring dashboard (optional) ** How to Run Your Own Instance** git clone https://github.com/ilyarah/Golden-Memecoin-Alert.git cd Golden-Memecoin-Alert # Install pip install -r requirements.txt # Create .env from .env.example # Fill TON_API_KEY, TELEGRAM_BOT_TOKEN, etc. python main.py Enter fullscreen mode Exit fullscreen mode Security warning Never run with main wallet. Always review the code yourself. Use limited balance wallets only. Final Notes The TON memecoin meta changes every few weeks. Tools that crushed in Q4 2025 are already lagging in Q1 2026. I open-sourced Golden-Memecoin-Alert because: I believe collective improvement beats solo edge The community can make it faster and smarter than I ever could alone PRs, forks, and brutal feedback are extremely welcome. Stay early. Stay sharp. Ilya ( @ilyarah on GitHub & Telegram) Repo: https://github.com/ilyarah/Golden-Memecoin-Alert Star it if it saves you from missing the next 50×. 🚀 Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse ilya rahnavard Follow Self-taught full-stack blockchain Firestarter — wired for Solana, TON, Fantom(Sonic), and Ethereum L2s. I ship, I write, I share Joined Dec 25, 2025 More from ilya rahnavard Supercharge Prediction Markets Liquidity on Sonic with Flying Tulip: The Leverage Flywheel Developers Need in 2026 # fullstack # programming # blockchain # web3 I Built a Maze Runner Simulation Where Teenage Sam Altman Survives the Glade December 25, 2025 # gamedev # python # simulation 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/scale_youtube/ndc-conferences-would-you-survive-the-titanic-with-ml-and-net-simon-painter-ndc-4aal | NDC Conferences: "Would YOU Survive the Titanic?", with ML and .NET - Simon Painter - NDC Copenhagen 2025 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Scale YouTube Posted on Nov 2, 2025 NDC Conferences: "Would YOU Survive the Titanic?", with ML and .NET - Simon Painter - NDC Copenhagen 2025 # career # azure # cloud Would YOU Survive the Titanic? with ML.NET Simon Painter dives into Microsoft’s ML.NET SDK to show how easy it is to drop machine learning right into your C# projects—no Python required. Using Visual Studio, he tackles Kaggle’s famous Titanic Challenge to predict who lives or drowns when the ship goes down. Expect a fun, informal demo straight from NDC Copenhagen, packed with real code, practical tips and just enough iceberg puns to keep you afloat. Ready to see if you’d survive? Pull up a deck chair and let ML.NET set sail! Watch on YouTube Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Scale YouTube Follow Joined Aug 2, 2025 More from Scale YouTube NDC Conferences: Optimize Your Internal OS and Minimize Compatibility Issues at Work - Alice Meredith # career NDC Conferences: Optimize Your Internal OS and Minimize Compatibility Issues at Work - Alice Meredith # career NDC Conferences: Optimize Your Internal OS and Minimize Compatibility Issues at Work - Alice Meredith # career 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://popcorn.forem.com/gg_news/ign-the-pout-pout-fish-official-trailer-2026-nick-offerman-jordin-sparks-amy-sedaris-2chm | IGN: The Pout-Pout Fish - Official Trailer (2026) Nick Offerman, Jordin Sparks, Amy Sedaris - Popcorn Movies and TV Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Popcorn Movies and TV Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Gaming News Posted on Oct 16, 2025 IGN: The Pout-Pout Fish - Official Trailer (2026) Nick Offerman, Jordin Sparks, Amy Sedaris # celebrities # adventure # animation # movies The Pout-Pout Fish is an animated family adventure set to splash into theaters on March 20, 2026. Introverted Mr. Fish (Nick Offerman) and his hyperactive sidekick Pip (Nina Oyama) dive into a quest for a legendary wish-granting fish—because only that mythical finned friend can save their homes. With a stellar voice cast including Jordin Sparks, Amy Sedaris, Miranda Otto and Remy Hii, this heartwarming romp is directed by Ricard Cussó and Rio Harrington and penned by Elise Allen, Elie Choufany and Dominic Morris. Expect plenty of giggles, a few heartfelt moments, and an undersea world you won’t forget. Watch on YouTube Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Gaming News Follow Joined Apr 30, 2025 More from Gaming News IGN: Baahubali: The Epic - Official Trailer #2 (2025) # adventure # action # directorscut # movies IGN: Baahubali: The Epic - Official Trailer #2 (2025) # adventure # action # marketing # movies IGN: Baahubali: The Epic - Official Trailer #2 (2025) # action # directorscut # movies 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Popcorn Movies and TV — Movie and TV enthusiasm, criticism and everything in-between. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Popcorn Movies and TV © 2016 - 2026. Let's watch something great! Log in Create account | 2026-01-13T08:49:34 |
https://popcorn.forem.com/popcorn_movies/cinemasins-everything-wrong-with-a-minecraft-movie-in-22-minutes-or-less-53jb | CinemaSins: Everything Wrong With A Minecraft Movie In 22 Minutes Or Less - Popcorn Movies and TV Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Popcorn Movies and TV Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Movie News Posted on Aug 28, 2025 CinemaSins: Everything Wrong With A Minecraft Movie In 22 Minutes Or Less # movies # reviews # animation # streaming Everything Wrong With A Minecraft Movie In 22 Minutes Or Less skewers the latest blockbuster video-game adaptation with trademark snark, pointing out how ticked-off audiences and massive box-office receipts don’t magically fix tired tropes. It’s basically CinemaSins doing what they do best—calling out every contrived plot twist, shaky dialogue moment, and CG overkill in rapid-fire fashion. The video description doubles as a promo blitz: head over to cinemasins.com for more content, check out spin-off channels like TVSins and CommercialSins, join their Discord or Reddit communities, and don’t forget to fill out their “sinful” poll. If you’re feeling generous, you can even support the team on Patreon—and get to know the writers behind all those deliciously sarcastic “sins.” Watch on YouTube Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Movie News Follow Joined Jun 22, 2025 More from Movie News Ringer Movies: The 2026 Golden Globes: ‘One Battle After Another’ vs. ‘Hamnet’ Begins # movies # reviews # analysis # streaming CinemaSins: Everything Wrong With Austin Powers in Goldmember in 19 Minutes Or Less # movies # reviews # analysis # marketing Ringer Movies: Five Burning Questions About Awards Season & Our Golden Globes Predictions # movies # analysis # reviews # recommendations 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Popcorn Movies and TV — Movie and TV enthusiasm, criticism and everything in-between. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Popcorn Movies and TV © 2016 - 2026. Let's watch something great! Log in Create account | 2026-01-13T08:49:34 |
https://resources.github.com | Home - GitHub Resources / Resources Resources to help enterprise teams do their best work Set your business up for success with solutions to any number of common questions. Learn about DevSecOps Learn about DevOps Copilot Bring the power of generative AI to engineering teams with GitHub Copilot. Learn how you can maximize developer velocity and innovation. Read more about Copilot Security Stay one step ahead by shipping your software securely within GitHub: Identify and fix security issues directly in the developer flow. Read more about Security Why GitHub? Learn why more than 90% of the Fortune 100 use GitHub—the leading developer platform compared to alternative solutions. Compare GitHub GitHub Learning Pathways Become a GitHub expert in CI/CD, application security, governance, and AI-developer tools through expert-guided learning pathways with tips and insights from leading enterprise organizations. Start your learning journey Latest articles See all articles Pricing changes for GitHub Actions December 15, 2025 TLDR: We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach. We are continuing to reduce hosted-runners prices by up to 39% on January 1, 2026. GitHub Actions , Platform December ‘25 enterprise roundup December 11, 2025 In case you missed it… Platform , Security , AI , Software Development Playbook series: Communities of practice December 1, 2025 Your AI knowledge is vanishing in private chats. It's time to build Communities of Practice—the engine that transforms scattered individual insights into collective, scalable organizational intelligence. AI , Software Development Browse by topic Explore all the GitHub offerings by topic. See all topics AI Case Studies Cloud Developer Productivity DevOps Enterprise GitHub Actions GitHub Advanced Security GitHub Enterprise Innersource Integrations Open Source Platform Product Management Security Security Lab Software Development Startups Tools Web Development Whitepapers Latest videos See all videos Video and materials released: GitHub Latest Information Webinar held on September 29th October 3, 2025 This webinar is in Japanese only: GitHub Latest Updates Webinar on September 29th AI Video and slides published: GitHub update webinar on Aug 21 (in Korean) July 28, 2025 This webinar is in Korean only: Introducing the latest GitHub updates GitHub Roadmap Webinar, Q3 2025 - The Americas and Europe July 25, 2025 Get a first look at what’s next from GitHub “ Designed to empower Developers with access to the tools and features they need for streamlined collaboration. Aicha Bah Gersing // Senior Director, Premium Support Accelerate innovation with the platform developers love At GitHub, you can build what’s next with the industry’s most complete developer platform. Grow your business by investing in end-to-end software delivery and advanced security capabilities that simplify how you ship software at scale. Codespaces Curate blazing fast developer environments and help your organization be more agile, secure, and efficient. Learn more Advanced Security Ship secure applications with a community-driven, developer-first approach. Learn more Actions Automate your software workflows with a powerful DevOps toolkit and built-in CI/CD. Learn more Packages Safely publish and consume packages within your organization. Learn more Questions? Reach out to our sales team Over 100M developers and 4M+ organizations worldwide trust GitHub to ship better software. Need help picking a plan? No problem—we’ll walk you through each one. Find my plan | 2026-01-13T08:49:34 |
https://dev.to/t/interview/page/4#main-content | Interview Page 4 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # interview Follow Hide Create Post Older #interview posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu How Do You Handle Exceptions Globally in Spring Boot? realNameHidden realNameHidden realNameHidden Follow Dec 21 '25 How Do You Handle Exceptions Globally in Spring Boot? # java # spring # springboot # interview 5 reactions Comments Add Comment 3 min read A Strategic Guide to Hire Angular Developers Aditya Aditya Aditya Follow Dec 22 '25 A Strategic Guide to Hire Angular Developers # interview # career # typescript # angular Comments Add Comment 2 min read Coding Challenge Practice - Question 83 Bukunmi Odugbesan Bukunmi Odugbesan Bukunmi Odugbesan Follow Dec 22 '25 Coding Challenge Practice - Question 83 # algorithms # interview # javascript # devchallenge Comments Add Comment 2 min read Autocomplete / Type-ahead System for a Search Box - Part 2 ZeeshanAli-0704 ZeeshanAli-0704 ZeeshanAli-0704 Follow Dec 21 '25 Autocomplete / Type-ahead System for a Search Box - Part 2 # systemdesign # algorithms # interview # architecture Comments Add Comment 5 min read What Is the Impact of Quota and Spike Arrest on Latency in Apigee X? realNameHidden realNameHidden realNameHidden Follow Dec 20 '25 What Is the Impact of Quota and Spike Arrest on Latency in Apigee X? # gcp # apigee # apigeex # interview 5 reactions Comments Add Comment 3 min read What Are Spring Boot Starters? realNameHidden realNameHidden realNameHidden Follow Dec 20 '25 What Are Spring Boot Starters? # java # spring # springboot # interview 5 reactions Comments Add Comment 3 min read I Built CodeCrush: Making LeetCode Practice Feel Like an RPG Sansita Malhotra Sansita Malhotra Sansita Malhotra Follow Dec 21 '25 I Built CodeCrush: Making LeetCode Practice Feel Like an RPG # showdev # interview # leetcode # react Comments Add Comment 1 min read How Do You Log Exceptions Without Exposing Sensitive Details to Clients in Spring Boot? realNameHidden realNameHidden realNameHidden Follow Dec 24 '25 How Do You Log Exceptions Without Exposing Sensitive Details to Clients in Spring Boot? # java # spring # springboot # interview 5 reactions Comments Add Comment 4 min read Redis Interview Preparation Guide: From Basics to Hero Ricky512227 Ricky512227 Ricky512227 Follow Dec 24 '25 Redis Interview Preparation Guide: From Basics to Hero # interview # career # database # tutorial 1 reaction Comments Add Comment 16 min read How Do You Measure API Performance in Apigee X? realNameHidden realNameHidden realNameHidden Follow Dec 19 '25 How Do You Measure API Performance in Apigee X? # apigee # gcp # apigeex # interview 5 reactions Comments Add Comment 3 min read Coding Challenge Practice - Question 82 Bukunmi Odugbesan Bukunmi Odugbesan Bukunmi Odugbesan Follow Dec 19 '25 Coding Challenge Practice - Question 82 # challenge # algorithms # interview # typescript Comments Add Comment 1 min read Java Thread Pools Explained with End-to-End Examples (Fixed, Cached, Single, Scheduled) realNameHidden realNameHidden realNameHidden Follow Dec 31 '25 Java Thread Pools Explained with End-to-End Examples (Fixed, Cached, Single, Scheduled) # java # thread # interview # multithreading 5 reactions Comments Add Comment 4 min read The Unwritten Rubric: Why Senior Engineers Fail "Google SRE" Interviews Ace Interviews Ace Interviews Ace Interviews Follow Dec 17 '25 The Unwritten Rubric: Why Senior Engineers Fail "Google SRE" Interviews # google # interview # career # devops Comments Add Comment 5 min read Day 73 of 100 days dsa coding challenge Manasi Patil Manasi Patil Manasi Patil Follow Dec 16 '25 Day 73 of 100 days dsa coding challenge # algorithms # devchallenge # interview 1 reaction Comments Add Comment 1 min read Permutations & Next Permutation ZeeshanAli-0704 ZeeshanAli-0704 ZeeshanAli-0704 Follow Dec 20 '25 Permutations & Next Permutation # algorithms # interview # computerscience # tutorial Comments Add Comment 4 min read 🔗 Designing a URL Shortener: From Architecture to Node.js Implementation Abhinav Abhinav Abhinav Follow Dec 14 '25 🔗 Designing a URL Shortener: From Architecture to Node.js Implementation # systemdesign # interview # node # softwaredevelopment Comments 1 comment 4 min read Intuitive.ai (Intuitive.Cloud)-Oncampus Interview Experience | 10LPA Vrajkumar Patel Vrajkumar Patel Vrajkumar Patel Follow Dec 27 '25 Intuitive.ai (Intuitive.Cloud)-Oncampus Interview Experience | 10LPA # interview # interviewexperience # intuitivecloud # career 1 reaction Comments Add Comment 2 min read Coding Challenge Practice - Question 77 Bukunmi Odugbesan Bukunmi Odugbesan Bukunmi Odugbesan Follow Dec 13 '25 Coding Challenge Practice - Question 77 # algorithms # javascript # interview # tutorial Comments Add Comment 1 min read Javascript Interview Logic Question Jyoti Jingar Jyoti Jingar Jyoti Jingar Follow Dec 26 '25 Javascript Interview Logic Question # beginners # interview # javascript 1 reaction Comments Add Comment 2 min read Coding Challenge Practice - Question 76 Bukunmi Odugbesan Bukunmi Odugbesan Bukunmi Odugbesan Follow Dec 11 '25 Coding Challenge Practice - Question 76 # interview # javascript # tutorial # devchallenge Comments Add Comment 1 min read DSA: Patterns Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 4 DSA: Patterns # algorithms # computerscience # interview # learning Comments Add Comment 3 min read What Happens If Spike Arrest Is Set to 10pm but Traffic Spikes to 100 Requests at Once? realNameHidden realNameHidden realNameHidden Follow Dec 10 '25 What Happens If Spike Arrest Is Set to 10pm but Traffic Spikes to 100 Requests at Once? # apigee # apigeex # interview # spike 5 reactions Comments Add Comment 3 min read What Are Functional Interfaces? A Beginner-Friendly Guide realNameHidden realNameHidden realNameHidden Follow Dec 10 '25 What Are Functional Interfaces? A Beginner-Friendly Guide # java # interview # interface 5 reactions Comments Add Comment 3 min read Made a MongoDB Mindmap — sharing a preview if it helps anyone The Study Hub The Study Hub The Study Hub Follow Dec 10 '25 Made a MongoDB Mindmap — sharing a preview if it helps anyone # showdev # interview # database # resources Comments Add Comment 1 min read Stop Grinding LeetCode: How to Build Algorithm Intuition (Not Memorization) with AI Hui Hui Hui Follow Dec 9 '25 Stop Grinding LeetCode: How to Build Algorithm Intuition (Not Memorization) with AI # algorithms # learning # interview # ai Comments Add Comment 5 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/t/tauri/page/3 | Tauri Page 3 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Close # tauri Follow Hide Create Post Older #tauri posts 1 2 3 4 5 6 7 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Script Correct AI Text Corrector Nicolas Nicolas Nicolas Follow Jan 20 '25 Script Correct AI Text Corrector # vue # programming # tauri # opensource 7 reactions Comments Add Comment 2 min read Chaski: A Feed Reader for 2025 Andrés Andrés Andrés Follow Jan 19 '25 Chaski: A Feed Reader for 2025 # news # rss # tauri # rust Comments Add Comment 3 min read Tauri（5）—— Tray Icon Implementation and Event Handling Rain9 Rain9 Rain9 Follow Jan 17 '25 Tauri（5）—— Tray Icon Implementation and Event Handling # tauri # rust # ts # webdev 9 reactions Comments 6 comments 3 min read Adding Node.js server to Tauri App as a sidecar Zaid Sunasra Zaid Sunasra Zaid Sunasra Follow Jan 11 '25 Adding Node.js server to Tauri App as a sidecar # tutorial # node # softwaredevelopment # tauri 14 reactions Comments Add Comment 3 min read Tauri (4) - Get the theme switching function fixed Rain9 Rain9 Rain9 Follow Dec 31 '24 Tauri (4) - Get the theme switching function fixed # tauri # react # themes # tailwindcss 5 reactions Comments Add Comment 4 min read Tauri (3) - Get the window configuration right first Rain9 Rain9 Rain9 Follow Dec 31 '24 Tauri (3) - Get the window configuration right first # webdev # tauri # javascript # react 5 reactions Comments Add Comment 4 min read Rewind AI + Cursor AI = screenpipe: how we built a high performance Rust frame streaming API (OSS) Louis Beaumont Louis Beaumont Louis Beaumont Follow Nov 10 '24 Rewind AI + Cursor AI = screenpipe: how we built a high performance Rust frame streaming API (OSS) # rust # ai # llm # tauri Comments Add Comment 1 min read Interview with Prabhu Kiran Konda, Creator of Snail AI! CrabNebula CrabNebula CrabNebula Follow for CrabNebulaDev Oct 10 '24 Interview with Prabhu Kiran Konda, Creator of Snail AI! # rust # tauri # svelte # sveltekit 7 reactions Comments Add Comment 1 min read I love Rust/Tauri & Svelte Nasser El Idrissi Nasser El Idrissi Nasser El Idrissi Follow Nov 1 '24 I love Rust/Tauri & Svelte # tauri # rust # svelte # opensource 195 reactions Comments 27 comments 2 min read Tauri 2.0 - Sqlite DB - React Stephan Lüddemann Stephan Lüddemann Stephan Lüddemann Follow Nov 4 '24 Tauri 2.0 - Sqlite DB - React # tauri # sqlite # react # typescript 21 reactions Comments 5 comments 4 min read Interview with Eson (Seven), Creator of DocKit! CrabNebula CrabNebula CrabNebula Follow for CrabNebulaDev Sep 26 '24 Interview with Eson (Seven), Creator of DocKit! # rust # tauri # gui # interview 10 reactions Comments Add Comment 1 min read EcoPaste -Open source clipboard management tool for MacOS and Windows platforms zhangmo8 zhangmo8 zhangmo8 Follow Sep 23 '24 EcoPaste -Open source clipboard management tool for MacOS and Windows platforms # opensource # paste # tauri Comments Add Comment 2 min read Interview with Hussein Hareb, Creator of Ηw-monitor! CrabNebula CrabNebula CrabNebula Follow for CrabNebulaDev Sep 19 '24 Interview with Hussein Hareb, Creator of Ηw-monitor! # rust # tauri # linux # interview 10 reactions Comments Add Comment 1 min read Interview with Krzysztof Andrelczyk, Tauri Developer and Creator of Twili Recipes CrabNebula CrabNebula CrabNebula Follow for CrabNebulaDev Sep 5 '24 Interview with Krzysztof Andrelczyk, Tauri Developer and Creator of Twili Recipes # rust # tauri 7 reactions Comments Add Comment 2 min read Interview with Klauss Andrei, Creator of FocusPocus.io! CrabNebula CrabNebula CrabNebula Follow for CrabNebulaDev Oct 7 '24 Interview with Klauss Andrei, Creator of FocusPocus.io! # tauri # rust 11 reactions Comments Add Comment 1 min read How I Built an Open Source App That Went Viral Aziz FADIL Aziz FADIL Aziz FADIL Follow Sep 24 '24 How I Built an Open Source App That Went Viral # opensource # rust # tauri # react 6 reactions Comments 1 comment 4 min read Interview with Victor Aremu, Creator of Menote, Usezap and more! CrabNebula CrabNebula CrabNebula Follow for CrabNebulaDev Sep 11 '24 Interview with Victor Aremu, Creator of Menote, Usezap and more! # tauri # rust # opensource # interview 11 reactions Comments 1 comment 1 min read Interview with Johans Justs Eris, Tauri Developer for Blenderbase at PhysicalAddons CrabNebula CrabNebula CrabNebula Follow for CrabNebulaDev Aug 14 '24 Interview with Johans Justs Eris, Tauri Developer for Blenderbase at PhysicalAddons # tauri # rust # opensource # cloud 6 reactions Comments Add Comment 1 min read Leptos + Tauri Tutorial Davide Del Papa Davide Del Papa Davide Del Papa Follow Sep 1 '24 Leptos + Tauri Tutorial # rust # tauri # leptos # webassembly 21 reactions Comments 2 comments 11 min read Tauri dialog instead of window.confirm nk_Enuke nk_Enuke nk_Enuke Follow Aug 19 '24 Tauri dialog instead of window.confirm # react # tauri # rust Comments Add Comment 1 min read Interview with Siddharth, creator of Micro, Tauri plugin decorum, and more! CrabNebula CrabNebula CrabNebula Follow for CrabNebulaDev Aug 8 '24 Interview with Siddharth, creator of Micro, Tauri plugin decorum, and more! # tauri # rust # startup # cloud 5 reactions Comments Add Comment 1 min read Tauri v2: Dos nuevos conceptos que debes conocer antes de actualizar tus apps a la nueva versión David Jiménez David Jiménez David Jiménez Follow Aug 17 '24 Tauri v2: Dos nuevos conceptos que debes conocer antes de actualizar tus apps a la nueva versión # tauri # tauriapp # español Comments Add Comment 3 min read How to Reasonably Keep Your Tauri Commands Organized in Rust Godwin Jemegah Godwin Jemegah Godwin Jemegah Follow Aug 13 '24 How to Reasonably Keep Your Tauri Commands Organized in Rust # rust # tauri # javascript # typescript 4 reactions Comments Add Comment 2 min read [Rust]How to make string handing to frontend on tauri app nk_Enuke nk_Enuke nk_Enuke Follow Jul 25 '24 [Rust]How to make string handing to frontend on tauri app # tauri # rust # devops # developer Comments Add Comment 1 min read Tauri vs. Electron: A Technical Comparison vorillaz vorillaz vorillaz Follow Jul 24 '24 Tauri vs. Electron: A Technical Comparison # tauri # electron # javascript 11 reactions Comments 3 comments 4 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/resumemind/how-to-write-a-resume-that-gets-interviews-not-rejections-127b#9-get-a-second-pair-of-eyes-on-your-resume | How to Write a Resume That Gets Interviews (Not Rejections) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Resumemind Posted on Jan 12 How to Write a Resume That Gets Interviews (Not Rejections) # career # interview # tutorial Most resumes don’t fail because the candidate is unqualified. They fail because the resume doesn’t communicate value fast enough. Recruiters spend 6–8 seconds scanning a resume before deciding whether to continue or reject it. If your resume doesn’t pass that first scan, it’s over — no matter how skilled you are. This guide will show you step by step how to write a resume that gets interviews, not silent rejections. 1. Understand How Recruiters Actually Read Resumes Before writing anything, you need to understand how resumes are evaluated. Recruiters don’t read resumes line by line. They scan for: Job title relevance Clear role identity Skills that match the job Recent experience or projects Structure and readability If these aren’t obvious in seconds, the resume is rejected. 👉 Your goal is clarity, not creativity. 2. Start With a Clear Role-Focused Resume Header Your resume must immediately answer one question: Who are you professionally? ❌ Weak header John Doe Email | Phone | Location ✅ Strong header John Doe Junior Software Developer | Frontend (Angular) Email | Phone | LinkedIn | Portfolio This instantly tells the recruiter: your level your role your focus Never make recruiters guess. 3. Write a Resume Summary That Sells (Not One That Repeats) Your resume summary is not your life story. It’s a 2–4 line pitch. ❌ Bad summary “Hardworking and motivated individual looking for opportunities to grow.” This says nothing. ✅ Good summary Junior Software Developer with hands-on experience building web applications using Angular and Spring Boot. Strong in problem-solving, REST APIs, and clean UI design. Actively seeking an entry-level role where I can contribute and grow. A good summary: mentions your role highlights key skills shows direction 4. Experience Matters — Even If You Have No Job Experience Many people think: “I can’t write a good resume because I have no experience.” That’s false. Recruiters accept: projects internships freelance work academic projects self-initiated work How to Write Experience Correctly Instead of listing duties, list impact. ❌ Bad: Built a website Worked with Angular ✅ Good: Built a responsive web application using Angular and REST APIs Implemented authentication and improved UI usability If you don’t have job experience, projects become your experience. 5. Skills Section: Be Honest, Relevant, and Specific Your skills section should support your role — not show everything you’ve ever touched. ❌ Bad skills list HTML, CSS, Java, Python, Photoshop, Networking, Excel This looks unfocused. ✅ Good skills list Frontend: Angular, TypeScript, HTML, CSS Backend: Java, Spring Boot, REST APIs Tools: Git, GitHub, Postman Only list skills you’re ready to discuss in an interview. 6. Formatting Can Get You Rejected Instantly Even strong content can fail if formatting is poor. Use: 1 page (for juniors) clear section headings consistent spacing readable font bullet points Avoid: long paragraphs heavy colors icons everywhere photos (unless required) fancy designs that hurt readability A clean resume looks professional and trustworthy. 7. Tailor Your Resume for Each Job (This Is Critical) Using one resume for every job is one of the biggest mistakes job seekers make. You should: adjust your summary reorder skills emphasize relevant projects This doesn’t mean rewriting everything — it means highlighting what matters most for that role. Tailoring your resume alone can double your interview chances. 8. Common Resume Mistakes That Lead to Rejection Avoid these at all costs: No role mentioned Weak or generic summary No projects listed Grammar mistakes Overcrowded layout Irrelevant skills Copy-pasted content Recruiters see these mistakes every day — and reject fast. 9. Get a Second Pair of Eyes on Your Resume One of the best things you can do is get honest feedback. When reviewing resumes manually, the most common missing elements are: unclear role weak summary missing experience descriptions no direction You might not see these issues yourself. Getting your resume reviewed by another person can completely change your results. Final Thoughts A resume that gets interviews is not about being perfect. It’s about being clear, relevant, and honest. If recruiters can quickly understand: who you are what you can do and why you fit the role You’ll start getting callbacks. Next Step If you’re unsure whether your resume is working, get it reviewed before you apply. Often, a few small changes are all it takes to start getting interviews. We offer a free manual resume review , where real people review resumes daily and give honest feedback — not automated scores. 👉 Request a free resume review: https://resumemind.com/public/resume-review Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Resumemind Follow Helping software developers and other related tech experts like project managers, QA, businesses analysts crafting their tech resumes for their next job applications. Joined Jan 4, 2026 More from Resumemind How I Built a Manual Resume Review System with Spring Boot & Angular # angular # career # showdev # springboot I Reviewed 50 Junior Developer Resumes — Here’s What Actually Works # beginners # career # codenewbie How to Write a Resume With No Work Experience (Fresh Graduate Guide for 2026) # beginners # career # tutorial 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/voxel51/neurlps-2024-a-textbook-remedy-for-domain-shifts-knowledge-priors-for-medical-image-analysis-ff9 | NeurlPS 2024 - A Textbook Remedy for Domain Shifts: Knowledge Priors for Medical Image Analysis - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Jimmy Guerrero for Voxel51 Posted on Dec 6, 2024 • Edited on Dec 10, 2024 NeurlPS 2024 - A Textbook Remedy for Domain Shifts: Knowledge Priors for Medical Image Analysis # computervision # machinelearning # datascience # ai Check out Harpreet Sahota 's conversation with Yue Yang about his NeurIPS 2024 paper, “A Textbook Remedy for Domain Shifts: Knowledge Priors for Medical Image Analysis”. Complete interview and discussion on YouTube Blog Post Research Paper Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Voxel51 Follow More from Voxel51 Elderly Action Recognition: No One Should Age Alone, AI’s Promise for the Next Generation of Elders # computervision # ai # machinelearning # datascience Journey into Visual AI: Exploring FiftyOne Together — Part IV Model Evaluation # computervision # machinelearning # ai # datascience How to Tame Your (Data) Dragon # computervision # ai # machinelearning # datascience 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#development | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:49:34 |
https://dev.to/veritaschain/the-eu-ai-act-doesnt-mandate-cryptographic-logs-but-youll-want-them-anyway-97f | The EU AI Act Doesn't Mandate Cryptographic Logs—But You'll Want Them Anyway - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse VeritasChain Standards Organization (VSO) Posted on Dec 25, 2025 The EU AI Act Doesn't Mandate Cryptographic Logs—But You'll Want Them Anyway # ai # cryptography # blockchain How Articles 12, 15, and 73 create implicit pressure for tamper-evident audit trails in high-risk AI systems TL;DR The EU AI Act (Regulation 2024/1689) requires automatic logging for high-risk AI systems but doesn't explicitly mandate cryptographic mechanisms. However, the combination of lifetime traceability requirements (Article 12), cybersecurity obligations (Article 15), and forensic evidence preservation rules (Article 73) makes hash-chained, digitally-signed logs the economically rational choice. This article maps each relevant provision to cryptographic implementations—and shows why "minimum compliance" approaches are legally riskier than going beyond the baseline. The Regulatory Landscape: What the Act Actually Says The EU AI Act entered into force on August 1, 2024. High-risk system requirements become enforceable on August 2, 2026 . The clock is ticking. Article 12: The Foundation "High-risk AI systems shall technically allow for the automatic recording of events (logs) over the lifetime of the system." — Article 12(1), Regulation (EU) 2024/1689 This is a mandatory pre-market design requirement . Systems lacking logging capabilities cannot legally enter the EU market. But notice what's not specified: ❌ Log format or schema ❌ Storage architecture ❌ Integrity protection methods ❌ Third-party verifiability The phrase "appropriate to the intended purpose" delegates technical specification to provider judgment. This is where cryptographic approaches shine. Article 19: Retention Requirements Obligation Minimum Period Automatically generated logs 6 months Technical documentation 10 years Conformity assessments 10 years Financial institutions face sector-specific extensions (MiFID II: 5-7 years). The question isn't whether to retain logs—it's whether you can prove they haven't been tampered with during that period. Article 73: The Forensic Imperative "The provider shall not perform any investigation which involves altering the AI system concerned in a way which may affect any subsequent evaluation of the causes of the incident." — Article 73(6) This is the killer provision. During serious incident investigations: 15 days for standard incidents 10 days for death or suspected death 2 days for critical infrastructure disruption Mutable logs create legal exposure. If you modify logs (intentionally or inadvertently) during investigation, you face: Regulatory presumption of non-compliance Enhanced penalties under Article 99 (misleading information) Civil liability in private litigation Cryptographic hash chains solve this. Append-only logs with cryptographic timestamps demonstrate preservation compliance without restricting legitimate analysis. The Compliance Gap: Minimum vs. Defensible Here's the uncomfortable truth: Minimum Compliance Vulnerability Cryptographic Solution Mutable database logs Article 73 evidence tampering allegations Tamper-evident hash chains Manual documentation Annex IV burden; human error Automated generation from event streams Provider-only verification Authority skepticism Third-party verifiable proofs Reactive incident response Article 73 deadline pressure Real-time anomaly detection The Act creates a "compliance floor, not ceiling" regime. Minimum compliance is achievable with conventional logging—but cryptographic approaches provide superior evidential weight and competitive differentiation. Technical Architecture: Building Compliant Audit Trails Hash Chain Implementation Every event links cryptographically to its predecessor: import hashlib import json from datetime import datetime , timezone class AuditEvent : def __init__ ( self , event_type : str , payload : dict , prev_hash : str ): self . timestamp = datetime . now ( timezone . utc ). isoformat () self . event_type = event_type self . payload = payload self . prev_hash = prev_hash self . hash = self . _compute_hash () def _compute_hash ( self ) -> str : """ SHA-256 hash of canonicalized event data """ canonical = json . dumps ({ " timestamp " : self . timestamp , " event_type " : self . event_type , " payload " : self . payload , " prev_hash " : self . prev_hash }, sort_keys = True , separators = ( ' , ' , ' : ' )) return hashlib . sha256 ( canonical . encode ()). hexdigest () def verify_chain ( self , expected_prev_hash : str ) -> bool : """ Verify hash chain integrity """ return self . prev_hash == expected_prev_hash # Article 12(3) biometric system logging event = AuditEvent ( event_type = " BIOMETRIC_VERIFICATION " , payload = { " start_time " : " 2025-12-25T09:00:00Z " , " end_time " : " 2025-12-25T09:00:03Z " , " reference_database " : " db_employees_v3 " , " match_confidence " : 0.97 , " verifier_id " : " operator_12345 " , # Article 12(3)(d) requirement " verifier_signature " : " ed25519:... " # Non-repudiation }, prev_hash = " abc123... " ) Enter fullscreen mode Exit fullscreen mode This satisfies: ✅ Article 12(1): Automatic recording capability ✅ Article 12(3): Biometric system minimum logging ✅ Article 73(6): Tamper-evident evidence preservation Digital Signatures for Human Oversight Article 14 requires human oversight capabilities. Article 12(3)(d) requires identification of human verifiers. Digital signatures provide non-repudiation: from nacl.signing import SigningKey , VerifyKey from nacl.encoding import HexEncoder class OversightAction : """ Article 14 human oversight with cryptographic attribution """ def __init__ ( self , action_type : str , operator_key : SigningKey ): self . action_type = action_type self . timestamp = datetime . now ( timezone . utc ). isoformat () self . operator_public_key = operator_key . verify_key . encode ( HexEncoder ). decode () self . _sign ( operator_key ) def _sign ( self , key : SigningKey ): message = f " { self . action_type } : { self . timestamp } " . encode () self . signature = key . sign ( message , encoder = HexEncoder ). signature . decode () def verify ( self , public_key : VerifyKey ) -> bool : message = f " { self . action_type } : { self . timestamp } " . encode () try : public_key . verify ( message , bytes . fromhex ( self . signature ) ) return True except : return False # Human override decision (Article 14(4)(d)) override = OversightAction ( action_type = " DECISION_OVERRIDE " , operator_key = operator_signing_key ) Enter fullscreen mode Exit fullscreen mode This creates: Individual attribution : Specific person exercised oversight Temporal proof : Intervention occurred at claimed time Decision integrity : Cannot be silently modified post-incident Merkle Trees for Efficient Verification Authorities don't need your entire operational dataset. Merkle proofs enable selective disclosure : import hashlib from typing import List , Optional class MerkleTree : """ Efficient verification without full dataset exposure """ def __init__ ( self , leaves : List [ str ]): self . leaves = [ self . _hash ( leaf ) for leaf in leaves ] self . tree = self . _build_tree ( self . leaves ) self . root = self . tree [ - 1 ][ 0 ] if self . tree else None def _hash ( self , data : str ) -> str : return hashlib . sha256 ( data . encode ()). hexdigest () def _build_tree ( self , leaves : List [ str ]) -> List [ List [ str ]]: if not leaves : return [] tree = [ leaves ] while len ( tree [ - 1 ]) > 1 : level = [] nodes = tree [ - 1 ] for i in range ( 0 , len ( nodes ), 2 ): left = nodes [ i ] right = nodes [ i + 1 ] if i + 1 < len ( nodes ) else left level . append ( self . _hash ( left + right )) tree . append ( level ) return tree def get_proof ( self , index : int ) -> List [ tuple ]: """ Generate proof for leaf at index """ proof = [] for level in self . tree [: - 1 ]: if index % 2 == 0 : sibling_idx = index + 1 if index + 1 < len ( level ) else index proof . append (( ' right ' , level [ sibling_idx ])) else : proof . append (( ' left ' , level [ index - 1 ])) index //= 2 return proof # Anchor daily Merkle roots for long-term verification daily_events = [ event . hash for event in today_audit_trail ] merkle = MerkleTree ( daily_events ) anchor_root = merkle . root # Store/publish this single hash Enter fullscreen mode Exit fullscreen mode Use case : Authority requests logs from incident timeframe. You provide: Relevant events (Article 72 post-market monitoring) Merkle proofs demonstrating completeness Anchored root (published/timestamped) proving data existed at claimed time No full dataset exposure. Mathematically verifiable integrity. MQL5 Integration: Trading System Audit Trails For algorithmic trading systems under EU AI Act scope: //+------------------------------------------------------------------+ //| VCP-compliant audit logging for MQL5 trading algorithms | //| Satisfies Article 12 automatic recording requirement | //+------------------------------------------------------------------+ #include <JAson.mqh> class CVCPAuditLog { private: string m_prev_hash; int m_file_handle; string ComputeSHA256(string data) { uchar src[], dst[], key[]; StringToCharArray(data, src); CryptEncode(CRYPT_HASH_SHA256, src, key, dst); string hash = ""; for(int i = 0; i < ArraySize(dst); i++) hash += StringFormat("%02x", dst[i]); return hash; } public: CVCPAuditLog() { m_prev_hash = "genesis"; m_file_handle = FileOpen("vcp_audit.jsonl", FILE_WRITE|FILE_TXT); } void LogOrderEvent(string event_type, ulong ticket, double price, double volume) { CJAVal json; json["timestamp"] = TimeToString(TimeGMT(), TIME_DATE|TIME_SECONDS); json["event_type"] = event_type; json["ticket"] = IntegerToString(ticket); json["price"] = DoubleToString(price, _Digits); json["volume"] = DoubleToString(volume, 2); json["symbol"] = _Symbol; json["prev_hash"] = m_prev_hash; string canonical = json.Serialize(); string current_hash = ComputeSHA256(canonical); json["hash"] = current_hash; if(m_file_handle != INVALID_HANDLE) { FileWriteString(m_file_handle, json.Serialize() + "\n"); FileFlush(m_file_handle); } m_prev_hash = current_hash; } // Article 14: Human oversight logging void LogHumanOverride(string reason, string operator_id) { CJAVal json; json["timestamp"] = TimeToString(TimeGMT(), TIME_DATE|TIME_SECONDS); json["event_type"] = "HUMAN_OVERRIDE"; json["reason"] = reason; json["operator_id"] = operator_id; json["prev_hash"] = m_prev_hash; // In production: add Ed25519 signature from operator's key string canonical = json.Serialize(); m_prev_hash = ComputeSHA256(canonical); json["hash"] = m_prev_hash; if(m_file_handle != INVALID_HANDLE) FileWriteString(m_file_handle, json.Serialize() + "\n"); } }; // Global audit logger CVCPAuditLog g_audit; void OnTrade() { // Automatically log all trade events (Article 12(1)) HistorySelect(TimeCurrent() - 1, TimeCurrent()); int total = HistoryDealsTotal(); for(int i = 0; i < total; i++) { ulong ticket = HistoryDealGetTicket(i); double price = HistoryDealGetDouble(ticket, DEAL_PRICE); double volume = HistoryDealGetDouble(ticket, DEAL_VOLUME); g_audit.LogOrderEvent("DEAL_EXECUTED", ticket, price, volume); } } Enter fullscreen mode Exit fullscreen mode GDPR Compatibility: The Crypto-Shredding Solution The elephant in the room: GDPR Article 5(1)(e) storage limitation vs. AI Act Article 19 retention requirements. Solution: Architectural separation ┌─────────────────────────────────────────────────────────────┐ │ AUDIT INTEGRITY LAYER │ │ (Immutable - hash chains, Merkle roots, timestamps) │ │ │ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ │ │ Event │──│ Event │──│ Event │──│ Event │ │ │ │ Hash #1 │ │ Hash #2 │ │ Hash #3 │ │ Hash #4 │ │ │ └────┬─────┘ └────┬─────┘ └────┬─────┘ └────┬─────┘ │ └───────┼─────────────┼─────────────┼─────────────┼──────────┘ │ │ │ │ ▼ ▼ ▼ ▼ ┌─────────────────────────────────────────────────────────────┐ │ PERSONAL DATA LAYER │ │ (Deletable - encrypted, key-managed) │ │ │ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ │ │ Encrypted│ │ Encrypted│ │ DELETED │ │ Encrypted│ │ │ │ PII #1 │ │ PII #2 │ │ (shredded)│ │ PII #4 │ │ │ │ [Key: K1]│ │ [Key: K1]│ │ │ │ [Key: K2]│ │ │ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │ └─────────────────────────────────────────────────────────────┘ Enter fullscreen mode Exit fullscreen mode Crypto-shredding workflow : Personal data encrypted with per-subject keys Hash of encrypted data stored in audit chain GDPR deletion request → destroy encryption key Audit chain intact (proves events occurred) Personal data irrecoverable (satisfies erasure right) from cryptography.fernet import Fernet from cryptography.hazmat.primitives import hashes from cryptography.hazmat.primitives.kdf.pbkdf2 import PBKDF2HMAC import base64 import os class CryptoShreddingManager : """ GDPR-compliant deletion with audit trail preservation """ def __init__ ( self , key_store_path : str ): self . key_store = {} self . key_store_path = key_store_path def _generate_subject_key ( self , subject_id : str ) -> bytes : """ Generate unique encryption key per data subject """ salt = os . urandom ( 16 ) kdf = PBKDF2HMAC ( algorithm = hashes . SHA256 (), length = 32 , salt = salt , iterations = 480000 , ) key = base64 . urlsafe_b64encode ( kdf . derive ( subject_id . encode ())) self . key_store [ subject_id ] = { " key " : key , " salt " : salt } return key def encrypt_pii ( self , subject_id : str , data : bytes ) -> tuple : """ Encrypt PII, return ciphertext and hash for audit chain """ if subject_id not in self . key_store : key = self . _generate_subject_key ( subject_id ) else : key = self . key_store [ subject_id ][ " key " ] f = Fernet ( key ) ciphertext = f . encrypt ( data ) # Hash goes in immutable audit chain data_hash = hashlib . sha256 ( ciphertext ). hexdigest () return ciphertext , data_hash def crypto_shred ( self , subject_id : str ) -> bool : """ GDPR Article 17 erasure via key destruction """ if subject_id in self . key_store : # Securely overwrite key material key_data = self . key_store [ subject_id ] key_data [ " key " ] = os . urandom ( len ( key_data [ " key " ])) del self . key_store [ subject_id ] # Log shredding event (itself goes in audit chain) return True return False Enter fullscreen mode Exit fullscreen mode The Business Case: Beyond Compliance Risk Calculus For a high-risk AI system serving the EU market: Scenario Conventional Logs Cryptographic Logs Article 73 investigation Integrity questioned; burden on provider to prove non-tampering Cryptographic proof of integrity; authority can verify independently Conformity assessment Self-attestation only Third-party verifiable evidence packages Litigation Logs challenged as potentially altered Mathematical proof of authenticity Insurance Higher premiums; exclusions for data integrity failures Favorable terms for verified audit trails Competitive positioning Baseline compliance "Cryptographically Verifiable" as premium feature Standards Trajectory CEN-CENELEC JTC 21 is developing harmonized standards for AI Act compliance: prEN ISO/IEC 24970 : AI System Logging (public consultation expected mid-2025) Standards likely to incorporate cryptographic mechanisms based on: ISO/IEC 27001 integrity controls Financial sector precedents (SEC CAT, ESMA transaction reporting) NIST Cybersecurity Framework cryptographic baselines Early adopters of cryptographic logging will be aligned with harmonized standards before publication. Implementation Roadmap Phase 1: Foundation (Now → Q2 2025) [ ] Implement hash-chained event logging [ ] Deploy Ed25519 signing for human oversight events [ ] Establish key management infrastructure [ ] Document architecture as Article 11/Annex IV technical documentation Phase 2: Verification (Q2 2025 → Q4 2025) [ ] Add Merkle tree aggregation for efficient proofs [ ] Integrate eIDAS-qualified timestamps [ ] Implement GDPR crypto-shredding layer [ ] Build authority reporting templates (Article 73) Phase 3: Hardening (Q4 2025 → August 2026) [ ] Conformity assessment dry run [ ] Third-party audit of cryptographic controls [ ] Post-market monitoring integration (Article 72) [ ] Incident response procedure validation Conclusion: The Implicit Mandate The EU AI Act doesn't explicitly require cryptographic audit trails. But it creates a regulatory environment where they're the economically rational choice : Article 12 demands lifetime logging → hash chains ensure continuity Article 15 requires cybersecurity → cryptographic integrity satisfies this Article 73 prohibits evidence alteration → immutable logs provide defense Article 72 needs verifiable monitoring → timestamped proofs demonstrate compliance The market is moving toward cryptographic verification not because it's legally mandated, but because alternatives are legally riskier. The VeritasChain Protocol (VCP) provides an open specification for implementing these patterns. Whether you adopt VCP or build your own architecture, the technical requirements are clear: hash chains, digital signatures, qualified timestamps, and verifiable proofs. The August 2026 deadline approaches. The question isn't whether to implement cryptographic audit trails—it's whether you'll be ready when authorities start asking for evidence you can actually prove. Resources EU AI Act Official Text : EUR-Lex 2024/1689 VeritasChain Protocol Specification : veritaschain.org VCP GitHub : github.com/veritaschain IETF Draft : draft-kamimura-scitt-vcp CEN-CENELEC JTC 21 : AI Standards Development This article is published by the VeritasChain Standards Organization (VSO) as educational content. VSO is a non-profit standards body and does not endorse specific commercial implementations. For technical inquiries: technical@veritaschain.org Tags : #ai #compliance #cryptography #euaiact #audit #blockchain #regulations #fintech Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse VeritasChain Standards Organization (VSO) Follow Developing global cryptographic standards for algorithmic & AI-driven trading. Maintainer of VeritasChain Protocol (VCP) — a tamper-evident audit layer designed for MiFID II, EU AI Act, and next-gener Location Tokyo, Japan Joined Dec 7, 2025 More from VeritasChain Standards Organization (VSO) Building Cryptographic Audit Trails for AI Trading Systems: A Deep Dive into RFC 6962-Based Verification # ai # regtech The Grok Scandal Proves AI Needs Cryptographic Audit Trails—Not Just Content Moderation # ai # security # opensource Why Your Trading Algorithm Needs a Flight Recorder: Lessons from the 2025 Market Chaos # fintech # cryptography # security # algorithms 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/thejaredwilcurt/bun-hype-how-we-learned-nothing-from-yarn-2n3j#comments | Bun hype. How we learned nothing from Yarn - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse The Jared Wilcurt Posted on Sep 16, 2023 Bun hype. How we learned nothing from Yarn # node # bunjs # npm # javascript Here we go again, making the same mistake. I'm constantly reminded that every 5 years the amount of programmers in the world doubles, which means at any point, 50% of the industry has less than 5 years experience. Which is probably why we keep falling for stuff like Bun. But I've seen this movie before, and I know how it ends. Part one - The story of Yarn I see a lot of parallels between Yarn and Bun. Both targeted existing open source systems, and instead of actually contributing to them, just went off to create their own competing technology. Both sold themselves on being way faster. Both went in with the goal of splitting the ecosystem. Neither had good backwards compatibility support. And both announced that they were officially v1.0 and ready for production! ...while not actually supporting Windows (read: not actually remotely production ready). So what happened to Yarn? Well, they came out with about a dozen cool new features that npm didn't have. And they were many times faster than npm. But then... only a year later, npm was already faster than Yarn. And another year later, Yarn would create a blog post explaining how it would ultimately be impossible for them to ever be faster than npm, due to the npm CLI being created by the same people in charge of the npm servers where the packages were stored and downloaded from. And that is still true to this day. In 2023, npm is still faster than Yarn. Its original big selling point.... has not been relevant for 5 years. But what about the other features Yarn offered? With each passing year, more and more of them were implemented and released in npm, and as of today, all of the formerly-unique features Yarn offered, are built in to npm. Sure the implementations of the features are slightly different and for those that really care about the subtle nuance between how Yarn, Lerna, Turbo, and npm handle mono-repo management, you may prefer one over the other. But for the vast majority of use cases, the way npm implements these features is perfectly fine for almost all users. Ah, but Bun is surely different? Right? I mean, it's written with ZIG! And ZIG! is super fast.... right? Eh, not really. It isn't doing anything magical, ultimately any performance you can achieve with it could be achieved with C++ (what Node.js is written in). So, just like with the story of old slow npm, once performance was prioritized, npm was able to go just as fast (faster even) than the competition. I can see a similar thing happening with Node. If given the proper attention, roughly equivalent speeds should be possible to the point where the differences are negligible. Well... kinda. I mean, we should probably acknowledge the fact that some of the benchmarks Bun brags about are cherry-picked or misrepresentative . So, even Bun doesn't live up to its own marketing hype. But you get the point. Back to the parable of Yarn. When Yarn came out, it said it supported Windows. But none of the Facebook developers working on Yarn used Windows for their primary OS. So they quickly found out that Yarn, in fact did not run on that platform when released. A short aside: Hi there, Primagen (the rest of you can skip this). Now I know, you've already made a snarky comment about Windows. But perhaps you should try to really value diversity in our society, and accept different ways of life. I mean, I get it. I totally do, Windows users make up a very very tiny minority of only 90% of computer users. But maybe... we should be respectful of that barely noticeable minority. :) Back to the story. So after about 2 weeks or so, they finally "fixed" it and Yarn could install and run on Windows.... kinda. I actually was never able to get Yarn to run reliably on Windows myself until they switched over to using corepack . Once you could install corepack via npm, and then install Yarn (or pnpm) on top of it, it was finally Windows compatible in a reliable, non-buggy, non-crashing, way. But by that point, Facebook had already dropped Yarn, and slowly, so did everyone else, it was already dying off by the time it ran on Windows. I've still, to this day, never been able to get a Yarn mono-repo to run on Windows. I'm convinced it is not possible. Anyone who says they got it to work is lying to you. Sure, maybe in some Windows VM with nothing installed (not even Windows Updates), maybe someone got a Yarn monorepo to run on Windows, for a few glorious seconds. And maybe they also saw Sasquatch in the woods. Anything can happen. But on a real developer laptop, with random shit in the PATH, and Node and nvm-windows and volta and who knows what other random things installed, no, it doesn't work. Okay, so Yarn came around, forced npm to get better, and then died. What's the problem? If that's all it did, then Yarn would have been great, but sadly it wasn't. npm was focused on developing and releasing the features the vast majority of users needed. But Yarn was focused on the features Facebook needed. Many of which were not important for 99% of people using npm. However, once people started using Yarn, npm had to repriortize what features they would develop and release. Instead of delivering higher value features that would be more relevant to more users, they had to quickly play catch up and add equivalent features to what Yarn was offering, as to avoid a split in the ecosystem. But Yarn marketed itself very well, and people bought into the hype. Even I was hyped for Yarn when it came out, until I found out it didn't actually run on Windows. But others didn't realize, or didn't care about that, and adopted it... and... and... ... And then Yarn became tribal. Stupid humans. Everything has to become tribal. And for several years there were thousands of README's created on projects that only told you the Yarn instructions for how to install the project. Confusing new developers. I can't tell you the amount of junior devs that have come to me asking for clarification on what this "Yarn thing" is, and if they need it. Thinking the project(s) they found would only work with Yarn. What a waste of everyone's time and mental space. I always assumed someone at Facebook just found that convincing their boss to let them spend time adding features to an open source project they couldn't take credit for was a hard sell. It was probably easier for them to get approval to work on these features if they could use it for marketing for job recruitment or something. It always smelled of Not Invented Here syndrome . Had Facebook just contributed to npm the features they wanted, then their features would have been released along side the ones npm was already working on. But instead it delayed the release of these other features by many years, resulting in duplicated efforts. And all for what? Yarn is basically dead at this point, except for a few niche edge cases. But I haven't seen a yarn add in a README in the past year or two. It's a sign of a past era. Part two - Bun is actually much worse Unlike Yarn, which offered speed and a dozen new features, Bun offers speed and like 3 new features. Let's briefly go over them. Macros - Used during a build process. They've been called a mistake by some. My biggest concern is that your build process is now stuck with Bun. You can't switch to something else unless it has an equivalent macro system, or you re-write your build process. You're opting into future tech debt. bun.x APIs - These are new API's that do literally the same thing the Node.js APIs do, "but faster". This is worse than the macros because now your code is a Bun virus. If I npm install your package and run it in Node, I'll get ReferenceError: Bun is not defined when trying to use your library. Forcing all users of your library to adopt Bun. This is another forced split of the ecosystem, similar to what Yarn was doing, but much worse. I could maybe see some wrapper library you import that checks if bun exists and if so it uses the faster API and if not it falls back to Node. If Bun gets remotely popular I imagine this would be very common. But that's just one more dependency to maintain in your project, which sort of defeats the point of an "all in one" system that lets you skip having tooling dependencies if everyone that uses it has to install additional tooling libraries to make it easier to use. Meta-language support - Should Node.js have the Vue-Template-Compiler built in? It sounds absolutely insane to ask that. What about Markdown, or Sass, or CoffeeScript? Yeah, that would be pretty stupid for the main platform that everything is built on top of to just build in. It would feel very short-sighted. Meta-languages exist to fill in a gap in the original languages, they are by their nature impermanent and flexible. They're like adding really good suspension to your car as your drive over the potholes in the original language. Until the original language can come by and fill the potholes. There is a reason we don't use CoffeeScript anymore, most of the features it offered were added into the language in ES6. CSS has slowly added "good enough" equivalents to a few high value Sass features, and we've seen the first decline in Sass usage ever afterwards. But here we are with the worst templating system, JSX and the most contentious of all frontend tooling, TypeScript built in to Bun. TypeScript's usage plateaued around 2020 (at a little over a 3rd of the JS ecosystem having adopted it), and in the past year finally showing its first signs of decline as it is replaced with better, simpler alternatives like eslint-plugin-jsdocs ( get started here ), and a potential comment based ES202X official type system that will likely lead to a rapid decline in the need for creating .ts files. With these potholes filled, TypeScript will need to either find new potholes to try to smooth out and justify it's existence, or accept that it's job is done and slowly fade away. Never actually dying, the same way CoffeeScript is still technically around, but ultimately being another sign of an older era. Like all the other once-useful technologies we've evolved beyond the utility of (LESS, Stylus, Sass, CoffeeScript, Yarn, Grunt, etc.). Sass is a great example. It was at one point used by ~96% of frontend devs and had an over 90% satisfaction rate ( State of CSS 2019 ). But has dropped in usage and satisfaction as the Meta-Language's API evolved to become much more complex in order to solve more complex problems. It is no longer focused on being the dead-simple tool for everyone, and is now focused on being a very advanced tool for people doing very advanced things. A much more niche use. I keep wondering what weird mishmash of technologies Bun would have been made out of it it came out in a previous year, and what weird legacy code they would be stuck maintaining today. If it came out in 2019 at the peak of Sass, used by basically everyone, it would totally make sense as a candidate to build into Bun right? But then what do you do when all of the Sass API's change and the old import system is completely deprecated? Normally you'd just npm install the version of Sass you need for your project, and pin the old version if that's what your code worked with and you don't want to upgrade. But if you were using Bun for this, and then you come back to it a few years later and now the project just won't build because the Sass version in Bun isn't compatible with the Sass code you wrote, you need to spend a day trying to figure out what version your code actually needs and manually installing the correct version of Sass to get your project to run again. That's why it would be insane to build a meta-language into Node.js, or by extension, Bun. But that's what they've done, and I forsee pain in the future for those that rely heavily on it instead of as a simple quick convenience. That last one, built-in meta-languages, sort of leans into what Bun really is. It's just an abstraction layer for a bunch of technologies. It isn't an actual alternative, or competitor, it's literally the same thing, just already built in. Which sounds nice on paper, but ultimately is pretty bad. Abstractions can be great, and simplify things. Let's look at Webpack for example. Webpack is... well just awful. NO ONE likes dealing with it. And that's why every JS Framework had to build an abstraction layer for it, because no wants to touch Webpack. Like the Angular-CLI, or Create-React-App, or Svelte-CLI, or the phenomenal Vue-CLI (which even has a GUI). We'll use Vue as the example, since it did the best job out of all of these abstractions. The vue.config.js file was a simple config that abstracted away all of the complexity of Webpack, while still giving you the exact same level of control if you needed it. It also reduced the amount of dependencies down from around 30-ish to like 3-ish. But then Vue's creator, Evan You, went and made Vite. And the vite.config.js was basically the same exact level of complexity as the vue.config.js except it didn't require them to maintain an entirely separate project (the Vue-CLI) to make it that way. Switching from Vue-CLI over to Vite, I ended up with the same amount of dependencies, and the same amount of config code. The end result is Vite is an abstraction layer for ESBuild that is as easy to use as the best abstraction layer for what it was replacing. But Bun isn't doing that. It isn't taking something hard, and making a simpler abstraction for it. It's taking ESBuild and abstracting it just like how Vite is. It's not an improvement, it's basically the same thing. This is also the case for unit tests. Where they don't even pretend to offer something new, instead telling you to write your code as Jest or Vitest like normal, and they'll just hijack the imports and replace them with their own faster code under the hood. Bun is just an abstraction layer on top of the tools we already have. Meaning it will always be behind the curve and can introduce additional bugs at that layer. Not ideal for such mission critical systems like installing dependencies , testing code , and building the code to be sent to production . But we haven't even gotten to the two worst things Bun does, and the really scary parts. Windows I picked on Yarn for it's poor Windows support. But they look amazing compared to Bun. At least they kind of had Windows support when they released it. It only barely worked some of the time, but it was there. However, of the dozens of features that Bun brags about, not even one of them is supported on Windows when it was released as "version 1.0". "The Windows build is highly experimental and not production-ready. Only the JavaScript runtime is enabled; the package manager, test runner, and bundler have been disabled. Performance is not optimized." - Official Bun 1.0 blog post So imagine this, they just launched and are showing off all these cool features that they are excited about and want people to use. What is more likely to happen? As thousands of people start using it and giving feedback, finding bugs, requesting features, needing support, do you think they will: A. Completely ignore all of the new users for the next year and focus solely on getting complete feature parity and making a polished, rock-solid, reliable, ultra-fast, Windows compatible build. Likely killing off any momentum they built from their initial hype-cycle, and maybe even losing them the VC funding they've been living off of. B. Focus almost all of their very small team's efforts on keeping their existing user's happy by improving the Linux/OSX versions that already mostly work so that the product looks well maintained and can slowly gain adoption within those communities, while being virally spread by tribal developers intentionally creating non-portable code, knowing that it will not work in Node, or even on Windows. I genuinely believe they have every intent on getting a Windows version up and working. I just do not believe for a second that a year after 1.0 is released that they will have feature parity in the Windows version. Maybe the Windows version will have feature parity with version 1.0 by then, but I doubt they will be stopping all work on the Linux version for a year. At that point the two flavors of Bun will be out of sync with each other, leading to confusion. This leads us into the biggest missing feature of Bun. There is no Bun Version Manager Of all the tools they put into Bun, the one tool they didn't build in is a version manager. That is INSANE to me. I think it's actually insane that Node.js doesn't have a version manager built in. Let's break this down. On Node.js I have: nvm - Which mostly works fine on linux/osx, but has some annoyances. nodist - Which is great, but only works on older versions of Windows. nvm-windows - For newer Windows versions, but barely works and is buggy as hell. volta - Which has the worst API of all of them, but is also the most stable and reliable and runs on all OS's, even really old versions of Windows. Why do I have to know about these 4 tools? This is stupid. But what's considerably worse than having to deal with 4 tools that do the same thing is just not having any tool at all. Node.js is WAY more focused on backwards compatibility than Bun is. But as time has gone on, even Node has deprecated parts of their API. Many times this is a result of the V8 engine itself deprecating features. Node.js is actually involved somewhat in the direction of V8 at this point, and even with having some level of input, it isn't possible for them to avoid all breaking changes and deprecations, leading to old Node.js code straight up not working on newer versions of Node. So I don't believe for a second that Bun got everything right on the first try, and nothing about it will change over time, and all code you write in it, will always work forever. Especially since they are inheriting whatever deprecations will come with the Apple Webkit JS engine they are using. What about a year from now when Bun 1.8 on Linux is out, but Windows just hits 1.0. Where I work, the devs on my team use different OS's (Linux, OSX, Windows). If we can't freely switch between versions of bun, then our Linux user's won't be able to downgrade to version 1.0 so we are all working with the same features (generously assuming a Windows version is released by then). We as web developers used Grunt for our build tooling. Then Gulp came out and made the process simpler and we switched over to it. Then Gulp 4 came out and completely changed the API and no one wanted to deal with that so we switched to npm scripts for our basic build automation. But then we wanted actual bundling abilities and tree shaking. So we, as an entire JS community, switched to Webpack (or more accurately, abstractions on top of it). But Webpack was slow and annoying, so when Vite came out we all switched over to it. But ya know what? I'm not in love with Vite. Is it the best thing right now? Yeah it is. But there are things about it I wish were better. And over the coming years more and more of those things will be identified and someone will inevitably make a new tool that is better than Vite, and I will happily switch to it. Not because I like changing tooling, but because from a practical stand point it will be better, and I will see the value in it and switch. That's it. Even if you think "nope, there is nothing left to do with our tooling, we've perfected minification". Do you think we have perfected everything on the web? What features of the web exist today that did not 10 years ago? What if, hypothetically, 10 years from now we finally have something in the browser that replaces Web Components and doesn't suck ? Won't we need some form of new build tooling to transform our code and take advantage of these native features? Just like we have today? As networks and internet protocols change and improve, how we optimize our bundles for them will change too. The web has always changed and evolved. It's never stopped. It will continue to change, and our tooling will continue to react to those changes. That will also be the case with everything that Bun is abstracting. When does it decide to drop its ESBuild abstraction and switch to whatever that new thing will be? What if it switches too soon, and the community goes with something else, and it needs to switch again? There's only so much you can do to guard against API changes for your end users. If all of Bun's users need to maintain a bunch of ESBuild plugins to work with Bun, and then ESBuild is removed from under the hood and replaced, then those users are stuck on the old Bun version. What happens when you use Bun to handle your build AND also your core JS runtime AND your testing tools. Then Bun does a major breaking change to one of those systems requiring a lot of tech debt to update your codebase to be able to switch over. Maybe your tests all need upgraded to work with the new system (I've done 3 major test refactors in my work codebase, the longest taking ~6 months to complete, this stuff happens). It could take months, maybe even a full year to upgrade all your code. And in the mean time you're stuck on the old version of Bun until everything works with the new version. BUT OH NO! A big security issue is found in the JS Runtime. So you need to update the JS Runtime, but you can't do that because your JS Runtime and your build tool and your testing tool are all the same. Until your major test refactor is complete, your code is vulnerable. In some industries you are required to address security issues in a certain window of time. Bun is a no-go for those folks. There are ways for them to deal with this, like shipping multiple build tools, or testing tools, and letting you switch to the new one or old one via a CLI argument. But how long do they support multiple alternative tools being built in? Can they afford to support all of them? With all the various abstractions for tools they have built in to Bun, it is only a matter of time until the glue holding it all together becomes too much to manage. Node, npm, Jest, Vite, etc. These are all large and very complex problem spaces each tool is separately solving. Even Vitest, under the hood is like 80% shared code with Jest, and just trying to handle the other 20% is a major effort. What happens when JavaScript Shadow Realms are released? Vitest is already planning on adopting Shadow Realms as a way to isolate JavaScript tests without having to spin up new Node processes. If my Vitest code is reliant on running in this isolation mode and Bun decides to hijack my imports instead of using the actual Vitest imports suddenly my tests could start randomly failing and there won't be anything I can do about it without removing Bun from the equation until they can update their code under the hood to use Shadow Realms. But what if realms are added into V8, but then Apple drags their feet on adding support into Safari for several years (they do that a lot ). There's literally nothing Bun could do in that scenario other then make their own internal native implementation of shadow realms until the feature is built in to Webkit. Which would be a pretty major undertaking and not a very scalable solution long term for other similar problems that come up. All of these reasons and more are why Bun Version Management is so important. And why having so many tools combined into one isn't as nice as it sounds on paper. Part Three - Random thoughts If Bun came out in 2012, it would have had Grunt built in. If Bun came out in 2014, it would have had Gulp built in. If Bun came out in 2016, it would have had Webpack built in. If Bun came out in 2018, it would have had Rollup built in. If Bun came out in 2020, it would have had ESBuild built in. What will happen in 2026? Back in 2014 Meteor JS came out and promised to do everything in one frontend/backend framework. It would handle websockets for you, and do reactive updating of the DOM and assume backend success but automatically rollback the UI if the request failed, to make the UI feel real fast and snappy. It let you have multiple people interacting with content on the same page in real time. And all you had to do was use their all-in-one CLI to run your project locally and deploy it to a free online test bed using your own custom project name. In 2023 I tried to run my 2014 Meteor project again and the version of the CLI that is compatible with the project doesn't exist any more and the project cannot be ran locally or deployed without completely re-writing the entire project to the latest version of Meteor. All documentation for the 2014 version is just gone. I have seen this movie before, and I know how it ends. Part Four - Final thoughts I've been very hard on Bun in this post, not because it sucks, but because it's almost good. And people will be excited to try it out and not realize all the downsides. Again, just like with Yarn, I was pretty hyped for Bun too. But I've since tempered my excitement and looked at it from a practical, and historical, standpoint. If Bun actually did everything it claimed, then I would 100% be on board. But the non-portable code, the complete lack of Windows support, and some of the shortsighted choices they've made bring me back to reality. I hope these critiques will lead to improvements in Bun. I hope that this thought process will allow others to look at Bun from a more cautious and thoughtful perspective. I hope these tales of Yarn and Meteor will allow us as a community to learn from our past. Part Five - My predictions for the future Most of the projects Bun picked on will get performance improvements over the next year or so and tighten the gap between them and Bun. You will start seeing more and more repos that mention Bun in their README's, maybe exclusively. All developers that quit their first dev job after 6 months to become a YouTube Coding Influencer will make a "BUN IS THE FUTURE OMG" video with this thumbnail . In the hope that it will trick people into watching their 12 part tutorial series on Bun. Like & Subscribe. We have not perfected our tools yet. As we continue to evolve and invent newer and better options Bun will struggle to keep up and people will slowly use it less as they get impatient and are willing to just install a dependency if it means a better, more practical solution to their problems than what they had. Bun will probably be around for about 5 years. That seems to be the life span for most similar tooling. Bun will eventually have really really great Windows support... probably right as people stop using it. For some reason Bun never adds in a version manager and instead 4 competing options show up all sucking in different ways. The year is 20XX and we have finally converted the last CJS Node Module to ESM. This was only possible after humanity finally gave in and let the AI take over. Was it worth it? Joe Biden will get a second term, but like, no one is really happy about it. It turns out that Yarn guy really did see Sasquatch. Now I feel bad for making fun of him. Honestly, Harry and the Hendersons may be worth a rewatch. Vue is still better than everything else, but people will just use whatever the youtube coders said was the hot new thing because if it wasn't, why would they have made 20 tutorial videos about it? They're going to remake Breaking Bad and it won't be very good. Someone in Primagen's chat is actually right about something for the first time ever. Did you know he works at Netflix? Top comments (125) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Barry Michael Doyle Barry Michael Doyle Barry Michael Doyle Follow 👨💻 Senior Frontend Engineer @ Crypto Exchange 💻 Boosting Tech Careers 🚀 Sharing Developer Insights 🛤️ Explore ⚛️ ReactJS, 📱 React Native, 🌐 NextJS & 🔷 TypeScript with me. Let's grow! 🌱 Location Cape Town, South Africa Education Bachelor of Science in Computing Pronouns He/Him Work Senior Frontend Engineer at Crypto Exchange Joined Nov 13, 2017 • Sep 16 '23 Dropdown menu Copy link Hide I don't know about all the points made in this post. Bun is not the solution to everything, but the speed benefits it give to scenarios like a replacement to jest are well worth it for me and my team. I love that fact that is a set of tools that you don't NEED to buy fully into. Regarding No Version Manager , I don't believe it is a priority to built a version manager when version 1 is only 1 week old, I think that would probably be more useful later on. I believe they're being pragmatic and releasing something usable that is stable. It's probably better than delaying a stable release with slightly more feature by 6 months. Otherwise great article and I look forward to coming back here and seeing how many of your predictions come true, especially the Breaking Bad part. Keep up the good writing! I enjoyed this and just wanted to mention my thoughts on some of the points here :) I do hope (and believe) that some of the things that Bun brings to the table does make it's way back to improving NodeJS. Like comment: Like comment: 35 likes Like Comment button Reply Collapse Expand The Jared Wilcurt The Jared Wilcurt The Jared Wilcurt Follow Cross-Platform Desktop App (XPDA) Engineer, Senior Frontend Web Developer. Maintainer of Scout-App. Editor of XPDA.net. Location Indianapolis, IN Joined Jul 27, 2017 • Sep 16 '23 Dropdown menu Copy link Hide The smaller the dosage you use Bun, the lower the risk. If you go all in, and use every feature it offers exclusively, then you are at high risk for running into the pain points outlined in this article. If you are able to replace a feature Bun offers with a different approach in a reasonable amount of time, and be back to normal, then I think it's totally valid to adopt it for that use. I hope you and your team get some value out of Bun and don't run into any of the problems I'm worried about. Like comment: Like comment: 10 likes Like Comment button Reply Collapse Expand Barry Michael Doyle Barry Michael Doyle Barry Michael Doyle Follow 👨💻 Senior Frontend Engineer @ Crypto Exchange 💻 Boosting Tech Careers 🚀 Sharing Developer Insights 🛤️ Explore ⚛️ ReactJS, 📱 React Native, 🌐 NextJS & 🔷 TypeScript with me. Let's grow! 🌱 Location Cape Town, South Africa Education Bachelor of Science in Computing Pronouns He/Him Work Senior Frontend Engineer at Crypto Exchange Joined Nov 13, 2017 • Sep 16 '23 Dropdown menu Copy link Hide That's a very mature point. Yeah in our specific case we've given it a shot to replace jest and it was as simple as a plug and play, it works pretty much exactly the (except it's quicker) and we haven't had to change any of our existing tests. The only difference of using Bun has been that we don't need use all the config for setting up jest that we had before. For now we'll keep the Jest config in-case we try to revert. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Ediur Ediur Ediur Follow Location Albania Joined Oct 21, 2019 • Sep 25 '23 Dropdown menu Copy link Hide I totally agree with you. I would just add that if, according to this article, it took NPM 5 years to catch up with Yarn, probably it would have taken 10 year to achieve the same progress if yarn was not introduced. I would say the same thing for Node.js even if some day catches up with Bun. IMHO, In overall, competition is the driving force behind remarkable innovations and progress and these diverging paths from the mainstream often bring significant value and who knows, It might become the main stream itself. Speaking of Tailwind, I was one of those developers that thought, it was the worst thing that had happened to web development, until I " suppressed the urge to retch" it and tried it. Now I can not go back to writing vanilla CSS. Like comment: Like comment: 12 likes Like Comment button Reply Collapse Expand Dave Rogers Dave Rogers Dave Rogers Follow Joined Sep 28, 2022 • Oct 4 '23 Dropdown menu Copy link Hide i'd imagine the idea is that the Yarn devs should've contributed those features to NPM directly. that said, idk how contributor-friendly the NPM team is. some core teams, like PHP Core, sort of meander until they're pushed by the threat of competing projects (in PHP they had to contend with Hack, which was much faster and had some nice features PHP lacked, and PHP quickly addressed these in PHP 7 which kept most PHP devs around; Hack now looks like a different language to a degree, afaik is only useful to Facebook). sometimes the threat of splitting the ecosystem is a good thing, but shouldn't be wielded as a first option. and in defense of core teams, having companies like Facebook threaten to split your ecosystem if they don't get their super specific features/changes (that sometimes don't benefit anybody but them) is also pretty gross so i don't always disagree with telling them where to stick it. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Rahul Dey Rahul Dey Rahul Dey Follow Joined Sep 18, 2023 • Sep 18 '23 Dropdown menu Copy link Hide Nodejs has a fast built in test runner. Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Adaptive Shield Matrix Adaptive Shield Matrix Adaptive Shield Matrix Follow Joined May 22, 2021 • Oct 26 '23 Dropdown menu Copy link Hide But it does not work with typescript code. If you have to compile your code first -> its like 10x slower instead. Like comment: Like comment: 2 likes Like Thread Thread Barry Michael Doyle Barry Michael Doyle Barry Michael Doyle Follow 👨💻 Senior Frontend Engineer @ Crypto Exchange 💻 Boosting Tech Careers 🚀 Sharing Developer Insights 🛤️ Explore ⚛️ ReactJS, 📱 React Native, 🌐 NextJS & 🔷 TypeScript with me. Let's grow! 🌱 Location Cape Town, South Africa Education Bachelor of Science in Computing Pronouns He/Him Work Senior Frontend Engineer at Crypto Exchange Joined Nov 13, 2017 • Oct 26 '23 Dropdown menu Copy link Hide Ah right, that makes sense why the bun hype is there. Yeah I'm pretty much all in on TypeScript so I guess that puts bun right back up there for my test runner of choice :) Like comment: Like comment: 3 likes Like Thread Thread The Jared Wilcurt The Jared Wilcurt The Jared Wilcurt Follow Cross-Platform Desktop App (XPDA) Engineer, Senior Frontend Web Developer. Maintainer of Scout-App. Editor of XPDA.net. Location Indianapolis, IN Joined Jul 27, 2017 • Nov 11 '23 Dropdown menu Copy link Hide You have identified a problem with TypeScript, not with Node. TS has always been excruciatingly slow. Many are now switching over to JSDocs for type management. It has many benefits over the TS Language while still being completely compatible with the TS Engine and tsc . However there is no build or runtime cost. You can do enforcement of keeping your JSDoc comments up-to-date via a simple linting plugin. If you don't want to configure all the linting rules yourself, this is the easiest 2 step process to get started github.com/tjw-lint/eslint-config-... Like comment: Like comment: 3 likes Like Thread Thread Barry Michael Doyle Barry Michael Doyle Barry Michael Doyle Follow 👨💻 Senior Frontend Engineer @ Crypto Exchange 💻 Boosting Tech Careers 🚀 Sharing Developer Insights 🛤️ Explore ⚛️ ReactJS, 📱 React Native, 🌐 NextJS & 🔷 TypeScript with me. Let's grow! 🌱 Location Cape Town, South Africa Education Bachelor of Science in Computing Pronouns He/Him Work Senior Frontend Engineer at Crypto Exchange Joined Nov 13, 2017 • Nov 11 '23 Dropdown menu Copy link Hide Bun still seems like a more elegant solution to my TypeScript problem though. I'm personally not a big fan of JSDocs as a replacement for TypeScript in its current state. Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Barry Michael Doyle Barry Michael Doyle Barry Michael Doyle Follow 👨💻 Senior Frontend Engineer @ Crypto Exchange 💻 Boosting Tech Careers 🚀 Sharing Developer Insights 🛤️ Explore ⚛️ ReactJS, 📱 React Native, 🌐 NextJS & 🔷 TypeScript with me. Let's grow! 🌱 Location Cape Town, South Africa Education Bachelor of Science in Computing Pronouns He/Him Work Senior Frontend Engineer at Crypto Exchange Joined Nov 13, 2017 • Sep 18 '23 Dropdown menu Copy link Hide How fast is it compared to bun and how much config setup does it require to run alongside things like RTL? Like comment: Like comment: 2 likes Like Thread Thread Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Follow Ultra-fullstack software developer. Python, JavaScript, C#, C. Location Earth Education I am a master of science Pronouns He/him/his/his Work Software Engineer Joined May 2, 2017 • Sep 18 '23 Dropdown menu Copy link Hide I saw a comparison in this video . Like comment: Like comment: 12 likes Like Comment button Reply Collapse Expand Ed Rutherford Ed Rutherford Ed Rutherford Follow IT Support Engineer, Cybersecurity Journeyman, Multi-Language Programmer. Avid learner of all things, and enjoy sharing with those willing to listen! Location Columbus, Ohio Education Devry University; The Ohio State University; Google IT Support Certification Work IT Support Engineer Joined Dec 1, 2022 • Sep 22 '23 Dropdown menu Copy link Hide Definitely an interesting article, and @barrymichaeldoyle I definitely agree that while Bun isn't the end-all-be-all, it certainly offers an excellent (and fast!) alternative for devs to utilize instead of the vast web of Node components. I've recently started building a number of project updates with Bun as a drop in and the reduction of time to test and build has been pretty darn impressive! Granted, most of these projects aren't exactly "huge".... even still, it's extremely noticeable how much quicker the process is regardless of the overall project complexity! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Cezary Tomczyk Cezary Tomczyk Cezary Tomczyk Follow Joined Feb 23, 2023 • Sep 16 '23 • Edited on Sep 16 • Edited Dropdown menu Copy link Hide I can't find on Bun's site that they use WebKit engine. I see: At its core is the Bun runtime, a fast JavaScript runtime designed as a drop-in replacement for Node.js. It's written in Zig and powered by JavaScriptCore under the hood, dramatically reducing startup times and memory usage. My personal opinion is that Bun is trying to build too many things around it, like TypeScript. Which effectively leads to so many distractions instead of focusing on core, stability, and performance. It will be a huge ballon that will eat memory with probably 70% of features not used. There will be quantity over quality. At the moment of writing this comment, there are 1590 open issues and 1703 closed. At this rate of bug growth , Bun will spend more and more time fighting bugs rather than stability and performance. Let's assume that it takes 4 hours to fix each bug (extremely optimistic), that's already 6360 hours spent just on fixing bugs. Let's keep counting, 8 hours a day, that's 795 days! 795 / 365 gives you over 2 years of work just to fix 1590 bugs! And it will keep growing, as implementing too many features is just a consequence of that. To the whole great post, I'd also add the overhyped Tailwind, which literally does nothing new and makes the whole development even worse. See example: flex transition-all dark:bg-darkNight bg-white duration-1000 relative 4xl:max-w-11xl 4xl:mx-auto 4xl:shadow-xl 4xl:rounded dark:shadow-4xl vs. chat-message Tailwind complicated development 10 times by moving from logical to illogical order. What's wrong with reusable classes? What's wrong with named CSS classes? Instead of first looking at named classes to understand what follows, the engineer now needs to spend time decrypting the intention of the implementation behind all CSS classes. It should be the opposite: Read the name of the class. Interested? Dive into implementation details. Not interested? Keep searching. That approach allows you to quickly scan the app logic without diving into implementation. Like comment: Like comment: 18 likes Like Comment button Reply Collapse Expand Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Follow Ultra-fullstack software developer. Python, JavaScript, C#, C. Location Earth Education I am a master of science Pronouns He/him/his/his Work Software Engineer Joined May 2, 2017 • Sep 18 '23 Dropdown menu Copy link Hide To quote trac.webkit.org/wiki/JavaScriptCore JavaScriptCore is the built-in JavaScript engine for WebKit. Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Cezary Tomczyk Cezary Tomczyk Cezary Tomczyk Follow Joined Feb 23, 2023 • Sep 18 '23 Dropdown menu Copy link Hide @mellen Thank you! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Andrzej Kowal Andrzej Kowal Andrzej Kowal Follow Senior Frontend Developer Location Poland, Krakow Pronouns He/His Work Senior Frontend Developer Joined Sep 17, 2023 • Sep 18 '23 Dropdown menu Copy link Hide You can always compose your own additional css class from tailwind css utility classes. What’s wrong with that approach which can be applied to such cases with classes that are too long/unreadable? Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand The Jared Wilcurt The Jared Wilcurt The Jared Wilcurt Follow Cross-Platform Desktop App (XPDA) Engineer, Senior Frontend Web Developer. Maintainer of Scout-App. Editor of XPDA.net. Location Indianapolis, IN Joined Jul 27, 2017 • Sep 20 '23 Dropdown menu Copy link Hide This is outside of the scope of this article. However, I would note that Tailwind's create (Adam Wathan) has specifically said that what you are advising is an anti-pattern and that @apply was only added to trick people into using Tailwind that did not like their HTML being littered with dozens of classes. His words, not mine. Source Like comment: Like comment: 5 likes Like Thread Thread Cezary Tomczyk Cezary Tomczyk Cezary Tomczyk Follow Joined Feb 23, 2023 • Sep 20 '23 Dropdown menu Copy link Hide @thejaredwilcurt This is outside of the scope of this article. That's for sure. However, I'd really love to hear what kind of problems Tailwind resolves that existed before. Like comment: Like comment: 2 likes Like Thread Thread Rocky Kev Rocky Kev Rocky Kev Follow Blog Location Portland Work Senior Dev at 2Barrels Joined Feb 17, 2019 • Sep 21 '23 Dropdown menu Copy link Hide If your company was using a css framework before, tailwind is solving that. pb-3 in bootstrap... what does the 3 mean? It means whatever your default size is. But what if you want something bigger? pb-4 ? But that's too big. Tailwind solves a lot of that. Like comment: Like comment: 1 like Like Thread Thread Andrzej Kowal Andrzej Kowal Andrzej Kowal Follow Senior Frontend Developer Location Poland, Krakow Pronouns He/His Work Senior Frontend Developer Joined Sep 17, 2023 • Sep 21 '23 Dropdown menu Copy link Hide I thing it should not be that much treated as the only way. If you need couple of composes classes - world will not break. You definitely don’t need to make own class for each element in the tree - it’s for sure is not as it supposed to be done. But just few classes for very long class names - it’s fine I think. Like comment: Like comment: 1 like Like Thread Thread Cezary Tomczyk Cezary Tomczyk Cezary Tomczyk Follow Joined Feb 23, 2023 • Sep 21 '23 Dropdown menu Copy link Hide Because this Tailwind is more understandable? h-screen xl:min-w-282pxl xl:w-260pxl hidden xl:block overflow-y-hidden dark:bg-darkNight dark:border-matteGray font-ubuntu Like comment: Like comment: 2 likes Like Thread Thread Pablets Pablets Pablets Follow Learnig, all the time Location Buenos Aires Work Software engineer at Santander, Argentina Joined Nov 24, 2020 • Oct 20 '23 Dropdown menu Copy link Hide I love Tailwind and SASS, but they have trade-offs. Tailwind offers scalability and maintainability, reducing the complexity of naming conventions. If your project doesn't scale, then Tailwind may have more cons than pros, as it truly shines when maintaining large codebases with specific needs like SSR or performance. I understand that it can be cumbersome and verbose to write styles like this, but using them at the right moment can be a lifesaver. I think it's really important to know and experiment about everything that you can to know what these cons/pros are and understand what it's the right tool for the job. Like comment: Like comment: 2 likes Like Thread Thread Cezary Tomczyk Cezary Tomczyk Cezary Tomczyk Follow Joined Feb 23, 2023 • Oct 20 '23 • Edited on Oct 20 • Edited Dropdown menu Copy link Hide @pablets Would you mind to explain what kinds of problems exactly does Tailwind solve? The "scalability and maintainability, reducing the complexity of naming conventions" doesn't explain the issue and what kind of solution was invented by Tailwind to resolve it. Is this bg-white dark:bg-darkNight dark:border-matteGray border-b border-grayLighter w-full flex justify-between px-2 py-3 items-center xl:hidden fixed top-0 z-20 called a "reducing the complexity of naming conventions"? If so, how so? Can you give an example of scalability challenges and how Tailwind resolves them? I'd appreciate it. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Cezary Tomczyk Cezary Tomczyk Cezary Tomczyk Follow Joined Feb 23, 2023 • Sep 19 '23 Dropdown menu Copy link Hide @andrzej_kowal Composing your own CSS class was available long before Tailwind was born. My primary question is: what kind of problems does Tailwind resolve that weren't resolved before? Like comment: Like comment: 5 likes Like Thread Thread Stephen Hebert Stephen Hebert Stephen Hebert Follow Joined Jul 9, 2021 • Sep 20 '23 Dropdown menu Copy link Hide By making styling more visible and flexible, and limiting cognitive load. When working with a massive component-based SaaS codebase and an immature, unstable design system, I want to see styles in the DOM template of the component where they’re being applied without having to reference several different CSS files written by different authors at different times all applying globally what they thought could be taken for granted finding myself in CSS cascade hell trying to implement something new without breaking existing legacy UIs or take on the complexity of the entire system. Pure CSS is beautiful and I can’t wait to ditch Tailwind… later, when the design system is mature and my UI is all nice, clean components, and what a joy it will be (and so easy too) to replace all of those tailwind classes with clean, structured CSS. But | 2026-01-13T08:49:34 |
https://popcorn.forem.com/popcorn_movies/ringer-movies-a-holiday-surprise-for-the-unboxing-boy-4gma | Ringer Movies: A Holiday Surprise for the Unboxing Boy - Popcorn Movies and TV Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Popcorn Movies and TV Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Movie News Posted on Dec 6, 2025 Ringer Movies: A Holiday Surprise for the Unboxing Boy # reviews # offtopic A Holiday Surprise for the Unboxing Boy The Unboxing Boy is back with a festive twist, unwrapping five surprise physical-media gifts handpicked by his wife. Expect plenty of genuine reactions and holiday cheer as he dives into each package. Don’t miss out—subscribe to The Ringer-Verse and Bill Simmons channels on YouTube, check out the Ringer shop and website, and follow on Twitter, Facebook, and Instagram for more unboxing fun! Watch on YouTube Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Movie News Follow Joined Jun 22, 2025 More from Movie News Ringer Movies: The 2026 Golden Globes: ‘One Battle After Another’ vs. ‘Hamnet’ Begins # movies # reviews # analysis # streaming CinemaSins: Everything Wrong With Austin Powers in Goldmember in 19 Minutes Or Less # movies # reviews # analysis # marketing Ringer Movies: Five Burning Questions About Awards Season & Our Golden Globes Predictions # movies # analysis # reviews # recommendations 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Popcorn Movies and TV — Movie and TV enthusiasm, criticism and everything in-between. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Popcorn Movies and TV © 2016 - 2026. Let's watch something great! Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/petar_liovic_9fb912bdc228/mathematical-audit-of-excalidraw-finding-logic-echoes-via-linear-algebra-26pj | Mathematical Audit of Excalidraw: Finding "Logic Echoes" via Linear Algebra - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Petar Liovic Posted on Jan 12 Mathematical Audit of Excalidraw: Finding "Logic Echoes" via Linear Algebra # architecture # computerscience # react # tooling The Signal is Getting Stronger When I released the first version of react-state-basis , the goal was theoretical: could we model React hooks as temporal signals to detect architectural debt? Since then, the project has hit #1 on r/reactjs and gained validation from senior engineers at companies like Calendly and Snowpact. But for v0.3.1 , I wanted to move from "Theory" to "Forensics." I wanted to run the auditor against one of the most high-performance engines in the React ecosystem: Excalidraw . The "Invisibility" Milestone (v0.3.1) The biggest barrier to architectural telemetry is the "Import Tax." No one wants to change their source code to run an audit. As of v0.3.1 , Basis is now a "Ghost" in the machine . Using a custom Babel AST transformer and a Vite Proxy , it auto-instruments standard React imports at build-time. Semantic Extraction: It reads your source code to label hooks automatically (e.g., count , user ). Zero Code Changes: You keep your import { useState } from 'react' exactly as is. Isomorphism: The proxy maintains 100% type congruence, ensuring the IDE and compiler see a "perfect body double" of React. Case Study: Auditing Excalidraw Excalidraw is a 114,000-star project and a masterpiece of performance engineering. It handles massive amounts of high-frequency state transitions. It was the perfect "Laboratory" for the R⁵⁰ vector model. The Audit Results: 1. Dimension Collapse in the Theme Engine The Basis HUD immediately flagged a perfect collinearity (1.0 similarity) between appTheme and editorTheme in the core theme-handle hook. The Math: These two vectors were pulsing in identical coordinates in the 50-dimensional space. The Debt: One variable was a redundant mirror of the other, kept in sync via an imperative effect. 2. Sequential Sync Leaks (Causal Loops) The telemetry matrix detected multiple "Blue Box" violations . These represent directed edges in the component's causal topology where an effect "pushes" data back into state after the render pass. The Cost: In a high-performance canvas, these sequential updates force unnecessary double-reconciliation cycles, adding avoidable overhead to every theme toggle and window focus event. Closing the Loop: The Refactor An auditor's job isn't just to find problems; it's to provide the Basis for a Solution . I submitted a Pull Request to Excalidraw (which was recently noticed and reposted by @vjeux on x.com platform, one of the most important people in the Frontend industry) to refactor this logic. The Fix: We removed the redundant state and moved to a Pure Projection using useSyncExternalStore and useMemo . The Win: Theme transitions now resolve in a single Atomic Render Pass , restoring the linear independence of the component's basis. What’s Next: v0.4.0 and Linear Maps We are now moving from Vector Spaces to Linear Operator Theory . To handle browser-thread jitter (1ms delays), we are investigating Signal Conditioning via linear maps. By applying a temporal convolution (smoothing) and a difference operator (velocity) to our R⁵⁰ basis, we can move from "Bit-Matching" to Scientific Signal Processing. Formalize Your Basis Basis is open-source and ready for zero-config integration. If you want to see the "heartbeat" of your own architecture and find where your logic is redundant, give it a run. GitHub: liovic/react-state-basis Technical Wiki: 8 Chapters on Vector Spaces and Causal Topology Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Petar Liovic Follow Full stack dev, Process Automation Architect (Camunda, BPMN, js) Joined Dec 27, 2025 More from Petar Liovic Auditing React State & Hooks with Math (shadcn-admin Case Study) # react # javascript # performance # webdev I used Linear Algebra to audit my React state (and built a tool for it) # react # typescript # linearalgebra # webdev 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://raspap.com/#quick | RaspAP - The Debian wireless router RaspAP Home Quick Start Kit Blog Docs Status Initializing search RaspAP/raspap-website Rasp AP The easiest, full-featured wireless router setup for Debian-based devices. Period. Quick start Get Insiders More than an access point RaspAP is feature-rich wireless router software that just works on many popular Debian-based devices, including the Raspberry Pi. Customizable, mobile-friendly interface in 20+ languages. Sets up in minutes. Multiple VPN options Popular OpenVPN , cutting edge WireGuard and Tailscale encrypted tunnels may be configured to securely connect your client devices. Ad block integration Streamline AP throughput for your clients by sending requests for ads, trackers and other undesirable hosts to DNS blacklist oblivion . Bridged mode Want your upstream router to assign IP addresses? RaspAP lets you change the default routed configuration to an alternate bridged AP mode. Easy to customize Modify RaspAP to suit your needs with a completely exposed default configuration , many installation options , themes and more. Docker ready Deploy RaspAP quickly in a portable, lightweight and isolated Docker container for all your application needs. Made for IoT Small on memory utilization yet big on features, RaspAP is ideal for IoT applications where wireless connectivity and data sharing are a must. Integrated API RaspAP includes support for stateless client-server data exchange via a high performance RESTful API based on FastAPI. Custom user plugins Want to extend RaspAP's functionality? A plugin manager and sample plugin make it easy for developers to create their own custom plugins . VPN provider control Administer several of the most popular VPN providers via their Command Line Interfaces (CLIs) directly in RaspAP's UI. Additional Features Data usage graphs for all interfaces SSL certificate support Captive portal integration Up-to-date security audits Advanced DHCP server control 802.11ac 5GHz operation Dynamic DNS support Auto-detect external wireless adapters WPA3-Personal + 802.11w support Docker support Fully responsive + mobile-ready Get Started with RaspAP Our frequently asked questions (FAQ) are continuously updated and are a great place to start. Need help not covered in the FAQ , have an idea or want to share your project with the RaspAP community? Head over to our GitHub Discussions or join our Discord . For everything else and more detailed information, dive into our official documentation . Quick Start The Debian wireless router RaspAP/raspap-website Home Quick Start Kit Blog Docs Status Home Back to top Next Quick Start Copyright © 2025 - All rights reserved Made with Material by A3Bagged | 2026-01-13T08:49:34 |
https://dev.to/t/espa%C3%B1ol | Español - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # español Follow Hide Create Post Older #español posts 1 2 3 4 5 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Agentes de IA: Dominando 3 Patrones Esenciales (Reflexive). Parte 3 de 3 Gabriel Melendez Gabriel Melendez Gabriel Melendez Follow Jan 4 Agentes de IA: Dominando 3 Patrones Esenciales (Reflexive). Parte 3 de 3 # spanish # ai # programming # español Comments Add Comment 5 min read Agentes de IA: Dominando 3 Patrones Esenciales (ReAct). Parte 2 de 3 Gabriel Melendez Gabriel Melendez Gabriel Melendez Follow Jan 4 Agentes de IA: Dominando 3 Patrones Esenciales (ReAct). Parte 2 de 3 # spanish # ai # programming # español Comments Add Comment 6 min read Surya OCR vs Tesseract en CPU con Python Carlos m. Ruiz Carlos m. Ruiz Carlos m. Ruiz Follow Jan 5 Surya OCR vs Tesseract en CPU con Python # python # ocr # machinelearning # español Comments Add Comment 4 min read Agentes de IA: Dominando 3 Patrones Esenciales (Tool Using). Parte 1 de 3 Gabriel Melendez Gabriel Melendez Gabriel Melendez Follow Jan 3 Agentes de IA: Dominando 3 Patrones Esenciales (Tool Using). Parte 1 de 3 # spanish # ai # programming # español Comments Add Comment 6 min read [ES] ContextFX - Un CDI ligero para JavaFX/GluonFX con soporte de ReactFX Ramon Ramon Ramon Follow for ContextFX Nov 29 '25 [ES] ContextFX - Un CDI ligero para JavaFX/GluonFX con soporte de ReactFX # javafx # gluonfx # español # reactfx Comments Add Comment 1 min read Fundamentos de JavaScript - Variables: La Base de Cualquier Programa Martín Aguirre Martín Aguirre Martín Aguirre Follow Oct 1 '25 Fundamentos de JavaScript - Variables: La Base de Cualquier Programa # webdev # javascript # programming # español Comments Add Comment 11 min read Despliega Agentes de IA con memoria a largo plazo a Producción en 15 Minutos (Sin Docker, Sin Kubernetes, Sin Dolor de Cabeza) Elizabeth Fuentes L Elizabeth Fuentes L Elizabeth Fuentes L Follow for AWS Español Oct 22 '25 Despliega Agentes de IA con memoria a largo plazo a Producción en 15 Minutos (Sin Docker, Sin Kubernetes, Sin Dolor de Cabeza) # tutorial # español # aws # agentcore 12 reactions Comments 1 comment 9 min read ¿El futuro del modelado es la IA o la especialización? Gabriel Cerdio Gabriel Cerdio Gabriel Cerdio Follow Sep 30 '25 ¿El futuro del modelado es la IA o la especialización? # webdev # español # spanish # hunyuan Comments Add Comment 2 min read Analisis de bloques de codigo en programacion TesseractDev TesseractDev TesseractDev Follow Aug 18 '25 Analisis de bloques de codigo en programacion # spanish # español # programming Comments Add Comment 1 min read (Spanish Version) Building MCP Tools: A PDF Processing Server Gabriel Melendez Gabriel Melendez Gabriel Melendez Follow Sep 18 '25 (Spanish Version) Building MCP Tools: A PDF Processing Server # spanish # mcp # ai # español Comments Add Comment 7 min read 🚀 Aprende Go con 13 Retos: una travesía práctica para dominar el lenguaje Brandon Sanchez Brandon Sanchez Brandon Sanchez Follow Jul 25 '25 🚀 Aprende Go con 13 Retos: una travesía práctica para dominar el lenguaje # go # learning # programming # español Comments Add Comment 3 min read Docker componentes esenciales Coles C Coles C Coles C Follow May 20 '25 Docker componentes esenciales # español # docker # devops # container Comments Add Comment 2 min read GitOps, Automatiza tu despliegue usando Flux y Kubernetes 🚀 Coles C Coles C Coles C Follow May 19 '25 GitOps, Automatiza tu despliegue usando Flux y Kubernetes 🚀 # español # gitop # kubernetes # devops Comments Add Comment 2 min read ¡Buenas buenas! Hice un video sobre tips para hacer tu CV 🤓🤙 MissaEng MissaEng MissaEng Follow Apr 4 '25 ¡Buenas buenas! Hice un video sobre tips para hacer tu CV 🤓🤙 # spanish # espanol # español # cv Comments Add Comment 1 min read Estado actual de Goliat Dashboard: ¡Descubre sus funcionalidades! 15:58 Daniel J. Saldaña Daniel J. Saldaña Daniel J. Saldaña Follow Mar 7 '25 Estado actual de Goliat Dashboard: ¡Descubre sus funcionalidades! # astro # development # react # español 1 reaction Comments Add Comment 1 min read Bloqueando IABots en Nginx Horacio Degiorgi Horacio Degiorgi Horacio Degiorgi Follow Feb 26 '25 Bloqueando IABots en Nginx # nginx # español # linux # webperf 2 reactions Comments Add Comment 1 min read 1- Alpine.js ¿Cómo instalar? Félix Moreno Félix Moreno Félix Moreno Follow Jan 20 '25 1- Alpine.js ¿Cómo instalar? # alpine # spanish # español # webdev Comments Add Comment 1 min read Everything as Code: La evolución de la infraestructura Israel Oña Ordoñez 🚀 Israel Oña Ordoñez 🚀 Israel Oña Ordoñez 🚀 Follow Feb 6 '25 Everything as Code: La evolución de la infraestructura # terraform # ansible # opa # español 7 reactions Comments Add Comment 7 min read EKS con Terraform: Todo lo necesario, desde la red hasta los nodos Israel Oña Ordoñez 🚀 Israel Oña Ordoñez 🚀 Israel Oña Ordoñez 🚀 Follow Jan 28 '25 EKS con Terraform: Todo lo necesario, desde la red hasta los nodos # devops # eks # terraform # español 13 reactions Comments 2 comments 7 min read Crea imágenes Docker ligeras y seguras Israel Oña Ordoñez 🚀 Israel Oña Ordoñez 🚀 Israel Oña Ordoñez 🚀 Follow Jan 26 '25 Crea imágenes Docker ligeras y seguras # docker # optimizacion # devops # español 6 reactions Comments Add Comment 4 min read ¡Primeros pasos en GIT! GIT para PRINCIPIANTES MissaEng MissaEng MissaEng Follow Dec 17 '24 ¡Primeros pasos en GIT! GIT para PRINCIPIANTES # spanish # español # espanol # git Comments Add Comment 1 min read Helm vs Kustomize: ¿Cuál es mejor para gestionar manifiestos en Kubernetes? Israel Oña Ordoñez 🚀 Israel Oña Ordoñez 🚀 Israel Oña Ordoñez 🚀 Follow Jan 20 '25 Helm vs Kustomize: ¿Cuál es mejor para gestionar manifiestos en Kubernetes? # kubernetes # helm # kustomize # español 4 reactions Comments Add Comment 3 min read ¿Qué es GIT, por qué TODOS los developers lo usan?: Historia de GIT MissaEng MissaEng MissaEng Follow Dec 16 '24 ¿Qué es GIT, por qué TODOS los developers lo usan?: Historia de GIT # spanish # español # git # github Comments Add Comment 1 min read 5 errores comunes en Kubernetes y cómo solucionarlos rápidamente Israel Oña Ordoñez 🚀 Israel Oña Ordoñez 🚀 Israel Oña Ordoñez 🚀 Follow Jan 13 '25 5 errores comunes en Kubernetes y cómo solucionarlos rápidamente # kubernetes # troubleshooting # devops # español 5 reactions Comments Add Comment 4 min read Domina Bash con ejemplos prácticos de Git Israel Oña Ordoñez 🚀 Israel Oña Ordoñez 🚀 Israel Oña Ordoñez 🚀 Follow Jan 8 '25 Domina Bash con ejemplos prácticos de Git # bash # scripting # git # español 5 reactions Comments Add Comment 5 min read loading... trending guides/resources Agentes de IA: Dominando 3 Patrones Esenciales (ReAct). Parte 2 de 3 Surya OCR vs Tesseract en CPU con Python Agentes de IA: Dominando 3 Patrones Esenciales (Reflexive). Parte 3 de 3 [ES] ContextFX - Un CDI ligero para JavaFX/GluonFX con soporte de ReactFX Agentes de IA: Dominando 3 Patrones Esenciales (Tool Using). Parte 1 de 3 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/munin-1/day-7200-full-stack-1k6f | Day 7/200 (full stack) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Munin Borah Posted on May 18, 2025 Day 7/200 (full stack) # programming # ai # beginners # javascript Today's progress: HTML completed. NOW moving to CSS Total build 7 projects to practice HTML. Top comments (6) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Nevo David Nevo David Nevo David Follow Founder of Postiz, an open-source social media scheduling tool. Running Gitroom, the best place to learn how to grow open-source tools. Education Didn't finish high school :( Pronouns Nev/Nevo Work OSS Chief @ Gitroom Joined Feb 23, 2022 • May 18 '25 Dropdown menu Copy link Hide Pretty cool seeing you get through those first 7 projects - do you ever find some days just hit way harder than others? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Munin Borah Munin Borah Munin Borah Follow 🚀 On a 1825-day mission to become a top 0.1% programmer | 💡 Learning in public | Building cool things & sharing my journey Email muninb126@gmail.com Education 🎓 Self-Taught Developer | Always Learning Pronouns He/Him Work 💼 Full-Stack Developer (In Progress) | 1825-Day Dev Journey Joined Mar 30, 2025 • May 19 '25 Dropdown menu Copy link Hide Yes, some days I feel full of motivation, but some days I feel like walking through hell. But in my mind, I knew that I should keep going, keep taking single steps toward my big goals. Like comment: Like comment: Like Comment button Reply Collapse Expand Dotallio Dotallio Dotallio Follow Joined Apr 7, 2025 • May 18 '25 Dropdown menu Copy link Hide Finishing 7 projects in HTML is huge - you're about to have a lot of fun with CSS next! Can't wait to see your progress. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Munin Borah Munin Borah Munin Borah Follow 🚀 On a 1825-day mission to become a top 0.1% programmer | 💡 Learning in public | Building cool things & sharing my journey Email muninb126@gmail.com Education 🎓 Self-Taught Developer | Always Learning Pronouns He/Him Work 💼 Full-Stack Developer (In Progress) | 1825-Day Dev Journey Joined Mar 30, 2025 • May 19 '25 Dropdown menu Copy link Hide Thanks buddy. Like comment: Like comment: Like Comment button Reply Collapse Expand Aryan Aryan Aryan Follow 🧑💻 Frontend Developer in the making | Turning visions into clean, responsive UIs. 🛠 Currently mastering JavaScript and building real-world projects. 💡 I believe in learning out loud, building in Joined May 8, 2025 • May 18 '25 Dropdown menu Copy link Hide hey buddy its really great to see that u r doing great on your journey . I am on the same journey and would like to collab on some project . Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Munin Borah Munin Borah Munin Borah Follow 🚀 On a 1825-day mission to become a top 0.1% programmer | 💡 Learning in public | Building cool things & sharing my journey Email muninb126@gmail.com Education 🎓 Self-Taught Developer | Always Learning Pronouns He/Him Work 💼 Full-Stack Developer (In Progress) | 1825-Day Dev Journey Joined Mar 30, 2025 • May 18 '25 Dropdown menu Copy link Hide sure buddy❤️. let's grow together. Like comment: Like comment: Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Munin Borah Follow 🚀 On a 1825-day mission to become a top 0.1% programmer | 💡 Learning in public | Building cool things & sharing my journey Education 🎓 Self-Taught Developer | Always Learning Pronouns He/Him Work 💼 Full-Stack Developer (In Progress) | 1825-Day Dev Journey Joined Mar 30, 2025 More from Munin Borah Day 19/200 (Full stack) # webdev # programming # javascript # beginners Day 17&18/200 (Full stack) # webdev # programming # javascript # beginners Day 16/200 (Full stack) # webdev # programming # javascript # beginners 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://resources.github.com/devops/tools/compare/ | How does GitHub compare to other DevOps tools? - GitHub Resources / Resources GitHub vs. GitLab and other DevOps tools Start a free trial Contact Sales Why GitHub GitHub vs. GitLab GitHub vs. Bitbucket GitHub vs. Jenkins More than 90% of the Fortune 100 use GitHub Enterprise DevOps is just the beginning. From McKesson to Meta and Spotify to SAP , many of the world's biggest and most innovative companies are built on GitHub—the leading developer platform compared to alternative solutions. Why teams choose GitHub Build on the most loved developer platform Build what's next with the all-in-one solution that's beloved by developers. Go from ideation to planning, project management, security, automation and delivery with extensive native capabilities and a rich integration ecosystem. Learn more Scale faster with powerful CI/CD Build your DevOps practice with native CI/CD that responds to any webhook. Bring your preferred tools seamlessly into your workflow with a rich ecosystem of integrations in the GitHub Marketplace—or build your own integrations with GitHub Actions. Explore the GitHub Marketplace Stay secure at every step Empower developers to fix vulnerabilities in minutes with the only community-driven, native application security testing solution on a platform designed for dynamic teams and regulated industries. Learn more Home to the world's largest open source registry Accelerate your workflows and scale your business fast with access to millions of open source projects on GitHub, the largest source code host. Learn more What our customers are saying “ GitHub keeps us up to speed with the industry's best tools. We want new hires to know GitHub is in our toolchain—it makes them excited to join us. Head of Emerging Tech American Airlines “ It's like night and day. It's the collaboration, it's the sharing, it's the community. It's all because of GitHub. Director of Build Platform Autodesk “ One of the big benefits of using GitHub for CI/CD and security automation is that we don't have to build, deploy, or maintain additional tools. Software Engineer Mercari “ We're a developer-first organization and we live and breathe GitHub. It's not just a developer platform for us. Chief Security Officer Hashicorp How GitHub compares to other DevOps platforms There are dozens of alternative DevOps tools from best-in-breed point solutions to full platforms. So how does GitHub compare? There are plenty of analyst reports that answer that question--but here's an overview to help you get started. Download PDF GitHub vs. GitLab for DevOps Use case GitHub GitLab Desktop and Mobile Support, CLI GitHub Native desktop app for macOS and Windows. Native iOS and Android mobile applications to enable collaboration on any device. Native CLI to enable collaboration via your terminal. GitLab Third-party apps with limited capabilities. Planning, tracking, and project management GitHub Comparable native capabilities GitLab Comparable native capabilities Collaboration GitHub Comparable native capabilities GitLab Comparable native capabilities Application security GitHub Native core capabilities based on GitHub's own IP with GitHub Advanced Security Integrations to third-party commercial products and open source solutions via support for the SARIF format GitLab Core capabilities based on embedded open source projects and integrations with other open source solutions. Automation & CI/CD GitHub Comparable native core capabilities Over 17,000 GitHub Actions are available in the GitHub Marketplace to automate your development workflow. GitLab Comparable native capabilities Innovative coding capabilities GitHub Cloud-hosted developer environments with GitHub Codespaces AI programming assistance with GitHub Copilot Third-party integrations GitLab Third-party integrations Platform security GitHub Comparable native capabilities Complete control over identity provisioning, access and removal of permissions with Enterprise Managed Users in the cloud. Certifications: GDPR Compliant ISO 27001:2013 SOC 1 Type 2 SOC 2 Type 2 ISAE 2000 ISAE 3402 FedRAMP LI-Saas Authorization to Operate (ATO) Trusted Cloud Provider(™) with the Cloud Security Alliance (CSA) GitLab Comparable native capabilities Certifications: ISO 27001 SOC 2 Type 2 Report: Security and Confidentiality Criteria SOC 3 Report: Security and Confidentiality Criteria ISO/IEC 20243-1:2018 Self Assessment CSA-Star PCI DSS SAQ-A Self-Assessment Scalability GitHub Comparable native capabilities Hosts the world's largest code graph with over 100 million registered users on github.com, and more on self-managed deployments. 99.90% uptime guarantee with GitHub Online Services SLA. GitLab Comparable native capabilities Claims estimated 30 million users including estimated user counts from self-managed deployments. Uptime SLA is not available. * This is a biased overview of capabilities by use case, based on publicly available information as of 2022-05-16. GitHub vs. Bitbucket for Devops Use case GitHub Bitbucket Desktop and Mobile Support, CLI GitHub Native desktop app for macOS and Windows. Native iOS and Android mobile applications to enable collaboration on any device. Native CLI to enable collaboration via your terminal. Bitbucket Third-party apps with limited capabilities. Planning, tracking, and project management GitHub Comparable native capabilities Next generation planning and tracking capabilities with the new GitHub Issues experience . Bitbucket Very limited native core capabilities Requires Atlassian's Jira (a separate product) for planning and tracking capabilities. Collaboration GitHub Comparable native capabilities Bitbucket Comparable native capabilities Application security GitHub Native core capabilities based on GitHub's own IP with GitHub Advanced Security Integrations to third-party commercial products and open source solutions via support for the SARIF format Bitbucket Third-party integrations with commercial products and open source solutions. Automation & CI/CD GitHub Comparable native core capabilities Over 17,000 GitHub Actions are available in the GitHub Marketplace to automate your development workflow. Bitbucket Comparable native capabilities Only supports 86 integrations as of 2022-05-16. Innovative coding capabilities GitHub Cloud-hosted developer environments with GitHub Codespaces AI programming assistance with GitHub Copilot Third-party integrations Bitbucket Third-party integrations Platform security GitHub Comparable native capabilities Complete control over identity provisioning, access and removal of permissions with Enterprise Managed Users in the cloud. Certifications: GDPR Compliant ISO 27001:2013 SOC 1 Type 2 SOC 2 Type 2 ISAE 2000 ISAE 3402 FedRAMP LI-Saas Authorization to Operate (ATO) Trusted Cloud Provider(™) with the Cloud Security Alliance (CSA) Bitbucket Comparable native capabilities Certifications: GDPR Compliant ISO 27001:2013 SOC 2 SOC 3 PCI DSS Compliant Scalability GitHub Comparable native capabilities Hosts the world's largest code graph with over 100 million registered users on github.com, and more on self-managed deployments. 99.90% uptime guarantee with GitHub Online Services SLA. Bitbucket No public information on total number of registered users. The last reported number was 10 million registered users in 2019. Uptime SLA is not available . ** This is a biased overview of capabilities by use case, based on publicly available information as of 2022-05-16. GitHub vs. Jenkins for CI/CD Use case GitHub Jenkins Automation & CI/CD GitHub Comparable native core capabilities Over 17,000 GitHub Actions are available in the GitHub Marketplace to automate your development workflow. Jenkins Comparable native capabilities 1,800+ community contributed Jenkins plugins in Jenkins Plugin Marketplace. Deployment models GitHub Cloud or self-hosted Jenkins Self-hosted only CloudBees is the cloud alternative *** This is a biased overview of capabilities by use case, based on publicly available information as of 2022-05-16. Frequently asked questions What are some quick facts about GitHub Enterprise Cloud? GitHub Enterprise Cloud offers a cloud-hosted enterprise product plan (SaaS) for large businesses and teams who need a complete DevSecOps solution. It provides tools for greater management of an organization's resources using sophisticated security and administrative features, for example through authentication with SAML single sign-on. GitHub Enterprise Cloud includes support for 50,000 minutes of GitHub Actions runtime for CI/CD workflows and 50GB of storage for shared components and containers. You can learn more about GitHub Enterprise Cloud in our documentation or product page . How rich is GitHub’s documentation and where can I find it? GitHub offers thorough documentation around all of its products with detailed how-to guides that walk teams, developers, and administrators through maximizing their investment with GitHub Enterprise. You can find GitHub’s documentation at docs.github.com , which offers a centralized place to find the latest information about GitHub’s products, how to use them, and how to get help. This documentation is kept up-to-date by our documentation teams partnering closely with engineering, our product teams, and our outside community via community contributions. How do I migrate to GitHub Enterprise Cloud? If you’re making the move to GitHub, we know you’ll have data you want to bring with you so your team can hit the ground running quickly. We know that fear of migration can be a big barrier to switching to GitHub, which is why we’re working hard to make moving quick, low cost and painless. GitHub Enterprise Importer is our tried and tested migration tool, used by thousands of GitHub customers to migrate more than 690,000 repositories to GitHub Enterprise Cloud. You can migrate on your own terms with free, self-service migrations from GitHub Enterprise Server, Bitbucket Server, Bitbucket Data Center and Azure DevOps. If you’re moving from another tool or you’re looking to adopt GitHub Enterprise Server, there are options for you. For more details, and to learn about our tools for planning your migration and moving large numbers of repositories, check out: https://resources.github.com/migrations/ How can I migrate teams from personal GitHub accounts to my organization account? GitHub offers a simple way to turn personal accounts into organization accounts and migrate teams from personal accounts into organization accounts, too. You can find a full guide on how to do this in our documentation . Does GitHub offer project planning and source code management in one place? GitHub offers a complete cloud-hosted developer platform, which includes project planning, source code management, CI/CD, automation, application security and more. All of these features and capabilities are centralized within the core platform making it simple to plan projects, assign tasks, track work, and deploy code from one interface. GitHub’s project planning solution also integrates with task management and forum boards to track decision making trees, conversations, and project statuses. Learn more about project planning with GitHub Issues and how it ties into the everyday developer platform to increase the speed at which you can build, deploy, and scale solutions. Does GitHub offer pre-built automation and CI/CD workflow templates? GitHub offers a number of pre-built and community-developed automation workflow templates that enable organizations to build powerful CI/CD pipelines, enforce environmental policies, and more. These workflow templates are designed to meet the needs of leading teams and companies and feature a sizable integration ecosystem. You can find more than 12,000 pre-built automation workflows in the GitHub Marketplace , which contains community-driven and tested automations for security, CI/CD, development workflows, platform integrations, and more. You can also learn more about how automation and CI/CD work on GitHub in our documentation . Can I use GitHub tools to manage, build, and deploy software to Amazon Web Services (AWS), Microsoft Azure, Google Cloud, a cloud provider of my choice, or my on-site servers? GitHub offers integrations with AWS, Microsoft Azure, Google Cloud, and other leading cloud providers through the GitHub Marketplace that make it simple to manage, build, and deploy cloud-native applications. GitHub also provides a number of pre-built and customizable CI/CD and automated workflows to manage, provision, and orchestrate cloud computing resources with GitHub Actions. What is the difference between GitHub and GitLab? Trying to choose between GitHub vs. GitLab for DevOps? The short answer: It depends on your current business needs and your growth plans. GitHub and GitLab are both mature, cloud-based SaaS platforms that offer native capabilities and integrations with third-party tools. While GitLab has their roots and the majority of their business in on-premises environments, they also have a relatively small cloud offering. GitHub is the home of open source and has been a cloud-native solution since their inception. GitHub also offers on-premises environments. Before making a decision on GitHub vs. GitLab, you’ll likely want to conduct your own research and test each solution. What is the difference between GitHub and Bitbucket? Making a decision between GitHub vs. Bitbucket to scale your DevOps practice? The answer depends on what you’re looking to accomplish and your organizational goals. GitHub and Atlassian Bitbucket are both mature platforms with native capabilities and third-party integrations. GitHub offers both a cloud-hosted SaaS model and a self-managed deployment model. In contrast, Bitbucket only offers a self-hosted solution for 500 seats or more with recurring license and support fees and otherwise promotes their cloud-hosted SaaS solution after making an end-of-life announcement for their on-premise Server product ). What is the difference between GitHub and Jenkins for CI/CD? Trying to decide whether to use GitHub Actions vs. Jenkins? If you’re looking for a cloud-hosted CI/CD solution, GitHub Actions bring extensive and platform-native capabilities to the GitHub platform. Plus, it’s included in GitHub Enterprise. You can also look at CloudBees, which is the commercial variant of Jenkins and fully integrates into the GitHub experience. But where GitHub offers a complete DevOps and DevSecOps platform, Jenkins and its CloudBees commercial solution focus only on automation and CI/CD capabilities. What is the difference between Git and GitHub? Trying to understand the difference between Git vs. GitHub? It helps to understand what each solution is. Let’s start with Git: Originally developed in 2005 by Linux inventor Linus Torvalds, Git is a locally installed version control system used to track file changes in development workflows. Its primary purpose is to help developers coordinate work and track changes to source code over time. You can learn more about Git on Git-guides . In contrast, GitHub offers an end-to-end DevOps platform with cloud-hosted Git services—i.e., source code management (SCM) and versioning control. GitHub also includes project management, CI/CD, automation, enterprise-grade security scanning, and more to serve all software development needs. Migrations made easy Moving to GitHub Enterprise Cloud is simpler than you think with self-serve migrations from leading developer tools. Plan your migration | 2026-01-13T08:49:34 |
https://dev.to/_402ccbd6e5cb02871506/super-fast-markdown-linting-for-go-developers-meet-gomarklint-3ikd#wrap-up | Super Fast Markdown Linting for Go Developers: Meet gomarklint - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Kazu Posted on Jan 13 Super Fast Markdown Linting for Go Developers: Meet gomarklint # go # performance # showdev # markdown The "Why" (The Motivation) Documentation is the heart of any project, but keeping it consistent is a nightmare. While working on various Go projects, I realized a few things about my workflow: Context Switching Costs: I love Go's speed and simplicity. Having to install Node.js or Ruby just to run a Markdown linter in a Go project felt "heavy." CI Fatigue: In large repositories, documentation checks shouldn't take seconds—they should take milliseconds. Every second saved in CI is a win for developer experience. The "Broken Link" Problem: There’s nothing more embarrassing than shipping a README with dead links. I needed a tool that catches these issues instantly. I couldn't find a tool that was Go-native, ultra-fast, and zero-config by default, so I decided to build one. The goal for gomarklint was simple: Make Markdown linting so fast and easy that you never have an excuse to skip it. Speed Performance When I say "fast," I mean Go-fast. In many CI/CD pipelines, linting documentation is often the bottleneck that adds unnecessary seconds (or even minutes) to every PR. gomarklint changes that. By leveraging Go's concurrency and efficient string handling, it delivers near-instant feedback. The Benchmark: I tested gomarklint against a large documentation set: Total Files: 180 Markdown files Total Volume: 100,000+ lines of text Execution Time: < 50ms To put that in perspective, 50ms is literally faster than the blink of a human eye. You can run this on every single file save without ever noticing a stutter in your workflow. By removing the overhead of a virtual machine or a heavy runtime, gomarklint ensures that your documentation quality stays high without sacrificing your velocity. Key Features gomarklint doesn't just check syntax; it enforces a logical structure for your documentation. Here are the core rules it handles out of the box: Heading Hierarchy Enforcement : Ever seen a document jump from an H2 directly to an H4? It breaks the visual flow and accessibility. gomarklint ensures your heading levels follow a strict, logical sequence. Duplicate Heading Detection : Identical headings in the same file can break anchor links (e.g., #features vs #features-1). We catch these early so your internal navigation never breaks. Broken Link Checker (Internal & External) : This is my favorite. It scans your Markdown for links and validates them. No more 404s for your users when they click on a "Getting Started" guide or an external API reference. Configuration via JSON : While it works great with zero config, you can easily tweak rules or ignore specific paths using a simple .gomarklint.json file. Quick Start # install (choose one) go install github.com/shinagawa-web/gomarklint@latest # or clone and build manually git clone https://github.com/shinagawa-web/gomarklint cd gomarklint make build # or: go build ./cmd/gomarklint Enter fullscreen mode Exit fullscreen mode 1) Initialize config (optional but recommended) gomarklint init Enter fullscreen mode Exit fullscreen mode This creates .gomarklint.json with sensible defaults: { "include": ["."], "ignore": ["node_modules", "vendor"], "minHeadingLevel": 2, "enableHeadingLevelCheck": true, "enableDuplicateHeadingCheck": true, "enableLinkCheck": false, "skipLinkPatterns": [], "outputFormat": "text" } Enter fullscreen mode Exit fullscreen mode You can edit it anytime — CLI flags override config values. 2) Run it # lint current directory recursively gomarklint ./... # lint specific targets gomarklint docs README.md internal/handbook Enter fullscreen mode Exit fullscreen mode What's Next? (Roadmap) gomarklint is already stable and fast, but I have a clear vision for where it’s headed. I’m actively working on expanding its rule set to cover even more edge cases and best practices. Here’s what you can expect in the coming updates: max-line-length Enforcement : To keep your Markdown source files readable in any editor or GitHub's UI. Image Alt-Text Validation : Improving accessibility by ensuring every image has a descriptive alt attribute. Custom Rules via JSON : Giving you the power to define your own project-specific rules in .gomarklint.json. Auto-fixing (The Dream) : While currently focused on linting, I’m exploring ways to automatically fix simple issues like heading level skips. We are Open for Contributions! If you have a rule in mind that would make your documentation better, or if you find a bug, please open an Issue or a Pull Request on GitHub. I’d love to build the future of this tool together with the community. Wrap Up Building gomarklint has been an incredible journey into the world of Go performance and static analysis. It started as a small tool for my own workflow, but I realized that many other developers are likely facing the same "slow linting" frustration. If you're looking for a way to keep your documentation spotless without adding bloat to your CI/CD, I’d be honored if you gave gomarklint a try. Check it out on GitHub : shinagawa-web/gomarklint Give it a ⭐: If you find the project useful, a Star would mean the world to me and helps others discover the tool! I’m really curious to hear from you: What’s the most annoying thing you’ve encountered with Markdown formatting? Let’s chat in the comments below! Happy hacking! 🚀 Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Kazu Follow Joined Aug 9, 2025 More from Kazu Building a Culture of Documentation Quality in CI/CD # markdown # cicd # documentation # opensource Inside gomarklint: Architecture, Rule Engine, and How to Extend It # programming # go # markdown Inside gomarklint: Building a High-Performance Markdown Linter in Go # go # markdown # opensource 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://meshedinsights.com/ | Meshed Insights Ltd | Navigating Rights and Responsibilities in the Meshed Society Site Index About Us Business Information Meshed Logo Store Rented Accommodation Thank You! Services Subscribe! We support entrepreneurs in emerging economies through the Kiva micro-finance initiative, and we encourage you to do so too . Meta Create account Log in Entries feed Comments feed WordPress.com © 2013-25, Meshed Insights Ltd. All rights reserved, all wrongs righted. Unless otherwise credited all photographs, videos and other media are included in this statement. Some photographs are available for licensing via iStockPhoto . Privacy Notice & Cookie Policy . + Meshed Insights Ltd Navigating Rights and Responsibilities in the Meshed Society Facebook Twitter Menu Skip to content About Meshed Insights Subscribe! Posted on November 27, 2025 by Simon Phipps Tagged open source The CRA’s Impetus To Openness The definition of “open source” in recital 18 of the Cyber Resilience Act (CRA) goes beyond the Open Source Definition (OSD) managed by OSI. It says: “Free and open-source software is understood as software the source code of which is openly shared and the licensing of which provides for all rights to make it freely accessible, usable, modifiable and redistributable.” As I and others confirmed when it was introduced, the addition of “openly shared” was a considered and intentional addition by the co-legislators – they even checked with community members that it did not cause unintended effects before adding it. While open source communities all “openly share” the source code of their projects, the same is not true of some companies, especially those with “open core” business models. For historical reasons, it is not a requirement either of the OSD or of the FSF’s Free Software Definition (FSD) and the most popular open source licenses do not require it. Notably, the GPL does not insist that source code be made public – only that those receiving the binaries must be able to request the full source code corresponding to the software they received and enjoy it however they wish (including making it public). For most open source projects and their uses, the CRA’s extra requirement will make no difference. But it complicates matters for companies that either restrict source availability to paying customers or make little distinction between available and non-available source or withhold source to certain premium elements. It means that there is no pathway by which the alternative compliance pathways for Open Source Software Stewards can be accessed, for example. A similar construct is used in the AI Act (recital 102) and I anticipate this trend will continue through other future legislation. Personally I welcome this additional impetus to openness. (Updated from a post at opensource.org ) Share this: Click to share on LinkedIn (Opens in new window) LinkedIn Click to share on X (Opens in new window) X Click to share on Facebook (Opens in new window) Facebook More Click to email a link to a friend (Opens in new window) Email Click to share on Pinterest (Opens in new window) Pinterest Click to share on Tumblr (Opens in new window) Tumblr Click to share on Reddit (Opens in new window) Reddit Click to share on Pocket (Opens in new window) Pocket Like Loading... Posted on January 31, 2024 by Simon Phipps Tagged Causality FLOSS FOSS FreeSoftware open source open-source-software software SoftwareFreedom technology Comments 1 Comment on Stochastic Confidence and the Open Source Network Effect Stochastic Confidence and the Open Source Network Effect What has powered open source to become part of almost all software and drive nearly €100 bn of GDP in Europe? Reuse, yes. But that was always possible. Collaboration, definitely. But repositories existed for years before open source was coined in 1998. The software freedom philosophy. Absolutely, but that went 15 years without triggering a software revolution. I suggest it’s something less measurable and observable — developer confidence — and that the effects involved are stochastic, not deterministic. Continue reading → Share this: Click to share on LinkedIn (Opens in new window) LinkedIn Click to share on X (Opens in new window) X Click to share on Facebook (Opens in new window) Facebook More Click to email a link to a friend (Opens in new window) Email Click to share on Pinterest (Opens in new window) Pinterest Click to share on Tumblr (Opens in new window) Tumblr Click to share on Reddit (Opens in new window) Reddit Click to share on Pocket (Opens in new window) Pocket Like Loading... Posted on December 9, 2022 by Simon Phipps Tagged Activitypub Fediverse Mastodon Standards The Future Promise Of The Fediverse There’s an old story about someone in the dark feeling the trunk of an elephant and believing it’s a snake because they can’t see the whole animal. It’s happening again, as people spooked from the Twitter crash try to feel their way around the Fediverse. One of the benefits of the Fediverse is that I can use my preferred system to post things and you can follow and interact with any ActivityPub-compatible system you prefer. Your choice of, say, a photo-sharing platform doesn’t dictate that I have to sign up to the same site, or even to another photo sharing thing. It’s all powered by the ActivityPub standard – which is like RSS you can reply to . But there’s the potential to end the reign of monetized surveillance (AKA advertising) with a switch to user-owned applications. No platform virality If I were posting my photos to Instagram, to follow them you would have to sign up too (and since that’s Facebook-owned, submit to all their monetized identity harvesting). But if I post with PixelFed – an ActivityPub system tailored to posting photographs like on Instagram – you can follow from a compatible photo tool for sure. But you can also follow – and comment – from micro-blogging systems like Mastodon or Pleroma or from video-sharing systems like PeerTube or a blogging tool like Plume. Yes, you have to join the Fediverse somewhere, but you can do it the way that’s comfortable on a platform that shares your values and still interact with people who made different choices, and once you’ve done it you can follow any feed regardless of the platform it’s from. It’s the end of platform virality and lock-in. It means every small app can benefit from a network effect previously only available to gatekeeper platforms. This is the most important dimension of the Fediverse, and the one we need to develop. We need ActivityPub federated software tools of all kinds, cutting the link between my choices and your choices without also cutting our ability to interact with each other. I never want to have to leave my social graph behind again. Composable applications This detachment goes further. I can segment my posting and use a more appropriate tool for specific content types and interaction styles. For example, I have been putting my travel photos on my new PixelFed server so that followers have the choice of following my micro-blogging feed on Mastodon , my photo feed on PixelFed or indeed both. This means I don’t have to wait for my microblogging tool to get better support for posting photos; instead I can mix and match tools and build the ideal creative environment for me, and you’re not affected beyond needing to follow me in more than one place. Over time this will get fixed and I’ll be able to offer an aggregated subscription to all my feeds – it just needs someone to write a gadget to do it! Of course, there’s much more to it than this. Since ActivityPub has two layers, a client-to-server layer and a server-to-server layer , there is great scope for wiring composable applications together so they collaborate better. And then there’s the privacy dimension – I especially like Christine Lemmer-Webber’s OCapPub ideas . I‘m sure we will see much innovation both in creating user capabilities and in managing infrastructure needs. Because pretty much everything in the Fediverse is open in every sense, there is plenty of scope for relays and clients to layer fresh capabilities upon the activity stream. It’s the UNIX philosophy revisited. Open Source and standards done right This is all powered by the dual merits of Open Source software and truly open standards . ActivityPub is a freely-available, royalty-free W3C standard . All the systems that manipulate it to date are Open Source software, which anyone can enjoy without asking permission first. Together that openness has fueled the wave of change triggered by the collapse of Twitter. But there is much more to it than that. I’ll not tell you that calling the Fediverse “Mastodon” is a mistake (even if it is!) but I do recommend looking beyond the obvious similarities of Mastodon to Twitter and realize the phenomenon it is riding is not only bigger than a single piece of software, it’s bigger than a single category of software. Federation will get smarter, more secure and new categories of activity will be added. This is not so much an elephant in the dark as a whole zoo in the dark, and we’ve only touched the first few animals. Based on an original Mastodon thread First published on OSI’s Voices Of Open Source Share this: Click to share on LinkedIn (Opens in new window) LinkedIn Click to share on X (Opens in new window) X Click to share on Facebook (Opens in new window) Facebook More Click to email a link to a friend (Opens in new window) Email Click to share on Pinterest (Opens in new window) Pinterest Click to share on Tumblr (Opens in new window) Tumblr Click to share on Reddit (Opens in new window) Reddit Click to share on Pocket (Opens in new window) Pocket Like Loading... Posted on September 15, 2022 by Simon Phipps Tagged Licensing open source Rights Ratchet Akka Ratchets The Rights Away There’s been a regrettable rise in the number of projects switching to “fauxpensource” proprietary licenses. In the main, this is the inevitable consequence of the rights-ratchet model running its course and reflects the growth of open source ten years or so ago, the model’s typical life-cycle. The rights ratchet model offers open source freedoms in the initial years of a product to secure adoption and market acceptance and then gradually removes their viability from customers as the company seeks to control their ecosystem and increase revenue. So the license change that LightBend applied to its Akka product to end its open source status was in retrospect more probable than not given the available evidence that they were using a rights-ratchet business model, just like Elastic and other before them. Signs that together seem a clear warning include: VC backing includes VCs who have previously advised portfolio companies to ignore the community rather than leaving money on the table. Used a Contributor Agreement despite also using a license entirely suitable for use without one . Change of CEO recently saw the departure of a respected open source leader who had been at the helm during the community-building years. The web site does not mention open source as a customer benefit. The typical 10-year cycle of the rights-ratchet model from open source to proprietary was nearly up. Those familiar with the rights-ratchet model will undoubtedly have been preparing for the switch. Anyone else may be surprised by it – this time. Share this: Click to share on LinkedIn (Opens in new window) LinkedIn Click to share on X (Opens in new window) X Click to share on Facebook (Opens in new window) Facebook More Click to email a link to a friend (Opens in new window) Email Click to share on Pinterest (Opens in new window) Pinterest Click to share on Tumblr (Opens in new window) Tumblr Click to share on Reddit (Opens in new window) Reddit Click to share on Pocket (Opens in new window) Pocket Like Loading... Posted on August 4, 2022 by Simon Phipps Tagged bug bounty open source Sustainability Are bug bounty programs good for Open Source? Seems obvious doesn’t it? They have to be a good thing surely? They are paying people to work on Open Source software – isn’t that increasing the sustainability of open source? Stag beetle emerging from elder blossom Except the money isn’t going to open-source development; it’s going to a cottage industry of hacking that will likely sell the defects to the highest bidder. Even if the highest bidder is part of a white-hat bug bounty program the community that owns the code may well not have members who can fix the problem readily. Even if the community has got commercial contributors they may not have the income necessary to fix all these bugs found by people who are not buying their product. Even assuming they want to ( screenshot ): this is a mere bugbounty effort. no harm done. report will be released. https://t.co/k3Z3yWWaW0 — pl0x_plox_chiken_p0x (@Pl0xP) August 3, 2022 Bugs and Knowing It’s good to have bug reports and know about defects, but there can be down sides. If the defects are exploitable vulnerabilities – CVEs – the reports are kept on a private security list until fixed to avoid informing black-hats. But in projects that can’t fix the defects fast enough they may well end up being disclosed before there is a resolution. They also show up on CVE databases and become a cause for support calls and demands for resolution from volunteer community members, increasingly so as automatic scanning tools spread. Some of the bugs are rejected by the developers who own the software because in some cases being a bug or a feature is truthfully a matter of opinion, resulting in “will not fix” false positives. A case can be made for bug bounty programs run for a company seeking low-cost penetration testing to be handled by their professional development team for a commercial product. It can also be made for an administration seeking community testing of public systems, like the Swiss government . But community-focussed programs like the European Commission’s Open Source bug bounty are well-meaning but surely miss their mark, creating work for communities and their commercial backers without generating donations or revenues to pay for bug resolution. Who Can We Fund? Specifically to that example, there’s nothing in the EU program that actually leads to any maintainers being paid, which is because that’s “software procurement” and has stringent rules. There’s a 20% uplift for bug reports who propose fixes for their bugs, but the on-ramp for maintainers of the targeted code is usually substantial and a 20% premium is unlikely to be enough to incent someone to come on board as a maintainer. The EU has built outbound funding programs for Open Source at NL Net and NGI, but they are all earmarked for “the next big thing”, not for the boring job of keeping Open Source maintained. Edgy new features have indeed been paid for by them, but they have no regard for funding bug-bounty burdens. One fix would be to associate an earmarked grant with a matched bug bounty award so the maintainer could go claim it, giving a concrete incentive to invest the time. Ideally, the grant to the reporter would be at least partly tied to the bug getting fixed as well. But even if the community has members able and willing to take on bounties, haggling with one or multiple unknown parties over acceptance of a solution after the investment has been made is huge risk for small rewards for implementors. Conclusion In the sense they reflect a growing realisation by software consumers that strip-mining Open Source is not sustainable, bug bounties are definitely welcome. But they are not the solution to creating sustainability. Open Source in the supply chain is not mainly or even largely about security. Rather, it has the same profile as Open Source elsewhere – a collaborative matter where beneficiaries share the sunk costs in proportion to the benefits gained. Bug bounties prioritise the non-contributor’s worldview – the quality of the strip-mined commodity – and neglect the true community view – pooled innovation and shared costs. They are a good first step, but need to be rapidly followed by enlightened self-interest expressed by funding and enabling of the maintainers rather than just rewarding their users. Share this: Click to share on LinkedIn (Opens in new window) LinkedIn Click to share on X (Opens in new window) X Click to share on Facebook (Opens in new window) Facebook More Click to email a link to a friend (Opens in new window) Email Click to share on Pinterest (Opens in new window) Pinterest Click to share on Tumblr (Opens in new window) Tumblr Click to share on Reddit (Opens in new window) Reddit Click to share on Pocket (Opens in new window) Pocket Like Loading... Posted on July 26, 2022 by Simon Phipps Tagged Patents Standards The Future Of Innovation Has Patent-Free Standards It may come as a surprise to find that some supposedly “open“ standards – including those ratified by standards development organisations (SDOs) like ISO, CEN and ETSI – can’t be implemented without going cap-in-hand to the world’s largest companies to buy a licence. As I explained for OSI , it’s the result of a legacy approach to innovation from the days when it was only really about hardware. As with any legal loophole, simply existing meant it was exploited and became the norm, even if it was initially temporary (“ like income tax ”). Once exploitation of a legal loophole becomes competitive, it becomes its own justification for the existence of the regulations (“look at the economic value of this segment”) and they become near impossible to remove – even when the original justification has ceased to need preferential protection. So today we see a swathe of rich consumer electronics and telecoms companies, addicted to the revenue they get from licensing the patents (SEPs) they have embedded in “open” standards * , lobbying hard to ensure their value to the economy is recognised. They have much to lose from the loss of their special status, so invest much to protect it and to glorify it. On the other hand, software companies have less to gain by the reformation of this anachronism – to the extent they have flirted with SEPs, maybe even a little to lose. Meanwhile, the new world of Open Source powered innovation lacks rich lobbyists due to its diffusion, and is accustomed to working round the obscenity of valuable standards being taxed by patent cartels. While the freedoms of Open Source mitigate to a degree, this means interoperability and interchangeability are being sacrificed on the altar of SEP protection. It is not an ideological outlook that makes thoughtful Open Source advocates oppose patents in standards. It’s primarily pragmatic. Requiring a patent license to implement a standard implies that those implementing it must engage in private negotiation to get a license to proceed. That’s super-toxic to Open Source, whose mainspring is code owners giving advance, un-negotiated, equal permission to enjoy the software in any way – use, improve, share, monetise – all protected by a rights license reviewed and approved by OSI. So most projects avoid or work around SEP-encumbered standards and the ones that don’t are industry-specific. OSI thus takes the position that standards destined to be implemented as Open Source must come with all the rights waived (and has done so for 15+ years ). For some, that is already true; for others it is being actively resisted. If you want the crop of innovation you have to get the growing conditions right , and this new crop has different needs to the old hardware world and its long horizons. The future of innovation is open innovation, implemented as Open Source. Using anachronistic patent-centric metrics and regulations will chill that future. How about we don’t do that? * Reusable Footnote : The word “open” is overloaded here. (An edited version of this article appeared in the OpenUK survey report 2022) Share this: Click to share on LinkedIn (Opens in new window) LinkedIn Click to share on X (Opens in new window) X Click to share on Facebook (Opens in new window) Facebook More Click to email a link to a friend (Opens in new window) Email Click to share on Pinterest (Opens in new window) Pinterest Click to share on Tumblr (Opens in new window) Tumblr Click to share on Reddit (Opens in new window) Reddit Click to share on Pocket (Opens in new window) Pocket Like Loading... Posted on July 22, 2022 by Simon Phipps Tagged Licensing open source Patents Standards Briefly: FRAND Is Toxic To Collaboration I’ve repeatedly heard lawyers arguing about whether Open Source licenses and FRAND terms are compatible. But ultimately it doesn’t matter, because the toxin remains whatever the answer – legal compatibility is the wrong lens . When developers come to an Open Source project, they need to find a level playing field, a uniform surface with no traps, a fully illuminated environment with no shadows. Without them, collaboration is compromised. But the presence of a standard with embedded patents (standard-essential patents or SEPs) under so-called “Fair Reasonable and Non-Discriminatory” (FRAND) terms introduces inequality. Some developers believe they are unaffected, because their usage is purely personal or they are poorly advised. Others are unconcerned because their employer is part of a cross-licensing cartel with the patent holder. But the remainder must each go privately and under NDA to the patent holder(s) and negotiate individual terms to use the patents. They then can’t publicly share the exact arrangements — or possibly even the existence of the arrangement — because of the NDA. Individual terms and secret rights are the opposite of open collaboration and destroy trust. It’s this inequality that is toxic, not the precise compliance with the legal terms in the Open Source license. Whether great legal minds find the presence of SEPs compatible or incompatible with the license, t he inequality of the participants in the community is what makes it avoid SEP-laden standards. That’s why the Open Standards Requirement for Software says any SEPs have to be waived or freely licensed in advance – to restore the level playing field. It’s not because of ideology or an anti-patent agenda or an attempt at market manipulation. The open source network effect underlying the market depends on it. So learned dissertations about the compatibility of FRAND terms with Open Source licenses may be academically interesting, but they aren’t relevant. All SEPs in standards intended to be implemented as Open Source must be waived or freely pre-licensed, or the standard won’t be implemented by open communities Share this: Click to share on LinkedIn (Opens in new window) LinkedIn Click to share on X (Opens in new window) X Click to share on Facebook (Opens in new window) Facebook More Click to email a link to a friend (Opens in new window) Email Click to share on Pinterest (Opens in new window) Pinterest Click to share on Tumblr (Opens in new window) Tumblr Click to share on Reddit (Opens in new window) Reddit Click to share on Pocket (Opens in new window) Pocket Like Loading... Posted on July 6, 2022 by Simon Phipps Tagged open source Terminology Briefly: On Overloading “Open” The word “open” is overloaded. In the domain of standardisers, a process that permits any company to participate (even if doing so is punitively expensive) is considered “open” and the resulting deliverable is considered an “open standard” even if you have to pay to read it and negotiate patent licenses to implement it. In the domain of software and APIs, it is the deliverable that has to be open – usable for any purpose without negotiation with its rights-holders. This overloading of the term is the origin of many of today’s issues, since – properly understood – Open Source and open standards are conceptually orthogonal . This variation in how “open” is understood within linked and overlapping domains is why “Open Source” is treated as a term of art with a consensually-agreed meaning in the domain of technology – a noun – and not as a descriptive adverbial phrase. If you see a hyphen in the middle of open-source it’s about military/political intelligence and not technology. Share this: Click to share on LinkedIn (Opens in new window) LinkedIn Click to share on X (Opens in new window) X Click to share on Facebook (Opens in new window) Facebook More Click to email a link to a friend (Opens in new window) Email Click to share on Pinterest (Opens in new window) Pinterest Click to share on Tumblr (Opens in new window) Tumblr Click to share on Reddit (Opens in new window) Reddit Click to share on Pocket (Opens in new window) Pocket Like Loading... Posted on July 4, 2022 by Simon Phipps Tagged Community Copyright Github Licensing AI Code Is Like Public Domain Code GitHub’s CoPilot tool may well be revolutionary, according to Bradley Kuhn . An AI trained by reading a massive and unidentified corpus of code, assumed to mostly be open source and licensed for any use to Github under their terms of use, it is able to watch what you are coding in your IDE and make suggestions on how to autocomplete the code – potentially at length. It is a kind of Clippy for code. It has just had the ultimate validation; Amazon copied it . No room for a co-pilot Sure, quit Github While that may seem an unalloyed good to many programmers, there is an outbreak of moral panic surrounding it, as evidenced by the recent call to boycott GitHub because of it. Now, I am all in favour of people using distributed tools instead of centralised ones. Git itself is intended as a distributed tool and in a way it’s offensive for GitHub to have annexed its name to create a centralised and proprietary control point. I am also keen for everyone as far as they can to exercise self-sufficiency over their computing and control of their personal data, and given Git was written as a response to the final abridgement of that self-sovereignty by the author of an earlier tool that the Linux developers were dependent on, Github is again somewhat offensive. Those would both be fine reasons to encourage people to move on from Github and to escape the social honeypot of carefully crafted network effect funnels that it embodies. … but not because of Copilot But Copilot is not a great reason to quit, or at least not for the reasons people insist on articulating. Those reasons seem strong on copyleft maximalism and the homeopathic thinking that assumes because there was GPL vapour in the air everything written at the time is infused. They also seem laced with a residual mistrust of Microsoft. Copilot is unlikely to be infringing copyright. Certainly not in the USA. Probably not in most other places (although see Brown for more nuance). Even for humans, learning patterns doesn’t infringe copyrights, and quoting minimal or essential fragments rarely rises to the level needed for protection by copyright. Copyrights are not the same as patents, and re-expressing the same idea does not amount to infringement – even if such infringement were possible for a machine. Which it is not, so all these considerations are moot in many jurisdictions. Copilot is unlikely to be breaching the GPL. That could only happen if copyright was being infringed. Just because the author of a work doesn’t like use of their code by Microsoft’s tool, that doesn’t somehow create an infringement that triggers the license. Copilot in not morally bankrupt for using open source code for training. The whole point of Open Source Free Software is to give anyone the unconditional right to study the code and learn from it. If that’s a via an automated tool that makes the matter more efficient, it makes no difference. Making a new thing that does the same as my patented widget is always an infringement of my patent, but making a new thing that does the same as my copyrighted code is not. An unfortunate consequence of the propaganda term “Intellectual Property” is that non-specialists munge all the concepts for all of {Copyright, Patents, Trade Secrets, Trademarks, Database rights} into one big hairball and assume anything matching the hairball triggers some form of infringement of any/all of the concepts. So arguments that mix-and-match IP concepts to imply an infringement are … problematic. You shouldn’t use it for Open Source though AI code helpers like Copilot are thus very unlikely to infringe rights per se . But that doesn’t mean code made by them should be welcome in Open Source projects. To summarise a long article, Reda concludes that the output of an AI like Copilot is best understood as Public Domain. But ironically, that’s the real problem with Copilot for an Open Source developer. Public Domain is not Open Source , and AI-generated code introduces friction that works against the Open Source network effect for just the same reasons. As Brown explains, not every jurisdiction has the same degree of certainty or the same attributes to its conclusion about AI-generated works as seems commonly understood in the USA. So while you may feel comfortable using AI-generated blocks in your code, what will you write in the pull-request to give others the same confidence? Even Github (and indeed Amazon ) are at pains to point out that’s your responsibility, not theirs. Their tool may be a very helpful learning aid, but it’s something of a trap for the responsible Open Source contributor. There’s a different case to be understood in every jurisdiction both about the code origin and the threshold for copyrightability. While the (many) lawyers I have heard from have largely waved a hand and said the arguments would never stand up in court, the arguable cases create a context where a community can’t rely on AI-generated code without further advice. Just like Public Domain, that added friction makes it non-viable for any community serious about provenance. The biggest challenges are the ones exerting subtle, systemic steering effects that people don’t take seriously. Github may not be a digital scofflaw, but their tool is a Siren tempting you onto rocks that can ruin communities. (Thanks to the Patreon backers who made this post possible) Share this: Click to share on LinkedIn (Opens in new window) LinkedIn Click to share on X (Opens in new window) X Click to share on Facebook (Opens in new window) Facebook More Click to email a link to a friend (Opens in new window) Email Click to share on Pinterest (Opens in new window) Pinterest Click to share on Tumblr (Opens in new window) Tumblr Click to share on Reddit (Opens in new window) Reddit Click to share on Pocket (Opens in new window) Pocket Like Loading... Posted on May 30, 2022 by Simon Phipps Tagged AlmaLinux Red Hat Comments 2 Comments on Why we all need Almalinux Why we all need Almalinux … whether we use it or not! The AlmaLinux OS Foundation continues to make license-compliant releases of a fully RHEL-Compatible Linux distribution within one or two days of RedHat’s releases. This (and indeed any independent downstream of RHEL) is actually good for everyone, including Red Hat. The most recent release, AlmaLinux 9.0 , appeared within a week of the release of RHEL 9. It validates Red Hat’s good faith The AlmaLinux community validates that Red Hat’s product is indeed a true, forkable Open Source project and not a bad-faith hack like some other self-described open source products (for example, Forgerock, who appear to actively engineer their code to be unforkable by failing to document which parts are proprietary and which are just the CDDL-licensed Sun/Oracle code they took, and by failing to provide tools for debranding). It provides those who need a self maintained Linux with something that has an off-ramp Not everyone wants Red Hat’s subscription. Some Linux users – notably in the cloud hosting market – are happy to self-support and have the skills and resources to do so. They could base their work on Debian or another distribution, but as a RHEL downstream their customers retain a freedom of choice of support provider, including being free to switch to Red Hat at any time. It creates an on-ramp for RHEL Red Hat benefits from the growth of its adoption base, as users of downstream distributions can and do become customers. It creates a no negotiation zone for innovative hacking Some users need access to RHEL for skunkworks hacking that does not affect their licensing accounting under their Red Hat agreement. This flexibility used to be included within Red Hat’s licensing universe but a hacker at a hedge fund on Wall Street ruined things for everyone by gaming Red Hat’s original trust in their customers and using a single licence to support an entire company. Red Hat was forced to reword its customer agreement to embrace all systems running RHEL. Disclosure: I am a director of the AlmaLinux OS Foundation and its founder CloudLinux is a client. This article represents my own opinion and is no way endored by either entity. Share this: Click to share on LinkedIn (Opens in new window) LinkedIn Click to share on X (Opens in new window) X Click to share on Facebook (Opens in new window) Facebook More Click to email a link to a friend (Opens in new window) Email Click to share on Pinterest (Opens in new window) Pinterest Click to share on Tumblr (Opens in new window) Tumblr Click to share on Reddit (Opens in new window) Reddit Click to share on Pocket (Opens in new window) Pocket Like Loading... Post navigation ← Older posts Tip Jars! We’re an independent team & rely on your support & donations for our community interventions – thanks! Sponsor at GitHub Can We Help? Meshed Insights can help you with your open source strategy. Contact us for support with community, governance, licensing, branding or any other aspect of your open source strategy. We can also support you on digital rights issues. We offer research reports and white papers for your management and Board from experienced advisors, as well as on-site consulting and longer term engagements such as non-executive directorships. Contact us now , or read more about our services. Search January 2026 M T W T F S S 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 « Nov Apache API Bitcoin blockchain Blocking Bolzano business model Censorship CERN Chromebook Cloud Community Compliance Contributor Agreements Copyleft Copyright crowdfunding Culture European Directives Facebook FAQ FLOSS Weekly FOSDEM Foundations FRAND Free Software Github Google Governance Government GPL InfoWorld Intellectual property Internet Interoperability Java LibreOffice License licenses Licensing Linux Linux Desktop Linux Voice MariaDB Meshed Society Microsoft NSA ODF OIN Open data OpenJDK Open Rights Group open source OpenSource Open source license open standards Oracle Oracle v Google OSCON OSI OSPO Patent Patents Patent Trolls Policy Privacy Rights Ratchet SCOTUS Security software freedom Software Heritage Software Patents Standards Sun The Linux Foundation Enter your email address to receive new posts via email. Email Address: Join Mailing List Follow Simon on Mastodon Follow Meshed Insights on Mastodon Website Powered by WordPress.com . Meshed Insights Ltd Website Powered by WordPress.com . Subscribe Subscribed Meshed Insights Ltd Join 127 other subscribers Sign me up Already have a WordPress.com account? Log in now. Meshed Insights Ltd Subscribe Subscribed Sign up Log in Report this content View site in Reader Manage subscriptions Collapse this bar Loading Comments... Write a Comment... Email (Required) Name (Required) Website %d | 2026-01-13T08:49:34 |
https://dev.to/souviktests/sos-in-morse-code-4omf | SOS in Morse Code - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Souvik Paul Posted on Sep 5, 2024 SOS in Morse Code # wecoded # morsecode # learning In this video, I've said SOS in Morse Code. Morse Code is one of the first digital communication languages used worldwide. This code was invented by Samuel Morse in 1938. Know more: https://en.wikipedia.org/wiki/Morse_code SOS! Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Souvik Paul Follow Just an ordinary computer science noob 🖱️ Location Kolkata, India Work Software Developer, Blogger Joined Jun 16, 2020 Trending on DEV Community Hot I Debug Code Like I Debug Life (Spoiler: Both Throw Exceptions) # discuss # career # programming # beginners AI should not be in Code Editors # programming # ai # productivity # discuss Meme Monday # discuss # watercooler # jokes 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/t/roundrecap/page/2 | Roundrecap Page 2 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # roundrecap Follow Hide Sharing stories, scores, and highlights from recent rounds Create Post Older #roundrecap posts 1 2 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://www.fine.dev/blog/bolt-vs-v0-es#por-que-suscribirse-a-fine | Bolt vs. V0: ¿Cuál es la mejor herramienta de programación con IA para el desarrollo front-end? Home Docs Changelog Pricing Sign in Get started -> Menu Home Docs Changelog Pricing <- Go Back Bolt vs. V0: ¿Cuál es la mejor herramienta de programación con IA para el desarrollo front-end? Introducción En el mundo del desarrollo front-end, dos herramientas de programación con IA han ganado popularidad: Bolt y V0 . Ambas ofrecen características únicas que pueden mejorar la productividad de los desarrolladores, pero ¿cuál es la mejor opción para tus necesidades específicas? Este blog compara estas dos herramientas, centrándose en sus capacidades, facilidad de uso y rendimiento general. Diferencias Principales Bolt está diseñado para optimización de código y generación rápida . Ofrece sugerencias de código en tiempo real y es conocido por su capacidad para mejorar la eficiencia del código. Por otro lado, V0 se centra en integración y colaboración , permitiendo a los equipos trabajar juntos de manera más efectiva a través de características de colaboración en tiempo real. Ambas herramientas utilizan tecnologías avanzadas de IA, pero Bolt es más adecuado para desarrolladores que buscan mejorar la eficiencia del código, mientras que V0 es ideal para equipos que priorizan la colaboración. Rendimiento y Usabilidad El rendimiento de estas herramientas es crucial para los desarrolladores que buscan mejorar su flujo de trabajo. Bolt ofrece tiempos de respuesta rápidos y es altamente eficiente en la generación de código, mientras que V0 proporciona una experiencia de usuario fluida con su interfaz intuitiva y características de colaboración. Ambas herramientas son fáciles de usar, pero sus capacidades brillan en diferentes áreas. Bolt es excelente para optimización de código , mientras que V0 se destaca en colaboración en equipo . Actualización de Bolt - Octubre 2024 - ¿Es Bolt ahora mejor que V0 para el desarrollo front-end? En octubre de 2024, se anunció una actualización significativa de Bolt. Las recientes mejoras han aumentado sus capacidades de optimización de código, superando a V0 en pruebas de rendimiento. Esta actualización refleja la mayor precisión de Bolt en la generación de código eficiente y su capacidad para integrarse con herramientas de desarrollo populares. Las pruebas iniciales indican que Bolt ahora sobresale en tareas de desarrollo front-end, como optimización de CSS y generación de componentes de React. Empresas como GitHub han informado mejoras significativas en la eficiencia del desarrollo con la nueva versión de Bolt. Ejemplos Prácticos de Uso de IA en el Desarrollo Front-end con Bolt y V0 Bolt: Optimización de CSS: Usa Bolt para mejorar la eficiencia del código CSS y reducir el tiempo de carga de la página. Generación de componentes de React: Emplea Bolt para crear componentes de React optimizados y reutilizables. Refactorización de código: Ideal para reestructurar código existente para mejorar su legibilidad y rendimiento. V0: Colaboración en tiempo real: Permite a los equipos trabajar juntos en proyectos de desarrollo front-end con características de colaboración en tiempo real. Integración con herramientas de desarrollo: Usa V0 para integrar fácilmente con herramientas populares como GitHub y Slack. Gestión de proyectos: Facilita la gestión de proyectos con su interfaz intuitiva y características de seguimiento de tareas. Conclusión Al decidir entre Bolt y V0 , considera tus necesidades específicas de desarrollo front-end. Bolt ofrece una mejor optimización de código y generación rápida, mientras que V0 proporciona una colaboración más efectiva y una integración fluida con herramientas de desarrollo. Ambas herramientas son poderosas y pueden mejorar significativamente tu productividad como desarrollador front-end. Regístrate en una plataforma como Fine , que incluye acceso a ambas herramientas, para aprovechar lo mejor de ambos mundos sin pagar de más. ¿Por qué suscribirse a Fine? Fine es una plataforma que ofrece acceso a Bolt y V0 , permitiendo a los desarrolladores cambiar entre estas herramientas según sus necesidades. Esta flexibilidad es perfecta para aquellos que requieren optimización de código de Bolt o colaboración efectiva de V0. Con Fine, no hay necesidad de gestionar tus propias claves API o preocuparte por los límites de uso: todo está incluido. Suscribirse a Fine simplifica el proceso, ofreciendo acceso rentable a ambas herramientas para todas tus tareas de desarrollo front-end. Fuentes "Bolt vs V0: ¿Cuál es mejor para el desarrollo front-end?" Tech Blog , 20 Sep 2024. Enlace . "Comparación de herramientas de programación con IA para el desarrollo front-end." Dev Tools Review , 18 Sep 2024. Enlace . "Actualización de Bolt 2024." Bolt News . Enlace . Tabla de Contenidos Introducción Diferencias Principales Rendimiento y Usabilidad Actualización de Bolt - Octubre 2024 - ¿Es Bolt ahora mejor que V0 para el desarrollo front-end? Ejemplos Prácticos de Uso de IA en el Desarrollo Front-end con Bolt y V0 Conclusión ¿Por qué suscribirse a Fine? Start building today Try out the smoothest way to build, launch and manage an app Try for Free -> © Fine.dev - All rights reserved. Product Overview AI Workflows Pricing & Plans Changelog Blog Docs Company Press Terms & Conditions Privacy policy | 2026-01-13T08:49:34 |
https://dev.to/lingarao_yechuri_2f59259c | Lingarao Yechuri - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Close Follow User actions Lingarao Yechuri I am Web developer Joined Joined on Dec 18, 2025 More info about @lingarao_yechuri_2f59259c Post 1 post published Comment 0 comments written Tag 0 tags followed Navigating Long AI Chats Is Broken — So I Built a Chrome Extension to Fix It Lingarao Yechuri Lingarao Yechuri Lingarao Yechuri Follow Jan 12 Navigating Long AI Chats Is Broken — So I Built a Chrome Extension to Fix It # chatgpt # gemini # productivity # ux Comments Add Comment 2 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://www.facebook.com/sharer.php?u=https%3A%2F%2Fdev.to%2Fshuckle_xd%2Fyou-cant-trust-images-anymore-58jh | Facebook에 로그인 Notice 계속하려면 로그인해주세요. Facebook에 로그인 계속하려면 로그인해주세요. 로그인 계정을 잊으셨나요? 또는 새 계정 만들기 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T08:49:34 |
https://dev.to/resumemind/how-to-write-a-resume-that-gets-interviews-not-rejections-127b#how-to-write-experience-correctly | How to Write a Resume That Gets Interviews (Not Rejections) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Resumemind Posted on Jan 12 How to Write a Resume That Gets Interviews (Not Rejections) # career # interview # tutorial Most resumes don’t fail because the candidate is unqualified. They fail because the resume doesn’t communicate value fast enough. Recruiters spend 6–8 seconds scanning a resume before deciding whether to continue or reject it. If your resume doesn’t pass that first scan, it’s over — no matter how skilled you are. This guide will show you step by step how to write a resume that gets interviews, not silent rejections. 1. Understand How Recruiters Actually Read Resumes Before writing anything, you need to understand how resumes are evaluated. Recruiters don’t read resumes line by line. They scan for: Job title relevance Clear role identity Skills that match the job Recent experience or projects Structure and readability If these aren’t obvious in seconds, the resume is rejected. 👉 Your goal is clarity, not creativity. 2. Start With a Clear Role-Focused Resume Header Your resume must immediately answer one question: Who are you professionally? ❌ Weak header John Doe Email | Phone | Location ✅ Strong header John Doe Junior Software Developer | Frontend (Angular) Email | Phone | LinkedIn | Portfolio This instantly tells the recruiter: your level your role your focus Never make recruiters guess. 3. Write a Resume Summary That Sells (Not One That Repeats) Your resume summary is not your life story. It’s a 2–4 line pitch. ❌ Bad summary “Hardworking and motivated individual looking for opportunities to grow.” This says nothing. ✅ Good summary Junior Software Developer with hands-on experience building web applications using Angular and Spring Boot. Strong in problem-solving, REST APIs, and clean UI design. Actively seeking an entry-level role where I can contribute and grow. A good summary: mentions your role highlights key skills shows direction 4. Experience Matters — Even If You Have No Job Experience Many people think: “I can’t write a good resume because I have no experience.” That’s false. Recruiters accept: projects internships freelance work academic projects self-initiated work How to Write Experience Correctly Instead of listing duties, list impact. ❌ Bad: Built a website Worked with Angular ✅ Good: Built a responsive web application using Angular and REST APIs Implemented authentication and improved UI usability If you don’t have job experience, projects become your experience. 5. Skills Section: Be Honest, Relevant, and Specific Your skills section should support your role — not show everything you’ve ever touched. ❌ Bad skills list HTML, CSS, Java, Python, Photoshop, Networking, Excel This looks unfocused. ✅ Good skills list Frontend: Angular, TypeScript, HTML, CSS Backend: Java, Spring Boot, REST APIs Tools: Git, GitHub, Postman Only list skills you’re ready to discuss in an interview. 6. Formatting Can Get You Rejected Instantly Even strong content can fail if formatting is poor. Use: 1 page (for juniors) clear section headings consistent spacing readable font bullet points Avoid: long paragraphs heavy colors icons everywhere photos (unless required) fancy designs that hurt readability A clean resume looks professional and trustworthy. 7. Tailor Your Resume for Each Job (This Is Critical) Using one resume for every job is one of the biggest mistakes job seekers make. You should: adjust your summary reorder skills emphasize relevant projects This doesn’t mean rewriting everything — it means highlighting what matters most for that role. Tailoring your resume alone can double your interview chances. 8. Common Resume Mistakes That Lead to Rejection Avoid these at all costs: No role mentioned Weak or generic summary No projects listed Grammar mistakes Overcrowded layout Irrelevant skills Copy-pasted content Recruiters see these mistakes every day — and reject fast. 9. Get a Second Pair of Eyes on Your Resume One of the best things you can do is get honest feedback. When reviewing resumes manually, the most common missing elements are: unclear role weak summary missing experience descriptions no direction You might not see these issues yourself. Getting your resume reviewed by another person can completely change your results. Final Thoughts A resume that gets interviews is not about being perfect. It’s about being clear, relevant, and honest. If recruiters can quickly understand: who you are what you can do and why you fit the role You’ll start getting callbacks. Next Step If you’re unsure whether your resume is working, get it reviewed before you apply. Often, a few small changes are all it takes to start getting interviews. We offer a free manual resume review , where real people review resumes daily and give honest feedback — not automated scores. 👉 Request a free resume review: https://resumemind.com/public/resume-review Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Resumemind Follow Helping software developers and other related tech experts like project managers, QA, businesses analysts crafting their tech resumes for their next job applications. Joined Jan 4, 2026 More from Resumemind How I Built a Manual Resume Review System with Spring Boot & Angular # angular # career # showdev # springboot I Reviewed 50 Junior Developer Resumes — Here’s What Actually Works # beginners # career # codenewbie How to Write a Resume With No Work Experience (Fresh Graduate Guide for 2026) # beginners # career # tutorial 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/t/web3/videos#main-content | Videos - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close All videos # web3 on Video 𝐒𝐭𝐚𝐤𝐞𝐋𝐢𝐆𝐚𝐦𝐞𝐬 Soumil Mukhopadhyay 07:05 Chain Abstraction - Etherspot Pulse Demo Alexandra 09:55 Account Abstraction's Role in Decentralized Innovation | Michael Messele | Etherspot | ZebuLive 2024 Alexandra 02:38 GMX trading with Etherspot - Easy as ABC Alexandra 01:03 Welcome to Solcial (Web3 Social Media Network on Solana) Vadim Voronovskiy 58:13 🎉 PyLadies Dublin Jan 2023 Meetup whykay 👩🏻💻🐈🏳️🌈 (she/her) 05:56 How Blockchain hides your Identity? Siddharth Singh Baghel loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://open.forem.com/ava_mendes | Ava Mendes - Open Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Open Forem Close Follow User actions Ava Mendes ⚡ Especialista em portabilidade de energia elétrica | Fundadora @ energialex.app | Ajudo brasileiros a economizarem até 20% na conta de luz | Energia limpa, economia inteligente e sustentabilidade Location Brasil Joined Joined on Oct 20, 2025 Personal website https://energialex.app More info about @ava_mendes Badges Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Post 8 posts published Comment 0 comments written Tag 2 tags followed Energia Solar + Mercado Livre para MEI: Requisitos Técnicos em 2025 Ava Mendes Ava Mendes Ava Mendes Follow Dec 25 '25 Energia Solar + Mercado Livre para MEI: Requisitos Técnicos em 2025 # news # freelance # security Comments Add Comment 8 min read Energia Solar + Mercado Livre para MEI: Requisitos Técnicos em 2025 Ava Mendes Ava Mendes Ava Mendes Follow Dec 15 '25 Energia Solar + Mercado Livre para MEI: Requisitos Técnicos em 2025 Comments Add Comment 6 min read Tarifa Branca em Zona Rural: Economia Real para Consumo Baixo Ava Mendes Ava Mendes Ava Mendes Follow Nov 24 '25 Tarifa Branca em Zona Rural: Economia Real para Consumo Baixo Comments Add Comment 6 min read MP 1.300/2025: Entenda os Prazos e Custos para Retornar ao Mercado Cativo Ava Mendes Ava Mendes Ava Mendes Follow Nov 20 '25 MP 1.300/2025: Entenda os Prazos e Custos para Retornar ao Mercado Cativo Comments Add Comment 7 min read Bandeiras Tarifárias 2025: cores, valores e como economizar Ava Mendes Ava Mendes Ava Mendes Follow Nov 12 '25 Bandeiras Tarifárias 2025: cores, valores e como economizar # discuss # learning # watercooler Comments Add Comment 11 min read Por que minha conta de luz está tão alta em 2025? 7 causas ocultas Ava Mendes Ava Mendes Ava Mendes Follow Nov 11 '25 Por que minha conta de luz está tão alta em 2025? 7 causas ocultas Comments Add Comment 9 min read MP 1.300/2025: o que muda no mercado livre de energia até 2027 Ava Mendes Ava Mendes Ava Mendes Follow Nov 10 '25 MP 1.300/2025: o que muda no mercado livre de energia até 2027 # discuss # news Comments Add Comment 9 min read Quem pode fazer portabilidade de energia? Requisitos completos 2025 Ava Mendes Ava Mendes Ava Mendes Follow Nov 10 '25 Quem pode fazer portabilidade de energia? Requisitos completos 2025 Comments Add Comment 13 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Open Forem — A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Open Forem © 2016 - 2026. Where all the other conversations belong Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/paulo_abbcba03b4df70572fc/the-covenant-guardian-4547 | The Covenant Guardian - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Paulo Posted on Dec 12, 2025 The Covenant Guardian # devchallenge # xanochallenge # api # backend Xano AI-Powered Backend Challenge: Public API Submission This is a submission for the Xano AI-Powered Backend Challenge : Production-Ready Public API What I Built I built the Covenant Guardian Public API , an AI-powered covenant monitoring backend for financial institutions that exposes structured data about banks, borrowers, contracts, covenants, alerts, and adverse events. The goal is to turn the internal covenant engine into a production-ready public API that other teams can plug into to build risk dashboards, monitoring tools, and automated workflows without managing their own backend or database. The same Xano backend powers a React + TypeScript frontend deployed at [ https://illustrious-kelpie-c65700.netlify.app ]( https://illustrious-kelpie-c65700.netlify.app ), which serves as a live demo and reference client for consuming the API. The full project code (frontend + API integration + docs) is available on GitHub in the Covenant Guardian repository. Demo: https://illustrious-kelpie-c65700.netlify.app GitHub: https://github.com/seu-usuario/covenant-guardian API Documentation The backend is implemented on Xano with a managed PostgreSQL database and exposed as a versioned REST API suitable for real-world consumption by third-party apps. The API is organized into resource groups such as /banks , /borrowers , /contracts , /covenants , /alerts , and /adverse-events , under a base similar to: https://<workspace-id>.xano.io/api:v1/ – production `https://-staging.xano.io/api Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Paulo Follow Joined May 30, 2025 More from Paulo ConectaBairro: AI-Powered Cross-Platform Community App for Brazilian Social Impact # devchallenge # unoplatformchallenge # dotnet # crossplatform 🥊 MMA Coach Assistant - AI-Powered Fight Analysis # devchallenge # googleaichallenge # ai # gemini MMA Coach Assistant # devchallenge # googleaichallenge # ai # gemini 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/pyladiesdub/pyladies-dublin-november-meetup-519i | PyLadies Dublin November Meetup (last meetup of 2021) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse whykay 👩🏻💻🐈🏳️🌈 (she/her) for PyLadies Dublin Posted on Nov 25, 2021 • Edited on Dec 10, 2021 PyLadies Dublin November Meetup (last meetup of 2021) # python # maker # datascience # video PyLadies Dublin 2021 (9 Part Series) 1 Creative coding in Python by Beatrice Ionascu (CTO & Co-Founder, ImagiLabs) 2 PyLadies Dublin Feb'21: Automatic multiclass news classification w/ DL and NLP ... 5 more parts... 3 Bias in NLP || Automating social media content w/ Python & Mako 4 PyLadies Dublin: Shipping Python Apps using Podman / Collaborative documentation as code with Git, Mkdocs and Pandoc 5 PyLadies Dublin July Meetup: FastAPI, Lambdas, PyTest and other cool things 6 PyLadies Dublin Aug Meetup: HuggingFace Transformers || PySparks 101 7 PyLadies Dublin September Meetup: Lifelogging || Sentiment Analysis 8 PyLadies Dublin x PyLadies Paris October Meetup 9 PyLadies Dublin November Meetup (last meetup of 2021) A quick write-up adapted from the post-event message sent to folks who joined us at the stream at our last event of 2021 . Huge thanks to our speakers Jeffrey Roe and Pavithra Eswaramoorthy . 🙌 A special thanks to Lei and Mick for all their support throughout this year. 🌈 Thanks to our community partners (alphabetical order): Coding Grace - Zoom ImagiLabs PSF - Meetup fees PyLadies If you missed our talks in the past couple of years, you can find them on our channel: https://www.youtube.com/channel/UCMunGHeQPceOWhNSqlmYWPg Don't forget to ❤️ like, subscribe and hit that 🔔 bell notification. Talk Details TALK 1: "Using Python to bring a physical game to the Internet" by Jeffrey Roe (15 mins) The talk will outline how a LED game got Jeffrey's living room onto the internet for all to play it. The project mixture Raspberry Pi, Arduino, LED display array and an IoT smart plug all in one. The game uses remote.tv to allow the player to remotely control all the buttons of this fun arcade-style LED game. The game has the user trying to kill all the red dots in order to stay alive and not see hot pink. About Jeffrey is a software/hardware engineer, working on public transport systems. In his spare time, he likes to make fun projects. On the team of festival makers for Dublin Maker, co-founder of Tog Hackerspace and Council member of Engineers Ireland 👉 https://twitter.com/Jeffrey_Roe TALK 2: "Scaling Data Science with Dask" by Pavithra Eswaramoorthy (30 mins) With the growing significance of big data for data science and machine learning, scaling data work is more important than ever. In this talk, you'll learn to scale your workflow to larger datasets and larger models, while staying in the comfort of the PyData ecosystem (NumPy, pandas, scikit-learn, Jupyter notebooks), using Dask. Dask is an open source library for parallel computing in Python. It provides a complete framework for distributed computing and makes it easy for data professionals to scale their workflows quickly. Dask is used in a wide range of domains from finance and retail to academia and life sciences. It is also leveraged internally by numerous special-purpose tools like XGBoost, RAPIDS, PyTorch, Prefect, Airflow, and more. After attending, you'll know: What is Dask, how it works, and what makes it powerful; What are parallel, distributed, and cloud computing technologies; When to consider scaling your data and machine learning work, and when not to; How to use Dask to leverage parallelism on your local workstation, such as your laptop; How to use Dask to harness the power of distributed clusters (on-cloud or on-prem) from the comfort of your laptop. About Pavithra works as an Evangelist at Coiled, where she helps make scalable data science more accessible to everyone. She also contributes to open-source software at Bokeh and Wikimedia. In her spare time, she enjoys a good book and coffee. :) 👉 https://www.linkedin.com/in/pavithra-eswaramoorthy-47977b146/ Announcements from the September event can be found here: https://twomeylee.notion.site/PyLadies-Dublin-November-2021-fc2c057ec6224f3790afbcbd877ceea4 Call for Speakers If you have CFP, feel free to post it below in the comments section. PyLadies Dublin When: Jan, Feb, Mar 2022 Interested in sharing your project or something cool you came across? Submit your talk/Demo/workshop to following: Call for Proposal Form Events PyjamasConf 2021 Conference Date: December 4th 2021 https://pyjamas.live Python Ireland Christmas Get Together When: Wed Dec 8 https://python.ie Python Ireland: Speakers Coaching Session When: Sat Jan 22, 2022 https://python.ie/coaching-program ⛔️ There will be no PyLadies Dublin next month The next one will be on Tue Jan 18 (18:30) and will be online. If you like to give a short talk, submit your talk with this PyLadies Dublin CFP 2022 form Any questions, drop us an email at dublin@pyladies.com PyLadies Dublin 2021 (9 Part Series) 1 Creative coding in Python by Beatrice Ionascu (CTO & Co-Founder, ImagiLabs) 2 PyLadies Dublin Feb'21: Automatic multiclass news classification w/ DL and NLP ... 5 more parts... 3 Bias in NLP || Automating social media content w/ Python & Mako 4 PyLadies Dublin: Shipping Python Apps using Podman / Collaborative documentation as code with Git, Mkdocs and Pandoc 5 PyLadies Dublin July Meetup: FastAPI, Lambdas, PyTest and other cool things 6 PyLadies Dublin Aug Meetup: HuggingFace Transformers || PySparks 101 7 PyLadies Dublin September Meetup: Lifelogging || Sentiment Analysis 8 PyLadies Dublin x PyLadies Paris October Meetup 9 PyLadies Dublin November Meetup (last meetup of 2021) Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse PyLadies Dublin Follow We are looking for speakers from 5 min lightning talks, demos, talks that are not more than 30 minutes. Anything Python-related from your projects, cool libraries, and more! Submit Talk More from PyLadies Dublin PyLadies Dublin visits Fingal MakerSpace # pyladies # maker How to test Machine Learning code in Python? April 2023 # video # pyladies PyLadies Dublin x Women in AI Ireland in-person event (Sat May 21, 2022) # pyladies # diversityintech # ai # video 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/resumemind/how-to-write-a-resume-that-gets-interviews-not-rejections-127b#4-experience-matters-even-if-you-have-no-job-experience | How to Write a Resume That Gets Interviews (Not Rejections) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Resumemind Posted on Jan 12 How to Write a Resume That Gets Interviews (Not Rejections) # career # interview # tutorial Most resumes don’t fail because the candidate is unqualified. They fail because the resume doesn’t communicate value fast enough. Recruiters spend 6–8 seconds scanning a resume before deciding whether to continue or reject it. If your resume doesn’t pass that first scan, it’s over — no matter how skilled you are. This guide will show you step by step how to write a resume that gets interviews, not silent rejections. 1. Understand How Recruiters Actually Read Resumes Before writing anything, you need to understand how resumes are evaluated. Recruiters don’t read resumes line by line. They scan for: Job title relevance Clear role identity Skills that match the job Recent experience or projects Structure and readability If these aren’t obvious in seconds, the resume is rejected. 👉 Your goal is clarity, not creativity. 2. Start With a Clear Role-Focused Resume Header Your resume must immediately answer one question: Who are you professionally? ❌ Weak header John Doe Email | Phone | Location ✅ Strong header John Doe Junior Software Developer | Frontend (Angular) Email | Phone | LinkedIn | Portfolio This instantly tells the recruiter: your level your role your focus Never make recruiters guess. 3. Write a Resume Summary That Sells (Not One That Repeats) Your resume summary is not your life story. It’s a 2–4 line pitch. ❌ Bad summary “Hardworking and motivated individual looking for opportunities to grow.” This says nothing. ✅ Good summary Junior Software Developer with hands-on experience building web applications using Angular and Spring Boot. Strong in problem-solving, REST APIs, and clean UI design. Actively seeking an entry-level role where I can contribute and grow. A good summary: mentions your role highlights key skills shows direction 4. Experience Matters — Even If You Have No Job Experience Many people think: “I can’t write a good resume because I have no experience.” That’s false. Recruiters accept: projects internships freelance work academic projects self-initiated work How to Write Experience Correctly Instead of listing duties, list impact. ❌ Bad: Built a website Worked with Angular ✅ Good: Built a responsive web application using Angular and REST APIs Implemented authentication and improved UI usability If you don’t have job experience, projects become your experience. 5. Skills Section: Be Honest, Relevant, and Specific Your skills section should support your role — not show everything you’ve ever touched. ❌ Bad skills list HTML, CSS, Java, Python, Photoshop, Networking, Excel This looks unfocused. ✅ Good skills list Frontend: Angular, TypeScript, HTML, CSS Backend: Java, Spring Boot, REST APIs Tools: Git, GitHub, Postman Only list skills you’re ready to discuss in an interview. 6. Formatting Can Get You Rejected Instantly Even strong content can fail if formatting is poor. Use: 1 page (for juniors) clear section headings consistent spacing readable font bullet points Avoid: long paragraphs heavy colors icons everywhere photos (unless required) fancy designs that hurt readability A clean resume looks professional and trustworthy. 7. Tailor Your Resume for Each Job (This Is Critical) Using one resume for every job is one of the biggest mistakes job seekers make. You should: adjust your summary reorder skills emphasize relevant projects This doesn’t mean rewriting everything — it means highlighting what matters most for that role. Tailoring your resume alone can double your interview chances. 8. Common Resume Mistakes That Lead to Rejection Avoid these at all costs: No role mentioned Weak or generic summary No projects listed Grammar mistakes Overcrowded layout Irrelevant skills Copy-pasted content Recruiters see these mistakes every day — and reject fast. 9. Get a Second Pair of Eyes on Your Resume One of the best things you can do is get honest feedback. When reviewing resumes manually, the most common missing elements are: unclear role weak summary missing experience descriptions no direction You might not see these issues yourself. Getting your resume reviewed by another person can completely change your results. Final Thoughts A resume that gets interviews is not about being perfect. It’s about being clear, relevant, and honest. If recruiters can quickly understand: who you are what you can do and why you fit the role You’ll start getting callbacks. Next Step If you’re unsure whether your resume is working, get it reviewed before you apply. Often, a few small changes are all it takes to start getting interviews. We offer a free manual resume review , where real people review resumes daily and give honest feedback — not automated scores. 👉 Request a free resume review: https://resumemind.com/public/resume-review Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Resumemind Follow Helping software developers and other related tech experts like project managers, QA, businesses analysts crafting their tech resumes for their next job applications. Joined Jan 4, 2026 More from Resumemind How I Built a Manual Resume Review System with Spring Boot & Angular # angular # career # showdev # springboot I Reviewed 50 Junior Developer Resumes — Here’s What Actually Works # beginners # career # codenewbie How to Write a Resume With No Work Experience (Fresh Graduate Guide for 2026) # beginners # career # tutorial 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://open.forem.com/t/cloud#main-content | The "Cloud" - Open Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Open Forem Close The "Cloud" Follow Hide There is no cloud, only other peoples computers. Create Post submission guidelines Be nice. Be respectful. Assume best intentions. Be kind, rewind. Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu 🚀 Roast My Portfolio: I Launched mobeenfolio.com (Built with React & Firebase) long time ago. Mobeen ul Hassan Hashmi Mobeen ul Hassan Hashmi Mobeen ul Hassan Hashmi Follow Jan 4 🚀 Roast My Portfolio: I Launched mobeenfolio.com (Built with React & Firebase) long time ago. # discuss # cloud # showcase # webdev Comments Add Comment 1 min read Solved: I hired two junior people and realized media buyers being bad at creative strategy is actually a huge problem Darian Vance Darian Vance Darian Vance Follow Dec 31 '25 Solved: I hired two junior people and realized media buyers being bad at creative strategy is actually a huge problem # devops # programming # tutorial # cloud Comments Add Comment 7 min read Solved: PoE+++?! WHEN WILL THE MADNESS END? Darian Vance Darian Vance Darian Vance Follow Dec 28 '25 Solved: PoE+++?! WHEN WILL THE MADNESS END? # devops # programming # tutorial # cloud Comments Add Comment 7 min read Solved: How to look for a good MSP Darian Vance Darian Vance Darian Vance Follow Dec 26 '25 Solved: How to look for a good MSP # devops # programming # tutorial # cloud Comments Add Comment 8 min read Message Trace in Microsoft 365 Tabinda Zeeshan Tabinda Zeeshan Tabinda Zeeshan Follow for IT Services and Consulting Dec 9 '25 Message Trace in Microsoft 365 # help # cloud # productivity Comments Add Comment 2 min read Best Production Management Software for Small Manufacturers in 20256 Learn dev tools Learn dev tools Learn dev tools Follow Nov 26 '25 Best Production Management Software for Small Manufacturers in 20256 # productivity # management # software # cloud Comments Add Comment 1 min read 10 Cloud-Based Translation Management System (TMS) Benefits Colin Reed Colin Reed Colin Reed Follow Nov 13 '25 10 Cloud-Based Translation Management System (TMS) Benefits # management # tools # cloud # productivity 5 reactions Comments Add Comment 4 min read AppExchange Growth: How niche apps are reshaping the ecosystem Il'ya Dudkin Il'ya Dudkin Il'ya Dudkin Follow Sep 28 '25 AppExchange Growth: How niche apps are reshaping the ecosystem # news # cloud # software Comments Add Comment 3 min read Sourcing Data from Different Platforms Using Tableau: A Complete Guide with Real-World Applications Anshuman Anshuman Anshuman Follow Sep 28 '25 Sourcing Data from Different Platforms Using Tableau: A Complete Guide with Real-World Applications # cloud # datascience # learning # tools 5 reactions Comments Add Comment 6 min read How to Customize the Service Catalog in BILLmanager Mateo Rivera Mateo Rivera Mateo Rivera Follow Sep 27 '25 How to Customize the Service Catalog in BILLmanager # tutorial # software # cloud # cloudcomputing Comments Add Comment 5 min read Day 44 of Data analytics journey ! Ramya .C Ramya .C Ramya .C Follow Sep 28 '25 Day 44 of Data analytics journey ! # cloud # datascience # learning # security 1 reaction Comments Add Comment 2 min read loading... trending guides/resources 10 Cloud-Based Translation Management System (TMS) Benefits Best Production Management Software for Small Manufacturers in 20256 🚀 Roast My Portfolio: I Launched mobeenfolio.com (Built with React & Firebase) long time ago. Perspectives on Networking Solved: I hired two junior people and realized media buyers being bad at creative strategy is act... Solved: How to look for a good MSP Message Trace in Microsoft 365 Solved: PoE+++?! WHEN WILL THE MADNESS END? 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Open Forem — A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Open Forem © 2016 - 2026. Where all the other conversations belong Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/ezzahirtaha/bun-a-new-javascript-runtime-for-the-modern-era-46dm | Bun: A new JavaScript runtime for the modern era - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse EZZAHIR Taha Posted on Sep 15, 2023 Bun: A new JavaScript runtime for the modern era # bunjs # javascript # node # programming Bun is a new JavaScript runtime built from scratch to serve the modern JavaScript ecosystem. It is designed to be fast, lightweight, and easy to use. Bun provides a minimal set of highly-optimizable APIs for performing common tasks, like starting an HTTP server and writing files. It also includes a complete toolkit for building JavaScript apps, including a package manager, test runner, and bundler. Bun is still under development, but it has already been used to build some popular projects, such as Next.js and SvelteKit. It is a promising new tool for JavaScript developers, and I am interested to see how it develops in the future. Here are some of the key benefits of using Bun: Speed: Bun is significantly faster than Node.js. This is because Bun is built on top of the JavaScriptCore engine, which is the same engine that powers Safari. Bun also uses a number of optimizations to make it even faster. Lightweight: Bun is much lighter weight than Node.js. This means that Bun can be used in resource-constrained environments, such as serverless functions. Ease of use: Bun is designed to be easy to use. It has a simple and intuitive API, and it comes with a number of tools to help developers get started quickly. Complete toolkit: Bun includes a complete toolkit for building JavaScript apps, including a package manager, test runner, and bundler. This means that developers can use Bun to build their entire app from start to finish. If you are looking for a fast, lightweight, and easy-to-use JavaScript runtime, then Bun is worth considering. It is still under development, but it has a lot of potential. Here are some specific use cases where Bun may be a good fit: Building high-performance server-side applications: Bun is ideal for building high-performance server-side applications because it is so fast and lightweight. Developing serverless functions: Bun is a good choice for developing serverless functions because it is lightweight and easy to use. Building modern web applications: Bun can be used to build modern web applications, such as Next.js and SvelteKit. If you are interested in trying Bun, you can install it from the Bun website. There are also a number of tutorials and resources available to help you get started. Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse EZZAHIR Taha Follow I am a full-stack developer with a passion for creating dynamic and interactive web applications. Location Casablanca, Morocco Education University Work Junior Full stack Web Developer Joined Feb 10, 2023 More from EZZAHIR Taha Understanding the React Component Lifecycle! # react # javascript # webdev # frontend A Beginner's Guide to React Redux Toolkit: Simplify Your State Management # react # redux # webdev # javascript What's the difference between Nuxt js and Vite? # frontend # node # vue # react 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
https://dev.to/t/computerscience/page/239 | Computer Science 🤓 Page 239 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Computer Science 🤓 Follow Hide This tag is for sharing and asking questions about anything related to computer science, including data structures, algorithms, research, and white papers! 🤓 Create Post submission guidelines Please ensure that any post that is tagged with #computerscience is related to computer science in some way. Promotional posts will be untagged, as will posts unrelated to CS. Please also be sure that your content adheres to the DEV Code of Conduct and that your comments are constructive and kind. about #computerscience Did you learn about a new data structure recently? Or perhaps you tried to implement an algorithm in a new language? Or maybe you need help understanding a white paper? The #computerscience tag is a great place for any of these questions and ideas. Please be sure to cross-tag any content that might help other folks in the DEV community. For example, an introduction to linked lists should also be tagged with the #beginners tag. Similarly, a post that asks for a simple explanation to the traveling salesman problem should be tagged with the #explainlikeimfive tag. Older #computerscience posts 236 237 238 239 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:34 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.