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/t/mentalhealth/page/6 | Mental Health Page 6 - 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 Mental Health Follow Hide Mental health matters! Break the stigma. We can empower ourselves and each other to invest in our mental health. We can give support and care to ourselves and each other while we struggle. Let's talk about making our mental health priority. Create Post about #mentalhealth Posts should be related to mental health. This is a pretty wide category but some things that are included are: Managing mental health as a developer Living with mental illness and how it affects your work Ways to cope with mental health issues Avoiding burn out Tools, apps, and methods that help you with your mental health ...and more “Your mental health is a priority. Your happiness is an essential. Your self-care is a necessity.” Struggling? Help is out there. Click here to find a list of global mental health resources and hotlines. Older #mentalhealth posts 3 4 5 6 7 8 9 10 11 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu I tracked 7 daily habits for 3 weeks. The data surprised me. Alex Chen Alex Chen Alex Chen Follow Oct 30 '25 I tracked 7 daily habits for 3 weeks. The data surprised me. # productivity # mentalhealth # data # habits 6 reactions Comments 1 comment 2 min read What I Learned From 60 Days of Brutal Honesty in My Work Journal Ed Ed Ed Follow Oct 31 '25 What I Learned From 60 Days of Brutal Honesty in My Work Journal # devjournal # mentalhealth # productivity 1 reaction Comments 2 comments 4 min read 🌊 Part 3.5 — Calm Between Waves Masato Kato Masato Kato Masato Kato Follow Oct 29 '25 🌊 Part 3.5 — Calm Between Waves # ai # creativity # poetry # mentalhealth 2 reactions Comments Add Comment 3 min read Ted talks that everyone should hear - part 1 Or Yaacov Or Yaacov Or Yaacov Follow Sep 23 '25 Ted talks that everyone should hear - part 1 # discuss # learning # mentalhealth Comments Add Comment 3 min read Practical Strategies to Improve Your Mental Health Every Day Oliver Davis Oliver Davis Oliver Davis Follow Sep 23 '25 Practical Strategies to Improve Your Mental Health Every Day # mentalhealth # therapy # selfcare # wellnesstips Comments Add Comment 4 min read How Endless Scrolling Broke My Focus — and Why I Built Block Scroll to Fix It Block Scroll Block Scroll Block Scroll Follow Oct 26 '25 How Endless Scrolling Broke My Focus — and Why I Built Block Scroll to Fix It # productivity # mentalhealth # digitalwellbeing # startup 6 reactions Comments 1 comment 3 min read 🖥️ Cut the Screen, Boost Your Mood: A Developer’s Guide to Digital Wellness NVelUp NVelUp NVelUp Follow Sep 22 '25 🖥️ Cut the Screen, Boost Your Mood: A Developer’s Guide to Digital Wellness # digitalwellness # mentalhealth # productivity # selfcare Comments Add Comment 2 min read We Need to Talk About How Toxic Dev Culture Has Become (And How We Fix It) Elvis Sautet Elvis Sautet Elvis Sautet Follow Oct 23 '25 We Need to Talk About How Toxic Dev Culture Has Become (And How We Fix It) # culture # community # mentalhealth # webdev 26 reactions Comments 3 comments 15 min read Unleashing Developer Potential: Balancing Cognitive Load for Peak Productivity George Udonte George Udonte George Udonte Follow Oct 23 '25 Unleashing Developer Potential: Balancing Cognitive Load for Peak Productivity # mentalhealth # productivity # softwareengineering Comments 1 comment 2 min read Know your tendencies - Questioning yourself (and others)- The 4 Tendencies Framework Davide de Paolis Davide de Paolis Davide de Paolis Follow Oct 22 '25 Know your tendencies - Questioning yourself (and others)- The 4 Tendencies Framework # personalgrowth # mentalhealth # growthmindset # leadership 1 reaction Comments Add Comment 5 min read 🌱 Acupuncture for Anxiety? Here’s What Developers Should Know 🧠 NVelUp NVelUp NVelUp Follow Sep 19 '25 🌱 Acupuncture for Anxiety? Here’s What Developers Should Know 🧠 # mentalhealth # productivity # selfcare # wellness Comments Add Comment 2 min read Some rejections hit hard Manasvi Pal Manasvi Pal Manasvi Pal Follow Oct 26 '25 Some rejections hit hard # career # interview # mentalhealth Comments 5 comments 1 min read 🧘♂️ Mindfulness Meditation: Science-Backed Path to a Calmer Mind NVelUp NVelUp NVelUp Follow Sep 18 '25 🧘♂️ Mindfulness Meditation: Science-Backed Path to a Calmer Mind # mentalhealth # mindfulness # wellness # neuroscience Comments Add Comment 2 min read When Passion Becomes Commodity Andrew Reese Andrew Reese Andrew Reese Follow Oct 8 '25 When Passion Becomes Commodity # discuss # mentalhealth # inclusion # watercooler 50 reactions Comments 16 comments 9 min read Balancing Focus and Fatigue as a Full-Time Developer Miriam Miriam Miriam Follow Oct 19 '25 Balancing Focus and Fatigue as a Full-Time Developer # help # productivity # mentalhealth # career Comments 2 comments 1 min read 💬 Breaking the Stigma: Why Open Mental Health Conversations Matter (and How You Can Help) NVelUp NVelUp NVelUp Follow Sep 16 '25 💬 Breaking the Stigma: Why Open Mental Health Conversations Matter (and How You Can Help) # mentalhealth # selfimprovement # productivity # wellbeing Comments Add Comment 2 min read I Built a Mental Ritual That Doesn’t Explain Itself katorymnddev katorymnddev katorymnddev Follow Sep 16 '25 I Built a Mental Ritual That Doesn’t Explain Itself # mentalhealth # mindfulness # webdev Comments Add Comment 4 min read Misunderstood: Notice What You’ve Been Feeling, Not Just What You Showed Rajat Singh Rajat Singh Rajat Singh Follow Sep 13 '25 Misunderstood: Notice What You’ve Been Feeling, Not Just What You Showed # misunderstoodbook # mentalhealth # sreekrishnaseelam # readforgrowth Comments Add Comment 3 min read Talk Therapy & Mental Wellbeing: A Developer’s Guide to Debugging the Mind 🧠 NVelUp NVelUp NVelUp Follow Sep 13 '25 Talk Therapy & Mental Wellbeing: A Developer’s Guide to Debugging the Mind 🧠 # mentalhealth # productivity # therapy # cbt Comments Add Comment 2 min read Moriah Behavioral Health’s Commitment to Reducing the Stigma Around Mental Health Moriah Behavioral Health Moriah Behavioral Health Moriah Behavioral Health Follow Sep 13 '25 Moriah Behavioral Health’s Commitment to Reducing the Stigma Around Mental Health # discuss # mentalhealth Comments Add Comment 4 min read A Review of 'Misunderstood': Insights into Mental Health Literature Preetinder Kaur Preetinder Kaur Preetinder Kaur Follow Sep 12 '25 A Review of 'Misunderstood': Insights into Mental Health Literature # misunderstood # sreekrishnaseelam # mentalhealth # awareness Comments Add Comment 2 min read How Gratitude Can Rewire Your Brain (and Why Devs Should Care) NVelUp NVelUp NVelUp Follow Sep 25 '25 How Gratitude Can Rewire Your Brain (and Why Devs Should Care) # productivity # mentalhealth Comments Add Comment 2 min read Introducing… Git Pushups Justin Higgins ➡️ Justin Higgins ➡️ Justin Higgins ➡️ Follow Sep 12 '25 Introducing… Git Pushups # git # github # mentalhealth # mobile Comments Add Comment 1 min read Discomfort isn’t the enemy: Lessons from 3 times I cried at work Davide de Paolis Davide de Paolis Davide de Paolis Follow Oct 13 '25 Discomfort isn’t the enemy: Lessons from 3 times I cried at work # leadership # impostersyndrome # mentalhealth # careerdevelopment 1 reaction Comments Add Comment 5 min read Congested Mind vs. Fresh Mind: The Hidden Factor in Problem Solving Muhammed Shafeeque AKP Muhammed Shafeeque AKP Muhammed Shafeeque AKP Follow Sep 9 '25 Congested Mind vs. Fresh Mind: The Hidden Factor in Problem Solving # programming # mentalhealth # career # productivity 1 reaction 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 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:48:42 |
https://anchor.fm/anand12/episodes/New-update-of-Battlegrounds-Mobile-India-e14d0ms | New update of Battlegrounds Mobile India by #WithAnand #WithAnand By Mr. Ånand Podcast of useful written blogs & Some original record ✨ Converting blogs into podcasts🎙️ ❤️Use #WithAnand on social media to share our work. 💌Want to Convert Blogs into podcast? Send me a voice message or DM on Social. Listen on Spotify Available on Report content on Spotify New update of Battlegrounds Mobile India #WithAnand Jul 13, 2021 Share 00:00 03:50 15 Recommended Books For Computer Science Students We are in the modern world where the digitization of education is already going on. Now lots of blogs, articles are there on the internet to learn from. But Book has its own value, the author puts his all knowledge experience and time to write one whole book. The knowledge and details you get from a book are very precious. Read Blog📖 Twitter💌 Voice Message🎙️ Buy Me a Coffee❤️ May 12, 2022 09:09 8 Lucrative Ways To Earn Money As A Writer No matter whether you're seeking extra pocket money or career advancement, writing for money is worth the effort. Here is a list of the eight best ways to make money by writing to help you maximize your skills. Read Blog📖 Twitter💌 Voice Message🎙️ Buy Me a Coffee❤️ Dec 30, 2021 03:48 25 Must-Visit Killer Websites For Developers 90% of developers don’t know about these websites. There are so many websites to make the work of developers easier. Everyone doesn't know all. In this podcast, we will see 25 Must-Visit Killer Websites For Developers. Read Blog📖 Twitter💌 Voice Message🎙️ Buy Me a Coffee❤️ Dec 07, 2021 07:02 Open Source Best Practices The open-source software industry is booming. Software developed by large corporations is built on open collaboration, thus enjoying the benefits of widespread adoption. In addition to bringing together many people from all over the world, free and open-source software brings people together by bringing their individual interests together. Read Blog📖 Twitter💌 Voice Message🎙️ Buy Me a Coffee❤️ Nov 20, 2021 05:18 10 Bad Coding Habits You Need to Put an End to Right Now Everyone isn’t perfect, and it’s the most honest of truths. It is the same with programmers as with any other field in life. There are a lot of good, great, and still-growing-up programmers, but they are often not the best. We all make mistakes and everyone is human. Apart from faults, bad habits can also cause a lot of trouble. These bad habits may seem innocent at first glance, but if not corrected, can cause a lot of problems. Read Blog📖 Twitter💌 Voice Message🎙️ Buy Me a Coffee❤️ Nov 12, 2021 04:56 Are You A Coder? Here Are 20 Top Tips From The Coding Community Learning to code is an amazing thing. How you can code something interesting and then view its fascinating outcomes. But Doing it in the right way is also very important. I am going to share 20 Top Tips From The Coding Community Read Blog📖 Twitter💌 Voice Message🎙️ Buy Me a Coffee❤️ Nov 10, 2021 07:23 Introduction to Web Development Web development is basically the creation of website pages — either a single page or many pages. There are several aspects to it, including web design, web publishing, web programming, and database management. It is the creation of an application that works over the internet i.e. websites. The word Web Development is made up of two words, that is: Web: It refers to websites, web pages, or anything that works over the internet. Development: Building the application from scratch. Read Blog📖 Twitter💌 Voice Message🎙️ Buy Me a Coffee❤️ Nov 09, 2021 09:04 Top 10 Technology Trends of 2021 The 21st century has been a century of technological change. Several highly commercial and prevalent technologies during the early 2000s have entirely vanished, and new ones have taken their place. Many completely new technologies have also come up in 2021, especially in the arena of computer science and engineering. Read Blog📖 Twitter💌 Voice Message🎙️ Buy Me a Coffee❤️ Nov 07, 2021 10:56 7 Things You Should Know Before You Try Coding If you're considering learning to code, you might want a little guidance in order to eradicate any self-doubt you may have. In addition, you might simply want a few pointers to get you even more excited about coding. This is a list of 7 things you should know before starting to program. Read Blog📖 Twitter💌 Voice Message🎙️ Buy Me a Coffee❤️ Nov 06, 2021 03:15 Top 10 Git Commands Every Developer Should Know Git is an important part of daily programming (especially if you're working with a team) and is widely used in the software industry. Since there are many various commands you can use, mastering Git takes time. https://muthuannamalai.tech/top-10-git-commands-every-developer-should-know. Read Blog📖 Twitter💌 Voice Message🎙️ Buy Me a Coffee❤️ Oct 26, 2021 06:47 How To Contribute To Open-Source Projects As A Beginner It's important to understand that contributing to open source projects is not all about coding you can contribute in other ways such as improving the documentation, organizing the project, designing stuff reviewing code, and so on. Read Blog📖 Twitter💌 Voice Message🎙️ Buy Me a Coffee❤️ Oct 14, 2021 06:56 Everything you need to know about Hackathons Hackathon is a word creation of the words hack(-ing) and marathon. In this context, hacking stands for the development of software- or hardware solution and the marathon describes the format, which is a 1–3 days lasting event. Usually, it takes place in a spacious venue, which fits sometimes several hundred hackers. Read Blog📖 Twitter💌 Voice Message🎙️ Buy Me a Coffee❤️ Oct 06, 2021 07:24 Cryptocurrency: The Future Cryptocurrency, the most famous currency in recent times, can be referred to as the future of transactions. Read blog: https://leap2live.wordpress.com/2021/05/29/cryptocurrency/ Sep 26, 2021 05:33 New World Of Unemployment: The Useless Class Since we all know that earlier, in past years, a society was divided into three classes upper class, middle class, and the lower class. But in these modern years, due to the increase in automation and artificial intelligence a new class will be introduced soon, which will be named “ The USELESS CLASS” . Read blog: https://leap2live.wordpress.com/2021/05/23/new-world-of-unemployment-the-useless-class/ Sep 16, 2021 01:50 Hustle Culture Hustle culture is all about constantly working. Those who believe in hustle culture try to devote as many hours as possible to working or hustling. Hustling is important but taking care of yourself is even more important. Read blog: https://leap2live.wordpress.com/2021/05/22/hustle-culture/ Sep 07, 2021 03:07 The Keyboard Warrior: Irfan Hafiz Nobody can defeat you if you are enough capable to face your problems. Today I am going to talk about an undefeatable person, the most courageous person in the entire world, a person who can definitely give you some courage and can change the meaning of disability for you. Yes, I am talking about the undefeatable man Irfan, from a small country Sri Lanka. Read Blog: https://ravimehta95112.medium.com/the-keyboard-warrior-irfan-hafiz-dcf4cc19126d Sep 06, 2021 02:22 What is Open Source Open source is a term that originally referred to open source software (OSS). Open source software is code that is designed to be publicly accessible—anyone can see, modify, and distribute the code as they see fit. Aug 22, 2021 02:23 The Invite-Only chat App: Clubhouse Clubhouse was launched back in April 2020 as an iOS app. It is a new social media platform based on audio. Jul 17, 2021 03:18 New update of Battlegrounds Mobile India Upcoming Update of BATTLEGROUNDS MOBILE INDIA: Update 1.5 of PUBG Mobile (Global). Jul 13, 2021 03:50 Filter Apps for yourself as Student Developer Having useful apps in phones is very important now-a-days. And as a student you must use apps useful for you. In this new world of technology, there are various apps coming time to time to ease the life and work of peoples. As a student, you must have to use some apps that helps in your study, learning and creating contents. Jul 10, 2021 03:06 © 2026 Spotify AB Careers Legal Help App Store Google Play | 2026-01-13T08:48:42 |
https://dev.to/szabgab/perl-weekly-602-rip-ben-davies-lbl | Perl Weekly #602 - RIP Ben Davies - 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 Gabor Szabo Posted on Feb 6, 2023 • Originally published at perlweekly.com Perl Weekly #602 - RIP Ben Davies # perl # news # programming perl-weekly (153 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 149 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution Originally published at Perl Weekly 602 Hi there, I got the sad news about Ben Davies through the git notifications, being member Raku github repositories. Although I didn't know him personally but I felt a personal loss. He was so young and actively involved in development of Raku language. I found this page sharing the details, if you are interested. It reminded of loss another very dear friend of mine, Jeff Goff (aka DrForr) . I had the honour to meet him at various Perl/Raku conferences. Life is so unpredictable, it is unbelievable. I have reached a point in my life where every little things create havoc as far as health is concerned. Talking about heartbroken news, I would like to bring the subject raised by Gabor Szabo in the last edition of the weekly newsletter . At times, I wonder how can one be so disrespectful to others. I was really sad to hear what Gabor had to go through. Honestly speaking, I only came to know about Antisemitism when I moved to England in 2000. During my college days, I never had interest in subject outside of domain of India. Although I was aware of love/hate relationship between Muslims and Jews, I never bothered looking into the history behind it. Muslim community in general in India is more sympathetic towards fellow muslims. Some may find, my relationship with Gabor strange. Again, I must confess that I wasn't aware about Gabor background when I first met him when he took my interview in 2016 . I only found out later about him being a Jewish when I had further interactions with him with regard to CPAN works. He has been my mentor ever since I first met him and has helped me every time I was in trouble. For me, religion is very personal thing and I like to keep it private. Having said, I don't hide the fact that I am a practicing Muslim. I urge everyone, please be kind to each other and spread love. Life is too short, so enjoy every moment of it. Enjoy the rest of the newsletter. -- Your editor: Mohammad S. Anwar. Announcements New Dancer, Dancer2 plus Ecosystem Updates Welcome to 2023 (just a little bit late)! We've put together a number of long overdue updates for Dancer, Dancer2, and other parts of the ecosystem. This Week in PSC (096) Another quick updates from Perl Steering Council. United-domains supports the German Perl/Raku-Workshop United-domains now sponsor for German Perl/Raku workshop. Articles Color Evolution The most requested feature of the Cellgraph is now in operation: Colors. Add a base URL to xlinx I used... Raku Why use Raku? Nice answer. CPAN Annotated Test2::Tools Index Interesting use case with regard to skip test inside for-loop. Highly recommended. Data::Resolver - some docs The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 203 Welcome to a new week with a couple of fun tasks: "Special Quadruplets" and "Copy Directory". If you are new to the weekly challenge, why not join us and have fun every week? For more information, please read the FAQ . RECAP - The Weekly Challenge - 202 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Consecutive Odds" and "Widest Valley" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Into the Odd Wide Valley Good to see the use of Perl v5.36, thanks for spreading the knowledge. Odd Valleys Not just one but multiple versions presented by Arne with detailed comments. Keep it up great work. How Wide is My Valley? Task analysis by Colin is always the highlight of the week. Really enjoyed itm thanks for sharing. Challenge Accepted Solutions without any complicated logic, using just for-loops. Incredible, well done. Weekly Challenge 202 Easy to follow Perl solutions. Keep it up, great work. PWC202 - Consecutive Odds Interesting questions raised and cool solutions too in the end. Well done. PWC202 - Widest Valley Loved the story behind the solution. The process of getting there is always fun. Great work, keep it up. Perl Weekly Challenge: Week 202 Unique style of code with inline comment really helps understand the flow. Great work. The Weekly Challenge 202 Compact yet power packed solutions as always. Thanks for sharing the knowledge with us. Perl Weekly Challenge 202: Consecutive Odds and Widest Valley Great demo of porting Raku solutions into Perl. I find it helpful to understand the code better. Well done. nested loops everywhere! We not have Raku magic but also SQL solutions. Highly recommend. Three odd things in the valleys Cool one-liner in Perl and interesting task analysis. Great work. The Weekly Challenge #202 Use of finite state mmachine to solve the Widest Valley task is interesting. Well done. Consecutive Valley Roger choosen Raku and Rust this week to talk about in the blog post. Highly recommended if you Raku/Rust fan. Weekly Challenge 202 Simon gone into the finer details this week, you don't want to miss it. Well done. Rakudo 2023.05 RB Awarded Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . Perl Jobs by Perl Careers Perl to Node Cross-training? Yes Please! UK Remote Perl Role The client is interested in anyone with experience building web apps in Perl, using one of the major Perl frameworks. If you’re a crack-hand with Catalyst, a Mojolicious master, or a distinguished Dancer, they want you. You’ll be deploying apps your work to AWS, so experience would be handy, and the company’s big on testing, so they’d like you to know your way around Test::More. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe. UK Remote Perl Role A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. Bold, beautiful, and… brainy? Senior Perl roles in Malaysia, Dubai and Malta With all the knowledge in your big, beautiful brain, it’s time to join a company that appreciates your breadth of experience. Our client provides online trading services and with offices in Dubai, Malta, and Malaysia, they’ve got the global reach that may provide the challenge you’re looking for. A seasoned Perl pro is just what their team needs as they expand, and that’s where you come in! You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (153 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 149 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming Perl 🐪 Weekly #752 - Marlin - OOP Framework # perl # news # programming 💎 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:48:42 |
https://survivejs.com/blog/state-ref-interview/ | state-ref - Easy to integrate state management library - Interview with Kim Jinwoo Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Can you tell a bit about yourself? How would you describe state-ref to someone who has never heard of it? How does state-ref work? How does state-ref differ from other solutions? Why did you develop state-ref? What next? What does the future look like for state-ref and web development in general? Can you see any particular trends? What advice would you give to programmers getting into web development? Who should I interview next? Any last remarks? Conclusion Can you tell a bit about yourself? How would you describe state-ref to someone who has never heard of it? How does state-ref work? How does state-ref differ from other solutions? Why did you develop state-ref? What next? What does the future look like for state-ref and web development in general? Can you see any particular trends? What advice would you give to programmers getting into web development? Who should I interview next? Any last remarks? Conclusion Loading... state-ref - Easy to integrate state management library - Interview with Kim Jinwoo Author: Juho Vepsäläinen Topics Interview JavaScript State management Published: 18.10.2024 State management is one of those recurring themes in frontend development. State becomes an issue when you try to build something even a little complex. This time I’m interviewing Kim Jinwoo ↗ about state-ref , his technology agnostic solution to the problem. Can you tell a bit about yourself? # Hello, I am Kim Jinwoo, an ordinary web developer living in Korea. I work as a programmer. I enjoy coding outside of work like it’s a game. It’s a bit embarrassing, but I believe I have strong expertise in web development, and I have a very high self-esteem as a developer. :) I’m not sure if I’m doing well, but since I was born a programmer, I have a dream to contribute to the world in some way with good ideas or code. I don’t know how much time I have left, but as long as I can live as a programmer, I want to create something even more amazing. It’s not easy. How would you describe state-ref to someone who has never heard of it? # state-ref is a state management system based on the Observer pattern ↗ . It was designed with easy integration with popular UI libraries in mind. state-ref implements the Observer pattern for you. As developers, you may already have a good understanding of this pattern, but grasping it makes it clear how programs manage state and how code that depends on that state automatically reflects the new state. state-ref simplifies the Observer pattern and transforms it into an API that can be easily accessed and utilized in various situations. While state-ref was created with the intention of being easily used alongside many different UI libraries (such as React, Preact, Vue, Svelte, and SolidJS), it does not have dependencies on any specific library and can be used independently as well. How does state-ref work? # state-ref was designed with a focus on data immutability to determine value changes. It tracks when users directly read values from the store and adds those references to the dependency callbacks. The pattern for remembering or locating references uses the lenses pattern from functional programming, allowing for accurate identification of reference locations. When users attempt to change values, they do so according to the interface I have designed, and within state-ref , values are safely modified using a memory management technique called copyOnWrite ↗ . Due to the characteristics of the copyOnWrite technique, state-ref accurately determines which references are affected by the changed value, finds the corresponding dependent callbacks, and executes them. How does state-ref differ from other solutions? # Compared to other solutions, the way of accessing and modifying values is much easier and more intuitive. For example, in other solutions, when dealing with objects or arrays that have nested sub-nodes, users have to manually handle the copyOnWrite process, which can be inconvenient. In contrast, state-ref automatically handles copyOnWrite , making it more user-friendly. Additionally, other solutions are often created for specific UI libraries, meaning they are tied to the lifecycle of those libraries. However, state-ref has no dependencies on any specific UI libraries, allowing for greater flexibility in modifications and extensions. Why did you develop state-ref ? # I felt that most JavaScript state management libraries are too tightly coupled with specific UI libraries. For instance, I have been alternating between React and Preact in my project, and I wanted to use a state management library called Zustand ↗ with Preact. However, since Zustand does not officially support Preact, I ended up not being able to use it and gave up. Backend frameworks tend to provide interfaces that generalize connections with similar external modules, allowing for easy dependency swapping. In contrast, most frontend libraries offer weak support for this. Initially, my idea was to create a connector that would easily link a normal state management library with UI libraries while keeping the coupling as low as possible. However, I thought it would be fun also to create a state management library while I was at it, which led me to start the state-ref project. What next? # I don’t consider state-ref to be a particularly complex library. Also, since it started as a personal hobby project, I don’t expect to attract a large number of users. However, if a few users show interest in this library, I plan to provide them with detailed documentation and tutorials. Currently, state-ref supports connectors for Vue, Preact, React, Svelte, and Solid. I also plan to implement connectors for many other UI libraries. What does the future look like for state-ref and web development in general? Can you see any particular trends? # Currently, frameworks like Next.js for React, Nuxt for Vue, and SvelteKit for Svelte, along with state management libraries like Recoil, Vuex, and Svelte/store, are tightly integrated through strong coupling. However, personally, I hope that in the future, these libraries, frameworks, and state management solutions will have lower coupling with various modules, allowing for more flexible integration and easier replacement. In this context, I expect state-ref to become an exemplary case that inspires many. What advice would you give to programmers getting into web development? # I, too, experienced this, but many people start coding with the pure curiosity and fun of a child. However, when coding becomes a profession, that joy often fades, and curiosity tends to diminish. Don’t lose the curiosity you had in the beginning, and try various things. If you have even a small idea, make sure to realize it and share it with those around you, even if it’s not directly related to programming. The ideas you come up with are not trivial or personal; they might be messages from a higher power urging you to contribute to the world, even if just a little. Thinking this way adds meaning to life. I only recently realized this, and it took me a long time. In my case, by thinking this way, I’ve found new joy in coding and significantly improved my skills (though I still have a long way to go). Who should I interview next? # I recommend an interview with Tao Xin, the creator of VanJS ↗ . While I don’t know him personally, I’ve always admired his passion for developing VanJS with good intentions and ideas. I believe he is a great developer who can inspire many people. Any last remarks? # state-ref is simply a project I created as a hobby. However, I have poured a lot of passion into it, so I take great pride in it. I would like to express my heartfelt gratitude once again to Juho for showing interest in my project and suggesting this interview. Conclusion # Thank you for the interview Kim! I think it is great to see innovation in the space and the fundamental ideas behind state-ref seem solid to me. Especially the fact that you separated state management from a specific UI library seems like a smart move to me. You can learn more about state-ref on GitHub. ↗ Author: Juho Vepsäläinen Topics Interview JavaScript State management Published: 18.10.2024 ← Previous KaibanJS - Open-source framework for building multi-agent AI systems - Interview with Dariel Vila Next → Impressions on Web Summit 2024 ← Previous KaibanJS - Open-source framework for building multi-agent AI systems - Interview with Dariel Vila Next → Impressions on Web Summit 2024 Comments # Show comments Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:42 |
https://docs.suprsend.com/docs/react-native-send-event-data | Sync Events - 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 Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK SuprSend Client SDK Authentication Javascript Android iOS React Native Android Integration iOS Integration Manage Users Sync Events iOS Push Setup Android Push (FCM) Flutter React Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation React Native Sync Events Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog React Native Sync Events OpenAI Open in ChatGPT Methods for sending events from your react native app to the SuprSend platform to trigger workflows. OpenAI Open in ChatGPT In this section, we’ll cover how to send events to the Suprsend platform for both iOS and Android application Pre-Requisites Create User - Mandatory to pass in event trigger Sending Events to SuprSend You can setup events on user actions in your app and configure workflows on top of it that triggers when the corresponding event is passed through App. Variables added in the template or workflow should be passed as event properties You can send Events from your app to SuprSend platform by using suprsend.track() method. javascript Copy Ask AI suprsend . track ( event_name , properties ); suprsend . track ( "grocery_purchased" , { "item" : "olive oil" , "amount" : "$12" }); Event Name or Property Name should not start with $ or ss_ . These keywords are reserved for internal events and property names. System Events tracked by SuprSend There are some system events tracked by SuprSend SDK by default. These are some basic events, as well as events that are necessary for tracking notifications related activity (like delivered, clicked, etc). You are not required to do anything here. Event Name Description $app_installed $app_installed will get tracked when user launch his app for the first time. FYI cases in which it will also get called 1. When user launches his app for first time. 2. When user uninstall the app and installs it again. 3. [Multiple device login ]When user launch app for first time on different devices. 4. When user clears the app cache and relaunches the app. $app_launched Gets tracked when user launches the app each time. $user_login Gets tracked when user logs in inside the app $user_logout Gets tracked when user logs in to the app $notification_delivered Will get tracked when the suprsend notification payload is received at SDK end. $notification_clicked Will get tracked when user either clicks the notification body or any action button in the notification. $notification_dismissed Will get tracked when user dismisses the notification by left swiping the notification or by clicking on “Clear All” button Advanced concepts 1. Super Properties Super Properties are data that are always sent with events data. These super properties will be sent in each event after calling this method. Super Properties will be stored in local storage, and will persist across invocations of app. Set Super Property There are some super properties that SuprSend SDK will send by default. Developer can set custom super properties as well with suprsend.setSuperProperties() method javascript Copy Ask AI //method suprsend . setSuperProperties ( key , value ); suprsend . setSuperProperties ( property_obj ); //Example suprsend . setSuperProperties ( "Location" , "Banglore" ); suprsend . setSuperProperties ({ "Location" : "Banglore" , "Pincode" : 1234567 }); Default Super Properties tracked by SuprSend SDK: Super Property Description Sample Value $app_version_string Version of your app 0.0.1 $app_build_number Build number of your app 2 $os Operating system of the user android $manufacturer Manufacturer of the user’s device OnePlus $brand Brand of the user’s device OnePlus $model Model of the user’s device GM1901 $deviceId Device id 89eead05a0150146 $ss_sdk_version SuprSend SDK version 0.1.31 $network Network on which the user is wifi $connected Whether the user is connected to the network true Unset Super Property There are unset custom super properties with suprsend.unSetSuperProperty() method. This method will stop calling that property with every event trigger. javascript Copy Ask AI suprsend . unSetSuperProperty ( key ); suprsend . unSetSuperProperty ( "Location" ); 2. Flush Events SuprSend SDK automatically flushes events at an interval of 5 seconds, and on certain activities like app relaunch, etc. If you wish to flush a time sensitive event to SuprSend immediately, you can use the suprSendApi.flush() method. All the system tracked events are flushed immediately javascript Copy Ask AI suprSendApi . flush (); Was this page helpful? Yes No Suggest edits Raise issue Previous iOS Push Setup Step-by-step guide to setup APNS iOSpush notifications in your react native app. Next ⌘ I x github linkedin youtube Powered by On this page Pre-Requisites Sending Events to SuprSend System Events tracked by SuprSend Advanced concepts 1. Super Properties 2. Flush Events | 2026-01-13T08:48:42 |
https://docs.suprsend.com/reference/cli-schema-push | Push Schemas - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Schema Push Schemas Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Schema Push Schemas OpenAI Open in ChatGPT Upload schema files from your local directory or server to SuprSend workspace. OpenAI Open in ChatGPT This command reads and validates schema files locally before pushing them to the target workspace, where they are created in draft mode. To commit schemas while pushing, include the --commit=true flag. Any schema that fails validation will be skipped and not pushed to the workspace. Syntax Copy Ask AI suprsend schema push [flags] Options Flag Description Default -h, --help Show help for the command – -c, --commit string Commit the schemas (—commit=true) true -m, --commit-message string Commit message describing the changes for —commit=true – -d, --dir string Directory for schemas pull to suprsend/schema -g, --slug string Slug of schema to push – Example Copy Ask AI # Push schemas to staging workspace (default) suprsend schema push # Push schemas to production workspace suprsend schema push --workspace production # Push individual schema by passing it's slug suprsend schema push --slug my-schema # Push schemas and commit them suprsend schema push --commit=true --commit-message "Commit message" 🚨 Push and Commit Behavior : Schemas not showing up in live mode? → Check if they’re linked to workflows Fix : Update your workflow files to include the new schemas, or remove the workflow links Was this page helpful? Yes No Suggest edits Raise issue Previous Commit Schema Make schema changes live in a SuprSend workspace. Next ⌘ I x github linkedin youtube Powered by On this page Syntax Options Example | 2026-01-13T08:48:42 |
https://docs.python.org/3/library/functions.html#len | Built-in Functions — Python 3.14.2 documentation Theme Auto Light Dark Previous topic Introduction Next topic Built-in Constants This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Standard Library » Built-in Functions | Theme Auto Light Dark | Built-in Functions ¶ The Python interpreter has a number of functions and types built into it that are always available. They are listed here in alphabetical order. Built-in Functions A abs() aiter() all() anext() any() ascii() B bin() bool() breakpoint() bytearray() bytes() C callable() chr() classmethod() compile() complex() D delattr() dict() dir() divmod() E enumerate() eval() exec() F filter() float() format() frozenset() G getattr() globals() H hasattr() hash() help() hex() I id() input() int() isinstance() issubclass() iter() L len() list() locals() M map() max() memoryview() min() N next() O object() oct() open() ord() P pow() print() property() R range() repr() reversed() round() S set() setattr() slice() sorted() staticmethod() str() sum() super() T tuple() type() V vars() Z zip() _ __import__() abs ( number , / ) ¶ Return the absolute value of a number. The argument may be an integer, a floating-point number, or an object implementing __abs__() . If the argument is a complex number, its magnitude is returned. aiter ( async_iterable , / ) ¶ Return an asynchronous iterator for an asynchronous iterable . Equivalent to calling x.__aiter__() . Note: Unlike iter() , aiter() has no 2-argument variant. Added in version 3.10. all ( iterable , / ) ¶ Return True if all elements of the iterable are true (or if the iterable is empty). Equivalent to: def all ( iterable ): for element in iterable : if not element : return False return True awaitable anext ( async_iterator , / ) ¶ awaitable anext ( async_iterator , default , / ) When awaited, return the next item from the given asynchronous iterator , or default if given and the iterator is exhausted. This is the async variant of the next() builtin, and behaves similarly. This calls the __anext__() method of async_iterator , returning an awaitable . Awaiting this returns the next value of the iterator. If default is given, it is returned if the iterator is exhausted, otherwise StopAsyncIteration is raised. Added in version 3.10. any ( iterable , / ) ¶ Return True if any element of the iterable is true. If the iterable is empty, return False . Equivalent to: def any ( iterable ): for element in iterable : if element : return True return False ascii ( object , / ) ¶ As repr() , return a string containing a printable representation of an object, but escape the non-ASCII characters in the string returned by repr() using \x , \u , or \U escapes. This generates a string similar to that returned by repr() in Python 2. bin ( integer , / ) ¶ Convert an integer number to a binary string prefixed with “0b”. The result is a valid Python expression. If integer is not a Python int object, it has to define an __index__() method that returns an integer. Some examples: >>> bin ( 3 ) '0b11' >>> bin ( - 10 ) '-0b1010' If the prefix “0b” is desired or not, you can use either of the following ways. >>> format ( 14 , '#b' ), format ( 14 , 'b' ) ('0b1110', '1110') >>> f ' { 14 : #b } ' , f ' { 14 : b } ' ('0b1110', '1110') See also enum.bin() to represent negative values as twos-complement. See also format() for more information. class bool ( object = False , / ) ¶ Return a Boolean value, i.e. one of True or False . The argument is converted using the standard truth testing procedure . If the argument is false or omitted, this returns False ; otherwise, it returns True . The bool class is a subclass of int (see Numeric Types — int, float, complex ). It cannot be subclassed further. Its only instances are False and True (see Boolean Type - bool ). Changed in version 3.7: The parameter is now positional-only. breakpoint ( * args , ** kws ) ¶ This function drops you into the debugger at the call site. Specifically, it calls sys.breakpointhook() , passing args and kws straight through. By default, sys.breakpointhook() calls pdb.set_trace() expecting no arguments. In this case, it is purely a convenience function so you don’t have to explicitly import pdb or type as much code to enter the debugger. However, sys.breakpointhook() can be set to some other function and breakpoint() will automatically call that, allowing you to drop into the debugger of choice. If sys.breakpointhook() is not accessible, this function will raise RuntimeError . By default, the behavior of breakpoint() can be changed with the PYTHONBREAKPOINT environment variable. See sys.breakpointhook() for usage details. Note that this is not guaranteed if sys.breakpointhook() has been replaced. Raises an auditing event builtins.breakpoint with argument breakpointhook . Added in version 3.7. class bytearray ( source = b'' ) class bytearray ( source , encoding , errors = 'strict' ) Return a new array of bytes. The bytearray class is a mutable sequence of integers in the range 0 <= x < 256. It has most of the usual methods of mutable sequences, described in Mutable Sequence Types , as well as most methods that the bytes type has, see Bytes and Bytearray Operations . The optional source parameter can be used to initialize the array in a few different ways: If it is a string , you must also give the encoding (and optionally, errors ) parameters; bytearray() then converts the string to bytes using str.encode() . If it is an integer , the array will have that size and will be initialized with null bytes. If it is an object conforming to the buffer interface , a read-only buffer of the object will be used to initialize the bytes array. If it is an iterable , it must be an iterable of integers in the range 0 <= x < 256 , which are used as the initial contents of the array. Without an argument, an array of size 0 is created. See also Binary Sequence Types — bytes, bytearray, memoryview and Bytearray Objects . class bytes ( source = b'' ) class bytes ( source , encoding , errors = 'strict' ) Return a new “bytes” object which is an immutable sequence of integers in the range 0 <= x < 256 . bytes is an immutable version of bytearray – it has the same non-mutating methods and the same indexing and slicing behavior. Accordingly, constructor arguments are interpreted as for bytearray() . Bytes objects can also be created with literals, see String and Bytes literals . See also Binary Sequence Types — bytes, bytearray, memoryview , Bytes Objects , and Bytes and Bytearray Operations . callable ( object , / ) ¶ Return True if the object argument appears callable, False if not. If this returns True , it is still possible that a call fails, but if it is False , calling object will never succeed. Note that classes are callable (calling a class returns a new instance); instances are callable if their class has a __call__() method. Added in version 3.2: This function was first removed in Python 3.0 and then brought back in Python 3.2. chr ( codepoint , / ) ¶ Return the string representing a character with the specified Unicode code point. For example, chr(97) returns the string 'a' , while chr(8364) returns the string '€' . This is the inverse of ord() . The valid range for the argument is from 0 through 1,114,111 (0x10FFFF in base 16). ValueError will be raised if it is outside that range. @ classmethod ¶ Transform a method into a class method. A class method receives the class as an implicit first argument, just like an instance method receives the instance. To declare a class method, use this idiom: class C : @classmethod def f ( cls , arg1 , arg2 ): ... The @classmethod form is a function decorator – see Function definitions for details. A class method can be called either on the class (such as C.f() ) or on an instance (such as C().f() ). The instance is ignored except for its class. If a class method is called for a derived class, the derived class object is passed as the implied first argument. Class methods are different than C++ or Java static methods. If you want those, see staticmethod() in this section. For more information on class methods, see The standard type hierarchy . Changed in version 3.9: Class methods can now wrap other descriptors such as property() . Changed in version 3.10: Class methods now inherit the method attributes ( __module__ , __name__ , __qualname__ , __doc__ and __annotations__ ) and have a new __wrapped__ attribute. Deprecated since version 3.11, removed in version 3.13: Class methods can no longer wrap other descriptors such as property() . compile ( source , filename , mode , flags = 0 , dont_inherit = False , optimize = -1 ) ¶ Compile the source into a code or AST object. Code objects can be executed by exec() or eval() . source can either be a normal string, a byte string, or an AST object. Refer to the ast module documentation for information on how to work with AST objects. The filename argument should give the file from which the code was read; pass some recognizable value if it wasn’t read from a file ( '<string>' is commonly used). The mode argument specifies what kind of code must be compiled; it can be 'exec' if source consists of a sequence of statements, 'eval' if it consists of a single expression, or 'single' if it consists of a single interactive statement (in the latter case, expression statements that evaluate to something other than None will be printed). The optional arguments flags and dont_inherit control which compiler options should be activated and which future features should be allowed. If neither is present (or both are zero) the code is compiled with the same flags that affect the code that is calling compile() . If the flags argument is given and dont_inherit is not (or is zero) then the compiler options and the future statements specified by the flags argument are used in addition to those that would be used anyway. If dont_inherit is a non-zero integer then the flags argument is it – the flags (future features and compiler options) in the surrounding code are ignored. Compiler options and future statements are specified by bits which can be bitwise ORed together to specify multiple options. The bitfield required to specify a given future feature can be found as the compiler_flag attribute on the _Feature instance in the __future__ module. Compiler flags can be found in ast module, with PyCF_ prefix. The argument optimize specifies the optimization level of the compiler; the default value of -1 selects the optimization level of the interpreter as given by -O options. Explicit levels are 0 (no optimization; __debug__ is true), 1 (asserts are removed, __debug__ is false) or 2 (docstrings are removed too). This function raises SyntaxError or ValueError if the compiled source is invalid. If you want to parse Python code into its AST representation, see ast.parse() . Raises an auditing event compile with arguments source and filename . This event may also be raised by implicit compilation. Note When compiling a string with multi-line code in 'single' or 'eval' mode, input must be terminated by at least one newline character. This is to facilitate detection of incomplete and complete statements in the code module. Warning It is possible to crash the Python interpreter with a sufficiently large/complex string when compiling to an AST object due to stack depth limitations in Python’s AST compiler. Changed in version 3.2: Allowed use of Windows and Mac newlines. Also, input in 'exec' mode does not have to end in a newline anymore. Added the optimize parameter. Changed in version 3.5: Previously, TypeError was raised when null bytes were encountered in source . Added in version 3.8: ast.PyCF_ALLOW_TOP_LEVEL_AWAIT can now be passed in flags to enable support for top-level await , async for , and async with . class complex ( number = 0 , / ) ¶ class complex ( string , / ) class complex ( real = 0 , imag = 0 ) Convert a single string or number to a complex number, or create a complex number from real and imaginary parts. Examples: >>> complex ( '+1.23' ) (1.23+0j) >>> complex ( '-4.5j' ) -4.5j >>> complex ( '-1.23+4.5j' ) (-1.23+4.5j) >>> complex ( ' \t ( -1.23+4.5J ) \n ' ) (-1.23+4.5j) >>> complex ( '-Infinity+NaNj' ) (-inf+nanj) >>> complex ( 1.23 ) (1.23+0j) >>> complex ( imag =- 4.5 ) -4.5j >>> complex ( - 1.23 , 4.5 ) (-1.23+4.5j) If the argument is a string, it must contain either a real part (in the same format as for float() ) or an imaginary part (in the same format but with a 'j' or 'J' suffix), or both real and imaginary parts (the sign of the imaginary part is mandatory in this case). The string can optionally be surrounded by whitespaces and the round parentheses '(' and ')' , which are ignored. The string must not contain whitespace between '+' , '-' , the 'j' or 'J' suffix, and the decimal number. For example, complex('1+2j') is fine, but complex('1 + 2j') raises ValueError . More precisely, the input must conform to the complexvalue production rule in the following grammar, after parentheses and leading and trailing whitespace characters are removed: complexvalue : floatvalue | floatvalue ( "j" | "J" ) | floatvalue sign absfloatvalue ( "j" | "J" ) If the argument is a number, the constructor serves as a numeric conversion like int and float . For a general Python object x , complex(x) delegates to x.__complex__() . If __complex__() is not defined then it falls back to __float__() . If __float__() is not defined then it falls back to __index__() . If two arguments are provided or keyword arguments are used, each argument may be any numeric type (including complex). If both arguments are real numbers, return a complex number with the real component real and the imaginary component imag . If both arguments are complex numbers, return a complex number with the real component real.real-imag.imag and the imaginary component real.imag+imag.real . If one of arguments is a real number, only its real component is used in the above expressions. See also complex.from_number() which only accepts a single numeric argument. If all arguments are omitted, returns 0j . The complex type is described in Numeric Types — int, float, complex . Changed in version 3.6: Grouping digits with underscores as in code literals is allowed. Changed in version 3.8: Falls back to __index__() if __complex__() and __float__() are not defined. Deprecated since version 3.14: Passing a complex number as the real or imag argument is now deprecated; it should only be passed as a single positional argument. delattr ( object , name , / ) ¶ This is a relative of setattr() . The arguments are an object and a string. The string must be the name of one of the object’s attributes. The function deletes the named attribute, provided the object allows it. For example, delattr(x, 'foobar') is equivalent to del x.foobar . name need not be a Python identifier (see setattr() ). class dict ( ** kwargs ) class dict ( mapping , / , ** kwargs ) class dict ( iterable , / , ** kwargs ) Create a new dictionary. The dict object is the dictionary class. See dict and Mapping Types — dict for documentation about this class. For other containers see the built-in list , set , and tuple classes, as well as the collections module. dir ( ) ¶ dir ( object , / ) Without arguments, return the list of names in the current local scope. With an argument, attempt to return a list of valid attributes for that object. If the object has a method named __dir__() , this method will be called and must return the list of attributes. This allows objects that implement a custom __getattr__() or __getattribute__() function to customize the way dir() reports their attributes. If the object does not provide __dir__() , the function tries its best to gather information from the object’s __dict__ attribute, if defined, and from its type object. The resulting list is not necessarily complete and may be inaccurate when the object has a custom __getattr__() . The default dir() mechanism behaves differently with different types of objects, as it attempts to produce the most relevant, rather than complete, information: If the object is a module object, the list contains the names of the module’s attributes. If the object is a type or class object, the list contains the names of its attributes, and recursively of the attributes of its bases. Otherwise, the list contains the object’s attributes’ names, the names of its class’s attributes, and recursively of the attributes of its class’s base classes. The resulting list is sorted alphabetically. For example: >>> import struct >>> dir () # show the names in the module namespace ['__builtins__', '__name__', 'struct'] >>> dir ( struct ) # show the names in the struct module ['Struct', '__all__', '__builtins__', '__cached__', '__doc__', '__file__', '__initializing__', '__loader__', '__name__', '__package__', '_clearcache', 'calcsize', 'error', 'pack', 'pack_into', 'unpack', 'unpack_from'] >>> class Shape : ... def __dir__ ( self ): ... return [ 'area' , 'perimeter' , 'location' ] ... >>> s = Shape () >>> dir ( s ) ['area', 'location', 'perimeter'] Note Because dir() is supplied primarily as a convenience for use at an interactive prompt, it tries to supply an interesting set of names more than it tries to supply a rigorously or consistently defined set of names, and its detailed behavior may change across releases. For example, metaclass attributes are not in the result list when the argument is a class. divmod ( a , b , / ) ¶ Take two (non-complex) numbers as arguments and return a pair of numbers consisting of their quotient and remainder when using integer division. With mixed operand types, the rules for binary arithmetic operators apply. For integers, the result is the same as (a // b, a % b) . For floating-point numbers the result is (q, a % b) , where q is usually math.floor(a / b) but may be 1 less than that. In any case q * b + a % b is very close to a , if a % b is non-zero it has the same sign as b , and 0 <= abs(a % b) < abs(b) . enumerate ( iterable , start = 0 ) ¶ Return an enumerate object. iterable must be a sequence, an iterator , or some other object which supports iteration. The __next__() method of the iterator returned by enumerate() returns a tuple containing a count (from start which defaults to 0) and the values obtained from iterating over iterable . >>> seasons = [ 'Spring' , 'Summer' , 'Fall' , 'Winter' ] >>> list ( enumerate ( seasons )) [(0, 'Spring'), (1, 'Summer'), (2, 'Fall'), (3, 'Winter')] >>> list ( enumerate ( seasons , start = 1 )) [(1, 'Spring'), (2, 'Summer'), (3, 'Fall'), (4, 'Winter')] Equivalent to: def enumerate ( iterable , start = 0 ): n = start for elem in iterable : yield n , elem n += 1 eval ( source , / , globals = None , locals = None ) ¶ Parameters : source ( str | code object ) – A Python expression. globals ( dict | None ) – The global namespace (default: None ). locals ( mapping | None ) – The local namespace (default: None ). Returns : The result of the evaluated expression. Raises : Syntax errors are reported as exceptions. Warning This function executes arbitrary code. Calling it with user-supplied input may lead to security vulnerabilities. The source argument is parsed and evaluated as a Python expression (technically speaking, a condition list) using the globals and locals mappings as global and local namespace. If the globals dictionary is present and does not contain a value for the key __builtins__ , a reference to the dictionary of the built-in module builtins is inserted under that key before source is parsed. That way you can control what builtins are available to the executed code by inserting your own __builtins__ dictionary into globals before passing it to eval() . If the locals mapping is omitted it defaults to the globals dictionary. If both mappings are omitted, the source is executed with the globals and locals in the environment where eval() is called. Note, eval() will only have access to the nested scopes (non-locals) in the enclosing environment if they are already referenced in the scope that is calling eval() (e.g. via a nonlocal statement). Example: >>> x = 1 >>> eval ( 'x+1' ) 2 This function can also be used to execute arbitrary code objects (such as those created by compile() ). In this case, pass a code object instead of a string. If the code object has been compiled with 'exec' as the mode argument, eval() 's return value will be None . Hints: dynamic execution of statements is supported by the exec() function. The globals() and locals() functions return the current global and local dictionary, respectively, which may be useful to pass around for use by eval() or exec() . If the given source is a string, then leading and trailing spaces and tabs are stripped. See ast.literal_eval() for a function that can safely evaluate strings with expressions containing only literals. Raises an auditing event exec with the code object as the argument. Code compilation events may also be raised. Changed in version 3.13: The globals and locals arguments can now be passed as keywords. Changed in version 3.13: The semantics of the default locals namespace have been adjusted as described for the locals() builtin. exec ( source , / , globals = None , locals = None , * , closure = None ) ¶ Warning This function executes arbitrary code. Calling it with user-supplied input may lead to security vulnerabilities. This function supports dynamic execution of Python code. source must be either a string or a code object. If it is a string, the string is parsed as a suite of Python statements which is then executed (unless a syntax error occurs). [ 1 ] If it is a code object, it is simply executed. In all cases, the code that’s executed is expected to be valid as file input (see the section File input in the Reference Manual). Be aware that the nonlocal , yield , and return statements may not be used outside of function definitions even within the context of code passed to the exec() function. The return value is None . In all cases, if the optional parts are omitted, the code is executed in the current scope. If only globals is provided, it must be a dictionary (and not a subclass of dictionary), which will be used for both the global and the local variables. If globals and locals are given, they are used for the global and local variables, respectively. If provided, locals can be any mapping object. Remember that at the module level, globals and locals are the same dictionary. Note When exec gets two separate objects as globals and locals , the code will be executed as if it were embedded in a class definition. This means functions and classes defined in the executed code will not be able to access variables assigned at the top level (as the “top level” variables are treated as class variables in a class definition). If the globals dictionary does not contain a value for the key __builtins__ , a reference to the dictionary of the built-in module builtins is inserted under that key. That way you can control what builtins are available to the executed code by inserting your own __builtins__ dictionary into globals before passing it to exec() . The closure argument specifies a closure–a tuple of cellvars. It’s only valid when the object is a code object containing free (closure) variables . The length of the tuple must exactly match the length of the code object’s co_freevars attribute. Raises an auditing event exec with the code object as the argument. Code compilation events may also be raised. Note The built-in functions globals() and locals() return the current global and local namespace, respectively, which may be useful to pass around for use as the second and third argument to exec() . Note The default locals act as described for function locals() below. Pass an explicit locals dictionary if you need to see effects of the code on locals after function exec() returns. Changed in version 3.11: Added the closure parameter. Changed in version 3.13: The globals and locals arguments can now be passed as keywords. Changed in version 3.13: The semantics of the default locals namespace have been adjusted as described for the locals() builtin. filter ( function , iterable , / ) ¶ Construct an iterator from those elements of iterable for which function is true. iterable may be either a sequence, a container which supports iteration, or an iterator. If function is None , the identity function is assumed, that is, all elements of iterable that are false are removed. Note that filter(function, iterable) is equivalent to the generator expression (item for item in iterable if function(item)) if function is not None and (item for item in iterable if item) if function is None . See itertools.filterfalse() for the complementary function that returns elements of iterable for which function is false. class float ( number = 0.0 , / ) ¶ class float ( string , / ) Return a floating-point number constructed from a number or a string. Examples: >>> float ( '+1.23' ) 1.23 >>> float ( ' -12345 \n ' ) -12345.0 >>> float ( '1e-003' ) 0.001 >>> float ( '+1E6' ) 1000000.0 >>> float ( '-Infinity' ) -inf If the argument is a string, it should contain a decimal number, optionally preceded by a sign, and optionally embedded in whitespace. The optional sign may be '+' or '-' ; a '+' sign has no effect on the value produced. The argument may also be a string representing a NaN (not-a-number), or positive or negative infinity. More precisely, the input must conform to the floatvalue production rule in the following grammar, after leading and trailing whitespace characters are removed: sign : "+" | "-" infinity : "Infinity" | "inf" nan : "nan" digit : <a Unicode decimal digit, i.e. characters in Unicode general category Nd> digitpart : digit ([ "_" ] digit )* number : [ digitpart ] "." digitpart | digitpart [ "." ] exponent : ( "e" | "E" ) [ sign ] digitpart floatnumber : number [ exponent ] absfloatvalue : floatnumber | infinity | nan floatvalue : [ sign ] absfloatvalue Case is not significant, so, for example, “inf”, “Inf”, “INFINITY”, and “iNfINity” are all acceptable spellings for positive infinity. Otherwise, if the argument is an integer or a floating-point number, a floating-point number with the same value (within Python’s floating-point precision) is returned. If the argument is outside the range of a Python float, an OverflowError will be raised. For a general Python object x , float(x) delegates to x.__float__() . If __float__() is not defined then it falls back to __index__() . See also float.from_number() which only accepts a numeric argument. If no argument is given, 0.0 is returned. The float type is described in Numeric Types — int, float, complex . Changed in version 3.6: Grouping digits with underscores as in code literals is allowed. Changed in version 3.7: The parameter is now positional-only. Changed in version 3.8: Falls back to __index__() if __float__() is not defined. format ( value , format_spec = '' , / ) ¶ Convert a value to a “formatted” representation, as controlled by format_spec . The interpretation of format_spec will depend on the type of the value argument; however, there is a standard formatting syntax that is used by most built-in types: Format Specification Mini-Language . The default format_spec is an empty string which usually gives the same effect as calling str(value) . A call to format(value, format_spec) is translated to type(value).__format__(value, format_spec) which bypasses the instance dictionary when searching for the value’s __format__() method. A TypeError exception is raised if the method search reaches object and the format_spec is non-empty, or if either the format_spec or the return value are not strings. Changed in version 3.4: object().__format__(format_spec) raises TypeError if format_spec is not an empty string. class frozenset ( iterable = () , / ) Return a new frozenset object, optionally with elements taken from iterable . frozenset is a built-in class. See frozenset and Set Types — set, frozenset for documentation about this class. For other containers see the built-in set , list , tuple , and dict classes, as well as the collections module. getattr ( object , name , / ) ¶ getattr ( object , name , default , / ) Return the value of the named attribute of object . name must be a string. If the string is the name of one of the object’s attributes, the result is the value of that attribute. For example, getattr(x, 'foobar') is equivalent to x.foobar . If the named attribute does not exist, default is returned if provided, otherwise AttributeError is raised. name need not be a Python identifier (see setattr() ). Note Since private name mangling happens at compilation time, one must manually mangle a private attribute’s (attributes with two leading underscores) name in order to retrieve it with getattr() . globals ( ) ¶ Return the dictionary implementing the current module namespace. For code within functions, this is set when the function is defined and remains the same regardless of where the function is called. hasattr ( object , name , / ) ¶ The arguments are an object and a string. The result is True if the string is the name of one of the object’s attributes, False if not. (This is implemented by calling getattr(object, name) and seeing whether it raises an AttributeError or not.) hash ( object , / ) ¶ Return the hash value of the object (if it has one). Hash values are integers. They are used to quickly compare dictionary keys during a dictionary lookup. Numeric values that compare equal have the same hash value (even if they are of different types, as is the case for 1 and 1.0). Note For objects with custom __hash__() methods, note that hash() truncates the return value based on the bit width of the host machine. help ( ) ¶ help ( request ) Invoke the built-in help system. (This function is intended for interactive use.) If no argument is given, the interactive help system starts on the interpreter console. If the argument is a string, then the string is looked up as the name of a module, function, class, method, keyword, or documentation topic, and a help page is printed on the console. If the argument is any other kind of object, a help page on the object is generated. Note that if a slash(/) appears in the parameter list of a function when invoking help() , it means that the parameters prior to the slash are positional-only. For more info, see the FAQ entry on positional-only parameters . This function is added to the built-in namespace by the site module. Changed in version 3.4: Changes to pydoc and inspect mean that the reported signatures for callables are now more comprehensive and consistent. hex ( integer , / ) ¶ Convert an integer number to a lowercase hexadecimal string prefixed with “0x”. If integer is not a Python int object, it has to define an __index__() method that returns an integer. Some examples: >>> hex ( 255 ) '0xff' >>> hex ( - 42 ) '-0x2a' If you want to convert an integer number to an uppercase or lower hexadecimal string with prefix or not, you can use either of the following ways: >>> ' %#x ' % 255 , ' %x ' % 255 , ' %X ' % 255 ('0xff', 'ff', 'FF') >>> format ( 255 , '#x' ), format ( 255 , 'x' ), format ( 255 , 'X' ) ('0xff', 'ff', 'FF') >>> f ' { 255 : #x } ' , f ' { 255 : x } ' , f ' { 255 : X } ' ('0xff', 'ff', 'FF') See also format() for more information. See also int() for converting a hexadecimal string to an integer using a base of 16. Note To obtain a hexadecimal string representation for a float, use the float.hex() method. id ( object , / ) ¶ Return the “identity” of an object. This is an integer which is guaranteed to be unique and constant for this object during its lifetime. Two objects with non-overlapping lifetimes may have the same id() value. CPython implementation detail: This is the address of the object in memory. Raises an auditing event builtins.id with argument id . input ( ) ¶ input ( prompt , / ) If the prompt argument is present, it is written to standard output without a trailing newline. The function then reads a line from input, converts it to a string (stripping a trailing newline), and returns that. When EOF is read, EOFError is raised. Example: >>> s = input ( '--> ' ) --> Monty Python's Flying Circus >>> s "Monty Python's Flying Circus" If the readline module was loaded, then input() will use it to provide elaborate line editing and history features. Raises an auditing event builtins.input with argument prompt before reading input Raises an auditing event builtins.input/result with the result after successfully reading input. class int ( number = 0 , / ) ¶ class int ( string , / , base = 10 ) Return an integer object constructed from a number or a string, or return 0 if no arguments are given. Examples: >>> int ( 123.45 ) 123 >>> int ( '123' ) 123 >>> int ( ' -12_345 \n ' ) -12345 >>> int ( 'FACE' , 16 ) 64206 >>> int ( '0xface' , 0 ) 64206 >>> int ( '01110011' , base = 2 ) 115 If the argument defines __int__() , int(x) returns x.__int__() . If the argument defines __index__() , it returns x.__index__() . For floating-point numbers, this truncates towards zero. If the argument is not a number or if base is given, then it must be a string, bytes , or bytearray instance representing an integer in radix base . Optionally, the string can be preceded by + or - (with no space in between), have leading zeros, be surrounded by whitespace, and have single underscores interspersed between digits. A base-n integer string contains digits, each representing a value from 0 to n-1. The values 0–9 can be represented by any Unicode decimal digit. The values 10–35 can be represented by a to z (or A to Z ). The default base is 10. The allowed bases are 0 and 2–36. Base-2, -8, and -16 strings can be optionally prefixed with 0b / 0B , 0o / 0O , or 0x / 0X , as with integer literals in code. For base 0, the string is interpreted in a similar way to an integer literal in code , in that the actual base is 2, 8, 10, or 16 as determined by the prefix. Base 0 also disallows leading zeros: int('010', 0) is not legal, while int('010') and int('010', 8) are. The integer type is described in Numeric Types — int, float, complex . Changed in version 3.4: If base is not an instance of int and the base object has a base.__index__ method, that method is called to obtain an integer for the base. Previous versions used base.__int__ instead of base.__index__ . Changed in version 3.6: Grouping digits with underscores as in code literals is allowed. Changed in version 3.7: The first parameter is now positional-only. Changed in version 3.8: Falls back to __index__() if __int__() is not defined. Changed in version 3.11: int string inputs and string representations can be limited to help avoid denial of service attacks. A ValueError is raised when the limit is exceeded while converting a string to an int or when converting an int into a string would exceed the limit. See the integer string conversion length limitation documentation. Changed in version 3.14: int() no longer delegates to the __trunc__() method. isinstance ( object , classinfo , / ) ¶ Return True if the object argument is an instance of the classinfo argument, or of a (direct, indirect, or virtual ) subclass thereof. If object is not an object of the given type, the function always returns False . If classinfo is a tuple of type objects (or recursively, other such tuples) or a Union Type of multiple types, return True if object is an instance of any of the types. If classinfo is not a type or tuple of types and such tuples, a TypeError exception is raised. TypeError may not be raised for an invalid type if an earlier check succeeds. Changed in version 3.10: classinfo can be a Union Type . issubclass ( class , classinfo , / ) ¶ Return True if class is a subclass (direct, indirect, or virtual ) of classinfo . A class is considered a subclass of itself. classinfo may be a tuple of class objects (or recursively, other such tuples) or a Union Type , in which case return True if class is a subclass of any entry in classinfo . In any other case, a TypeError exception is raised. Changed in version 3.10: classinfo can be a Union Type . iter ( iterable , / ) ¶ iter ( callable , sentinel , / ) Return an iterator object. The first argument is interpreted very differently depending on the presence of the second argument. Without a second argument, the single argument must be a collection object which supports the iterable protocol (the __iter__() method), or it must support the sequence protocol (the __getitem__() method with integer arguments starting at 0 ). If it does not support either of those protocols, TypeError is raised. If the second argument, sentinel , is given, then the first argument must be a callable object. The iterator created in this case will call callable with no arguments for each call to its __next__() method; if the value returned is equal to sentinel , StopIteration will be raised, otherwise the value will be returned. See also Iterator Types . One useful application of the second form of iter() is to build a block-reader. For example, reading fixed-width blocks from a binary database file until the end of file is reached: from functools import partial with open ( 'mydata.db' , 'rb' ) as f : for block in iter ( partial ( f . read , 64 ), b '' ): process_block ( block ) len ( object , / ) ¶ Return the length (the number of items) of an object. The argument may be a sequence (such as a string, bytes, tuple, list, or range) or a collection (such as a dictionary, set, or frozen set). CPython implementation detail: len raises OverflowError on lengths larger than sys.maxsize , such as range(2 ** 100) . class list ( iterable = () , / ) Rather than being a function, list is actually a mutable sequence type, as documented in Lists and Sequence Types — list, tuple, range . locals ( ) ¶ Return a mapping object representing the current local symbol table, with variable names as the keys, and their currently bound references as the values. At module scope, as well as when using exec() or eval() with a single namespace, this function returns the same namespace as globals() . At class scope, it returns the namespace that will be passed to the metaclass constructor. When using exec() or eval() with separate local and global arguments, it returns the local namespace passed in to the function call. In all of the above cases, each call to locals() in a given frame of execution will return the same mapping object. Changes made through the mapping object returned from locals() will be visible as assigned, reassigned, or deleted local variables, and assigning, reassigning, or deleting local variables will immediately affect the contents of the returned mapping object. In an optimized scope (including functions, generators, and coroutines), each call to locals() instead returns a fresh dictionary containing the current bindings of the function’s local variables and any nonlocal cell references. In this case, name binding changes made via the returned dict are not written back to the corresponding local variables or nonlocal cell references, and assigning, reassigning, or deleting local variables and nonlocal cell references does not affect the contents of previously returned dictionaries. Calling locals() as part of a comprehension in a function, generator, or coroutine is equivalent to calling it in the containing scope, except that the comprehension’s initialised iteration variables will be included. In other scopes, it behaves as if the comprehension were running as a nested function. Calling locals() as part of a generator expression is equivalent to calling it in a nested generator function. Changed in version 3.12: The behaviour of locals() in a comprehension has been updated as described in PEP 709 . Changed in version 3.13: As part of PEP 667 , the semantics of mutating the mapping objects returned from this function are now defined. The behavior in optimized scopes is now as described above. Aside from being defined, the behaviour in other scopes remains unchanged from previous versions. map ( function , iterable , / , * iterables , strict = False ) ¶ Return an iterator that applies function to every item of iterable , yielding the results. If additional iterables arguments are passed, function must take that many arguments and is applied to the items from all iterables in parallel. With multiple iterables, the iterator stops when the shortest iterable is exhausted. If strict is True and one of the iterables is exhausted before the others, a ValueError is raised. For cases where the function inputs are already arranged into argument tuples, see itertools.starmap() . Changed in version 3.14: Added the strict parameter. max ( iterable , / , * , key = None ) ¶ max ( iterable , / , * , default , key = None ) max ( arg1 , arg2 , / , * args , key = None ) Return the largest item in an iterable or the largest of two or more arguments. If one positional argument is provided, it should be an iterable . The largest item in the iterable is returned. If two or more positional arguments are provided, the largest of the positional arguments is returned. There are two optional keyword-only arguments. The key argument specifies a one-argument ordering function like that used for list.sort() . The default argument specifies an object to return if the provided iterable is empty. If the iterable is empty and default is not provided, a ValueError is raised. If multiple items are maximal, the function returns the first one encountered. This is consistent with other sort-stability preserving tools such as sorted(iterable, key=keyfunc, reverse=True)[0] and heapq.nlargest(1, iterable, key=keyfunc) . Changed in version 3.4: Added the default keyword-only parameter. Changed in version 3.8: The key can be None . class memoryview ( object ) Return a “memory view” object created from the given argument. See Memory Views for more information. min ( iterable , / , * , key = None ) ¶ min ( iterable , / , * , default , key = None ) min ( arg1 , arg2 , / , * args , key = None ) Return the smallest item in an iterable or the smallest of two or more arguments. If one positional argument is provided, it should be an iterable . The smallest item in the iterable is returned. If two or more positional arguments are provided, the smallest of the positional arguments is returned. There are two optional keyword-only arguments. The key argument specifies a one-argument ordering function like that used for list.sort() . The default argument specifies an object to return if the provided iterable is empty. If the iterable is empty and default is not provided, a ValueError is raised. If multiple items are minimal, the function returns the first one encountered. This is consistent with other sort-stability preserving tools such as sorted(iterable, key=keyfunc)[0] and heapq.nsmallest(1, iterable, key=keyfunc) . Changed in version 3.4: Added the default keyword-only parameter. Changed in version 3.8: The key can be None . next ( iterator , / ) ¶ next ( iterator , default , / ) Retrieve the next item from the iterator by calling its __next__() method. If default is given, it is returned if the iterator is exhausted, otherwise StopIteration is raised. class object ¶ This is the ultimate base class of all other classes. It has methods that are common to all instances of Python classes. When the constructor is called, it returns a new featureless object. The constructor does not accept any arguments. Note object instances do not have __dict__ attributes, so you can’t assign arbitrary attributes to an instance of object . oct ( integer , / ) ¶ Convert an integer number to an octal string prefixed with “0o”. The result is a valid Python expression. If integer is not a Python int object, it has to define an __index__() method that returns an integer. For example: >>> oct ( 8 ) '0o10' >>> oct ( - 56 ) '-0o70' If you want to convert an integer number to an octal string either with the prefix “0o” or not, you can use either of the following ways. >>> ' %#o ' % 10 , ' %o ' % 10 ('0o12', '12') >>> format ( 10 , '#o' ), format ( 10 , 'o' ) ('0o12', '12') >>> f ' { 10 : #o } ' , f ' { 10 : o } ' ('0o12', '12') See also format() for more information. open ( file , mode = 'r' , buffering = -1 , encoding = None , errors = None , newline = None , closefd = True , opener = None ) ¶ Open file and return a corresponding file object . If the file cannot be opened, an OSError is raised. See Reading and Writing Files for more examples of how to use this function. file is a path-like object giving the pathname (absolute or relative to the current working directory) of the file to be opened or an integer file descriptor of the file to be wrapped. (If a file descriptor is given, it is closed when the returned I/O object is closed unless closefd is set to False .) mode is an optional string that specifies the mode in which the file is opened. It defaults to 'r' which means open for reading in text mode. Other common values are 'w' for writing (truncating the file if it already exists), 'x' for exclusive creation, and 'a' for appending (which on some Unix systems, means that all writes append to the end of the file regardless of the current seek position). In text mode, if encoding is not specified the encoding used is platform-dependent: locale.getencoding() is called to get the current locale encoding. (For reading and writing raw bytes use binary mode and leave encoding unspecified.) The available modes are: Character Meaning 'r' open for reading (default) 'w' open for writing, truncating the file first 'x' open for exclusive creation, failing if the file already exists 'a' open for writing, appending to the end of file if it exists 'b' binary mode 't' text mode (default) '+' open for updating (reading and writing) The default mode is 'r' (open for reading text, a synonym of 'rt' ). Modes 'w+' and 'w+b' open and truncate the file. Modes 'r+' and 'r+b' open the file with no truncation. As mentioned in the Overview , Python distinguishes between binary and text I/O. Files opened in binary mode (including 'b' in the mode argument) return contents as bytes objects without any decoding. In text mode (the default, or when 't' is included in the mode argument), the contents of the file are returned as str , the bytes having been first decoded using a platform-dependent encoding or using the specified encoding if given. Note Python doesn’t depend on the underlying operating system’s notion of text files; all the processing is done by Python itself, and is therefore platform-independent. buffering is an optional integer used to set the buffering policy. Pass 0 to switch buffering off (only allowed in binary mode), 1 to select line buffering (only usable when writing in text mode), and an integer > 1 to indicate the size in bytes of a fixed-size chunk buffer. Note that specifying a buffer size this way applies for binary buffered I/O, but TextIOWrapper (i.e., files opened with mode='r+' ) would have another buffering. To disable buffering in TextIOWrapper , consider using the write_through flag for io.TextIOWrapper.reconfigure() . When no buffering argument is given, the default buffering policy works as follows: Binary files are buffered in fixed-size chunks; the size of the buffer is max(min(blocksize, 8 MiB), DEFAULT_BUFFER_SIZE) when the device block size is available. On most systems, the buffer will typically be 128 kilobytes long. “Interactive” text files (files for which isatty() returns True ) use line buffering. Other text files use the policy described above for binary files. encoding is the name of the encoding used to decode or encode the file. This should only be used in text mode. The default encoding is platform dependent (whatever locale.getencoding() returns), but any text encoding supported by Python can be used. See the codecs module for the list of supported encodings. errors is an optional string that specifies how encoding and decoding errors are to be handled—this cannot be used in binary mode. A variety of standard error handlers are available (listed under Error Handlers ), though any error handling name that has | 2026-01-13T08:48:42 |
https://share.transistor.fm/s/940dfccb#copya | APIs You Won't Hate | The State of the API Address APIs You Won't Hate 40 ? 30 : 10)" @keyup.document.left="seekBySeconds(-10)" @keyup.document.m="toggleMute" @keyup.document.s="toggleSpeed" @play="play(false, true)" @loadedmetadata="handleLoadedMetadata" @pause="pause(true)" preload="none" @timejump.window="seekToSeconds($event.detail.timestamp); shareTimeFormatted = formatTime($event.detail.timestamp)" > Trailer Bonus 10 40 ? 30 : 10)" class="seek-seconds-button" > 40 ? 30 : 10"> Subscribe Share More Info Download More episodes Subscribe newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyFeedUrl()" class="form-input-group" > Copied to clipboard Apple Podcasts Spotify Pocket Casts Overcast Castro YouTube Goodpods Goodpods Metacast Amazon Music Pandora CastBox Anghami Anghami Fountain JioSaavn Gaana iHeartRadio TuneIn TuneIn Player FM SoundCloud SoundCloud Deezer Podcast Addict Share newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyShareUrl()" class="form-input-group" > Share Copied to clipboard newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyEmbedHtml()" class="form-input-group" > Embed Copied to clipboard Start at Trailer Bonus Full Transcript View the website updateDescriptionLinks($el))" class="episode-description" > Chapters December 1, 2021 by APIs You Won't Hate View the website Listen On Apple Podcasts Listen On Spotify Listen On YouTube RSS Feed Subscribe RSS Feed RSS Feed URL Copied! Follow Episode Details / Transcript Matt and Phil are joined by Matthew Reinbold, director of API Ecosystems and Digital Transformations at Postman, to talk about Postman's State of the API 2021. Show Notes Matt and Phil are joined by Matthew Reinbold, director of API Ecosystems and Digital Transformations to discuss Postman's State of the API 2021 report, detailing various data points from around the API world from which specification people turn to, to how confident people feel deploying their APIs. They also discuss various topics around remote work, how APIs enable more remote work and what will happen in the next few years for APIs. Notes: Matthew on twitter: https://twitter.com/libel_vox Postman's State of the API Creators and Guests Host Mike Bifulco Cofounder and host of APIs You Won't Hate. Blogs at https://mikebifulco.com Into 🚴♀️, espresso ☕, looking after 🌍. ex @Stripe @Google @Microsoft What is APIs You Won't Hate? A no-nonsense (well, some-nonsense) podcast about API design & development, new features in the world of HTTP, service-orientated architecture, microservices, and probably bikes. Matt Trask: Cool. Welcome back to APS. You won't hate episode 17. I have Phil with me and we're joined by a very special guest today. Matthew Reinbold, fresh from postman, who is a director of API ecosystems and digital transformations here to talk about their report, the 2021 state of the API ecosystem. Matthew, how's it going? Matthew Reinbold: It is going. I am happy to be here first time, caller, long time listener. Is that how we say that? Matt Trask: I think that's yeah. It's how you say it. Yeah. So I mean, for those of you, like in the off chance that someone doesn't know who you are in the API ecosystem world can you give us a little bit kind of about yourself? Like you manage two different newsletters, at least as well as a pretty prolific Twitter presence as well. But if someone hasn't run into you, like. Matthew Reinbold: Well, yeah, well, first off, thanks for calling it prolific. Some people would call it annoying, but yeah, I I manage a fair number of tweets over at Twitter slash L I B E L underscore Vox, reliable Vox. That's where I talk about digital transformation and APIs and a lot of technology stuff. Occasionally. Fights with blockchain and NFT enthusiastic. But then I also manage, I also manage a newsletter called net API notes, where for almost 200 issues, going back to 2015, I've covered the landscape. I've shared essential bits of information. I've tried to boil down the, the. Current climate and get it right into just the most essential things that decision makers need to know and care about. And then I do a fair amount of blogging on a blog. That's very imaginatively named Matthew reinbold.com. In there, I talk about a fair number of things as well, but in, in, in short my passion is really about coaching people, helping people, teaching people to get better with their API ecosystem. Matt Trask: That's really cool. So one thing that kinda stuck out to me cause it's, so we're going to be talking about the 20, 21 Sidi APR report. However, I'm curious since you've been doing it now since 2015, you've been keeping notes on. The API world. How does your kind of, I hate to say this phrase, the 30,000 foot view of everything that, you know, from 2015, how does that kind of line up to what you saw with the 2021 state of the API report? Matthew Reinbold: Oh, that's interesting. So there's definitely. Maturing as a industry, we've gone through a number of phases. Those of us that have been around the block a few times, see trends come. And most often they, they tend to roll away. And over that time we have to develop models so that we can kind of. Pick the, the, the wheat from the chaff, you know, what, what are the properties of something new, some kind of buzzword, some kind of hyperbole that we can latch onto and say, yes, this is worth investing in. This is worth our interest in our effort versus, yeah, this is some marketing system, some spin as I'm looking at the 20, 21 postman report. I see. Where we've come. It's gone from being single point to point integrations. One-off bespoke API APIs to where we're now talking about things as ecosystems. We're now talking about collections of these things and how entire organizations. Manage these as, as something that's beneficial, something that's collaborative and, and managed as a separate entity rather than, than each individual unit I've got Phil here. So I have to use the forest for the trees analogy rather than just managing the individual API trees. There's now a greater awareness of what the forest, what the forest role is in the company and how to manage that. In a unique way, as opposed to the individual pieces. I will say for those that are listening, like I'm one of the things I want to highlight right up front here is that you don't have to enter an email address. It's not behind the page. We really felt strongly at postman that we had to get this information out to the most number of decision-makers so that they could make better decisions so that they could be informed as they're developing their strategies and roadmaps. So if you go to postman.com/state-of-api, you'll be able to download. With out any worry about having somebody from sales follow up with you later, or getting spam in your inbox, it's free for all. We want this information to be used. We want the dialogues to happen. We want the discourse to be rich and for me and frothy. And so please, you know, don't let past marketing spam. Stop you from checking this out. We want this in the hands of people. Phil Sturgeon: Fantastic. That's good to hear. I mean, that's I haven't got around to reading it as you might have seen from Twitter. Life has been a bit of a mess recently just spending far too much time in the field, as opposed to in the field doing APA stuff. But, yeah, that's definitely always been a concern of mine, of, you know, you hear about these white papers and reports and you just know so many of them like should have just be in the blog post, but instead that like a PDF that and you've got to enter information and then you just get like that fifth email, like, why didn't you reply to my previous four? I was like, I don't know who you are. I just want to read this thing. So yeah, I'm glad you folks are going in a different direction, but Maybe just taking a step back. Like, what is the state of API is report all about where are you getting your information from? What sort of research is being done? And what's the hospital. Matthew Reinbold: Great question. So this is, as far as I know, the largest survey of its kind, we had more than 28,000 people respond to our latest in a series. What we tend to do is try and track where the industry is at. And typically that's been around certain areas. Like how much time do you spend developing API APIs? What kind of tools are you using? Really good stuff there tracking the growth of, of the industry and the maturation of the industry. What I brought to the table this year. Was an interest on finding the behaviors that lead to sustainable, healthy API ecosystems. Like so much of what we talk about when it comes to API ecosystems is still very anecdotal. We tell stories about the Bezos Amazon memo, where we talk about like Twilio or Stripe, but when it comes to decision makers in large organizations, they're still. Trying to pull at what are decent KPIs, what are the behaviors I should be grooming or promoting within my company to make sure that I can keep producing quality API experiences again and again and again. And so what we did with this report that I'm really proud of is dig deep and discover, like, what are the correlating behaviors in organizations that lead to good things happening for companies? Phil Sturgeon: Okay. That's interesting. Cause I think. There's always this question around, like, what's a good API and what's a bad API. Right. And that's just such a nebulous, almost pointless topic so often, because you're just going to end up with opinions about camel case versus kebab case and opinions about rest versus graph UI, and all the nonsense that we love to fight about. And there's going to be someone with a fever at HTTP status code. And none of that actually matters, but you're talking about more of the business level stuff or what, what sort of things have come up as like. Really interesting results from, from your survey about how to build a good API what's what's, what's new and what's interesting. Matthew Reinbold: Right. Well, one of the things I wanted to look at was some of the insights that popped out to me when I was reading accelerate. So accelerate is like from. The previous decade, but it was written by Nicole Forsgren, Jess humble, Jean Kim, they came together and tried to figure out like, what was it about dev ops? That was so powerful. And they wanted to do it in a, in a way that quantified things, not just like, Hey, this is awesome. You should be doing it, but like get to the meat and potatoes of why is this powerful and why should businesses adopt dev ops? And as they went through their research they ended up discovering that there was really four things, four metrics that showed how dev. Made for better organizational performance. And those things were lead time, deployment, frequency, meantime to restore, or how quickly you recover and the change fail percentage. And I thought, huh, that's really interesting. Now that's for dev ops, but if these things are so instrumental in having organizations outperform. Their peers. Can we find the same correlation with API APIs? If we have the same behaviors, can we therefore then draw a line and say, if you have these things, if you have positive aspects of these four attributes, can you then have a more sustainable, more powerful API program? And based on our survey results, the answer is yes. So I can, I can go in and how we, how we drew that correlation. Phil Sturgeon: I'm curious, what sort of metrics are We, looking at? Matthew Reinbold: yeah. So first off we asked people on a 10 point scale. What, how, how well do you think that you've become API first? So out of our 28,000 respondents, they looked at this 10 point scale and they, they put themselves, you know, how they felt approximately 8% of the people that responded said, yes, we are either a nine or a 10 on the scale for API first, we said fine. And then we went through and we said, okay, you know, how long does it take you to make an API? Are we talking hours, days, weeks, so on and so forth. And we also said, okay, you know, not just time to produce, but how frequently you deploy and how many times do you have a deployment failure? Meaning like you put something in production, but it didn't work. Right. So you have to roll back and then like, what was your time to recovery? Like when an outage does occur and let's be. And outage always occurs at some point. Like how, how quickly can you recover from those things? So we got these nice, you know, bell curves and everybody kind of clumped toward the center on these things. And then we said, okay, Now the magic is we go back to that first question, the people that say their API first that have some kind of strong belief that they're doing API first, let's see how they compare to their peers on these metrics. And again, and again, all for these items, API, first people perform better. So, you know, taking one example here. API first people were able to deploy 17% faster than their peers and you know, in a day or less. So if you are API first and granted, there, there might be some subtlety in how a company defines that. But bottom line, if you are API first, you perform better on these metrics than your counterparts. Phil Sturgeon: Interesting. And yeah. Seeing, seeing as you raised it, what is API first? There's, there's a lot of different definitions floating around. Right. And so just for listeners that might not have listened to everything we've ever talked about and read every blog post we've ever read ref ever wrote how do you define it? Matthew Reinbold: Sure. Well, first for people that haven't heard this and haven't listened to every episode, shame on you. Second, I define I defined API first and. Making the API experience or the interface, the primary means for the functionality exchange. So not viewing, like I'm going to create this functionality and then subsequently go and some other team or, or some other project we'll be wrapping this thing in an API. It's thinking of creating an API experience as the primary exchange mechanism with dysfunctional. Not a library, not a module, not a class, the API. So this is slightly different than API design first, which is, I am going to subsequently talk to stakeholders, create a model, whether that's in an open API document or some other means, but I'm going to sketch that out. Test my assumptions, and then subsequently only begin code after. That's API design. First, I do draw a line between those two. They are very copacetic. They, they work together like peanut butter and chocolate, but there, there is a difference. You can, you can do API first without necessarily being API design first. Phil Sturgeon: For sure. Oh, well, we've got you on a roll. You're doing these really well. What is API as a product? Matthew Reinbold: Ooh, API API as a product. So that is creating an API with the. Awareness that it will have a roadmap. It will have ownership beyond just being put into a production environment that it will grow and change and subsequently necessitates the kind of modeling responsibilities and, and awareness that it will be growing and changing over time. Phil Sturgeon: Okay. So instead of, yeah, API first is your product should have an API. And that will be managed by the team who was making this product. And API as a product is a slight variant of API. First, that kind of takes that API out of that generic functionality team and says the API itself is the product. And another team potentially on the same team will be making a product using that Matthew Reinbold: Right. I, I would, I would, I would venture there's a lot of large enterprise environments for which API for. It's about a project that gets the thing into production. And then that thing is left to operate and run on its own. Perhaps there's some monitoring, perhaps some observability, but the actual team that made it is off doing the next thing and the next thing and the next thing there's not the idea that. This is a long lived item that, that produces some kind of business functionality value that is competing in a complex dynamic marketplace like that. That's the API product side of the house. Phil Sturgeon: Hm. Matt Trask: So the, I guess like the, the big question to bring up, I think right now is what did the pandemic do for the API ecosystem? Matthew Reinbold: Well, you know, first of all, I want to just stress that, that this thing that we kind of hand wave is the pandemic was actually like multiple congenital. Crises all at once. Right. You know, I, I want to, for the audience, like we're talking social unrest and political upheaval and supply chain disruption, and the, the pandemic was really a catch all for a tremendous amount of business stress. And what we've seen in the report is the usage of APIs, the number of API APIs the. Amount of focus and care on API. APIs has increased tremendously with that pandemic because business leaders, technology leaders are struggling with this amount of change, this amount of disruption. And so having architectures that are slow to change, difficult to change is just not cutting it in this. Set of multiple crises. So any kind of architectural advantage that allows them to change rapidly change quickly to do different things with how their development investment is deployed. So, you know, for example, taking that one dev team that was altogether in the office and being able to break it down into microservices to allow for greater asynchronous operation, greater flexibility. Those are the architectures that are being sought right now. Matt Trask: Yeah, that makes sense. I mean, it always here in America, I don't know if it feels sing, but you know, like there's. At the core level there. So like the whole, did we go back to the office and be Sandy the office upheaval as well. So it makes sense that there is kind of like a, a struggle on rapping, like getting non-technical CEOs, CTOs, CFOs their heads around the game-changing, this of APIs that doesn't surprise me at all to hear that they're still kind of, I don't want to say struggling, but unsure. Maybe like, Matthew Reinbold: Well, and, and, well, I, I think that's an interesting perspective because it assumes that leaders were in command and control positions of how the labor was divided anyway. And I would actually, I would actually posit that it's the opposite. It was everybody immediately going and running to their home offices and working in a remote work environment. The change in the communication paths changed the architectures that were subsequently produced by those teams. It's Conway's law in effect. And therefore, as we, as we look forward, as we look forward to what's going to happen, I would, I would venture that the organizations that pull people back to centralized locations, for whatever reason, I'm not going to debate whether that's good or bad, but the people that pull the development teams back to. see, like the Terminator two bad guy they'll reform remold because there will be more efficient communication patterns when everybody's face to face. Whereas those organizations that continue to have a distributed workforce will have more distributed architectural patterns because that's how communication is happening. Phil Sturgeon: That's really interesting. I haven't really thought about it before, but I, I, I bet there's been an uptick in kind of API design first, specifically due to this as well. Right? Because my experience working we work was, was pretty awful as far as like API planning goes and as a result, APA architecture and API performance and Matthew Reinbold: You don't say you should blog about that. Fail. Matt Trask: Yeah. Phil Sturgeon: 25. I'm going to do a book about that shit. Matt Trask: Have you tweeted about this yet? Phil? I'm not sure if anyone knows your true Phil Sturgeon: I did a talk. I did a talk recently. But yeah, there was, there was such an element of like, we're real in an open plan office, playing ping pong together and shooting each other with nerves that there was never any effort on API contract being written down in any shape or form because you're all sitting about. And you're just like, what's that end point? Cool mate. Oh, if slash whatever. Oh, is that a, is that property of booty? It's a string called true with QuoteWerks and then you didn't have a need to write it down because you just show it over, over the top of Nerf fire. And I, I do wonder if remote work, well, not necessarily remote work, but quarantine remote work has helped push people more towards it because if you can all be sitting around asking each other, you're going to be typing. The contract over slack. And if you're going to be typing it out over slack, which is inherently ephemeral, then you might as well type it into a Yammel file and commit that in the repo. And then you can have design reviews around the board request or other tools that the offer, that sort of thing. So, yeah, that's, that's just completely a hypothetical and something I'm thinking the second night and check that, but I'm sure it's happening. Matthew Reinbold: I completely agree. And, and let me throw in something that's not in the report, but something that's got me totally geeked out and I'm watching for on my radar, we are going to see the greatest Renaissance of API design documentation that we've ever seen in the next couple of years. Now, granted, you know, as far as Renaissance goes, maybe Renaissance. Documentation are not that great. So, you know, let's put the party hats back in the closet, but what we're seeing with the great resignation right now is all of that knowledge that people acquired in their heads is leaving. It's headed out the door and I've read reports like up to 80% of how to do things with API APIs is in people's heads. Like at we work. If you needed to know how API has worked. You know, you knew Phil was the guy that could get you straightened and Phil Sturgeon: I didn't have a clue. That was the problem. I was trying to find out how to do it. Matthew Reinbold: Okay. So I wasn't, it was somebody, it was somebody on the other end of a, of a Nerf battle away Phil Sturgeon: Someone who quit already is the person that you. Matthew Reinbold: But right now in organizations like you have this phenomenon where a tremendous number of people are leaving organizations and they might've been the sole person who knew where the end points were or knew how that particular tricky function worked. And as organizations are trying to deal with this and recover and still be productive, there's going to be a greater emphasis on having that crap written down, having things documented. Organizations don't have aren't left on their back foot like they are right now. So whether that's heavy handed processes, whether that's just a greater appreciation for documentation among the staff, that's left, whatever that manifests as there's going to be an increasing amount of emphasis on documentation, because people have seen that too much was stuck in people's heads and it's not sustained. Phil Sturgeon: Yeah, that's a really good point. I mean, and not just kind of documentation, but the whole open API as a source of truth earlier on. And I figured it has to be, has to become more noticeably important when Yeah. They've, they've lost the whole team. How the API works and you know what it's like, code's always a bloody mess. Cause you just hacked up within about what over the place and patch things and fix things. And what about and yeah, when they find themselves rewrite in the API, cause no one can really take it over and no one remembers how it works and there's no documentation for it. And it's just too hard to figure out when they just make a brand new one. And they have a whole brand new team doing it. Cause they've already lost all that stuff. Matthew Reinbold: Yeah. Phil Sturgeon: That's a situation that a lot of managers and business people are going to say, how can we go about avoiding doing this? And I just hope there's someone in the room that says, well, APA designed first would really help avoid this problem because otherwise they'll just repeat all the same mistakes again. Matthew Reinbold: Right. Absolutely. Whether it's design first or tools that help analyze existing traffic and write the document afterwards, like whatever you got to do, get that written down and start taking some notes against it because. It's it, I believe right now with the great resignation. It's an Achilles heel. That's probably hampering a lot of organizational ecosystems right now. Matt Trask: Yeah, I would definitely agree. I mean, it shows in the report under open API three dot oh, 44% of people are aware of it, but they don't use it 28% say they use it. 12% said they use it, the love it. So even just combining use it and use it in love. It still does not match aware of we're not using it. Which means that there is definitely a. A river to jump over. So to speak, to getting more people on, to open API, which is probably currently like the standard for API documentation right now which comes back to your point, which allows them to start writing things down and start documenting things. And Phil gets it by bus tomorrow. We work is still going to be okay. It very well could happen. Which is exactly why I use that example. And it, it, yeah, it it'll give the organization a little bit more or a little less reliance on what's in people's heads a little bit more stability in case great races, nation three Datto happens in three years. You know, you don't know what's gonna happen. Phil Sturgeon: Is that when everyone resigns from web three point now, Matt Trask: please. Don't don't threaten me with a good time. Like I've already, I've already muted those web three and NFD on my Twitter and it cleaned it up so Phil Sturgeon: Why do you hate progress, man? Matt Trask: A lot of reasons. I'm a combustion at heart? No. Matthew Reinbold: Hey, if you don't, Phil Sturgeon: particular messages of this progress that are the problem. Matthew Reinbold: if you, don't stand for something, you'll fall for anything. Good for you, Matt. Matt Trask: yes, I've always wanted my life to be attributed to a, a Hamilton quote. So I am glad I did. I can check that one off to get back onto the actual topic and not just bashing NFTs for an hour and a half, which sounds like a lot of fun. What you the most about this report? Like what was something that you read that just you weren't expecting? Matthew Reinbold: I, I think there was two things that when you combine them together it made me tilt my head and go, huh? The, the first is that more than anything else? Including speed to production. People want quality API APIs. They want stability. They want some other things reliability. But the primary thing that people want out of their, their API APIs is quality. And yet when it came to whether or not people had time to test. Everybody acknowledged that testing was good. Tested was valid, but nobody had enough time for testing and it's like, huh? These two things kind of seem like. The, the two sides of a coin, right. You know, people aren't getting the quality that they want, but everybody acknowledges that they don't have enough time to do testing, even though they recognize the testing is an extremely valuable type thing. So I think when it comes to socializing this report and talking to decision-makers and doing the kind of coaching that I so often do, I, this is one of those things too, to bring up, like how in your program are you supporting. Testing and ensuring that enough is being done there so that your developers feel like you're, you're reaching the kind of quality goals that, that you're, you're promising to the rest of the world. Phil Sturgeon: Hm, do you, is the survey broken down by role? So can you, can you look to see if. Managers and engineers have a rule, very interested in, in high quality. And engineers are going, but we don't have enough time, but the manager's like, oh, they definitely have enough time. Matthew Reinbold: Right. So we do have a breakdown by role and job title, but I don't have the numbers in front of me that, that combined, and show me how to break down the quality question. Phil Sturgeon: Yeah, that'd be an interesting one. Cause yeah, so many roles, so many organizations, I just take it as like a universal truth is that companies are just, you know, business and product are demanding feature, feature, feature, feature, feature, and engineers are just like screaming, just keyboards on fire, trying to try to hit them goals. And everything's just wonky as hell. And it seems to be everywhere I go. There's not enough to have. There's not enough time for QA. They might've got rid of the QA team because it's slowed down product and slowed down delivery of features. Yeah, everyone wants high-quality API has, but no one wants to put the time in to testing because testing is inherently hard and slow. Matthew Reinbold: Right. And kind of along those same lines, another stat that jumped out at me was that 76% of the people building API APIs have less than five years experience doing. I mean, you know, as far as restful APIs now, we're, we're more than a decade into that journey. So that stat leaps out at me, like what is it about API development, where we're getting people with zero to five years experience like what's happening. There are the successful API builders, aging out and becoming management. it, are they moving on to web three O and NFTs? Like, like what is, where are our experienced API builders and why are these critical pieces of business infrastructure? In the hands of relatively younger people. That's not to say that they can't be doing a good job, that, that it's impossible to build a great web experience at your first time at bat. But it's also something where I think everybody on this call would probably agree. Experience counts, experience matters. Ha being around the block once or twice, you pick up a feel for what's beneficial, what's maybe a little wonky and you can imbue that into a better design at launch. So, you know, where are the. 10 year, the 12 year, the 15 year veterans. And why are they not the primary source of API infrastructure development? Phil Sturgeon: Yeah. Some that I've seen so much, again, just, I love complaining about we work. Pretty much everyone that was a junior developer, Right. Like the vast majority, what, what you need developers and their role responsible for creating you know, there's like a hundred API APIs and, you know more than a hundred junior developers with just a sprinkling of seniors who were more on the cowboy coder end of things. Not, not to be rude, you know, like startup, you need to be super agile, super fast, not, not a perfectionist. And so, so many of the problems where this is, this person's first rails app, like they know how to accept incoming Jason parameters and they know how to spit something back from the database. And. That's that, and they know how to make a web request. So he talks to . He talks to F talks to G in the thread, and then no, one's got a timer anyway. So everything falls over, like, things like that. The sort of thing you realize, if you've been doing APIs for five years, or for 10 years, you've been doing it for 10 years, you wouldn't do that. You just wouldn't do that. You'd put something in a sidekick job and then implement a web socket or a web hook, or literally anything else. But. That's the sort of thing you do when you consider like HTP failures or server downtime, to be an edge case that is like some weird scenario that probably won't happen. And when you've been doing it for a longer time, you're like you, you change your mindset to this web requests probably won't work. And on the off chance that it. This is what should happen. And you just get really defensive and paranoid and have like 25 different guard statements and, you know, 25 different types of ex exception catching and, and every single circuit breaker and trigger warning that you can possibly put on this thing. And there is, yeah, there is a change in mind. Around around that kind of it doesn't, I'm not being a gatekeeper or at least they're saying you've got to be doing EPS for 10 years until you're good. But when you start out, you you're such, you're more of an optimist. You haven't seen it go wrong in as many ways. You haven't had cascading failures and you haven't had all these terrifying things that happen. So that, that is definitely a concern for me is that I think, yeah. Happy, happy path development. When you go from having one AP. To having 20 or a hundred, the, the the chance of straying off the happy path gets exponentially worse. Right. And, and that's just something, I think a lot of these younger developers on experience with. Matthew Reinbold: Right. Even, even when it comes to design, having used API APIs, having to incorporate the API APIs, you better understand what makes a good description and what is just a reiteration of the, the name itself. Yeah. Yeah. If I have a field called date of birth and the description is just the birth, that, the date that the person was born on, like, well, what was the. do I need to refresh it? Or is it cashed? You know, like, can I store it or is it part of some kind of regulatory PII? And I shouldn't, you know, I can use it, but I shouldn't store, like, there's so many issues that once you've been down that road, and then you're asked to produce an API, you bring that experience with you and you put it into the description that adds so much that yeah. I, I, I, I don't know. How we continue to get that, that experience circulating and get that in front of people. But I think it's really important. Matt Trask: Well, I must wonder too, like how many of those, like experienced API builders are getting swallowed up into Stripe? Twilio, Google. And kind of almost locked away working on their API APIs and not able to share their experiences down the road to junior developers in their own companies or interim networks, things like that too, because it feels like you do your five, seven years as developer, you get pulled into the management game and then all of your knowledge is still there, but you're having to balance both managing a development team, hitting your goals. Pushing out products because you've got to make money for the business. And all of your knowledge that you've worked so hard to gain is kind of sidelined in the name of profits or KPIs or whatever it might be. Matthew Reinbold: Possibly there's, there's certainly exceptions that spring to mind. One of which is Tim Burks and the team over at Google and with the number of resources that they put out there. For their APIs. It's, it's kind of a mouthful, but if you do a Google search for that, they've produced a tremendous amount of documentation about how they support API APIs at scale, how they do their design reviews, how they think about consistency and cohesion across their entire footprint. So that certainly what you described could be the case in some places. You know, I, I, I do think that it's not necessarily the default that's people go off to these big organizations and then just disappear because the folks at Google around Tim and his crew they're doing some great work. Phil Sturgeon: So I've been sat in the room with you having these sort of conversations your last job, Right, Like a center of excellence type stuff. You, you get a bunch of smart people and me together and start talking about what, what would help with these various different problems? Like how do we do APA design reviews? How do we do governance? What standards should we be interested in? So I think sometimes yeah. Experienced developers can get sucked up into these companies and kind of finish and end up having that scale was used for something else. But I, I think companies that have those governance processes, like they're sharing their experience back by creating style guides, by creating programs that they explain how these, how these like API designed life cycles or API life cycle should work. And that's a way that they can essentially. Distribute their experience. So instead of like, I know what to look for when I'm reviewing a poor request, they can create a style guide. That means that everyone will do that. I think the danger there is that when style goes focus on what, instead of why then, then you kind of lose some of that experience because it just seems like arbitrary decisions delivered from upon high. Right. You just get. Do it this way, but, but Y I've read loads of style guides recently. And, and some of them, I should probably show the examples. It's just like, do this. Like, why you don't tell me what to do? You don't my dad, like, it just, I couldn't figure out what they possibly could have meant by it. Cause usually I can look at something. Why might they mean that? Oh, that reminds me of a thing that happened along these lines. They probably got burned by that before, and they want to avoid it, but if you don't see why it just sounds arbitrary and you're not actually teaching anyone on anything, but if you do it right. that that can be really helpful. Matthew Reinbold: Right. And it's also essential that if you're designing these systems like a governance or like a center of excellence that you have the feedback process that you have, the, the communication cycles so that when people do have that kind of. That they have a recourse. It's not a dead end. It's not either you do this or you're punished for it, but oh, if this doesn't make sense, here's who you talk to. Here's how you can escalate your concern here is how you elevate your edge case. And we can have a discussion about it and you can help co-evolve this thing, because you own this as much as somebody else, the, the phenomenon that you described, where it's a dead end. It's thrust upon you. You don't have ownership of that. And as a developer, that does not feel good, that does not invest you in seeing the long-term growth of, of that system. You want to burn that system. You want to be the rebels flying through the death star trench. You want to take that thing down? So what's essential is to realize. You provide the avenues for people to, to voice their concerns, voice their questions, and make them feel heard in such a way that their process, the process is theirs. It's not something done to them. It's it's their process. Phil Sturgeon: I'm just laughing about the death star rebel situation. Now I'm completely distracted. I need to go rewatch some star wars. I don't know. Matt Trask: I mean, your, your thought on the ownership thing is also interesting cause And we like watching the junior Twitter, the junior developer Twitter circles, which is not the end all be all of it all, but there is a large emphasis on if you want to make more money, you need to jump ship every two years on average. And that kind of removes the does or not the desire, but like the, the ownership of any sort of product from a junior developer, because in two years, they're going to be onto another thing. They're going to be onto another system. Codebase, maybe another language and it, it does kind of bring back, like, how do you entice people to have ownership, even if they only are going to plan to say somewhere for a short period? Because we all know that like having, like you said, having that ownership is going to kind of make you more invested, more caring, more thoughtful, more empathetic towards whatever it is that you're building. Matthew Reinbold: Right. I mean, we're veering into management territory, which I'm happy to talk about. I, I know. Matt Trask: very allergic to management. So. Matthew Reinbold: But I, I was just reading Harvard business review. Hey, I'm fun at parties too. So I was reading Harvard business review talking about COVID and the great resignation and the, the management challenges that, that come with that and what we need more. In all companies is a feeling of belonging, a feeling like we have a career progression feeling like our, our, our work has impact and all too often management, just as about making sure people don't do dumpster. Right. You know, I'm, I'm here to police you because the organization doesn't trust you. And it leads to all kinds of weird effects. Like, Hey, if you actually want to grow your career, you need to leave. You need to hop companies every two years and let's be clear that may work, but it's still very disruptive, not just for the company, but for the individual. 'cause they're having to rebuild all of those social structures, their relationships, their patterns, the routines it, it's not, it doesn't come for free. And so from a management standpoint, if you can show people how to have that fulfilling career, how to fulfill those needs. They don't have to jump ship every two years. There's no reason that that has to be the default blueprint. And from a company standpoint, you actually benefit from that accrued experience rather than having a developer. That's done the same thing. Five times you get five years of experience. That's really powerful, really tremendous. And that, that ultimately not only leads to better APIs, but leads to a better employee. So there is a disconnect we need to work with our management layers. It shouldn't just be the technician that has some headcount is by default manager. There needs to be an appreciation for how those are unique skill sets. Those are unique muscles that need to be exercised, but. If we can create that fulfilling sense of duty then, and that the career path for these individuals, we can get them off of this kind of binge and purge career treadmill. Matt Trask: So that's a really, yeah, that's a really good way to put the whole two year turn. And I mean, it comes back full circle to what you just said earlier, which is, you know, 75% of API has been developed now or done by people with less than five years experience. And that's probably because of the same, people are jumping, jumping, jumping. Whereas if you can keep them around, make them happy, make them feel like they belong. We might actually start seeing that number. Dropped significantly to more experienced API developers building more thoughtful API design with, with years of knowledge built up. So I think it'll be really interesting to see kind of what happens with this great resignation how that all shapes up. And then it'll be interesting to see to kind of the 2022 say the API report. How does that. How, how will things change from a year in a year going forward? And what can we expect possibly looking at these two years, the next five years after that, the next 10 years growing on different trends, you know, we might see NFTs ruling the world. We might see graph QL. Rolling. Phil Sturgeon: No comment. Matt Trask: Matthew is kind of shrugging Phil Sturgeon: we're all sad. Now, rural sat now, NFTs powered by graft UL, problem solved. Can you, can you still right click that? No, you can't. It's like a post. So. Matt Trask: Well, there goes Matthew Reinbold: Each unique query is published as an innovator. And you can put the ownership of that query in a blockchain so that you don't have the centralized point of failure. Phil Sturgeon: I was going to thank you for being for, for making this podcast sound intelligent for once. And, Matthew Reinbold: And then I ruined it. Sorry. Phil Sturgeon: and then you. Matt Trask: no, no, no, you didn't ruin it. You just brought it back down to its normal level of ridiculousness. Phil Sturgeon: Fantastic. No. Do you have any predictions for what we're going to see in the, in next year's state of this report? Because then we can play that clip back and laugh at how wrong you were. Matthew Reinbold: Oh, lovely. All right, well, let me have a few minutes to sandbag my answer. No, I think there's a tremendous amount of, of areas where we can take this correlation that I talked about before behaviors. You know how the question immediately becomes well, okay. If these four behaviors are so good and are present in high-performing API companies, how do we get there? And this year we had a little bit around leadership and what leaders do. To get an API first company. I think there is a lot of exploration we can do there to really dial in and say, okay, we know these things are good. How do you get there? How do you promote these things? How do you, how do you get it so that you are able to deploy in a minimal amount of time or recover faster? What are leaders in those organizations doing? That's one of the things I'd love to dig into obviously. A lot of post pandemic aftermath. There's been a tremendous amount of published about how this digital transformation and, you know, we're so much more flexible and adaptable because we, we are now doing all our conversations over zoom. And I look at that and I, I scratch my head because. Digital transformation, at least in the non buzzword compliant way is a whole lot more difficult than just moving everything to a slack conversation or a, or a zoom conversation. Like it means fundamentally dismantling your policies and procedures and reinventing them in a way that digital technology lends itself to. So figuring out what that post pandemic landscape looks like and how we're still feeling the knock on effect. Is going to be something that's also going to be very interesting to explore. Matt Trask: Yeah, that's definitely true. I mean, I think one thing I would like to see is, is that number of people who know open API, but don't use it start to gradually shift down and people who are using open. Start to shift up, which, you know, from a silver right back to having documentation and some sort of notes about their API. So when the, the knowledge people do eventually leave because everyone leaves the company at some point, the knowledge isn't necessarily leaving. And instead we're, we're kind of leaving a better legacy to the people following us. Yeah, definitely. Matthew Reinbold: Here here. Matt Trask: Cool. Matthew, thank you so much for taking some time out of your, your, your day to talk to us. We really appreciate it. Look forward to having you back in roughly a year's time to talk 20, 22. Say the API report Matthew Reinbold: I love it. Let's do it. Pencil it in right now. Matt Trask: Yep. It's it's on my calendar. I don't know what I'll be doing in a year from today, but I know for a fact we'll be talking again. If you want to get. Matthew on Twitter. He is at libel Vox, L I B E L underscore V O X M. And we'll throw the link to your blog and Twitter in the show notes as well as everything else. Awesome. Cool. Thank you so much. We appreciate it. Phil Sturgeon: Yeah. All audio, artwork, episode descriptions and notes are property of APIs You Won't Hate, for APIs You Won't Hate, and published with permission by Transistor, Inc. Broadcast by | 2026-01-13T08:48:42 |
https://docs.suprsend.com/reference/cli-translation-overview | Commands and Flags - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Translation Commands and Flags Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Translation Commands and Flags OpenAI Open in ChatGPT Reference for managing translations in the SuprSend CLI. OpenAI Open in ChatGPT Translations are used to manage multilingual content in SuprSend. You can use CLI commands to manage translations - list, push, pull, and commit. Syntax Copy Ask AI suprsend translation [command] Commands Command Description translation list List translations in a workspace translation push Push translations from local directory to SuprSend translation pull Pull translations from SuprSend to local directory translation commit Commit translations to make them live Inherited Global Flags This command also supports Global Flags , such as: -s, --service-token – Service token for authentication (default: $SUPRSEND_SERVICE_TOKEN ) -v, --verbosity – Log level (debug, info, warn, error, fatal, panic) (default info ) --config – Config file path (default: $HOME/.suprsend.yaml ) -n, --no-color – Disable color output (default: $NO_COLOR ) -w, --workspace string – Workspace to use (default: staging ) Was this page helpful? Yes No Suggest edits Raise issue Previous List Translations List translations in a workspace Next ⌘ I x github linkedin youtube Powered by On this page Syntax Commands Inherited Global Flags | 2026-01-13T08:48:42 |
https://dev.to/szabgab/perl-weekly-601-the-bad-apple-33kl | Perl Weekly #601 - The bad apple - 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 Gabor Szabo Posted on Jan 30, 2023 • Originally published at perlweekly.com Perl Weekly #601 - The bad apple # perl # news # programming perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? Originally published at Perl Weekly 601 Welcome to the Perl Weekly! I am ambivalent about writing this and including in the Perl Weekly, but I feel if I don't speak up then how can expect others to do so. For another perspective on the subject I'd recommend you read this thread by Mohammed Hashim on trust and perspective. A couple of weeks ago I received an email full of good old antisemitism. It was clearly indicating that it is from one of the readers of the Perl Weekly. It was a tirade of expressions common to white Christian antisemites. Usually also referred to as white supremacists. It is clear that the sender knew what he was doing was reprehensible as he tried to hide behind an anonymous address. However, I am not sure what he wanted to achieve with this message. I guess he was upset that he cannot physically harm me. This person is also a bit slow. He found out that I am a Jew only now and I definitely did not hide this fact. I wonder what will happen when he understands that the other editor is a Muslim. These white supremacists usually hate them too. This past week was the International Holocaust Remembrance day. Both of my parents went through the Holocaust, but at the end they were among the few lucky ones who survived. My father was born in 1917 so he was well aware of the pre-Holocaust rhetoric. I am quite sure he would be shocked by the level of Jew-hatred that goes on the social networks and in the public sphere in general. More or less with impunity. Both from the right and from the left. After WWII many Germans said they did not know what was happening. Now we can see what's going on. Unfortunately most people try not to look and don't speak up. They might be afraid to speak up. If they do speak up they usually point to the other side of the political aisle and it gets tagged as partisan politics. The growing anti-Jewish public expressions bother me a lot, but what bothers me even more is that the majority is silent. OK, now that I got this off my chest, let me mention the Open source development course I started to teach last week. We had our first session, but if you hurry you can still join us and catch up using the videos. If you are interested here is the site that is being generated from the information of the participants. Here is another site where you can see the participants of a similar course I started 4 weeks ago. If you are interested look at this page for the details on how to sign up. Participants in the course are already blogging about it and soon they will start contributing to Perl-based projects. Most likely CPAN distributions. Join us! Enjoy your week! -- Your editor: Gabor Szabo. Articles Monty Hall - the comeback! You're given three doors, A, B, and C. There is a prize behind one. If you choose the right door, you win the prize. What is the prize? Perl Testing in 2023 This is a quick run-down of how Toby is structuring his test suite. What is the correct mix of unit- and integration-tests? What is the difference between a unit-test and an integrations test? Do you call a test integration test when it involves two microservices? Two modules? Two functions? Turn this in that 'So well, yeah... this is as much of an incomplete post as it can be, but I set a goal to write/publish something every day, not to always write self-contained meaningful stuff!' I like that spirit! Just started the OSDC course The first of several article that will go along the Open Source Developer Course . Open Source Development Course for Perl developers. Quick note about caller This is mostly a mute post, as the code below should say it all SYNOPSIS-style. Command line counter with plain text file database I have a series of examples called 'counter examples' where I implement a simple counter in various languages and technologies. This one is in Perl. Doubtful about release new module AstEval Flavio coded a new module AstEval but he is doubtful about releasing it on CPAN. Color Evolution The most requested feature of the Cellgraph is now in operation: Colors. PDF document creation with Markup languages New, powerful features have recently been added to PDF::Builder and PDF::Table, enabling faster and easier high-level generation of PDF documents. The versions are respectively 3.025 and 1.005, and are available on CPAN. My Favorite Modules: PerlIO::via PerlIO::via allows you, easily, and with minimal code, to modify an I/O stream before it gets to the reader of the stream. or after the writer has written it. SPVM improved Exchange API at v0.9684. Welcome to this easy world of type conversion! SPVM::File::Basename is released. This is the first module of SPVM using regular expressions. Perl This Week in PSC (095) The Perl Steering Council The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 202 Welcome to a new week with a couple of fun tasks "Consecutive Odds" and "Widest Valley". If you are new to the weekly challenge then why not join us and have fun every week. For more information, please read the FAQ . RECAP - The Weekly Challenge - 201 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Missing Numbers" and "Penny Piles" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. How Many Missing Coins? Code re-use and smart use of exists makes it really fun. Keep it going. Pennies by the numbers Thanks for sharing the related stories on top of clever Raku solutions. Keep it up great work. Weekly Challenge 201 Smart match in Perl? It is marked deprecated and advised to avoid it. Having said, the end result looks sharp. The Weekly Challenge 201 Having clever solution is not good enough for James as he shares behind scene story. Incredible. PWC201 - Missing Numbers Cute solutions in Perl and Raku equally. Thanks for keeping us enlightened. PWC201 - Penny Piles Little overloaded for me, had to read twice to get my head around it. Liked the discussion of SUB . Perl Weekly Challenge 201: Missing Numbers Raku flaunts the power so openly every week. You can check out yourself, if you don't believe me. not satisfied! Clever one-liner in Raku for "Penny Piles" task, very impressive. Thanks for sharing. Perl Weekly Challenge 201 Here we go, Perl one-liner giving tough fight to Python. Thanks for sharing the knowledge with us. 201: Missing numbers and piles of pennies Some smart tricks used in the solutions. Thanks for sharing. The Weekly Challenge #201 Robbie, being partner in crime this week, I was looking forward to his solution. I must confess it was top notch. Penny Numbers Ruby in action this week, I am sure you will fall in love. Thanks for your contributions as always. Missing pennies Python is not far behind Perl when it comes to one-liner. I am loving it. Well done. Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . Perl Jobs by Perl Careers Senior Perl Developer with Cross-Trained Chops. UK Remote Perl Role The best senior developers know that variety is the spice of life. Sure, you’ve got Perl chops for days, but that’s not all you can do — and that’s why our client wants to meet you. They’re looking for senior Perl developers, Node engineers, and those with mighty Python and SQL skills to lead their team. Adventure! Senior Perl roles in Malaysia, Dubai and Malta Clever folks know that if you’re lucky, you can earn a living and have an adventure at the same time. Enter our international client: online trading is their game, and they’re looking for Perl developers with a strong background in Modern Perl (you should be comfortable with Moose and PSGI/Plack ) and have a passion, drive, and an appreciation for new experiences. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe. UK Remote Perl Developer Role A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #755 - Does TIOBE help Perl? # perl # news # programming Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming 💎 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:48:42 |
https://www.dataprotection.ie | Homepage | Data Protection Commission FAQs Contact us Children Gaeilge English Search Gaeilge Site Search Search Header Menu Your Data For Organisations Resources Who We Are News and Media Data Protection Officers FAQs Contact us Children Protect Your Children's Data Find out more Previous Next Contact the DPC For Organisations Report a breach Register your DPO The Data Protection Commission The Data Protection Commission (DPC) is the national independent authority responsible for upholding the fundamental right of individuals in the EU to have their personal data protected. The DPC is the Irish supervisory authority for the General Data Protection Regulation (GDPR), and also has functions and powers related to other important regulatory frameworks including the Irish ePrivacy Regulations (2011) and the EU Directive known as the Law Enforcement Directive. Frequently Asked Questions Latest News 07/11/2025 DPC statement on LinkedIn AI Training 16/10/2025 The Data Protection Commission and Coimisiún na Meán sign Cooperation Agreement and issue Joint Statement on Children 06/10/2025 Further Update from the DPC regarding RTÉ's Prime Time Investigation Your Data Want to find out more about your data protection rights as an individual or contact us in relation to a potential infringement of your rights? For Individuals For Organisations Want to find out more about your data protection obligations as a Data Controller or Processor or contact us in relation to a potential breach? For Organisations Resources Are you interested in learning more about data protection and get insights into the new General Data Protection Regulation? Guidance Information for Data Protection Officers Are you a Data Protection Officer interested in our guidance and other resources? Resources Your Data Data Protection: The Basics Your rights under the GDPR Exercising your rights Organisations Data Protection: The Basics Know your obligations Codes of Conduct GDPR Certification Resources for Organisations Rules for direct electronic marketing International Transfers Sports Conference 2025 Sports Infographics ARC SME Awareness ARC Conference ARC Workshops ARC Infographics Contact us Data Protection Commission 6 Pembroke Row Dublin 2 D02 X963 Ireland Accessibility Statement Data Protection Statement Cookie Policy Website Development by FUSIO | 2026-01-13T08:48:42 |
https://survivejs.com/research/ | SurviveJS - Research Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... Research For the completion of my doctorate, I produced several papers and you can find all of the papers I have written at ORCID ↗ . I have listed several on this page in addition to other works, including works of my students (MSc, BSc). Dissertation – Emergence of hybrid rendering models in web application development (2025) # Web is the largest application platform available globally as at least 60% of humanity has access to it [52]. The situation has been enabled by the almost ubiquitous nature of the internet and broad access to it. The popularity of the web platform comes with its challenges, as it was originally designed for static content and evolved to support application development. The continuous process of evolution has forced developers to evaluate their development practices from time to time. Simultaneously, the demands for the quality of web applications have increased and so has their size as their size has tripled over the past ten years [22]. The development contradicts the global trend of increased web usage through mobile devices, where bandwidth and computational power are limited by definition. Due to the prevailing trends of increasing application size and mobile usage, new, more effective ways to develop web applications are needed. This dissertation captures the current situation of web development while providing directions on how to address the industry’s current pain points. The dissertation shows how web developers can apply niche techniques and technologies to improve their applications on all levels while delivering faster and better user experiences without forgetting developer experience. Examining so-called hybrid rendering techniques and edge computing, I show what web development might become in the years to come and propose solutions beyond what is available in the mainstream. The primary purpose of this dissertation is to explore the space between static and dynamic web development to open new venues for web developers through novel techniques and technologies without forgetting users. Read the dissertation at ResearchGate ↗ View the defense at YouTube ↗ Papers # My research focuses mainly on static site generation, edge computing, islands architecture, and web architectures. You can get the best overview of my research outputs through ORCID ↗ , ResearchGate ↗ , or Google Scholar ↗ . I have listed several of my main papers below and you can find more from the aforementioned sources. Perspectives and potential issues in using artificial intelligence for computer science education (2025, preprint) ↗ Since its launch in late 2022, ChatGPT has ignited widespread interest in Large Language Models (LLMs) and broader Artificial Intelligence (AI) solutions. As this new wave of AI permeates various sectors of society, we are continually uncovering both the potential and the limitations of existing AI tools. The need for adjustment is particularly significant in Computer Science Education (CSEd), as LLMs have evolved into core coding tools themselves, blurring the line between programming aids and intelligent systems, and reinforcing CSEd’s role as a nexus of technology and pedagogy. The findings of our survey indicate that while AI technologies hold potential for enhancing learning experiences, such as through personalized learning paths, intelligent tutoring systems, and automated assessments, there are also emerging concerns. These include the risk of over-reliance on technology, the potential erosion of fundamental cognitive skills, and the challenge of maintaining equitable access to such innovations. Recent advancements represent a paradigm shift, transforming not only the content we teach but also the methods by which teaching and learning take place. Rather than placing the burden of adapting to AI technologies on students, educational institutions must take a proactive role in verifying, integrating, and applying new pedagogical approaches. Such efforts can help ensure that both educators and learners are equipped with the skills needed to navigate the evolving educational landscape shaped by these technological innovations. Read about usage of AI for CSEd ↗ Challenges related to approximating the energy consumption of a website (2025) ↗ Based on a rough estimate, the ICT industry consumes 7 to 10% of the world’s energy, and around 70% of this is related to usage while the rest can be considered embodied due to manufacturing, logistics, and related activities. Simultaneously, the web has become an important channel for consuming ICT services as it is the largest available application platform globally. Especially energy consumption of mobile web applications has been studied in detail, but there is a clear research gap for web applications because suitable measurement tooling has not been available earlier.The purpose of this article is to review the current state of the art and understand how to approximate the energy consumption of web applications effectively by measuring an existing website that has been implemented with two different web frameworks—Qwik and Next.js. Our main findings indicate that although services that approximate energy consumption of web applications exist, they tend to overestimate consumption when compared to our measurements and they may even show contradictory results between different web frameworks. Further, we found that Firefox Profiler can be used to measure energy consumption with high precision. We also found that Website Carbon service fails to acknowledge techniques, such as lazy rendering, and there were open questions related to hosting detection (green or not) while the service was not transparent in calculating the results—not disclosing intermediary results or exposing the scope of the calculation. Our key recommendation is to use CPU-based measurement methods in estimating web energy consumption. Read about website energy consumption ↗ The Potential of Serverless Edge-powered Islands for Web Development (2025) ↗ Web developers face two significant challenges when developing their applications and websites: latency and payload size. Given that web services rely on servers, the related communication incurs a cost in terms of latency. In contrast, the payload passed to the client incurs a communication cost, not to mention the computational cost to the client. The concept of serverless edge computing, built on top of content delivery networks (CDNs), is an approach that has begun to gain the attention of web developers for its promise of lower latencies due to its efficiencies in communication thanks to globally distributed networks and replication. Islands architecture is a technical approach that addresses payload size by giving developers easy ways to defer and potentially even avoid the cost of loading content. Combined, these two approaches form edge-powered islands and, in this article, we examine how the combination can help to address these two notable costs web developers have to consider in their daily work. Our findings indicate that edge-powered islands can provide a way to introduce interactivity to otherwise static websites while wrapping dynamic portions of a page within islands to gain the benefits of static approaches in more dynamic contexts, such as storefronts. In addition, islands can provide loading benefits even for more application-like websites, such as social networks, and give web developers an additional control layer in their development work. Read about edge-powered islands ↗ Overview of Web Application Performance Optimization Techniques (2025) ↗ During its thirty years of existence, the World Wide Web has helped to transform the world and create digital economies. Although it started as a global information exchange, it has become the most significant available application platform on top of its initial target. One of the side effects of this evolution was perhaps suboptimal ways to deliver content over the web, leading to wasted resources and business through lost conversions. Technically speaking, there are many ways to improve the performance of web applications. In this article, we examine the currently available options and the latest trends related to improving web application performance. Read about web performance ↗ Resumability — A New Primitive for Developing Web Applications (2023) ↗ Hydration is a common technique employed by current JavaScript-based frontend frameworks, such as React. In hydration, the application code is re-executed on the client to recover component boundaries, application state, and event listeners. In this article, we look into a new primitive called resumability that avoids thework as the necessary information is serialized into HTML. The idea has been adopted by Asta (2023), Google Wiz, Marko (planned for version 6 [1]), Sidewind (since 2022), and Qwik (2021) as a main building block. Resumability gives these solutions unique advantages by avoiding the cost of hydration. Furthermore, resumability can allow developers to leverage code-splitting out of the box, depending on the implementation. The shift has implications for both developer and user experience. This article aims to understand why resumability matters and why it is a good option for replacing earlier hydration-based approaches. We also consider challenges related to adopting resumability on a framework level and briefly highlight the first resumable solutions for developing web applications. Read about resumability ↗ ECMAScript - The journey of a programming language from an idea to a standard (2023) ↗ A significant portion of the web is powered by ECMAScript. As a web technology, it is ubiquitous and available on most platforms natively or through a web browser. ECMAScript is the dominant language of the web, but at the same time, it was not designed as such. The story of ECMAScript is a story of the impact of standardization on the popularity of technology. Simultaneously, the story shows how external pressures can shape a programming language and how politics can mar the evolution of a standard. In this article, we will go through the movements that led to the dominant position of ECMAScript, evaluate the factors leading to it, and consider its evolution using the Futures Triangle framework and the theory of standards wars. Read about ECMAScript ↗ The Rise of Disappearing Frameworks in Web Development (2023) ↗ The evolution of the web can be characterized as an emergence of frameworks paving the way from static websites to dynamic web applications. As the scope of web applications has grown, new technical challenges have emerged, leading to the need for new solutions. The latest of these developments is the rise of so-called disappearing web frameworks that question the axioms of earlier generations of web frameworks, providing benefits of the early web and simple static sites. Read about disappearing frameworks ↗ The State of Disappearing Frameworks in 2023 (2023) ↗ Disappearing frameworks represent a new type of thinking for web development. In the current mainstream JavaScript frameworks, the focus has been on developer experience at the cost of user experience. Disappearing frameworks shift the focus by aiming to deliver as little, even zero, JavaScript to the client. In this paper, we look at the options available in the ecosystem in mid-2023 and characterize them in terms of functionality and features to provide a state-of-the-art view of the trend. We found that the frameworks rely heavily on compilers, often support progressive enhancement, and most of the time support static output. While solutions like Astro are UI library agnostic, others, such as Marko, are more opinionated. Read about disappearing frameworks ↗ Implications of Edge Computing for Static Site Generation (2023) ↗ Static site generation (SSG) is a common technique in the web development space to create performant websites that are easy to host. Numerous SSG tools exist, and the approach has been complemented by newer approaches, such as Jamstack, that extend its usability. Edge computing represents a new option to extend the usefulness of SSG further by allowing the creation of dynamic sites on top of a static backdrop, providing dynamic resources close to the user. In this paper, we explore the impact of the recent developments in the edge computing space and consider its implications for SSG. Read about edge computing and SSG ↗ Booklets # As a part of coursework, I authored a short booklet under the title “Disappearing frameworks explained”. The booklet was published in 2023 through arXiv. ↗ Lectures # I give a yearly lecture titled “Web application development - The past, the present, the future”. You can find the 2024 slides of the lecture here ↗ . Advisory work # During my studies, I have worked as an advisor for several theses. You can find a selection below. Masters # Artificial Intelligence for Web Development: Perspectives from Industry and Literature (Pyry Pohjalainen, 2025, MSc) ↗ The integration of generative AI is transforming industries, enhancing efficiency and user experience, while introducing new opportunities and challenges to web development. The AI era-defining release of ChatGPT has cemented AI tools in the toolkits of people working in web development, as previously labor intensive tasks such as programming and debugging could possibly be outsourced to the AI – this, however, has brought up new issues of when the utilization of AI is useful, which tasks should the developer complete without AI, and what effects can be found from the utilization of AI for tasks previously seen as out of reach for machines. Given this, the objective of this study is to clarify the effect the utilization of AI has had on web development using the sequential qualitative-quantitative design method with interviews and a survey to validate and expand upon the findings from the interviews. This study finds that AI is used by people working in web development to increase efficiency and for the ease of use it provides, with multiple minor downsides, such as AI not being able to understand complex logic, everything created by an AI needing to be validated by the user and AI suggesting code which could potentially cause a security issue. This means there are clear benefits to continued development of AI tools for web development and an increased role of AI proficiency for people working in web development, with the user knowing when to utilize AI to receive the optimal results, with open questions and possibilities of future research being directed towards code quality of AI tools. Read about AI in web development ↗ FlagShip: Reimagining Stateful Serverless Architectures at the Edge (Anoop Bidikar, 2024, MSc) ↗ Feature flag systems enable dynamic control of application features without code redeployment, playing a crucial role in modern software development. While edge computing and serverless architectures offer promising solutions for low-latency applications, integrating stateful services into these environments presents significant challenges. This research investigates how stateful services in commercial edge computing platforms influence the feasibility and performance of stateful serverless applications, through the implementation and evaluation of a feature flag management system. We developed FlagShip, an edge-based feature flag management system utilizing stateful serverless functions and storage services from a commercial edge platform provider. Through extensive evaluation, we compared FlagShip’s performance against traditional cloud-hosted feature flag services, analyzing metrics such as client-side and server-side latency across different deployment configurations. Our results demonstrate that FlagShip achieved up to 70% reduction in client-side latency and 93% decrease in server-side latency compared to baseline implementations. Notably, a cached cloud-hosted variant outperformed all implementations, including edge deployments, challenging conventional assumptions about edge computing’s performance advantages. These findings provide valuable insights into the practical implications of building stateful edge applications, highlighting the critical role of storage and caching solutions that operate within the same runtime environment. Read about serverless architectures ↗ See also Anoop's blog post about the topic ↗ The potential of WebAssembly in Edge Computing (Antti Nousiainen, 2024, MSc) ↗ WebAssembly is a well-supported web technology that allows easy conversion of existing code as well as generation of new projects from a multitude of programming languages for the web, in a portable manner. Edge environments, meanwhile, provide a way to distribute workloads near the end user, and allow scaling of execution well. Furthermore, edge environments offer the possibility of decreased latency compared to more conventional cloud services. Combining these could improve the usability and suitability of edge computing in certain kinds of applications, such as data processing for Internet-of-Things (IoT) devices. Therefore, research into combining these technologies makes sense. The objective of this thesis was to study this intersection of WebAssembly and edge environments through examination of performance and usability. Performance was considered through creating a test environment and by benchmarking WebAssembly, while usability was considered by documenting in detail potential problems for developers and the ways how WebAssembly and edge environments can be used together. Overall, the thesis found that even though some roadblocks were encountered during the test environment development and performance was decreased in comparison to locally executed tests, existing C-based benchmarks could be converted to WebAssembly and be run in the selected edge environment with acceptable performance when compared to locally executed tests. Read about WebAssembly in Edge Computing ↗ Impact of React component libraries on developer experience - An empirical study on component libraries' styling approaches (Ossian Rajala, 2024, MSc) ↗ Over the past three decades, web design has transitioned from simple static pages to complex, interactive applications. Modern web development relies heavily on JavaScript frameworks and reusable components, often utilizing third-party, pre-styled component libraries. Customizing the styles - which are typically implemented with CSS (Cascading Style Sheets) - of such libraries to meet specific design requirements is a common task. This customization creates a need for effective styling solutions that enhance developer experience and maintainability. Despite its widespread use in web development, CSS remains under-researched, particularly in the context of how it affects developers’ day-to-day work with component libraries. As technologies continue to evolve, understanding and improving the developer experience becomes increasingly crucial, as it can positively impact software development outcomes. This thesis seeks to understand how React component libraries’ theming approaches impact customization, particularly ease of implementation, reusability of styles, and flexibility to accommodate various design requirements. Furthermore, the study investigates how the aforementioned factors and the library’s documentation support or hinder the developer’s work. These factors were investigated by porting the same application to four pre-styled component libraries. The implementation process, methods used, and challenges encountered were documented and analyzed. As a result, the study found that meeting the design requirements was possible with all compared libraries: Ant Design, Chakra UI, shadcn/ui, and Mantine. However, the ease, intuitiveness, and maintainability of required solutions varied. Especially as one of the libraries, Ant Design, was tightly coupled with a specific design system. Color customization and dark and light modes were frequent sources of confusion. Overall, the libraries offered a positive experience and allowed the desired design to be reached without resorting to style hacks. Still, all the libraries would benefit from improved documentation, namely more detailed examples and explanations of the customization options. Read about component libraries for React ↗ The Effects of Architectural Design Decisions on Framework Adoption: A Comparative Evaluation of Meta-Frameworks in Modern Web Development (Joel Hassan, 2024, MSc) ↗ The rise of JavaScript meta-frameworks has transformed the development of web applications in recent years. Alongside established frameworks, such as Next.js, more recent entrants, such as Astro and Qwik City have introduced novel approaches centred on simplifying developer experience and improving the perceived performance of applications for users. The competitive nature of the meta-framework space and the long-term impact of framework choice on projects calls for an understanding of the factors that drive framework adoption. This research first delineates extensibility, ease of migration and updates as a set of adoption factors based on prior research and their relevance to modern meta- frameworks. The factors form a basis of evaluating three meta-frameworks—Next.js, Astro, and Qwik City—selected based on their popularity, design, and phase on the innovation curve. A developer survey is conducted to complement the analysis, gathering insights from developers on the value they associate with architectural aspects and their personal experiences with the selected frameworks. The findings substantiate previous research that identified learnability and extensibility as primary adoption drivers. The main risks driving unadoption involve complexity associated with a high degree of configurability and the perceived framework lock-in due to an abundance of framework-specific concepts. Despite shared authoring experiences across evaluated meta-frameworks, the analysis indicates that newer frameworks are showing potential to considerably enhance user and developer experiences by focusing on a simplified authoring experience, addressing issues related to the transmission of application logic from the server to the client and providing more fine-grained approaches to managing client-side JavaScript. Read about framework adoption ↗ Improving the Initial Rendering Performance of React Applications Through Contemporary Rendering Approaches (Touko Lonka, 2023, MSc) ↗ Modern JavaScript frameworks have enabled the development of interactive and user-friendly web applications. Over the past decade, React has become the leading user interface framework in the JavaScript world, contributing to the rise of Single Page Applications (SPA). However, the extensive development of SPAs has led to an increase in the amount of client-side JavaScript, thus triggering performance issues in terms of initial loading times. The speed at which a web application is initially rendered can significantly influence its potential for revenue generation, as the initial loading time often determines whether a user stays on or abandons a web page. Recognizing the integral role of the initial loading speed in user retention, this study delves into the realm of performance optimization strategies, focusing predominantly on the use of React-like UI frameworks and meta-frameworks as a means to improve the initial rendering performance of web applications. Through this exploration, we aim to provide a comprehensive understanding of contemporary rendering approaches and their role in enhancing web application performance. To compare the performance impacts of various rendering approaches, we implement a React application simulating the dynamics of a real-world e-commerce platform and replicate the same application through multiple technologies. These technologies include the UI frameworks Preact, Qwik, and Solid, as well as the meta-frameworks Next, Astro, and Qwik City. Finally, we provide extensive benchmarks to measure the page weights and initial rendering performance of each application version. Our findings demonstrate that the utilization of React-like UI frameworks and meta-frameworks can considerably decrease the amount of JavaScript downloaded by the client, contributing to improved initial rendering times. The most promising results are achieved by using meta-frameworks for extending the capabilities of UI frameworks with modern rendering strategies like Server-Side Rendering and Static Site Generation. However, these approaches often present significant trade-offs, such as increased Server Response Times and extended build durations. Read about initial rendering performance ↗ Bachelors # Transforming Web Development with NLP and Vibe Coding Techniques (Joona Heinonen, 2025, BSc) ↗ With LLMs and AI getting significantly better in recent years, it has changed how web development is approached. This thesis aims to cover the changes that vibe coding and natural language programming bring to web development and what type of benefits and drawbacks might emerge. Vibe coding and fully delegating development to AI tools is a relatively new area in web development, which is the reason for this study. This study is conducted as a literature review going over papers and research related to vibe coding and no-code style programming in web development. Web development has shifted from manually writing code to generating code and tests with AI agents, which leaves resources for other parts of the process. Delegating development to AI has several levels depending on the amount of work left to the human developer, ranging from expert consultant to full delegation - in other words, using vibe coding. Vibe coding is defined as leaving everything to the “vibes” referring to fully letting the AI agent create and test the web application. Vibe coding can bring benefits to the user with its speed and knowledge, offering an easy way to try new projects and ideas with limited resources. it can also teach users about certain algorithms and architectural decisions. Applying vibe coding can also bring a series of drawbacks, such as vulnerabilities in the form of security issues and risks. The use of LLMs can also bring ethical issues, such as bias in the LLM outputs, LLM hallucinations in the form of non-factual outputs, and the non-transparent use of AI. Furthermore, purely using AI to program can lead to the decay of knowledge for the developer, leading to more risks in the future. Read about vibe coding ↗ Systematic Literature Review of Agentic AI and AIOps Across Software Lifecycle (Eppu Ruotsalainen, 2025, BSc) ↗ Agentic Artificial Intelligence (agentic AI) and AI for IT Operations (AIOps) are evolving concepts that bring autonomous decision-making agents into the Software Development Life Cycle (SDLC). This thesis conducted a systematic literature review of how these technologies are applied across the SDLC of software development. The review covers the design and coding phase, testing and Continuous Integration/Continuous Delivery (CI/CD), and operations and maintenance. The review followed PRISMA 2020 reporting principles. Relevant studies were identified from major digital libraries and screened against explicit inclusion criteria. Data were gathered and synthesized by SDLC phase to compare approaches, benefits, limitations and maturity, and to examine cross-phase patterns. The evidence reveals a clear progression of maturity. Operations is the most advanced: AIOps capabilities have been used in practice to reduce time-to-detect/resolve. Testing and CI/CD yield promising but uneven gains, constrained by trust, data availability and toolchain integration. Design and coding are the least mature — generative assistants speed up routine development, but still require human in the loop review. Overall, the integration of agentic AI across phases is still limited. This review highlights important research gaps, including the need for greater autonomous AI assistance in the early stages of development and stronger feedback loops that bring operational insights into testing and development through shared data models and interoperable tooling. In practice, organizations may gain the most by first using AIOps, then piloting AI-assisted testing and finally deploying coding assistants with strict guardrails. For researchers, priorities include early-phase agents with explainable outputs, cross-phase pipelines and longitudinal assessments of end-to-end impact. Read about agentic AI ↗ A Comparative Study of the Specification Processes of ECMAScript and TypeScript (Can Kolho, 2025, BSc) ↗ JavaScript was developed in 1995 to enhance interactivity on web pages, and today it is one of the most widely used programming languages in the world. Its official standard is ECMAScript, which is maintained by Technical Committee 39 (TC39) of ECMA International. Based on ECMAScript, Microsoft’s open source project TypeScript includes all the features of JavaScript, with its most significant addition being static typing. This helps identify errors during development rather than at runtime. This thesis examines the development phases of ECMAScript and TypeScript before a feature is included in the official specification. The work was conducted as a literature review, with key sources including scientific articles, official ECMAScript specification, documentation maintained by the technical committee, as well as documents from Microsoft and the open source community. The aim of the research is to answer the question: How do the specification processes of ECMAScript and TypeScript differ from each other? The ECMAScript development is a well-defined six-stage standardization process. A proposal is advanced by a designated champion appointed by the ECMA organization and each stage requires approval from the TC39 commitee. In contrast to ECMAScript, TypeScript does not follow a formal specification process. Its development is more pragmatic and led by Microsoft. New features arise from practical needs without a structured phase model or committee process. This allows for a more responsive approach to the need of the developer community. Read about specification processes ↗ Local-First Software: Promises and Pitfalls (Otto Otsamo, 2025, BSc) ↗ Software applications with collaboration features are typically built to store and process data on remote servers, making the client application completely dependent on those servers. This architectural pattern is simple to implement but has drawbacks: it is not possible to use the application without an internet connection, it is not always clear who owns the user’s data, communication with the server may cause delays in actions taken by the user, and the application stops working if the service shuts down, potentially resulting in data loss. Local-first software refers to a software design pattern that prioritises storing and processing data locally on the user’s device instead of remote servers. In this approach, servers are typically only utilised as a synchronisation tool to enable collaboration between users. This thesis reviews the benefits and drawbacks of each approach based on existing research and describes the common technologies typically used to build local-first software. The study demonstrates that the local-first pattern can be beneficial in applications involving asynchronous collaboration, but is unable to replace certain types of cloud-based software, such as those handling financial transactions or large datasets. Currently, the development of local-first applications remains relatively limited; however, there is clear interest in the topic within both academic and professional communities. To advance local-first development, it would be beneficial to research how existing synchronous data structures could be adapted to support asynchronous collaboration and how the memory overhead and other limitations of local-first data structures can be mitigated. Read about local-first software ↗ Comparison of web application architecture styles (Otto Söderman, 2025, BSc) ↗ Web application architecture styles define the overall structure of a web application. In today’s web development landscape, there are numerous web architecture styles to choose from. Choosing the right architecture is often difficult, and the choice can have a significant impact on the performance, development, and maintainability of a given web software project. Currently, information about these architectures is scattered. Therefore, the purpose of this thesis is to consolidate this information. In particular, the research goal is to identify the commonly used web application architectures and map out their benefits and drawbacks. The research was conducted as a literature review, using conference proceedings, research articles, and books as the main sources. The four main software application architecture styles that were identified are: monolithic, tiered, microservices, and micro-frontends. Monolithic systems were found to be the easiest to setup and manage, with tiered systems being a bit harder, and microservice-based systems, which include micro-frontends, being even more difficult. However, microservice-based systems were found to often be easier to maintain and develop further features for, as opposed to monolithic and tiered systems. Microservice-based systems were also found to be more scalable than monoliths, while tiered systems sit somewhere in the middle. In addition, microservice-based systems, and to a lesser extent tiered systems, were less prone to technology lock-in, and more suitable for multi-team development than monolithic systems. Read about web application architectures ↗ Comparison of the standardization processes of ECMAScript, HTML, and CSS (Juhana Laakso, 2025, BSc) ↗ ECMAScript, HTML, and CSS are some of the main technologies of the Internet. Each of these languages is standardized using a different process and by a different organization. The standardization process of a programming language can impact how the language is developed and how widely it is used. Therefore, understanding and comparing standardization processes can help understand the current state and development of these languages. This thesis aims to describe the current standardization processes of the three languages in a comparable way and to identify the key similarities and differences of the processes by investigating the following research question through a literature review: What are the key similarities and differences in how ECMAScript, HTML, and CSS are standardized? Three key similarities in the standardization of the languages were identified: (1) global technology organizations have decision making power in the standardization organizations, (2) contributing is generally open to anyone, but decisions are made by appointed individuals, and (3) the standardization processes and decision making are publicly documented. In addition, four key differences were identified. (1) the processes and criteria for making changes are different for each standard, (2) decision making differs from the consensus based decisions of ECMAScript and CSS, to the editor based decisions of HTML, (3) the structure of the standards differs, from the single HTML standard document to the CSS modular standard, and (4) the publication cadences of the standards differ from the constantly updated HTML standard, to the annually updated ECMAScript standard. Further research could analyze the weaknesses and strengths of the three standardization processes in relation to each other. Read about web standardization ↗ Adapting SQLite to the Distributed Edge: A Comparative Study of Different Adaptations (Kalle Ahlström, 2025, BSc) ↗ This thesis is a comparative study of different SQLite adaptations and their viability for Distributed Edge Computing environments. The four adaptions chosen for closer analysis are FaaSFS, LiteFS, libSQL, and rqlite. An ideal architecture is presented and that is used as a basis for the comparison between the adaptations. None of the solutions studied implement the ideal architecture. Each has different trade-offs, making the selection process of what to use use-case specific. The main trade-offs highlight significant differences between write performance, stronger consistency guarantees, and/or increased read latency. According to the CAP theorem, distributed systems can’t fully guarantee consistency, availability, and partition tolerance simultaneously. Empirical analysis of the chosen adaptations indicates that implementation designs inherently favor either the CA or AP model, thereby substantiating the theorem. Read about SQLite on distributed edge ↗ Survey of web API definition languages (Niklas Saarikoski, 2025, BSc) ↗ Web Application Programming Interfaces (APIs) are the backbone of modern software development, enabling communication between diverse applications and platforms.To support the different needs, a variety of web API technologies have emerged, each with its own architecture, data transmission protocols, and design philosophies. This bachelor’s thesis introduces existing web APIs, examines applications developed for them, and evaluates their advantages and disadvantages. The comparison considers the popularity, efficiency, and architectural security of these APIs. The research has been conducted as a literature review, exploring existing materials to identify previous studies and potential gaps in the research. The comparison focuses on four web API technologies: RPC (Remote Procedure Call), SOAP (Simple Object Access Protocol), REST (Representational State Transfer), and GraphQL (Graph Query Language). These APIs represent the vast majority of web APIs in use today, and provide a good look in to the different limitations brought on with certain design choices Currently, the development of entirely new web API technologies seems unlikely. Although existing solutions have clear weaknesses, they are often offset by the strengths of other technologies. Nevertheless, in the future, new use cases might emerge that demand processes beyond the capabilities of current web API technologies. Read about API definition languages ↗ Survey of Edge Databases for the Web (Arttu Pesonen, 2024, BSc) ↗ Database as a Service offerings have transformed the development of web applications, enabling almost limitless scalability of databases according to the capacity and performance requirements. With the growth of global user bases in web applications, the use of traditional database systems can lead to high latency, as the database is often located far from the end users. Edge databases aim to bring data processing closer to the end users, reducing latency and improving service performance. While cloud computing has enabled the deployment of traditional databases in regions with the highest concentrations of end users, it has not fully addressed the challenges of growing global user bases. This thesis examines edge databases and their use in the context of web applications through a literature review and by comparing different edge database service providers. This study seeks to identify the edge databases designed for web applications and explore their features and design approaches. The technical review found that all the compared edge database solutions are compatible with existing database technologies and models: CockroachDB is compatible with PostgreSQL, Redis Cloud with Redis, and Turso with SQLite. This compatibility simplifies the adoption of the services, as developers can use familiar tools and programming languages, and integrate the services directly into existing web applications. All three compared edge database services enable extensive scalability by leveraging the infrastructure of major cloud service providers for deployment. Edge databases are especially beneficial for web applications that require precise management of database locations, as this has a significant impact on the latency experienced by end users. By using edge databases, web applications can improve their usability and customer experience by reducing service latency. Read about edge databases ↗ Comparison of web performance optimization techniques -1990s vs. 2020s (Klaus Rehnberg, 2024, BSc) ↗ The transition from web sites to web applications has led to numerous changes in web optimization methods. An understanding of the evolution of optimization methods is paramount for understanding why the current optimization methods are in use. In this thesis I compare web optimization methods used in the 1990s and methods used in modern web development. The methods I analyze in this thesis are limited to methods that have a measurable impact on user perceived latency, data throughput and resource usage of web servers. The literature survey made in this thesis shows that no previous works of this kind have been made from a high level overview. To keep itself on a high level, this thesis includes a multitude of sources covering multiple optimization methods. The results of the survey indicate that optimization methods have improved in multiple regards. Not only have existing methods improved, but new methods have been created to match the new requirements of web applications. Additionally, the focus of optimization methods has shifted from reducing the impact of low network bandwidth, to instead covering dynamic web data, which can be modified to suit a specific user, and the growing number of mobile devices, which have varying screen sizes and resolutions. Web servers have also moved from local servers to cloud and edge computing. Read about web performance optimization ↗ Survey of the current state of 3D production pipelines for the web (Lauri Lyytikäinen, 2024, BSc) ↗ This paper aims to find out what is the current state of 3D production for the web. The research focuses on examining the process of creating 3D content, optimising it, and integrating it into a final product. It contains an overview of the long and complicated process of creating content for web-based platforms. The review was conducted as the current research on the topic is limited or the available information is several years old. The sources used were scientific articles and books about the topic, programming library documentation and programming articles. The research presents the different steps and tools available for creating good quality and functional 3D content for web applications. The paper outlines how 3D data is created, edited, and exported and the different applications for it. How the different libraries, frameworks and tools can be used heavily depends on the final content’s specific purpose and use case, budget and target audience. The survey also explores the different criteria that the developers can use to select their libraries and pipelines, and when it might be better to create a custom implementation. The different applications of 3D content and their unique differences are also investigated. My main findings were that 3D content in web applications is growing in popularity, and new uses for it are discovered continuously. While 3D technology has been around for multiple decades, it still is relatively new on the web platform. It is being avoided because of a complicated development process, technical limitations and the lack of standardisation. Different libraries and programming languages have greatly evolved in recent years and the standards in the industry are still forming. Read about 3D production for the web ↗ Understanding re-emergence of the RPC model in web development (Ruupert Koponen, 2024, BSc) ↗ RPC is a request-response protocol from the 1980s, which allows developers to invoke remote functions from an application. It was originally used in distributed systems, but was also used in web development in the late 1990s and early 2000s. RPC’s popularity began decreasing after the REST-style architecture appeared in the early 2000s. However, in the recent years, the RPC-model has re-emerged in web development. This bachelor’s thesis focuses on understanding the recent growth in popularity of the RPC model. In addition, this work explores the impact of modern RPC frameworks on web development practices and offers comparison between REST, RPC and GraphQL. This thesis is a literature review that utilizes scientific articles, technological documentation and blog posts. This study found out that in the early 2000s, web development moved from RPC to REST architecture due to the low performance of RPC implementations at the time. The internet was growing rapidly, requiring scalable and high-performance web services, and REST answered to this demand. The 2010s saw new trends in web development, such as microservices and TypeScript. These trends led to the emergence of new RPC frameworks, such as gRPC and tRPC. These modern RPC frameworks leverage advancements in network protocols, serialization formats, and type systems to offer an alternative to the REST architectural style. gRPC is especially popular in microservices systems due to its high performance, whereas tRPC offers developers using TypeScript the ability to develop type-safe full-stack applications. The RPC model has also been integrated into the popular front-end framework React, which provides the ability to call server-side methods directly from client-side components. With the emergence of modern RPC frameworks, developers have more options in web service development tools. Developers have access to more specialized tools and can choose the one that best suits their needs. Although modern RPC implementations may not be as universally applicable as REST or GraphQL, they can offer significant benefits in certain types of applications. gRPC and tRPC streamline the development of web services by offering an improved developer experience. Additionally, they reduce the risk of errors through type safety. Read about the RPC model ↗ Survey of Serverless Edge Computing for Web Applications (Mikael Siidorow, 2024, BSc) ↗ Cloud computing has revolutionized the way we build software with infrastructure and computing power available always on demand. Serverless computing has allowed developers to focus on applications instead of infrastructure management. However, large data center are often far away from the end users, which introduces latency. Edge computing attempts to bring computing closer to the users, to the edge. Edge computing is already widely used in Internet of Things and mobile devices, and there exists a large amount of research this area. Web applications already use edge technologies such as Content Delivery Networks, but edge computing for dynamic computation is not yet widely used. This thesis reviews edge computing for web applications and summarizes research and service providers as literature research. The aim of the study is to determine what are the benefits and limitations of serverless edge computing compared to serverless cloud computing for web application development. The technical review showed that edge computing service providers were split in two based on the internal runtime: AWS uses micro virtual machines, while Cloudflare and Deno use V8 isolates. V8 isolates start faster with less overhead, but their technologies are more limited and security is less obvious than virtual machines. Serverless edge and cloud computing are not mutually exclusive technologies. The benefits of edge computing come from both closer location and faster runtimes. Edge is suitable for latency-critical parts of the application and V8 isolates significantly reduce load times. When developing serverless applications, some computation should be moved to the edge. Many web applications could improve usability and user experience by moving computation to the edge, reducing latency. Read about serverless edge computing ↗ Using Storybook.js for component-driven design system web development (Tuomas Nummela, 2024, BSc) ↗ Building web application user interfaces has become increasingly complex due to heightened expectations and requirements in interface customizability, visual appeal, performance, and accessibility. This has given birth to frontend tools like Storybook.js that help developers manage the development complexity through component isolation and test automation. Storybook is mainly used by developers to build and maintain design systems that can be used to construct UIs across applications regardless of the different application contexts. This thesis explores developer experiences with using Storybook to build and maintain design systems, identifying some benefits and drawbacks of the tool in the process. The developer experiences are inspected from the task viewpoints of designer-developer-handoff, component programming, and component testing. For each task, the Storybook way of approaching it is explained first. That is followed by a case study of using Storybook to help with that task in a software company. Finally, some observations are made from the experiences of using Storybook for that specific task. The final discussion presents and argues for four observations about Storybook. Firstly, Storybook offers approachable component workshopping. Secondly, Storybook doubles well as rich component documentation. Thirdly, there exist numerous add-ons to further leverage the use of Storybook. Finally, to fully | 2026-01-13T08:48:42 |
https://docs.suprsend.com/reference/cli-workflow-overview | Commands and Flags - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations 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 Commands and Flags Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Workflow Commands and Flags OpenAI Open in ChatGPT Reference for managing workflows in the SuprSend CLI. OpenAI Open in ChatGPT Workflows define the notifications logic in SuprSend. You can use CLI command to manage workflows - list, push, pull, enable, disable. Syntax Copy Ask AI suprsend workflow [command] Commands Command Description workflow list List workflows in a workspace workflow push Push workflows from local directory to SuprSend workflow pull Pull workflows from SuprSend to local directory workflow enable Enable a workflow workflow disable Disable a workflow Inherited Global Flags This command also supports Global Flags , such as: -s, --service-token – Service token for authentication -v, --verbosity – Logging level --config – Config file path -n, --no-color – Disable color output -w, --workspace string – Workspace to use (default: staging ) Was this page helpful? Yes No Suggest edits Raise issue Previous List Workflows List workflows in a workspace Next ⌘ I x github linkedin youtube Powered by On this page Syntax Commands Inherited Global Flags | 2026-01-13T08:48:42 |
https://dev.to/codemouse92 | Jason C. McDonald - 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 Jason C. McDonald Author. Speaker. Time Lord. (Views are my own) Location Time Vortex Joined Joined on Jan 31, 2017 Email address codemouse92@outlook.com Personal website https://codemouse92.com github website twitter website Pronouns he/him Work Author of "Dead Simple Python" (No Starch Press) Eight Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least eight years. Got it Close 5 Top 7 Awarded for having a post featured in the weekly "must-reads" list. 🙌 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 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 Tag Moderator 2022 Awarded for being a tag moderator in 2022. Got it Close Trusted Member 2022 Awarded for being a trusted member in 2022. 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 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 DevDiscuss Podcast Guest Awarded to DEV community members who appeared as guests on the DevDiscuss podcast 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 Fab 5 Awarded for having at least one comment featured in the weekly "top 5 posts" list. Got it Close She Coded Rewarded to participants in our annual International Women's Day event, either via #shecoded, #theycoded or #shecodedally 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 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 Beloved Comment Awarded for making a well-loved comment, as voted on with 25 heart (❤️) reactions by the community. 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 Show all 23 badges More info about @codemouse92 Organizations MousePaw Media The Bug Hunters Café GitHub Repositories wordperil A word puzzle party game. Python dkim_manage A script to automate most tasks associated with OpenDKIM key rotation. Shell • 5 stars Timecard Track time beautifully. Python • 26 stars dicebox Roll dice, flip coins, and simulate other decision-making methods. Python • 5 stars DEVModInACan Canned moderation messages and comments for DEV. 13 stars Elements A modern music library application. Python • 1 star no-monster-minecraft A data pack for Minecrafters who like playing without monsters. mcfunction • 15 stars WacomTouchToggle Easily turn on and off touchpad capabilities for Wacom tablets (such as the Wacom Bamboo) Shell • 1 star Skills/Languages Management and business analysis for complex and high-risk projects. Python and C++ expert. Legacy code modernization. Mentorship, building high-performance teams, running internships. Currently hacking on Quantified Tasks Available for Speaking, podcasts, consulting. Post 121 posts published Comment 2138 comments written Tag 27 tags followed Pin Pinned Dead Simple Python: Working with Files Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Dec 21 '19 Dead Simple Python: Working with Files # python # beginners 182 reactions Comments 11 comments 12 min read Three Ground Rules for Sane Project Planning Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Oct 1 '19 Three Ground Rules for Sane Project Planning # management # coding # project # planning 83 reactions Comments 3 comments 8 min read How To Become A Developer -- Part 1: Coding Skills Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Aug 6 '19 How To Become A Developer -- Part 1: Coding Skills # beginners # career 325 reactions Comments 7 comments 7 min read The Rules of Debugging Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Feb 16 '19 The Rules of Debugging # coding # culture # humor 197 reactions Comments 8 comments 8 min read Clean, DRY, SOLID Spaghetti Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Jul 24 '18 Clean, DRY, SOLID Spaghetti # oop # coding # culture # design 287 reactions Comments 37 comments 9 min read Searching Outside the Box (OTB Ep 9: Anna Greene-Hicks) Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Dec 13 '24 Searching Outside the Box (OTB Ep 9: Anna Greene-Hicks) # career # jobsearch # interview # resume 1 reaction Comments Add Comment 1 min read Want to connect with Jason C. McDonald? Create an account to connect with Jason C. McDonald. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in Networking Your Next Role (OTB Ep 8: Marlon Peseke) Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Dec 6 '24 Networking Your Next Role (OTB Ep 8: Marlon Peseke) # career # jobsearch # interview # resume Comments Add Comment 1 min read Navigating Expectations (OTB Ep 7: JJ Brenner) Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Nov 22 '24 Navigating Expectations (OTB Ep 7: JJ Brenner) # career # jobsearch # interview # resume Comments Add Comment 1 min read Challenging Bias in Hiring (OTB Ep 6: Todd Lucas) Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Nov 15 '24 Challenging Bias in Hiring (OTB Ep 6: Todd Lucas) # career # jobsearch # interview # resume 1 reaction Comments Add Comment 1 min read Transcending the Niche (OTB Ep 5: Paul Hardin) Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Nov 8 '24 Transcending the Niche (OTB Ep 5: Paul Hardin) # career # jobsearch # interview # resume Comments Add Comment 1 min read Taking on New Challenges (OTB Ep 4: Ned Batchelder) Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Nov 1 '24 Taking on New Challenges (OTB Ep 4: Ned Batchelder) # career # jobsearch # interview # resume 5 reactions Comments 1 comment 1 min read Leveraging Job Hopping (OTB Ep 3: Abraham Vanderpool) Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Oct 30 '24 Leveraging Job Hopping (OTB Ep 3: Abraham Vanderpool) # jobsearch # career # resume # interview 2 reactions Comments Add Comment 1 min read Overcoming Imposter Syndrome (OTB Ep 2: Monica Ayhens-Madon) Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Oct 28 '24 Overcoming Imposter Syndrome (OTB Ep 2: Monica Ayhens-Madon) # career # jobsearch # interview # resume 1 reaction Comments Add Comment 1 min read Finding the Right Job (OTB Ep 1: Jennifer Rorex) Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Oct 25 '24 Finding the Right Job (OTB Ep 1: Jennifer Rorex) # career # jobsearch # resume # interview 1 reaction Comments Add Comment 1 min read Introducing "On The Board" Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Oct 25 '24 Introducing "On The Board" # career # resume # interview # jobsearch 7 reactions Comments 1 comment 1 min read How To Estimate Software Development Effort Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Sep 7 '23 How To Estimate Software Development Effort # agile # management # scrum # kanban 7 reactions Comments 1 comment 6 min read Training Juniors Remotely Is Possible. Here's How. Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Aug 28 '23 Training Juniors Remotely Is Possible. Here's How. # remote # management # workplace 14 reactions Comments 4 comments 11 min read Ten Principles of Critique Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Sep 30 '21 Ten Principles of Critique # culture # communication # community # codereview 34 reactions Comments 3 comments 5 min read Episode 9: Sneeze Decor Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for The Bug Hunters Café Jul 12 '21 Episode 9: Sneeze Decor # speaking # communities # mentorship # programming 2 reactions Comments Add Comment 1 min read Episode 8: More Power To You Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for The Bug Hunters Café Jul 8 '21 Episode 8: More Power To You # management # mentorship # leadership # teams Comments Add Comment 1 min read Episode 7: Brain Scans and Networking Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for The Bug Hunters Café Jun 16 '21 Episode 7: Brain Scans and Networking # datascience # python # career # ux Comments Add Comment 1 min read Episode 6: Mentorship with Cheese Sauce Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for The Bug Hunters Café Jun 1 '21 Episode 6: Mentorship with Cheese Sauce # teaching # learning # programming # mentorship 10 reactions Comments 3 comments 1 min read Six Things You Thought Senior Devs Did (But We Don't) Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow May 21 '21 Six Things You Thought Senior Devs Did (But We Don't) 295 reactions Comments 58 comments 3 min read Episode 5: Bojan Reads the Documentation Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for The Bug Hunters Café May 3 '21 Episode 5: Bojan Reads the Documentation # agile # scrum # management 2 reactions Comments Add Comment 1 min read Episode 4: Attack of the Fresh Fruit Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for The Bug Hunters Café Apr 19 '21 Episode 4: Attack of the Fresh Fruit 4 reactions Comments Add Comment 1 min read Episode 3: To Boldly Debug Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for The Bug Hunters Café Apr 8 '21 Episode 3: To Boldly Debug # debugging # python # devops # sre 3 reactions Comments Add Comment 1 min read News: Call to remove RMS from FSF Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Mar 24 '21 News: Call to remove RMS from FSF # news # inclusion 19 reactions Comments 6 comments 4 min read Type Literal Tabs Anywhere Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Nov 28 '20 Type Literal Tabs Anywhere # linux # tooling 14 reactions Comments 1 comment 2 min read Writing Zenlike Python (Talk) Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Sep 15 '20 Writing Zenlike Python (Talk) # python # beginners 13 reactions Comments Add Comment 1 min read How to rename 'master' in an organization Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for MousePaw Media Jul 7 '20 How to rename 'master' in an organization # devops # inclusion # git 14 reactions Comments Add Comment 4 min read Ask Guido van Rossum a question! Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for EuroPython Jul 6 '20 Ask Guido van Rossum a question! # python 12 reactions Comments Add Comment 1 min read 5 Ways to Retain Open Source Contributors Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Jul 6 '20 5 Ways to Retain Open Source Contributors # opensource # culture # projectmanagement 41 reactions Comments 4 comments 5 min read Goodbye Master, Hello...What? Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for MousePaw Media Jun 29 '20 Goodbye Master, Hello...What? # devops # culture # inclusion # git 29 reactions Comments 19 comments 3 min read Development Log: One Month In Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for MousePaw Media Jun 29 '20 Development Log: One Month In # python # contributorswanted # hackathon # gamedev 8 reactions Comments 1 comment 3 min read Development Log: All About Structure Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for MousePaw Media Jun 12 '20 Development Log: All About Structure # python # gamedev # hackathon # contributorswanted 33 reactions Comments Add Comment 6 min read Development Log: Planning a Game Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for MousePaw Media May 26 '20 Development Log: Planning a Game # contributorswanted # hackathon # python # gamedev 28 reactions Comments 1 comment 3 min read How to Apologize Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow May 25 '20 How to Apologize # culture # triplebyte 170 reactions Comments 8 comments 5 min read Are you a ladder or a roadblock? Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow May 20 '20 Are you a ladder or a roadblock? # career # culture # diversity 28 reactions Comments 7 comments 8 min read Windows and Linux: A Sane Discussion Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow May 16 '20 Windows and Linux: A Sane Discussion # discuss # healthydebate 47 reactions Comments 55 comments 2 min read GAME MODE 2020: Building a Game in One Month Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow for MousePaw Media Apr 30 '20 GAME MODE 2020: Building a Game in One Month # contributorswanted # hackathon # python # gamedev 55 reactions Comments 9 comments 2 min read Debugging with SQrL Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Apr 1 '20 Debugging with SQrL # jokes 4 reactions Comments Add Comment 1 min read Pair Programming: Dog Edition Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Feb 1 '20 Pair Programming: Dog Edition # jokes 50 reactions Comments 4 comments 1 min read Social Lifespan of Posts Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Jan 29 '20 Social Lifespan of Posts # discuss # meta 54 reactions Comments 30 comments 4 min read Turning Bugs Into Features Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Jan 14 '20 Turning Bugs Into Features # healthydebate # debugging # discuss 51 reactions Comments 2 comments 2 min read Socks Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Jan 8 '20 Socks # watercooler 18 reactions Comments 5 comments 1 min read Introducing: Timecard Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Dec 30 '19 Introducing: Timecard # showdev # python 63 reactions Comments 11 comments 6 min read The Use-Case Paradox Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Nov 30 '19 The Use-Case Paradox # coding # philosophy 7 reactions Comments Add Comment 1 min read 8 Ways to Be More Professional Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Nov 7 '19 8 Ways to Be More Professional # career # beginners 240 reactions Comments 28 comments 9 min read Python SnakeBytes: Unpacking Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Nov 5 '19 Python SnakeBytes: Unpacking # python # coding 19 reactions Comments 2 comments 1 min read What's Your Costume? Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Oct 31 '19 What's Your Costume? # watercooler # discuss 15 reactions Comments 9 comments 1 min read 10 Skills of a Professional Author Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Oct 28 '19 10 Skills of a Professional Author # writing 57 reactions Comments 3 comments 8 min read A Day In The Life Of A Writer Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Oct 24 '19 A Day In The Life Of A Writer # writing 25 reactions Comments 5 comments 6 min read Python SnakeBytes: The Walrus Operator Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Oct 21 '19 Python SnakeBytes: The Walrus Operator # python # coding 41 reactions Comments 7 comments 1 min read Has Stack Overflow Become An Antipattern? Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Oct 19 '19 Has Stack Overflow Become An Antipattern? # culture 316 reactions Comments 109 comments 7 min read Beware Counterfeit No Starch Books from Amazon! Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Oct 13 '19 Beware Counterfeit No Starch Books from Amazon! # news # books 11 reactions Comments Add Comment 1 min read Compiled! An Unobfuscated Glossary Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Sep 6 '19 Compiled! An Unobfuscated Glossary # programming # coding # compiling # building 68 reactions Comments 4 comments 13 min read What Is An "Interpreted" Language? Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Sep 1 '19 What Is An "Interpreted" Language? # healthydebate # discuss 33 reactions Comments 31 comments 3 min read Introducing #devjournal Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Aug 30 '19 Introducing #devjournal # devjournal # meta 106 reactions Comments 8 comments 2 min read Stealing Isn't "Sharing" Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Aug 22 '19 Stealing Isn't "Sharing" # culture # ethics 53 reactions Comments 50 comments 11 min read Let's Get Clever #2: Spades Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Aug 20 '19 Let's Get Clever #2: Spades # challenge # fun # coding # programming 11 reactions Comments Add Comment 4 min read Let's Get Clever #1: Fibonacci Sequence Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Aug 13 '19 Let's Get Clever #1: Fibonacci Sequence # challenge # fun # coding # programming 44 reactions Comments 56 comments 2 min read The Dark Side Of The Magic Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Aug 12 '19 The Dark Side Of The Magic # career # beginners # programming 68 reactions Comments 50 comments 6 min read Dead Simple Python: Lambdas, Decorators, and Other Magic Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Aug 7 '19 Dead Simple Python: Lambdas, Decorators, and Other Magic # python # beginners # functional 125 reactions Comments 15 comments 14 min read How To Become A Developer -- Part 4: Recommended Reading Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Aug 6 '19 How To Become A Developer -- Part 4: Recommended Reading # beginners # career 118 reactions Comments 1 comment 2 min read How To Become A Developer -- Part 3: People Skills Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Aug 6 '19 How To Become A Developer -- Part 3: People Skills # beginners # career 89 reactions Comments 10 comments 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:48:42 |
https://survivejs.com/research/ | SurviveJS - Research Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... Research For the completion of my doctorate, I produced several papers and you can find all of the papers I have written at ORCID ↗ . I have listed several on this page in addition to other works, including works of my students (MSc, BSc). Dissertation – Emergence of hybrid rendering models in web application development (2025) # Web is the largest application platform available globally as at least 60% of humanity has access to it [52]. The situation has been enabled by the almost ubiquitous nature of the internet and broad access to it. The popularity of the web platform comes with its challenges, as it was originally designed for static content and evolved to support application development. The continuous process of evolution has forced developers to evaluate their development practices from time to time. Simultaneously, the demands for the quality of web applications have increased and so has their size as their size has tripled over the past ten years [22]. The development contradicts the global trend of increased web usage through mobile devices, where bandwidth and computational power are limited by definition. Due to the prevailing trends of increasing application size and mobile usage, new, more effective ways to develop web applications are needed. This dissertation captures the current situation of web development while providing directions on how to address the industry’s current pain points. The dissertation shows how web developers can apply niche techniques and technologies to improve their applications on all levels while delivering faster and better user experiences without forgetting developer experience. Examining so-called hybrid rendering techniques and edge computing, I show what web development might become in the years to come and propose solutions beyond what is available in the mainstream. The primary purpose of this dissertation is to explore the space between static and dynamic web development to open new venues for web developers through novel techniques and technologies without forgetting users. Read the dissertation at ResearchGate ↗ View the defense at YouTube ↗ Papers # My research focuses mainly on static site generation, edge computing, islands architecture, and web architectures. You can get the best overview of my research outputs through ORCID ↗ , ResearchGate ↗ , or Google Scholar ↗ . I have listed several of my main papers below and you can find more from the aforementioned sources. Perspectives and potential issues in using artificial intelligence for computer science education (2025, preprint) ↗ Since its launch in late 2022, ChatGPT has ignited widespread interest in Large Language Models (LLMs) and broader Artificial Intelligence (AI) solutions. As this new wave of AI permeates various sectors of society, we are continually uncovering both the potential and the limitations of existing AI tools. The need for adjustment is particularly significant in Computer Science Education (CSEd), as LLMs have evolved into core coding tools themselves, blurring the line between programming aids and intelligent systems, and reinforcing CSEd’s role as a nexus of technology and pedagogy. The findings of our survey indicate that while AI technologies hold potential for enhancing learning experiences, such as through personalized learning paths, intelligent tutoring systems, and automated assessments, there are also emerging concerns. These include the risk of over-reliance on technology, the potential erosion of fundamental cognitive skills, and the challenge of maintaining equitable access to such innovations. Recent advancements represent a paradigm shift, transforming not only the content we teach but also the methods by which teaching and learning take place. Rather than placing the burden of adapting to AI technologies on students, educational institutions must take a proactive role in verifying, integrating, and applying new pedagogical approaches. Such efforts can help ensure that both educators and learners are equipped with the skills needed to navigate the evolving educational landscape shaped by these technological innovations. Read about usage of AI for CSEd ↗ Challenges related to approximating the energy consumption of a website (2025) ↗ Based on a rough estimate, the ICT industry consumes 7 to 10% of the world’s energy, and around 70% of this is related to usage while the rest can be considered embodied due to manufacturing, logistics, and related activities. Simultaneously, the web has become an important channel for consuming ICT services as it is the largest available application platform globally. Especially energy consumption of mobile web applications has been studied in detail, but there is a clear research gap for web applications because suitable measurement tooling has not been available earlier.The purpose of this article is to review the current state of the art and understand how to approximate the energy consumption of web applications effectively by measuring an existing website that has been implemented with two different web frameworks—Qwik and Next.js. Our main findings indicate that although services that approximate energy consumption of web applications exist, they tend to overestimate consumption when compared to our measurements and they may even show contradictory results between different web frameworks. Further, we found that Firefox Profiler can be used to measure energy consumption with high precision. We also found that Website Carbon service fails to acknowledge techniques, such as lazy rendering, and there were open questions related to hosting detection (green or not) while the service was not transparent in calculating the results—not disclosing intermediary results or exposing the scope of the calculation. Our key recommendation is to use CPU-based measurement methods in estimating web energy consumption. Read about website energy consumption ↗ The Potential of Serverless Edge-powered Islands for Web Development (2025) ↗ Web developers face two significant challenges when developing their applications and websites: latency and payload size. Given that web services rely on servers, the related communication incurs a cost in terms of latency. In contrast, the payload passed to the client incurs a communication cost, not to mention the computational cost to the client. The concept of serverless edge computing, built on top of content delivery networks (CDNs), is an approach that has begun to gain the attention of web developers for its promise of lower latencies due to its efficiencies in communication thanks to globally distributed networks and replication. Islands architecture is a technical approach that addresses payload size by giving developers easy ways to defer and potentially even avoid the cost of loading content. Combined, these two approaches form edge-powered islands and, in this article, we examine how the combination can help to address these two notable costs web developers have to consider in their daily work. Our findings indicate that edge-powered islands can provide a way to introduce interactivity to otherwise static websites while wrapping dynamic portions of a page within islands to gain the benefits of static approaches in more dynamic contexts, such as storefronts. In addition, islands can provide loading benefits even for more application-like websites, such as social networks, and give web developers an additional control layer in their development work. Read about edge-powered islands ↗ Overview of Web Application Performance Optimization Techniques (2025) ↗ During its thirty years of existence, the World Wide Web has helped to transform the world and create digital economies. Although it started as a global information exchange, it has become the most significant available application platform on top of its initial target. One of the side effects of this evolution was perhaps suboptimal ways to deliver content over the web, leading to wasted resources and business through lost conversions. Technically speaking, there are many ways to improve the performance of web applications. In this article, we examine the currently available options and the latest trends related to improving web application performance. Read about web performance ↗ Resumability — A New Primitive for Developing Web Applications (2023) ↗ Hydration is a common technique employed by current JavaScript-based frontend frameworks, such as React. In hydration, the application code is re-executed on the client to recover component boundaries, application state, and event listeners. In this article, we look into a new primitive called resumability that avoids thework as the necessary information is serialized into HTML. The idea has been adopted by Asta (2023), Google Wiz, Marko (planned for version 6 [1]), Sidewind (since 2022), and Qwik (2021) as a main building block. Resumability gives these solutions unique advantages by avoiding the cost of hydration. Furthermore, resumability can allow developers to leverage code-splitting out of the box, depending on the implementation. The shift has implications for both developer and user experience. This article aims to understand why resumability matters and why it is a good option for replacing earlier hydration-based approaches. We also consider challenges related to adopting resumability on a framework level and briefly highlight the first resumable solutions for developing web applications. Read about resumability ↗ ECMAScript - The journey of a programming language from an idea to a standard (2023) ↗ A significant portion of the web is powered by ECMAScript. As a web technology, it is ubiquitous and available on most platforms natively or through a web browser. ECMAScript is the dominant language of the web, but at the same time, it was not designed as such. The story of ECMAScript is a story of the impact of standardization on the popularity of technology. Simultaneously, the story shows how external pressures can shape a programming language and how politics can mar the evolution of a standard. In this article, we will go through the movements that led to the dominant position of ECMAScript, evaluate the factors leading to it, and consider its evolution using the Futures Triangle framework and the theory of standards wars. Read about ECMAScript ↗ The Rise of Disappearing Frameworks in Web Development (2023) ↗ The evolution of the web can be characterized as an emergence of frameworks paving the way from static websites to dynamic web applications. As the scope of web applications has grown, new technical challenges have emerged, leading to the need for new solutions. The latest of these developments is the rise of so-called disappearing web frameworks that question the axioms of earlier generations of web frameworks, providing benefits of the early web and simple static sites. Read about disappearing frameworks ↗ The State of Disappearing Frameworks in 2023 (2023) ↗ Disappearing frameworks represent a new type of thinking for web development. In the current mainstream JavaScript frameworks, the focus has been on developer experience at the cost of user experience. Disappearing frameworks shift the focus by aiming to deliver as little, even zero, JavaScript to the client. In this paper, we look at the options available in the ecosystem in mid-2023 and characterize them in terms of functionality and features to provide a state-of-the-art view of the trend. We found that the frameworks rely heavily on compilers, often support progressive enhancement, and most of the time support static output. While solutions like Astro are UI library agnostic, others, such as Marko, are more opinionated. Read about disappearing frameworks ↗ Implications of Edge Computing for Static Site Generation (2023) ↗ Static site generation (SSG) is a common technique in the web development space to create performant websites that are easy to host. Numerous SSG tools exist, and the approach has been complemented by newer approaches, such as Jamstack, that extend its usability. Edge computing represents a new option to extend the usefulness of SSG further by allowing the creation of dynamic sites on top of a static backdrop, providing dynamic resources close to the user. In this paper, we explore the impact of the recent developments in the edge computing space and consider its implications for SSG. Read about edge computing and SSG ↗ Booklets # As a part of coursework, I authored a short booklet under the title “Disappearing frameworks explained”. The booklet was published in 2023 through arXiv. ↗ Lectures # I give a yearly lecture titled “Web application development - The past, the present, the future”. You can find the 2024 slides of the lecture here ↗ . Advisory work # During my studies, I have worked as an advisor for several theses. You can find a selection below. Masters # Artificial Intelligence for Web Development: Perspectives from Industry and Literature (Pyry Pohjalainen, 2025, MSc) ↗ The integration of generative AI is transforming industries, enhancing efficiency and user experience, while introducing new opportunities and challenges to web development. The AI era-defining release of ChatGPT has cemented AI tools in the toolkits of people working in web development, as previously labor intensive tasks such as programming and debugging could possibly be outsourced to the AI – this, however, has brought up new issues of when the utilization of AI is useful, which tasks should the developer complete without AI, and what effects can be found from the utilization of AI for tasks previously seen as out of reach for machines. Given this, the objective of this study is to clarify the effect the utilization of AI has had on web development using the sequential qualitative-quantitative design method with interviews and a survey to validate and expand upon the findings from the interviews. This study finds that AI is used by people working in web development to increase efficiency and for the ease of use it provides, with multiple minor downsides, such as AI not being able to understand complex logic, everything created by an AI needing to be validated by the user and AI suggesting code which could potentially cause a security issue. This means there are clear benefits to continued development of AI tools for web development and an increased role of AI proficiency for people working in web development, with the user knowing when to utilize AI to receive the optimal results, with open questions and possibilities of future research being directed towards code quality of AI tools. Read about AI in web development ↗ FlagShip: Reimagining Stateful Serverless Architectures at the Edge (Anoop Bidikar, 2024, MSc) ↗ Feature flag systems enable dynamic control of application features without code redeployment, playing a crucial role in modern software development. While edge computing and serverless architectures offer promising solutions for low-latency applications, integrating stateful services into these environments presents significant challenges. This research investigates how stateful services in commercial edge computing platforms influence the feasibility and performance of stateful serverless applications, through the implementation and evaluation of a feature flag management system. We developed FlagShip, an edge-based feature flag management system utilizing stateful serverless functions and storage services from a commercial edge platform provider. Through extensive evaluation, we compared FlagShip’s performance against traditional cloud-hosted feature flag services, analyzing metrics such as client-side and server-side latency across different deployment configurations. Our results demonstrate that FlagShip achieved up to 70% reduction in client-side latency and 93% decrease in server-side latency compared to baseline implementations. Notably, a cached cloud-hosted variant outperformed all implementations, including edge deployments, challenging conventional assumptions about edge computing’s performance advantages. These findings provide valuable insights into the practical implications of building stateful edge applications, highlighting the critical role of storage and caching solutions that operate within the same runtime environment. Read about serverless architectures ↗ See also Anoop's blog post about the topic ↗ The potential of WebAssembly in Edge Computing (Antti Nousiainen, 2024, MSc) ↗ WebAssembly is a well-supported web technology that allows easy conversion of existing code as well as generation of new projects from a multitude of programming languages for the web, in a portable manner. Edge environments, meanwhile, provide a way to distribute workloads near the end user, and allow scaling of execution well. Furthermore, edge environments offer the possibility of decreased latency compared to more conventional cloud services. Combining these could improve the usability and suitability of edge computing in certain kinds of applications, such as data processing for Internet-of-Things (IoT) devices. Therefore, research into combining these technologies makes sense. The objective of this thesis was to study this intersection of WebAssembly and edge environments through examination of performance and usability. Performance was considered through creating a test environment and by benchmarking WebAssembly, while usability was considered by documenting in detail potential problems for developers and the ways how WebAssembly and edge environments can be used together. Overall, the thesis found that even though some roadblocks were encountered during the test environment development and performance was decreased in comparison to locally executed tests, existing C-based benchmarks could be converted to WebAssembly and be run in the selected edge environment with acceptable performance when compared to locally executed tests. Read about WebAssembly in Edge Computing ↗ Impact of React component libraries on developer experience - An empirical study on component libraries' styling approaches (Ossian Rajala, 2024, MSc) ↗ Over the past three decades, web design has transitioned from simple static pages to complex, interactive applications. Modern web development relies heavily on JavaScript frameworks and reusable components, often utilizing third-party, pre-styled component libraries. Customizing the styles - which are typically implemented with CSS (Cascading Style Sheets) - of such libraries to meet specific design requirements is a common task. This customization creates a need for effective styling solutions that enhance developer experience and maintainability. Despite its widespread use in web development, CSS remains under-researched, particularly in the context of how it affects developers’ day-to-day work with component libraries. As technologies continue to evolve, understanding and improving the developer experience becomes increasingly crucial, as it can positively impact software development outcomes. This thesis seeks to understand how React component libraries’ theming approaches impact customization, particularly ease of implementation, reusability of styles, and flexibility to accommodate various design requirements. Furthermore, the study investigates how the aforementioned factors and the library’s documentation support or hinder the developer’s work. These factors were investigated by porting the same application to four pre-styled component libraries. The implementation process, methods used, and challenges encountered were documented and analyzed. As a result, the study found that meeting the design requirements was possible with all compared libraries: Ant Design, Chakra UI, shadcn/ui, and Mantine. However, the ease, intuitiveness, and maintainability of required solutions varied. Especially as one of the libraries, Ant Design, was tightly coupled with a specific design system. Color customization and dark and light modes were frequent sources of confusion. Overall, the libraries offered a positive experience and allowed the desired design to be reached without resorting to style hacks. Still, all the libraries would benefit from improved documentation, namely more detailed examples and explanations of the customization options. Read about component libraries for React ↗ The Effects of Architectural Design Decisions on Framework Adoption: A Comparative Evaluation of Meta-Frameworks in Modern Web Development (Joel Hassan, 2024, MSc) ↗ The rise of JavaScript meta-frameworks has transformed the development of web applications in recent years. Alongside established frameworks, such as Next.js, more recent entrants, such as Astro and Qwik City have introduced novel approaches centred on simplifying developer experience and improving the perceived performance of applications for users. The competitive nature of the meta-framework space and the long-term impact of framework choice on projects calls for an understanding of the factors that drive framework adoption. This research first delineates extensibility, ease of migration and updates as a set of adoption factors based on prior research and their relevance to modern meta- frameworks. The factors form a basis of evaluating three meta-frameworks—Next.js, Astro, and Qwik City—selected based on their popularity, design, and phase on the innovation curve. A developer survey is conducted to complement the analysis, gathering insights from developers on the value they associate with architectural aspects and their personal experiences with the selected frameworks. The findings substantiate previous research that identified learnability and extensibility as primary adoption drivers. The main risks driving unadoption involve complexity associated with a high degree of configurability and the perceived framework lock-in due to an abundance of framework-specific concepts. Despite shared authoring experiences across evaluated meta-frameworks, the analysis indicates that newer frameworks are showing potential to considerably enhance user and developer experiences by focusing on a simplified authoring experience, addressing issues related to the transmission of application logic from the server to the client and providing more fine-grained approaches to managing client-side JavaScript. Read about framework adoption ↗ Improving the Initial Rendering Performance of React Applications Through Contemporary Rendering Approaches (Touko Lonka, 2023, MSc) ↗ Modern JavaScript frameworks have enabled the development of interactive and user-friendly web applications. Over the past decade, React has become the leading user interface framework in the JavaScript world, contributing to the rise of Single Page Applications (SPA). However, the extensive development of SPAs has led to an increase in the amount of client-side JavaScript, thus triggering performance issues in terms of initial loading times. The speed at which a web application is initially rendered can significantly influence its potential for revenue generation, as the initial loading time often determines whether a user stays on or abandons a web page. Recognizing the integral role of the initial loading speed in user retention, this study delves into the realm of performance optimization strategies, focusing predominantly on the use of React-like UI frameworks and meta-frameworks as a means to improve the initial rendering performance of web applications. Through this exploration, we aim to provide a comprehensive understanding of contemporary rendering approaches and their role in enhancing web application performance. To compare the performance impacts of various rendering approaches, we implement a React application simulating the dynamics of a real-world e-commerce platform and replicate the same application through multiple technologies. These technologies include the UI frameworks Preact, Qwik, and Solid, as well as the meta-frameworks Next, Astro, and Qwik City. Finally, we provide extensive benchmarks to measure the page weights and initial rendering performance of each application version. Our findings demonstrate that the utilization of React-like UI frameworks and meta-frameworks can considerably decrease the amount of JavaScript downloaded by the client, contributing to improved initial rendering times. The most promising results are achieved by using meta-frameworks for extending the capabilities of UI frameworks with modern rendering strategies like Server-Side Rendering and Static Site Generation. However, these approaches often present significant trade-offs, such as increased Server Response Times and extended build durations. Read about initial rendering performance ↗ Bachelors # Transforming Web Development with NLP and Vibe Coding Techniques (Joona Heinonen, 2025, BSc) ↗ With LLMs and AI getting significantly better in recent years, it has changed how web development is approached. This thesis aims to cover the changes that vibe coding and natural language programming bring to web development and what type of benefits and drawbacks might emerge. Vibe coding and fully delegating development to AI tools is a relatively new area in web development, which is the reason for this study. This study is conducted as a literature review going over papers and research related to vibe coding and no-code style programming in web development. Web development has shifted from manually writing code to generating code and tests with AI agents, which leaves resources for other parts of the process. Delegating development to AI has several levels depending on the amount of work left to the human developer, ranging from expert consultant to full delegation - in other words, using vibe coding. Vibe coding is defined as leaving everything to the “vibes” referring to fully letting the AI agent create and test the web application. Vibe coding can bring benefits to the user with its speed and knowledge, offering an easy way to try new projects and ideas with limited resources. it can also teach users about certain algorithms and architectural decisions. Applying vibe coding can also bring a series of drawbacks, such as vulnerabilities in the form of security issues and risks. The use of LLMs can also bring ethical issues, such as bias in the LLM outputs, LLM hallucinations in the form of non-factual outputs, and the non-transparent use of AI. Furthermore, purely using AI to program can lead to the decay of knowledge for the developer, leading to more risks in the future. Read about vibe coding ↗ Systematic Literature Review of Agentic AI and AIOps Across Software Lifecycle (Eppu Ruotsalainen, 2025, BSc) ↗ Agentic Artificial Intelligence (agentic AI) and AI for IT Operations (AIOps) are evolving concepts that bring autonomous decision-making agents into the Software Development Life Cycle (SDLC). This thesis conducted a systematic literature review of how these technologies are applied across the SDLC of software development. The review covers the design and coding phase, testing and Continuous Integration/Continuous Delivery (CI/CD), and operations and maintenance. The review followed PRISMA 2020 reporting principles. Relevant studies were identified from major digital libraries and screened against explicit inclusion criteria. Data were gathered and synthesized by SDLC phase to compare approaches, benefits, limitations and maturity, and to examine cross-phase patterns. The evidence reveals a clear progression of maturity. Operations is the most advanced: AIOps capabilities have been used in practice to reduce time-to-detect/resolve. Testing and CI/CD yield promising but uneven gains, constrained by trust, data availability and toolchain integration. Design and coding are the least mature — generative assistants speed up routine development, but still require human in the loop review. Overall, the integration of agentic AI across phases is still limited. This review highlights important research gaps, including the need for greater autonomous AI assistance in the early stages of development and stronger feedback loops that bring operational insights into testing and development through shared data models and interoperable tooling. In practice, organizations may gain the most by first using AIOps, then piloting AI-assisted testing and finally deploying coding assistants with strict guardrails. For researchers, priorities include early-phase agents with explainable outputs, cross-phase pipelines and longitudinal assessments of end-to-end impact. Read about agentic AI ↗ A Comparative Study of the Specification Processes of ECMAScript and TypeScript (Can Kolho, 2025, BSc) ↗ JavaScript was developed in 1995 to enhance interactivity on web pages, and today it is one of the most widely used programming languages in the world. Its official standard is ECMAScript, which is maintained by Technical Committee 39 (TC39) of ECMA International. Based on ECMAScript, Microsoft’s open source project TypeScript includes all the features of JavaScript, with its most significant addition being static typing. This helps identify errors during development rather than at runtime. This thesis examines the development phases of ECMAScript and TypeScript before a feature is included in the official specification. The work was conducted as a literature review, with key sources including scientific articles, official ECMAScript specification, documentation maintained by the technical committee, as well as documents from Microsoft and the open source community. The aim of the research is to answer the question: How do the specification processes of ECMAScript and TypeScript differ from each other? The ECMAScript development is a well-defined six-stage standardization process. A proposal is advanced by a designated champion appointed by the ECMA organization and each stage requires approval from the TC39 commitee. In contrast to ECMAScript, TypeScript does not follow a formal specification process. Its development is more pragmatic and led by Microsoft. New features arise from practical needs without a structured phase model or committee process. This allows for a more responsive approach to the need of the developer community. Read about specification processes ↗ Local-First Software: Promises and Pitfalls (Otto Otsamo, 2025, BSc) ↗ Software applications with collaboration features are typically built to store and process data on remote servers, making the client application completely dependent on those servers. This architectural pattern is simple to implement but has drawbacks: it is not possible to use the application without an internet connection, it is not always clear who owns the user’s data, communication with the server may cause delays in actions taken by the user, and the application stops working if the service shuts down, potentially resulting in data loss. Local-first software refers to a software design pattern that prioritises storing and processing data locally on the user’s device instead of remote servers. In this approach, servers are typically only utilised as a synchronisation tool to enable collaboration between users. This thesis reviews the benefits and drawbacks of each approach based on existing research and describes the common technologies typically used to build local-first software. The study demonstrates that the local-first pattern can be beneficial in applications involving asynchronous collaboration, but is unable to replace certain types of cloud-based software, such as those handling financial transactions or large datasets. Currently, the development of local-first applications remains relatively limited; however, there is clear interest in the topic within both academic and professional communities. To advance local-first development, it would be beneficial to research how existing synchronous data structures could be adapted to support asynchronous collaboration and how the memory overhead and other limitations of local-first data structures can be mitigated. Read about local-first software ↗ Comparison of web application architecture styles (Otto Söderman, 2025, BSc) ↗ Web application architecture styles define the overall structure of a web application. In today’s web development landscape, there are numerous web architecture styles to choose from. Choosing the right architecture is often difficult, and the choice can have a significant impact on the performance, development, and maintainability of a given web software project. Currently, information about these architectures is scattered. Therefore, the purpose of this thesis is to consolidate this information. In particular, the research goal is to identify the commonly used web application architectures and map out their benefits and drawbacks. The research was conducted as a literature review, using conference proceedings, research articles, and books as the main sources. The four main software application architecture styles that were identified are: monolithic, tiered, microservices, and micro-frontends. Monolithic systems were found to be the easiest to setup and manage, with tiered systems being a bit harder, and microservice-based systems, which include micro-frontends, being even more difficult. However, microservice-based systems were found to often be easier to maintain and develop further features for, as opposed to monolithic and tiered systems. Microservice-based systems were also found to be more scalable than monoliths, while tiered systems sit somewhere in the middle. In addition, microservice-based systems, and to a lesser extent tiered systems, were less prone to technology lock-in, and more suitable for multi-team development than monolithic systems. Read about web application architectures ↗ Comparison of the standardization processes of ECMAScript, HTML, and CSS (Juhana Laakso, 2025, BSc) ↗ ECMAScript, HTML, and CSS are some of the main technologies of the Internet. Each of these languages is standardized using a different process and by a different organization. The standardization process of a programming language can impact how the language is developed and how widely it is used. Therefore, understanding and comparing standardization processes can help understand the current state and development of these languages. This thesis aims to describe the current standardization processes of the three languages in a comparable way and to identify the key similarities and differences of the processes by investigating the following research question through a literature review: What are the key similarities and differences in how ECMAScript, HTML, and CSS are standardized? Three key similarities in the standardization of the languages were identified: (1) global technology organizations have decision making power in the standardization organizations, (2) contributing is generally open to anyone, but decisions are made by appointed individuals, and (3) the standardization processes and decision making are publicly documented. In addition, four key differences were identified. (1) the processes and criteria for making changes are different for each standard, (2) decision making differs from the consensus based decisions of ECMAScript and CSS, to the editor based decisions of HTML, (3) the structure of the standards differs, from the single HTML standard document to the CSS modular standard, and (4) the publication cadences of the standards differ from the constantly updated HTML standard, to the annually updated ECMAScript standard. Further research could analyze the weaknesses and strengths of the three standardization processes in relation to each other. Read about web standardization ↗ Adapting SQLite to the Distributed Edge: A Comparative Study of Different Adaptations (Kalle Ahlström, 2025, BSc) ↗ This thesis is a comparative study of different SQLite adaptations and their viability for Distributed Edge Computing environments. The four adaptions chosen for closer analysis are FaaSFS, LiteFS, libSQL, and rqlite. An ideal architecture is presented and that is used as a basis for the comparison between the adaptations. None of the solutions studied implement the ideal architecture. Each has different trade-offs, making the selection process of what to use use-case specific. The main trade-offs highlight significant differences between write performance, stronger consistency guarantees, and/or increased read latency. According to the CAP theorem, distributed systems can’t fully guarantee consistency, availability, and partition tolerance simultaneously. Empirical analysis of the chosen adaptations indicates that implementation designs inherently favor either the CA or AP model, thereby substantiating the theorem. Read about SQLite on distributed edge ↗ Survey of web API definition languages (Niklas Saarikoski, 2025, BSc) ↗ Web Application Programming Interfaces (APIs) are the backbone of modern software development, enabling communication between diverse applications and platforms.To support the different needs, a variety of web API technologies have emerged, each with its own architecture, data transmission protocols, and design philosophies. This bachelor’s thesis introduces existing web APIs, examines applications developed for them, and evaluates their advantages and disadvantages. The comparison considers the popularity, efficiency, and architectural security of these APIs. The research has been conducted as a literature review, exploring existing materials to identify previous studies and potential gaps in the research. The comparison focuses on four web API technologies: RPC (Remote Procedure Call), SOAP (Simple Object Access Protocol), REST (Representational State Transfer), and GraphQL (Graph Query Language). These APIs represent the vast majority of web APIs in use today, and provide a good look in to the different limitations brought on with certain design choices Currently, the development of entirely new web API technologies seems unlikely. Although existing solutions have clear weaknesses, they are often offset by the strengths of other technologies. Nevertheless, in the future, new use cases might emerge that demand processes beyond the capabilities of current web API technologies. Read about API definition languages ↗ Survey of Edge Databases for the Web (Arttu Pesonen, 2024, BSc) ↗ Database as a Service offerings have transformed the development of web applications, enabling almost limitless scalability of databases according to the capacity and performance requirements. With the growth of global user bases in web applications, the use of traditional database systems can lead to high latency, as the database is often located far from the end users. Edge databases aim to bring data processing closer to the end users, reducing latency and improving service performance. While cloud computing has enabled the deployment of traditional databases in regions with the highest concentrations of end users, it has not fully addressed the challenges of growing global user bases. This thesis examines edge databases and their use in the context of web applications through a literature review and by comparing different edge database service providers. This study seeks to identify the edge databases designed for web applications and explore their features and design approaches. The technical review found that all the compared edge database solutions are compatible with existing database technologies and models: CockroachDB is compatible with PostgreSQL, Redis Cloud with Redis, and Turso with SQLite. This compatibility simplifies the adoption of the services, as developers can use familiar tools and programming languages, and integrate the services directly into existing web applications. All three compared edge database services enable extensive scalability by leveraging the infrastructure of major cloud service providers for deployment. Edge databases are especially beneficial for web applications that require precise management of database locations, as this has a significant impact on the latency experienced by end users. By using edge databases, web applications can improve their usability and customer experience by reducing service latency. Read about edge databases ↗ Comparison of web performance optimization techniques -1990s vs. 2020s (Klaus Rehnberg, 2024, BSc) ↗ The transition from web sites to web applications has led to numerous changes in web optimization methods. An understanding of the evolution of optimization methods is paramount for understanding why the current optimization methods are in use. In this thesis I compare web optimization methods used in the 1990s and methods used in modern web development. The methods I analyze in this thesis are limited to methods that have a measurable impact on user perceived latency, data throughput and resource usage of web servers. The literature survey made in this thesis shows that no previous works of this kind have been made from a high level overview. To keep itself on a high level, this thesis includes a multitude of sources covering multiple optimization methods. The results of the survey indicate that optimization methods have improved in multiple regards. Not only have existing methods improved, but new methods have been created to match the new requirements of web applications. Additionally, the focus of optimization methods has shifted from reducing the impact of low network bandwidth, to instead covering dynamic web data, which can be modified to suit a specific user, and the growing number of mobile devices, which have varying screen sizes and resolutions. Web servers have also moved from local servers to cloud and edge computing. Read about web performance optimization ↗ Survey of the current state of 3D production pipelines for the web (Lauri Lyytikäinen, 2024, BSc) ↗ This paper aims to find out what is the current state of 3D production for the web. The research focuses on examining the process of creating 3D content, optimising it, and integrating it into a final product. It contains an overview of the long and complicated process of creating content for web-based platforms. The review was conducted as the current research on the topic is limited or the available information is several years old. The sources used were scientific articles and books about the topic, programming library documentation and programming articles. The research presents the different steps and tools available for creating good quality and functional 3D content for web applications. The paper outlines how 3D data is created, edited, and exported and the different applications for it. How the different libraries, frameworks and tools can be used heavily depends on the final content’s specific purpose and use case, budget and target audience. The survey also explores the different criteria that the developers can use to select their libraries and pipelines, and when it might be better to create a custom implementation. The different applications of 3D content and their unique differences are also investigated. My main findings were that 3D content in web applications is growing in popularity, and new uses for it are discovered continuously. While 3D technology has been around for multiple decades, it still is relatively new on the web platform. It is being avoided because of a complicated development process, technical limitations and the lack of standardisation. Different libraries and programming languages have greatly evolved in recent years and the standards in the industry are still forming. Read about 3D production for the web ↗ Understanding re-emergence of the RPC model in web development (Ruupert Koponen, 2024, BSc) ↗ RPC is a request-response protocol from the 1980s, which allows developers to invoke remote functions from an application. It was originally used in distributed systems, but was also used in web development in the late 1990s and early 2000s. RPC’s popularity began decreasing after the REST-style architecture appeared in the early 2000s. However, in the recent years, the RPC-model has re-emerged in web development. This bachelor’s thesis focuses on understanding the recent growth in popularity of the RPC model. In addition, this work explores the impact of modern RPC frameworks on web development practices and offers comparison between REST, RPC and GraphQL. This thesis is a literature review that utilizes scientific articles, technological documentation and blog posts. This study found out that in the early 2000s, web development moved from RPC to REST architecture due to the low performance of RPC implementations at the time. The internet was growing rapidly, requiring scalable and high-performance web services, and REST answered to this demand. The 2010s saw new trends in web development, such as microservices and TypeScript. These trends led to the emergence of new RPC frameworks, such as gRPC and tRPC. These modern RPC frameworks leverage advancements in network protocols, serialization formats, and type systems to offer an alternative to the REST architectural style. gRPC is especially popular in microservices systems due to its high performance, whereas tRPC offers developers using TypeScript the ability to develop type-safe full-stack applications. The RPC model has also been integrated into the popular front-end framework React, which provides the ability to call server-side methods directly from client-side components. With the emergence of modern RPC frameworks, developers have more options in web service development tools. Developers have access to more specialized tools and can choose the one that best suits their needs. Although modern RPC implementations may not be as universally applicable as REST or GraphQL, they can offer significant benefits in certain types of applications. gRPC and tRPC streamline the development of web services by offering an improved developer experience. Additionally, they reduce the risk of errors through type safety. Read about the RPC model ↗ Survey of Serverless Edge Computing for Web Applications (Mikael Siidorow, 2024, BSc) ↗ Cloud computing has revolutionized the way we build software with infrastructure and computing power available always on demand. Serverless computing has allowed developers to focus on applications instead of infrastructure management. However, large data center are often far away from the end users, which introduces latency. Edge computing attempts to bring computing closer to the users, to the edge. Edge computing is already widely used in Internet of Things and mobile devices, and there exists a large amount of research this area. Web applications already use edge technologies such as Content Delivery Networks, but edge computing for dynamic computation is not yet widely used. This thesis reviews edge computing for web applications and summarizes research and service providers as literature research. The aim of the study is to determine what are the benefits and limitations of serverless edge computing compared to serverless cloud computing for web application development. The technical review showed that edge computing service providers were split in two based on the internal runtime: AWS uses micro virtual machines, while Cloudflare and Deno use V8 isolates. V8 isolates start faster with less overhead, but their technologies are more limited and security is less obvious than virtual machines. Serverless edge and cloud computing are not mutually exclusive technologies. The benefits of edge computing come from both closer location and faster runtimes. Edge is suitable for latency-critical parts of the application and V8 isolates significantly reduce load times. When developing serverless applications, some computation should be moved to the edge. Many web applications could improve usability and user experience by moving computation to the edge, reducing latency. Read about serverless edge computing ↗ Using Storybook.js for component-driven design system web development (Tuomas Nummela, 2024, BSc) ↗ Building web application user interfaces has become increasingly complex due to heightened expectations and requirements in interface customizability, visual appeal, performance, and accessibility. This has given birth to frontend tools like Storybook.js that help developers manage the development complexity through component isolation and test automation. Storybook is mainly used by developers to build and maintain design systems that can be used to construct UIs across applications regardless of the different application contexts. This thesis explores developer experiences with using Storybook to build and maintain design systems, identifying some benefits and drawbacks of the tool in the process. The developer experiences are inspected from the task viewpoints of designer-developer-handoff, component programming, and component testing. For each task, the Storybook way of approaching it is explained first. That is followed by a case study of using Storybook to help with that task in a software company. Finally, some observations are made from the experiences of using Storybook for that specific task. The final discussion presents and argues for four observations about Storybook. Firstly, Storybook offers approachable component workshopping. Secondly, Storybook doubles well as rich component documentation. Thirdly, there exist numerous add-ons to further leverage the use of Storybook. Finally, to fully | 2026-01-13T08:48:42 |
https://dev.to/szabgab/perl-weekly-595-happy-hanukkah-merry-christmas-4c24 | Perl Weekly #595 - Happy Hanukkah - Merry Christmas - 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 Gabor Szabo Posted on Dec 18, 2022 • Originally published at perlweekly.com Perl Weekly #595 - Happy Hanukkah - Merry Christmas # perl # news # programming perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? Originally published at Perl Weekly 595 Hi there! Yesterday was the 35th birthday of Perl. Congratulation to Larry Wall! Today is the 1st day of Hanukkah , commemorating the Maccabean revolt agains the Seleucid (Greek) Empire when the Jews recovered Jerusalem roughly 2200 years ago. When I go for my daily stroll, I often pass by some archeological digging from that era. We lit the first candle yesterday night. In a few days the Christian world will celebrate Christmas, the birth of Yeshua (commonly known as Jesus) roughtly 164 years later. Both events are celebrated by lights and way too much food. Two weeks ago I wrote extensively about DEV inviting you to post there and even if you don't feel like writing, at least to support the few of us who post about Perl. A few people followed my call. It is still mostly only Yuki Kimoto posting there, but there were a few posts by others, there were some comments and a few "likes". As for me, I publish about a lot of things, not only Perl and I put most of them in series. I have a steady number or readers and the number of followers is also growing nicely. There are more than 400 already. If you too are interested about the subjects I write about follow me on DEV . Enjoy your week! -- Your editor: Gabor Szabo. Announcements FOSDEM FOSDEM 2023 is in person on February 4th and 5th and TPRF is seeking volunteers to help run the The Perl/Raku Foundation stand. I am quite happy that the tradition of having a stand at FOSDEM continues. It is a fun opportunity to talk about your favorite programming language with strangers. Articles Strawberry Perl vs ActivePerl Which Perl distribution to use on Windows? The Delivery Map - using GraphViz Santa has started to get more absent-minded lately. Year after year he tends to forget a few more things. Just little things like where he left the keys to the sled, or to put his red Santa hat on before he leaves the house. To give you an idea, in 2021, Santa completely forgot to deliver presents to the Johnson family in Birmingham. He had to come back later to fix it, and nearly got caught by the children! Santa's Helper Embrace the Shell jp is a tool to analyze JSON files. Let the Elves Import Your Packages Load all the modules in a namespace. Create Professional Slideshows with Mojolicious::Plugin::RevealJS Santa's elf had a problem. He had to write a presentation very fast and show it to a bunch of new elves. The email assigning this to him was sent by Santa himself. The elf started to look on MetaCPAN and found this module: Mojolicious::Plugin::RevealJS Day 16: Moving from Travis-CI to GitHub Actions for Marpa::R2 Do you think tests should always pass or are you in the school that's ok to go for some time while tests are failing. I think it is much better to make sure the test always pass and when they fail to make some intelligent decision. Those who let tests start to fail will most likely start expecting and accepting them to fail and slowly, but surely the tests will loose their value. Jeffrey Kegler, author of Marpa, thinks about this differently. Relocatable Perl That is, releases of perl that you can install anywhere on your disk. Naughty or Nice Networks IPv4 and IPv6 address mapping during the winter TWVycnkgQ2hyaXN0bWFzIDop Perl birthday party PerlayStation Games Console (Part 1) Game building in Perl using SDL and OpenGL The Weekly Challenge Advent Calendar 2022 Testing Github Actions for Perl Modules 2022-12-12 version Several examples for GitHub Workflows. Day 14: CI for the Log::Any Perl module 🐪 Simple is good for work. Less exciting for the blog. Check out the previous entries of this series if you'd like to find more exciting cases. Grants Maintaining Perl 5 Core (Dave Mitchell): November 2022 Maintaining Perl (Tony Cook) November 2022 Perl Suggestion: cpanm is added to Perl core This definitely sounds like a good idea. I really don't understand why it has not happened yet. This Week in PSC (091) The weekly report of the Perl Steering Council The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 196 Welcome to a new week with a couple of fun tasks "Pattern 132" and "Range List". If you are new to the weekly challenge then why not join us and have fun every week. For more information, please read the FAQ . RECAP - The Weekly Challenge - 195 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Special Integers" and "Most Frequent Even" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Especially Frequent Even Cool use of Perl's map and grep. Thanks for sharing the knowledge. Especially Even Lost of cool features of Raku shared with us, thanks as always for your contributions. Special Speedy Frequency Loved the use of inline-C, thanks for sharing the power of Perl. Well Ain’t That Special Colin can engage you on any topic with his quality writings. Get to know more about Numbers in general this week. PWC195 - Special Integers Getting to the end result can be enjoyable and fun journey. Flavio definitely makes it like one. Keep it up great work. PWC195 - Most Frequent Even Getting Perl and Raku solutions side-by-side makes it easy to follow. Nice one, thanks. The Weekly Challenge 195 As always the case every week, we got different ways to deal with task in Perl. Well done and keep it up. Special Integers and Most Frequent Even I liked the compact solutions in Perl and Raku. Great demo of language power. Thanks for sharing. Bags to the rescue! Nice demo of Raku Bag. It makes it easy to understand the underlying context. Thanks. Perl Weekly Challenge 195 Do you want to master Perl one-liner? This blog is good starter. Thanks. Some numbers are special and others are frequent and even Plenty to learn how to speed up your solutions. Thanks for sharing the knowledge. Frequently Special You will fall in love with the PostScript solution by Roger. Keep it up great work. PWC 195 Raku one-liner is always the winner. Nice presentation as always. Thanks for your contributions. Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . Perl Jobs by Perl Careers Adventure! Senior Perl roles in Malaysia, Dubai and Malta Clever folks know that if you’re lucky, you can earn a living and have an adventure at the same time. Enter our international client: online trading is their game, and they’re looking for Perl folks with passion, drive, and an appreciation for new experiences. Senior Perl Developer with Cross-Trained Chops. UK Remote Perl Role Sure, you’ve got Perl chops for days, but that’s not all you can do — and that’s why our client wants to meet you. They’re looking for senior Perl developers, Node engineers, and those with mighty Python and SQL skills to lead their team. Cross-trained team members are their sweet spot, and whether you’re cross-trained yourself or are open to the possibility, this may be your perfect role. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe. Remote UK Perl Role A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. Perl Developer and Business Owner? Remote Perl role in UK & EU Our clients run a job search engine that has grown from two friends with an idea to a site that receives more than 10 million visits per month. They're looking for a Perl pro with at least three years of experience with high-volume and high-traffic apps and sites, a solid understanding of Object-Oriented Perl (perks if that knowledge includes Moose), SQL/MySQL and DBIx::Class. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #755 - Does TIOBE help Perl? # perl # news # programming Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming 💎 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:48:42 |
https://docs.suprsend.com/docs#how-do-you-trigger-notifications | What is SuprSend? - 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 GETTING STARTED What is SuprSend? Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog GETTING STARTED What is SuprSend? OpenAI Open in ChatGPT Learn about SuprSend and how you can use it to power multi-channel product notifications. OpenAI Open in ChatGPT SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack: You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritise vendors and channels from your SuprSend account, You can design powerful templates for all channels together and manage them from a single place, You can leverage powerful features to experiment fast with notifications as well as take care of end user experience without writing a single line of code. Introduction to Workflows Communications are made up of multiple components - trigger, logic, content, variables, target user, channels, vendors, etc. Typical communication solutions have one or more components intertwined with each other. SuprSend solves communications from a different and more powerful approach, which we call Workflows. At SuprSend, all the constituent components are decoupled from each other, making it modular in nature. The components can come from any source. All these components are configured as nodes in Workflows, where the processing happens for delivery and optimisation. This allows Workflows to handle any complexity possible in your communication use cases. How do you trigger notifications? You can trigger notifications in one of the two ways: Send events to SuprSend from your frontend clients (android app, website, etc) via SuprSend Client SDK, and create a Workflow on SuprSend platform to trigger notification on an event. Create workflow and trigger notification from your backend itself using an omni-channel HTTPS API method, or you can use our Backend SDK. All the other components (like vendors, templates, optimisation, scaling, etc.) are created and managed on SuprSend platform. You can check the ‘Core Concepts’ section that lists down the components used in the platform, so you can navigate the platform and use all the features with ease. SuprSend APIs You can try out SuprSend APIs from our Postman collection Was this page helpful? Yes No Suggest edits Raise issue Overview Start setting up your notifications with SuprSend by following quick start guides for one of the mentioned channels. Next ⌘ I x github linkedin youtube Powered by On this page Benefits of using SuprSend as your notification stack: Introduction to Workflows How do you trigger notifications? SuprSend APIs | 2026-01-13T08:48:42 |
https://dev.to/szabgab/perl-weekly-599-open-source-development-course-for-perl-developers-5edk | Perl Weekly #599 - Open Source Development Course for Perl developers - 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 Gabor Szabo Posted on Jan 16, 2023 • Originally published at perlweekly.com Perl Weekly #599 - Open Source Development Course for Perl developers # perl # news # programming perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? Originally published at Perl Weekly 599 Hi there! Recently I started to offer a course called Open Source Development Course . The idea is to let participants learn and practice(!) git/github/pull-request/testing/code-coverage/linters/ci/etc. That way they improve their development practices and can also contribute to Open Source projects. It is a course designed to run for 12-13 weeks with about 5 hours per week workload. It can be either part of a university program or people can take it while they have a full-time job. Every week there is a 1-2 hours long presentation and the rest is hands-on work with my async help. I'd like to offer a version of this course especially for people who are interested in contributing to Perl-based Open Source projects. The participants will learn Perl-specific tools and processes. All proceedings will go to sponsor the The Perl Toolchain Summit . Check out this page for further details and let me know ASAP if you are interested. Enjoy your week! -- Your editor: Gabor Szabo. Articles so many CPAN uploads! (code review mark iii) Ricardo has 114 distributions on CPAN, give or take a few. ( MetaCPAN shows 265). He wanted to do some housekeeping that was almost fun. I think one of these cleanup uploads caught my eye thinking that the distribution is actively maintained and I sent him PR adding GitHub Actions probably making him regret a bit the new uploads. Jenkins for running scripts! Using Jenkins as a cron daemon that also nicely collects the results of all the jobs. Creating a Simple DSL in Perl Creating a XSPF playlist with your own words. New App::Easer release 2.006 Home-brewn sets Set operations are rarely needed, but when they are, perl developers usually use the keys of a hash to pretend they have sets. Number::Phone release candidate leaving perl v5.8 behind For a long time I felt that it is not a good idea to want to support people who have not upgraded their version of perl for 5-10-15(!) years, but want the latest modules from CPAN. I am glad RJBS also thinks so. He also writes about it a lot more nicely than I could ever do and gives several ways to handle the situation when a new version of a module starts requiring a version of Perl that is only 10 years old... Updating GitHub Pages using GitHub Actions How to prevent an infinite loop Perl This Week in PSC (093) Weekly report of the Perl Steering Council The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 200 Welcome to a new week with a couple of fun tasks "Arithmetic Slices" and "Seven Segment 200". If you are new to the weekly challenge then why not join us and have fun every week. For more information, please read the FAQ . RECAP - The Weekly Challenge - 199 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Good Pairs" and "Good Triplets" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Multiple Goods Did I repeat the past task? Well, it seems yes. Should have been more careful? Nice demo of do blocks and postfix for. Twice as Good Great use of Bag of Raku with detailed discussion. Keep it up great work. Not a Bad Couple… And There’s Always Room for One More, Baby Colin is back to blogging after a short break. Always pleasure to read his blog. Thanks for sharing. For The Good Dave is back with yet another blog post sharing the details of his contributions. Perl Weekly Challenge: Week 199 Jaldhar is back too, we all missed you. Thank you for sharing the knowledge with us. The Weekly Challenge 198 James never stop just after solving the weekly task but share the performance stats, magical. PWC199 - Good Pairs Flavio couldn't resist using one-liner in Perl and Raku. Always a treat. PWC199 - Good Triplets Although, not to his taste but we still have a solution. Fun Fun Fun. Perl Weekly Challenge 199: Good Pairs and Good Triplets Usually we get Raku to Perl but this time, it is other way around. Nice work, Nested Loops Everywhere! Fun and easy use of loops to get the job done. Well done. PWC 199 Sleek one-liner in Perl as always. You don't want to miss it. Thanks for sharing. All good things Use of regular for loop is enough this week. Thanks for sharing. Good N-lets Use of CPAN module makes the solution easier to follow. Great work! It's all good Like every week, we got Perl and Python twin solutions. Keep it up the momentum. PWC 199 Nice one-liners both in Perl and Raku. Well done and thanks for sharing. Videos Joel Berger on Mojolicious This interview was recorded in 2016. Other jq cheats jq is an excellent tool to interrogate and even change a JSON file. Flavio has some examples. Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . Events Geizhals Preisvergleich sponsors the German Perl/Raku Workshop The German Perl/Raku Workshop conference will take place 27.2-1.3 2023 in Frankfurt. The Perl Toolchain Summit is back in 2023! It will take place in Lyon, from Wednesday April 27 to Sunday April 30 2023 FOSDEM mini grants Would you like to give a Perl or Raku related presentation at FOSDEM 2023 that will take place 4-5 February in Brussels? TPRF can help you financially. Perl Jobs by Perl Careers Adventure! Senior Perl roles in Malaysia, Dubai and Malta Clever folks know that if you’re lucky, you can earn a living and have an adventure at the same time. Enter our international client: online trading is their game, and they’re looking for senior Perl developers with passion, drive, and an appreciation for new experiences. Senior Perl Developer with Cross-Trained Chops. UK Remote Perl Role The client is interested in anyone with experience building web apps in Perl, using one of the major Perl frameworks. If you’re a crack-hand with Catalyst, a Mojolicious master, or a distinguished Dancer, they want you. You’ll be deploying apps your work to AWS, so experience would be handy, and the company’s big on testing, so they’d like you to know your way around Test::More. Perl Developer and Business Owner? Remote Perl role in UK & EU Our clients run a job search engine that has grown from two friends with an idea to a site that receives more than 10 million visits per month. They're looking for a Perl pro with at least three years of experience with high-volume and high-traffic apps and sites, a solid understanding of Object-Oriented Perl (perks if that knowledge includes Moose), SQL/MySQL and DBIx::Class. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe. Remote Perl Role in the UK A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #755 - Does TIOBE help Perl? # perl # news # programming Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming 💎 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:48:42 |
https://aws.github.io/ | Open Source at AWS Open Source at AWS Code of Conduct FAQ Babelfish for PostgreSQL Apache-2.0 A SQL Server-compatible end-point to make PostgreSQL fluent in understanding communication from apps written for SQL EKS Distro Apache-2.0 Certified Kubernetes distribution based on and used by Amazon Elastic Kubernetes Service (EKS) to create reliable and secure Kubernetes clusters Bottlerocket Apache-2.0/MIT Linux-based operating system meant for hosting containers AWS Distro for OpenTelemetry Apache-2.0 Production-ready, AWS-supported distribution of the OpenTelemetry project Firecracker Apache-2.0 Virtual machine monitor (VMM) to create and manage microVMs OpenSearch Apache-2.0 Open source distributed and RESTful search engine. AWS Amplify Apache-2.0 Open source framework and tools for developing mobile and web applications FreeRTOS MIT Market-leading real-time operating system (RTOS) for microcontrollers and small microprocessors AWS CDK Apache-2.0 The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code AWS GitHub Organizations AWS | AWS Samples | AWS Labs AWS Docs | AWS Quick Starts | AWS Integration and Automation | AWS Solutions | AWS Actions | Amazon Archives | Amazon Science | AWS Controllers for Kubernetes OpenSearch | Projen | Corretto | Ace | Bottlerocket | Firecracker MicroVM | Gluon API | FreeRTOS | Boto | Neo AI | Model Checking Amazon Linux | AWS Observability | Amazon Connect | AWS CloudFormation | CDK Labs at AWS | AWS Amplify | AWS Robotics | AWS DeepRacer Copyright 2014-2021 Amazon.com, Inc. or its affiliates. All Rights Reserved. | 2026-01-13T08:48:42 |
https://docs.suprsend.com/reference/cli-category-push | Push Categories - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Preference Category Push Categories Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Preference Category Push Categories OpenAI Open in ChatGPT Push categories from local directory to SuprSend OpenAI Open in ChatGPT Categories are pushed in draft state until committed.\ You can either pass the —commit=true flag to push and commit categories in a single step, or commit them later using the category commit command to make them live. \ Until committed, changes remain inactive and will not be reflected in your application or workflow settings. Syntax Copy Ask AI suprsend category push [flags] Flags Flag Description Default -h, --help Show help for the command – -c, --commit string Commit the categories true -m, --commit-message string Commit message describing the changes – -d, --dir string directory path where pulled categories will be saved suprsend/category/ -w, --workspace string Workspace to push categories to staging Example Copy Ask AI # Push categories from default directory suprsend category push # Push categories from custom directory suprsend category push --dir categories # Push categories to production workspace suprsend category push --workspace production # Push categories with commit message suprsend category push --commit=true --commit-message "Update notification preferences" Frequently Asked Questions I have pushed my categories but don’t see the updated categories in live mode. You can view detailed logs by enabling debug mode export DEBUG=true in your terminal. In most cases, this happens when an existing preference category is being overridden by the latest push and that category is already linked to a workflow. When this occurs, the changes cannot be committed to live mode . The updated categories will still appear in draft mode, but you’ll need to update or unlink the workflows before committing the changes live. Was this page helpful? Yes No Suggest edits Raise issue Previous Commit Categories Commit categories to make them live in the workspace Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example Frequently Asked Questions | 2026-01-13T08:48:42 |
https://parenting.forem.com/code-of-conduct#our-pledge | Code of Conduct - Parenting 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 Parenting 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 Parenting — 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. 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 . Parenting © 2016 - 2026. Navigating the chaos and joy of parenting. Log in Create account | 2026-01-13T08:48:42 |
https://dev.to/szabgab/perl-weekly-596-new-year-resolution-539p | Perl Weekly #596 - New Year Resolution - 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 Gabor Szabo Posted on Dec 26, 2022 • Originally published at perlweekly.com Perl Weekly #596 - New Year Resolution # perl # news # programming perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? Originally published at Perl Weekly 596 Hi there, With the end of Advent Calendar celebration, another celebration kicks in i.e. Christmas/Boxing Day . Although I don't celebrate, being a Muslim, but I do enjoy the break from the routine work. This edition of the weekly newsletter is my 120th edition . I hope you enjoy reading the newsletter as much as I do getting ready for you. Do you have any new year resolutions? I used to but then last year I stopped it. Why? Well couple of projects closed to my heart didn't get started and that made me very pessimistic. I feel so bad that I don't even talk about it. I hope new year will bring positive change. Still, I don't feel like setting new year resolutions. Could it be, I am getting old to keep up with fast pace dev life? Having said, the dev inside me still alive but just needs some push. Fortunately I have so many people around me that always gives me much needed positive energy. Let's talk about some positivity now. Well for me, it was the Perl Advent Calendar 2022 , thanks to Olaf Alders and team. I wanted to be part of it but then missed the train unfortunately. Never mind, there is always next time. Having said, I did manage to get the post up but was too late to make it. Fortunately my contribution to Raku Advent Calendar 2022 did work out nicely like Raku and I . Enjoy rest of the holidays and stay safe. -- Your editor: Mohammad S. Anwar. Announcements First round of feature 'class' Paul "LeoNerd" Evans has created the first pull request for Corinna, the modern OOP system for Perl. Merry Christmas! Catalyst Framework For any of the Catalyst programmers out there interested in seeing the framework move forward, here's a PR that changes action chaining so that you can call the next action from within the action code, optionally passing and recieving arguments. Articles Writing a CPAN module that talks to ChatGPT ChatGPT is the hot topic now a days and Dave shared his view on the same. Linux::NFTables Perl interface to libnftables. PerlayStation Games Console (Part 1) Saif is back in action after a long break with yet another engaging topic. Discussion How to find files in a directory in Perl? Nice and easy solution. Web AoC 2022/13 - Nested lists AoC 2022/14 - Sand accumulation AoC 2022/15 - Diamonds are squares in disguise AoC 2022/16 - Pressured shame AoC 2022/17 - Tetris-ish accumulation The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 197 Welcome to a new week with a couple of fun tasks: "Move Zero" and "Wiggle Sort". If you are new to the weekly challenge, why not join us and have fun every week? For more information, please read the FAQ . RECAP - The Weekly Challenge - 196 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Pattern 132" and "Range List" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. The Weekly Challenge Advent Calendar 2022 Finally we now have a complete Advent Calendar 2022. Enjoy !!! 132 Lists Nice trick to deal with data type, thanks for sharing the knowledge. Range Rover, Over Clover Task analysis by Colin is the highlight of the blog post for me. Keep it up great work. Insert Clever Title Here Welcome back to blogging after a short break. The title is really unique. Well done. PWC196 - Pattern 132 No new questions, that is win for me. Keep it up great work. PWC196 - Range List Lucky twice this week, no questions asked. Thank you for sharing knowledge. Perl Weekly Challenge: Week 196 Thanks for getting blog post ready at the airport. I salute your dedication. The Weekly Challenge 196 James is known for compact and powerful solution. Thanks for sharing the knowledge. Perl Weekly Challenge 196: Pattern 132 and Range List Being one of the regular contributors, Laurent never misses the opportunity to entertain us every week. Merry Christmas! Along with Raku, we get SQL version too every week. Nice treat for all of us, thanks. Perl Weekly Challenge 196 Master of Perl one-liner is at it again. You don't want to miss the fun. Pattern 132 and sequential runs Nice and easy task analysis. There is always something to learn. Pattern and Range Roger's collection always has the surprising element, you don't want to miss. Highly recommended. Weekly Challenge 196 Interesting bunch of Perl and Python creations. Keep it up great work. PWC 196 Despite being holiday season, we still got creative post, thanks for your contributions. Rakudo 2022.51 Hijacking D3 Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . The corner of Gabor A couple of entries sneaked in by Gabor. Billions of unnecessary files in GitHub People seem to ignore the .gitignore file. Day 25: CI for Data::Alias in Perl - including threaded perl A simple GitHub Action configuration with some twist Day 24: CI for perl5-MIME-Types Day 23: CI using timescaledb a PostgreSQL based time series database Though this is a Ruby project, it was very interesting (and complex) setting up the Continuous Integration. Perl Jobs by Perl Careers Adventure! Senior Perl roles in Malaysia, Dubai and Malta Clever folks know that if you’re lucky, you can earn a living and have an adventure at the same time. Enter our international client: online trading is their game, and they’re looking for Perl folks with passion, drive, and an appreciation for new experiences. Senior Perl Developer with Cross-Trained Chops. UK Remote Perl Role Sure, you’ve got Perl chops for days, but that’s not all you can do — and that’s why our client wants to meet you. They’re looking for senior Perl developers, Node engineers, and those with mighty Python and SQL skills to lead their team. Cross-trained team members are their sweet spot, and whether you’re cross-trained yourself or are open to the possibility, this may be your perfect role. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe. Remote UK Perl Role A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. Perl Developer and Business Owner? Remote Perl role in UK & EU Our clients run a job search engine that has grown from two friends with an idea to a site that receives more than 10 million visits per month. They're looking for a Perl pro with at least three years of experience with high-volume and high-traffic apps and sites, a solid understanding of Object-Oriented Perl (perks if that knowledge includes Moose), SQL/MySQL and DBIx::Class. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? Top comments (1) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Matthew O. Persico Matthew O. Persico Matthew O. Persico Follow I was born. I am still alive. Well, it did say a "short" bio. Email matthew.persico@gmail.com Location Westchester, NY Joined Jan 12, 2018 • Dec 27 '22 Dropdown menu Copy link Hide Excellent. Hope to see more people find this here. Like comment: Like comment: 1 like 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #755 - Does TIOBE help Perl? # perl # news # programming Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming 💎 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:48:42 |
https://dev.to/t/mentalhealth/page/4 | Mental Health 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 Mental Health Follow Hide Mental health matters! Break the stigma. We can empower ourselves and each other to invest in our mental health. We can give support and care to ourselves and each other while we struggle. Let's talk about making our mental health priority. Create Post about #mentalhealth Posts should be related to mental health. This is a pretty wide category but some things that are included are: Managing mental health as a developer Living with mental illness and how it affects your work Ways to cope with mental health issues Avoiding burn out Tools, apps, and methods that help you with your mental health ...and more “Your mental health is a priority. Your happiness is an essential. Your self-care is a necessity.” Struggling? Help is out there. Click here to find a list of global mental health resources and hotlines. Older #mentalhealth 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 Rejection: The Gateway to Growth Mike Sorrenti Mike Sorrenti Mike Sorrenti Follow Nov 24 '25 Rejection: The Gateway to Growth # career # mentalhealth # motivation Comments Add Comment 4 min read Should developers meditate? Andreas Müller Andreas Müller Andreas Müller Follow Dec 13 '25 Should developers meditate? # discuss # mentalhealth # productivity 13 reactions Comments 5 comments 3 min read Why Tech Brains Struggle With Money Simplicity (And How to Fix It) James Patterson James Patterson James Patterson Follow Nov 19 '25 Why Tech Brains Struggle With Money Simplicity (And How to Fix It) # watercooler # mentalhealth # productivity Comments Add Comment 3 min read Hallucinating Help Rich Jeffries Rich Jeffries Rich Jeffries Follow Dec 1 '25 Hallucinating Help # discuss # ai # safety # mentalhealth 1 reaction Comments Add Comment 9 min read The Debugger’s Guide to Understanding Your Financial Biases Allen Bailey Allen Bailey Allen Bailey Follow Nov 19 '25 The Debugger’s Guide to Understanding Your Financial Biases # watercooler # learning # mentalhealth Comments Add Comment 4 min read The Cost of Stopping When We Hit the Wall Yodit Weldegeorgise Yodit Weldegeorgise Yodit Weldegeorgise Follow Dec 22 '25 The Cost of Stopping When We Hit the Wall # mentalhealth # motivation # productivity 5 reactions Comments 4 comments 2 min read The Story Behind Peaceful Night, a Calm Space for Tired Minds Thoma Nani Thoma Nani Thoma Nani Follow Nov 15 '25 The Story Behind Peaceful Night, a Calm Space for Tired Minds # showdev # mentalhealth # ux Comments Add Comment 2 min read Cybersecurity Fatigue Isn’t a Bug — It’s a Systemic Failure in MSP Engineering Donald Betancourt Donald Betancourt Donald Betancourt Follow Nov 13 '25 Cybersecurity Fatigue Isn’t a Bug — It’s a Systemic Failure in MSP Engineering # discuss # mentalhealth # career # cybersecurity Comments Add Comment 3 min read The Coffee Bean Yodit Weldegeorgise Yodit Weldegeorgise Yodit Weldegeorgise Follow Dec 15 '25 The Coffee Bean # career # mentalhealth # motivation 4 reactions Comments 6 comments 2 min read How to Prepare for the Future of Programming Clara Maine Clara Maine Clara Maine Follow Dec 10 '25 How to Prepare for the Future of Programming # discuss # mentalhealth # career # programming 16 reactions Comments 4 comments 6 min read The Environment Includes Soft, Hard, and Body sta sta sta Follow Dec 12 '25 The Environment Includes Soft, Hard, and Body # devex # developer # mentalhealth 2 reactions Comments Add Comment 7 min read Respiration Pascal CESCATO Pascal CESCATO Pascal CESCATO Follow Dec 3 '25 Respiration # watercooler # devjournal # writing # mentalhealth 30 reactions Comments 10 comments 6 min read 🌟 My First Hackathon Journey: My Mental Health Buddy at Hackaura 2025 Lavender Princess Lavender Princess Lavender Princess Follow Nov 7 '25 🌟 My First Hackathon Journey: My Mental Health Buddy at Hackaura 2025 # hackathon # beginners # python # mentalhealth Comments Add Comment 3 min read Beyond Burnout: A 5-Step Action Plan for Stressed-Out Developers Mikhail Dorokhovich Mikhail Dorokhovich Mikhail Dorokhovich Follow Dec 9 '25 Beyond Burnout: A 5-Step Action Plan for Stressed-Out Developers # burnout # careerdevelopment # mentalhealth # productivity Comments Add Comment 3 min read When the Spark is Done: The ADHD Energy Cycle No One Talks About ✨ Ashley Childress Ashley Childress Ashley Childress Follow Dec 4 '25 When the Spark is Done: The ADHD Energy Cycle No One Talks About ✨ # discuss # mentalhealth # productivity # adhd 18 reactions Comments 6 comments 5 min read LLM Context Window Stress Testing: Reliability Under Load Rich Jeffries Rich Jeffries Rich Jeffries Follow Nov 21 '25 LLM Context Window Stress Testing: Reliability Under Load # ai # mentalhealth # safety 9 reactions Comments 1 comment 4 min read Two People, Same Body: A Developer's Crisis Architecture CrisisCore-Systems CrisisCore-Systems CrisisCore-Systems Follow Dec 8 '25 Two People, Same Body: A Developer's Crisis Architecture # mentalhealth # opensource # webdev # react Comments Add Comment 4 min read From Cancer Cures to Pornography: The Six-Month Descent of AI Denis Stetskov Denis Stetskov Denis Stetskov Follow Nov 18 '25 From Cancer Cures to Pornography: The Six-Month Descent of AI # ai # mentalhealth # programming # webdev 5 reactions Comments 2 comments 7 min read When Someone Dismisses Your Work. Why You Should Keep Building Anyway Ed Ed Ed Follow Dec 7 '25 When Someone Dismisses Your Work. Why You Should Keep Building Anyway # discuss # motivation # mentalhealth # softwaredevelopment 4 reactions Comments Add Comment 3 min read The Dopamine Hit of git push vs. The Agony of git revert Tombri Bowei Tombri Bowei Tombri Bowei Follow Nov 30 '25 The Dopamine Hit of git push vs. The Agony of git revert # programming # webdev # career # mentalhealth 15 reactions Comments 6 comments 5 min read Building Confessly: The Anonymous Confession Platform That Actually Listens Nadim Chowdhury Nadim Chowdhury Nadim Chowdhury Follow Nov 1 '25 Building Confessly: The Anonymous Confession Platform That Actually Listens # showdev # opensource # mentalhealth # ai Comments Add Comment 7 min read I Built MoodFeed: An AI That Actually Knows When You're Having a Sh*t Day Nadim Chowdhury Nadim Chowdhury Nadim Chowdhury Follow Nov 1 '25 I Built MoodFeed: An AI That Actually Knows When You're Having a Sh*t Day # showdev # sideprojects # mentalhealth # ai Comments Add Comment 9 min read Finding Strength in Code, Part 2: Lessons from Loss and the Power of Reflection Sagrario Meneses Sagrario Meneses Sagrario Meneses Follow Nov 28 '25 Finding Strength in Code, Part 2: Lessons from Loss and the Power of Reflection # mentalhealth # postmortem # softwareengineering # problemsolving 5 reactions Comments 1 comment 5 min read Trauma-informed design left everyone asking: "How does it actually know I'm struggling without spying?" CrisisCore-Systems CrisisCore-Systems CrisisCore-Systems Follow Nov 29 '25 Trauma-informed design left everyone asking: "How does it actually know I'm struggling without spying?" # privacy # mentalhealth # opensource # webdev Comments Add Comment 7 min read The Silent Struggle of the High-Achiever: Why your own high standards are making you tired Cathy Lai Cathy Lai Cathy Lai Follow Nov 26 '25 The Silent Struggle of the High-Achiever: Why your own high standards are making you tired # discuss # mentalhealth # career # productivity 5 reactions Comments 4 comments 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:48:42 |
https://legal.x.com/purchaser-terms#purchasertermsofservice | X Purchaser Terms of Service X Purchaser Terms of Service Download X Purchaser Terms of Service Terms for Paid Services X Premium Additional Terms Subscriptions Additional Terms Download X Purchaser Terms of Service X Purchaser Terms of Service goglobalwithtwitterbanner Terms for Paid Services X Premium Additional Terms Creator Subscriptions Additional Terms Premium Business and Premium Organizations Additional Terms Terms for Paid Services X Premium Additional Terms Creator Subscriptions Additional Terms Premium Business and Premium Organizations Additional Terms X Purchaser Terms of Service Effective: August 1, 2025 If you live outside the European Union, EFTA States, or the United Kingdom, including if you live in the United States, the following X Purchaser Terms of Service apply to you. If you live in the European Union, EFTA States, or the United Kingdom, these X Purchaser Terms of Service apply to you. X Purchaser Terms of Service If you live outside the European Union, EFTA States, or the United Kingdom, including if you live in the United States X allows you to access certain features in exchange for payment of a one-time or recurring fee, as applicable to the relevant features (each a “ Paid Service ” and collectively the " Paid Services "). For example, X Premium (as defined below) and Subscriptions would each be considered a “Paid Service.” To the extent that you sign up for and/or use a Paid Service, your use of the Paid Services and any corresponding transactions are subject to: (i) the terms and conditions set forth herein, including the applicable terms and conditions for each Paid Service you purchase, each as listed below (collectively, the “ X Purchaser Terms of Service ”), and (ii) the applicable X Terms of Service , X Privacy Policy , X Rules and Policies , and all policies incorporated therein (collectively, the “ X User Agreement ”). This X Purchaser Terms of Service and the aforementioned X User Agreement shall be collectively referred to in this document as the “ Terms ”. “ X ” refers to the X entity that provides the Paid Services to you. Please read these X Purchaser Terms of Service carefully to make sure you understand the applicable terms, conditions and exceptions. IF YOU LIVE IN THE UNITED STATES, THESE TERMS CONTAIN IMPORTANT INFORMATION THAT APPLY TO YOU ABOUT RESOLUTION OF DISPUTES, INCLUDING A WAIVER OF YOUR RIGHT TO BRING CLAIMS AS CLASS ACTIONS, AND A LIMITATION ON YOUR RIGHT TO BRING CLAIMS AGAINST X MORE THAN 2 YEARS AFTER THE RELEVANT EVENTS OCCURRED, WHICH IMPACT YOUR RIGHTS AND OBLIGATIONS IF ANY DISPUTE WITH X ARISES. SEE SECTION 6 UNDER GENERAL TERMS FOR DETAILS ON THESE PROVISIONS. Acceptance . By using or accessing a Paid Service(s) from X, submitting payment thereunder and/or clicking on a button to make a one-time purchase or recurring subscription payments for the Paid Service provided by X, you agree to be bound by the Terms. If you do not understand the Terms, or do not accept any part of them, then you may not use or access any Paid Services. To purchase and use a Paid Service you must: (i) be at least 18 years old or the age of majority as determined by the laws of the jurisdiction in which you live or (ii) have the express consent of your parent or guardian to purchase and use that Paid Service. If you are a parent or legal guardian and you allow your child (or a child that you are a guardian of) to purchase or use a Paid Service, you agree that the Terms apply to you, that you will abide by the Terms, and that you are responsible for the child’s activity on the Paid Services and for ensuring that the child also abides by the Terms. In any case, as stated in the Who May Use the Services section of the X Terms of Service, you must be at least 13 years old to use the X Service. If you are accepting these X Purchaser Terms of Service and using the Paid Services on behalf of a company, organization, government, or other legal entity, you represent and warrant that you are authorized to do so and have the authority to bind such entity to these X Purchaser Terms of Service, in which case the words “you” and “your” as used in these X Purchaser Terms of Service shall refer to such entity. X Contracting Entity . You enter into these X Purchaser Terms of Service with the entity that corresponds to where you live, as listed below. This entity will provide the Paid Services to you. No other entity is bound to any obligations to you under these Purchaser Terms of Service. Your Location The continents of North America (including Hawaii) or South America Contracting Entity X Corp., with an office located at 865 FM 1209, Building 2, Bastrop, TX 78602, USA Your Location Any country not covered by the above two locations, including the Asia-Pacific region, Middle East, Africa or Europe (excluding EU countries, EFTA States and the United Kingdom) Contracting Entity X Global LLC, with its registered office at 701 S. Carson St., Suite 200, Carson City, NV 89701, USA Changes to Terms, Paid Services and Pricing 1. Changes to Terms. X may revise these X Purchaser Terms of Service from time to time, including for any business, financial, or legal reasons. The changes will not be retroactive, and the most current version of the X Purchaser Terms of Service, available at legal.x.com/purchaser-terms , will govern your use of Paid Services and any corresponding transactions. If we modify or revise these Terms after you have agreed to them (for example, if these terms are modified after you have purchased a subscription), we will notify you in advance of material revisions to these terms. Such notification may be provided electronically, including (and without limitation to) via a service notification or an email to the email address associated with your account. By continuing to access or use the Paid Services after those revisions become effective, you agree to be bound by the revised X Purchaser Terms of Service. If you do not agree to abide by these or any future X Purchaser Terms of Service, do not use or access (or continue to use or access) the Paid Services. The X Purchaser Terms of Service are written in English but are made available in multiple languages through translations. X strives to make the translations as accurate as possible to the original English version. However, in case of any discrepancies or inconsistencies, the English language version of the X Purchaser Terms of Service shall take precedence. You acknowledge that English shall be the language of reference for interpreting and constructing the terms of the X Purchaser Terms of Service. 2. Changes to Paid Services. Our Paid Services evolve constantly. As such, the Paid Services may change from time to time, at our discretion, including for any business, financial, or legal reasons. We may stop (permanently or temporarily) providing the Paid Services or any features within the Paid Services to you or to users generally with or without notice. X is not liable to you or to any third party for any modification, suspension or discontinuance of the Paid Services. The specific terms and conditions (included below) for the specific Paid Service specify how you can cancel a subscription or, when applicable, seek a refund. 3. Changes to Pricing. Prices for Paid Services, including recurring subscription fees, are subject to change from time to time, including for any business, financial, or legal reasons. X will provide reasonable advance notice of any material change to the price of Paid Services. For subscription services, price changes will take effect at the start of the next subscription period following the date of the price change. If you do not agree with a price change, you have the right to reject the change by cancelling your subscription to the applicable Paid Service prior to the price change going into effect. Payment Terms . X offers various payment options that may vary by Paid Service, your device and/or operating system, your geographic location, or other factors. To the extent available (as X may make various purchase methods available from time to time), these payment options may include the ability to use “In app payment” functionality offered by Google or Apple, or to make a web payment using X's third party payment processor, Stripe ( www.stripe.com - hereafter “ Stripe ”). When you make a payment, you explicitly agree: (i) to pay the price listed for the Paid Service, along with any additional amounts relating to applicable taxes, credit card fees, bank fees, foreign transaction fees, foreign exchange fees, and currency fluctuations; and (ii) to abide by any relevant terms of service, privacy policies, or other legal agreements or restrictions (including additional age restrictions) imposed by Google, Apple, or Stripe (as X's third party payment processor) in connection with your use of a given payment method (for example only, if you choose to make your payment via Apple’s in-app purchasing functionality, you agree to abide by any relevant terms, requirements, and/or restrictions imposed by Apple). Any private personal data that you provide in connection with your use of the Paid Services including, without limitation, any data provided in connection with payment, will be processed in accordance with the X Privacy Policy. X may share your payment information with payment services providers to process payments; prevent, detect, and investigate fraud or other prohibited activities; facilitate dispute resolution such as chargebacks or refunds; and for other purposes associated with the acceptance of credit cards, debit cards, or ACH. It is your responsibility to make sure your banking, credit card, debit card, and/or other payment information is up to date, complete and accurate at all times. If you make a payment for a Paid Service, we may receive information about your transaction such as when it was made, when a subscription is set to expire or auto- renew, what platform you made the purchase on, and other information. X will not be responsible or liable for any errors made or delays by a payment processor, Apple’s App Store or the Google Play Store, your bank, your credit card company, and/or any payment network. Please refer to each specific Paid Service Terms and Conditions below for payment terms applicable to that specific Paid Service, including how subscription renewals are handled and other important terms. Application of X User Agreement, Termination, No Refunds, Multiple X Accounts, and Restrictions 1. The X User Agreement Applies to You . YOU MUST ALWAYS FOLLOW AND COMPLY WITH THE X USER AGREEMENT. The X User Agreement always applies to your use of the X Service, including the Paid Services and features. Your failure to follow and comply with the X User Agreement, or X's belief that you have failed to follow and comply with the X User Agreement, may result in the cancellation of your Paid Services. Any such cancellation will be in addition to, and without limitation of, any enforcement action that X may take against you pursuant to the X User Agreement. In such instances you may lose the benefits of your Paid Services and you will not be eligible for a refund for any amounts you have paid (or pre-paid) for Paid Services. 2. Why X Might Terminate Your Access to Paid Services. X may suspend or terminate your access to Paid Service(s), cease providing you with all or part of the Paid Services, or take any other action it deems appropriate, including, for example, suspend your account, (without any liability) at any time for any or no reason, including, but not limited to any of the following reasons: a. X believes, in its sole discretion, that you have violated the Terms or your use of the Paid Service(s) would violate any applicable laws; b. X is requested or directed to do so by any competent court of law, regulatory authority, or law enforcement agency; c. X has unexpected technical or security issues; d. X believes, in its sole discretion, you have violated the X User Agreement; e. X believes, in its sole discretion, you are engaging in manipulation or other disruptive or prohibited conduct generally or in connection with the Paid Services; f. You create risk or possible legal exposure for X; g. Your account should be removed due to unlawful conduct; h. Your account should be removed due to prolonged inactivity; or i. Our provision of the Paid Services (in whole or in part) to you is no longer commercially viable (in X's sole discretion). 3. All Transactions Are Final. All payments for Paid Services are final and not refundable or exchangeable, except as required by applicable law. We make no guarantee as to the nature, quality, or value of a Paid Service or the availability or supply thereof. Refunds or credits are not provided for any unused or partially used Paid Service (for example, a partially used subscription period). 4. Paid Services Are Non-Transferable between X Accounts. Each purchase of a Paid Service applies to a single X account, meaning that your purchase will apply solely to the account you were using when you purchased the Paid Service and will not apply to other accounts that you may have access to, or control over. If you have or control multiple accounts and you want access to Paid Services on each account, you must purchase the Paid Service on each account individually. 5. Restrictions and Obligations. a. You may only purchase and use a Paid Service if you are legally allowed to use the Paid Service in your country and you live in a country supported by X for the applicable Paid Service. X may, in its discretion, restrict the ability to access or purchase a Paid Service in certain countries. X reserves the right to modify the list of supported countries from time to time. b. We reserve the right to refuse Paid Services transactions or to cancel or discontinue the sale or use of a Paid Service in our sole discretion. c. You may not allow others to use your X account to access any Paid Service that such person did not order. d. You may not purchase or use a Paid Service if you are a person with whom U.S. persons are not permitted to have dealings pursuant to economic sanctions, including, without limitation, sanctions administered by the United States Department of the Treasury's Office of Foreign Assets Control or any other applicable sanctions authority (" Prohibited Person "). This includes, without limitation, persons located in, or ordinarily resident in, the following countries and regions: Cuba, Iran, the Ukraine regions of Crimea, North Korea and Syria. You represent and warrant that you are not a Prohibited Person. e. YOU REPRESENT THAT YOU WILL USE THE PAID SERVICES ONLY FOR LAWFUL PURPOSES AND ONLY IN ACCORDANCE WITH THE TERMS. Taxes and fees . You are responsible for and agree to pay any applicable taxes, duties, tariffs, and fees related to the purchase of Paid Services, including those required to be paid to either X or a third-party payment processor. These taxes may include, but are not limited to, VAT, GST, sales tax, withholding tax, and any other applicable taxes. Depending on your location, X may be responsible for collecting and reporting information related to transaction taxes arising from your purchase of Paid Services. You grant X permission to provide your account and personal information to relevant tax authorities to fulfill our tax collection and reporting obligations. General Terms 1. Contact Information. If you have any questions about the Paid Services or these Terms, you can check out the X Paid Services Help Center for more details. If you’ve already purchased a Paid Service, you can also contact us via the support link available in the navigation menu of your X account under the payment or subscription settings. If you have additional questions, then you can contact us here by using the “Help with paid features” form. 2. DISCLAIMERS. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, YOUR ACCESS TO AND USE OF THE PAID SERVICES IS AT YOUR OWN RISK. YOU UNDERSTAND AND AGREE THAT THE PAID SERVICES ARE PROVIDED TO YOU ON AN “AS IS” AND “AS AVAILABLE” BASIS. X DISCLAIMS ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS OR IMPLIED, OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. X MAKES NO WARRANTY OR REPRESENTATION AND DISCLAIMS ALL RESPONSIBILITY AND LIABILITY FOR: (I) THE COMPLETENESS, ACCURACY, AVAILABILITY, TIMELINESS, SECURITY OR RELIABILITY OF THE PAID SERVICES; AND (II) WHETHER THE PAID SERVICES WILL MEET YOUR REQUIREMENTS OR BE AVAILABLE ON AN UNINTERRUPTED, SECURE, OR ERROR-FREE BASIS. YOU ARE RESPONSIBLE FOR YOUR USE OF THE X SERVICE, INCLUDING THE PAID SERVICES, AND ANY CONTENT YOU PROVIDE. 3. LIMITATION OF LIABILITY. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE X ENTITIES SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS OR REVENUES, WHETHER INCURRED DIRECTLY OR INDIRECTLY, OR ANY LOSS OF DATA, USE, GOODWILL, OR OTHER INTANGIBLE LOSSES, RESULTING FROM (i) YOUR ACCESS TO OR USE OF OR INABILITY TO ACCESS OR USE THE PAID SERVICES; (ii) ANY CONDUCT OR CONTENT OF ANY THIRD PARTY POSTED THROUGH THE PAID SERVICES, INCLUDING WITHOUT LIMITATION, ANY DEFAMATORY, OFFENSIVE OR ILLEGAL CONDUCT OF OTHER USERS OR THIRD PARTIES; (iii) ANY CONTENT OBTAINED FROM THE PAID SERVICES; OR (iv) UNAUTHORIZED ACCESS, USE OR ALTERATION OF YOUR TRANSMISSIONS OR CONTENT. FOR THE AVOIDANCE OF DOUBT, THE DEFINITION OF PAID SERVICES IS LIMITED TO THE FEATURES OFFERED BY X AND DOES NOT INCLUDE ANY CONTENT YOU ACCESS AND/OR INTERACT WITH IN USING THOSE FEATURES. IN NO EVENT SHALL THE AGGREGATE LIABILITY OF THE X ENTITIES EXCEED THE GREATER OF ONE HUNDRED U.S. DOLLARS (U.S. $100.00) OR THE AMOUNT YOU PAID X, IF ANY, IN THE PAST SIX MONTHS FOR THE PAID SERVICES GIVING RISE TO THE CLAIM. THE LIMITATIONS OF THIS SUBSECTION SHALL APPLY TO ANY THEORY OF LIABILITY, WHETHER BASED ON WARRANTY, CONTRACT, STATUTE, TORT (INCLUDING NEGLIGENCE) OR OTHERWISE, AND WHETHER OR NOT THE X ENTITIES HAVE BEEN INFORMED OF THE POSSIBILITY OF ANY SUCH DAMAGE, AND EVEN IF A REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. THE “X ENTITIES” REFERS TO X, ITS PARENTS, AFFILIATES, RELATED COMPANIES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, REPRESENTATIVES, PARTNERS, AND LICENSORS. APPLICABLE LAW IN YOUR JURISDICTION MAY NOT ALLOW FOR CERTAIN LIMITATIONS OF LIABILITY. TO THE EXTENT REQUIRED BY APPLICABLE LAW IN YOUR JURISDICTION, THE ABOVE DOES NOT LIMIT THE X ENTITIES’ LIABILITY FOR FRAUD, FRAUDULENT MISREPRESENTATION, DEATH OR PERSONAL INJURY CAUSED BY OUR NEGLIGENCE, GROSS NEGLIGENCE, AND/OR INTENTIONAL CONDUCT. TO THE FULLEST EXTENT ALLOWED UNDER APPLICABLE LAW, THE X ENTITIES’ MAXIMUM AGGREGATE LIABILITY FOR ANY NON-EXCLUDABLE WARRANTIES IS LIMITED TO ONE HUNDRED US DOLLARS (US$100.00). 4. Notice Regarding Apple. To the extent that you purchased the Paid Services or are using or accessing the Paid Services on an iOS device, you further acknowledge and agree to the terms of this Section. You acknowledge that the Terms are between you and us only, not with Apple, and Apple is not responsible for the Paid Services and the content thereof. Apple has no obligation whatsoever to furnish any maintenance and support service with respect to the Paid Services. In the event of any failure of the Paid Services to conform to any applicable warranty, then you may notify Apple and Apple will refund any applicable purchase price for the Paid Services to you; and, to the maximum extent permitted by applicable law, Apple has no other warranty obligation whatsoever with respect to the Paid Services. Apple is not responsible for addressing any claims by you or any third-party relating to the Paid Services or your possession and/or use of the Paid Services, including, but not limited to: (i) product liability claims; (ii) any claim that the Paid Services fail to conform to any applicable legal or regulatory requirement; and (iii) claims arising under consumer protection or similar legislation. Apple is not responsible for the investigation, defense, settlement and discharge of any third-party claim that the Paid Services and/or your possession and use of the mobile application infringe that third-party’s intellectual property rights. You agree to comply with any applicable third-party terms when using the Paid Services. Apple, and Apple’s subsidiaries, are third-party beneficiaries of the Terms, and upon your acceptance of the Terms, Apple will have the right (and will be deemed to have accepted the right) to enforce the Terms against you as a third-party beneficiary of the Terms. You hereby represent and warrant that (i) you are not located in a country that is subject to a U.S. Government embargo, or that has been designated by the U.S. Government as a "terrorist supporting" country; and (ii) you are not listed on any U.S. Government list of prohibited or restricted parties. 5. Conflict. In the event of a conflict between the provisions of this X Purchaser Terms of Service and those of the X User Agreement, the provisions of this X Purchaser Terms of Service take precedence solely with respect to your use of a Paid Service. 6. DISPUTE RESOLUTION AND CLASS ACTION WAIVER a. Initial Dispute Resolution . Most disputes between you and X can be resolved informally. You may contact us by writing to Paid Support here . When you contact us, please provide a brief description of the nature and bases for your concerns, your contact information, and the specific relief you seek. The parties shall use their best efforts through this support process to settle disputes, claims, or controversies arising out of or relating to these Terms and/or your participation in the Program (individually a “ Dispute ,” or more than one, “ Disputes ”). You and we agree that good faith participation in this informal process is required and must be completed as set forth above before either party can initiate litigation regarding any Dispute, except with respect to requests for emergency injunctive relief (“ Exempted Dispute ”). If we cannot reach an agreed upon resolution with you regarding a Dispute (other than an Exempted Dispute) within a period of thirty (30) days from the time informal dispute resolution commences under the Initial Dispute Resolution provision above, then either you or we may initiate litigation. b. Choice of Law and Forum Selection . PLEASE READ THIS SECTION CAREFULLY – IT MAY SIGNIFICANTLY AFFECT YOUR LEGAL RIGHTS, INCLUDING YOUR RIGHT TO FILE A LAWSUIT IN COURT. The laws of the State of Texas, excluding its choice of law provisions, will govern these Terms and any dispute that arises between you and us, notwithstanding any other agreement between you and us to the contrary. All disputes related to these Terms, including any disputes, claims, or controversies arising out of or relating to these Terms, will be brought exclusively in the federal or state courts located in Tarrant County, Texas, United States, and you consent to personal jurisdiction in those forums and waive any objection as to inconvenient forum. Without prejudice to the foregoing, you agree that, in its sole discretion, X may bring any claim, cause of action, or dispute we have against you in any competent court in the country in which you reside that has jurisdiction and venue over the claim. If you are a federal, state, or local government entity in the United States in your official capacity and legally unable to accept the controlling law, jurisdiction or venue clauses above, then those clauses do not apply to you. For such U.S. federal government entities, this Agreement and any action related thereto will be governed by the laws of the United States of America (without reference to conflict of laws) and, in the absence of federal law and to the extent permitted under federal law, the laws of the State of Texas (excluding choice of law). c. YOU HAVE TWO YEARS TO BRING A CLAIM AGAINST X . You must bring any claim against X arising out of or related to these Terms within two (2) years after the date of the occurrence of the event or facts giving rise to the dispute, unless applicable law provides that the normal statute of limitations for that claim may not be shortened by agreement. If you do not bring a claim within this period, you forever waive the right to pursue any claim or cause of action, of any kind or character, based on such events or facts, and such claims or causes of action are permanently banned, and X will have no liability with respect to such claim. d. Class Action Waiver . To the extent permitted by law, you also waive the right to participate as a plaintiff or class member in any purported class action, collective action or representative action proceeding. X Purchaser Terms of Service If you live in the European Union, EFTA States, or the United Kingdom X allows you to access certain features in exchange for payment of a one-time or recurring fee, as applicable to the relevant features (each a “ Paid Service ” and collectively the " Paid Services "). For example, X Premium (as defined below) and Subscriptions would each be considered a “Paid Service.” To the extent that you sign up for and/or use a Paid Service, your use of the Paid Services and any corresponding transactions are subject to: (i) the terms and conditions set forth herein, including the applicable terms and conditions for each Paid Service you purchase, each as listed below (collectively, the “ X Purchaser Terms of Service ”), and (ii) the applicable X Terms of Service , X Privacy Policy , X Rules and Policies , and all policies incorporated therein (collectively, the “ X User Agreement ”). This X Purchaser Terms of Service and the aforementioned X User Agreement shall be collectively referred to in this document as the “ Terms ”. “ X ” refers to the X entity that provides the Paid Services to you. Please read these X Purchaser Terms of Service carefully to make sure you understand the applicable terms, conditions and exceptions. IF YOU LIVE IN THE EUROPEAN UNION, EFTA STATES, OR THE UNITED KINGDOM, THESE TERMS CONTAIN IMPORTANT INFORMATION THAT APPLY TO YOU ABOUT RESOLUTION OF DISPUTES, INCLUDING A WAIVER OF YOUR RIGHT TO BRING CLAIMS AS CLASS ACTIONS, AND A LIMITATION ON YOUR RIGHT TO BRING CLAIMS AGAINST X MORE THAN 1 YEAR AFTER THE RELEVANT EVENTS OCCURRED, WHICH IMPACT YOUR RIGHTS AND OBLIGATIONS IF ANY DISPUTE WITH X ARISES. SEE SECTION 6 UNDER GENERAL TERMS FOR DETAILS ON THESE PROVISIONS. Acceptance . By using or accessing a Paid Service(s) from X, submitting payment thereunder and/or clicking on a button to make a one-time purchase or recurring subscription payments for the Paid Service provided by X, you agree to be bound by the Terms. If you do not understand the Terms, or do not accept any part of them, then you may not use or access any Paid Services. To purchase and use a Paid Service you must: (i) be at least 18 years old or the age of majority as determined by the laws of the jurisdiction in which you live or (ii) have the express consent of your parent or guardian to purchase and use that Paid Service. If you are a parent or legal guardian and you allow your child (or a child that you are a guardian of) to purchase or use a Paid Service, you agree that the Terms apply to you, that you will abide by the Terms, and that you are responsible for the child’s activity on the Paid Services and for ensuring that the child also abides by the Terms. In any case, as stated in the Who May Use the Services section of the X Terms of Service, you must be at least 13 years old to use the X Service. If you are accepting these X Purchaser Terms of Service and using the Paid Services on behalf of a company, organization, government, or other legal entity, you represent and warrant that you are authorized to do so and have the authority to bind such entity to these X Purchaser Terms of Service, in which case the words “you” and “your” as used in these X Purchaser Terms of Service shall refer to such entity. X Contracting Entity . You enter into these X Purchaser Terms of Service with the entity that corresponds to where you live, as listed below. This entity will provide the Paid Services to you. No other entity is bound to any obligations to you under these Purchaser Terms of Service. Your Location The European Union, EFTA States, or the United Kingdom Contracting Entity X Internet Unlimited Company, with its registered office at One Cumberland Place, Fenian Street, Dublin 2, D02 AX07 Ireland Changes to Terms, Paid Services and Pricing 1. Changes to Terms. X may revise these X Purchaser Terms of Service for a valid and reasonable basis from time to time. A valid and reasonable basis may include, (i) a change in our services, for example due to technical, security-related or operational developments, (ii) the elimination of technical errors, (iii) a change in our business, for example due to policy, financial or other directional changes, (iv) a change in the legal situation, for example due to a change in the law, a request from an official agency, or a decision by a court, and (v) the optimization of the user experience through the implementation of new features. The changes will not be retroactive, and the most current version of the X Purchaser Terms of Service, available at legal.x.com/purchaser-terms , will govern your use of Paid Services and any corresponding transactions. If we modify or revise these Terms after you have agreed to them (for example, if these terms are modified after you have purchased a subscription), we undertake to notify you up to 30 days (depending on the specific changes) in advance of the entry into force of material revisions to these terms while setting a reasonable deadline for the user with respect to the changes and notifying you of the consequences of continued use after the deadline has expired. Such notification may be provided electronically, including (and without limitation to) via a service notification or an email to the email address associated with your account. In case you continue to use the Paid Services after the aforementioned deadline expires, you agree to be bound by the revised X Purchaser Terms of Service. If you do not agree to the changes to the X Purchaser Terms of Service, you will have to stop using or accessing (or continue to use or access) the Paid Services. The X Purchaser Terms of Service are written in English but are made available in multiple languages through translations. X strives to make the translations as accurate as possible to the original English version. However, in case of any discrepancies or inconsistencies, the English language version of the X Purchaser Terms of Service shall take precedence. You acknowledge that English shall be the language of reference for interpreting and constructing the terms of the X Purchaser Terms of Service. 2. Changes to Paid Services. Our Paid Services and our products and services evolve constantly. X may change the Paid Services for a reasonable and valid basis. Such a valid and reasonable basis may include (i) technical, security-related or operational developments, (ii) the elimination of technical errors, (iii) compliance with a changed legal situation, for example due to a change in the law, a request from an official agency, or a decision by a court, (iv) the optimization of the user experience through the implementation of new features, and (v) a change in our business, for example due to policy, financial circumstances or other directional changes. We will notify you of any changes to the Paid Services up to 30 days before they take effect, for example by means of a service notification or an email sent to the email address linked to your account, specifying the characteristics and effective date of the changes and informing you of your eventual right to terminate the subscription. The deadline may be shortened in the event of safety-related changes. The following shall not be considered as changes to the Paid Services within the meaning of this provision: (i) changes that affect the fundamental nature of the Paid Services and the essential characteristics of the service to be provided by X, and (ii) the permanent discontinuation of services. X is not liable to you for any modification, suspension or discontinuance of the Paid Services. Where legally required, the aforementioned limitation of liability does not apply (i) to the compensation for foreseeable damage in cases of slightly negligent breach of duties, insofar as their fulfillment is essential for the proper execution of the contract and users can rely on their fulfillment (essential contractual obligations), by X or its legal representatives or vicarious agents, and (ii) the liability of X for (a) a damage resulting from harm to life, body or health as well as for damages caused by intent or gross negligence on the part of X, its legal representatives, or vicarious agents, and (b) a damage due to non-compliance with a guarantee or warranted characteristic or as a result of a fraudulently concealed defect. The specific terms and conditions (included below) for the specific Paid Service specify how you can cancel a subscription or, when applicable, seek a refund. 3. Changes to Pricing. Prices for Paid Services, including recurring subscription fees, are subject to change from time to time due to change in the costs relating to operation, maintenance, technical provision, business considerations, and fees charged by third parties or statutory fees, at our reasonable discretion. In the event of an increase in costs, X reserves the right to adjust the prices for chargeable services. X will notify you of any price changes in writing up to 30 days before they take effect, for example by means of a service notification or an email to the email address linked to your account, stating your rights and the consequences of not exercising them. In the event of a price change, you may terminate the subscription to the applicable Paid Service or the user agreement up to 24 hours before the start of your next billing cycle, provided the cancellation is made within 30 days of receiving the notification. Otherwise, the price change will take effect at the time specified in the notification. For subscription services, price changes will take effect at the start of the next subscription period following the date of the effectiveness of the price change. Payment Terms . X offers various payment options that may vary by Paid Service, your device and/or operating system, your geographic location, or other factors. To the extent available (as X may make various purchase methods available from time to time), these payment options may include the ability to use “In app payment” functionality offered by Google or Apple, or to make a web payment using X's third party payment processor, Stripe ( www.stripe.com - hereafter “ Stripe ”). When you make a payment, you explicitly agree: (i) to pay the price listed for the Paid Service, along with any additional amounts relating to applicable taxes, credit card fees, bank fees, foreign transaction fees, foreign exchange fees, and currency fluctuations; and (ii) to abide by any relevant terms of service, privacy policies, or other legal agreements or restrictions (including additional age restrictions) imposed by Google, Apple, or Stripe (as X's third party payment processor) in connection with your use of a given payment method (for example only, if you choose to make your payment via Apple’s in-app purchasing functionality, you agree to abide by any relevant terms, requirements, and/or restrictions imposed by Apple). Any private personal data that you provide in connection with your use of the Paid Services including, without limitation, any data provided in connection with payment, will be processed in accordance with the X Privacy Policy. X may share your payment information with payment services providers to process payments; prevent, detect, and investigate fraud or other prohibited activities; facilitate dispute resolution such as chargebacks or refunds; and for other purposes associated with the acceptance of credit cards, debit cards, or ACH. It is your responsibility to make sure your banking, credit card, debit card, and/or other payment information is up to date, complete and accurate at all times. If you make a payment for a Paid Service, we may receive information about your transaction such as when it was made, when a subscription is set to expire or auto- renew, what platform you made the purchase on, and other information. X will not be responsible or liable for any errors made or delays by a payment processor, Apple’s App Store or the Google Play Store, your bank, your credit card company, and/or any payment network. Please refer to each specific Paid Service Terms and Conditions below for payment terms applicable to that specific Paid Service, including how subscription renewals are handled and other important terms. Application of X User Agreement, Termination, No Refunds, Multiple X Accounts, and Restrictions 1. The X User Agreement Applies to You . YOU MUST ALWAYS FOLLOW AND COMPLY WITH THE X USER AGREEMENT. The X User Agreement always applies to your use of the X Service, including the Paid Services and features. Your failure to follow and comply with the X User Agreement, or X's belief that you have failed to follow and comply with the X User Agreement, may result in the cancellation of your Paid Services. Any such cancellation will be in addition to, and without limitation of, any enforcement action that X may take against you pursuant to the X User Agreement. In such instances you may lose the benefits of your Paid Services and you will not be eligible for a refund for any amounts you have paid (or pre-paid) for Paid Services. 2. Why X Might Terminate Your Access to Paid Services. X may suspend or terminate your access to Paid Service(s), cease providing you with all or part of the Paid Services, or take any other action it deems appropriate, including, for example, suspend your account, (without any liability) at any time for any or no reason, including, but not limited to any of the following reasonable grounds: a. X believes, in its sole discretion, that you have violated the Terms or your use of the Paid Service(s) would violate any applicable laws; b. X is requested or directed to do so by any competent court of law, regulatory authority, or law enforcement agency; c. X has unexpected technical or security issues; d. X believes, in its sole reasonable discretion, you have violated the X User Agreement; e. X believes for valid reasons such as if you are engaging in manipulation, gaming, or other disruptive or prohibited conduct in connection with the Paid Services; f. You create risk or possible legal exposure for X; g. Your account should be removed due to unlawful conduct; h. Your account should be removed due to prolonged inactivity; or i. Our provision of the Paid Services (in whole or in part) to you is no longer commercially viable (in X's sole discretion). 3. All Transactions Are Final. All payments for Paid Services are final and not refundable or exchangeable, except as required by applicable law. We make no guarantee as to the nature, quality, or value of a Paid Service or the availability or supply thereof. Refunds or credits are not provided for any unused or partially used Paid Service (for example, a partially used subscription period). 4. Paid Services Are Non-Transferable between X Accounts. Each purchase of a Paid Service applies to a single X account, meaning that your purchase will apply solely to the account you were using when you purchased the Paid Service and will not apply to other accounts that you may have access to, or control over. If you have or control multiple accounts and you want access to Paid Services on each account, you must purchase the Paid Service on each account individually. 5. Restrictions and Obligations. a. You may only purchase and use a Paid Service if you are legally allowed to use the Paid Service in your country and you live in a country supported by X for the applicable Paid Service. X may, in its discretion, restrict the ability to access or purchase a Paid Service in certain countries. X reserves the right to modify the list of supported countries from time to time. b. We reserve the right to refuse Paid Services transactions or to cancel or discontinue the sale or use of a Paid Service in our sole discretion. c. You may not allow others to use your X account to access any Paid Service that such person did not order. d. You may not purchase or use a Paid Service if you are a person with whom U.S. persons are not permitted to have dealings pursuant to economic sanctions, including, without limitation, sanctions administered by the United States Department of the Treasury's Office of Foreign Assets Control or any other applicable sanctions authority (" Prohibited Person "). This includes, without limitation, persons located in, or ordinarily resident in, the following countries and regions: Cuba, Iran, the Ukraine regions of Crimea, North Korea and Syria. You represent and warrant that you are not a Prohibited Person. e. YOU REPRESENT THAT YOU WILL USE THE PAID SERVICES ONLY FOR LAWFUL PURPOSES AND ONLY IN ACCORDANCE WITH THE TERMS. Taxes and fees . You are responsible for and agree to pay any applicable taxes, duties, tariffs, and fees related to the purchase of Paid Services, including those required to be paid to either X or a third-party payment processor. These taxes may include, but are not limited to, VAT, GST, sales tax, withholding tax, and any other applicable taxes. Depending on your location, X may be responsible for collecting and reporting information related to transaction taxes arising from your purchase of Paid Services. You grant X permission to provide your account and personal information to relevant tax authorities to fulfill our tax collection and reporting obligations. General Terms 1. Contact Information. If you have any questions about the Paid Services or these Terms, you can check out the X Paid Services Help Center for more details. If you’ve already purchased a Paid Service, you can also contact us via the support link available in the navigation menu of your X account under the payment or subscription settings. If you have additional questions, then you can contact us here by using the “Help with paid features” form. 2. DISCLAIMERS. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, YOUR ACCESS TO AND USE OF THE PAID SERVICES IS AT YOUR OWN RISK. YOU UNDERSTAND AND AGREE THAT THE PAID SERVICES ARE PROVIDED TO YOU ON AN “AS IS” AND “AS AVAILABLE” BASIS. X DISCLAIMS ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS OR IMPLIED, OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. X MAKES NO WARRANTY OR REPRESENTATION AND DISCLAIMS ALL RESPONSIBILITY AND LIABILITY FOR: (I) THE COMPLETENESS, ACCURACY, AVAILABILITY, TIMELINESS, SECURITY OR RELIABILITY OF THE PAID SERVICES; AND (II) WHETHER THE PAID SERVICES WILL MEET YOUR REQUIREMENTS OR BE AVAILABLE ON AN UNINTERRUPTED, SECURE, OR ERROR-FREE BASIS. YOU ARE RESPONSIBLE FOR YOUR USE OF THE X SERVICE, INCLUDING THE PAID SERVICES, AND ANY CONTENT YOU PROVIDE. 3. LIMITATION OF LIABILITY. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE X ENTITIES SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS OR REVENUES, WHETHER INCURRED DIRECTLY OR INDIRECTLY, OR ANY LOSS OF DATA, USE, GOODWILL, OR OTHER INTANGIBLE LOSSES, RESULTING FROM (i) YOUR ACCESS TO OR USE OF OR INABILITY TO ACCESS OR USE THE PAID SERVICES; (ii) ANY CONDUCT OR CONTENT OF ANY THIRD PARTY POSTED THROUGH THE PAID SERVICES, INCLUDING WITHOUT LIMITATION, ANY DEFAMATORY, OFFENSIVE OR ILLEGAL CONDUCT OF OTHER USERS OR THIRD PARTIES; (iii) ANY CONTENT OBTAINED FROM THE PAID SERVICES; OR (iv) UNAUTHORIZED ACCESS, USE OR ALTERATION OF YOUR TRANSMISSIONS OR CONTENT. FOR THE AVOIDANCE OF DOUBT, THE DEFINITION OF PAID SERVICES IS LIMITED TO THE FEATURES OFFERED BY X AND DOES NOT INCLUDE ANY CONTENT YOU ACCESS AND/OR INTERACT WITH IN USING THOSE FEATURES. IN NO EVENT SHALL THE AGGREGATE LIABILITY OF THE X ENTITIES EXCEED THE GREATER OF ONE HUNDRED EUROS (€100.00) OR THE AMOUNT YOU PAID X, IF ANY, IN THE PAST SIX MONTHS FOR THE PAID SERVICES GIVING RISE TO THE CLAIM. THE LIMITATIONS OF THIS SUBSECTION SHALL APPLY TO ANY THEORY OF LIABILITY, WHETHER BASED ON WARRANTY, CONTRACT, STATUTE, TORT (INCLUDING NEGLIGENCE) OR OTHERWISE, AND WHETHER OR NOT THE X ENTITIES HAVE BEEN INFORMED OF THE POSSIBILITY OF ANY SUCH DAMAGE, AND EVEN IF A REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. THE “X ENTITIES” REFERS TO X, ITS PARENTS, AFFILIATES, RELATED COMPANIES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, REPRESENTATIVES, PARTNERS, AND LICENSORS. APPLICABLE LAW IN YOUR JURISDICTION MAY NOT ALLOW FOR CERTAIN LIMITATIONS OF LIABILITY. TO THE EXTENT REQUIRED BY APPLICABLE LAW IN YOUR JURISDICTION, THE ABOVE DOES NOT LIMIT THE X ENTITIES’ LIABILITY FOR FRAUD, FRAUDULENT MISREPRESENTATION, DEATH OR PERSONAL INJURY CAUSED BY OUR NEGLIGENCE, GROSS NEGLIGENCE, AND/OR INTENTIONAL CONDUCT. TO THE FULLEST EXTENT ALLOWED UNDER APPLICABLE LAW, THE X ENTITIES’ MAXIMUM AGGREGATE LIABILITY FOR ANY NON-EXCLUDABLE WARRANTIES IS LIMITED TO ONE HUNDRED EUROS (€100.00). 4. Notice Regarding Apple. To the extent that you purchased the Paid Services or are using or accessing the Paid Services on an iOS device, you further acknowledge and agree to the terms of this Section. You acknowledge that the Terms are between you and us only, not with Apple, and Apple is not responsible for the Paid Services and the content thereof. Apple has no obligation whatsoever to furnish any maintenance and support service with respect to the Paid Services. In the event of any failure of the Paid Services to conform to any applicable warranty, then you may notify Apple and Apple will refund any applicable purchase price for the Paid Services to you; and, to the maximum extent permitted by applicable law, Apple has no other warranty obligation whatsoever with respect to the Paid Services. Apple is not responsible for addressing any claims by you or any third-party relating to the Paid Services or your possession and/or use of the Paid Services, including, but not limited to: (i) product liability claims; (ii) any claim that the Paid Services fail to conform to any applicable legal or regulatory requirement; and (iii) claims arising under consumer protection or similar legislation. Apple is not responsible for the investigation, defense, settlement and discharge of any third-party claim that the Paid Services and/or your possession and use of the mobile application infringe that third-party’s intellectual property rights. You agree to comply with any applicable third-party terms when using the Paid Services. Apple, and Apple’s subsidiaries, are third-party beneficiaries of the Terms, and upon your acceptance of the Terms, Apple will have the right (and will be deemed to have accepted the right) to enforce the Terms against you as a third-party beneficiary of the Terms. You hereby represent and warrant that (i) you are not located in a country that is subject to a U.S. Government embargo, or that has been designated by the U.S. Government as a "terrorist supporting" country; and (ii) you are not listed on any U.S. Government list of prohibited or restricted parties. 5. Conflict. In the event of a conflict between the provisions of this X Purchaser Terms of Service and those of the X User Agreement, the provisions of this X Purchaser Terms of Service take precedence solely with respect to your use of a Paid Service. 6. DISPUTE RESOLUTION AND CLASS ACTION WAIVER a. Initial Dispute Resolution . Most disputes between you and X can be resolved informally. You may contact us by writing to Paid Support here . When you contact us, please provide a brief description of the nature and bases for your concerns, your contact information, and the specific relief you seek. The parties shall use their best efforts through this support process to settle disputes, claims, or controversies arising out of or relating to these Terms and/or your participation in the Program (individually a “ Dispute ,” or more than one, “ Disputes ”). You and we agree that good faith participation in this informal process is required and must be completed as set forth above before either party can initiate litigation regarding any Dispute, except with respect to requests for emergency injunctive relief (“ Exempted Dispute ”). If we cannot reach an agreed upon resolution with you regarding a Dispute (other than an Exempted Dispute) within a period of thirty (30) days from the time informal dispute resolution commences under the Initial Dispute Resolution provision above, then either you or we may initiate litigation. b. Choice of Law and Forum Selection . PLEASE READ THIS SECTION CAREFULLY – IT MAY SIGNIFICANTLY AFFECT YOUR LEGAL RIGHTS, INCLUDING YOUR RIGHT TO FILE A LAWSUIT IN COURT. To the extent permitted by law, all disputes related to these Terms, including any disputes, claims, or controversies arising out of or relating to these Terms will be brought exclusively before a competent court in Ireland without regard to conflict of law provisions a | 2026-01-13T08:48:42 |
https://dev.to/szabgab/perl-weekly-591-less-than-50-use-ci-4966 | Perl 🐪 Weekly #591 - Less than 50% use CI - 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 Gabor Szabo Posted on Nov 21, 2022 • Edited on Feb 24, 2025 • Originally published at perlweekly.com Perl 🐪 Weekly #591 - Less than 50% use CI # perl # news # programming perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? Originally published at Perl Weekly 591 Hi there, One of the best things about programming is that you can get almost immediate feedback from your work. The compiler tells you immediately if your code has syntax errors. Your tests can tell you within minutes if your code does what you expected on your computer. Your CI system can tell you within another few minutes if your code works on various other environments. In the Perl community writing test became the norm. You rarely find any Open Source Perl code without tests. People write test even for code that only they use. Even for code they consider 'toys'. Yet with CI we are still far from it. On our stats page you can see that 12% are missing their link to VCS (some of those do have VCS they are just missing the link), but 45-60% (depending on the week) of CPAN releases have no CI configured. From experience I know that corporations are way behind the curve in terms of test writing. So I can only imagine how few use Continuous Integration. There is a lot of work to be done. Enjoy your week! -- Your editor: Gabor Szabo. Sponsors Personalized investment with Torto AI Any investment in the stock market is partially based on objective data (e.g. P/E ratio) and partially on the subjective world-view of the investor (expected changes in inflation, politics, weather etc.) torto.ai works on providing you a platform where you can easily combine these aspects and find the investment that most suitable for your expectation. Articles Template::Perlish: added functions injection Lured by overengineering Working on a little website for helping people getting started and up to speed in using The GNU Privacy Guard. Is local a bad part in Perl? Yuki thinks it is. Beyond Perl Thinking aloud about the ways I can server the people who are using Perl. Discussion Code Maven Reddit community I have created a Reddit community for people who are interested to follow the Code Maven site and discuss the topic I cover there. I'd like to invite you to join it. Perl 5 This Week in PSC (087) This is a post of the Perl Steering Council. It seems like post 87, but we only saw post 86. Check out all the posts . Live streaming the release of Perl 5.37.6 By the time the Perl Weekly reaches you this will be over, but I hope it is recorded so you will be able to see the recording. The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 192 Welcome to a new week with a couple of fun tasks "Binary Flip" and "Equal Distribution". If you are new to the weekly challenge then why not join us and have fun every week. For more information, please read the FAQ . RECAP - The Weekly Challenge - 191 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Twice Largest" and "Cute List" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Twice Largest Once Cute Nice story behind the process and improvement to the algorithm. Thanks for sharing. Twice as Cute Complicated algorithm made simple using the Raku power, great skill, keep it up. Counting Cute Colin sharing two different methods to work on Cute List task. Getting the finest detail is really useful. PWC191 - Twice Largest For me, "The Quations" section is more attractive than the "The solution" section. Thanks for your contributions. PWC191 - Cute List I loved how Flavio play with numbers. Ideal use case for recursive. Keep it up great work. Perl Weekly Challenge: Week 191 Lots of Raku magic found in the blog post. Good for someone new to the language. The Weekly Challenge 191 You will never find Jame's blog boring, in terms of content and quality. Highly Recommended. Perl Weekly Challenge 191: Twice Largest and Cute List Clarity of inner details can be found in the blog. Great work, thanks for sharing. permutations! Nice demo of Raku power in the blog. Anyone interested to learn Raku should follow the blog. Perl Weekly Challenge 191 Another week with special one-liner in Perl. Well done. Keep it up. The twice largest and number of cuties Cute use of recursive subroutine to solve the task "Cute List". Great work, keep it up. Large but Cute Roger also shared different approaches to deal with Cute List task, Not to be missed, highly recommended. The cute recursive function Smart observations make the task simple and easy to follow. Once again, we get Perl and Python discussed in the blog post. PWC 191 Loved the honest approach and discuss the issues gives much clarity. Keep it up great work. Videos Reporting issues on GitHub (for Perl Advent) A video to explain how to open an issue to report a bug or some other deficiency in a system. Triggered by a post in the Perl Programmers Facebook group I checked out the Perl Advent-related links on MetaCPAN . One was broken and while trying to figure out what's going on I found 2 more issues. The Unicorn Project & The Five Ideals - Gene Kim - YOW! 2019 A long, but excellent presentation by Gene Kim. What he talks about is extremely important and valuable. Both for leaders and for lone developers who work on Open Source projects. One of the key points he make is always improving the development process and shortening the feedback loop. Other More Perl to Go Conversions Big Changes in Precious v0.4.0 Precious is a code quality meta-tool for configuring a collection of linters and tidiers for a project. Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . Perl Jobs by Perl Careers Senior Perl Developer with Cross-Trained Chops. UK Remote Perl Role The client is interested in anyone with experience building web apps in Perl, using one of the major Perl frameworks. If you’re a crack-hand with Catalyst, a Mojolicious master, or a distinguished Dancer, they want you. You’ll be deploying apps your work to AWS, so experience would be handy, and the company’s big on testing, so they’d like you to know your way around Test::More. Adventure! Senior Perl roles in Malaysia, Dubai and Malta Clever folks know that if you’re lucky, you can earn a living and have an adventure at the same time. Enter our international client: online trading is their game, and they’re looking for Perl developers with passion, drive, and an appreciation for new experiences. Perl Superheroes Wanted! Remote Perl within US time zone As the leading provider of award-winning intelligent SaaS solutions for clients that include first responders, engineers, manufacturers, and educators, this organization’s comprehensive offerings include training management, continuing education, compliance training, safety management, and workforce scheduling. Looking for strong Modern Perl developers with Catalyst/Mojolicious + DBIx::Class. Perl Developer and Business Owner? Remote Perl role in UK & EU Our clients run a job search engine that has grown from two friends with an idea to a site that receives more than 10 million visits per month. They're looking for a Perl pro with at least three years of experience with high-volume and high-traffic apps and sites, a solid understanding of Object-Oriented Perl (perks if that knowledge includes Moose), SQL/MySQL and DBIx::Class. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #755 - Does TIOBE help Perl? # perl # news # programming Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming 💎 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:48:42 |
https://docs.python.org/3/glossary.html#term-0 | Glossary — Python 3.14.2 documentation Theme Auto Light Dark Previous topic Deprecations Next topic About this documentation This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » Glossary | Theme Auto Light Dark | Glossary ¶ >>> ¶ The default Python prompt of the interactive shell. Often seen for code examples which can be executed interactively in the interpreter. ... ¶ Can refer to: The default Python prompt of the interactive shell when entering the code for an indented code block, when within a pair of matching left and right delimiters (parentheses, square brackets, curly braces or triple quotes), or after specifying a decorator. The three dots form of the Ellipsis object. abstract base class ¶ Abstract base classes complement duck-typing by providing a way to define interfaces when other techniques like hasattr() would be clumsy or subtly wrong (for example with magic methods ). ABCs introduce virtual subclasses, which are classes that don’t inherit from a class but are still recognized by isinstance() and issubclass() ; see the abc module documentation. Python comes with many built-in ABCs for data structures (in the collections.abc module), numbers (in the numbers module), streams (in the io module), import finders and loaders (in the importlib.abc module). You can create your own ABCs with the abc module. annotate function ¶ A function that can be called to retrieve the annotations of an object. This function is accessible as the __annotate__ attribute of functions, classes, and modules. Annotate functions are a subset of evaluate functions . annotation ¶ A label associated with a variable, a class attribute or a function parameter or return value, used by convention as a type hint . Annotations of local variables cannot be accessed at runtime, but annotations of global variables, class attributes, and functions can be retrieved by calling annotationlib.get_annotations() on modules, classes, and functions, respectively. See variable annotation , function annotation , PEP 484 , PEP 526 , and PEP 649 , which describe this functionality. Also see Annotations Best Practices for best practices on working with annotations. argument ¶ A value passed to a function (or method ) when calling the function. There are two kinds of argument: keyword argument : an argument preceded by an identifier (e.g. name= ) in a function call or passed as a value in a dictionary preceded by ** . For example, 3 and 5 are both keyword arguments in the following calls to complex() : complex ( real = 3 , imag = 5 ) complex ( ** { 'real' : 3 , 'imag' : 5 }) positional argument : an argument that is not a keyword argument. Positional arguments can appear at the beginning of an argument list and/or be passed as elements of an iterable preceded by * . For example, 3 and 5 are both positional arguments in the following calls: complex ( 3 , 5 ) complex ( * ( 3 , 5 )) Arguments are assigned to the named local variables in a function body. See the Calls section for the rules governing this assignment. Syntactically, any expression can be used to represent an argument; the evaluated value is assigned to the local variable. See also the parameter glossary entry, the FAQ question on the difference between arguments and parameters , and PEP 362 . asynchronous context manager ¶ An object which controls the environment seen in an async with statement by defining __aenter__() and __aexit__() methods. Introduced by PEP 492 . asynchronous generator ¶ A function which returns an asynchronous generator iterator . It looks like a coroutine function defined with async def except that it contains yield expressions for producing a series of values usable in an async for loop. Usually refers to an asynchronous generator function, but may refer to an asynchronous generator iterator in some contexts. In cases where the intended meaning isn’t clear, using the full terms avoids ambiguity. An asynchronous generator function may contain await expressions as well as async for , and async with statements. asynchronous generator iterator ¶ An object created by an asynchronous generator function. This is an asynchronous iterator which when called using the __anext__() method returns an awaitable object which will execute the body of the asynchronous generator function until the next yield expression. Each yield temporarily suspends processing, remembering the execution state (including local variables and pending try-statements). When the asynchronous generator iterator effectively resumes with another awaitable returned by __anext__() , it picks up where it left off. See PEP 492 and PEP 525 . asynchronous iterable ¶ An object, that can be used in an async for statement. Must return an asynchronous iterator from its __aiter__() method. Introduced by PEP 492 . asynchronous iterator ¶ An object that implements the __aiter__() and __anext__() methods. __anext__() must return an awaitable object. async for resolves the awaitables returned by an asynchronous iterator’s __anext__() method until it raises a StopAsyncIteration exception. Introduced by PEP 492 . atomic operation ¶ An operation that appears to execute as a single, indivisible step: no other thread can observe it half-done, and its effects become visible all at once. Python does not guarantee that high-level statements are atomic (for example, x += 1 performs multiple bytecode operations and is not atomic). Atomicity is only guaranteed where explicitly documented. See also race condition and data race . attached thread state ¶ A thread state that is active for the current OS thread. When a thread state is attached, the OS thread has access to the full Python C API and can safely invoke the bytecode interpreter. Unless a function explicitly notes otherwise, attempting to call the C API without an attached thread state will result in a fatal error or undefined behavior. A thread state can be attached and detached explicitly by the user through the C API, or implicitly by the runtime, including during blocking C calls and by the bytecode interpreter in between calls. On most builds of Python, having an attached thread state implies that the caller holds the GIL for the current interpreter, so only one OS thread can have an attached thread state at a given moment. In free-threaded builds of Python, threads can concurrently hold an attached thread state, allowing for true parallelism of the bytecode interpreter. attribute ¶ A value associated with an object which is usually referenced by name using dotted expressions. For example, if an object o has an attribute a it would be referenced as o.a . It is possible to give an object an attribute whose name is not an identifier as defined by Names (identifiers and keywords) , for example using setattr() , if the object allows it. Such an attribute will not be accessible using a dotted expression, and would instead need to be retrieved with getattr() . awaitable ¶ An object that can be used in an await expression. Can be a coroutine or an object with an __await__() method. See also PEP 492 . BDFL ¶ Benevolent Dictator For Life, a.k.a. Guido van Rossum , Python’s creator. binary file ¶ A file object able to read and write bytes-like objects . Examples of binary files are files opened in binary mode ( 'rb' , 'wb' or 'rb+' ), sys.stdin.buffer , sys.stdout.buffer , and instances of io.BytesIO and gzip.GzipFile . See also text file for a file object able to read and write str objects. borrowed reference ¶ In Python’s C API, a borrowed reference is a reference to an object, where the code using the object does not own the reference. It becomes a dangling pointer if the object is destroyed. For example, a garbage collection can remove the last strong reference to the object and so destroy it. Calling Py_INCREF() on the borrowed reference is recommended to convert it to a strong reference in-place, except when the object cannot be destroyed before the last usage of the borrowed reference. The Py_NewRef() function can be used to create a new strong reference . bytes-like object ¶ An object that supports the Buffer Protocol and can export a C- contiguous buffer. This includes all bytes , bytearray , and array.array objects, as well as many common memoryview objects. Bytes-like objects can be used for various operations that work with binary data; these include compression, saving to a binary file, and sending over a socket. Some operations need the binary data to be mutable. The documentation often refers to these as “read-write bytes-like objects”. Example mutable buffer objects include bytearray and a memoryview of a bytearray . Other operations require the binary data to be stored in immutable objects (“read-only bytes-like objects”); examples of these include bytes and a memoryview of a bytes object. bytecode ¶ Python source code is compiled into bytecode, the internal representation of a Python program in the CPython interpreter. The bytecode is also cached in .pyc files so that executing the same file is faster the second time (recompilation from source to bytecode can be avoided). This “intermediate language” is said to run on a virtual machine that executes the machine code corresponding to each bytecode. Do note that bytecodes are not expected to work between different Python virtual machines, nor to be stable between Python releases. A list of bytecode instructions can be found in the documentation for the dis module . callable ¶ A callable is an object that can be called, possibly with a set of arguments (see argument ), with the following syntax: callable ( argument1 , argument2 , argumentN ) A function , and by extension a method , is a callable. An instance of a class that implements the __call__() method is also a callable. callback ¶ A subroutine function which is passed as an argument to be executed at some point in the future. class ¶ A template for creating user-defined objects. Class definitions normally contain method definitions which operate on instances of the class. class variable ¶ A variable defined in a class and intended to be modified only at class level (i.e., not in an instance of the class). closure variable ¶ A free variable referenced from a nested scope that is defined in an outer scope rather than being resolved at runtime from the globals or builtin namespaces. May be explicitly defined with the nonlocal keyword to allow write access, or implicitly defined if the variable is only being read. For example, in the inner function in the following code, both x and print are free variables , but only x is a closure variable : def outer (): x = 0 def inner (): nonlocal x x += 1 print ( x ) return inner Due to the codeobject.co_freevars attribute (which, despite its name, only includes the names of closure variables rather than listing all referenced free variables), the more general free variable term is sometimes used even when the intended meaning is to refer specifically to closure variables. complex number ¶ An extension of the familiar real number system in which all numbers are expressed as a sum of a real part and an imaginary part. Imaginary numbers are real multiples of the imaginary unit (the square root of -1 ), often written i in mathematics or j in engineering. Python has built-in support for complex numbers, which are written with this latter notation; the imaginary part is written with a j suffix, e.g., 3+1j . To get access to complex equivalents of the math module, use cmath . Use of complex numbers is a fairly advanced mathematical feature. If you’re not aware of a need for them, it’s almost certain you can safely ignore them. concurrency ¶ The ability of a computer program to perform multiple tasks at the same time. Python provides libraries for writing programs that make use of different forms of concurrency. asyncio is a library for dealing with asynchronous tasks and coroutines. threading provides access to operating system threads and multiprocessing to operating system processes. Multi-core processors can execute threads and processes on different CPU cores at the same time (see parallelism ). concurrent modification ¶ When multiple threads modify shared data at the same time. Concurrent modification without proper synchronization can cause race conditions , and might also trigger a data race , data corruption, or both. context ¶ This term has different meanings depending on where and how it is used. Some common meanings: The temporary state or environment established by a context manager via a with statement. The collection of keyvalue bindings associated with a particular contextvars.Context object and accessed via ContextVar objects. Also see context variable . A contextvars.Context object. Also see current context . context management protocol ¶ The __enter__() and __exit__() methods called by the with statement. See PEP 343 . context manager ¶ An object which implements the context management protocol and controls the environment seen in a with statement. See PEP 343 . context variable ¶ A variable whose value depends on which context is the current context . Values are accessed via contextvars.ContextVar objects. Context variables are primarily used to isolate state between concurrent asynchronous tasks. contiguous ¶ A buffer is considered contiguous exactly if it is either C-contiguous or Fortran contiguous . Zero-dimensional buffers are C and Fortran contiguous. In one-dimensional arrays, the items must be laid out in memory next to each other, in order of increasing indexes starting from zero. In multidimensional C-contiguous arrays, the last index varies the fastest when visiting items in order of memory address. However, in Fortran contiguous arrays, the first index varies the fastest. coroutine ¶ Coroutines are a more generalized form of subroutines. Subroutines are entered at one point and exited at another point. Coroutines can be entered, exited, and resumed at many different points. They can be implemented with the async def statement. See also PEP 492 . coroutine function ¶ A function which returns a coroutine object. A coroutine function may be defined with the async def statement, and may contain await , async for , and async with keywords. These were introduced by PEP 492 . CPython ¶ The canonical implementation of the Python programming language, as distributed on python.org . The term “CPython” is used when necessary to distinguish this implementation from others such as Jython or IronPython. current context ¶ The context ( contextvars.Context object) that is currently used by ContextVar objects to access (get or set) the values of context variables . Each thread has its own current context. Frameworks for executing asynchronous tasks (see asyncio ) associate each task with a context which becomes the current context whenever the task starts or resumes execution. cyclic isolate ¶ A subgroup of one or more objects that reference each other in a reference cycle, but are not referenced by objects outside the group. The goal of the cyclic garbage collector is to identify these groups and break the reference cycles so that the memory can be reclaimed. data race ¶ A situation where multiple threads access the same memory location concurrently, at least one of the accesses is a write, and the threads do not use any synchronization to control their access. Data races lead to non-deterministic behavior and can cause data corruption. Proper use of locks and other synchronization primitives prevents data races. Note that data races can only happen in native code, but that native code might be exposed in a Python API. See also race condition and thread-safe . deadlock ¶ A situation in which two or more tasks (threads, processes, or coroutines) wait indefinitely for each other to release resources or complete actions, preventing any from making progress. For example, if thread A holds lock 1 and waits for lock 2, while thread B holds lock 2 and waits for lock 1, both threads will wait indefinitely. In Python this often arises from acquiring multiple locks in conflicting orders or from circular join/await dependencies. Deadlocks can be avoided by always acquiring multiple locks in a consistent order. See also lock and reentrant . decorator ¶ A function returning another function, usually applied as a function transformation using the @wrapper syntax. Common examples for decorators are classmethod() and staticmethod() . The decorator syntax is merely syntactic sugar, the following two function definitions are semantically equivalent: def f ( arg ): ... f = staticmethod ( f ) @staticmethod def f ( arg ): ... The same concept exists for classes, but is less commonly used there. See the documentation for function definitions and class definitions for more about decorators. descriptor ¶ Any object which defines the methods __get__() , __set__() , or __delete__() . When a class attribute is a descriptor, its special binding behavior is triggered upon attribute lookup. Normally, using a.b to get, set or delete an attribute looks up the object named b in the class dictionary for a , but if b is a descriptor, the respective descriptor method gets called. Understanding descriptors is a key to a deep understanding of Python because they are the basis for many features including functions, methods, properties, class methods, static methods, and reference to super classes. For more information about descriptors’ methods, see Implementing Descriptors or the Descriptor How To Guide . dictionary ¶ An associative array, where arbitrary keys are mapped to values. The keys can be any object with __hash__() and __eq__() methods. Called a hash in Perl. dictionary comprehension ¶ A compact way to process all or part of the elements in an iterable and return a dictionary with the results. results = {n: n ** 2 for n in range(10)} generates a dictionary containing key n mapped to value n ** 2 . See Displays for lists, sets and dictionaries . dictionary view ¶ The objects returned from dict.keys() , dict.values() , and dict.items() are called dictionary views. They provide a dynamic view on the dictionary’s entries, which means that when the dictionary changes, the view reflects these changes. To force the dictionary view to become a full list use list(dictview) . See Dictionary view objects . docstring ¶ A string literal which appears as the first expression in a class, function or module. While ignored when the suite is executed, it is recognized by the compiler and put into the __doc__ attribute of the enclosing class, function or module. Since it is available via introspection, it is the canonical place for documentation of the object. duck-typing ¶ A programming style which does not look at an object’s type to determine if it has the right interface; instead, the method or attribute is simply called or used (“If it looks like a duck and quacks like a duck, it must be a duck.”) By emphasizing interfaces rather than specific types, well-designed code improves its flexibility by allowing polymorphic substitution. Duck-typing avoids tests using type() or isinstance() . (Note, however, that duck-typing can be complemented with abstract base classes .) Instead, it typically employs hasattr() tests or EAFP programming. dunder ¶ An informal short-hand for “double underscore”, used when talking about a special method . For example, __init__ is often pronounced “dunder init”. EAFP ¶ Easier to ask for forgiveness than permission. This common Python coding style assumes the existence of valid keys or attributes and catches exceptions if the assumption proves false. This clean and fast style is characterized by the presence of many try and except statements. The technique contrasts with the LBYL style common to many other languages such as C. evaluate function ¶ A function that can be called to evaluate a lazily evaluated attribute of an object, such as the value of type aliases created with the type statement. expression ¶ A piece of syntax which can be evaluated to some value. In other words, an expression is an accumulation of expression elements like literals, names, attribute access, operators or function calls which all return a value. In contrast to many other languages, not all language constructs are expressions. There are also statement s which cannot be used as expressions, such as while . Assignments are also statements, not expressions. extension module ¶ A module written in C or C++, using Python’s C API to interact with the core and with user code. f-string ¶ f-strings ¶ String literals prefixed with f or F are commonly called “f-strings” which is short for formatted string literals . See also PEP 498 . file object ¶ An object exposing a file-oriented API (with methods such as read() or write() ) to an underlying resource. Depending on the way it was created, a file object can mediate access to a real on-disk file or to another type of storage or communication device (for example standard input/output, in-memory buffers, sockets, pipes, etc.). File objects are also called file-like objects or streams . There are actually three categories of file objects: raw binary files , buffered binary files and text files . Their interfaces are defined in the io module. The canonical way to create a file object is by using the open() function. file-like object ¶ A synonym for file object . filesystem encoding and error handler ¶ Encoding and error handler used by Python to decode bytes from the operating system and encode Unicode to the operating system. The filesystem encoding must guarantee to successfully decode all bytes below 128. If the file system encoding fails to provide this guarantee, API functions can raise UnicodeError . The sys.getfilesystemencoding() and sys.getfilesystemencodeerrors() functions can be used to get the filesystem encoding and error handler. The filesystem encoding and error handler are configured at Python startup by the PyConfig_Read() function: see filesystem_encoding and filesystem_errors members of PyConfig . See also the locale encoding . finder ¶ An object that tries to find the loader for a module that is being imported. There are two types of finder: meta path finders for use with sys.meta_path , and path entry finders for use with sys.path_hooks . See Finders and loaders and importlib for much more detail. floor division ¶ Mathematical division that rounds down to nearest integer. The floor division operator is // . For example, the expression 11 // 4 evaluates to 2 in contrast to the 2.75 returned by float true division. Note that (-11) // 4 is -3 because that is -2.75 rounded downward . See PEP 238 . free threading ¶ A threading model where multiple threads can run Python bytecode simultaneously within the same interpreter. This is in contrast to the global interpreter lock which allows only one thread to execute Python bytecode at a time. See PEP 703 . free variable ¶ Formally, as defined in the language execution model , a free variable is any variable used in a namespace which is not a local variable in that namespace. See closure variable for an example. Pragmatically, due to the name of the codeobject.co_freevars attribute, the term is also sometimes used as a synonym for closure variable . function ¶ A series of statements which returns some value to a caller. It can also be passed zero or more arguments which may be used in the execution of the body. See also parameter , method , and the Function definitions section. function annotation ¶ An annotation of a function parameter or return value. Function annotations are usually used for type hints : for example, this function is expected to take two int arguments and is also expected to have an int return value: def sum_two_numbers ( a : int , b : int ) -> int : return a + b Function annotation syntax is explained in section Function definitions . See variable annotation and PEP 484 , which describe this functionality. Also see Annotations Best Practices for best practices on working with annotations. __future__ ¶ A future statement , from __future__ import <feature> , directs the compiler to compile the current module using syntax or semantics that will become standard in a future release of Python. The __future__ module documents the possible values of feature . By importing this module and evaluating its variables, you can see when a new feature was first added to the language and when it will (or did) become the default: >>> import __future__ >>> __future__ . division _Feature((2, 2, 0, 'alpha', 2), (3, 0, 0, 'alpha', 0), 8192) garbage collection ¶ The process of freeing memory when it is not used anymore. Python performs garbage collection via reference counting and a cyclic garbage collector that is able to detect and break reference cycles. The garbage collector can be controlled using the gc module. generator ¶ A function which returns a generator iterator . It looks like a normal function except that it contains yield expressions for producing a series of values usable in a for-loop or that can be retrieved one at a time with the next() function. Usually refers to a generator function, but may refer to a generator iterator in some contexts. In cases where the intended meaning isn’t clear, using the full terms avoids ambiguity. generator iterator ¶ An object created by a generator function. Each yield temporarily suspends processing, remembering the execution state (including local variables and pending try-statements). When the generator iterator resumes, it picks up where it left off (in contrast to functions which start fresh on every invocation). generator expression ¶ An expression that returns an iterator . It looks like a normal expression followed by a for clause defining a loop variable, range, and an optional if clause. The combined expression generates values for an enclosing function: >>> sum ( i * i for i in range ( 10 )) # sum of squares 0, 1, 4, ... 81 285 generic function ¶ A function composed of multiple functions implementing the same operation for different types. Which implementation should be used during a call is determined by the dispatch algorithm. See also the single dispatch glossary entry, the functools.singledispatch() decorator, and PEP 443 . generic type ¶ A type that can be parameterized; typically a container class such as list or dict . Used for type hints and annotations . For more details, see generic alias types , PEP 483 , PEP 484 , PEP 585 , and the typing module. GIL ¶ See global interpreter lock . global interpreter lock ¶ The mechanism used by the CPython interpreter to assure that only one thread executes Python bytecode at a time. This simplifies the CPython implementation by making the object model (including critical built-in types such as dict ) implicitly safe against concurrent access. Locking the entire interpreter makes it easier for the interpreter to be multi-threaded, at the expense of much of the parallelism afforded by multi-processor machines. However, some extension modules, either standard or third-party, are designed so as to release the GIL when doing computationally intensive tasks such as compression or hashing. Also, the GIL is always released when doing I/O. As of Python 3.13, the GIL can be disabled using the --disable-gil build configuration. After building Python with this option, code must be run with -X gil=0 or after setting the PYTHON_GIL=0 environment variable. This feature enables improved performance for multi-threaded applications and makes it easier to use multi-core CPUs efficiently. For more details, see PEP 703 . In prior versions of Python’s C API, a function might declare that it requires the GIL to be held in order to use it. This refers to having an attached thread state . global state ¶ Data that is accessible throughout a program, such as module-level variables, class variables, or C static variables in extension modules . In multi-threaded programs, global state shared between threads typically requires synchronization to avoid race conditions and data races . hash-based pyc ¶ A bytecode cache file that uses the hash rather than the last-modified time of the corresponding source file to determine its validity. See Cached bytecode invalidation . hashable ¶ An object is hashable if it has a hash value which never changes during its lifetime (it needs a __hash__() method), and can be compared to other objects (it needs an __eq__() method). Hashable objects which compare equal must have the same hash value. Hashability makes an object usable as a dictionary key and a set member, because these data structures use the hash value internally. Most of Python’s immutable built-in objects are hashable; mutable containers (such as lists or dictionaries) are not; immutable containers (such as tuples and frozensets) are only hashable if their elements are hashable. Objects which are instances of user-defined classes are hashable by default. They all compare unequal (except with themselves), and their hash value is derived from their id() . IDLE ¶ An Integrated Development and Learning Environment for Python. IDLE — Python editor and shell is a basic editor and interpreter environment which ships with the standard distribution of Python. immortal ¶ Immortal objects are a CPython implementation detail introduced in PEP 683 . If an object is immortal, its reference count is never modified, and therefore it is never deallocated while the interpreter is running. For example, True and None are immortal in CPython. Immortal objects can be identified via sys._is_immortal() , or via PyUnstable_IsImmortal() in the C API. immutable ¶ An object with a fixed value. Immutable objects include numbers, strings and tuples. Such an object cannot be altered. A new object has to be created if a different value has to be stored. They play an important role in places where a constant hash value is needed, for example as a key in a dictionary. Immutable objects are inherently thread-safe because their state cannot be modified after creation, eliminating concerns about improperly synchronized concurrent modification . import path ¶ A list of locations (or path entries ) that are searched by the path based finder for modules to import. During import, this list of locations usually comes from sys.path , but for subpackages it may also come from the parent package’s __path__ attribute. importing ¶ The process by which Python code in one module is made available to Python code in another module. importer ¶ An object that both finds and loads a module; both a finder and loader object. interactive ¶ Python has an interactive interpreter which means you can enter statements and expressions at the interpreter prompt, immediately execute them and see their results. Just launch python with no arguments (possibly by selecting it from your computer’s main menu). It is a very powerful way to test out new ideas or inspect modules and packages (remember help(x) ). For more on interactive mode, see Interactive Mode . interpreted ¶ Python is an interpreted language, as opposed to a compiled one, though the distinction can be blurry because of the presence of the bytecode compiler. This means that source files can be run directly without explicitly creating an executable which is then run. Interpreted languages typically have a shorter development/debug cycle than compiled ones, though their programs generally also run more slowly. See also interactive . interpreter shutdown ¶ When asked to shut down, the Python interpreter enters a special phase where it gradually releases all allocated resources, such as modules and various critical internal structures. It also makes several calls to the garbage collector . This can trigger the execution of code in user-defined destructors or weakref callbacks. Code executed during the shutdown phase can encounter various exceptions as the resources it relies on may not function anymore (common examples are library modules or the warnings machinery). The main reason for interpreter shutdown is that the __main__ module or the script being run has finished executing. iterable ¶ An object capable of returning its members one at a time. Examples of iterables include all sequence types (such as list , str , and tuple ) and some non-sequence types like dict , file objects , and objects of any classes you define with an __iter__() method or with a __getitem__() method that implements sequence semantics. Iterables can be used in a for loop and in many other places where a sequence is needed ( zip() , map() , …). When an iterable object is passed as an argument to the built-in function iter() , it returns an iterator for the object. This iterator is good for one pass over the set of values. When using iterables, it is usually not necessary to call iter() or deal with iterator objects yourself. The for statement does that automatically for you, creating a temporary unnamed variable to hold the iterator for the duration of the loop. See also iterator , sequence , and generator . iterator ¶ An object representing a stream of data. Repeated calls to the iterator’s __next__() method (or passing it to the built-in function next() ) return successive items in the stream. When no more data are available a StopIteration exception is raised instead. At this point, the iterator object is exhausted and any further calls to its __next__() method just raise StopIteration again. Iterators are required to have an __iter__() method that returns the iterator object itself so every iterator is also iterable and may be used in most places where other iterables are accepted. One notable exception is code which attempts multiple iteration passes. A container object (such as a list ) produces a fresh new iterator each time you pass it to the iter() function or use it in a for loop. Attempting this with an iterator will just return the same exhausted iterator object used in the previous iteration pass, making it appear like an empty container. More information can be found in Iterator Types . CPython implementation detail: CPython does not consistently apply the requirement that an iterator define __iter__() . And also please note that free-threaded CPython does not guarantee thread-safe behavior of iterator operations. key function ¶ A key function or collation function is a callable that returns a value used for sorting or ordering. For example, locale.strxfrm() is used to produce a sort key that is aware of locale specific sort conventions. A number of tools in Python accept key functions to control how elements are ordered or grouped. They include min() , max() , sorted() , list.sort() , heapq.merge() , heapq.nsmallest() , heapq.nlargest() , and itertools.groupby() . There are several ways to create a key function. For example. the str.casefold() method can serve as a key function for case insensitive sorts. Alternatively, a key function can be built from a lambda expression such as lambda r: (r[0], r[2]) . Also, operator.attrgetter() , operator.itemgetter() , and operator.methodcaller() are three key function constructors. See the Sorting HOW TO for examples of how to create and use key functions. keyword argument ¶ See argument . lambda ¶ An anonymous inline function consisting of a single expression which is evaluated when the function is called. The syntax to create a lambda function is lambda [parameters]: expression LBYL ¶ Look before you leap. This coding style explicitly tests for pre-conditions before making calls or lookups. This style contrasts with the EAFP approach and is characterized by the presence of many if statements. In a multi-threaded environment, the LBYL approach can risk introducing a race condition between “the looking” and “the leaping”. For example, the code, if key in mapping: return mapping[key] can fail if another thread removes key from mapping after the test, but before the lookup. This issue can be solved with locks or by using the EAFP approach. See also thread-safe . lexical analyzer ¶ Formal name for the tokenizer ; see token . list ¶ A built-in Python sequence . Despite its name it is more akin to an array in other languages than to a linked list since access to elements is O (1). list comprehension ¶ A compact way to process all or part of the elements in a sequence and return a list with the results. result = ['{:#04x}'.format(x) for x in range(256) if x % 2 == 0] generates a list of strings containing even hex numbers (0x..) in the range from 0 to 255. The if clause is optional. If omitted, all elements in range(256) are processed. lock ¶ A synchronization primitive that allows only one thread at a time to access a shared resource. A thread must acquire a lock before accessing the protected resource and release it afterward. If a thread attempts to acquire a lock that is already held by another thread, it will block until the lock becomes available. Python’s threading module provides Lock (a basic lock) and RLock (a reentrant lock). Locks are used to prevent race conditions and ensure thread-safe access to shared data. Alternative design patterns to locks exist such as queues, producer/consumer patterns, and thread-local state. See also deadlock , and reentrant . loader ¶ An object that loads a module. It must define the exec_module() and create_module() methods to implement the Loader interface. A loader is typically returned by a finder . See also: Finders and loaders importlib.abc.Loader PEP 302 locale encoding ¶ On Unix, it is the encoding of the LC_CTYPE locale. It can be set with locale.setlocale(locale.LC_CTYPE, new_locale) . On Windows, it is the ANSI code page (ex: "cp1252" ). On Android and VxWorks, Python uses "utf-8" as the locale encoding. locale.getencoding() can be used to get the locale encoding. See also the filesystem encoding and error handler . magic method ¶ An informal synonym for special method . mapping ¶ A container object that supports arbitrary key lookups and implements the methods specified in the collections.abc.Mapping or collections.abc.MutableMapping abstract base classes . Examples include dict , collections.defaultdict , collections.OrderedDict and collections.Counter . meta path finder ¶ A finder returned by a search of sys.meta_path . Meta path finders are related to, but different from path entry finders . See importlib.abc.MetaPathFinder for the methods that meta path finders implement. metaclass ¶ The class of a class. Class definitions create a class name, a class dictionary, and a list of base classes. The metaclass is responsible for taking those three arguments and creating the class. Most object oriented programming languages provide a default implementation. What makes Python special is that it is possible to create custom metaclasses. Most users never need this tool, but when the need arises, metaclasses can provide powerful, elegant solutions. They have been used for logging attribute access, adding thread-safety, tracking object creation, implementing singletons, and many other tasks. More information can be found in Metaclasses . method ¶ A function which is defined inside a class body. If called as an attribute of an instance of that class, the method will get the instance object as its first argument (which is usually called self ). See function and nested scope . method resolution order ¶ Method Resolution Order is the order in which base classes are searched for a member during lookup. See The Python 2.3 Method Resolution Order for details of the algorithm used by the Python interpreter since the 2.3 release. module ¶ An object that serves as an organizational unit of Python code. Modules have a namespace containing arbitrary Python objects. Modules are loaded into Python by the process of importing . See also package . module spec ¶ A namespace containing the import-related information used to load a module. An instance of importlib.machinery.ModuleSpec . See also Module specs . MRO ¶ See method resolution order . mutable ¶ An object with state that is allowed to change during the course of the program. In multi-threaded programs, mutable objects that are shared between threads require careful synchronization to avoid race conditions . See also immutable , thread-safe , and concurrent modification . named tuple ¶ The term “named tuple” applies to any type or class that inherits from tuple and whose indexable elements are also accessible using named attributes. The type or class may have other features as well. Several built-in types are named tuples, including the values returned by time.localtime() and os.stat() . Another example is sys.float_info : >>> sys . float_info [ 1 ] # indexed access 1024 >>> sys . float_info . max_exp # named field access 1024 >>> isinstance ( sys . float_info , tuple ) # kind of tuple True Some named tuples are built-in types (such as the above examples). Alternatively, a named tuple can be created from a regular class definition that inherits from tuple and that defines named fields. Such a class can be written by hand, or it can be created by inheriting typing.NamedTuple , or with the factory function collections.namedtuple() . The latter techniques also add some extra methods that may not be found in hand-written or built-in named tuples. namespace ¶ The place where a variable is stored. Namespaces are implemented as dictionaries. There are the local, global and built-in namespaces as well as nested namespaces in objects (in methods). Namespaces support modularity by preventing naming conflicts. For instance, the functions builtins.open and os.open() are distinguished by their namespaces. Namespaces also aid readability and maintainability by making it clear which module implements a function. For instance, writing random.seed() or itertools.islice() makes it clear that those functions are implemented by the random and itertools modules, respectively. namespace package ¶ A package which serves only as a container for subpackages. Namespace packages may have no physical representation, and specifically are not like a regular package because they have no __init__.py file. Namespace packages allow several individually installable packages to have a common parent package. Otherwise, it is recommended to use a regular package . For more information, see PEP 420 and Namespace packages . See also module . native code ¶ Code that is compiled to machine instructions and runs directly on the processor, as opposed to code that is interpreted or runs in a virtual machine. In the context of Python, native code typically refers to C, C++, Rust or Fortran code in extension modules that can be called from Python. See also extension module . nested scope ¶ The ability to refer to a variable in an enclosing definition. For instance, a function defined inside another function can refer to variables in the outer function. Note that nested scopes by default work only for reference and not for assignment. Local variables both read and write in the innermost scope. Likewise, global variables read and write to the global namespace. The nonlocal allows writing to outer scopes. new-style class ¶ Old name for the flavor of classes now used for all class objects. In earlier Python versions, only new-style classes could use Python’s newer, versatile features like __slots__ , descriptors, properties, __getattribute__() , class methods, and static methods. non-deterministic ¶ Behavior where the outcome of a program can vary between executions with the same inputs. In multi-threaded programs, non-deterministic behavior often results from race conditions where the relative timing or interleaving of threads affects the result. Proper synchronization using locks and other synchronization primitives helps ensure deterministic behavior. object ¶ Any data with state (attributes or value) and defined behavior (methods). Also the ultimate base class of any new-style class . optimized scope ¶ A scope where target local variable names are reliably known to the compiler when the code is compiled, allowing optimization of read and write access to these names. The local namespaces for functions, generators, coroutines, comprehensions, and generator expressions are optimized in this fashion. Note: most interpreter optimizations are applied to all scopes, only those relying on a known set of local and nonlocal variable names are restricted to optimized scopes. optional module ¶ An extension module that is part of the standard library , but may be absent in some builds of CPython , usually due to missing third-party libraries or because the module is not available for a given platform. See Requirements for optional modules for a list of optional modules that require third-party libraries. package ¶ A Python module which can contain submodules or recursively, subpackages. Technically, a package is a Python module with a __path__ attribute. See also regular package and namespace package . parallelism ¶ Executing multiple operations at the same time (e.g. on multiple CPU cores). In Python builds with the global interpreter lock (GIL) , only one thread runs Python bytecode at a time, so taking advantage of multiple CPU cores typically involves multiple processes (e.g. multiprocessing ) or native extensions that release the GIL. In free-threaded Python, multiple Python threads can run Python code simultaneously on different cores. parameter ¶ A named entity in a function (or method) definition that specifies an argument (or in some cases, arguments) that the function can accept. There are five kinds of parameter: positional-or-keyword : specifies an argument that can be passed either positionally or as a keyword argument . This is the default kind of parameter, for example foo and bar in the following: def func ( foo , bar = None ): ... positional-only : specifies an argument that can be supplied only by position. Positional-only parameters can be defined by including a / character in the parameter list of the function definition after them, for example posonly1 and posonly2 in the following: def func ( posonly1 , posonly2 , / , positional_or_keyword ): ... keyword-only : specifies an argument that can be supplied only by keyword. Keyword-only parameters can be defined by including a single var-positional parameter or bare * in the parameter list of the function definition before them, for example kw_only1 and kw_only2 in the following: def func ( arg , * , kw_only1 , kw_only2 ): ... var-positional : specifies that an arbitrary sequence of positional arguments can be provided (in addition to any positional arguments already accepted by other parameters). Such a parameter can be defined by prepending the parameter name with * , for example args in the following: def func ( * args , ** kwargs ): ... var-keyword : specifies that arbitrarily many keyword arguments can be provided (in addition to any keyword arguments already accepted by other parameters). Such a parameter can be defined by prepending the parameter name with ** , for example kwargs in the example above. Parameters can specify both optional and required arguments, as well as default values for some optional arguments. See also the argument glossary entry, the FAQ question on the difference between arguments and parameters , the inspect.Parameter class, the Function definitions section, and PEP 362 . path entry ¶ A single location on the import path which the path based finder consults to find modules for importing. path entry finder ¶ A finder returned by a callable on sys.path_hooks (i.e. a path entry hook ) which knows how to locate modules given a path entry . See importlib.abc.PathEntryFinder for the methods that path entry finders implement. path entry hook ¶ A callable on the sys.path_hooks list which returns a path entry finder if it knows how to find modules on a specific path entry . path based finder ¶ One of the default meta path finders which searches an import path for modules. path-like object ¶ An object representing a file system path. A path-like object is either a str or bytes object representing a path, or an object implementing the os.PathLike protocol. An object that supports the os.PathLike protocol can be converted to a str or bytes file system path by calling the os.fspath() function; os.fsdecode() and os.fsencode() can be used to guarantee a str or bytes result instead, respectively. Introduced by PEP 519 . PEP ¶ Python Enhancement Proposal. A PEP is a design document providing information to the Python community, or describing a new feature for Python or its processes or environment. PEPs should provide a concise technical specification and a rationale for proposed features. PEPs are intended to be the primary mechanisms for proposing major new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Python. The PEP author is responsible for building consensus within the community and documenting dissenting opinions. See PEP 1 . portion ¶ A set of files in a single directory (possibly stored in a zip file) that contribute to a namespace package, as defined in PEP 420 . positional argument ¶ See argument . provisional API ¶ A provisional API is one which has been deliberately excluded from the standard library’s backwards compatibility guarantees. While major changes to such interfaces are not expected, as long as they are marked provisional, backwards incompatible changes (up to and including removal of the interface) may occur if deemed necessary by core developers. Such changes will not be made | 2026-01-13T08:48:42 |
https://docs.suprsend.com/docs/ms-teams-template#design-template | Microsoft teams Template - 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 Design Template Channel Editors Email Template In-App Inbox Template SMS Template Whatsapp Template Android Push Template iOS Push Template Web Push Template Slack Template Microsoft teams Template Testing the Template Handlebars Helpers Internationalization 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 Channel Editors Microsoft teams Template Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Channel Editors Microsoft teams Template OpenAI Open in ChatGPT How to design simple MS Teams template using markdown editor or use JSONNET editor to replicate Microsoft’s adaptive card design. OpenAI Open in ChatGPT Design Template You can design a simple text template with our default markdown editor. For advanced formatting and interactive options like buttons, images, and avatars, you can use Microsoft’s adaptive card design in JSONNET editor. Please note that the variable format for both editors will be different. We’ll cover more about it in the next sections. Design simple text template using Markdown editor You can send simple text templates using the markdown editor in teams. Variables has to be added in handlebars format. Supported markdown syntax in Teams text messages: Format Syntax Headings # Heading level 1 . Refer all heading formats here line break end a line with two or more spaces, and then type return ( only 1 continuous line break is supported ) Bold **bold text** or __bold text__ Italic _italic text_ or *italic text* Bold Italic ***bold italic text*** or ___bold italic text___ >Blockquotes > block quote text Lists (1) First item (2) Second item Refer more lists format here code At the command prompt, type code . Links [Duck Duck Go](https://duckduckgo.com) Adding dynamic data in markdown editor We use handlebarsjs as the template variable language in the markdown editor. You can learn about handlebarsjs here. If you are new to templates, we would recommend reading the templates documentation first to understand the basics of templating with SuprSend. To add dynamic data, first add the variable data from your event and workflow request in the Mock data . Enter the variables in JSON format as shown in the screenshot below. This JSON should be the same as passed in your workflow or event request (it is a part of the data field for workflow and properties field for event). Now, you can use your added sample by adding variables in the template. Type {{ and you’ll start getting auto-suggestions of the variables added in your sample data below the text field. You can select the variable from the dropdown or directly type it in. As a general rule, all the variables have to be entered within double curly brackets: {{variable_name}} . For URLs and links, we recommend using triple curly braces {{{url}}} .This is to avoid escaping html entities in handlebars. You can also write transformations like date-time formatting, if-else statement inside your templates using handlebar helpers . Design adaptive card template using JSONNET editor You can switch to JSONNET editor for advanced formatting and interactive options like buttons, images, and avatars. Microsoft provides support for adaptive card design to design such templates using a drag-and-drop editor. You can design your template in the adaptive card designer and copy the JSON payload from your designer into the Teams JSONNET editor. We have also created some sample templates for a quick start. You can choose one of the samples from the right side options on top of the editor to start editing. We have used some mock data in our examples. Copy-paste the mock data values in the global Mock Data button to see the preview. Please note that the variable format ${variable} used in adaptive card is not supported in the JSONNET editor. You’ll have to add the variable in JSONNET format as data.variable Adding dynamic data in JSONNET editor To add dynamic data, first add the variable data from your event and workflow request in the Mock data . Enter the variables in `JSON` format as shown in the screenshot below. This JSON should be the same as passed in your workflow or event request (it is a part of the `data` field for workflow and `properties` field for event). Once the variables are declared, you can add them in the template as data.<variable_name> . Note that you will be able to enter a variable name even when you have not declared it inside the ‘Mock data’ button. However, the preview will not load without declaring the variables in Mock Data . Hence it’s advised to always declare variables before loading the preview of the template. Below are some examples of how to enter variables in the JSONNET editor. We’ll use the sample shown in the screenshot above as a reference point. Add nested variable To enter a nested variable, enter in the format data.var1.var2.var3 . Eg. to refer to city in the example above, you need to enter data.location.city Add Variable with space and special characters in variable name If you have any space in the variable name, enclose it in square bracket data.event['first name'] or data[$brand].brand_name Add Single array element To refer to an array element, enter in format data.var[*index*].var2}} . Eg. to refer to product_name of the first element of the array array , enter data.array[0].product_name Add list of array items Enter in the below format to add a dynamic list of items. In the above example, variable array has a list of product items, with product_name , and product_price as array properties. Below is an example code to fetch array items in a text field list: JSONNET Copy Ask AI { "$schema" : "http://adaptivecards.io/schemas/adaptive-card.json" , "body" : [ { "text" : product.name + " at " + product.price , "type" : "TextBlock" , "wrap" : true } for product in data.products ], "type" : "AdaptiveCard" , "version" : "1.6" } You’ll need to add mock data for the variables added in your JSONNET template to view the parsed JSON template. JSON template will throw an error in case of missing mock data for a variable Preview message Click on the Load Preview button to load the message preview. You will be able to see if your template is rendering properly with the sample mock data by loading the preview of your draft version. Make sure to see the preview before publishing the template to check if the parsed JSON is valid or not. Publish the template Once finalized, you can publish the template by clicking on Publish template button on the draft version. Your template is now ready to be triggered. At the time of sending communication, if there is a variable present in the template whose value is not rendered due to mismatch or missing, SuprSend will simply discard the template and not send that particular notification to your user. Please note that the rest of the templates will still be sent. Eg. if there is an error in rendering Teams template, but email template is successfully rendered, Teams notification will not be triggered, but email notification will be triggered by SuprSend. Was this page helpful? Yes No Suggest edits Raise issue Previous Testing the Template How to send a test notification from the template editor to your device for actual message preview. Next ⌘ I x github linkedin youtube Powered by On this page Design Template Design simple text template using Markdown editor Adding dynamic data in markdown editor Design adaptive card template using JSONNET editor Adding dynamic data in JSONNET editor Preview message Publish the template | 2026-01-13T08:48:42 |
http://www.stripe.com/ | Chat with Stripe sales Stripe | Financial Infrastructure to Grow Your Revenue Stripe logo Products Solutions Developers Resources Pricing Dashboard Sign in Sign in Contact sales Open mobile navigation Stripe logo Back Close mobile navigation Products Solutions Developers Resources Pricing Sign in Global payments Payments Payments Online payments Payment Links No-code payments Checkout Prebuilt payment form Elements Flexible UI components Terminal Terminal In-person payments Radar Radar Fraud prevention Authorization Boost Authorization Boost Acceptance optimizations Money Management Connect Connect Payments for platforms Financial Accounts Financial Accounts Manage business finances Issuing Issuing Physical and virtual cards Payouts Global Payouts Send money to third parties Capital Capital for platforms Customer financing Revenue and Finance Automation Billing Billing Subscription management Usage-based Metered billing Invoicing One-time or recurring Tax Tax Sales tax & VAT automation Revenue Recognition Revenue Recognition Accounting automation Stripe Sigma Stripe Sigma Custom reports Data Pipeline Data sync More Payment methods Access to 100+ globally Link Accelerated checkout Financial Connections Linked financial account data Identity Online identity verification Atlas Startup incorporation By stage Enterprises Startups By use case Agentic commerce Crypto Ecommerce Embedded finance Finance automation Global businesses In-app payments Marketplaces Platforms SaaS By industry AI companies Creator economy Hospitality, travel, and leisure Insurance Media and entertainment Nonprofits Retail Ecosystem Stripe App Marketplace Partners Documentation Resources API reference Libraries and SDKs App integrations Guides Accept online payments Implement a prebuilt checkout Build a platform or marketplace API status Developer blog Support center Managed support plans Professional services Contact sales Blog Customer stories Guides Sessions conference Jobs Newsroom Stripe Press Become a partner Start now Contact sales Global payments Payments Payments Online payments Payment Links No-code payments Checkout Prebuilt payment form Elements Flexible UI components Terminal Terminal In-person payments Radar Radar Fraud prevention Authorization Authorization Boost Acceptance optimizations Money Management Connect Connect Payments for platforms Financial Accounts Financial Accounts Manage business finances Issuing Issuing Physical and virtual cards Payouts Global Payouts Send money to third parties Capital Capital Business financing Revenue and Finance Automation Billing Billing Subscription management Usage-based Metered billing Invoicing One-time or recurring Tax Tax Sales tax & VAT automation Revenue Recognition Revenue Recognition Accounting automation Stripe Sigma Stripe Sigma Custom reports Data Pipeline Data sync More Payment methods Access to 100+ globally Link Accelerated checkout Financial Connections Linked financial account data Identity Online identity verification Atlas Startup incorporation Climate Carbon removal By stage Enterprises Startups By use case Agentic commerce Crypto Ecommerce Embedded finance Finance automation Global businesses In-app payments Marketplaces Platforms SaaS By industry AI companies Creator economy Hospitality, travel, and leisure Insurance Media and entertainment Nonprofits Retail Ecosystem Stripe App Marketplace Partners Documentation Start integrating Stripe’s products and tools Resources API reference Libraries and SDKs App integrations Code samples Stripe Apps Guides Accept online payments Implement a prebuilt checkout Set up in-person payments Build a platform or marketplace Manage subscriptions Offer usage-based billing API status Developer blog Support center Managed support plans Professional services Contact sales Blog Customer stories Guides Sessions conference Jobs Newsroom Stripe Press Become a partner Sessions 2026 · Early-bird registration now open Financial infrastructure to grow your revenue Financial infrastructure to grow your revenue Financial infrastructure to grow your revenue Join the millions of companies that use Stripe to accept payments online and in person, embed financial services, power custom revenue models, and build a more profitable business. Start now Contact sales Start now Contact sales Rocket Rides Search Today Net volume $3,528,198.72 2:00 PM Yesterday $2,931,556.34 12:00 AM Now, 2:00 PM 11:59 PM USD Balance $553,257.51 Available to pay out View Payouts $102,633.07 Expected today View Net volume from sales +32.8% $39,274.29 $29,573.54 Apr 20 Today Updated today 7:50 AM New customers +32.1% 37 28 Apr 20 Today Updated today 7:50 AM Invoices Paid $25,000.00 Open $20,000.00 Past due $1,000.00 Updated today 7:50 AM Abstraction Magazine $19 per month Or pay with card Email Card Information Number MM / YY CVC Country or region United States ZIP Pay Cancel Chase Freedom (•••• 1234) 27 Fredrick Ave Brothers OR Billing John Appleseed 27 Fredrick Ave Brothers, OR 97712 United States Contact j.appleseed@example.com +1 (458) 555-2863 Pay total $65.00 OpenAI logo Amazon logo Google logo Anthropic logo Marriott logo Shopify logo Airbnb logo URBN logo Mousedown/⌘ FF/Rewind Right/left Stretch Up/down Amplitude -/+ Zoom P Pause/play 1 Red on/off 2 Blue on/off 3 Yellow on/off 4 Purple on/off Modular solutions A fully integrated suite of financial and payments products Reduce costs, grow revenue, and run your business more efficiently on a fully integrated, AI-powered platform. Use Stripe to handle all of your payments-related needs, manage revenue operations, and launch (or invent) new business models. Atlas Billing Capital Checkout Climate Connect Elements Identity Invoicing Issuing Payments Radar Sigma Tax Terminal Treasury Payments Tax Radar Terminal Wood Chair 001 $149 €135.00 ¥199.00 €135.00 $149 Pay $149 €135.00 zahlen 支付 ¥199.00 Betaal €135.00 Pay $149 Billing Invoicing RevRec Sigma Quantum Abstraction Typographic Quantum Products Pricing Contact Standard Up to 5 users $49 /month Subscribe This includes: 12 months historical data 4 hr data refresh 500+ third party integrations Professional Popular! Up to 25 users $149 /month Subscribe This includes: 24 months historical data 1 hr data refresh 1,000+ third party integrations Simple reporting Enterprise Unlimited users $299 /month Subscribe This includes: Unlimited historical data 15 min data refresh 2,000+ third party integrations Advanced reporting Priority support Basic Digital access $9 /month Subscribe This includes: Unlimited access to web content Exclusive subscriber content Premium Popular! Digital and print access $19 /month Subscribe This includes: Unlimited access to web content Monthly print issues Exclusive subscriber content Web 50-499 users $99 /month Subscribe This includes: Up to 3 fonts 50k requests 5 domains Unlimited seats Connect Payouts Terminal Elements #9125 Hanako Yamada Processing <div class= | 2026-01-13T08:48:42 |
https://open.forem.com/t/beginners#promotional-rules | Beginners - 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 Beginners Follow Hide "A journey of a thousand miles begins with a single step." -Chinese Proverb Create Post submission guidelines UPDATED AUGUST 2, 2019 This tag is dedicated to beginners to programming, development, networking, or to a particular language. Everything should be geared towards that! For Questions... Consider using this tag along with #help, if... You are new to a language, or to programming in general, You want an explanation with NO prerequisite knowledge required. You want insight from more experienced developers. Please do not use this tag if you are merely new to a tool, library, or framework. See also, #explainlikeimfive For Articles... Posts should be specifically geared towards true beginners (experience level 0-2 out of 10). Posts should require NO prerequisite knowledge, except perhaps general (language-agnostic) essentials of programming. Posts should NOT merely be for beginners to a tool, library, or framework. If your article does not meet these qualifications, please select a different tag. Promotional Rules Posts should NOT primarily promote an external work. This is what Listings is for. Otherwise accepable posts MAY include a brief (1-2 sentence) plug for another resource at the bottom. Resource lists ARE acceptable if they follow these rules: Include at least 3 distinct authors/creators. Clearly indicate which resources are FREE, which require PII, and which cost money. Do not use personal affiliate links to monetize. Indicate at the top that the article contains promotional links. about #beginners If you're writing for this tag, we recommend you read this article . If you're asking a question, read this article . Older #beginners posts 1 2 3 4 5 6 7 8 9 … 75 … 3379 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu digital marketing Junaid Rana Junaid Rana Junaid Rana Follow Jan 9 digital marketing # ai # programming # beginners # productivity Comments Add Comment 5 min read How to Build a website in 2026: Complete Beginner’s Guide (The Smartest Way to Launch Online This Year) Yogendra Prajapati Yogendra Prajapati Yogendra Prajapati Follow Jan 9 How to Build a website in 2026: Complete Beginner’s Guide (The Smartest Way to Launch Online This Year) # webdev # beginners # tools # business Comments Add Comment 8 min read What I Wish I Knew Before My First LED Strip Install: Light Diffusion + Power Planning emmma emmma emmma Follow Jan 6 What I Wish I Knew Before My First LED Strip Install: Light Diffusion + Power Planning # beginners # design # hardware Comments Add Comment 3 min read Science behind Mountain Formation Gustavo Woltmann Gustavo Woltmann Gustavo Woltmann Follow Jan 4 Science behind Mountain Formation # beginners # learning # science Comments Add Comment 5 min read My Journey: Technology, Knowledge, and Building Meaningful Platforms ARVIND GUPTA ARVIND GUPTA ARVIND GUPTA Follow Dec 22 '25 My Journey: Technology, Knowledge, and Building Meaningful Platforms # technology # software # softwaredevelopment # beginners Comments Add Comment 2 min read Abrir Propriedades do Sistema via CMD (Windows) Carlos Eduardo De Souza Lemos Carlos Eduardo De Souza Lemos Carlos Eduardo De Souza Lemos Follow Dec 22 '25 Abrir Propriedades do Sistema via CMD (Windows) # beginners # learning # productivity Comments Add Comment 2 min read The Art of Mastering Spoken English: A Complete Journey from Silence to Eloquence Abdulla A Abdulla A Abdulla A Follow Dec 23 '25 The Art of Mastering Spoken English: A Complete Journey from Silence to Eloquence # beginners # learning # motivation 1 reaction Comments Add Comment 7 min read 🌿 5 Simple Habits to Improve Your Daily Life Dharmikk Baria Dharmikk Baria Dharmikk Baria Follow Dec 23 '25 🌿 5 Simple Habits to Improve Your Daily Life # watercooler # beginners # motivation Comments Add Comment 1 min read Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story Rajguru Yadav Rajguru Yadav Rajguru Yadav Follow Dec 27 '25 Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story # discuss # programming # ai # beginners 10 reactions Comments Add Comment 3 min read My North Star as an AI Founder (And Why I’m Not Changing It) Jaideep Parashar Jaideep Parashar Jaideep Parashar Follow Dec 18 '25 My North Star as an AI Founder (And Why I’m Not Changing It) # webdev # ai # beginners # productivity 15 reactions Comments 3 comments 3 min read Why is Displacement a straight line from the starting point to the ending point? Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 Why is Displacement a straight line from the starting point to the ending point? # beginners # learning # science Comments Add Comment 2 min read Scalar vs Vector Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 Scalar vs Vector # beginners # learning # science Comments Add Comment 2 min read What Is Displacement? Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 What Is Displacement? # beginners # learning # science Comments Add Comment 2 min read Understanding the FTSE AIM 100: A Look at the UK’s Dynamic Growth Market Isabel Rayn Isabel Rayn Isabel Rayn Follow Dec 11 '25 Understanding the FTSE AIM 100: A Look at the UK’s Dynamic Growth Market # watercooler # beginners # learning Comments Add Comment 4 min read 4.4 ऋग्वैदिक काल Anil Anil Anil Follow Dec 5 '25 4.4 ऋग्वैदिक काल # beginners # education # learning Comments Add Comment 1 min read 🚀 How I Got 25,000+ Views in 2 Days on a YouTube Short Menula De Silva Menula De Silva Menula De Silva Follow Dec 4 '25 🚀 How I Got 25,000+ Views in 2 Days on a YouTube Short # socialmedia # webdev # productivity # beginners 1 reaction Comments Add Comment 3 min read Starting Over in 2026? Here’s How to Create a Vision Board That Supports a Fresh New Beginning Aparnaa Jadhav Aparnaa Jadhav Aparnaa Jadhav Follow Dec 4 '25 Starting Over in 2026? Here’s How to Create a Vision Board That Supports a Fresh New Beginning # beginners # motivation # productivity Comments Add Comment 4 min read Best Courses to Learn AI for 2026 Hameed Ansari Hameed Ansari Hameed Ansari Follow Dec 8 '25 Best Courses to Learn AI for 2026 # ai # programming # productivity # beginners 5 reactions Comments Add Comment 1 min read All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark Amelia Hartley Amelia Hartley Amelia Hartley Follow Dec 4 '25 All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark # beginners # learning Comments Add Comment 4 min read How to Search Non-Patent Literature for Prior Art Alisha Raza Alisha Raza Alisha Raza Follow for PatentScanAI Dec 1 '25 How to Search Non-Patent Literature for Prior Art # beginners # learning # productivity Comments Add Comment 7 min read Understanding the FTSE AIM 100 Index and the Growth Potential of Its Companies Bella Stewart Bella Stewart Bella Stewart Follow Dec 1 '25 Understanding the FTSE AIM 100 Index and the Growth Potential of Its Companies # beginners # learning Comments Add Comment 3 min read Running Without a Plan and Learning Who I Am Miles Hensley Miles Hensley Miles Hensley Follow Nov 29 '25 Running Without a Plan and Learning Who I Am # watercooler # beginners # motivation Comments Add Comment 11 min read A Beginner’s Guide to Power Yoga for Weight Loss and Strength bhaktimeshakti bhaktimeshakti bhaktimeshakti Follow Nov 30 '25 A Beginner’s Guide to Power Yoga for Weight Loss and Strength # watercooler # motivation # learning # beginners Comments Add Comment 6 min read Beginner’s Guide to IT Support Ticketing Systems Amit khan Amit khan Amit khan Follow Nov 27 '25 Beginner’s Guide to IT Support Ticketing Systems # beginners # career # helpedesk # productivity Comments 1 comment 3 min read ## ⏳ From Dot-Com Bubble to Digital Hype: Learning from the Past Jean Klebert de A Modesto Jean Klebert de A Modesto Jean Klebert de A Modesto Follow Nov 27 '25 ## ⏳ From Dot-Com Bubble to Digital Hype: Learning from the Past # discuss # productivity # career # beginners 3 reactions Comments Add Comment 2 min read loading... trending guides/resources Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story Abrir Propriedades do Sistema via CMD (Windows) How to Organize Your Notes Using Printable Lined Paper — A Simple Productivity Hack How to Find Patent Prior Art in Research Papers Understanding the All Ordinaries Index: Structure, Purpose, and Market Role Science behind Mountain Formation Understanding ASX 200 Futures and Their Role in Market Observation Understanding the Basics of Pay-Per-Click (PPC) Advertising A Beginner’s Guide to Power Yoga for Weight Loss and Strength All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark Decoding Startup Success: Understanding Burn Rate, Runway, and Churn Metrics Understanding the FTSE AIM 100 Index and the Growth Potential of Its Companies Creating a Physical Wired Network in Cisco Packet Tracer - My Experience | Israh Binoj Best Courses to Learn AI for 2026 Yelken Eğitiminde Hissetmenin Bilgiyi Geçtiği An: Teknenin Sizinle Konuştuğu O An Yelken Eğitiminde Sabır: Rüzgarın Öğrettiği En Değerli Ders How We Process Information Using The DIKW Model How to fix: “less than 1MB free space" Warning 📍Un Viaje Continuo: De Córdoba a Barcelona A Beginner’s Guide to Channel Attribution Modeling in 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 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:48:42 |
https://dev.to/szabgab/perl-weekly-603-generating-prejudice-j5p | Perl Weekly #603 - Generating prejudice - 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 Gabor Szabo Posted on Feb 13, 2023 • Originally published at perlweekly.com Perl Weekly #603 - Generating prejudice # perl # news # programming perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? Originally published at Perl Weekly 603 Hi there! I am sure most of you reading this newsletter have heard that "perl is unreadable" or "perl is a write only language", or maybe that "perl is dead". In many cases this comes from people who have never actually saw perl. You might have not named this phenomenon, but this is called prejudice. Prejudice is having (usually negative) opinion about an individual, a group of people, or a thing, with partial or no real knowledge about the subject. It's name is quite clear. It is having a judgement before (pre) having knowledge. One can see prejudice as a phenomenon that happens naturally, but it can also be manufactured and used for personal, economic, or political gains. We saw that happening in the last 25 years with Perl. I saw a number of very interesting, though painful cases. Prejudice against Perl clearly has way less personal consequences than other forms of prejudice, but maybe because of that it is easier to discuss it. In one case, a few years ago, someone explained to me that he writes both in Perl and in Python. When he writes in Perl he does not care about indentation or good programming practices as Perl works that way as well. Then he continued explaining that Perl is unreadable. He did not seem to realize the absurdity that the cause and effect relationship might not be of language->readability, but rather effort-to-write-clean-code->readability. I often hear people writing in Perl talking about the code being unmaintainable. It is a type of internalized prejudice when you could know otherwise, but because of the social pressure of viewing the negative aspects one will adopts, repeats, and thus strengthens the prejudice. "If even Perl developers say so then it must be true." Once, more than 10 years ago, when I was at FOSDEM I talked to someone at the pre-conference beer drinking party. She explained that at their company they would not consider hiring anyone who had ever written in Perl. - Clearly a very stupid idea as there are some brilliant Perl programmers. However, this is where prejudice leads to. It does not only hurt the Perl developers, it also hurts the people having the prejudice. How is prejudice manufactured? One key aspect of creating and then increasing this prejudice against Perl and even against people who wrote in Perl was the repetition of lies that are now accepted as "facts". Another aspect was that saying bad things about Perl seemed like a requirement to be accepted in the Python community. It certainly helped some people who moved from Perl to Python to "be forgiven". I remember when I first started to write in Python and go to Python events, there was a some pressure to distance myself from my "sinful past" writing Perl. So far I managed no to cave in and so I still receive such demands once in a while. How to fight prejudice? There are many articles about this topic, I am sure it will be interesting to read some of them. That's it for this weeks rant. In the meantime I continue running two instances of the Open Source Development Course . One in Hebrew for a mix of biologists and programmers. Some of whom are students and some with work experience. The other one is in English with extra focus on Perl. I hope that the participants in this course will soon start opening issues and sending Pull-Requests to various CPAN modules. Enjoy your week! -- Your editor: Gabor Szabo. Announcement RIP Prairie Nyx Just a few months ago I talked to her. She wanted to work at least till she is 70. Unfortunately that won't happen now. Articles Project Report "Google TensorFlow API Bindings for Perl" The project has been submitted for final review. The delivered deliverables are in the article as outlined by John Napiorkowski. Bug fix and maintenance release 1.62 of perl-workflow I can only applaud the extra mile Jonas goes publishing about his releases on DEV.to too. The Perl Toolchain Summit 2023 has a COVID Policy The single most important step in protecting others is to not show up sick. First release of SPVM::File::Copy and SPVM::FindBin It is really nice that Yuki sticks to his project(s) so much and even keeps blogging about them. Where are the followers? Find expiring SSL certs using curl, Go and Perl. Just like domain name registrations, SSL certificates need to be renewed regularly, otherwise they expire. This means you now have one more thing to monitor. Let's look at ways to do this in Perl, curl and Go. The article also gives a quick introduction to a hosted Mojolicious app that Olaf wrote to make this even easier. CPAN I am not sure why post all of these now, but maybe Steven has just created the script to generate the annual reports. So here they are. List of new CPAN distributions in 2022 Number of new CPAN distributions this period: 789; Number of authors releasing new CPAN distributions this period: 252 List of new CPAN distributions in 2021 Number of new CPAN distributions this period: 876; Number of authors releasing new CPAN distributions this period: 269 List of new CPAN distributions in 2020 Number of new CPAN distributions this period: 1287; Number of authors releasing new CPAN distributions this period: 329 List of new CPAN distributions in 2019 Number of new CPAN distributions this period: 1179; Number of authors releasing new CPAN distributions this period: 352 List of new CPAN distributions in 2018 Number of new CPAN distributions this period: 1358; Number of authors releasing new CPAN distributions this period: 426 Perl This week in PSC (097) The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 204 Welcome to a new week with a couple of fun tasks "Monotonic Array" and "Reshape Matrix". If you are new to the weekly challenge then why not join us and have fun every week. For more information, please read the FAQ . RECAP - The Weekly Challenge - 203 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Special Quadruplets" and "Copy Directory" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Quadruple Copies Dry run with verbose mode is the best combination. Keep it up great work. Non-Authoritative Information Dave is fan of recursion and use it very intelligently. Cool contributions. Thanks. The Weekly Challenge 203 James is master of elegant Perl solution. You will fall in love with Perl again. Highly Recommended. PWC203 - Special Quadruplets No hard question for me this time, happy me. Thanks for your funny notes. PWC203 - Copy Directory Cool use of CPAN modules, I loved it. Thanks for sharing the knowledge. Perl Weekly Challenge 203: Special Quadruplets and Copy Directory (Functional Programming Approach) Laurent always spoil us with varieties of solutions. Keep it up great work and thanks for your contributions. Nested Loops Using good old loops did the trick this time. Clean solution, well done. Perl Weekly Challenge 203 One-liner wasn't appropriate this time, so we got to see the different side of Luis. Thanks for sharing. Quads and directory enquiries Practical discussion around the task makes it easy to follow the solution. Well done. The Weekly Challenge #203 Full credit goes to Robbie for the extra effort. Appreciate your contributions. Directing the Quadruplets Pure CPAN solution this time, smart move. Well done. Training OSDC Lesson 2 Notes from the 2nd meeting of the Open Source Developer Course for Perl programmers . Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . Perl Jobs by Perl Careers Adventure! Senior Perl roles in Malaysia, Dubai and Malta Clever folks know that if you’re lucky, you can earn a living and have an adventure at the same time. Enter our international client: online trading is their game and they’re looking for Perl people who have passion, drive, and an appreciation for new experiences. Senior Perl Developer with Cross-Trained Chops. UK Remote Perl Role The client is interested in anyone with experience building web apps in Perl, using one of the major Perl frameworks. If you’re a crack-hand with Catalyst, a Mojolicious master, or a distinguished Dancer, they want you. You’ll be deploying apps your work to AWS, so experience would be handy, and the company’s big on testing, so they’d like you to know your way around Test::More. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe. UK Remote Perl Role A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #755 - Does TIOBE help Perl? # perl # news # programming Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming 💎 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:48:42 |
https://dev.to/t/mentalhealth/page/3 | Mental Health 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 DEV Community Close Mental Health Follow Hide Mental health matters! Break the stigma. We can empower ourselves and each other to invest in our mental health. We can give support and care to ourselves and each other while we struggle. Let's talk about making our mental health priority. Create Post about #mentalhealth Posts should be related to mental health. This is a pretty wide category but some things that are included are: Managing mental health as a developer Living with mental illness and how it affects your work Ways to cope with mental health issues Avoiding burn out Tools, apps, and methods that help you with your mental health ...and more “Your mental health is a priority. Your happiness is an essential. Your self-care is a necessity.” Struggling? Help is out there. Click here to find a list of global mental health resources and hotlines. Older #mentalhealth 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 Why "Productivity" Won't Save You: How I Built My Way Out of a Rut ElevenApril ElevenApril ElevenApril Follow Dec 10 '25 Why "Productivity" Won't Save You: How I Built My Way Out of a Rut # devjournal # mentalhealth # productivity Comments Add Comment 3 min read Staying Sharp After 40 SGTSanjay SGTSanjay SGTSanjay Follow Dec 11 '25 Staying Sharp After 40 # career # learning # mentalhealth 1 reaction Comments Add Comment 3 min read Debugging the Mind's Legacy Code: A Cognitive Architect's Log Aleksei Sergeevich Aleksei Sergeevich Aleksei Sergeevich Follow Dec 10 '25 Debugging the Mind's Legacy Code: A Cognitive Architect's Log # mentalhealth # productivity # softwaredevelopment Comments Add Comment 2 min read Why I didn't build in public JohannKrugell JohannKrugell JohannKrugell Follow Dec 12 '25 Why I didn't build in public # discuss # motivation # mentalhealth # devjournal Comments Add Comment 1 min read Kelime Eda Deniz Sarsılmaz Eda Deniz Sarsılmaz Eda Deniz Sarsılmaz Follow Dec 9 '25 Kelime # discuss # mentalhealth # watercooler Comments Add Comment 1 min read Failing LeetCode Over and Over? Here's How to Stay Motivated Alex Hunter Alex Hunter Alex Hunter Follow Dec 12 '25 Failing LeetCode Over and Over? Here's How to Stay Motivated # beginnerguide # motivation # mentalhealth # learningstrategy Comments Add Comment 9 min read 🚀 How Media Misrepresents Mental Health — And Why It Matters in a Digital World NVelUp NVelUp NVelUp Follow Dec 8 '25 🚀 How Media Misrepresents Mental Health — And Why It Matters in a Digital World # mentalhealth Comments Add Comment 3 min read The Double-Edged Sword of "Flow State" in Game Dev ⚔️ crow crow crow Follow Dec 11 '25 The Double-Edged Sword of "Flow State" in Game Dev ⚔️ # productivity # mentalhealth # web3 # developers 1 reaction Comments 1 comment 3 min read How Dopamine Detox Made Me a Better Developer yusuf yonturk yusuf yonturk yusuf yonturk Follow Dec 26 '25 How Dopamine Detox Made Me a Better Developer # discuss # productivity # mentalhealth # devlife 2 reactions Comments 4 comments 4 min read How to Deal with LeetCode Anxiety and Interview Stress: A Mental Health Guide Alex Hunter Alex Hunter Alex Hunter Follow Dec 6 '25 How to Deal with LeetCode Anxiety and Interview Stress: A Mental Health Guide # mentalhealth # anxietymanagement # interviewstress # beginnerguide Comments Add Comment 8 min read The Invisible Bonds: Understanding Hatred’s Deep Roots DriftLens team DriftLens team DriftLens team Follow Dec 7 '25 The Invisible Bonds: Understanding Hatred’s Deep Roots # mentalhealth # emotion # productivity # career 1 reaction Comments Add Comment 3 min read 🧠 [Memory Leak] Why I Felt Stupid at 2 PM: Debugging My Brain's RAM Vital Access Vital Access Vital Access Follow Dec 1 '25 🧠 [Memory Leak] Why I Felt Stupid at 2 PM: Debugging My Brain's RAM # productivity # career # mentalhealth # softskills 2 reactions Comments Add Comment 5 min read Why Reflection Needs Structure: A Cognitive Model from Buddhism DriftLens team DriftLens team DriftLens team Follow Dec 2 '25 Why Reflection Needs Structure: A Cognitive Model from Buddhism # learning # mentalhealth # productivity Comments Add Comment 4 min read Surviving Cancer Doesn't Suck Abbey Perini Abbey Perini Abbey Perini Follow Jan 6 Surviving Cancer Doesn't Suck # watercooler # devjournal # mentalhealth # motivation 9 reactions Comments Add Comment 10 min read Why Psychological Safety Matters in Dev Workplaces Aarti Jangid Aarti Jangid Aarti Jangid Follow Dec 25 '25 Why Psychological Safety Matters in Dev Workplaces # management # career # productivity # mentalhealth 2 reactions Comments 2 comments 3 min read Understanding the Attention Economy: Why Your Focus Is the New Currency Martin Ghazaryan Martin Ghazaryan Martin Ghazaryan Follow Dec 1 '25 Understanding the Attention Economy: Why Your Focus Is the New Currency # learning # mentalhealth # productivity Comments Add Comment 4 min read The Reset Button That Wasn't: Why 2026 Demands a New Kind of Resolution Tombri Bowei Tombri Bowei Tombri Bowei Follow Dec 30 '25 The Reset Button That Wasn't: Why 2026 Demands a New Kind of Resolution # newyearchallenge # career # productivity # mentalhealth 7 reactions Comments 1 comment 3 min read When Sleep Became a Problem Nimesh Thakur Nimesh Thakur Nimesh Thakur Follow Dec 25 '25 When Sleep Became a Problem # discuss # mentalhealth # productivity # motivation 9 reactions Comments 1 comment 3 min read The Divine Algorithm: A Developer’s Confession crow crow crow Follow Nov 22 '25 The Divine Algorithm: A Developer’s Confession # watercooler # web3 # showdev # mentalhealth Comments Add Comment 3 min read Improving Developer Productivity Without Burning Out Your Team Practical engineering habits that actually scale SYFOX dev SYFOX dev SYFOX dev Follow Dec 25 '25 Improving Developer Productivity Without Burning Out Your Team Practical engineering habits that actually scale # management # productivity # devops # mentalhealth Comments Add Comment 2 min read Digital Sabbatical and Outernet (Bite-size Article) koshirok096 koshirok096 koshirok096 Follow Nov 21 '25 Digital Sabbatical and Outernet (Bite-size Article) # discuss # mentalhealth # productivity Comments Add Comment 3 min read Replacing Phone Addiction with Building a Real Project Vigneshwaralingam Vigneshwaralingam Vigneshwaralingam Follow Dec 25 '25 Replacing Phone Addiction with Building a Real Project # fullstack # productivity # motivation # mentalhealth 8 reactions Comments Add Comment 1 min read Why I Keep My Kids Away From Screens (Even Though I Work in Tech) Juan Rueda Juan Rueda Juan Rueda Follow Dec 23 '25 Why I Keep My Kids Away From Screens (Even Though I Work in Tech) # discuss # mentalhealth # watercooler 4 reactions Comments 1 comment 5 min read The Growing Crisis of Burnout Among Cybersecurity Professionals GuardingPearSoftware GuardingPearSoftware GuardingPearSoftware Follow Nov 24 '25 The Growing Crisis of Burnout Among Cybersecurity Professionals # career # cybersecurity # mentalhealth Comments Add Comment 5 min read The Afternoon I Found Comfort In A Small Conversation Milo Anders Milo Anders Milo Anders Follow Nov 19 '25 The Afternoon I Found Comfort In A Small Conversation # watercooler # devjournal # mentalhealth Comments Add Comment 8 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:48:42 |
https://fr.react.dev/ | React React v 18.3.1 Recherche ⌘ Ctrl K Apprendre Référence Communauté Blog React La bibliothèque pour des interfaces utilisateurs web et natives Apprenez React Référence de l’API Créez des interfaces utilisateurs à l’aide de composants React vous permet de construire des interfaces utilisateurs à partir de briques individuelles appelées composants. Créez vos propres composants tels que Thumbnail , LikeButton , et Video . Puis combinez-les pour produire des écrans, pages et applis entières. Video.js function Video ( { video } ) { return ( < div > < Thumbnail video = { video } /> < a href = { video . url } > < h3 > { video . title } </ h3 > < p > { video . description } </ p > </ a > < LikeButton video = { video } /> </ div > ) ; } Ma vidéo Description de la vidéo Que vous travailliez dans votre coin ou avec des milliers d’autres développeur·se·s, l’utilisation de React est la même. React est conçu pour vous permettre de combiner sans effort des composants produits par des acteurs distincts, qu’il s’agisse de personnes, d’équipes ou d’organisations entières. Écrivez des composants avec du code et des balises Les composants React sont des fonctions JavaScript. Envie d’afficher du contenu conditionnellement ? Utilisez un if . Un affichage de liste ? Essayez le map() des tableaux. Apprendre React, c’est apprendre à programmer. VideoList.js function VideoList ( { videos , emptyHeading } ) { const count = videos . length ; let heading = emptyHeading ; if ( count > 0 ) { const noun = count > 1 ? 'vidéos' : 'vidéo' ; heading = count + ' ' + noun ; } return ( < section > < h2 > { heading } </ h2 > { videos . map ( video => < Video key = { video . id } video = { video } /> ) } </ section > ) ; } 3 vidéos Première vidéo Description de la vidéo Deuxième vidéo Description de la vidéo Troisième vidéo Description de la vidéo Cette syntaxe de balises s’appelle JSX. C’est une extension de la syntaxe JavaScript, popularisée par React. Conserver votre balisage JSX près de votre logique de rendu facilite la création, la maintenance et le nettoyage de vos composants React. Ajoutez de l’interactivité partout où vous en avez besoin Les composants React reçoivent des données et renvoient ce qui devrait apparaître à l’écran. Vous pouvez leur passer de nouvelles données en réaction à des interactions, comme une saisie utilisateur dans un champ. React mettra alors à jour l’écran pour refléter les nouvelles données. SearchableVideoList.js import { useState } from 'react' ; function SearchableVideoList ( { videos } ) { const [ searchText , setSearchText ] = useState ( '' ) ; const foundVideos = filterVideos ( videos , searchText ) ; return ( < > < SearchInput value = { searchText } onChange = { newText => setSearchText ( newText ) } /> < VideoList videos = { foundVideos } emptyHeading = { `Aucun résultat pour « ${ searchText } »` } /> </ > ) ; } example.com / videos.html Vidéos React Une brève histoire de React Recherche 5 vidéos React: The Documentary L’histoire de l’origine de React Rethinking Best Practices Pete Hunt (2013) Introducing React Native Tom Occhino (2015) Introducing React Hooks Sophie Alpert et Dan Abramov (2018) Introducing Server Components Dan Abramov et Lauren Tan (2020) Vous n’avez pas besoin de construire toute votre page en React. Ajoutez React à une page HTML existante, et affichez des composants React interactifs où bon vous semble à l’intérieur. Ajoutez React à votre page Passez au full-stack avec un framework React est une bibliothèque. Il vous permet d’assembler des composants, mais n’est pas prescriptif en ce qui concerne le routage ou le chargement de données. Pour construire une appli entière avec React, nous vous conseillons un framework React full-stack tels que Next.js ou Remix . confs/[slug].js import { db } from './database.js' ; import { Suspense } from 'react' ; async function ConferencePage ( { slug } ) { const conf = await db . Confs . find ( { slug } ) ; return ( < ConferenceLayout conf = { conf } > < Suspense fallback = { < TalksLoading /> } > < Talks confId = { conf . id } /> </ Suspense > </ ConferenceLayout > ) ; } async function Talks ( { confId } ) { const talks = await db . Talks . findAll ( { confId } ) ; const videos = talks . map ( talk => talk . video ) ; return < SearchableVideoList videos = { videos } /> ; } example.com / confs/react-conf-2021 React Conf 2021 React Conf 2019 Recherche 19 vidéos React Conf Keynote React 18 L’équipe React React Conf React 18 for App Developers Shruti Kapoor React Conf Streaming Server Rendering with Suspense Shaundai Person React Conf The First React Working Group Aakansha Doshi React Conf React Developer Tooling Brian Vaughn React Conf React without memo Xuan Huang (黄玄) React Conf React Docs Keynote Rachel Nabors React Conf Things I Learnt from the New React Docs Debbie O'Brien React Conf Learning in the Browser Sarah Rainsberger React Conf The ROI of Designing with React Linton Ye React Conf Interactive Playgrounds with React Delba de Oliveira React Conf Re-introducing Relay Robert Balicki React Conf React Native Desktop Eric Rozell and Steven Moyes React Conf On-device Machine Learning for React Native Roman Rädle React Conf React 18 for External Store Libraries Daishi Kato React Conf Building Accessible Components with React 18 Diego Haz React Conf Accessible Japanese Form Components with React Tafu Nakazaki React Conf UI Tools for Artists Lyle Troxell React Conf Hydrogen + React 18 Helen Lin React est aussi une architecture. Les frameworks qui l’implémentent vous permettent de charger des données dans des composants asynchrones exécutés côté serveur ou même lors du build . Lisez des données depuis un fichier ou une base de données, et passez-les à vos composants interactifs. Démarrez avec un framework Tirez le meilleur de chaque plateforme Les gens adorent le web et les applis natives pour des raisons différentes. React vous permet de construire tant des applis web que des applis natives avec un même jeu de compétences. Il s’appuie sur les forces uniques de chaque plateforme pour que vos interfaces aient un comportement toujours naturel. example.com Restez fidèle au web Les gens s’attendent à ce que les pages des applis web se chargent rapidement. Coté serveur, React vous permet de commencer à streamer le HTML alors que vous chargez encore des données, en remplissant progressivement le contenu manquant avant même que JavaScript ne soit chargé. Côté client, React utilise des API web standard pour que votre UI reste réactive même en plein milieu d’un rendu. 6:50 AM Faites du vrai natif Les gens attendent un aspect et un comportement bien précis des applis natives. React Native et Expo vous permettent de construire des applis en React pour Android, iOS et plus encore. Elles ont un aspect et un comportement natifs parce que leurs UI sont véritablement natives. Ce n’est pas une web view : vos composants React affichent de véritables vues Android et iOS fournies par la plateforme. Avec React, vous pouvez faire du développement web et natif. Votre équipe peut déployer sur de multiples plateformes sans sacrifier l’expérience utilisateur. Votre organisation peut créer des ponts entre les silos des plateformes et monter des équipes capables de gérer leurs fonctionnalités de bout en bout. Construisez des applis natives Mettez à jour quand l’avenir est prêt React fait attention à ses évolutions. Chaque commit React est testé dans des contextes critiques à la mission de plus d’un milliard d’utilisateurs. Les plus de 100 000 composants React de Meta nous aident à valider chaque stratégie de migration. L’équipe React cherche en permanence à améliorer React. Certains sujets de recherche prennent des années à porter leurs fruits. React met la barre très haut pour infuser la recherche dans la production. Seules les approches aux bénéfices largement prouvés trouvent leur place dans React. Lisez davantage d’actualités React Lisez davantage d’actualités React React Compiler : beta et feuille de route 21 octobre 2024 La React Conf 2024 en bref 22 mai 2024 React 19 RC 25 avril 2024 React 19 RC : guide de migration 25 avril 2024 Lisez davantage d’actualités React Rejoignez des millions de devs React Vous n’êtes pas seul·e. Deux millions de devs du monde entier utilisent les docs React tous les mois. React est un choix qui fédère les personnes et les équipes. C’est pourquoi React est plus qu’une bibliothèque, une architecture, ou même un écosystème. React est une communauté. C’est un endroit où vous pouvez demander de l’aide, trouver de nouvelles opportunités, et vous faire de nouveaux amis. Vous rencontrerez des développeur·se·s et des designers, des débutants et des experts, des chercheurs et des artistes, des enseignants et des étudiants. Nos parcours sont peut-être très différents, mais React nous permet à tou·te·s de créer des interfaces utilisateurs ensemble. Bienvenue dans la communauté React Commencez Copyright © Meta Platforms, Inc no uwu plz uwu? Logo by @sawaratsuki1004 Apprendre React Démarrage rapide Installation Décrire l’UI Ajouter de l’interactivité Gérer l’état Échappatoires Référence de l’API API React API React DOM Communauté Code de conduite L’équipe Contributeurs aux docs Remerciements Plus Blog React Native Politique de confidentialité Mentions légales | 2026-01-13T08:48:42 |
https://open.forem.com/t/beginners#for-articles | Beginners - 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 Beginners Follow Hide "A journey of a thousand miles begins with a single step." -Chinese Proverb Create Post submission guidelines UPDATED AUGUST 2, 2019 This tag is dedicated to beginners to programming, development, networking, or to a particular language. Everything should be geared towards that! For Questions... Consider using this tag along with #help, if... You are new to a language, or to programming in general, You want an explanation with NO prerequisite knowledge required. You want insight from more experienced developers. Please do not use this tag if you are merely new to a tool, library, or framework. See also, #explainlikeimfive For Articles... Posts should be specifically geared towards true beginners (experience level 0-2 out of 10). Posts should require NO prerequisite knowledge, except perhaps general (language-agnostic) essentials of programming. Posts should NOT merely be for beginners to a tool, library, or framework. If your article does not meet these qualifications, please select a different tag. Promotional Rules Posts should NOT primarily promote an external work. This is what Listings is for. Otherwise accepable posts MAY include a brief (1-2 sentence) plug for another resource at the bottom. Resource lists ARE acceptable if they follow these rules: Include at least 3 distinct authors/creators. Clearly indicate which resources are FREE, which require PII, and which cost money. Do not use personal affiliate links to monetize. Indicate at the top that the article contains promotional links. about #beginners If you're writing for this tag, we recommend you read this article . If you're asking a question, read this article . Older #beginners posts 1 2 3 4 5 6 7 8 9 … 75 … 3379 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu digital marketing Junaid Rana Junaid Rana Junaid Rana Follow Jan 9 digital marketing # ai # programming # beginners # productivity Comments Add Comment 5 min read How to Build a website in 2026: Complete Beginner’s Guide (The Smartest Way to Launch Online This Year) Yogendra Prajapati Yogendra Prajapati Yogendra Prajapati Follow Jan 9 How to Build a website in 2026: Complete Beginner’s Guide (The Smartest Way to Launch Online This Year) # webdev # beginners # tools # business Comments Add Comment 8 min read What I Wish I Knew Before My First LED Strip Install: Light Diffusion + Power Planning emmma emmma emmma Follow Jan 6 What I Wish I Knew Before My First LED Strip Install: Light Diffusion + Power Planning # beginners # design # hardware Comments Add Comment 3 min read Science behind Mountain Formation Gustavo Woltmann Gustavo Woltmann Gustavo Woltmann Follow Jan 4 Science behind Mountain Formation # beginners # learning # science Comments Add Comment 5 min read My Journey: Technology, Knowledge, and Building Meaningful Platforms ARVIND GUPTA ARVIND GUPTA ARVIND GUPTA Follow Dec 22 '25 My Journey: Technology, Knowledge, and Building Meaningful Platforms # technology # software # softwaredevelopment # beginners Comments Add Comment 2 min read Abrir Propriedades do Sistema via CMD (Windows) Carlos Eduardo De Souza Lemos Carlos Eduardo De Souza Lemos Carlos Eduardo De Souza Lemos Follow Dec 22 '25 Abrir Propriedades do Sistema via CMD (Windows) # beginners # learning # productivity Comments Add Comment 2 min read The Art of Mastering Spoken English: A Complete Journey from Silence to Eloquence Abdulla A Abdulla A Abdulla A Follow Dec 23 '25 The Art of Mastering Spoken English: A Complete Journey from Silence to Eloquence # beginners # learning # motivation 1 reaction Comments Add Comment 7 min read 🌿 5 Simple Habits to Improve Your Daily Life Dharmikk Baria Dharmikk Baria Dharmikk Baria Follow Dec 23 '25 🌿 5 Simple Habits to Improve Your Daily Life # watercooler # beginners # motivation Comments Add Comment 1 min read Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story Rajguru Yadav Rajguru Yadav Rajguru Yadav Follow Dec 27 '25 Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story # discuss # programming # ai # beginners 10 reactions Comments Add Comment 3 min read My North Star as an AI Founder (And Why I’m Not Changing It) Jaideep Parashar Jaideep Parashar Jaideep Parashar Follow Dec 18 '25 My North Star as an AI Founder (And Why I’m Not Changing It) # webdev # ai # beginners # productivity 15 reactions Comments 3 comments 3 min read Why is Displacement a straight line from the starting point to the ending point? Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 Why is Displacement a straight line from the starting point to the ending point? # beginners # learning # science Comments Add Comment 2 min read Scalar vs Vector Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 Scalar vs Vector # beginners # learning # science Comments Add Comment 2 min read What Is Displacement? Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 What Is Displacement? # beginners # learning # science Comments Add Comment 2 min read Understanding the FTSE AIM 100: A Look at the UK’s Dynamic Growth Market Isabel Rayn Isabel Rayn Isabel Rayn Follow Dec 11 '25 Understanding the FTSE AIM 100: A Look at the UK’s Dynamic Growth Market # watercooler # beginners # learning Comments Add Comment 4 min read 4.4 ऋग्वैदिक काल Anil Anil Anil Follow Dec 5 '25 4.4 ऋग्वैदिक काल # beginners # education # learning Comments Add Comment 1 min read 🚀 How I Got 25,000+ Views in 2 Days on a YouTube Short Menula De Silva Menula De Silva Menula De Silva Follow Dec 4 '25 🚀 How I Got 25,000+ Views in 2 Days on a YouTube Short # socialmedia # webdev # productivity # beginners 1 reaction Comments Add Comment 3 min read Starting Over in 2026? Here’s How to Create a Vision Board That Supports a Fresh New Beginning Aparnaa Jadhav Aparnaa Jadhav Aparnaa Jadhav Follow Dec 4 '25 Starting Over in 2026? Here’s How to Create a Vision Board That Supports a Fresh New Beginning # beginners # motivation # productivity Comments Add Comment 4 min read Best Courses to Learn AI for 2026 Hameed Ansari Hameed Ansari Hameed Ansari Follow Dec 8 '25 Best Courses to Learn AI for 2026 # ai # programming # productivity # beginners 5 reactions Comments Add Comment 1 min read All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark Amelia Hartley Amelia Hartley Amelia Hartley Follow Dec 4 '25 All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark # beginners # learning Comments Add Comment 4 min read How to Search Non-Patent Literature for Prior Art Alisha Raza Alisha Raza Alisha Raza Follow for PatentScanAI Dec 1 '25 How to Search Non-Patent Literature for Prior Art # beginners # learning # productivity Comments Add Comment 7 min read Understanding the FTSE AIM 100 Index and the Growth Potential of Its Companies Bella Stewart Bella Stewart Bella Stewart Follow Dec 1 '25 Understanding the FTSE AIM 100 Index and the Growth Potential of Its Companies # beginners # learning Comments Add Comment 3 min read Running Without a Plan and Learning Who I Am Miles Hensley Miles Hensley Miles Hensley Follow Nov 29 '25 Running Without a Plan and Learning Who I Am # watercooler # beginners # motivation Comments Add Comment 11 min read A Beginner’s Guide to Power Yoga for Weight Loss and Strength bhaktimeshakti bhaktimeshakti bhaktimeshakti Follow Nov 30 '25 A Beginner’s Guide to Power Yoga for Weight Loss and Strength # watercooler # motivation # learning # beginners Comments Add Comment 6 min read Beginner’s Guide to IT Support Ticketing Systems Amit khan Amit khan Amit khan Follow Nov 27 '25 Beginner’s Guide to IT Support Ticketing Systems # beginners # career # helpedesk # productivity Comments 1 comment 3 min read ## ⏳ From Dot-Com Bubble to Digital Hype: Learning from the Past Jean Klebert de A Modesto Jean Klebert de A Modesto Jean Klebert de A Modesto Follow Nov 27 '25 ## ⏳ From Dot-Com Bubble to Digital Hype: Learning from the Past # discuss # productivity # career # beginners 3 reactions Comments Add Comment 2 min read loading... trending guides/resources Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story Abrir Propriedades do Sistema via CMD (Windows) How to Organize Your Notes Using Printable Lined Paper — A Simple Productivity Hack How to Find Patent Prior Art in Research Papers Understanding the All Ordinaries Index: Structure, Purpose, and Market Role Science behind Mountain Formation Understanding ASX 200 Futures and Their Role in Market Observation Understanding the Basics of Pay-Per-Click (PPC) Advertising A Beginner’s Guide to Power Yoga for Weight Loss and Strength All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark Decoding Startup Success: Understanding Burn Rate, Runway, and Churn Metrics Understanding the FTSE AIM 100 Index and the Growth Potential of Its Companies Creating a Physical Wired Network in Cisco Packet Tracer - My Experience | Israh Binoj Best Courses to Learn AI for 2026 Yelken Eğitiminde Hissetmenin Bilgiyi Geçtiği An: Teknenin Sizinle Konuştuğu O An Yelken Eğitiminde Sabır: Rüzgarın Öğrettiği En Değerli Ders How We Process Information Using The DIKW Model How to fix: “less than 1MB free space" Warning 📍Un Viaje Continuo: De Córdoba a Barcelona A Beginner’s Guide to Channel Attribution Modeling in 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 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:48:42 |
https://open.forem.com/t/beginners#for-questions | Beginners - 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 Beginners Follow Hide "A journey of a thousand miles begins with a single step." -Chinese Proverb Create Post submission guidelines UPDATED AUGUST 2, 2019 This tag is dedicated to beginners to programming, development, networking, or to a particular language. Everything should be geared towards that! For Questions... Consider using this tag along with #help, if... You are new to a language, or to programming in general, You want an explanation with NO prerequisite knowledge required. You want insight from more experienced developers. Please do not use this tag if you are merely new to a tool, library, or framework. See also, #explainlikeimfive For Articles... Posts should be specifically geared towards true beginners (experience level 0-2 out of 10). Posts should require NO prerequisite knowledge, except perhaps general (language-agnostic) essentials of programming. Posts should NOT merely be for beginners to a tool, library, or framework. If your article does not meet these qualifications, please select a different tag. Promotional Rules Posts should NOT primarily promote an external work. This is what Listings is for. Otherwise accepable posts MAY include a brief (1-2 sentence) plug for another resource at the bottom. Resource lists ARE acceptable if they follow these rules: Include at least 3 distinct authors/creators. Clearly indicate which resources are FREE, which require PII, and which cost money. Do not use personal affiliate links to monetize. Indicate at the top that the article contains promotional links. about #beginners If you're writing for this tag, we recommend you read this article . If you're asking a question, read this article . Older #beginners posts 1 2 3 4 5 6 7 8 9 … 75 … 3379 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu digital marketing Junaid Rana Junaid Rana Junaid Rana Follow Jan 9 digital marketing # ai # programming # beginners # productivity Comments Add Comment 5 min read How to Build a website in 2026: Complete Beginner’s Guide (The Smartest Way to Launch Online This Year) Yogendra Prajapati Yogendra Prajapati Yogendra Prajapati Follow Jan 9 How to Build a website in 2026: Complete Beginner’s Guide (The Smartest Way to Launch Online This Year) # webdev # beginners # tools # business Comments Add Comment 8 min read What I Wish I Knew Before My First LED Strip Install: Light Diffusion + Power Planning emmma emmma emmma Follow Jan 6 What I Wish I Knew Before My First LED Strip Install: Light Diffusion + Power Planning # beginners # design # hardware Comments Add Comment 3 min read Science behind Mountain Formation Gustavo Woltmann Gustavo Woltmann Gustavo Woltmann Follow Jan 4 Science behind Mountain Formation # beginners # learning # science Comments Add Comment 5 min read My Journey: Technology, Knowledge, and Building Meaningful Platforms ARVIND GUPTA ARVIND GUPTA ARVIND GUPTA Follow Dec 22 '25 My Journey: Technology, Knowledge, and Building Meaningful Platforms # technology # software # softwaredevelopment # beginners Comments Add Comment 2 min read Abrir Propriedades do Sistema via CMD (Windows) Carlos Eduardo De Souza Lemos Carlos Eduardo De Souza Lemos Carlos Eduardo De Souza Lemos Follow Dec 22 '25 Abrir Propriedades do Sistema via CMD (Windows) # beginners # learning # productivity Comments Add Comment 2 min read The Art of Mastering Spoken English: A Complete Journey from Silence to Eloquence Abdulla A Abdulla A Abdulla A Follow Dec 23 '25 The Art of Mastering Spoken English: A Complete Journey from Silence to Eloquence # beginners # learning # motivation 1 reaction Comments Add Comment 7 min read 🌿 5 Simple Habits to Improve Your Daily Life Dharmikk Baria Dharmikk Baria Dharmikk Baria Follow Dec 23 '25 🌿 5 Simple Habits to Improve Your Daily Life # watercooler # beginners # motivation Comments Add Comment 1 min read Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story Rajguru Yadav Rajguru Yadav Rajguru Yadav Follow Dec 27 '25 Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story # discuss # programming # ai # beginners 10 reactions Comments Add Comment 3 min read My North Star as an AI Founder (And Why I’m Not Changing It) Jaideep Parashar Jaideep Parashar Jaideep Parashar Follow Dec 18 '25 My North Star as an AI Founder (And Why I’m Not Changing It) # webdev # ai # beginners # productivity 15 reactions Comments 3 comments 3 min read Why is Displacement a straight line from the starting point to the ending point? Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 Why is Displacement a straight line from the starting point to the ending point? # beginners # learning # science Comments Add Comment 2 min read Scalar vs Vector Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 Scalar vs Vector # beginners # learning # science Comments Add Comment 2 min read What Is Displacement? Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 What Is Displacement? # beginners # learning # science Comments Add Comment 2 min read Understanding the FTSE AIM 100: A Look at the UK’s Dynamic Growth Market Isabel Rayn Isabel Rayn Isabel Rayn Follow Dec 11 '25 Understanding the FTSE AIM 100: A Look at the UK’s Dynamic Growth Market # watercooler # beginners # learning Comments Add Comment 4 min read 4.4 ऋग्वैदिक काल Anil Anil Anil Follow Dec 5 '25 4.4 ऋग्वैदिक काल # beginners # education # learning Comments Add Comment 1 min read 🚀 How I Got 25,000+ Views in 2 Days on a YouTube Short Menula De Silva Menula De Silva Menula De Silva Follow Dec 4 '25 🚀 How I Got 25,000+ Views in 2 Days on a YouTube Short # socialmedia # webdev # productivity # beginners 1 reaction Comments Add Comment 3 min read Starting Over in 2026? Here’s How to Create a Vision Board That Supports a Fresh New Beginning Aparnaa Jadhav Aparnaa Jadhav Aparnaa Jadhav Follow Dec 4 '25 Starting Over in 2026? Here’s How to Create a Vision Board That Supports a Fresh New Beginning # beginners # motivation # productivity Comments Add Comment 4 min read Best Courses to Learn AI for 2026 Hameed Ansari Hameed Ansari Hameed Ansari Follow Dec 8 '25 Best Courses to Learn AI for 2026 # ai # programming # productivity # beginners 5 reactions Comments Add Comment 1 min read All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark Amelia Hartley Amelia Hartley Amelia Hartley Follow Dec 4 '25 All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark # beginners # learning Comments Add Comment 4 min read How to Search Non-Patent Literature for Prior Art Alisha Raza Alisha Raza Alisha Raza Follow for PatentScanAI Dec 1 '25 How to Search Non-Patent Literature for Prior Art # beginners # learning # productivity Comments Add Comment 7 min read Understanding the FTSE AIM 100 Index and the Growth Potential of Its Companies Bella Stewart Bella Stewart Bella Stewart Follow Dec 1 '25 Understanding the FTSE AIM 100 Index and the Growth Potential of Its Companies # beginners # learning Comments Add Comment 3 min read Running Without a Plan and Learning Who I Am Miles Hensley Miles Hensley Miles Hensley Follow Nov 29 '25 Running Without a Plan and Learning Who I Am # watercooler # beginners # motivation Comments Add Comment 11 min read A Beginner’s Guide to Power Yoga for Weight Loss and Strength bhaktimeshakti bhaktimeshakti bhaktimeshakti Follow Nov 30 '25 A Beginner’s Guide to Power Yoga for Weight Loss and Strength # watercooler # motivation # learning # beginners Comments Add Comment 6 min read Beginner’s Guide to IT Support Ticketing Systems Amit khan Amit khan Amit khan Follow Nov 27 '25 Beginner’s Guide to IT Support Ticketing Systems # beginners # career # helpedesk # productivity Comments 1 comment 3 min read ## ⏳ From Dot-Com Bubble to Digital Hype: Learning from the Past Jean Klebert de A Modesto Jean Klebert de A Modesto Jean Klebert de A Modesto Follow Nov 27 '25 ## ⏳ From Dot-Com Bubble to Digital Hype: Learning from the Past # discuss # productivity # career # beginners 3 reactions Comments Add Comment 2 min read loading... trending guides/resources Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story Abrir Propriedades do Sistema via CMD (Windows) How to Organize Your Notes Using Printable Lined Paper — A Simple Productivity Hack How to Find Patent Prior Art in Research Papers Understanding the All Ordinaries Index: Structure, Purpose, and Market Role Science behind Mountain Formation Understanding ASX 200 Futures and Their Role in Market Observation Understanding the Basics of Pay-Per-Click (PPC) Advertising A Beginner’s Guide to Power Yoga for Weight Loss and Strength All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark Decoding Startup Success: Understanding Burn Rate, Runway, and Churn Metrics Understanding the FTSE AIM 100 Index and the Growth Potential of Its Companies Creating a Physical Wired Network in Cisco Packet Tracer - My Experience | Israh Binoj Best Courses to Learn AI for 2026 Yelken Eğitiminde Hissetmenin Bilgiyi Geçtiği An: Teknenin Sizinle Konuştuğu O An Yelken Eğitiminde Sabır: Rüzgarın Öğrettiği En Değerli Ders How We Process Information Using The DIKW Model How to fix: “less than 1MB free space" Warning 📍Un Viaje Continuo: De Córdoba a Barcelona A Beginner’s Guide to Channel Attribution Modeling in 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 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:48:42 |
https://docs.suprsend.com/docs#suprsend-apis | What is SuprSend? - 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 GETTING STARTED What is SuprSend? Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog GETTING STARTED What is SuprSend? OpenAI Open in ChatGPT Learn about SuprSend and how you can use it to power multi-channel product notifications. OpenAI Open in ChatGPT SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack: You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritise vendors and channels from your SuprSend account, You can design powerful templates for all channels together and manage them from a single place, You can leverage powerful features to experiment fast with notifications as well as take care of end user experience without writing a single line of code. Introduction to Workflows Communications are made up of multiple components - trigger, logic, content, variables, target user, channels, vendors, etc. Typical communication solutions have one or more components intertwined with each other. SuprSend solves communications from a different and more powerful approach, which we call Workflows. At SuprSend, all the constituent components are decoupled from each other, making it modular in nature. The components can come from any source. All these components are configured as nodes in Workflows, where the processing happens for delivery and optimisation. This allows Workflows to handle any complexity possible in your communication use cases. How do you trigger notifications? You can trigger notifications in one of the two ways: Send events to SuprSend from your frontend clients (android app, website, etc) via SuprSend Client SDK, and create a Workflow on SuprSend platform to trigger notification on an event. Create workflow and trigger notification from your backend itself using an omni-channel HTTPS API method, or you can use our Backend SDK. All the other components (like vendors, templates, optimisation, scaling, etc.) are created and managed on SuprSend platform. You can check the ‘Core Concepts’ section that lists down the components used in the platform, so you can navigate the platform and use all the features with ease. SuprSend APIs You can try out SuprSend APIs from our Postman collection Was this page helpful? Yes No Suggest edits Raise issue Overview Start setting up your notifications with SuprSend by following quick start guides for one of the mentioned channels. Next ⌘ I x github linkedin youtube Powered by On this page Benefits of using SuprSend as your notification stack: Introduction to Workflows How do you trigger notifications? SuprSend APIs | 2026-01-13T08:48:42 |
https://docs.suprsend.com/reference/cli-workflow-push | Push Workflows - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations 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 Push Workflows Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Workflow Push Workflows OpenAI Open in ChatGPT Push workflows from local directory or server to SuprSend OpenAI Open in ChatGPT ⚠️ Important: Always sync Schema and Category changes before pushing Workflows. If the schema or category referenced in a workflow is not available in the target workspace, it will result in validation errors during sync. Pushed workflows are saved in draft version. Make sure to pass --commit=true flag to commit the workflows while pushing it. Syntax Copy Ask AI suprsend workflow push [flags] Flags Flag Description Default -h, --help Show help for the command – -c, --commit string Commit the workflows (—commit=true) true -m, --commit-message string Commit message describing the changes for —commit=true – -d, --dir string Output directory for workflows suprsend/workflow -g, --slug string Slug of the workflow to push – Example Copy Ask AI # Push workflows from default directory suprsend workflow push # Push workflows from custom directory suprsend workflow push --dir dev-environment/workflows # Push individual workflow by passing it's slug suprsend workflow push --slug welcome-email # Push workflows and commit them suprsend workflow push --commit=true --commit-message "Commit message" 🚨 Push and Commit Behavior : New workflow not showing up? → Push without commit first, then commit separately Changes not appearing in live mode? → Check if workflows are linked to other workflows Fix : Update your workflow files to include all dependencies, or remove the links Was this page helpful? Yes No Suggest edits Raise issue Previous Enable Workflow Enable a workflow in a SuprSend workspace to start processing notifications. Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example | 2026-01-13T08:48:42 |
https://dev.to/t/perl | Perl - 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 Perl Follow Hide Perl is a high-level dynamic programming language with some extraordinary features that make using it fun and that make the users productive. As the saying goes, TMTOWTDI — "There's more than one way to do it." Create Post submission guidelines All about Perl Older #perl 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 Perl 🐪 Weekly #755 - Does TIOBE help Perl? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jan 12 Perl 🐪 Weekly #755 - Does TIOBE help Perl? # news # perl # programming Comments Add Comment 6 min read Marlin Racing Toby Inkster Toby Inkster Toby Inkster Follow Jan 11 Marlin Racing # perl # oop # moose # moo 1 reaction Comments Add Comment 4 min read Perl 🐪 Weekly #754 - New Year Resolution Gabor Szabo Gabor Szabo Gabor Szabo Follow Jan 5 Perl 🐪 Weekly #754 - New Year Resolution # news # perl # programming Comments Add Comment 6 min read Weekly Challenge: Commify every mountain Simon Green Simon Green Simon Green Follow Jan 6 Weekly Challenge: Commify every mountain # perl # python # theweeklychallenge Comments Add Comment 3 min read Weekly Challenge: New Year, New Challenges Simon Green Simon Green Simon Green Follow Jan 2 Weekly Challenge: New Year, New Challenges # perl # python # theweeklychallenge Comments Add Comment 3 min read App::HTTPThis: the tiny web server I keep reaching for Dave Cross Dave Cross Dave Cross Follow Jan 4 App::HTTPThis: the tiny web server I keep reaching for # web # httpthis # perl # staticsites 1 reaction Comments Add Comment 5 min read The Perl Claude Agent LNATION LNATION LNATION Follow for LNATION Jan 11 The Perl Claude Agent # perl # ai # programming Comments 2 comments 11 min read Weekly Challenge: Validating Words Simon Green Simon Green Simon Green Follow Dec 28 '25 Weekly Challenge: Validating Words # python # theweeklychallenge # perl Comments Add Comment 3 min read Weekly Challenge: Strings and Binaries Simon Green Simon Green Simon Green Follow Dec 21 '25 Weekly Challenge: Strings and Binaries # perl # python # theweeklychallenge Comments Add Comment 3 min read PWC 352 Five is the one-liest number Bob Lied Bob Lied Bob Lied Follow Dec 19 '25 PWC 352 Five is the one-liest number # perl # perlweeklychallenge # pwc Comments Add Comment 4 min read Perl 🐪 Weekly #753 - Happy New Year! Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 29 '25 Perl 🐪 Weekly #753 - Happy New Year! # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl PAGI Project Update John Napiorkowski John Napiorkowski John Napiorkowski Follow Dec 28 '25 Perl PAGI Project Update # webdev # perl 3 reactions Comments 2 comments 5 min read Perl 🐪 Weekly #752 - Marlin - OOP Framework Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 22 '25 Perl 🐪 Weekly #752 - Marlin - OOP Framework # news # perl # programming 2 reactions Comments Add Comment 7 min read Weekly Challenge: Average Progression Simon Green Simon Green Simon Green Follow Dec 14 '25 Weekly Challenge: Average Progression # perl # python # theweeklychallenge Comments Add Comment 3 min read PWC 353 To each (array) his own Bob Lied Bob Lied Bob Lied Follow Dec 22 '25 PWC 353 To each (array) his own # perl # perlweeklychallenge # pwc Comments Add Comment 5 min read Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 8 '25 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 # news # perl # programming 1 reaction Comments Add Comment 7 min read Weekly Challenge: Good shuffling Simon Green Simon Green Simon Green Follow Dec 7 '25 Weekly Challenge: Good shuffling # python # theweeklychallenge # perl Comments Add Comment 3 min read PWC 350 Good Substring / Shuffle Pairs Bob Lied Bob Lied Bob Lied Follow Dec 3 '25 PWC 350 Good Substring / Shuffle Pairs # perl # perlweeklychallenge # pwc Comments Add Comment 5 min read Why I Built a jq-Compatible Tool in Pure Perl (and Why It Still Matters) Shingo Kawamura Shingo Kawamura Shingo Kawamura Follow Jan 2 Why I Built a jq-Compatible Tool in Pure Perl (and Why It Still Matters) # perl # devops # cli # legacy 2 reactions Comments 2 comments 3 min read PWC 349 More complex than it has to be Bob Lied Bob Lied Bob Lied Follow Nov 26 '25 PWC 349 More complex than it has to be # perl # perlweeklychallenge # pwc Comments Add Comment 3 min read Maintenance release 2.09 for the Perl Distribution Workflow Jonas Brømsø Jonas Brømsø Jonas Brømsø Follow Nov 23 '25 Maintenance release 2.09 for the Perl Distribution Workflow # maintenance # release # perl Comments Add Comment 2 min read The Weekly Challenge: Alike Time Simon Green Simon Green Simon Green Follow Nov 23 '25 The Weekly Challenge: Alike Time # python # perl # theweeklychallenge Comments Add Comment 3 min read NOAA::Aurora for Space Weather Forecasts Dimitrios Kechagias Dimitrios Kechagias Dimitrios Kechagias Follow Dec 25 '25 NOAA::Aurora for Space Weather Forecasts # perl # weather # cpan 2 reactions Comments Add Comment 1 min read PWC 348 String Alike, Convert Time Bob Lied Bob Lied Bob Lied Follow Nov 19 '25 PWC 348 String Alike, Convert Time # perl # perlweeklychallenge # pwc Comments Add Comment 4 min read Weekly Challenge: The one about formatting Simon Green Simon Green Simon Green Follow Nov 16 '25 Weekly Challenge: The one about formatting # perl # python # theweeklychallenge Comments Add Comment 4 min read loading... trending guides/resources Perl PAGI Project Update Perl 🐪 Weekly #749 - Design Patterns in Modern Perl PWC 353 To each (array) his own PAGI: ASGI For Perl, or the Spiritual Successor to Plack Introducing Marlin Perl 🐪 Weekly #753 - Happy New Year! Perl 🐪 Weekly #754 - New Year Resolution The Weekly Challenge: Alike Time Dancing in the Clouds: Moving Dancer2 Apps from a VPS to Cloud Run PWC 348 String Alike, Convert Time Dotcom Survivor Syndrome – How Perl’s Early Success Created the Seeds of Its Downfall Perl 🐪 Weekly #752 - Marlin - OOP Framework Weekly Challenge: Commify every mountain Perl 🐪 Weekly #748 - Perl v5.43.5 Perl 🐪 Weekly #751 - Open Source contributions Perl 🐪 Weekly #755 - Does TIOBE help Perl? PWC 350 Good Substring / Shuffle Pairs Weekly Challenge: Validating Words The Perl Claude Agent Marlin Racing 💎 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:48:42 |
https://docs.suprsend.com/reference/cli-translation-list | List Translations - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Translation List Translations Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Translation List Translations OpenAI Open in ChatGPT List translations in a workspace OpenAI Open in ChatGPT Syntax Copy Ask AI suprsend translation list [flags] Flags Flag Description Default -h, --help Show help for the command – -c, --content string Include content in the output false -l, --limit int Limit the number of translations to list 20 -m, --mode string Mode to list translations for live -f, --offset int Offset the number of translations to list – -o, --output string Output type (pretty, yaml, json) pretty Example Copy Ask AI # List translations in staging workspace (default) suprsend translation list # List translations in production workspace suprsend translation list --workspace production # List draft translations with limit suprsend translation list --mode draft --limit 50 # List translations in JSON format suprsend translation list --output json # List translations with content included suprsend translation list --content true Was this page helpful? Yes No Suggest edits Raise issue Previous Pull Translations Fetch translations from SuprSend workspace to local directory Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example | 2026-01-13T08:48:42 |
https://docs.suprsend.com/docs#benefits-of-using-suprsend-as-your-notification-stack%3A | What is SuprSend? - 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 GETTING STARTED What is SuprSend? Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog GETTING STARTED What is SuprSend? OpenAI Open in ChatGPT Learn about SuprSend and how you can use it to power multi-channel product notifications. OpenAI Open in ChatGPT SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack: You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritise vendors and channels from your SuprSend account, You can design powerful templates for all channels together and manage them from a single place, You can leverage powerful features to experiment fast with notifications as well as take care of end user experience without writing a single line of code. Introduction to Workflows Communications are made up of multiple components - trigger, logic, content, variables, target user, channels, vendors, etc. Typical communication solutions have one or more components intertwined with each other. SuprSend solves communications from a different and more powerful approach, which we call Workflows. At SuprSend, all the constituent components are decoupled from each other, making it modular in nature. The components can come from any source. All these components are configured as nodes in Workflows, where the processing happens for delivery and optimisation. This allows Workflows to handle any complexity possible in your communication use cases. How do you trigger notifications? You can trigger notifications in one of the two ways: Send events to SuprSend from your frontend clients (android app, website, etc) via SuprSend Client SDK, and create a Workflow on SuprSend platform to trigger notification on an event. Create workflow and trigger notification from your backend itself using an omni-channel HTTPS API method, or you can use our Backend SDK. All the other components (like vendors, templates, optimisation, scaling, etc.) are created and managed on SuprSend platform. You can check the ‘Core Concepts’ section that lists down the components used in the platform, so you can navigate the platform and use all the features with ease. SuprSend APIs You can try out SuprSend APIs from our Postman collection Was this page helpful? Yes No Suggest edits Raise issue Overview Start setting up your notifications with SuprSend by following quick start guides for one of the mentioned channels. Next ⌘ I x github linkedin youtube Powered by On this page Benefits of using SuprSend as your notification stack: Introduction to Workflows How do you trigger notifications? SuprSend APIs | 2026-01-13T08:48:42 |
https://docs.suprsend.com/docs/integrate-go-sdk#installation | Integrate Go SDK - 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 Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Node.js SDK Java SDK Go SDK Integrate Go SDK Manage Users Send and Track Events Trigger Workflow from API Tenants Lists Broadcast SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Go SDK Integrate Go SDK Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Go SDK Integrate Go SDK OpenAI Open in ChatGPT Install & Initialize SuprSend Go SDK using your workspace credentials for sending notifications. OpenAI Open in ChatGPT Installation Install suprsend-go sdk bash Copy Ask AI go get github.com/suprsend/suprsend-go Initialization For initializing SDK, you need workspace_key and workspace_secret. You will get both the tokens from your Suprsend dashboard (Developers -> API Keys). Request Copy Ask AI package main import ( " log " suprsend " github.com/suprsend/suprsend-go " ) // Initialize SDK func main () { opts := [] suprsend . ClientOption { // suprsend.WithDebug(true), } suprClient , err := suprsend . NewClient ( "__workspace_key__" , "__workspace_secret__" , opts ... ) if err != nil { log . Println ( err ) } } Was this page helpful? Yes No Suggest edits Raise issue Previous Manage Users Manage user profiles and communication channels programmatically with the Go SDK. Next ⌘ I x github linkedin youtube Powered by On this page Installation Initialization | 2026-01-13T08:48:42 |
https://dev.to/szabgab | Gabor Szabo - 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 Gabor Szabo Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Joined Joined on Oct 11, 2017 Email address gabor@szabgab.com Personal website https://szabgab.com github website twitter website Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Eight Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least eight years. Got it Close 2 Top 7 Awarded for having a post featured in the weekly "must-reads" list. 🙌 Got it Close Rust Awarded to the top Rust author each week Got it Close 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 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 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 16 Week Writing Streak You are a writing star! You've written at least one post per week for 16 straight weeks. Congratulations! Got it Close 8 Week Community Wellness Streak Consistency pays off! Be an active part of our community by posting at least 2 comments per week for 8 straight weeks. Earn the 16 Week Badge next. Got it Close Tag Moderator 2022 Awarded for being a tag moderator in 2022. Got it Close Trusted Member 2022 Awarded for being a trusted member in 2022. 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 Community Wellness Streak Keep contributing to discussions by posting at least 2 comments per week for 4 straight weeks. Unlock the 8 Week Badge next. Got it Close 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 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 1 Week Community Wellness Streak For actively engaging with the community by posting at least 2 comments in a single week. 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 Hacktoberfest 2020 Awarded for successful completion of the 2020 Hacktoberfest challenge. 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 Hacktoberfest 2019 Awarded for successful completion of the 2019 Hacktoberfest challenge. 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 Show all 23 badges More info about @szabgab Organizations Code Maven Skills/Languages Perl, Python, Git, CI systems, Test Automation, Docker, DevOps related tools Currently learning More CI systems, Video creation Currently hacking on The digger projects - PyDigger, Ruby Digger, CPAN Digger Available for Helping with testing, test automation, CI, CD, Docker Post 372 posts published Comment 240 comments written Tag 24 tags followed Pin Pinned Billions of unnecessary files in GitHub Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 21 '22 Billions of unnecessary files in GitHub # github # programming # python # webdev 125 reactions Comments 51 comments 3 min read Why use a version control system? - 💒 Gabor Szabo Gabor Szabo Gabor Szabo Follow Nov 28 '22 Why use a version control system? - 💒 # git # programming # beginners # tutorial 6 reactions Comments 3 comments 5 min read Python Functional Programming: Introduction Gabor Szabo Gabor Szabo Gabor Szabo Follow Nov 25 '22 Python Functional Programming: Introduction # python # tutorial # programming 11 reactions Comments 1 comment 3 min read Docker course: Introduction Gabor Szabo Gabor Szabo Gabor Szabo Follow Nov 22 '22 Docker course: Introduction # docker # tutorial # beginners # devops 9 reactions Comments 2 comments 1 min read Perl 🐪 Weekly #755 - Does TIOBE help Perl? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jan 12 Perl 🐪 Weekly #755 - Does TIOBE help Perl? # news # perl # programming Comments Add Comment 6 min read Want to connect with Gabor Szabo? Create an account to connect with Gabor Szabo. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in Perl 🐪 Weekly #754 - New Year Resolution Gabor Szabo Gabor Szabo Gabor Szabo Follow Jan 5 Perl 🐪 Weekly #754 - New Year Resolution # news # perl # programming Comments Add Comment 6 min read Perl 🐪 Weekly #753 - Happy New Year! Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 29 '25 Perl 🐪 Weekly #753 - Happy New Year! # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl 🐪 Weekly #752 - Marlin - OOP Framework Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 22 '25 Perl 🐪 Weekly #752 - Marlin - OOP Framework # news # perl # programming 2 reactions Comments Add Comment 7 min read Perl 🐪 Weekly #751 - Open Source contributions Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 15 '25 Perl 🐪 Weekly #751 - Open Source contributions # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 8 '25 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 # news # perl # programming 1 reaction Comments Add Comment 7 min read Perl 🐪 Weekly #749 - Design Patterns in Modern Perl Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 1 '25 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl 🐪 Weekly #748 - Perl v5.43.5 Gabor Szabo Gabor Szabo Gabor Szabo Follow Nov 24 '25 Perl 🐪 Weekly #748 - Perl v5.43.5 # news # perl # programming 2 reactions Comments Add Comment 6 min read Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 Gabor Szabo Gabor Szabo Gabor Szabo Follow Nov 10 '25 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 # news # perl # programming 2 reactions Comments Add Comment 5 min read Perl 🐪 Weekly #745 - Perl IDE Survey Gabor Szabo Gabor Szabo Gabor Szabo Follow Nov 3 '25 Perl 🐪 Weekly #745 - Perl IDE Survey # news # perl # programming 2 reactions Comments Add Comment 7 min read How to find an open source project to contribute to? Gabor Szabo Gabor Szabo Gabor Szabo Follow Oct 28 '25 How to find an open source project to contribute to? # opensource # programming # beginners 6 reactions Comments Add Comment 1 min read Perl 🐪 Weekly #744 - London Perl Workshop 2025 Gabor Szabo Gabor Szabo Gabor Szabo Follow Oct 27 '25 Perl 🐪 Weekly #744 - London Perl Workshop 2025 # news # perl # programming 1 reaction Comments Add Comment 8 min read Perl 🐪 Weekly #743 - Writing Perl with LLMs Gabor Szabo Gabor Szabo Gabor Szabo Follow Oct 20 '25 Perl 🐪 Weekly #743 - Writing Perl with LLMs # news # perl # programming 1 reaction Comments Add Comment 7 min read Perl 🐪 Weekly #742 - Support TPRF Gabor Szabo Gabor Szabo Gabor Szabo Follow Oct 13 '25 Perl 🐪 Weekly #742 - Support TPRF # news # perl # programming 1 reaction Comments Add Comment 7 min read Perl 🐪 Weekly #741 - Money to TPRF 💰 Gabor Szabo Gabor Szabo Gabor Szabo Follow Oct 6 '25 Perl 🐪 Weekly #741 - Money to TPRF 💰 # news # perl # programming Comments Add Comment 7 min read Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 Gabor Szabo Gabor Szabo Gabor Szabo Follow Sep 22 '25 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 # news # perl # programming 2 reactions Comments Add Comment 5 min read Perl 🐪 Weekly #737 - Perl oneliners Gabor Szabo Gabor Szabo Gabor Szabo Follow Sep 8 '25 Perl 🐪 Weekly #737 - Perl oneliners # news # perl # programming 2 reactions Comments Add Comment 6 min read Perl 🐪 Weekly #736 - NICEPERL Gabor Szabo Gabor Szabo Gabor Szabo Follow Sep 1 '25 Perl 🐪 Weekly #736 - NICEPERL # news # perl # programming 2 reactions Comments 1 comment 6 min read Programming communities? Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 25 '25 Programming communities? # programming # beginners 5 reactions Comments 5 comments 2 min read Perl 🐪 Weekly #735 - Perl-related events Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 25 '25 Perl 🐪 Weekly #735 - Perl-related events # news # perl # programming Comments Add Comment 5 min read Open Source Software Foundations Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 22 '25 Open Source Software Foundations # opensource # programming Comments Add Comment 1 min read Why Testing? Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 20 '25 Why Testing? # testing # programming # beginners Comments 1 comment 2 min read Perl 🐪 Weekly #734 - CPAN Day Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 18 '25 Perl 🐪 Weekly #734 - CPAN Day # news # perl # programming Comments Add Comment 5 min read Python Flask: Testing hello world Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 13 '25 Python Flask: Testing hello world # python # webdev # testing # programming 1 reaction Comments Add Comment 1 min read Python Flask: Hello World Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 12 '25 Python Flask: Hello World # python # webdev # programming # tutorial 1 reaction Comments 1 comment 1 min read Perl 🐪 Weekly #733 - Perl using AI Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 11 '25 Perl 🐪 Weekly #733 - Perl using AI # news # perl # programming Comments Add Comment 6 min read What is the interest of companies in Open Source? Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 5 '25 What is the interest of companies in Open Source? # opensource # programming # beginners 2 reactions Comments Add Comment 1 min read How to find projects that are easy to contribute to? Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 4 '25 How to find projects that are easy to contribute to? # opensource # beginners # programming 2 reactions Comments Add Comment 1 min read Perl 🐪 Weekly #732 - MetaCPAN Success Story Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 4 '25 Perl 🐪 Weekly #732 - MetaCPAN Success Story # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl 🐪 Weekly #731 - Looking for a Perl event organizer Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 28 '25 Perl 🐪 Weekly #731 - Looking for a Perl event organizer # news # perl # programming 1 reaction Comments Add Comment 5 min read Perl 🐪 Weekly #730 - RIP MST Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 21 '25 Perl 🐪 Weekly #730 - RIP MST # news # perl # programming 1 reaction Comments Add Comment 7 min read Should you start your own open source project or should you contribute to an existing one? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 15 '25 Should you start your own open source project or should you contribute to an existing one? # opensource # programming # career Comments 2 comments 2 min read Contributing to a well-known Open Source project Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 14 '25 Contributing to a well-known Open Source project # opensource # programming 3 reactions Comments Add Comment 1 min read Perl 🐪 Weekly #729 - Videos from TPRC Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 14 '25 Perl 🐪 Weekly #729 - Videos from TPRC # news # perl # programming 2 reactions Comments Add Comment 5 min read Why do you contribute to Open Source? What is your motivation? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 13 '25 Why do you contribute to Open Source? What is your motivation? # opensource # beginners # programming # career 1 reaction Comments Add Comment 2 min read Contributing to PyPI Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 12 '25 Contributing to PyPI # python # opensource # programming 2 reactions Comments Add Comment 1 min read Would you like to be a movie star by contributing to open source? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 11 '25 Would you like to be a movie star by contributing to open source? # opensource # programming # python # cybersecurity 1 reaction Comments Add Comment 2 min read How to contribute to Moodle? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 10 '25 How to contribute to Moodle? # opensource # php # beginners # programming 2 reactions Comments Add Comment 3 min read Do you need to be a programmer to contribute to open source projects? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 8 '25 Do you need to be a programmer to contribute to open source projects? # opensource # beginners 1 reaction Comments Add Comment 1 min read Perl 🐪 Weekly #728 - Perl Conference Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 7 '25 Perl 🐪 Weekly #728 - Perl Conference # news # perl # programming 1 reaction Comments Add Comment 7 min read Perl 🐪 Weekly #727 - Which versions of Perl do you use? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jun 30 '25 Perl 🐪 Weekly #727 - Which versions of Perl do you use? # news # perl # programming Comments Add Comment 8 min read Perl 🐪 Weekly #726 - Perl and ChatGPT Gabor Szabo Gabor Szabo Gabor Szabo Follow Jun 23 '25 Perl 🐪 Weekly #726 - Perl and ChatGPT # news # perl # programming Comments Add Comment 7 min read Perl 🐪 Weekly #725 - Perl podcasts? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jun 23 '25 Perl 🐪 Weekly #725 - Perl podcasts? # news # perl # programming Comments Add Comment 6 min read Publishing in Arabic, Hebrew, or Persian? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jun 16 '25 Publishing in Arabic, Hebrew, or Persian? # github # gitlab 2 reactions Comments Add Comment 1 min read Perl 🐪 Weekly #724 - Perl and XS Gabor Szabo Gabor Szabo Gabor Szabo Follow Jun 9 '25 Perl 🐪 Weekly #724 - Perl and XS # news # perl # programming 2 reactions Comments 2 comments 5 min read Perl 🐪 Weekly #723 - Perl Ad Server needs ads Gabor Szabo Gabor Szabo Gabor Szabo Follow Jun 2 '25 Perl 🐪 Weekly #723 - Perl Ad Server needs ads # news # perl # programming 2 reactions Comments Add Comment 5 min read Perl 🐪 Weekly #721 - Perl Roadmap Gabor Szabo Gabor Szabo Gabor Szabo Follow May 19 '25 Perl 🐪 Weekly #721 - Perl Roadmap # news # perl # programming 2 reactions Comments 1 comment 6 min read Perl 🐪 Weekly #720 - GPW 2025 Gabor Szabo Gabor Szabo Gabor Szabo Follow May 12 '25 Perl 🐪 Weekly #720 - GPW 2025 # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl 🐪 Weekly #719 - How do you deal with the decline? Gabor Szabo Gabor Szabo Gabor Szabo Follow May 5 '25 Perl 🐪 Weekly #719 - How do you deal with the decline? # news # perl # programming 2 reactions Comments Add Comment 5 min read Perl 🐪 Weekly #717 - Happy Easter Gabor Szabo Gabor Szabo Gabor Szabo Follow Apr 21 '25 Perl 🐪 Weekly #717 - Happy Easter # news # perl # programming 1 reaction Comments Add Comment 5 min read Perl 🐪 Weekly #716 - CVE in Perl Gabor Szabo Gabor Szabo Gabor Szabo Follow Apr 14 '25 Perl 🐪 Weekly #716 - CVE in Perl # news # perl # programming Comments Add Comment 6 min read Perl 🐪 Weekly #715 - Why do companies move away from Perl? Gabor Szabo Gabor Szabo Gabor Szabo Follow Apr 7 '25 Perl 🐪 Weekly #715 - Why do companies move away from Perl? # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl 🐪 Weekly #714 - Munging Data? Gabor Szabo Gabor Szabo Gabor Szabo Follow Mar 31 '25 Perl 🐪 Weekly #714 - Munging Data? # news # perl # programming 2 reactions Comments Add Comment 6 min read Public mdBooks Gabor Szabo Gabor Szabo Gabor Szabo Follow Mar 30 '25 Public mdBooks # rust # programming # tutorial # productivity 2 reactions Comments Add Comment 1 min read Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? Gabor Szabo Gabor Szabo Gabor Szabo Follow Mar 24 '25 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? # news # perl # programming 2 reactions Comments Add Comment 6 min read Perl 🐪 Weekly #712 - RIP Zefram Gabor Szabo Gabor Szabo Gabor Szabo Follow Mar 17 '25 Perl 🐪 Weekly #712 - RIP Zefram # news # perl # programming 1 reaction Comments Add Comment 7 min read Perl 🐪 Weekly #711 - Obfuscating Perl Gabor Szabo Gabor Szabo Gabor Szabo Follow Mar 10 '25 Perl 🐪 Weekly #711 - Obfuscating Perl # news # perl # programming 1 reaction Comments Add Comment 5 min read Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes Gabor Szabo Gabor Szabo Gabor Szabo Follow Mar 3 '25 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes # news # perl # programming 2 reactions Comments Add Comment 6 min read Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit Gabor Szabo Gabor Szabo Gabor Szabo Follow Feb 24 '25 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit # news # perl # programming 1 reaction Comments Add Comment 5 min read Online events: Python in English (Feb 18-Feb 28) Gabor Szabo Gabor Szabo Gabor Szabo Follow Feb 18 '25 Online events: Python in English (Feb 18-Feb 28) # python 2 reactions 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:48:42 |
https://dev.to/szabgab/perl-weekly-600-600th-edition-and-still-going--4ika | Perl Weekly #600 - 600th edition and still going ... - 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 Gabor Szabo Posted on Jan 23, 2023 • Originally published at perlweekly.com Perl Weekly #600 - 600th edition and still going ... # perl # news # programming perl-weekly (153 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 149 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution Originally published at Perl Weekly 600 Hi there, Last week, Team PWC celebrated the 200th week and today we are presenting 600th edition . Kudos to all the editors, current and past for the care and affections. It feels nice to be associated with such a popular events. I would also like to thank all the die hard fans of the Perl Weekly Newsletter for their support and constructive suggestions from time to time. It really helps me to focus on things important to the readers. I know it is not easy to do this every week but the love and affection we get works like a magic. I remember there was time when blogging was the only source of information but now a days we have plenty of platforms where you get usefull informations. You know what I mean and where you can catch us. I love having 2-ways dicussion on any topics related to Perl. It is something I always encourage if you have spare time. I have seen how young blood getting involved in so many exciting things about Perl, for example on Telegram . Although I don't get time to take part in the discussion but I do watch how the discussion follow through. I have senior member of Perl Community helping young blood with their experiences. It would be unfair to name few here. You know who I am talking about. I salute to all those who keep Perl alive. If you have any ideas/suggestions then please do share with us. I would to hear your point of views. Enjoy the rest of the newsletter till then. -- Your editor: Mohammad S. Anwar. Announcement by Gabor Open Source Development Course for Perl developers Last week I already mentioned this course that will start tomorrow , January 24th, 2023. In the course we'll learn and practice all the process of contributing to Open Source projects with an emphasize on Perl. We'll learn and practice git/github/pull-request/github pages/testing/test coverage/github actions/etc. You can still register and join the group. Announcements This Week in PSC (094) I love getting regular update by the Perl Steering Council. Every minute details are now public. Well done. OTOBO supports the German Perl/Raku-Workshop Happy to see GPW getting support of OTOBO. You should attend the workshop if you can. It is not just for German speaking audience. I have attended once in the past too. Retirement Announcement - Dave Rolsky After several years of service to The Perl/Raku Foundation, Dave Rolsky is retiring. The board thanks Dave for all of his work, he will be missed. Articles Using Perl to prepare sequencing files to submit to NCBI's GEO Pleasantly surprised to see how Perl can be used is so many different fields. Util::H2O and More, during Ordinary Times Nice to see, Perl Advent Calendar post is still being discussed today. We should all share the work done by the Perl community with the rest of the world. My Family and Other Fish (PerlayStation Part 2) Good to see Saif is back. I find the subject very engaging and ofcouse his style of writing takes it to another level.. Regexp Delimiters Looking at regexp through the lens of Perl is always fun. You will never get bored. Web Synacor Challenge - my repo Did you know about Synacor Challenge? I didn't. Find out more in the blog post. KnowTee - easy notifications Another tool for hobby-scale projects. Interesting, worth checking. The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 201 Welcome to a new week with a couple of fun tasks: "Missing Numbers" and "Penny Piles". If you are new to the weekly challenge, why not join us and have fun every week? For more information, please read the FAQ . RECAP - The Weekly Challenge - 200 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Arithmetic Slices" and "Seven Segment 200" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Seven Angry Slices The verbose version of solution is worth checking. Keep it up great work. Seven Segments to Midnight The background story of task is something you don't want to miss it. I loved it. Thank you Colin. Bicent-Weekly Solution Loop is the flavour of the week. Complicated solutions can be solved using simple loops. Well done. Weekly Challenge 200 Nice to know how Perl and Raku behave differently at times. Thanks for sharing your experience. PWC200 - Arithmetic Slices No question from Flavio this week. Straight to the solution in Perl and Raku. Thank you. PWC200 - Seven Segment 200 Good use of state in the solution. Thanks for sharing. The Weekly Challenge 200 We missed the performance stats this week. Never mind, we still have top notch solution. Perl Weekly Challenge 200: Arithmetic Slices and Seven Segment Display Plenty of demo makes it crystal clear how the code works. Cool attempt. Keep it up. not optimal! Easy route picked up by Luca, still not a bad attempt. Thanks for your contributions. Perl Weekly Challenge 200 Use of binary mask is good choice. I liked it, thanks for sharing. Slicing and dicing a double century The simplest solution yet very compact. I am impressed. Well done. The Weekly Challenge #200 Robbie found task #2 easier than task #1. It was supposed to the otherway around. Still we got two nice solutions. Thank you. Seven Slices Use of bitmap table is really nice. Thanks for sharing your knowledge with us. Two hundred slices Thank you for spreading the work on dev.to site and your kind message. We got the usual collection of Perl and Python, deadly combination. PWC 200 I liked the various different approaches being used by all. Steve came up with simple string to solve the task. Nice one. Rakudo 2023.03 Advent Radux Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . The corner of Gabor A couple of entries sneaked in by Gabor. one-liner: read first elements of a huge directory At a client where I work we have a pretty big folder with quite a few files. Trying the list the first few files was an issue with ls and thus I wrote a short one-liner. Then shortened it. I wrote an article about it. Then Aristotle further improved it. It's all there in the blog post. Open Source Development Course for Perl developers Last week I already mentioned this course that will start tomorrow , January 24th, 2023. In the course we'll learn and practice all the process of contributing to Open Source projects with an emphasize on Perl. We'll learn and practice git/github/pull-request/github pages/testing/test coverage/github actions/etc. You can still register and join the group. Perl Jobs by Perl Careers Perl to Node Cross-training? Yes Please! UK Remote Perl Role The client is interested in anyone with experience building web apps in Perl, using one of the major Perl frameworks. If you’re a crack-hand with Catalyst, a Mojolicious master, or a distinguished Dancer, they want you. You’ll be deploying apps your work to AWS, so experience would be handy, and the company’s big on testing, so they’d like you to know your way around Test::More. Bold, beautiful, and… brainy? Senior Perl roles in Malaysia, Dubai and Malta Offices are located within Dubai, Malta, and Malaysia so if you’re in one of those places, you’re one step closer to where you need to be. Hanging out in Honolulu? Not to worry. For the right person, they’ve got a work-sponsored visa and relocation package — if you’ve got the expertise and an adventurous spirit, they’ve got the will and means to get you where you need to be. Modern Perl and positive team vibes. UK Remote Perl role If you’re a Modern Perl developer in the UK with Go-lang experience (or at least a strong desire to learn) and you’re searching for a team of dynamos, we’ve found the perfect place for you. This award-winning company may be newer, but the combined experience of their people is impressive. No doubt this is one of the many reasons their AI recruitment marketing business has taken off! You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (153 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 149 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming Perl 🐪 Weekly #752 - Marlin - OOP Framework # perl # news # programming 💎 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:48:42 |
https://dev.to/t/mentalhealth/page/8 | Mental Health Page 8 - 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 Mental Health Follow Hide Mental health matters! Break the stigma. We can empower ourselves and each other to invest in our mental health. We can give support and care to ourselves and each other while we struggle. Let's talk about making our mental health priority. Create Post about #mentalhealth Posts should be related to mental health. This is a pretty wide category but some things that are included are: Managing mental health as a developer Living with mental illness and how it affects your work Ways to cope with mental health issues Avoiding burn out Tools, apps, and methods that help you with your mental health ...and more “Your mental health is a priority. Your happiness is an essential. Your self-care is a necessity.” Struggling? Help is out there. Click here to find a list of global mental health resources and hotlines. Older #mentalhealth posts 5 6 7 8 9 10 11 12 13 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu AI Chatbots and Mental Health: The Hidden Crisis Developers Need to Know shiva shanker shiva shanker shiva shanker Follow Sep 8 '25 AI Chatbots and Mental Health: The Hidden Crisis Developers Need to Know # ethics # mentalhealth # psychology # usersafety 40 reactions Comments 1 comment 3 min read 🧠 Breaking Negative Thinking Patterns with Cognitive Behavioral Therapy (CBT): A Practical Guide NVelUp NVelUp NVelUp Follow Sep 6 '25 🧠 Breaking Negative Thinking Patterns with Cognitive Behavioral Therapy (CBT): A Practical Guide # mentalhealth # productivity # cbt # selfimprovement 1 reaction Comments Add Comment 3 min read Life’s Answers Are Only Visible in Hindsight (Bite-size Article) koshirok096 koshirok096 koshirok096 Follow Aug 1 '25 Life’s Answers Are Only Visible in Hindsight (Bite-size Article) # mentalhealth Comments Add Comment 2 min read Is Burnout Inevitable in the World of Tech? Let's Talk About It Cesar Aguirre Cesar Aguirre Cesar Aguirre Follow Aug 25 '25 Is Burnout Inevitable in the World of Tech? Let's Talk About It # discuss # career # programming # mentalhealth 17 reactions Comments 8 comments 2 min read The Trigger… Sayman Lal Sayman Lal Sayman Lal Follow Jul 29 '25 The Trigger… # developer # lifeexperience # motivation # mentalhealth 1 reaction Comments Add Comment 1 min read Zeigarnik Effect (Bite-size Article) koshirok096 koshirok096 koshirok096 Follow Jul 25 '25 Zeigarnik Effect (Bite-size Article) # productivity # mentalhealth 1 reaction Comments Add Comment 4 min read Дефицит железа у разработчиков: Невидимый баг производительности 🐛 Sport Store Sport Store Sport Store Follow Jul 24 '25 Дефицит железа у разработчиков: Невидимый баг производительности 🐛 # mentalhealth # supplements # ionic # programming Comments Add Comment 1 min read HEY!! Don't Burnout 🤗 David James David James David James Follow Aug 18 '25 HEY!! Don't Burnout 🤗 # webdev # mentalhealth # workplace # career Comments 1 comment 2 min read Doom Vibe Coding: How AI is Changing the Way We Work—and Think BeFede BeFede BeFede Follow Aug 13 '25 Doom Vibe Coding: How AI is Changing the Way We Work—and Think # ai # programming # productivity # mentalhealth 1 reaction Comments Add Comment 5 min read Why Meditation Matters More Than You Think Jorge Sequeira Jorge Sequeira Jorge Sequeira Follow Aug 13 '25 Why Meditation Matters More Than You Think # psychology # mentalhealth # productivity # science 1 reaction Comments Add Comment 5 min read From Economics to Engineering My Future — Day Two of the Journey Slobodan Jevtić Slobodan Jevtić Slobodan Jevtić Follow Jul 7 '25 From Economics to Engineering My Future — Day Two of the Journey # python # coding # 100daysofcode # mentalhealth Comments Add Comment 1 min read Day Two – Sleep Tracker Tab Built and Working Slobodan Jevtić Slobodan Jevtić Slobodan Jevtić Follow Jul 7 '25 Day Two – Sleep Tracker Tab Built and Working # programming # 100daysofcode # python # mentalhealth 1 reaction Comments Add Comment 2 min read Data Privacy in AI Mental Health Tools: What You Should Know bvanderbilt0033 bvanderbilt0033 bvanderbilt0033 Follow Jul 3 '25 Data Privacy in AI Mental Health Tools: What You Should Know # mental # health # mentalhealth # mentalhealthtools Comments Add Comment 4 min read Building an AI Health Platform That Could Save the NHS £8.5M+ Annually shiva shanker shiva shanker shiva shanker Follow Aug 4 '25 Building an AI Health Platform That Could Save the NHS £8.5M+ Annually # healthydebate # mentalhealth # uk # software 16 reactions Comments 2 comments 3 min read Build Something You Can Eat: Raised Garden Beds for Devs potager project potager project potager project Follow Jul 1 '25 Build Something You Can Eat: Raised Garden Beds for Devs # sideprojects # gardeningfordevelopers # sustainability # mentalhealth Comments Add Comment 1 min read Hello...Just Wondering If There Are Others Out There Like Me? Ivan Krause Ivan Krause Ivan Krause Follow Jun 29 '25 Hello...Just Wondering If There Are Others Out There Like Me? # intro # devlife # mentalhealth # ireland Comments Add Comment 1 min read Why I’m All In on Burnout Prevention and What I’m Building with DustOff Reset Gaofenngwe Kabubi Gaofenngwe Kabubi Gaofenngwe Kabubi Follow Jun 28 '25 Why I’m All In on Burnout Prevention and What I’m Building with DustOff Reset # founder # burnout # ai # mentalhealth Comments Add Comment 2 min read The Ones Who Tried, and Disappeared Anyway versiqcontent versiqcontent versiqcontent Follow Jun 24 '25 The Ones Who Tried, and Disappeared Anyway # discuss # mentalhealth # community # coding 1 reaction Comments Add Comment 1 min read Sundays Are My AI Recharge Day Accio by Alibaba Group Accio by Alibaba Group Accio by Alibaba Group Follow Jul 27 '25 Sundays Are My AI Recharge Day # mentalhealth Comments Add Comment 1 min read Book reflection: 5 killer habits be a rebel Ansu Shaw Ansu Shaw Ansu Shaw Follow Jul 25 '25 Book reflection: 5 killer habits be a rebel # kindnessisstrength # books # mentalhealth # emotionalwellbeing Comments Add Comment 2 min read Organizing Your “Mental Logs”: A Meditation Approach That Turns Distractions Into Allies (Bite-size Article) koshirok096 koshirok096 koshirok096 Follow Jun 20 '25 Organizing Your “Mental Logs”: A Meditation Approach That Turns Distractions Into Allies (Bite-size Article) # mentalhealth # productivity Comments Add Comment 4 min read Building Slurp: A Fruit-Themed AI Mood Tracker with Supabase and Next.js Arka Arka Arka Follow Jun 20 '25 Building Slurp: A Fruit-Themed AI Mood Tracker with Supabase and Next.js # mentalhealth # webdev # ai Comments Add Comment 2 min read 🚀 How Kiro Helped Me Build BreezaAI – an AI Mental Wellness Tutor in Record Time Miiu Miiu Miiu Follow Jul 23 '25 🚀 How Kiro Helped Me Build BreezaAI – an AI Mental Wellness Tutor in Record Time # kiro # hackathon # mentalhealth # ai 3 reactions Comments 1 comment 2 min read How Social Media Subconsciously Controls Your Mind: An Academic Review on Dopamine, FOMO & Algorithms Sarthak Wakade Sarthak Wakade Sarthak Wakade Follow Jul 20 '25 How Social Media Subconsciously Controls Your Mind: An Academic Review on Dopamine, FOMO & Algorithms # socialmedia # mentalhealth # algorithms # psychology 6 reactions Comments 1 comment 4 min read Beating the Monday Blues as a CTO (Without Losing Your Mind) Akshay Joshi Akshay Joshi Akshay Joshi Follow Jun 16 '25 Beating the Monday Blues as a CTO (Without Losing Your Mind) # productivity # leadership # mentalhealth # workculture 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:48:42 |
https://docs.suprsend.com/reference/cli-translation-commit | Commit Translations - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Translation Commit Translations Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Translation Commit Translations OpenAI Open in ChatGPT Commit translations to make them live in the workspace OpenAI Open in ChatGPT This command will make translation changes live. You don’t need to run this command if you already used the --commit=true flag with the translation push command. Syntax Copy Ask AI suprsend translation commit [flags] Flags Flag Description Default -h, --help Show help for the command – -m, --commit-message string The commit message for the translation – Example Copy Ask AI # Commit translations in staging workspace (default) suprsend translation commit # Commit translations in production workspace suprsend translation commit --workspace production # Commit translations with a descriptive message suprsend translation commit --commit-message "Updated all French translations" Was this page helpful? Yes No Suggest edits Raise issue Previous Push Translations Push translations from local directory to SuprSend ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example | 2026-01-13T08:48:42 |
https://docs.python.org/3/license.html#licenses-and-acknowledgements-for-incorporated-software | History and License — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents History and License History of the software Terms and conditions for accessing or otherwise using Python PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION Licenses and Acknowledgements for Incorporated Software Mersenne Twister Sockets Asynchronous socket services Cookie management Execution tracing UUencode and UUdecode functions XML Remote Procedure Calls test_epoll Select kqueue SipHash24 strtod and dtoa OpenSSL expat libffi zlib cfuhash libmpdec W3C C14N test suite mimalloc asyncio Global Unbounded Sequences (GUS) Zstandard bindings Previous topic Copyright This page Report a bug Show source Navigation index modules | previous | Python » 3.14.2 Documentation » History and License | Theme Auto Light Dark | History and License ¶ History of the software ¶ Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see https://www.cwi.nl ) in the Netherlands as a successor of a language called ABC. Guido remains Python’s principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see https://www.cnri.reston.va.us ) in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations, which became Zope Corporation. In 2001, the Python Software Foundation (PSF, see https://www.python.org/psf/ ) was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation was a sponsoring member of the PSF. All Python releases are Open Source (see https://opensource.org for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the table below summarizes the various releases. Release Derived from Year Owner GPL-compatible? (1) 0.9.0 thru 1.2 n/a 1991-1995 CWI yes 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes 1.6 1.5.2 2000 CNRI no 2.0 1.6 2000 BeOpen.com no 1.6.1 1.6 2001 CNRI yes (2) 2.1 2.0+1.6.1 2001 PSF no 2.0.1 2.0+1.6.1 2001 PSF yes 2.1.1 2.1+2.0.1 2001 PSF yes 2.1.2 2.1.1 2002 PSF yes 2.1.3 2.1.2 2002 PSF yes 2.2 and above 2.1.1 2001-now PSF yes Note GPL-compatible doesn’t mean that we’re distributing Python under the GPL. All Python licenses, unlike the GPL, let you distribute a modified version without making your changes open source. The GPL-compatible licenses make it possible to combine Python with other software that is released under the GPL; the others don’t. According to Richard Stallman, 1.6.1 is not GPL-compatible, because its license has a choice of law clause. According to CNRI, however, Stallman’s lawyer has told CNRI’s lawyer that 1.6.1 is “not incompatible” with the GPL. Thanks to the many outside volunteers who have worked under Guido’s direction to make these releases possible. Terms and conditions for accessing or otherwise using Python ¶ Python software and documentation are licensed under the Python Software Foundation License Version 2. Starting with Python 3.8.6, examples, recipes, and other code in the documentation are dual licensed under the PSF License Version 2 and the Zero-Clause BSD license . Some software incorporated into Python is under different licenses. The licenses are listed with code falling under that license. See Licenses and Acknowledgements for Incorporated Software for an incomplete list of these licenses. PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 ¶ 1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright © 2001 Python Software Foundation; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee. 3. In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python. 4. PSF is making Python available to Licensee on an "AS IS" basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms and conditions of this License Agreement. BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 ¶ BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization ("Licensee") accessing and otherwise using this software in source or binary form and its associated documentation ("the Software"). 2. Subject to the terms and conditions of this BeOpen Python License Agreement, BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that the BeOpen Python License is retained in the Software, alone or in any derivative version prepared by Licensee. 3. BeOpen is making the Software available to Licensee on an "AS IS" basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 5. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 6. This License Agreement shall be governed by and interpreted in all respects by the law of the State of California, excluding conflict of law provisions. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between BeOpen and Licensee. This License Agreement does not grant permission to use BeOpen trademarks or trade names in a trademark sense to endorse or promote products or services of Licensee, or any third party. As an exception, the "BeOpen Python" logos available at http://www.pythonlabs.com/logos.html may be used according to the permissions granted on that web page. 7. By copying, installing or otherwise using the software, Licensee agrees to be bound by the terms and conditions of this License Agreement. CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 ¶ 1. This LICENSE AGREEMENT is between the Corporation for National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA 20191 ("CNRI"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 1.6.1 software in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 1.6.1 alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, i.e., "Copyright © 1995-2001 Corporation for National Research Initiatives; All Rights Reserved" are retained in Python 1.6.1 alone or in any derivative version prepared by Licensee. Alternately, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes): "Python 1.6.1 is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement together with Python 1.6.1 may be located on the internet using the following unique, persistent identifier (known as a handle): 1895.22/1013. This Agreement may also be obtained from a proxy server on the internet using the following URL: http://hdl.handle.net/1895.22/1013". 3. In the event Licensee prepares a derivative work that is based on or incorporates Python 1.6.1 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 1.6.1. 4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. This License Agreement shall be governed by the federal intellectual property law of the United States, including without limitation the federal copyright law, and, to the extent such U.S. federal law does not apply, by the law of the Commonwealth of Virginia, excluding Virginia's conflict of law provisions. Notwithstanding the foregoing, with regard to derivative works based on Python 1.6.1 that incorporate non-separable material that was previously distributed under the GNU General Public License (GPL), the law of the Commonwealth of Virginia shall govern this License Agreement only as to issues arising under or with respect to Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee. This License Agreement does not grant permission to use CNRI trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using Python 1.6.1, Licensee agrees to be bound by the terms and conditions of this License Agreement. CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ¶ Copyright © 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION ¶ Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Licenses and Acknowledgements for Incorporated Software ¶ This section is an incomplete, but growing list of licenses and acknowledgements for third-party software incorporated in the Python distribution. Mersenne Twister ¶ The _random C extension underlying the random module includes code based on a download from http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html . The following are the verbatim comments from the original code: A C-program for MT19937, with initialization improved 2002/1/26. Coded by Takuji Nishimura and Makoto Matsumoto. Before using, initialize the state by using init_genrand(seed) or init_by_array(init_key, key_length). Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura, All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The names of its contributors may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Any feedback is very welcome. http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html email: m-mat @ math.sci.hiroshima-u.ac.jp (remove space) Sockets ¶ The socket module uses the functions, getaddrinfo() , and getnameinfo() , which are coded in separate source files from the WIDE Project, https://www.wide.ad.jp/ . Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Asynchronous socket services ¶ The test.support.asynchat and test.support.asyncore modules contain the following notice: Copyright 1996 by Sam Rushing All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Sam Rushing not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Cookie management ¶ The http.cookies module contains the following notice: Copyright 2000 by Timothy O'Malley <timo@alum.mit.edu> All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Timothy O'Malley not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Execution tracing ¶ The trace module contains the following notice: portions copyright 2001, Autonomous Zones Industries, Inc., all rights... err... reserved and offered to the public under the terms of the Python 2.2 license. Author: Zooko O'Whielacronx http://zooko.com/ mailto:zooko@zooko.com Copyright 2000, Mojam Media, Inc., all rights reserved. Author: Skip Montanaro Copyright 1999, Bioreason, Inc., all rights reserved. Author: Andrew Dalke Copyright 1995-1997, Automatrix, Inc., all rights reserved. Author: Skip Montanaro Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved. Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of neither Automatrix, Bioreason or Mojam Media be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. UUencode and UUdecode functions ¶ The uu codec contains the following notice: Copyright 1994 by Lance Ellinghouse Cathedral City, California Republic, United States of America. All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Lance Ellinghouse not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Modified by Jack Jansen, CWI, July 1995: - Use binascii module to do the actual line-by-line conversion between ascii and binary. This results in a 1000-fold speedup. The C version is still 5 times faster, though. - Arguments more compliant with Python standard XML Remote Procedure Calls ¶ The xmlrpc.client module contains the following notice: The XML-RPC client interface is Copyright (c) 1999-2002 by Secret Labs AB Copyright (c) 1999-2002 by Fredrik Lundh By obtaining, using, and/or copying this software and/or its associated documentation, you agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, and distribute this software and its associated documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Secret Labs AB or the author not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT- ABILITY AND FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. test_epoll ¶ The test.test_epoll module contains the following notice: Copyright (c) 2001-2006 Twisted Matrix Laboratories. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Select kqueue ¶ The select module contains the following notice for the kqueue interface: Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SipHash24 ¶ The file Python/pyhash.c contains Marek Majkowski’ implementation of Dan Bernstein’s SipHash24 algorithm. It contains the following note: <MIT License> Copyright (c) 2013 Marek Majkowski <marek@popcount.org> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. </MIT License> Original location: https://github.com/majek/csiphash/ Solution inspired by code from: Samuel Neves (supercop/crypto_auth/siphash24/little) djb (supercop/crypto_auth/siphash24/little2) Jean-Philippe Aumasson (https://131002.net/siphash/siphash24.c) strtod and dtoa ¶ The file Python/dtoa.c , which supplies C functions dtoa and strtod for conversion of C doubles to and from strings, is derived from the file of the same name by David M. Gay, currently available from https://web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c . The original file, as retrieved on March 16, 2009, contains the following copyright and licensing notice: /**************************************************************** * * The author of this software is David M. Gay. * * Copyright (c) 1991, 2000, 2001 by Lucent Technologies. * * Permission to use, copy, modify, and distribute this software for any * purpose without fee is hereby granted, provided that this entire notice * is included in all copies of any software which is or includes a copy * or modification of this software and in all copies of the supporting * documentation for such software. * * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED * WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY * REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY * OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. * ***************************************************************/ OpenSSL ¶ The modules hashlib , posix and ssl use the OpenSSL library for added performance if made available by the operating system. Additionally, the Windows and macOS installers for Python may include a copy of the OpenSSL libraries, so we include a copy of the OpenSSL license here. For the OpenSSL 3.0 release, and later releases derived from that, the Apache License v2 applies: Apache License Version 2.0, January 2004 https://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS expat ¶ The pyexpat extension is built using an included copy of the expat sources unless the build is configured --with-system-expat : Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. libffi ¶ The _ctypes C extension underlying the ctypes module is built using an included copy of the libffi sources unless the build is configured --with-system-libffi : Copyright (c) 1996-2008 Red Hat, Inc and others. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. zlib ¶ The zlib extension is built using an included copy of the zlib sources if the zlib version found on the system is too old to be used for the build: Copyright (C) 1995-2011 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly Mark Adler jloup@gzip.org madler@alumni.caltech.edu cfuhash ¶ The implementation of the hash table used by the tracemalloc is based on the cfuhash project: Copyright (c) 2005 Don Owens All rights reserved. This code is released under the BSD license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. libmpdec ¶ The _decimal C extension underlying the decimal module is built using an included copy of the libmpdec library unless the build is configured --with-system-libmpdec : Copyright (c) 2008-2020 Stefan Krah. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. W3C C14N test suite ¶ The C14N 2.0 test suite in the test package ( Lib/test/xmltestdata/c14n-20/ ) was retrieved from the W3C website at https://www.w3.org/TR/xml-c14n2-testcases/ and is distributed under the 3-clause BSD license: Copyright (c) 2013 W3C(R) (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of works must retain the original copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the original copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the W3C nor the names of its contributors may be used to endorse or promote products derived from this work without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. mimalloc ¶ MIT License: Copyright (c) 2018-2021 Microsoft Corporation, Daan Leijen Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. asyncio ¶ Parts of the asyncio module are incorporated from uvloop 0.16 , which is distributed under the MIT license: Copyright (c) 2015-2021 MagicStack Inc. http://magic.io Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Global Unbounded Sequences (GUS) ¶ The file Python/qsbr.c is adapted from FreeBSD’s “Global Unbounded Sequences” safe memory reclamation scheme in subr_smr.c . The file is distributed under the 2-Clause BSD License: Copyright (c) 2019,2020 Jeffrey Roberson <jeff@FreeBSD.org> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following con | 2026-01-13T08:48:42 |
https://docs.suprsend.com/docs/integrate-go-sdk#content-area | Integrate Go SDK - 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 Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Node.js SDK Java SDK Go SDK Integrate Go SDK Manage Users Send and Track Events Trigger Workflow from API Tenants Lists Broadcast SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Go SDK Integrate Go SDK Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Go SDK Integrate Go SDK OpenAI Open in ChatGPT Install & Initialize SuprSend Go SDK using your workspace credentials for sending notifications. OpenAI Open in ChatGPT Installation Install suprsend-go sdk bash Copy Ask AI go get github.com/suprsend/suprsend-go Initialization For initializing SDK, you need workspace_key and workspace_secret. You will get both the tokens from your Suprsend dashboard (Developers -> API Keys). Request Copy Ask AI package main import ( " log " suprsend " github.com/suprsend/suprsend-go " ) // Initialize SDK func main () { opts := [] suprsend . ClientOption { // suprsend.WithDebug(true), } suprClient , err := suprsend . NewClient ( "__workspace_key__" , "__workspace_secret__" , opts ... ) if err != nil { log . Println ( err ) } } Was this page helpful? Yes No Suggest edits Raise issue Previous Manage Users Manage user profiles and communication channels programmatically with the Go SDK. Next ⌘ I x github linkedin youtube Powered by On this page Installation Initialization | 2026-01-13T08:48:42 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fthekarlesi%2Fhow-to-handle-stripe-and-paystack-webhooks-in-nextjs-the-app-router-way-5bgi&title=How%20to%20Handle%20Stripe%20and%20Paystack%20Webhooks%20in%20Next.js%20%28The%20App%20Router%20Way%29&summary=The%20%231%20reason%20developers%20struggle%20with%20SaaS%20payments%20is%20Webhook%20Signature%20Verification.%20You%20set...&source=DEV%20Community | LinkedIn {"data":{"status":401},"included":[]} {"request":"/voyager/api/voyagerSegmentsDashChameleonConfig","status":401,"body":"bpr-guid-885826","method":"GET","headers":{"x-li-uuid":"AAZIQQ7BGwfw8xpkXBeUSg\u003D\u003D"}} {"data":{"status":401},"included":[]} {"request":"/voyager/api/voyagerLaunchpadDashLaunchpadViews?decorationId\u003Dcom.linkedin.voyager.dash.deco.launchpad.LaunchpadView-96\u0026launchpadContext\u003DTAKEOVER\u0026q\u003Dcontext","status":401,"body":"bpr-guid-885827","method":"GET","headers":{"x-li-uuid":"AAZIQQ7BGwfw8xpkXBeUSg\u003D\u003D"}} {"data":{"status":401},"included":[]} {"request":"/voyager/api/me","status":401,"body":"bpr-guid-885828","method":"GET","headers":{"x-li-uuid":"AAZIQQ7BGwfw8xpkXBeUSg\u003D\u003D"}} {"data":{"status":401},"included":[]} {"request":"/voyager/api/premium/featureAccess?name\u003DreactivationFeaturesEligible","status":401,"body":"bpr-guid-885829","method":"GET","headers":{"x-li-uuid":"AAZIQQ7BGwfw8xpkXBeUSg\u003D\u003D"}} urn:li:page:d_UNKNOWN_ROUTE_inshare-redirect;f5f6dfbc-cc01-44c9-9217-a2bd248ef478 | 2026-01-13T08:48:42 |
https://docs.python.org/3/library/stdtypes.html#str | Built-in Types — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents Built-in Types Truth Value Testing Boolean Operations — and , or , not Comparisons Numeric Types — int , float , complex Bitwise Operations on Integer Types Additional Methods on Integer Types Additional Methods on Float Additional Methods on Complex Hashing of numeric types Boolean Type - bool Iterator Types Generator Types Sequence Types — list , tuple , range Common Sequence Operations Immutable Sequence Types Mutable Sequence Types Lists Tuples Ranges Text and Binary Sequence Type Methods Summary Text Sequence Type — str String Methods Formatted String Literals (f-strings) Debug specifier Conversion specifier Format specifier Template String Literals (t-strings) printf -style String Formatting Binary Sequence Types — bytes , bytearray , memoryview Bytes Objects Bytearray Objects Bytes and Bytearray Operations printf -style Bytes Formatting Memory Views Set Types — set , frozenset Mapping Types — dict Dictionary view objects Context Manager Types Type Annotation Types — Generic Alias , Union Generic Alias Type Standard Generic Classes Special Attributes of GenericAlias objects Union Type Other Built-in Types Modules Classes and Class Instances Functions Methods Code Objects Type Objects The Null Object The Ellipsis Object The NotImplemented Object Internal Objects Special Attributes Integer string conversion length limitation Affected APIs Configuring the limit Recommended configuration Previous topic Built-in Constants Next topic Built-in Exceptions This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Standard Library » Built-in Types | Theme Auto Light Dark | Built-in Types ¶ The following sections describe the standard types that are built into the interpreter. The principal built-in types are numerics, sequences, mappings, classes, instances and exceptions. Some collection classes are mutable. The methods that add, subtract, or rearrange their members in place, and don’t return a specific item, never return the collection instance itself but None . Some operations are supported by several object types; in particular, practically all objects can be compared for equality, tested for truth value, and converted to a string (with the repr() function or the slightly different str() function). The latter function is implicitly used when an object is written by the print() function. Truth Value Testing ¶ Any object can be tested for truth value, for use in an if or while condition or as operand of the Boolean operations below. By default, an object is considered true unless its class defines either a __bool__() method that returns False or a __len__() method that returns zero, when called with the object. [ 1 ] If one of the methods raises an exception when called, the exception is propagated and the object does not have a truth value (for example, NotImplemented ). Here are most of the built-in objects considered false: constants defined to be false: None and False zero of any numeric type: 0 , 0.0 , 0j , Decimal(0) , Fraction(0, 1) empty sequences and collections: '' , () , [] , {} , set() , range(0) Operations and built-in functions that have a Boolean result always return 0 or False for false and 1 or True for true, unless otherwise stated. (Important exception: the Boolean operations or and and always return one of their operands.) Boolean Operations — and , or , not ¶ These are the Boolean operations, ordered by ascending priority: Operation Result Notes x or y if x is true, then x , else y (1) x and y if x is false, then x , else y (2) not x if x is false, then True , else False (3) Notes: This is a short-circuit operator, so it only evaluates the second argument if the first one is false. This is a short-circuit operator, so it only evaluates the second argument if the first one is true. not has a lower priority than non-Boolean operators, so not a == b is interpreted as not (a == b) , and a == not b is a syntax error. Comparisons ¶ There are eight comparison operations in Python. They all have the same priority (which is higher than that of the Boolean operations). Comparisons can be chained arbitrarily; for example, x < y <= z is equivalent to x < y and y <= z , except that y is evaluated only once (but in both cases z is not evaluated at all when x < y is found to be false). This table summarizes the comparison operations: Operation Meaning < strictly less than <= less than or equal > strictly greater than >= greater than or equal == equal != not equal is object identity is not negated object identity Unless stated otherwise, objects of different types never compare equal. The == operator is always defined but for some object types (for example, class objects) is equivalent to is . The < , <= , > and >= operators are only defined where they make sense; for example, they raise a TypeError exception when one of the arguments is a complex number. Non-identical instances of a class normally compare as non-equal unless the class defines the __eq__() method. Instances of a class cannot be ordered with respect to other instances of the same class, or other types of object, unless the class defines enough of the methods __lt__() , __le__() , __gt__() , and __ge__() (in general, __lt__() and __eq__() are sufficient, if you want the conventional meanings of the comparison operators). The behavior of the is and is not operators cannot be customized; also they can be applied to any two objects and never raise an exception. Two more operations with the same syntactic priority, in and not in , are supported by types that are iterable or implement the __contains__() method. Numeric Types — int , float , complex ¶ There are three distinct numeric types: integers , floating-point numbers , and complex numbers . In addition, Booleans are a subtype of integers. Integers have unlimited precision. Floating-point numbers are usually implemented using double in C; information about the precision and internal representation of floating-point numbers for the machine on which your program is running is available in sys.float_info . Complex numbers have a real and imaginary part, which are each a floating-point number. To extract these parts from a complex number z , use z.real and z.imag . (The standard library includes the additional numeric types fractions.Fraction , for rationals, and decimal.Decimal , for floating-point numbers with user-definable precision.) Numbers are created by numeric literals or as the result of built-in functions and operators. Unadorned integer literals (including hex, octal and binary numbers) yield integers. Numeric literals containing a decimal point or an exponent sign yield floating-point numbers. Appending 'j' or 'J' to a numeric literal yields an imaginary number (a complex number with a zero real part) which you can add to an integer or float to get a complex number with real and imaginary parts. The constructors int() , float() , and complex() can be used to produce numbers of a specific type. Python fully supports mixed arithmetic: when a binary arithmetic operator has operands of different numeric types, the operand with the “narrower” type is widened to that of the other, where integer is narrower than floating point. Arithmetic with complex and real operands is defined by the usual mathematical formula, for example: x + complex ( u , v ) = complex ( x + u , v ) x * complex ( u , v ) = complex ( x * u , x * v ) A comparison between numbers of different types behaves as though the exact values of those numbers were being compared. [ 2 ] All numeric types (except complex) support the following operations (for priorities of the operations, see Operator precedence ): Operation Result Notes Full documentation x + y sum of x and y x - y difference of x and y x * y product of x and y x / y quotient of x and y x // y floored quotient of x and y (1)(2) x % y remainder of x / y (2) -x x negated +x x unchanged abs(x) absolute value or magnitude of x abs() int(x) x converted to integer (3)(6) int() float(x) x converted to floating point (4)(6) float() complex(re, im) a complex number with real part re , imaginary part im . im defaults to zero. (6) complex() c.conjugate() conjugate of the complex number c divmod(x, y) the pair (x // y, x % y) (2) divmod() pow(x, y) x to the power y (5) pow() x ** y x to the power y (5) Notes: Also referred to as integer division. For operands of type int , the result has type int . For operands of type float , the result has type float . In general, the result is a whole integer, though the result’s type is not necessarily int . The result is always rounded towards minus infinity: 1//2 is 0 , (-1)//2 is -1 , 1//(-2) is -1 , and (-1)//(-2) is 0 . Not for complex numbers. Instead convert to floats using abs() if appropriate. Conversion from float to int truncates, discarding the fractional part. See functions math.floor() and math.ceil() for alternative conversions. float also accepts the strings “nan” and “inf” with an optional prefix “+” or “-” for Not a Number (NaN) and positive or negative infinity. Python defines pow(0, 0) and 0 ** 0 to be 1 , as is common for programming languages. The numeric literals accepted include the digits 0 to 9 or any Unicode equivalent (code points with the Nd property). See the Unicode Standard for a complete list of code points with the Nd property. All numbers.Real types ( int and float ) also include the following operations: Operation Result math.trunc(x) x truncated to Integral round(x[, n]) x rounded to n digits, rounding half to even. If n is omitted, it defaults to 0. math.floor(x) the greatest Integral <= x math.ceil(x) the least Integral >= x For additional numeric operations see the math and cmath modules. Bitwise Operations on Integer Types ¶ Bitwise operations only make sense for integers. The result of bitwise operations is calculated as though carried out in two’s complement with an infinite number of sign bits. The priorities of the binary bitwise operations are all lower than the numeric operations and higher than the comparisons; the unary operation ~ has the same priority as the other unary numeric operations ( + and - ). This table lists the bitwise operations sorted in ascending priority: Operation Result Notes x | y bitwise or of x and y (4) x ^ y bitwise exclusive or of x and y (4) x & y bitwise and of x and y (4) x << n x shifted left by n bits (1)(2) x >> n x shifted right by n bits (1)(3) ~x the bits of x inverted Notes: Negative shift counts are illegal and cause a ValueError to be raised. A left shift by n bits is equivalent to multiplication by pow(2, n) . A right shift by n bits is equivalent to floor division by pow(2, n) . Performing these calculations with at least one extra sign extension bit in a finite two’s complement representation (a working bit-width of 1 + max(x.bit_length(), y.bit_length()) or more) is sufficient to get the same result as if there were an infinite number of sign bits. Additional Methods on Integer Types ¶ The int type implements the numbers.Integral abstract base class . In addition, it provides a few more methods: int. bit_length ( ) ¶ Return the number of bits necessary to represent an integer in binary, excluding the sign and leading zeros: >>> n = - 37 >>> bin ( n ) '-0b100101' >>> n . bit_length () 6 More precisely, if x is nonzero, then x.bit_length() is the unique positive integer k such that 2**(k-1) <= abs(x) < 2**k . Equivalently, when abs(x) is small enough to have a correctly rounded logarithm, then k = 1 + int(log(abs(x), 2)) . If x is zero, then x.bit_length() returns 0 . Equivalent to: def bit_length ( self ): s = bin ( self ) # binary representation: bin(-37) --> '-0b100101' s = s . lstrip ( '-0b' ) # remove leading zeros and minus sign return len ( s ) # len('100101') --> 6 Added in version 3.1. int. bit_count ( ) ¶ Return the number of ones in the binary representation of the absolute value of the integer. This is also known as the population count. Example: >>> n = 19 >>> bin ( n ) '0b10011' >>> n . bit_count () 3 >>> ( - n ) . bit_count () 3 Equivalent to: def bit_count ( self ): return bin ( self ) . count ( "1" ) Added in version 3.10. int. to_bytes ( length = 1 , byteorder = 'big' , * , signed = False ) ¶ Return an array of bytes representing an integer. >>> ( 1024 ) . to_bytes ( 2 , byteorder = 'big' ) b'\x04\x00' >>> ( 1024 ) . to_bytes ( 10 , byteorder = 'big' ) b'\x00\x00\x00\x00\x00\x00\x00\x00\x04\x00' >>> ( - 1024 ) . to_bytes ( 10 , byteorder = 'big' , signed = True ) b'\xff\xff\xff\xff\xff\xff\xff\xff\xfc\x00' >>> x = 1000 >>> x . to_bytes (( x . bit_length () + 7 ) // 8 , byteorder = 'little' ) b'\xe8\x03' The integer is represented using length bytes, and defaults to 1. An OverflowError is raised if the integer is not representable with the given number of bytes. The byteorder argument determines the byte order used to represent the integer, and defaults to "big" . If byteorder is "big" , the most significant byte is at the beginning of the byte array. If byteorder is "little" , the most significant byte is at the end of the byte array. The signed argument determines whether two’s complement is used to represent the integer. If signed is False and a negative integer is given, an OverflowError is raised. The default value for signed is False . The default values can be used to conveniently turn an integer into a single byte object: >>> ( 65 ) . to_bytes () b'A' However, when using the default arguments, don’t try to convert a value greater than 255 or you’ll get an OverflowError . Equivalent to: def to_bytes ( n , length = 1 , byteorder = 'big' , signed = False ): if byteorder == 'little' : order = range ( length ) elif byteorder == 'big' : order = reversed ( range ( length )) else : raise ValueError ( "byteorder must be either 'little' or 'big'" ) return bytes (( n >> i * 8 ) & 0xff for i in order ) Added in version 3.2. Changed in version 3.11: Added default argument values for length and byteorder . classmethod int. from_bytes ( bytes , byteorder = 'big' , * , signed = False ) ¶ Return the integer represented by the given array of bytes. >>> int . from_bytes ( b ' \x00\x10 ' , byteorder = 'big' ) 16 >>> int . from_bytes ( b ' \x00\x10 ' , byteorder = 'little' ) 4096 >>> int . from_bytes ( b ' \xfc\x00 ' , byteorder = 'big' , signed = True ) -1024 >>> int . from_bytes ( b ' \xfc\x00 ' , byteorder = 'big' , signed = False ) 64512 >>> int . from_bytes ([ 255 , 0 , 0 ], byteorder = 'big' ) 16711680 The argument bytes must either be a bytes-like object or an iterable producing bytes. The byteorder argument determines the byte order used to represent the integer, and defaults to "big" . If byteorder is "big" , the most significant byte is at the beginning of the byte array. If byteorder is "little" , the most significant byte is at the end of the byte array. To request the native byte order of the host system, use sys.byteorder as the byte order value. The signed argument indicates whether two’s complement is used to represent the integer. Equivalent to: def from_bytes ( bytes , byteorder = 'big' , signed = False ): if byteorder == 'little' : little_ordered = list ( bytes ) elif byteorder == 'big' : little_ordered = list ( reversed ( bytes )) else : raise ValueError ( "byteorder must be either 'little' or 'big'" ) n = sum ( b << i * 8 for i , b in enumerate ( little_ordered )) if signed and little_ordered and ( little_ordered [ - 1 ] & 0x80 ): n -= 1 << 8 * len ( little_ordered ) return n Added in version 3.2. Changed in version 3.11: Added default argument value for byteorder . int. as_integer_ratio ( ) ¶ Return a pair of integers whose ratio is equal to the original integer and has a positive denominator. The integer ratio of integers (whole numbers) is always the integer as the numerator and 1 as the denominator. Added in version 3.8. int. is_integer ( ) ¶ Returns True . Exists for duck type compatibility with float.is_integer() . Added in version 3.12. Additional Methods on Float ¶ The float type implements the numbers.Real abstract base class . float also has the following additional methods. classmethod float. from_number ( x ) ¶ Class method to return a floating-point number constructed from a number x . If the argument is an integer or a floating-point number, a floating-point number with the same value (within Python’s floating-point precision) is returned. If the argument is outside the range of a Python float, an OverflowError will be raised. For a general Python object x , float.from_number(x) delegates to x.__float__() . If __float__() is not defined then it falls back to __index__() . Added in version 3.14. float. as_integer_ratio ( ) ¶ Return a pair of integers whose ratio is exactly equal to the original float. The ratio is in lowest terms and has a positive denominator. Raises OverflowError on infinities and a ValueError on NaNs. float. is_integer ( ) ¶ Return True if the float instance is finite with integral value, and False otherwise: >>> ( - 2.0 ) . is_integer () True >>> ( 3.2 ) . is_integer () False Two methods support conversion to and from hexadecimal strings. Since Python’s floats are stored internally as binary numbers, converting a float to or from a decimal string usually involves a small rounding error. In contrast, hexadecimal strings allow exact representation and specification of floating-point numbers. This can be useful when debugging, and in numerical work. float. hex ( ) ¶ Return a representation of a floating-point number as a hexadecimal string. For finite floating-point numbers, this representation will always include a leading 0x and a trailing p and exponent. classmethod float. fromhex ( s ) ¶ Class method to return the float represented by a hexadecimal string s . The string s may have leading and trailing whitespace. Note that float.hex() is an instance method, while float.fromhex() is a class method. A hexadecimal string takes the form: [ sign ] [ '0x' ] integer [ '.' fraction ] [ 'p' exponent ] where the optional sign may by either + or - , integer and fraction are strings of hexadecimal digits, and exponent is a decimal integer with an optional leading sign. Case is not significant, and there must be at least one hexadecimal digit in either the integer or the fraction. This syntax is similar to the syntax specified in section 6.4.4.2 of the C99 standard, and also to the syntax used in Java 1.5 onwards. In particular, the output of float.hex() is usable as a hexadecimal floating-point literal in C or Java code, and hexadecimal strings produced by C’s %a format character or Java’s Double.toHexString are accepted by float.fromhex() . Note that the exponent is written in decimal rather than hexadecimal, and that it gives the power of 2 by which to multiply the coefficient. For example, the hexadecimal string 0x3.a7p10 represents the floating-point number (3 + 10./16 + 7./16**2) * 2.0**10 , or 3740.0 : >>> float . fromhex ( '0x3.a7p10' ) 3740.0 Applying the reverse conversion to 3740.0 gives a different hexadecimal string representing the same number: >>> float . hex ( 3740.0 ) '0x1.d380000000000p+11' Additional Methods on Complex ¶ The complex type implements the numbers.Complex abstract base class . complex also has the following additional methods. classmethod complex. from_number ( x ) ¶ Class method to convert a number to a complex number. For a general Python object x , complex.from_number(x) delegates to x.__complex__() . If __complex__() is not defined then it falls back to __float__() . If __float__() is not defined then it falls back to __index__() . Added in version 3.14. Hashing of numeric types ¶ For numbers x and y , possibly of different types, it’s a requirement that hash(x) == hash(y) whenever x == y (see the __hash__() method documentation for more details). For ease of implementation and efficiency across a variety of numeric types (including int , float , decimal.Decimal and fractions.Fraction ) Python’s hash for numeric types is based on a single mathematical function that’s defined for any rational number, and hence applies to all instances of int and fractions.Fraction , and all finite instances of float and decimal.Decimal . Essentially, this function is given by reduction modulo P for a fixed prime P . The value of P is made available to Python as the modulus attribute of sys.hash_info . CPython implementation detail: Currently, the prime used is P = 2**31 - 1 on machines with 32-bit C longs and P = 2**61 - 1 on machines with 64-bit C longs. Here are the rules in detail: If x = m / n is a nonnegative rational number and n is not divisible by P , define hash(x) as m * invmod(n, P) % P , where invmod(n, P) gives the inverse of n modulo P . If x = m / n is a nonnegative rational number and n is divisible by P (but m is not) then n has no inverse modulo P and the rule above doesn’t apply; in this case define hash(x) to be the constant value sys.hash_info.inf . If x = m / n is a negative rational number define hash(x) as -hash(-x) . If the resulting hash is -1 , replace it with -2 . The particular values sys.hash_info.inf and -sys.hash_info.inf are used as hash values for positive infinity or negative infinity (respectively). For a complex number z , the hash values of the real and imaginary parts are combined by computing hash(z.real) + sys.hash_info.imag * hash(z.imag) , reduced modulo 2**sys.hash_info.width so that it lies in range(-2**(sys.hash_info.width - 1), 2**(sys.hash_info.width - 1)) . Again, if the result is -1 , it’s replaced with -2 . To clarify the above rules, here’s some example Python code, equivalent to the built-in hash, for computing the hash of a rational number, float , or complex : import sys , math def hash_fraction ( m , n ): """Compute the hash of a rational number m / n. Assumes m and n are integers, with n positive. Equivalent to hash(fractions.Fraction(m, n)). """ P = sys . hash_info . modulus # Remove common factors of P. (Unnecessary if m and n already coprime.) while m % P == n % P == 0 : m , n = m // P , n // P if n % P == 0 : hash_value = sys . hash_info . inf else : # Fermat's Little Theorem: pow(n, P-1, P) is 1, so # pow(n, P-2, P) gives the inverse of n modulo P. hash_value = ( abs ( m ) % P ) * pow ( n , P - 2 , P ) % P if m < 0 : hash_value = - hash_value if hash_value == - 1 : hash_value = - 2 return hash_value def hash_float ( x ): """Compute the hash of a float x.""" if math . isnan ( x ): return object . __hash__ ( x ) elif math . isinf ( x ): return sys . hash_info . inf if x > 0 else - sys . hash_info . inf else : return hash_fraction ( * x . as_integer_ratio ()) def hash_complex ( z ): """Compute the hash of a complex number z.""" hash_value = hash_float ( z . real ) + sys . hash_info . imag * hash_float ( z . imag ) # do a signed reduction modulo 2**sys.hash_info.width M = 2 ** ( sys . hash_info . width - 1 ) hash_value = ( hash_value & ( M - 1 )) - ( hash_value & M ) if hash_value == - 1 : hash_value = - 2 return hash_value Boolean Type - bool ¶ Booleans represent truth values. The bool type has exactly two constant instances: True and False . The built-in function bool() converts any value to a boolean, if the value can be interpreted as a truth value (see section Truth Value Testing above). For logical operations, use the boolean operators and , or and not . When applying the bitwise operators & , | , ^ to two booleans, they return a bool equivalent to the logical operations “and”, “or”, “xor”. However, the logical operators and , or and != should be preferred over & , | and ^ . Deprecated since version 3.12: The use of the bitwise inversion operator ~ is deprecated and will raise an error in Python 3.16. bool is a subclass of int (see Numeric Types — int, float, complex ). In many numeric contexts, False and True behave like the integers 0 and 1, respectively. However, relying on this is discouraged; explicitly convert using int() instead. Iterator Types ¶ Python supports a concept of iteration over containers. This is implemented using two distinct methods; these are used to allow user-defined classes to support iteration. Sequences, described below in more detail, always support the iteration methods. One method needs to be defined for container objects to provide iterable support: container. __iter__ ( ) ¶ Return an iterator object. The object is required to support the iterator protocol described below. If a container supports different types of iteration, additional methods can be provided to specifically request iterators for those iteration types. (An example of an object supporting multiple forms of iteration would be a tree structure which supports both breadth-first and depth-first traversal.) This method corresponds to the tp_iter slot of the type structure for Python objects in the Python/C API. The iterator objects themselves are required to support the following two methods, which together form the iterator protocol : iterator. __iter__ ( ) ¶ Return the iterator object itself. This is required to allow both containers and iterators to be used with the for and in statements. This method corresponds to the tp_iter slot of the type structure for Python objects in the Python/C API. iterator. __next__ ( ) ¶ Return the next item from the iterator . If there are no further items, raise the StopIteration exception. This method corresponds to the tp_iternext slot of the type structure for Python objects in the Python/C API. Python defines several iterator objects to support iteration over general and specific sequence types, dictionaries, and other more specialized forms. The specific types are not important beyond their implementation of the iterator protocol. Once an iterator’s __next__() method raises StopIteration , it must continue to do so on subsequent calls. Implementations that do not obey this property are deemed broken. Generator Types ¶ Python’s generator s provide a convenient way to implement the iterator protocol. If a container object’s __iter__() method is implemented as a generator, it will automatically return an iterator object (technically, a generator object) supplying the __iter__() and __next__() methods. More information about generators can be found in the documentation for the yield expression . Sequence Types — list , tuple , range ¶ There are three basic sequence types: lists, tuples, and range objects. Additional sequence types tailored for processing of binary data and text strings are described in dedicated sections. Common Sequence Operations ¶ The operations in the following table are supported by most sequence types, both mutable and immutable. The collections.abc.Sequence ABC is provided to make it easier to correctly implement these operations on custom sequence types. This table lists the sequence operations sorted in ascending priority. In the table, s and t are sequences of the same type, n , i , j and k are integers and x is an arbitrary object that meets any type and value restrictions imposed by s . The in and not in operations have the same priorities as the comparison operations. The + (concatenation) and * (repetition) operations have the same priority as the corresponding numeric operations. [ 3 ] Operation Result Notes x in s True if an item of s is equal to x , else False (1) x not in s False if an item of s is equal to x , else True (1) s + t the concatenation of s and t (6)(7) s * n or n * s equivalent to adding s to itself n times (2)(7) s[i] i th item of s , origin 0 (3)(8) s[i:j] slice of s from i to j (3)(4) s[i:j:k] slice of s from i to j with step k (3)(5) len(s) length of s min(s) smallest item of s max(s) largest item of s Sequences of the same type also support comparisons. In particular, tuples and lists are compared lexicographically by comparing corresponding elements. This means that to compare equal, every element must compare equal and the two sequences must be of the same type and have the same length. (For full details see Comparisons in the language reference.) Forward and reversed iterators over mutable sequences access values using an index. That index will continue to march forward (or backward) even if the underlying sequence is mutated. The iterator terminates only when an IndexError or a StopIteration is encountered (or when the index drops below zero). Notes: While the in and not in operations are used only for simple containment testing in the general case, some specialised sequences (such as str , bytes and bytearray ) also use them for subsequence testing: >>> "gg" in "eggs" True Values of n less than 0 are treated as 0 (which yields an empty sequence of the same type as s ). Note that items in the sequence s are not copied; they are referenced multiple times. This often haunts new Python programmers; consider: >>> lists = [[]] * 3 >>> lists [[], [], []] >>> lists [ 0 ] . append ( 3 ) >>> lists [[3], [3], [3]] What has happened is that [[]] is a one-element list containing an empty list, so all three elements of [[]] * 3 are references to this single empty list. Modifying any of the elements of lists modifies this single list. You can create a list of different lists this way: >>> lists = [[] for i in range ( 3 )] >>> lists [ 0 ] . append ( 3 ) >>> lists [ 1 ] . append ( 5 ) >>> lists [ 2 ] . append ( 7 ) >>> lists [[3], [5], [7]] Further explanation is available in the FAQ entry How do I create a multidimensional list? . If i or j is negative, the index is relative to the end of sequence s : len(s) + i or len(s) + j is substituted. But note that -0 is still 0 . The slice of s from i to j is defined as the sequence of items with index k such that i <= k < j . If i is omitted or None , use 0 . If j is omitted or None , use len(s) . If i or j is less than -len(s) , use 0 . If i or j is greater than len(s) , use len(s) . If i is greater than or equal to j , the slice is empty. The slice of s from i to j with step k is defined as the sequence of items with index x = i + n*k such that 0 <= n < (j-i)/k . In other words, the indices are i , i+k , i+2*k , i+3*k and so on, stopping when j is reached (but never including j ). When k is positive, i and j are reduced to len(s) if they are greater. When k is negative, i and j are reduced to len(s) - 1 if they are greater. If i or j are omitted or None , they become “end” values (which end depends on the sign of k ). Note, k cannot be zero. If k is None , it is treated like 1 . Concatenating immutable sequences always results in a new object. This means that building up a sequence by repeated concatenation will have a quadratic runtime cost in the total sequence length. To get a linear runtime cost, you must switch to one of the alternatives below: if concatenating str objects, you can build a list and use str.join() at the end or else write to an io.StringIO instance and retrieve its value when complete if concatenating bytes objects, you can similarly use bytes.join() or io.BytesIO , or you can do in-place concatenation with a bytearray object. bytearray objects are mutable and have an efficient overallocation mechanism if concatenating tuple objects, extend a list instead for other types, investigate the relevant class documentation Some sequence types (such as range ) only support item sequences that follow specific patterns, and hence don’t support sequence concatenation or repetition. An IndexError is raised if i is outside the sequence range. Sequence Methods Sequence types also support the following methods: sequence. count ( value , / ) ¶ Return the total number of occurrences of value in sequence . sequence. index ( value[, start[, stop] ) ¶ Return the index of the first occurrence of value in sequence . Raises ValueError if value is not found in sequence . The start or stop arguments allow for efficient searching of subsections of the sequence, beginning at start and ending at stop . This is roughly equivalent to start + sequence[start:stop].index(value) , only without copying any data. Caution Not all sequence types support passing the start and stop arguments. Immutable Sequence Types ¶ The only operation that immutable sequence types generally implement that is not also implemented by mutable sequence types is support for the hash() built-in. This support allows immutable sequences, such as tuple instances, to be used as dict keys and stored in set and frozenset instances. Attempting to hash an immutable sequence that contains unhashable values will result in TypeError . Mutable Sequence Types ¶ The operations in the following table are defined on mutable sequence types. The collections.abc.MutableSequence ABC is provided to make it easier to correctly implement these operations on custom sequence types. In the table s is an instance of a mutable sequence type, t is any iterable object and x is an arbitrary object that meets any type and value restrictions imposed by s (for example, bytearray only accepts integers that meet the value restriction 0 <= x <= 255 ). Operation Result Notes s[i] = x item i of s is replaced by x del s[i] removes item i of s s[i:j] = t slice of s from i to j is replaced by the contents of the iterable t del s[i:j] removes the elements of s[i:j] from the list (same as s[i:j] = [] ) s[i:j:k] = t the elements of s[i:j:k] are replaced by those of t (1) del s[i:j:k] removes the elements of s[i:j:k] from the list s += t extends s with the contents of t (for the most part the same as s[len(s):len(s)] = t ) s *= n updates s with its contents repeated n times (2) Notes: If k is not equal to 1 , t must have the same length as the slice it is replacing. The value n is an integer, or an object implementing __index__() . Zero and negative values of n clear the sequence. Items in the sequence are not copied; they are referenced multiple times, as explained for s * n under Common Sequence Operations . Mutable Sequence Methods Mutable sequence types also support the following methods: sequence. append ( value , / ) ¶ Append value to the end of the sequence This is equivalent to writing seq[len(seq):len(seq)] = [value] . sequence. clear ( ) ¶ Added in version 3.3. Remove all items from sequence . This is equivalent to writing del sequence[:] . sequence. copy ( ) ¶ Added in version 3.3. Create a shallow copy of sequence . This is equivalent to writing sequence[:] . Hint The copy() method is not part of the MutableSequence ABC , but most concrete mutable sequence types provide it. sequence. extend ( iterable , / ) ¶ Extend sequence with the contents of iterable . For the most part, this is the same as writing seq[len(seq):len(seq)] = iterable . sequence. insert ( index , value , / ) ¶ Insert value into sequence at the given index . This is equivalent to writing sequence[index:index] = [value] . sequence. pop ( index = -1 , / ) ¶ Retrieve the item at index and also removes it from sequence . By default, the last item in sequence is removed and returned. sequence. remove ( value , / ) ¶ Remove the first item from sequence where sequence[i] == value . Raises ValueError if value is not found in sequence . sequence. reverse ( ) ¶ Reverse the items of sequence in place. This method maintains economy of space when reversing a large sequence. To remind users that it operates by side-effect, it returns None . Lists ¶ Lists are mutable sequences, typically used to store collections of homogeneous items (where the precise degree of similarity will vary by application). class list ( iterable = () , / ) ¶ Lists may be constructed in several ways: Using a pair of square brackets to denote the empty list: [] Using square brackets, separating items with commas: [a] , [a, b, c] Using a list comprehension: [x for x in iterable] Using the type constructor: list() or list(iterable) The constructor builds a list whose items are the same and in the same order as iterable ’s items. iterable may be either a sequence, a container that supports iteration, or an iterator object. If iterable is already a list, a copy is made and returned, similar to iterable[:] . For example, list('abc') returns ['a', 'b', 'c'] and list( (1, 2, 3) ) returns [1, 2, 3] . If no argument is given, the constructor creates a new empty list, [] . Many other operations also produce lists, including the sorted() built-in. Lists implement all of the common and mutable sequence operations. Lists also provide the following additional method: sort ( * , key = None , reverse = False ) ¶ This method sorts the list in place, using only < comparisons between items. Exceptions are not suppressed - if any comparison operations fail, the entire sort operation will fail (and the list will likely be left in a partially modified state). sort() accepts two arguments that can only be passed by keyword ( keyword-only arguments ): key specifies a function of one argument that is used to extract a comparison key from each list element (for example, key=str.lower ). The key corresponding to each item in the list is calculated once and then used for the entire sorting process. The default value of None means that list items are sorted directly without calculating a separate key value. The functools.cmp_to_key() utility is available to convert a 2.x style cmp function to a key function. reverse is a boolean value. If set to True , then the list elements are sorted as if each comparison were reversed. This method modifies the sequence in place for economy of space when sorting a large sequence. To remind users that it operates by side effect, it does not return the sorted sequence (use sorted() to explicitly request a new sorted list instance). The sort() method is guaranteed to be stable. A sort is stable if it guarantees not to change the relative order of elements that compare equal — this is helpful for sorting in multiple passes (for example, sort by department, then by salary grade). For sorting examples and a brief sorting tutorial, see Sorting Techniques . CPython implementation detail: While a list is being sorted, the effect of attempting to mutate, or even inspect, the list is undefined. The C implementation of Python makes the list appear empty for the duration, and raises ValueError if it can detect that the list has been mutated during a sort. Thread safety Reading a single element from a list is atomic : lst [ i ] # list.__getitem__ The following methods traverse the list and use atomic reads of each item to perform their function. That means that they may return results affected by concurrent modifications: item in lst lst . index ( item ) lst . count ( item ) All of the above methods/operations are also lock-free. They do not block concurrent modifications. Other operations that hold a lock will not block these from observing intermediate states. All other operations from here on block using the per-object lock. Writing a single item via lst[i] = x is safe to call from multiple threads and will not corrupt the list. The following operations return new objects and appear atomic to other threads: lst1 + lst2 # concatenates two lists into a new list x * lst # repeats lst x times into a new list lst . copy () # returns a shallow copy of the list Methods that only operate on a single elements with no shifting required are atomic : lst . append ( x ) # append to the end of the list, no shifting required lst . pop () # pop element from the end of the list, no shifting required The clear() method is also atomic . Other threads cannot observe elements being removed. The sort() method is not atomic . Other threads cannot observe intermediate states during sorting, but the list appears empty for the duration of the sort. The following operations may allow lock-free operations to observe intermediate states since they modify multiple elements in place: lst . insert ( idx , item ) # shifts elements lst . pop ( idx ) # idx not at the end of the list, shifts elements lst *= x # copies elements in place The remove() method may allow concurrent modifications since element comparison may execute arbitrary Python code (via __eq__() ). extend() is safe to call from multiple threads. However, its guarantees depend on the iterable passed to it. If it is a list , a tuple , a set , a frozenset , a dict or a dictionary view object (but not their subclasses), the extend operation is safe from concurrent modifications to the iterable. Otherwise, an iterator is created which can be concurrently modified by another thread. The same applies to inplace concatenation of a list with other iterables when using lst += iterable . Similarly, assigning to a list slice with lst[i:j] = iterable is safe to call from multiple threads, but iterable is only locked when it is also a list (but not its subclasses). Operations that involve multiple accesses, as well as iteration, are never atomic. For example: # NOT atomic: read-modify-write lst [ i ] = lst [ i ] + 1 # NOT atomic: check-then-act if lst : item = lst . pop () # NOT thread-safe: iteration while modifying for item in lst : process ( item ) # another thread may modify lst Consider external synchronization when sharing list instances across threads. See Python support for free threading for more information. Tuples ¶ Tuples are immutable sequences, typically used to store collections of heterogeneous data (such as the 2-tuples produced by the enumerate() built-in). Tuples are also used for cases where an immutable sequence of homogeneous data is needed (such as allowing storage in a set or dict instance). class tuple ( iterable = () , / ) ¶ Tuples may be constructed in a number of ways: Using a pair of parentheses to denote the empty tuple: () Using a trailing comma for a singleton tuple: a, or (a,) Separating items with commas: a, b, c or (a, b, c) Using the tuple() built-in: tuple() or tuple(iterable) The constructor builds a tuple whose items are the same and in the same order as iterable ’s items. iterable may be either a sequence, a container that supports iteration, or an iterator object. If iterable is already a tuple, it is returned unchanged. For example, tuple('abc') returns ('a', 'b', 'c') and tuple( [1, 2, 3] ) returns (1, 2, 3) . If no argument is given, the constructor creates a new empty tuple, () . Note that it is actually the comma which makes a tuple, not the parentheses. The parentheses are optional, except in the empty tuple case, or when they are needed to avoid syntactic ambiguity. For example, f(a, b, c) is a function call with three arguments, while f((a, b, c)) is a function call with a 3-tuple as the sole argument. Tuples implement all of the common sequence operations. For heterogeneous collections of data where access by name is clearer than access by index, collections.namedtuple() may be a more appropriate choice than a simple tuple object. Ranges ¶ The range type represents an immutable sequence of numbers and is commonly used for looping a specific number of times in for loops. class range ( stop , / ) ¶ class range ( start , stop , step = 1 , / ) The arguments to the range constructor must be integers (either built-in int or any object that implements the __index__() special method). If the step argument is omitted, it defaults to 1 . If the start argument is omitted, it defaults to 0 . If step is zero, ValueError is raised. For a positive step , the contents of a range r are determined by the formula r[i] = start + step*i where i >= 0 and r[i] < stop . For a negative step , the contents of the range are still determined by the formula r[i] = start + step*i , but the constraints are i >= 0 and r[i] > stop . A range object will be empty if r[0] does not meet the value constraint. Ranges do support negative indices, but these are interpreted as indexing from the end of the sequence determined by the positive indices. Ranges containing absolute values larger than sys.maxsize are permitted but some features (such as len() ) may raise OverflowError . Range examples: >>> list ( range ( 10 )) [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] >>> list ( range ( 1 , 11 )) [1, 2, 3, 4, 5, 6, 7, 8, 9, 10] >>> list ( range ( 0 , 30 , 5 )) [0, 5, 10, 15, 20, 25] >>> list ( range ( 0 , 10 , 3 )) [0, 3, 6, 9] >>> list ( range ( 0 , - 10 , - 1 )) [0, -1, -2, -3, -4, -5, -6, -7, -8, -9] >>> list ( range ( 0 )) [] >>> list ( range ( 1 , 0 )) [] Ranges implement all of the common sequence operations except concatenation and repetition (due to the fact that range objects can only represent sequences that follow a strict pattern and repetition and concatenation will usually violate that pattern). start ¶ The value of the start parameter (or 0 if the parameter was not supplied) stop ¶ The value of the stop parameter step ¶ The value of the step parameter (or 1 if the parameter was not supplied) The advantage of the range type over a regular list or tuple is that a range object will always take the same (small) amount of memory, no matter the size of the range it represents (as it only stores the start , stop and step values, calculating individual items and subranges as needed). Range objects implement the collections.abc.Sequence ABC, and provide features such as containment tests, element index lookup, slicing and support for negative indices (see Sequence Types — list, tuple, range ): >>> r = range ( 0 , 20 , 2 ) >>> r range(0, 20, 2) >>> 11 in r False >>> 10 in r True >>> r . index ( 10 ) 5 >>> r [ 5 ] 10 >>> r [: 5 ] range(0, 10, 2) >>> r [ - 1 ] 18 Testing range objects for equality with == and != compares them as sequences. That is, two range objects are considered equal if they represent the same sequence of values. (Note that two range objects that compare equal might have different start , stop and step attributes, for example range(0) == range(2, 1, 3) or range(0, 3, 2) == range(0, 4, 2) .) Changed in version 3.2: Implement the Sequence ABC. Support slicing and negative indices. Test int objects for membership in constant time instead of iterating through all items. Changed in version 3.3: Define ‘==’ and ‘!=’ to compare range objects based on the sequence of values they define (instead of comparing based on object identity). Added the start , stop and step attributes. See also The linspace recipe shows how to implement a lazy version of range suitable for floating-point applications. Text and Binary Sequence Type Methods Summary ¶ The following table summarizes the text and binary sequence types methods by category. Category str methods bytes and bytearray methods Formatting str.format() str.format_map() f-strings printf-style String Formatting printf-style Bytes Formatting Searching and Replacing str.find() str.rfind() bytes.find() bytes.rfind() str.index() str.rindex() bytes.index() bytes.rindex() str.startswith() bytes.startswith() str.endswith() bytes.endswith() str.count() bytes.count() str.replace() bytes.replace() Splitting and Joining str.split() str.rsplit() bytes.split() bytes.rsplit() str.splitlines() bytes.splitlines() str.partition() bytes.partition() str.rpartition() bytes.rpartition() str.join() bytes.join() String Classification str.isalpha() bytes.isalpha() str.isdecimal() str.isdigit() bytes.isdigit() str.isnumeric() str.isalnum() bytes.isalnum() str.isidentifier() str.islower() bytes.islower() str.isupper() bytes.isupper() str.istitle() bytes.istitle() str.isspace() bytes.isspace() str.isprintable() Case Manipulation str.lower() bytes.lower() str.upper() bytes.upper() str.casefold() str.capitalize() bytes.capitalize() str.title() bytes.title() str.swapcase() bytes.swapcase() Padding and Stripping str.ljust() str.rjust() bytes.ljust() bytes.rjust() str.center() bytes.center() str.expandtabs() bytes.expandtabs() str.strip() bytes.strip() str.lstrip() str.rstrip() bytes.lstrip() bytes.rstrip() Translation and Encoding str.translate() bytes.translate() str.maketrans() bytes.maketrans() str.encode() bytes.decode() Text Sequence Type — str ¶ Textual data in Python is handled with str objects, or strings . Strings are immutable sequences of Unicode code points. String literals are written in a variety of ways: Single quotes: 'allows embedded "double" quotes' Double quotes: "allows embedded 'single' quotes" Triple quoted: '''Three single quotes''' , """Three double quotes""" Triple quoted strings may span multiple lines - all associated whitespace will be included in the string literal. String literals that are part of a single expression and have only whitespace between them will be implicitly converted to a single string literal. That is, ("spam " "eggs") == "spam eggs" . See String and Bytes literals for more about the various forms of string literal | 2026-01-13T08:48:42 |
https://www.youtube.com/watch?v=ufHfs67xtXg | Resilient Angular Testing – Jaw Dropping Magic Tricks by The Magnificent Shairezniko | Shai Reznik - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x83c77a1d9e9f13e0"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtpTUNpY2VyR05oQSjjjZjLBjIKCgJLUhIEGgAgHw%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZR_BqeauckWVc64MaIGwyoL5MCIziJ3s8QokHRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","messageRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","badgeViewModel","continuationItemRenderer","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","adsEngagementPanelContentRenderer","engagementPanelTitleHeaderRenderer","chipBarViewModel","chipViewModel","sectionListRenderer","macroMarkersListRenderer","macroMarkersListItemRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","compactInfocardRenderer","mediaLockupRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cardCollectionRenderer","cardRenderer","simpleCardTeaserRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgtpTUNpY2VyR05oQSjjjZjLBjIKCgJLUhIEGgAgHw%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwjpyf30kIiSAxUX0jQHHWPlI5kyDHJlbGF0ZWQtYXV0b0j46sb3uvb3-LkBmgEFCAMQ-B3KAQS0Riyw","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=41zksebuVbc\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"41zksebuVbc","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjpyf30kIiSAxUX0jQHHWPlI5kyDHJlbGF0ZWQtYXV0b0j46sb3uvb3-LkBmgEFCAMQ-B3KAQS0Riyw","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=41zksebuVbc\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"41zksebuVbc","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjpyf30kIiSAxUX0jQHHWPlI5kyDHJlbGF0ZWQtYXV0b0j46sb3uvb3-LkBmgEFCAMQ-B3KAQS0Riyw","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=41zksebuVbc\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"41zksebuVbc","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"Resilient Angular Testing – Jaw Dropping Magic Tricks by The Magnificent Shairezniko | Shai Reznik"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 1,577회"},"shortViewCount":{"simpleText":"조회수 1.5천회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CKsCEMyrARgAIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC3VmSGZzNjd4dFhnGmBFZ3QxWmtobWN6WTNlSFJZWjBBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDNWbVNHWnpOamQ0ZEZobkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CKsCEMyrARgAIhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}}],"trackingParams":"CKsCEMyrARgAIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"17","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLYCEKVBIhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}},{"innertubeCommand":{"clickTrackingParams":"CLYCEKVBIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLcCEPqGBCITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLcCEPqGBCITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"ufHfs67xtXg"},"likeParams":"Cg0KC3VmSGZzNjd4dFhnIAAyCwjkjZjLBhCT1PdV"}},"idamTag":"66426"}},"trackingParams":"CLcCEPqGBCITCOnJ_fSQiJIDFRfSNAcdY-UjmQ=="}}}}}}}]}},"accessibilityText":"다른 사용자 17명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLYCEKVBIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"18","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLUCEKVBIhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}},{"innertubeCommand":{"clickTrackingParams":"CLUCEKVBIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"ufHfs67xtXg"},"removeLikeParams":"Cg0KC3VmSGZzNjd4dFhnGAAqCwjkjZjLBhCH-PhV"}}}]}},"accessibilityText":"다른 사용자 17명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLUCEKVBIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CKsCEMyrARgAIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","isTogglingDisabled":true}},"likeStatusEntityKey":"Egt1ZkhmczY3eHRYZyA-KAE%3D","likeStatusEntity":{"key":"Egt1ZkhmczY3eHRYZyA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLMCEKiPCSITCOnJ_fSQiJIDFRfSNAcdY-UjmQ=="}},{"innertubeCommand":{"clickTrackingParams":"CLMCEKiPCSITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLQCEPmGBCITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLQCEPmGBCITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"ufHfs67xtXg"},"dislikeParams":"Cg0KC3VmSGZzNjd4dFhnEAAiCwjkjZjLBhD3lvtV"}},"idamTag":"66425"}},"trackingParams":"CLQCEPmGBCITCOnJ_fSQiJIDFRfSNAcdY-UjmQ=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLMCEKiPCSITCOnJ_fSQiJIDFRfSNAcdY-UjmQ==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLICEKiPCSITCOnJ_fSQiJIDFRfSNAcdY-UjmQ=="}},{"innertubeCommand":{"clickTrackingParams":"CLICEKiPCSITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"ufHfs67xtXg"},"removeLikeParams":"Cg0KC3VmSGZzNjd4dFhnGAAqCwjkjZjLBhCS0ftV"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLICEKiPCSITCOnJ_fSQiJIDFRfSNAcdY-UjmQ==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CKsCEMyrARgAIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","isTogglingDisabled":true}},"dislikeEntityKey":"Egt1ZkhmczY3eHRYZyA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"Egt1ZkhmczY3eHRYZyD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLACEOWWARgCIhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}},{"innertubeCommand":{"clickTrackingParams":"CLACEOWWARgCIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgt1ZkhmczY3eHRYZ6ABAQ%3D%3D","commands":[{"clickTrackingParams":"CLACEOWWARgCIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CLECEI5iIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLACEOWWARgCIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CK4CEOuQCSITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CK8CEPuGBCITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DufHfs67xtXg%2526pp%253D0gcJCfcAYGclG_1k\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CK8CEPuGBCITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=ufHfs67xtXg\u0026pp=0gcJCfcAYGclG_1k","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"ufHfs67xtXg","playerParams":"0gcJCfcAYGclG_1k","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=b9f1dfb3aef1b578\u0026ip=1.208.108.242\u0026initcwndbps=3655000\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CK8CEPuGBCITCOnJ_fSQiJIDFRfSNAcdY-UjmQ=="}}}}}},"trackingParams":"CK4CEOuQCSITCOnJ_fSQiJIDFRfSNAcdY-UjmQ=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CKwCEOuQCSITCOnJ_fSQiJIDFRfSNAcdY-UjmQ=="}},{"innertubeCommand":{"clickTrackingParams":"CKwCEOuQCSITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CK0CEPuGBCITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DufHfs67xtXg%2526pp%253D0gcJCfcAYGclG_1k\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CK0CEPuGBCITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=ufHfs67xtXg\u0026pp=0gcJCfcAYGclG_1k","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"ufHfs67xtXg","playerParams":"0gcJCfcAYGclG_1k","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=b9f1dfb3aef1b578\u0026ip=1.208.108.242\u0026initcwndbps=3655000\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CK0CEPuGBCITCOnJ_fSQiJIDFRfSNAcdY-UjmQ=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CKwCEOuQCSITCOnJ_fSQiJIDFRfSNAcdY-UjmQ==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CKsCEMyrARgAIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","dateText":{"simpleText":"2020. 5. 26."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"5년 전"}},"simpleText":"5년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/b5_T6cF4QQgLHWemfk-ZPf2wShnPuKRFki7QrT9nfqFqkN5y4qHezJKIDfjEuPDsNRoaPOKkVA=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/b5_T6cF4QQgLHWemfk-ZPf2wShnPuKRFki7QrT9nfqFqkN5y4qHezJKIDfjEuPDsNRoaPOKkVA=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/b5_T6cF4QQgLHWemfk-ZPf2wShnPuKRFki7QrT9nfqFqkN5y4qHezJKIDfjEuPDsNRoaPOKkVA=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"ng-conf","navigationEndpoint":{"clickTrackingParams":"CKoCEOE5IhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"url":"/@ngconfonline","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCm9iiIfgmVODUJxINecHQkA","canonicalBaseUrl":"/@ngconfonline"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CKoCEOE5IhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"url":"/@ngconfonline","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCm9iiIfgmVODUJxINecHQkA","canonicalBaseUrl":"/@ngconfonline"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 6.59만명"}},"simpleText":"구독자 6.59만명"},"trackingParams":"CKoCEOE5IhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCm9iiIfgmVODUJxINecHQkA","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CJwCEJsrIhMI6cn99JCIkgMVF9I0Bx1j5SOZKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"ng-conf을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"ng-conf을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. ng-conf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CKkCEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. ng-conf 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. ng-conf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CKgCEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. ng-conf 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CKECEJf5ASITCOnJ_fSQiJIDFRfSNAcdY-UjmQ==","command":{"clickTrackingParams":"CKECEJf5ASITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CKECEJf5ASITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CKcCEOy1BBgDIhMI6cn99JCIkgMVF9I0Bx1j5SOZMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQS0Riyw","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ205aWlJZmdtVk9EVUp4SU5lY0hRa0ESAggBGAAgBFITCgIIAxILdWZIZnM2N3h0WGcYAA%3D%3D"}},"trackingParams":"CKcCEOy1BBgDIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CKYCEO21BBgEIhMI6cn99JCIkgMVF9I0Bx1j5SOZMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQS0Riyw","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ205aWlJZmdtVk9EVUp4SU5lY0hRa0ESAggDGAAgBFITCgIIAxILdWZIZnM2N3h0WGcYAA%3D%3D"}},"trackingParams":"CKYCEO21BBgEIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CKICENuLChgFIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKICENuLChgFIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CKMCEMY4IhMI6cn99JCIkgMVF9I0Bx1j5SOZ","dialogMessages":[{"runs":[{"text":"ng-conf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CKUCEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZMgV3YXRjaMoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCm9iiIfgmVODUJxINecHQkA"],"params":"CgIIAxILdWZIZnM2N3h0WGcYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CKUCEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CKQCEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CKICENuLChgFIhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CJwCEJsrIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CKACEP2GBCITCOnJ_fSQiJIDFRfSNAcdY-UjmTIJc3Vic2NyaWJlygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DufHfs67xtXg%2526pp%253D0gcJCfcAYGclG_1k%26continue_action%3DQUFFLUhqbTl4RkRoMGJNcHBvX2I1SXo1alRNVHgtckZUZ3xBQ3Jtc0tuWkM0YnFDd1pFSUlJRk8yeWhDQklyNVY0d0Vnd0FzR0c3cE1iejBkYWNrYU5BX1VjSnRoZnNySXNWU2w3U1lfdFRrNTRUV29Wa1dXZGxWeEpJMTN1VnpmTDVQbnZwY0JNMGdmT0lwMnFwV1RJTWZwQTBlUjA2OVNDaU5mYWJlV2d6VjdLcHhTa2UwVXlMaGRSR2xZT01sWEtyRkpVQktyM2lpb1gzb3VXcGcxYWNRV29ZU3ZXc1ZLUmg3eVhQNFJsWTZmVXk\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CKACEP2GBCITCOnJ_fSQiJIDFRfSNAcdY-UjmcoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=ufHfs67xtXg\u0026pp=0gcJCfcAYGclG_1k","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"ufHfs67xtXg","playerParams":"0gcJCfcAYGclG_1k","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=b9f1dfb3aef1b578\u0026ip=1.208.108.242\u0026initcwndbps=3655000\u0026mt=1768293662\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbTl4RkRoMGJNcHBvX2I1SXo1alRNVHgtckZUZ3xBQ3Jtc0tuWkM0YnFDd1pFSUlJRk8yeWhDQklyNVY0d0Vnd0FzR0c3cE1iejBkYWNrYU5BX1VjSnRoZnNySXNWU2w3U1lfdFRrNTRUV29Wa1dXZGxWeEpJMTN1VnpmTDVQbnZwY0JNMGdmT0lwMnFwV1RJTWZwQTBlUjA2OVNDaU5mYWJlV2d6VjdLcHhTa2UwVXlMaGRSR2xZT01sWEtyRkpVQktyM2lpb1gzb3VXcGcxYWNRV29ZU3ZXc1ZLUmg3eVhQNFJsWTZmVXk","idamTag":"66429"}},"trackingParams":"CKACEP2GBCITCOnJ_fSQiJIDFRfSNAcdY-UjmQ=="}}}}}},"subscribedEntityKey":"EhhVQ205aWlJZmdtVk9EVUp4SU5lY0hRa0EgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CJwCEJsrIhMI6cn99JCIkgMVF9I0Bx1j5SOZKPgdMgV3YXRjaMoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCm9iiIfgmVODUJxINecHQkA"],"params":"EgIIAxgAIgt1ZkhmczY3eHRYZw%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CJwCEJsrIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJwCEJsrIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CJ0CEMY4IhMI6cn99JCIkgMVF9I0Bx1j5SOZ","dialogMessages":[{"runs":[{"text":"ng-conf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CJ8CEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZKPgdMgV3YXRjaMoBBLRGLLA=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCm9iiIfgmVODUJxINecHQkA"],"params":"CgIIAxILdWZIZnM2N3h0WGcYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CJ8CEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CJ4CEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Get your free ticket to EnterpriseNG conference Keynote: https://ng-conf.org\n\nHow would you like to save time while improving your code design? What about having future-proof upgrades of your 3rd party dependencies?\n\n“Resilient Angular testing” is a magical marvel designed to overload the senses with unbelievable illusions and coding techniques that will get you exponential gains with little to no effort.\n\nPerformed by The Magnificent Shairezniko, a legendary showman who’s been hailed by audiences and critics alike as the “greatest code illusionist of our time.”\n\nThis talk is a MUST for anyone who’d like to learn this critical coding principle which will benefit you whether you’re testing your code or not.\nWatch all the ng-conf: Hardwired presentations/videos at https://videos.ng-conf.org\n\nng-conf is a multi-day Angular conference focused on delivering the highest quality training in the Angular JavaScript framework. 1500+ developers from across the globe converge on Salt Lake City, UT every year to attend talks and workshops by the Angular team and community experts.\n\nng-conf: Hardwired is brought to you by:\nhttps://thinkster.io/ The best Angular and JavaScript tutorials on the web\nhttps://herodevs.com/ Engineering and consulting by web development experts\nhttps://xlts.dev/ Extended support for AngularJS\n\nFollow us on twitter / ngconf \nOfficial Website: https://www.ng-conf.org/","commandRuns":[{"startIndex":57,"length":19,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZSPjqxve69vf4uQHKAQS0Riyw","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbkN1SzdhMWpYYWw5czJyek1jUW9xMDRMYVZNUXxBQ3Jtc0ttdVlhWS03M2NDYmJ0R19PeW9lUnlvNGJkS3FNRkZkU24wVlRDMDRiYVo5ZV91ZmVKZkhhaS01dWFTdGRaZXE3RVFwWkpJMFNMTWhod3ZldnFkZy15Ni1kZHZVRHZSUDVCTElUdjVNZjlBWnJLeld5bw\u0026q=https%3A%2F%2Fng-conf.org%2F\u0026v=ufHfs67xtXg","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbkN1SzdhMWpYYWw5czJyek1jUW9xMDRMYVZNUXxBQ3Jtc0ttdVlhWS03M2NDYmJ0R19PeW9lUnlvNGJkS3FNRkZkU24wVlRDMDRiYVo5ZV91ZmVKZkhhaS01dWFTdGRaZXE3RVFwWkpJMFNMTWhod3ZldnFkZy15Ni1kZHZVRHZSUDVCTElUdjVNZjlBWnJLeld5bw\u0026q=https%3A%2F%2Fng-conf.org%2F\u0026v=ufHfs67xtXg","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":773,"length":26,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZSPjqxve69vf4uQHKAQS0Riyw","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbHotVm1hWDNrcEtNOE1PckRQQnREdEVXZWFPZ3xBQ3Jtc0tsS1I5ai00YnJpempuNUFadnhqMEg5bzRITllwMWZGWEN4WlRhb21pblplZ0xFMG5aNGU0azZESG5OQzBkMERzdWVQRktSOGNTRmVYNkhYM1NCNmF4RTFPMDZEaFhBMmR5MnU4d21KeVhrNzBqdk91TQ\u0026q=https%3A%2F%2Fvideos.ng-conf.org%2F\u0026v=ufHfs67xtXg","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbHotVm1hWDNrcEtNOE1PckRQQnREdEVXZWFPZ3xBQ3Jtc0tsS1I5ai00YnJpempuNUFadnhqMEg5bzRITllwMWZGWEN4WlRhb21pblplZ0xFMG5aNGU0azZESG5OQzBkMERzdWVQRktSOGNTRmVYNkhYM1NCNmF4RTFPMDZEaFhBMmR5MnU4d21KeVhrNzBqdk91TQ\u0026q=https%3A%2F%2Fvideos.ng-conf.org%2F\u0026v=ufHfs67xtXg","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":1127,"length":21,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZSPjqxve69vf4uQHKAQS0Riyw","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbEZBMU9hYUV1T2hEbmNhRzViME1YT3Q4eFRjUXxBQ3Jtc0tsakU1N3BxX0ZjWjFyeWF4NTkwUWRueWl0REJVSHRMaUVwSzRYOUpZZ1lnM1Z2Sndta0VodzNLaEhEbUtmX0pjOEZ2NWE1UUd6Qko5LUNxVUZfV2FWaUtOckJKRnJxSFhzSzlPa2lhODlTY2lyVXhadw\u0026q=https%3A%2F%2Fthinkster.io%2F\u0026v=ufHfs67xtXg","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbEZBMU9hYUV1T2hEbmNhRzViME1YT3Q4eFRjUXxBQ3Jtc0tsakU1N3BxX0ZjWjFyeWF4NTkwUWRueWl0REJVSHRMaUVwSzRYOUpZZ1lnM1Z2Sndta0VodzNLaEhEbUtmX0pjOEZ2NWE1UUd6Qko5LUNxVUZfV2FWaUtOckJKRnJxSFhzSzlPa2lhODlTY2lyVXhadw\u0026q=https%3A%2F%2Fthinkster.io%2F\u0026v=ufHfs67xtXg","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":1202,"length":21,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZSPjqxve69vf4uQHKAQS0Riyw","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbm9QSGlDNHUxTjRVb2FfcEtKSW10c3UtWWlEUXxBQ3Jtc0tsY1BUQnZ1NUJmTlI2SnJkOFBFX20weFprZVM2ZnZJSkVlOWJMZU9yN2x0UlJ6bGd3T29feU1wVWF6QS05QmRqTjdyUEpRYmxVNUhWcmF1QnZ3MDUtdVgyWi1peUR0U3p5VmtwR2dTOUVSalJvZnVmVQ\u0026q=https%3A%2F%2Fherodevs.com%2F\u0026v=ufHfs67xtXg","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbm9QSGlDNHUxTjRVb2FfcEtKSW10c3UtWWlEUXxBQ3Jtc0tsY1BUQnZ1NUJmTlI2SnJkOFBFX20weFprZVM2ZnZJSkVlOWJMZU9yN2x0UlJ6bGd3T29feU1wVWF6QS05QmRqTjdyUEpRYmxVNUhWcmF1QnZ3MDUtdVgyWi1peUR0U3p5VmtwR2dTOUVSalJvZnVmVQ\u0026q=https%3A%2F%2Fherodevs.com%2F\u0026v=ufHfs67xtXg","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":1278,"length":17,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZSPjqxve69vf4uQHKAQS0Riyw","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbUplSUkxcW81SWx1eEdLbzNMOWtKd1pfaGJ3UXxBQ3Jtc0treWFZbVFEWHZYeUF1TlNXQXl0STNzc3hWVnl1aFpON1d2b05tQ3V0WGFzeWgya29fRHhTVVRpdXBnUzdhMlV5dllCT1QySUhmcVJrNEtadGlxQ01YaHg5cDhUZHhzb3I5X18yeHBYd0M0VUpXeXRqNA\u0026q=https%3A%2F%2Fxlts.dev%2F\u0026v=ufHfs67xtXg","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbUplSUkxcW81SWx1eEdLbzNMOWtKd1pfaGJ3UXxBQ3Jtc0treWFZbVFEWHZYeUF1TlNXQXl0STNzc3hWVnl1aFpON1d2b05tQ3V0WGFzeWgya29fRHhTVVRpdXBnUzdhMlV5dllCT1QySUhmcVJrNEtadGlxQ01YaHg5cDhUZHhzb3I5X18yeHBYd0M0VUpXeXRqNA\u0026q=https%3A%2F%2Fxlts.dev%2F\u0026v=ufHfs67xtXg","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":1350,"length":12,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZSPjqxve69vf4uQHKAQS0Riyw","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0txOW9SRnpVTE5EM1hieXJvUzFZbnlucUlqQXxBQ3Jtc0trb0o4R3FOdnBrSzk0U3QtcDhyM2tWNTJydTdvS0dyZ3lxNzB2ZWp4WmM3dE1qdmZLYTdDcFgycm9zU2ItWVRiR1RPazE5Y2dnWDZNbzRYc3VuWEZqX2FfazFNc1lFdUtWLWFmeXNXMGJod081UU5Ddw\u0026q=https%3A%2F%2Ftwitter.com%2Fngconf\u0026v=ufHfs67xtXg","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0txOW9SRnpVTE5EM1hieXJvUzFZbnlucUlqQXxBQ3Jtc0trb0o4R3FOdnBrSzk0U3QtcDhyM2tWNTJydTdvS0dyZ3lxNzB2ZWp4WmM3dE1qdmZLYTdDcFgycm9zU2ItWVRiR1RPazE5Y2dnWDZNbzRYc3VuWEZqX2FfazFNc1lFdUtWLWFmeXNXMGJod081UU5Ddw\u0026q=https%3A%2F%2Ftwitter.com%2Fngconf\u0026v=ufHfs67xtXg","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: ngconf"}}},{"startIndex":1381,"length":24,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJsCEM2rARgBIhMI6cn99JCIkgMVF9I0Bx1j5SOZSPjqxve69vf4uQHKAQS0Riyw","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbHB4UDJ6eVFjRk9mOGFCUFEzcWw5UUFLOTBtQXxBQ3Jtc0tuR2NYNkl2MlRFVHpMUHY0LUVYbDBMN3duR3EwcHFSLXVpY1ZidzZVNDVLTXRLLWwzMllocEJFMmVpUndyVjk4aHhhUFVZZ0l3cWhXandGdWZkeDc5LTh3OU9rQl9MNkpBVzhDdnZYbDBZSVllYmk5SQ\u0026q=https%3A%2F%2Fwww.ng-conf.org%2F\u0026v=ufHfs67xtXg","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbHB4UDJ6eVFjRk9mOGFCUFEzcWw5UUFLOTBtQXxBQ3Jtc0tuR2NYNkl2MlRFVHpMUHY0LUVYbDBMN3duR3EwcHFSLXVpY1ZidzZVNDVLTXRLLWwzMllocEJFMmVpUndyVjk4aHhhUFVZZ0l3cWhXandGdWZkeDc5LTh3OU9rQl9MNkpBVzhDdnZYbDBZSVllYmk5SQ\u0026q=https%3A%2F%2Fwww.ng-conf.org%2F\u0026v=ufHfs67xtXg","target":"TARGET_NEW_WINDOW","nofollow":true}}}}],"styleRuns":[{"startIndex":0,"length":57,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":57,"length":19,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":76,"length":697,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":773,"length":26,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":799,"length":328,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1127,"length":21,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1148,"length":54,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1202,"length":21,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1223,"length":55,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1278,"length":17,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1295,"length":33,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1328,"length":22,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1350,"length":12,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}}},{"startIndex":1362,"length":19,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1381,"length":24,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"}],"attachmentRuns":[{"startIndex":1351,"length":0,"element":{"type":{"imageType":{"image":{"sources":[{"url":"https://www.gstatic.com/youtube/img/watch/social_media/twitter_1x_v2.png"}]}}},"properties":{"layoutProperties":{"height":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"width":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"margin":{"top":{"value":0.5,"unit":"DIMENSION_UNIT_POINT"}}}}},"alignment":"ALIGNMENT_VERTICAL_CENTER"}],"decorationRuns":[{"textDecorator":{"highlightTextDecorator":{"startIndex":1350,"length":12,"backgroundCornerRadius":8,"bottomPadding":1,"highlightTextDecoratorExtensions":{"highlightTextDecoratorColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":452984831},{"key":"USER_INTERFACE_THEME_LIGHT","value":218103808}]}}}}}],"paragraphStyleRuns":[{"startIndex":1127,"length":201,"listGroup":{"listType":"LIST_TYPE_BULLET","listItems":[{"listType":"LIST_TYPE_BULLET","startIndex":1127,"length":75},{"listType":"LIST_TYPE_BULLET","startIndex":1202,"length":76},{"listType":"LIST_TYPE_BULLET","startIndex":1278,"length":50}]}},{"length":1329}]},"headerRuns":[{"startIndex":0,"length":57,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":57,"length":19,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":76,"length":697,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":773,"length":26,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":799,"length":328,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1127,"length":21,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1148,"length":54,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1202,"length":21,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1223,"length":55,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1278,"length":17,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1295,"length":33,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1328,"length":22,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1350,"length":12,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1362,"length":19,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1381,"length":24,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"messageRenderer":{"text":{"runs":[{"text":"댓글이 사용 중지되었습니다. "},{"text":"자세히 알아보기","navigationEndpoint":{"clickTrackingParams":"CJoCEJY7GAAiEwjpyf30kIiSAxUX0jQHHWPlI5nKAQS0Riyw","commandMetadata":{"webCommandMetadata":{"url":"https://support.google.com/youtube/answer/9706180?hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://support.google.com/youtube/answer/9706180?hl=ko"}}}]},"trackingParams":"CJoCEJY7GAAiEwjpyf30kIiSAxUX0jQHHWPlI5k="}}],"trackingParams":"CJkCELsvGAMiEwjpyf30kIiSAxUX0jQHHWPlI5k=","sectionIdentifier":"comment-item-section"}}],"trackingParams":"CJgCELovIhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/N1JZNHep8YQ/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLCl3mA8B7_bSz_ClTiA0rW3W9tAEQ","width":168,"height":94},{"url":"https://i.ytimg.com/vi/N1JZNHep8YQ/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLA1QRi8kjLn1jIX2EW2Pqk4yyBUmw","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"1:00:47","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"N1JZNHep8YQ","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"1시간 47초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CJcCEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"N1JZNHep8YQ","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJcCEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CJYCEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"N1JZNHep8YQ"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJYCEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZ","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CI8CENTEDBgAIhMI6cn99JCIkgMVF9I0Bx1j5SOZ"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CJUCEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJUCEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"N1JZNHep8YQ","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CJUCEPBbIhMI6cn99JCIkgMVF9I0Bx1j5SOZygEEtEYssA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPl | 2026-01-13T08:48:40 |
https://parenting.forem.com/about#how-to-get-involved | About Parenting 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 Parenting Close About Parenting Welcome to Parenting! Parenting is the most rewarding, challenging, and unpredictable journey of a lifetime. Whether you're celebrating a first smile, navigating the tumultuous teens, or learning to let go with adult children, we're here for you. Parenting is a warm and supportive community built by parents, for parents. We're here to share the unfiltered realities—the sleepless nights and the belly laughs, the tough questions and the proudest moments. You are not alone on this adventure. Our Mission Our purpose is simple: to create a judgment-free space where parents can connect, share experiences, and find solidarity. We embrace the idea that there is no one-size-fits-all manual for raising children. Instead, we learn from each other, offering diverse perspectives and unwavering support through every stage of parenthood, from the first cries of infancy to the complexities of having grown-up kids. What to Discuss We encourage open and honest conversations about all aspects of family life. Jump into discussions or start your own on topics like: Milestone Moments: Share the joy of first steps, graduations, and everything in between. Tough Questions: From sleep training and toddler tantrums to screen time debates and difficult conversations. Product & Resource Swaps: Ask for recommendations on everything from the best strollers to books on navigating teenage anxiety. Personal Stories: Share the funny, messy, and beautiful moments that make up your unique parenting story. Seeking Advice: Get real-world perspectives on challenges you're facing. Relationship Dynamics: Discuss co-parenting, managing family expectations, and finding time for your partner. How to Get Involved Becoming part of our community is easy! Here’s how you can contribute: Ask a question: No question is too big or too small. The collective wisdom here is one of our greatest assets. Share your experience: Your story could be exactly what another parent needs to hear today. Offer support: Sometimes, the best response is a simple, "I've been there too." Lend an ear and a virtual shoulder to lean on. Leave some love: Engage with posts that resonate with you. Your participation helps great conversations rise to the top. Our Community Values To keep this a safe, welcoming, and helpful space for everyone, we ask all members to follow a few simple guidelines: Be Kind and Respectful. We all have different backgrounds and parenting styles. Engage in constructive, not critical, conversations. It's okay to disagree with an idea, but it's never okay to attack a person. Support, Don't Judge. This is a shame-free zone. Offer empathy and encouragement. We are here to lift each other up. Protect Privacy. Be mindful of sharing personally identifiable information about yourself and your children. What you share is public. Never share private information about other members. This Is Not a Substitute for Professional Advice. While sharing personal experiences is valuable, please remember that this community cannot provide professional medical, legal, or mental health advice. Always consult a qualified expert for serious concerns. No Spam or Self-Promotion. This community is for connection, not for advertising. Please refrain from unsolicited marketing or excessive self-promotion. We're so glad you're here ❤️ 💎 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 Parenting — 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. 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 . Parenting © 2016 - 2026. Navigating the chaos and joy of parenting. Log in Create account | 2026-01-13T08:48:42 |
https://youtube.com/new | YouTube 실험실 페이지 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:48:42 |
https://dev.to/szabgab | Gabor Szabo - 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 Gabor Szabo Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Joined Joined on Oct 11, 2017 Email address gabor@szabgab.com Personal website https://szabgab.com github website twitter website Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Eight Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least eight years. Got it Close 2 Top 7 Awarded for having a post featured in the weekly "must-reads" list. 🙌 Got it Close Rust Awarded to the top Rust author each week Got it Close 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 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 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 16 Week Writing Streak You are a writing star! You've written at least one post per week for 16 straight weeks. Congratulations! Got it Close 8 Week Community Wellness Streak Consistency pays off! Be an active part of our community by posting at least 2 comments per week for 8 straight weeks. Earn the 16 Week Badge next. Got it Close Tag Moderator 2022 Awarded for being a tag moderator in 2022. Got it Close Trusted Member 2022 Awarded for being a trusted member in 2022. 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 Community Wellness Streak Keep contributing to discussions by posting at least 2 comments per week for 4 straight weeks. Unlock the 8 Week Badge next. Got it Close 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 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 1 Week Community Wellness Streak For actively engaging with the community by posting at least 2 comments in a single week. 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 Hacktoberfest 2020 Awarded for successful completion of the 2020 Hacktoberfest challenge. 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 Hacktoberfest 2019 Awarded for successful completion of the 2019 Hacktoberfest challenge. 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 Show all 23 badges More info about @szabgab Organizations Code Maven Skills/Languages Perl, Python, Git, CI systems, Test Automation, Docker, DevOps related tools Currently learning More CI systems, Video creation Currently hacking on The digger projects - PyDigger, Ruby Digger, CPAN Digger Available for Helping with testing, test automation, CI, CD, Docker Post 372 posts published Comment 240 comments written Tag 24 tags followed Pin Pinned Billions of unnecessary files in GitHub Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 21 '22 Billions of unnecessary files in GitHub # github # programming # python # webdev 125 reactions Comments 51 comments 3 min read Why use a version control system? - 💒 Gabor Szabo Gabor Szabo Gabor Szabo Follow Nov 28 '22 Why use a version control system? - 💒 # git # programming # beginners # tutorial 6 reactions Comments 3 comments 5 min read Python Functional Programming: Introduction Gabor Szabo Gabor Szabo Gabor Szabo Follow Nov 25 '22 Python Functional Programming: Introduction # python # tutorial # programming 11 reactions Comments 1 comment 3 min read Docker course: Introduction Gabor Szabo Gabor Szabo Gabor Szabo Follow Nov 22 '22 Docker course: Introduction # docker # tutorial # beginners # devops 9 reactions Comments 2 comments 1 min read Perl 🐪 Weekly #755 - Does TIOBE help Perl? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jan 12 Perl 🐪 Weekly #755 - Does TIOBE help Perl? # news # perl # programming Comments Add Comment 6 min read Want to connect with Gabor Szabo? Create an account to connect with Gabor Szabo. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in Perl 🐪 Weekly #754 - New Year Resolution Gabor Szabo Gabor Szabo Gabor Szabo Follow Jan 5 Perl 🐪 Weekly #754 - New Year Resolution # news # perl # programming Comments Add Comment 6 min read Perl 🐪 Weekly #753 - Happy New Year! Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 29 '25 Perl 🐪 Weekly #753 - Happy New Year! # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl 🐪 Weekly #752 - Marlin - OOP Framework Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 22 '25 Perl 🐪 Weekly #752 - Marlin - OOP Framework # news # perl # programming 2 reactions Comments Add Comment 7 min read Perl 🐪 Weekly #751 - Open Source contributions Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 15 '25 Perl 🐪 Weekly #751 - Open Source contributions # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 8 '25 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 # news # perl # programming 1 reaction Comments Add Comment 7 min read Perl 🐪 Weekly #749 - Design Patterns in Modern Perl Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 1 '25 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl 🐪 Weekly #748 - Perl v5.43.5 Gabor Szabo Gabor Szabo Gabor Szabo Follow Nov 24 '25 Perl 🐪 Weekly #748 - Perl v5.43.5 # news # perl # programming 2 reactions Comments Add Comment 6 min read Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 Gabor Szabo Gabor Szabo Gabor Szabo Follow Nov 10 '25 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 # news # perl # programming 2 reactions Comments Add Comment 5 min read Perl 🐪 Weekly #745 - Perl IDE Survey Gabor Szabo Gabor Szabo Gabor Szabo Follow Nov 3 '25 Perl 🐪 Weekly #745 - Perl IDE Survey # news # perl # programming 2 reactions Comments Add Comment 7 min read How to find an open source project to contribute to? Gabor Szabo Gabor Szabo Gabor Szabo Follow Oct 28 '25 How to find an open source project to contribute to? # opensource # programming # beginners 6 reactions Comments Add Comment 1 min read Perl 🐪 Weekly #744 - London Perl Workshop 2025 Gabor Szabo Gabor Szabo Gabor Szabo Follow Oct 27 '25 Perl 🐪 Weekly #744 - London Perl Workshop 2025 # news # perl # programming 1 reaction Comments Add Comment 8 min read Perl 🐪 Weekly #743 - Writing Perl with LLMs Gabor Szabo Gabor Szabo Gabor Szabo Follow Oct 20 '25 Perl 🐪 Weekly #743 - Writing Perl with LLMs # news # perl # programming 1 reaction Comments Add Comment 7 min read Perl 🐪 Weekly #742 - Support TPRF Gabor Szabo Gabor Szabo Gabor Szabo Follow Oct 13 '25 Perl 🐪 Weekly #742 - Support TPRF # news # perl # programming 1 reaction Comments Add Comment 7 min read Perl 🐪 Weekly #741 - Money to TPRF 💰 Gabor Szabo Gabor Szabo Gabor Szabo Follow Oct 6 '25 Perl 🐪 Weekly #741 - Money to TPRF 💰 # news # perl # programming Comments Add Comment 7 min read Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 Gabor Szabo Gabor Szabo Gabor Szabo Follow Sep 22 '25 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 # news # perl # programming 2 reactions Comments Add Comment 5 min read Perl 🐪 Weekly #737 - Perl oneliners Gabor Szabo Gabor Szabo Gabor Szabo Follow Sep 8 '25 Perl 🐪 Weekly #737 - Perl oneliners # news # perl # programming 2 reactions Comments Add Comment 6 min read Perl 🐪 Weekly #736 - NICEPERL Gabor Szabo Gabor Szabo Gabor Szabo Follow Sep 1 '25 Perl 🐪 Weekly #736 - NICEPERL # news # perl # programming 2 reactions Comments 1 comment 6 min read Programming communities? Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 25 '25 Programming communities? # programming # beginners 5 reactions Comments 5 comments 2 min read Perl 🐪 Weekly #735 - Perl-related events Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 25 '25 Perl 🐪 Weekly #735 - Perl-related events # news # perl # programming Comments Add Comment 5 min read Open Source Software Foundations Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 22 '25 Open Source Software Foundations # opensource # programming Comments Add Comment 1 min read Why Testing? Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 20 '25 Why Testing? # testing # programming # beginners Comments 1 comment 2 min read Perl 🐪 Weekly #734 - CPAN Day Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 18 '25 Perl 🐪 Weekly #734 - CPAN Day # news # perl # programming Comments Add Comment 5 min read Python Flask: Testing hello world Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 13 '25 Python Flask: Testing hello world # python # webdev # testing # programming 1 reaction Comments Add Comment 1 min read Python Flask: Hello World Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 12 '25 Python Flask: Hello World # python # webdev # programming # tutorial 1 reaction Comments 1 comment 1 min read Perl 🐪 Weekly #733 - Perl using AI Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 11 '25 Perl 🐪 Weekly #733 - Perl using AI # news # perl # programming Comments Add Comment 6 min read What is the interest of companies in Open Source? Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 5 '25 What is the interest of companies in Open Source? # opensource # programming # beginners 2 reactions Comments Add Comment 1 min read How to find projects that are easy to contribute to? Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 4 '25 How to find projects that are easy to contribute to? # opensource # beginners # programming 2 reactions Comments Add Comment 1 min read Perl 🐪 Weekly #732 - MetaCPAN Success Story Gabor Szabo Gabor Szabo Gabor Szabo Follow Aug 4 '25 Perl 🐪 Weekly #732 - MetaCPAN Success Story # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl 🐪 Weekly #731 - Looking for a Perl event organizer Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 28 '25 Perl 🐪 Weekly #731 - Looking for a Perl event organizer # news # perl # programming 1 reaction Comments Add Comment 5 min read Perl 🐪 Weekly #730 - RIP MST Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 21 '25 Perl 🐪 Weekly #730 - RIP MST # news # perl # programming 1 reaction Comments Add Comment 7 min read Should you start your own open source project or should you contribute to an existing one? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 15 '25 Should you start your own open source project or should you contribute to an existing one? # opensource # programming # career Comments 2 comments 2 min read Contributing to a well-known Open Source project Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 14 '25 Contributing to a well-known Open Source project # opensource # programming 3 reactions Comments Add Comment 1 min read Perl 🐪 Weekly #729 - Videos from TPRC Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 14 '25 Perl 🐪 Weekly #729 - Videos from TPRC # news # perl # programming 2 reactions Comments Add Comment 5 min read Why do you contribute to Open Source? What is your motivation? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 13 '25 Why do you contribute to Open Source? What is your motivation? # opensource # beginners # programming # career 1 reaction Comments Add Comment 2 min read Contributing to PyPI Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 12 '25 Contributing to PyPI # python # opensource # programming 2 reactions Comments Add Comment 1 min read Would you like to be a movie star by contributing to open source? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 11 '25 Would you like to be a movie star by contributing to open source? # opensource # programming # python # cybersecurity 1 reaction Comments Add Comment 2 min read How to contribute to Moodle? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 10 '25 How to contribute to Moodle? # opensource # php # beginners # programming 2 reactions Comments Add Comment 3 min read Do you need to be a programmer to contribute to open source projects? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 8 '25 Do you need to be a programmer to contribute to open source projects? # opensource # beginners 1 reaction Comments Add Comment 1 min read Perl 🐪 Weekly #728 - Perl Conference Gabor Szabo Gabor Szabo Gabor Szabo Follow Jul 7 '25 Perl 🐪 Weekly #728 - Perl Conference # news # perl # programming 1 reaction Comments Add Comment 7 min read Perl 🐪 Weekly #727 - Which versions of Perl do you use? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jun 30 '25 Perl 🐪 Weekly #727 - Which versions of Perl do you use? # news # perl # programming Comments Add Comment 8 min read Perl 🐪 Weekly #726 - Perl and ChatGPT Gabor Szabo Gabor Szabo Gabor Szabo Follow Jun 23 '25 Perl 🐪 Weekly #726 - Perl and ChatGPT # news # perl # programming Comments Add Comment 7 min read Perl 🐪 Weekly #725 - Perl podcasts? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jun 23 '25 Perl 🐪 Weekly #725 - Perl podcasts? # news # perl # programming Comments Add Comment 6 min read Publishing in Arabic, Hebrew, or Persian? Gabor Szabo Gabor Szabo Gabor Szabo Follow Jun 16 '25 Publishing in Arabic, Hebrew, or Persian? # github # gitlab 2 reactions Comments Add Comment 1 min read Perl 🐪 Weekly #724 - Perl and XS Gabor Szabo Gabor Szabo Gabor Szabo Follow Jun 9 '25 Perl 🐪 Weekly #724 - Perl and XS # news # perl # programming 2 reactions Comments 2 comments 5 min read Perl 🐪 Weekly #723 - Perl Ad Server needs ads Gabor Szabo Gabor Szabo Gabor Szabo Follow Jun 2 '25 Perl 🐪 Weekly #723 - Perl Ad Server needs ads # news # perl # programming 2 reactions Comments Add Comment 5 min read Perl 🐪 Weekly #721 - Perl Roadmap Gabor Szabo Gabor Szabo Gabor Szabo Follow May 19 '25 Perl 🐪 Weekly #721 - Perl Roadmap # news # perl # programming 2 reactions Comments 1 comment 6 min read Perl 🐪 Weekly #720 - GPW 2025 Gabor Szabo Gabor Szabo Gabor Szabo Follow May 12 '25 Perl 🐪 Weekly #720 - GPW 2025 # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl 🐪 Weekly #719 - How do you deal with the decline? Gabor Szabo Gabor Szabo Gabor Szabo Follow May 5 '25 Perl 🐪 Weekly #719 - How do you deal with the decline? # news # perl # programming 2 reactions Comments Add Comment 5 min read Perl 🐪 Weekly #717 - Happy Easter Gabor Szabo Gabor Szabo Gabor Szabo Follow Apr 21 '25 Perl 🐪 Weekly #717 - Happy Easter # news # perl # programming 1 reaction Comments Add Comment 5 min read Perl 🐪 Weekly #716 - CVE in Perl Gabor Szabo Gabor Szabo Gabor Szabo Follow Apr 14 '25 Perl 🐪 Weekly #716 - CVE in Perl # news # perl # programming Comments Add Comment 6 min read Perl 🐪 Weekly #715 - Why do companies move away from Perl? Gabor Szabo Gabor Szabo Gabor Szabo Follow Apr 7 '25 Perl 🐪 Weekly #715 - Why do companies move away from Perl? # news # perl # programming 1 reaction Comments Add Comment 6 min read Perl 🐪 Weekly #714 - Munging Data? Gabor Szabo Gabor Szabo Gabor Szabo Follow Mar 31 '25 Perl 🐪 Weekly #714 - Munging Data? # news # perl # programming 2 reactions Comments Add Comment 6 min read Public mdBooks Gabor Szabo Gabor Szabo Gabor Szabo Follow Mar 30 '25 Public mdBooks # rust # programming # tutorial # productivity 2 reactions Comments Add Comment 1 min read Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? Gabor Szabo Gabor Szabo Gabor Szabo Follow Mar 24 '25 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? # news # perl # programming 2 reactions Comments Add Comment 6 min read Perl 🐪 Weekly #712 - RIP Zefram Gabor Szabo Gabor Szabo Gabor Szabo Follow Mar 17 '25 Perl 🐪 Weekly #712 - RIP Zefram # news # perl # programming 1 reaction Comments Add Comment 7 min read Perl 🐪 Weekly #711 - Obfuscating Perl Gabor Szabo Gabor Szabo Gabor Szabo Follow Mar 10 '25 Perl 🐪 Weekly #711 - Obfuscating Perl # news # perl # programming 1 reaction Comments Add Comment 5 min read Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes Gabor Szabo Gabor Szabo Gabor Szabo Follow Mar 3 '25 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes # news # perl # programming 2 reactions Comments Add Comment 6 min read Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit Gabor Szabo Gabor Szabo Gabor Szabo Follow Feb 24 '25 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit # news # perl # programming 1 reaction Comments Add Comment 5 min read Online events: Python in English (Feb 18-Feb 28) Gabor Szabo Gabor Szabo Gabor Szabo Follow Feb 18 '25 Online events: Python in English (Feb 18-Feb 28) # python 2 reactions 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:48:42 |
https://docs.suprsend.com/docs/node-broadcast | Broadcast - 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 Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Node.js SDK Integrate Node SDK Manage Users Objects Send and Track Events Trigger Workflow from API Tenants Lists Broadcast Java SDK Go SDK SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Node.js SDK Broadcast Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Node.js SDK Broadcast OpenAI Open in ChatGPT Trigger broadcast notifications to a list of users with NodeJS SDK. OpenAI Open in ChatGPT Pre-Requisites Create a list of users Trigger broadcast You can trigger broadcast using supr_client.subscriber_lists.broadcast() method. Request Example Response Copy Ask AI const { Suprsend , SubscriberListBroadcast } = require ( "@suprsend/node-sdk" ); const supr_client = new Suprsend ( "workspace_key" , "workspace_secret" ); // prepare payload const broadcast_body = { list_id: "_list_id_" , template: "_template_slug_" , notification_category: "_" , channels: [], delay: "_time_delay_" , trigger_at: "_ISO_timestamp_" / "number in seconds" , data: { key1: "value1" , key2: "value2" , }, }; const broadcast_instance = new SubscriberListBroadcast ( broadcast_body , { tenant_id : "your_tenant_id" , idempotency_key = "__uniq_request_id__" }); // create broadcast instance const response = supr_client . subscriber_lists . broadcast ( inst ); // trigger broadcast response . then (( res ) => console . log ( "response" , res )); Parameter Description list_id list of users that you want to send broadcast messages. template It is the template slug which can be found in Templates tab in SuprSend dashboard. notification_category Preference Category to apply user preference settings while sending. Root categories- system / transactional / promotional channels (Optional) User channels on which the broadcast messages to be sent. If not provided, it will trigger notifications on all available channels in user profile. Available channels: androidpush / iospush / inbox / email / whatsapp / sms Example:[“sms”, “inbox”] delay (Optional) Broadcast will be halted for the time mentioned in delay, and become active once the delay period is over. Example: 1d2h3m4s / 60 trigger_at (Optional) Trigger broadcast on a specific date-time. Example: “2021-08-27T20:14:51.643Z” data (Optional) variable data defined in templates Add file attachment (for email) To add one or more attachments to a notification (viz. Email), call add_attachment() on broadcast instance for each attachment file. Ensure that attachment url is valid and public, otherwise error will be raised. Since broadcast instance size can’t be > 100 KB, local file paths can’t be passed in event attachment. Request Copy Ask AI const broadcast_instance = new SubscriberListBroadcast ( broadcast_body ); broadcast_instance . add_attachment ( "/home/user/billing.pdf" ); broadcast_instance . add_attachment ( "https://www.adobe.com/sample_file.pdf" ); 🚧 A single broadcast instance size (including attachment) must not exceed 100KB (100 x 1024 bytes). Was this page helpful? Yes No Suggest edits Raise issue Previous Integrate Java SDK Install & Initialize SuprSend Java SDK using your workspace credentials for sending notifications. Next ⌘ I x github linkedin youtube Powered by On this page Pre-Requisites Trigger broadcast Add file attachment (for email) | 2026-01-13T08:48:42 |
https://docs.suprsend.com/docs/python-create-user-profile | Manage Users - 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 Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Integrate Python SDK Manage Users Objects Send and Track Events Trigger Workflow from API Tenants Lists Broadcast Node.js SDK Java SDK Go SDK SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Python SDK Manage Users Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Python SDK Manage Users OpenAI Open in ChatGPT Create, update, & manage user profiles and communication channels using Python SDK methods. OpenAI Open in ChatGPT How Suprsend identifies a user SuprSend identifies users with immutable distinct_id . It’s best to map the same identifier in your DB with distinct_id in SuprSend. Do not use identifiers that can be changed like email or phone number. You can view synced users by searching distinct_id on Users page . Create User To create a new user or to update an existing user, you’ll have to fetch user instance. Call supr_client.user.get_instance to instantiate user object. Copy Ask AI import suprsend supr_client = suprsend.Suprsend( "workspace_key" , "workspace_secret" ) distinct_id = "distinct_id" # Unique identifier of user in your application # Instantiate User profile user = supr_client.users.get_edit_instance(distinct_id) Edit User To Edit user, you need to first fetch user instance, call all the update methods and save changes using users.async_edit method. Request Response Copy Ask AI #Fetch user instance user = supr_client.users.get_edit_instance( "_distinct_id_" ) #Call user update methods user.set_timezone( "America/Los_Angeles" ) user.set( "name" , "John Doe" ) #Save Changes res = supr_client.users.async_edit(user) print (res) Here’s a list of all edit methods: Add User Channels Add communication channels on which you want to notify user. Push sand Inbox tokens are automatically tracked on user identification when the corresponding frontend SDK is integrated. Other channels (Email, SMS, Slack, MS teams, WhatsApp) need to be explicitly set in user profile. Use user.add_* method(s) to add user channels. python Copy Ask AI # Add channel details to user-instance. Call relevant add_* methods user.add_email( " [email protected] " ) # - To add Email user.add_sms( "+15555555555" ) # - To add SMS user.add_whatsapp( "+15555555555" ) # - To add WhatsApp user.add_androidpush( "__android_push_fcm_token__" ) user.add_iospush( "__iospush_token__" ) # - To add Slack using email user.add_slack( { "email" : " [email protected] " , "access_token" : "xoxb-XXXXXXXX" }) # - To add Slack if slack member_id is known user.add_slack( { "user_id" : "U03XXXXXXXX" , "access_token" : "xoxb-XXXXXXXX" }) # - To add Slack channel user.add_slack( { "channel_id" : "CXXXXXXXX" , "access_token" : "xoxb-XXXXXXXX" }) # - To add Slack incoming webhook user.add_slack( { "incoming_webhook" : { "url" : "https://hooks.slack.com/services/TXXXX/BXXXX/XXXXXXX" } }) # - To add MS teams user or channel using conversation_id user.add_ms_teams( { "tenant_id" : "c1981ab2-9aaf-xxxx-xxxx" , "service_url" : "https://smba.trafficmanager.net/amer" , "conversation_id" : "19:c1524d7c-a06f-456f-8abe-xxxx" }) # - To add MS teams user using user_id user.add_ms_teams( { "tenant_id" : "c1981ab2-9aaf-xxxx-xxxx" , "service_url" : "https://smba.trafficmanager.net/amer" , "user_id" : "29:1nsLcmJ2RKtYH6Cxxxx-xxxx" }) # - To add MS teams using incoming webhook user.add_ms_teams( { "incoming_webhook" : { "url" : "https://wnk1z.webhook.office.com/webhookb2/XXXXXXXXX" } }) Remove User Channels Use user.remove_* method(s) to remove channels. python Copy Ask AI # Remove channel details from user-instance. Call relevant remove_* methods user.remove_email( " [email protected] " ) user.remove_sms( "+15555555555" ) user.remove_whatsapp( "+15555555555" ) user.remove_androidpush( "__android_push_fcm_token__" ) user.remove_iospush( "__iospush_token__" ) # - To remove Slack email user.remove_slack( { "email" : " [email protected] " , "access_token" : "xoxb-XXXXXXXX" }) # - To remove Slack if slack member_id is known user.remove_slack( { "user_id" : "U03XXXXXXXX" , "access_token" : "xoxb-XXXXXXXX" }) # - To remove Slack channel user.remove_slack( { "channel_id" : "CXXXXXXXX" , "access_token" : "xoxb-XXXXXXXX" }) # - To remove Slack incoming webhook user.remove_slack( { "incoming_webhook" : { "url" : "https://hooks.slack.com/services/TXXXX/BXXXX/XXXXXXX" } }) # - To remove MS teams user or channel using conversation_id user.remove_ms_teams( { "tenant_id" : "c1981ab2-9aaf-xxxx-xxxx" , "service_url" : "https://smba.trafficmanager.net/amer" , "conversation_id" : "19:c1524d7c-a06f-456f-8abe-xxxx" }) # - To remove MS teams user using user_id user.remove_ms_teams( { "tenant_id" : "c1981ab2-9aaf-xxxx-xxxx" , "service_url" : "https://smba.trafficmanager.net/amer" , "user_id" : "29:1nsLcmJ2RKtYH6Cxxxx-xxxx" }) # - To remove MS teams using incoming webhook user.remove_ms_teams( { "incoming_webhook" : { "url" : "https://wnk1z.webhook.office.com/webhookb2/XXXXXXXXX" } }) Remove Channel types This method will delete/unset all values in specified channel for user (ex: remove all emails attached to user). python Copy Ask AI # --- To delete all emails associated with user user.unset( "$email" ) user.unset([ "$email" , "$sms" , "$whatsapp" ]) # Supported channel keys are: # $email, $whatsapp, $sms, $androidpush, $iospush, $webpush, $slack, $ms_teams Set Preferred language If you want to send notification in user’s preferred language, you can set it by passing language code in this method. This is useful especially for the applications which offer vernacular or multi-lingual support. Copy Ask AI user.set_preferred_language( "en" ) Set preferred timezone You can set timezone of user using this method. Value for timezone must be from amongst the IANA timezones . Copy Ask AI user.set_timezone( "America/Los_Angeles" ) Set Set is used to add custom user properties. It is an upsert function, meaning any existing property value with the same key will be overwritten on subsequent updates. Copy Ask AI user.set(key, value) user.set( "name" , "John Doe" ) user.set({ key1: value1, key2: value2 }) user.set({ "name" : "John Doe" , "city" : "San Francisco" }) Set Once Works just like user.set, except it will not override already existing property values. This is useful for properties like first_login_date. Copy Ask AI user.set_once(key, value) user.set_once( "first_login" , "2021-11-02" ) user.set_once({ key1: value1, key2: value2 }) user.set_once({ "first_login" : "2021-11-02" , "signup_date" : "2021-11-02" }) Unset Unset is used to remove a property key. Copy Ask AI user.unset(key) user.unset( "name" ) user.unset([key1, key2]) user.unset([ "name" , "city" ]) Append This method will append a value to the array list. Copy Ask AI user.append(key, value) user.append( "played_games" , "game_1" ) user.append({ key1: value1, key2: value2 }) user.append({ "played_games" : "game_1" , "liked_games" : "game_2" }) Remove This method will remove a value from the array list. Copy Ask AI user.remove(key, value) user.remove( "played_games" , "game_1" ) user.remove({ key1: value1, key2: value2 }) user.remove({ "played_games" : "game_1" , "liked_games" : "game_2" }) Increment Increase or decrease integer values on consecutive action, like login count. To reduce a property, provide a negative number for the value. Copy Ask AI user.increment(key, value) user.increment( "login_count" , 1 ) user.increment({ key1: value1, key2: value2 }) user.increment({ "login_count" : 1 , "order_count" : 1 }) After calling add*/remove*/unset methods, don’t forget to call users.async_edit() since user edit is async update and the changes will be sent to SuprSend only after calling this method. Bulk Update users Bulk operations use UPSERT to create or update users. There isn’t any limit on number-of-records that can be added to bulk_users instance. Use .append() on bulk_users instance to add however-many-records to call in bulk. Rate limit: 1000 requests per second. The SDK automatically chunks requests based on the size of the payload. So, you don’t need to worry about these rate limits while using bulk operations. Request Response Copy Ask AI # Create bulk instance bulk_ins = supr_client.users.get_bulk_edit_instance() # Prepare multiple users edit instance distinct_id1 = "__distinct_id1__" # User 1 u1 = supr_client.users.get_edit_instance(distinct_id1) u1.add_email( " [email protected] " ) distinct_id2 = "__distinct_id2__" # User 2 u2 = supr_client.users.get_edit_instance(distinct_id2) u2.add_email( " [email protected] " ) # Append users to the bulk instance bulk_ins.append(u1, u2) # ------- res = bulk_ins.save() print (res) Bulk API supported in SDK version 0.2.0 and above: Bulk API is supported in SuprSend python-sdk version 0.2.0 and above. If you are using an older version, please upgrade to the latest SDK version. Get user details Request Response Copy Ask AI res = supr_client . users . get ( "_distinct_id_" ) print ( res ) Delete user Request Response Copy Ask AI res = supr_client . users . delete ( "_distinct_id_" ) print ( res ) Get list of objects subscribed by user You can pass optional query parameters - limit , before , after Request Response Copy Ask AI res = supr_client . users . get_objects_subscribed_to ( "_distinct_id_" , { "after" : "01JJW6HXXXXPB59ARDW85G0KN" , "limit" : 1 }) print ( res ) Get lists subscribed by user You can pass optional query parameters - limit , before , after Request Response Copy Ask AI res = supr_client . users . get_lists_subscribed_to ( "_distinct_id_" , { "after" : "01JJW6HXXXXPB59ARDW85G0KN" , "limit" : 1 }) print ( res ) Was this page helpful? Yes No Suggest edits Raise issue Previous Objects Create, update, & manage objects and their subscriptions using Python SDK methods. Next ⌘ I x github linkedin youtube Powered by On this page How Suprsend identifies a user Create User Edit User Bulk Update users Get user details Delete user Get list of objects subscribed by user Get lists subscribed by user | 2026-01-13T08:48:42 |
https://docs.suprsend.com/docs/java-create-user-profile | Manage Users - 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 Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Node.js SDK Java SDK Integrate Java SDK Manage Users Objects Send and Track Events Trigger Workflow from API Tenants Lists Broadcast Go SDK SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Java SDK Manage Users Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Java SDK Manage Users OpenAI Open in ChatGPT Manage user profiles and communication channels programmatically with the Java SDK. OpenAI Open in ChatGPT How Suprsend identifies a user SuprSend identifies users with immutable distinct_id . It’s best to map the same identifier in your DB with distinct_id in SuprSend. Do not use identifiers that can be changed like email or phone number. You can view synced users by searching distinct_id on Users page . Please note: you cannot change a user’s id once it has been set, so we recommend you use a non-transient id like a primary key rather than a phone number or email address. Create User To create a new user or to update an existing user, you’ll have to fetch user instance. Call supr_client.user.get_instance to instantiate user object. Request Response Copy Ask AI import org.json.JSONObject; import suprsend.Suprsend; import suprsend.Subscriber; public class UserEdit { public static void main ( String [] args ) throws Exception { getInstance (); } private static Subscriber getSuprClient () throws SuprsendException { Suprsend suprsendClient = new Suprsend ( "_workspace_key_" , "_workspace_secret_" ); return suprsendClient; } private static Subscriber getInstance () throws SuprsendException { Suprsend suprsendClient = getSuprClient (); // Instiantiate user String distinctId = "_distinct_id_" ; Subscriber user = suprClient . user . getInstance (distinctId); return user; } } Edit User To Edit user, you need to first fetch user instance, call all the update methods and save changes using user.save method. Request Copy Ask AI import org.json.JSONObject; import suprsend.Suprsend; import suprsend.Subscriber; public class UserEdit { public static void updateProfile () throws Exception { Suprsend suprsendClient = getSuprClient (); // User Edit Instance String distinctID = "_distinct_id_" ; Subscriber user = suprsendClient . user . getInstance (distinctID); // Edit Helper methods user . addEmail ( " [email protected] " ); user . setTimezone ( "America/New_York" ); // Save JSONObject response = user . save (); System . out . println (response); } } Here’s a list of all edit methods: Add User Channels Add communication channels on which you want to notify user. Push sand Inbox tokens are automatically tracked on user identification when the corresponding frontend SDK is integrated. Other channels (Email, SMS, Slack, MS teams, Whatsapp) need to be explicitly set in user profile. Use user.add_* method(s) to add user channels. Request Copy Ask AI // User Edit Instance String distinctID = "_distinct_id_" ; Subscriber user = suprsendClient . user . getInstance (distinctID); // Add Email user . addEmail ( " [email protected] " ); //Add SMS user . addSms ( "+919999999999" ); //Add Whatsapp user . addWhatsapp ( "+919999999999" ); // Add Androidpush token.Pass the vendor as 2nd param. user . addAndroidpush ( "androidpush_fcm_token__" , "fcm" ); // Add iospush token user . addIospush ( "__iospush_apns_token__" ); // Add Slack using user email id JSONObject slackIdent = new JSONObject () . put ( "access_token" , "xoxb-XXXXXXXX" ) . put ( "email" , " [email protected] " ); user . addSlack (slackIdent); // Add Slack using member_id of the user if known JSONObject slackIdent = new JSONObject () . put ( "access_token" , "xoxb-XXXXXXXX" ) . put ( "user_id" , "U03XXXXXXXX" ); user . addSlack (slackIdent); // Add Slack channel_id JSONObject slackIdent = new JSONObject () . put ( "access_token" , "xoxb-XXXXXXXX" ) . put ( "channel_id" , "C04XXXXXXXX" ); user . addSlack (slackIdent); // Add Slack incoming webhook JSONObject slackIdent = new JSONObject () . put ( "incoming_webhook" , new JSONObject (). put ( "url" , "https://hooks.slack.com/services/TXXXX/BXXXX/XXXXXXX" )) user . addSlack (slackIdent); // Add Webpush token json (VAPID) JSONObject webpush = new JSONObject () . put ( "endpoint" , "__end_point__" ) . put ( "expirationTime" , "" ) . put ( "keys" , new JSONObject () . put ( "p256dh" , "__p256dh__" ) . put ( "auth" , "__auth_key__" )); user . addWebpush (webpush, "vapid" ); Remove User Channels Use user.remove_* method(s) to remove channels. Request Copy Ask AI // Remove Email user . removeEmail ( " [email protected] " ); //Remove SMS user . removeSms ( "+919999999999" ); //Remove Whatsapp user . removeWhatsapp ( "+919999999999" ); // Remove Androidpush token.Pass the vendor as 2nd param. user . removeAndroidpush ( "androidpush_fcm_token__" , "fcm" ); // Remove iospush token user . removeIospush ( "__iospush_apns_token__" ); // Remove Slack using user email id JSONObject slackIdent = new JSONObject () . put ( "access_token" , "xoxb-XXXXXXXX" ) . put ( "email" , " [email protected] " ); user . removeSlack (slackIdent); // Remove Slack using member_id of the user if known JSONObject slackIdent = new JSONObject () . put ( "access_token" , "xoxb-XXXXXXXX" ) . put ( "user_id" , "U03XXXXXXXX" ); user . removeSlack (slackIdent); // Remove Slack channel_id JSONObject slackIdent = new JSONObject () . put ( "access_token" , "xoxb-XXXXXXXX" ) . put ( "channel_id" , "C04XXXXXXXX" ); user . removeSlack (slackIdent); // Remove Slack incoming webhook JSONObject slackIdent = new JSONObject () . put ( "incoming_webhook" , new JSONObject (). put ( "url" , "https://hooks.slack.com/services/TXXXX/BXXXX/XXXXXXX" )) user . removeSlack (slackIdent); // Remove Webpush token json (VAPID) JSONObject webpush = new JSONObject () . put ( "endpoint" , "__end_point__" ) . put ( "expirationTime" , "" ) . put ( "keys" , new JSONObject () . put ( "p256dh" , "__p256dh__" ) . put ( "auth" , "__auth_key__" )); user . removeWebpush (webpush, "vapid" ); Remove Channel Types This method will delete/unset all values in specified channel for user (ex: remove all emails attached to user). Request Copy Ask AI // --- To unset one channel, e.g. to delete all emails associated with user // -- Channel keys - ("$email","$whatsapp","$sms," $androidpush","$iospush","$webpush","$slack") user . unset ( "$email" ); // --- multiple channels can also be deleted in one call by passing argument as a list ArrayList < String > channels = new ArrayList < > ( Arrays . asList ( "$email" , "$slack" , "$androidpush" , "$iospush" , "$webpush" , "$whatsapp" )); user . unset (channels); Set Preferred language If you want to send notification in user’s preferred language, you can set it by passing language code in this method. This is useful especially for the applications which offer vernacular or multi-lingual support. Request Copy Ask AI // User Edit Instance String distinctID = "_distinct_id_" ; Subscriber user = suprsendClient . user . getInstance (distinctID); // Pass language in ISO 639-1 code user . setPreferredLanguage ( "es" ); Set preferred timezone You can set timezone of user using this method. Value for timezone must be from amongst the IANA timezones . Request Copy Ask AI // User Edit Instance String distinctID = "_distinct_id_" ; Subscriber user = suprsendClient . user . getInstance (distinctID); // Pass IANA timezone user . setTimezone ( "America/New_York" ); Set Set is used to add custom user properties. It is an upsert function, meaning any existing property value with the same key will be overwritten on subsequent updates. Request Copy Ask AI user . set (key, value) user . set ( "name" , "John Doe" ) user . set ({ key1 : value1, key2 : value2 }) user . set ({ "name" : "John Doe" , "city" : "San Francisco" }) Set Once Works just like user.set, except it will not override already existing property values. This is useful for properties like first_login_date. Copy Ask AI user . set_once (key, value) user . set_once ( "first_login" , "2021-11-02" ) user . set_once ({ key1 : value1, key2 : value2 }) user . set_once ({ "first_login" : "2021-11-02" , "signup_date" : "2021-11-02" }) Unset Unset is used to remove a property key. Copy Ask AI user . unset (key) user . unset ( "name" ) user . unset ([key1, key2]) user . unset ([ "name" , "city" ]) Append This method will append a value to the array list. Copy Ask AI user . append (key, value) user . append ( "played_games" , "game_1" ) user . append ({ key1 : value1, key2 : value2 }) user . append ({ "played_games" : "game_1" , "liked_games" : "game_2" }) Remove This method will remove a value from the array list. Copy Ask AI user . remove (key, value) user . remove ( "played_games" , "game_1" ) user . remove ({ key1 : value1, key2 : value2 }) user . remove ({ "played_games" : "game_1" , "liked_games" : "game_2" }) Increment Increase or decrease integer values on consecutive action, like login count. To reduce a property, provide a negative number for the value. Copy Ask AI user . increment (key, value) user . increment ( "login_count" , 1 ) user . increment ({ key1 : value1, key2 : value2 }) user . increment ({ "login_count" : 1 , "order_count" : 1 }) After calling add_*/remove_*/unset methods, don’t forget to call users.save() since user edit is async update and the changes will be sent to SuprSend only after calling this method. Bulk Update Users Bulk operations use UPSERT to create or update users. There isn’t any limit on number-of-records that can be added to bulk_users instance. Use .append() on bulk_users instance to add however-many-records to call in bulk. Rate limit: 1000 requests per second. The SDK automatically chunks requests based on the size of the payload. So, you don’t need to worry about these rate limits while using bulk operations. Request Response Copy Ask AI //Creating bulk instance BulkSubscribers bulkIns = suprClient . bulkUsers . newInstance (); // Prepare multiple users String distinctID1 = "__distinct_id1__" ; // User 1 User u1 = suprsendClient . user . getInstance (distinctID1); u1 . addEmail ( " [email protected] " ); String distinctID2 = "__distinct_id2__" ; // User 2 User u2 = suprsendClient . user . getInstance (distinctID2); u2 . addEmail ( " [email protected] " ); // --- use .append on bulk instance to add one or more records bulkIns . append (u1); bulkIns . append (u2); // OR bulkIns . append (u1, u2); // Save JSONObject response = bulkIns . save (); System . out . println (response); Bulk API supported in SDK version 0.2.0 and above: Bulk API is supported in SuprSend java-sdk version 0.2.0 and above. If you are using an older version, please upgrade to the latest SDK version. Get user details Fetch User by passing distinct_id Request Response Copy Ask AI String distinctId = "_distinct_id_" ; JSONObject res = suprClient . users . get (distinctId); System . out . println (response); Delete user Delete User by passing distinct_id . Delete action will take into immediate effect. Request Response Copy Ask AI String distinctId = "_distinct_id_" ; JSONObject res = suprClient . users . delete (distinctId); System . out . println (response); Get list of objects subscribed by user You can pass optional query parameters - limit , before , after Request Response Copy Ask AI String distinctId = "_distinct_id_" ; // optional params to pass limit (default=10) and cursor pointer for fetching the next set of results HashMap < String , Object > opts = new HashMap < String , Object > () { { put ( "limit" , 10 ); put ( "after" , "01HFS04E4J29KHPYRK7HT3YQQ5" ); } }; JSONObject res = suprClient . users . getObjectsSubscribedTo (distinctId, opts); System . out . println (response); Get lists subscribed by user You can pass optional query parameters - limit , before , after Request Response Copy Ask AI String distinctId = "_distinct_id_" ; // optional params to pass limit (default=10) and cursor pointer for fetching the next set of results HashMap < String , Object > opts = new HashMap < String , Object > () { { put ( "limit" , 10 ); put ( "after" , "01HFS04E4J29KHPYRK7HT3YQQ5" ); } }; JSONObject res = suprClient . users . getListsSubscribedTo (distinctId, opts); System . out . println (response); Was this page helpful? Yes No Suggest edits Raise issue Previous Objects Create, update, & manage objects and their subscriptions with Java SDK. Next ⌘ I x github linkedin youtube Powered by On this page How Suprsend identifies a user Create User Edit User Bulk Update Users Get user details Delete user Get list of objects subscribed by user Get lists subscribed by user 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 code: \"code\",\n p: \"p\",\n pre: \"pre\",\n span: \"span\",\n strong: \"strong\",\n ..._provideComponents(),\n ...props.components\n }, {Accordion, AccordionGroup, CodeBlock, CodeGroup, Heading, Note, Tip, Warning} = _components;\n if (!Accordion) _missingMdxReference(\"Accordion\", true);\n if (!AccordionGroup) _missingMdxReference(\"AccordionGroup\", true);\n if (!CodeBlock) _missingMdxReference(\"CodeBlock\", true);\n if (!CodeGroup) _missingMdxReference(\"CodeGroup\", true);\n if (!Heading) _missingMdxReference(\"Heading\", true);\n if (!Note) _missingMdxReference(\"Note\", true);\n if (!Tip) _missingMdxReference(\"Tip\", true);\n if (!Warning) _missingMdxReference(\"Warning\", true);\n return _jsxs(_Fragment, {\n children: [_jsx(Heading, {\n level: \"2\",\n id: \"how-suprsend-identifies-a-user\",\n children: \"How Suprsend identifies a user\"\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"SuprSend identifies users with immutable \", _jsx(_components.code, {\n children: \"distinct_id\"\n }), \". It’s best to map the same identifier in your DB with \", _jsx(_components.code, {\n children: \"distinct_id\"\n }), \" in SuprSend. Do not use identifiers that can be changed like email or phone number. You can view synced users by searching \", _jsx(_components.code, {\n children: \"distinct_id\"\n }), \" on \", _jsx(_components.a, {\n href: \"https://app.suprsend.com/en/production/users\",\n children: \"Users page\"\n }), \".\"]\n }), \"\\n\", _jsx(Note, {\n children: _jsxs(_components.p, {\n children: [_jsx(_components.strong, {\n children: \"Please note:\"\n }), \" you cannot change a user’s id once it has been set, so we recommend you use a non-transient id like a primary key rather than a phone number or email address.\"]\n })\n }), \"\\n\", _jsx(Heading, {\n level: \"2\",\n id: \"create-user\",\n children: \"Create User\"\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"To create a new user or to update an existing user, you’ll have to fetch user instance. Call \", _jsx(_components.code, {\n children: \"supr_client.user.get_instance\"\n }), \" to instantiate user object.\"]\n }), \"\\n\", _jsxs(CodeGroup, {\n children: [_jsx(CodeBlock, {\n filename: \"Request\",\n numberOfLines: \"23\",\n language: \"java\",\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: \"java\",\n children: _jsxs(_components.code, {\n language: \"java\",\n numberOfLines: \"23\",\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: \"import\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" org.json.JSONObject;\"\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: \"import\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" suprsend.Suprsend;\"\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: \"import\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" suprsend.Subscriber;\"\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: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \"public\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \" class\"\n }), _jsx(_components.span, {\n style: {\n color: \"#953800\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" UserEdit\"\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: \" public\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \" static\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" void\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \" main\"\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\": \"#4EC9B0\"\n },\n children: \"String\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"[] \"\n }), _jsx(_components.span, {\n style: {\n color: \"#953800\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \"args\"\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\": \"#569CD6\"\n },\n children: \"throws\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" Exception\"\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: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \" getInstance\"\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\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \" private\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \" static\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" Subscriber\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \" getSuprClient\"\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\": \"#569CD6\"\n },\n children: \"throws\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" SuprsendException\"\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: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" Suprsend\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" suprsendClient\"\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\": \"#C586C0\"\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\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \" return\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" suprsendClient;\"\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\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \" private\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \" static\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" Subscriber\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \" getInstance\"\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\": \"#569CD6\"\n },\n children: \"throws\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" SuprsendException\"\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: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" Suprsend\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" suprsendClient\"\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: \" getSuprClient\"\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: \" // Instiantiate user\"\n })\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" String\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" distinctId\"\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: \" \\\"_distinct_id_\\\"\"\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\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" Subscriber\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" user\"\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\": \"#9CDCFE\"\n },\n children: \" suprClient\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \".\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \"user\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \".\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \"getInstance\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"(distinctId);\"\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: \" return\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" 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\", _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\"]\n })\n })\n }), _jsx(CodeBlock, {\n filename: \"Response\",\n numberOfLines: \"14\",\n language: \"java\",\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: \"java\",\n children: _jsxs(_components.code, {\n language: \"java\",\n numberOfLines: \"14\",\n children: [_jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#6E7781\",\n \"--shiki-dark\": \"#6A9955\"\n },\n children: \"// Response structure\"\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: \" \\\"success\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \":\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0550AE\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \" true\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \", \"\n }), _jsx(_components.span, {\n style: {\n color: \"#6E7781\",\n \"--shiki-dark\": \"#6A9955\"\n },\n children: \"// if true, request was accepted.\"\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: \" \\\"status\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \":\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"success\\\"\"\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: \" \\\"status_code\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \":\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0550AE\",\n \"--shiki-dark\": \"#B5CEA8\"\n },\n children: \" 202\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \", \"\n }), _jsx(_components.span, {\n style: {\n color: \"#6E7781\",\n \"--shiki-dark\": \"#6A9955\"\n },\n children: \"// http status code\"\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: \" \\\"message\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \":\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"OK\\\"\"\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: \"#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: \" \\\"success\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \":\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0550AE\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \" false\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \", \"\n }), _jsx(_components.span, {\n style: {\n color: \"#6E7781\",\n \"--shiki-dark\": \"#6A9955\"\n },\n children: \"// error will be present in message\"\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: \" \\\"status\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \":\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"fail\\\"\"\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: \" \\\"status_code\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \":\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0550AE\",\n \"--shiki-dark\": \"#B5CEA8\"\n },\n children: \" 500\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \", \"\n }), _jsx(_components.span, {\n style: {\n color: \"#6E7781\",\n \"--shiki-dark\": \"#6A9955\"\n },\n children: \"// http status code\"\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: \" \\\"message\\\"\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#C586C0\"\n },\n children: \":\"\n }), _jsx(_components.span, {\n style: {\n color: \"#0A3069\",\n \"--shiki-dark\": \"#CE9178\"\n },\n children: \" \\\"error message\\\"\"\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\"]\n })\n })\n })]\n }), \"\\n\", _jsx(Heading, {\n level: \"2\",\n id: \"edit-user\",\n children: \"Edit User\"\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"To Edit user, you need to first fetch user instance, call all the update methods and save changes using \", _jsx(_components.code, {\n children: \"user.save\"\n }), \" method.\"]\n }), \"\\n\", _jsx(CodeGroup, {\n children: _jsx(CodeBlock, {\n filename: \"Request\",\n numberOfLines: \"21\",\n language: \"java\",\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: \"java\",\n children: _jsxs(_components.code, {\n language: \"java\",\n numberOfLines: \"21\",\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: \"import\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" org.json.JSONObject;\"\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: \"import\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" suprsend.Suprsend;\"\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: \"import\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \" suprsend.Subscriber;\"\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: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \"public\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \" class\"\n }), _jsx(_components.span, {\n style: {\n color: \"#953800\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" UserEdit\"\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\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \" public\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#569CD6\"\n },\n children: \" static\"\n }), _jsx(_components.span, {\n style: {\n color: \"#CF222E\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" void\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \" updateProfile\"\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\": \"#569CD6\"\n },\n children: \"throws\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" Exception\"\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: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" Suprsend\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" suprsendClient\"\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: \" getSuprClient\"\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: \" // User Edit Instance\"\n })\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" String\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" distinctID\"\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: \" \\\"_distinct_id_\\\"\"\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: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" Subscriber\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" user\"\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\": \"#9CDCFE\"\n },\n children: \" suprsendClient\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \".\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \"user\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \".\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \"getInstance\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"(distinctID);\"\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: \" // Edit Helper methods\"\n })\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" user\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \".\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \"addEmail\"\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: \"\\\"example@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: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" user\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \".\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \"setTimezone\"\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\", _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: \" // Save\"\n })\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \" JSONObject\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\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\": \"#9CDCFE\"\n },\n children: \" user\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \".\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \"save\"\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: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" System\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \".\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \"out\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \".\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \"println\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \"(response);\"\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\"]\n })\n })\n })\n }), \"\\n\", _jsx(_components.p, {\n children: \"Here’s a list of all edit methods:\"\n }), \"\\n\", _jsxs(AccordionGroup, {\n children: [_jsxs(Accordion, {\n title: \"Add User Channels\",\n children: [_jsx(_components.p, {\n children: \"Add communication channels on which you want to notify user. Push sand Inbox tokens are automatically tracked on user identification when the corresponding frontend SDK is integrated. Other channels (Email, SMS, Slack, MS teams, Whatsapp) need to be explicitly set in user profile.\"\n }), _jsxs(_components.p, {\n children: [\"Use \", _jsx(_components.code, {\n children: \"user.add_*\"\n }), \" method(s) to add user channels.\"]\n }), _jsx(CodeGroup, {\n children: _jsx(CodeBlock, {\n filename: \"Request\",\n numberOfLines: \"50\",\n language: \"java\",\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: \"java\",\n children: _jsxs(_components.code, {\n language: \"java\",\n numberOfLines: \"50\",\n children: [_jsx(_components.span, {\n className: \"line\",\n children: _jsx(_components.span, {\n style: {\n color: \"#6E7781\",\n \"--shiki-dark\": \"#6A9955\"\n },\n children: \"// User Edit Instance\"\n })\n }), \"\\n\", _jsxs(_components.span, {\n className: \"line\",\n children: [_jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \"String\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" distinctID\"\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: \" \\\"_distinct_id_\\\"\"\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: \"#1F2328\",\n \"--shiki-dark\": \"#4EC9B0\"\n },\n children: \"Subscriber\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \" user\"\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\": \"#9CDCFE\"\n },\n children: \" suprsendClient\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \".\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#9CDCFE\"\n },\n children: \"user\"\n }), _jsx(_components.span, {\n style: {\n color: \"#1F2328\",\n \"--shiki-dark\": \"#D4D4D4\"\n },\n children: \".\"\n }), _jsx(_components.span, {\n style: {\n color: \"#8250DF\",\n \"--shiki-dark\": \"#DCDCAA\"\n },\n children: \"getInstance\"\n }), _jsx(_components.span, { | 2026-01-13T08:48:42 |
https://docs.suprsend.com/reference/cli-category-translation-list | List Category Translations - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Preference Category List Category Translations Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Preference Category List Category Translations OpenAI Open in ChatGPT List available translation locales for preference categories. OpenAI Open in ChatGPT Syntax Copy Ask AI suprsend category translation list [flags] Flags Flag Description Default -h, --help Show help for the command – -w, --workspace string Workspace to list translation locales from staging Example Copy Ask AI # List translation locales in staging workspace (default) suprsend category translation list # List translation locales in production workspace suprsend category translation list --workspace production Related documentation Category Translations How to manage Category translations Was this page helpful? Yes No Suggest edits Raise issue Previous Pull Category Translations Fetch category translations from SuprSend workspace to local JSON files Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example Related documentation | 2026-01-13T08:48:42 |
https://docs.suprsend.com/docs/python-tenants | Tenants - 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 Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Integrate Python SDK Manage Users Objects Send and Track Events Trigger Workflow from API Tenants Lists Broadcast Node.js SDK Java SDK Go SDK SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Python SDK Tenants Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Python SDK Tenants OpenAI Open in ChatGPT Learn how to create, update, fetch, & list tenants using Python SDK. OpenAI Open in ChatGPT Tenants (previously named as brands) are used for white labeling notifications, personalizing template content or capturing admin preferences for another entity/organization. Tenants are workspace-level entities and by default, a tenant with tenant_id="default" (representing your organization) is created your workspace. Read more about tenants here . Create / Update tenant Request Response Copy Ask AI from suprsend import Suprsend, SuprsendAPIException supr_client = Suprsend( "workspace_key" , "workspace_secret" ) # Define tenant ID and prepare tenant payload tenant_id = "tenant_01" tenant_payload = { "tenant_name" : "ABC Company" , "logo" : "https://company_logo_image.png" , "primary_color" : "#ff0000" , # ---- Optional Parameters ------- "secondary_color" : "#00ff00" , "tertiary_color" : "#0000ff" , "timezone" : "America/New_York" , "blocked_channels" : [ "email" ], # These channels will be skipped for sending notification to recipients when triggering for this tenant. "social_links" : { "website" : "https://suprsend.com" , "facebook" : "" , "linkedin" : "" , "x" : "" , "instagram" : "" , "medium" : "" , "discord" : "" , "telegram" : "" , "youtube" : "" , "tiktok" : "" , }, "embedded_preference_url" : "" , # In-product Notification centre link for capturing user preferences. "properties" : { "prop1" : "value1" , "prop2" : { "prop3" : [ "value2" ] } } } try : response = supr_client.tenants.upsert(tenant_id, tenant_payload) print (response) except SuprsendAPIException as ex: print (ex) Field Description tenant_id (mandatory) Unique identifier for the tenant (max 64 characters, case insenstive). It can contain characters [a-z0-9_\-] that is alphanumeric characters, \_(underscore) and -(hyphen). tenant_name (*mandatory) Tenant’s display name in a human-readable format logo Logo URL, used in email headers or on hosted preference page for per-tenant branding. primary_color, secondary_color, tertiary_color Tenant branding colors- used in template design or hosted preference page for per-tenant branding. timezone The primary timezone for most tenants’ recipients. Used as a fallback when sending notifications in the recipient’s timezone and timezone is not set in recipient profile. blocked_channels These channels will be skipped for sending notification to recipients when triggering for this tenant. Used to apply channel level opt-outs at admin level. social_links URLs of the tenant’s social media accounts. embedded_preference_url properties Custom properties of the tenant like address, to be used in template or workflow. All properties of the tenant can be referred as {{$brand.prop}} (handlebars) or data\["tenant"\].prop in JSONNET format. Get tenant Request Response Copy Ask AI from suprsend import Suprsend, SuprsendAPIException supr_client = Suprsend( "workspace_key" , "workspace_secret" ) try : response = supr_client.tenants.get( "tenant_id" ) print (response) except SuprsendAPIException as ex: print (ex) List tenants By default, limit=20 . The maximum value for limit is 1000 . Request Response Copy Ask AI from suprsend import Suprsend, SuprsendAPIException supr_client = Suprsend( "workspace_key" , "workspace_secret" ) try : params = { "limit" : 20 , "offset" : 0 } response = supr_client.tenants.list( ** params) print (response) except SuprsendAPIException as ex: print (ex) Was this page helpful? Yes No Suggest edits Raise issue Previous Lists Manage subscriber lists with Python SDK: create/update list, add/remove/replace users. Next ⌘ I x github linkedin youtube Powered by On this page Create / Update tenant Get tenant List tenants | 2026-01-13T08:48:42 |
https://www.youtube.com/channel/UC3_cJM5UxFUYCi3n39vvvCw | fine - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:48:42 |
https://dev.to/szabgab/perl-weekly-597-happy-new-year-1ofm | Perl Weekly #597 - Happy New Year! - 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 Gabor Szabo Posted on Jan 2, 2023 • Originally published at perlweekly.com Perl Weekly #597 - Happy New Year! # perl # news # programming perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? Originally published at Perl Weekly 597 Hi there! I hope you had a successful 2022 and you are ready for the next year. I certainly have lots of plans. As always. They are also changing a lot all the time. One of them is a new course I am working on called OSDC - Open Source Development Course . It is a hands-on course that covers git/GitHub/GitLab/Testing/CI using real-world open source projects. It is also not only a plan, I am starting the first session next Sunday. It will be given in Hebrew. For the course I started to collect Open Source projects developed by corporations . There are a few where the product is open source such as Redis and Elastic . There are others where the company shares some of its code as open source such as Netflix, Facebook, or Booking.com. I'd like to ask for your help. Look around at your company and maybe other companies and let me know which one shares projects using an Open Source license. It would help me and the participants of this courses a lot. For the purpose of the course and for my collection the programming languages don't matter. However, if you can also point out Perl-based projects, that would be even better. Then I could feature these projects in the newsletter. Let's start now with one I already found: pakket by Booking.com is an Unopinionated Meta-Packaging System that allows you to manage dependencies. It works by trying to avoid work. Enjoy your year! -- Your editor: Gabor Szabo. Articles Set HTTP headers with WWW-Mechanize Perl Suggestion: Improve metacpan title in Google SEO Yuki is trying hard to improve the ranking of MetaCPAN pages, but does he talk to the MetaCPAN developers. Did he send a pull-request to implement this? If not Yuki, then will someone pick-up the idea and implement it? MetaCPAN most voted distributions in 2022 This is the metacpan most voted distributions in 2022 13 best perl distributions created at 2022 (metacpan rating) This list contains distributions created at 2022 10 best Perl questions at stackoverflow in 2022 This is the ten most rated questions at 2022 Stack Overflow. SemVer but with Extra Steps SemVer is Semantic Versioning. Versions have three parts: MAJOR, MINOR, and PATCH. PSA: Changing your b.p.o password is recommended Aristotle has further improved blogs.Perl.org and now he invites the users to update their passwords to ensure that they are secure. Christmas Fractal Christmas Tree The last entry of the 2022 Perl Advent Calendar - a Christmas tree. Reviews and New Year Views, reactions, and followers on DEV in 2022 A little end of year review on my very short year on DEV. Basically 40 days. Happy New Year! Marketing Committee Achievements in 2022 I am glad they published these accomplishments New Years Resolution: 52 posts in 2023 I am looking forward the articles of JONASBN . CPAN List of new CPAN distributions - Dec 2022 The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 198 Welcome to a new week with a couple of fun tasks "Max Gap" and "Prime Count". If you are new to the weekly challenge then why not join us and have fun every week. For more information, please read the FAQ . RECAP - The Weekly Challenge - 197 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Move Zero" and "Wiggle Sort" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Zero Wiggle Lots of Raku gems in one place, thanks for sharing knowledge with us every week. PWC197 - Move Zero Well documented solution as always. Thanks for sharing. PWC197 - Wiggle Sort Interesting task analysis ends up with easy and simple solution. Well done. The Weekly Challenge 197 Elegant yet powerful Perl solutions shared by James week after week. Plenty to learn from his contributions. Perl Weekly Challenge 197: Move Zero and Wiggle Sort Once again Laurent came up with a clean one-liner, worth checking out. Keep it up great work. Lists everywhere! Smart hack to solve the Wiggle Sort. Cool, thanks for sharing. Perl Weekly Challenge 197 Even the complex task like Wiggle Sort is done with ease in one-liner (kind of). Nice work. The Perl Weekly Challege #197 Simply loved the narrative form of blog. You end up with pretty solution in no time. Great work, keep it up. Sorting Lists One place for both Perl and Python fans. Plenty to keep you busy. PWC 197 Very impressive one-liner both in Perl and Raku. Nice work, keep it up. Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . Perl Jobs by Perl Careers Adventure! Senior Perl roles in Malaysia, Dubai and Malta Clever folks know that if you’re lucky, you can earn a living and have an adventure at the same time. Enter our international client: online trading is their game, and they’re looking for Perl folks with passion, drive, and an appreciation for new experiences. Senior Perl Developer with Cross-Trained Chops. UK Remote Perl Role Sure, you’ve got Perl chops for days, but that’s not all you can do — and that’s why our client wants to meet you. They’re looking for senior Perl developers, Node engineers, and those with mighty Python and SQL skills to lead their team. Cross-trained team members are their sweet spot, and whether you’re cross-trained yourself or are open to the possibility, this may be your perfect role. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe. Remote UK Perl Role A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. Perl Developer and Business Owner? Remote Perl role in UK & EU Our clients run a job search engine that has grown from two friends with an idea to a site that receives more than 10 million visits per month. They're looking for a Perl pro with at least three years of experience with high-volume and high-traffic apps and sites, a solid understanding of Object-Oriented Perl (perks if that knowledge includes Moose), SQL/MySQL and DBIx::Class. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #755 - Does TIOBE help Perl? # perl # news # programming Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming 💎 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:48:42 |
https://dev.to/szabgab/perl-weekly-592-perl-blogging-725 | Perl 🐪 Weekly #592 - Perl Blogging? - 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 Gabor Szabo Posted on Nov 28, 2022 • Edited on Feb 24, 2025 • Originally published at perlweekly.com Perl 🐪 Weekly #592 - Perl Blogging? # perl # news # programming perl-weekly (153 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 149 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution Originally published at Perl Weekly 592 Hi there, We all know not many people blog about Perl anymore. Are we doing anything to get it back on track? Well, unfortunately again, nothing is happening on that front either. But, hey, there is still hope and handful of Perl fans doing their best. One of them is our chief editor, Gabor Szabo . He has been running Perl Maven for years now and many of us benefitted from his work. He recently started blogging on Dev.To . I request all the Perl fans to follow him and like blog post. I didn't have the account there before so I decided to create personal account . Although I no longer blog at all but this is going to change soon. Earlier I used to blog on blogs.perl.org but then I moved to The Weekly Challenge recently. Talking about blogging, how can I miss one name, Flavio Poletti ? He has been blogging daily for years now. Feel free to check out his work here . Kudos to him for his effort. I would like to mention another name, Olaf Alders , for his hard work in reviving the good old friend, Perl Advent Calendar . Julien has been helping him in the project too. I remember there was a call for papers by him. If you have time and something to share about your favourite CPAN module then please do contribute. I have booked one slot for myself for this year Advent Calendar . Hopefully, I will submit my article on time. Last but not the least, I would like to thank all the members of Team PWC for creating friendly and positive vibes for years now. As of today, they have published 3000+ blog posts sharing creative ideas and solutions. If you are interested then please do checkout blog posts . Enjoy the rest of the newsletter. -- Your editor: Mohammad S. Anwar. Announcements This Week in PSC (088) Brief update about the Perl Steering Council latest meetup. Sponsors Personalized investment with Torto AI Any investment in the stock market is partially based on objective data (e.g. P/E ratio) and partially on the subjective world-view of the investor (expected changes in inflation, politics, weather etc.) torto.ai works on providing you a platform where you can easily combine these aspects and find the investment that most suitable for your expectation. Articles Two-factor authentication (2FA) in Perl with TOTP algorithm (Microsoft or Google Authenticator or others) Get the insights of 2FA and how Perl can help you deal with it. Speaking of certificates and Root CAs... Preparing for Advent of Code 2022 Samir sharing his plan for this year Advent of Code. Mojolicious cheatsheet For Mojolicious fan, please checkout this cheatsheet. Kephra: Select All If you are following post about Kephra then this is for you to explore further. Web Feature Switch Best Practices Curtis is back, well organised blog post. Highly Recommended. Git worktree Nice little introduction to git worktree. Highly recommended if you are git fan. An objective criteria for deprecating community platforms Take a look at the history of community platforms. Interesting ... Advent of Code 2022 is coming Never played with Advent of Code. If time permits, I will give it a go. Thanks for sharing. CPAN Playing with MQTT Do you know MQTT? I didn't. Thanks for sharing the knowledge. The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 193 Welcome to a new week with a couple of fun tasks: "Binary String" and "Odd String". If you are new to the weekly challenge, why not join us and have fun every week? For more information, please read the FAQ . RECAP - The Weekly Challenge - 192 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Binary Flip" and "Equal Distribution" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Flipping to Redistribute Playing with raw bits makes it fun. Keep it up great work. Flipped Equilibrium Cool discussion of the task and solutions in Perl, Raku and Haskell. Worth checking it out. Thanks for sharing. Frosting a cake without flipping the spatula Plenty of different approaches discussed from the performance point of view. Great work, keep it up. Liberté, Égalité, Fraternité Colin's style of task analysis opens up new angle to it. Highly recommended. PWC192 - Binary Flip Bitwise operation in full play in Perl and Raku. Nice work. PWC192 - Equal Distribution Task analysis made it so simple to follow. Implementation in Perl and Raku is also fun to watch. The Weekly Challenge 192 Loved the different ways to deal with bits. Enough to keep you busy. Highly Recommended. The Counter to Equilibrium Pure mathematical solution, very nice attempt. Thanks for sharing. Perl Weekly Challenge 192: Binary Flip and Equal Distribution Laurent's ability to make difficult task easy is worth watching. Keep it up great work. distribute and flip Special one-liner in Raku is not to be nissed. Well done. Thanks for sharing. Perl Weekly Challenge 192 This week task fits in one-liner as far as Perl is concerned. Great work. Flipping easy and distributing fairly Pure discussion of task, just like story telling. You really don't want to skip it. Equal Flips For All Javascript bit operation in play this week. Great work, keep it up. Weekly Challenge 192 As always, we got Perl and Python together playing with bits. Well done. PWC 192 Loved the discussion of "Equal Distribution" task. Enjoy behind the scene story. Rakudo 2022.47 Migratory Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . The corner of Gabor A couple of entries sneaked in by Gabor. Read dates from Excel file using Perl Videos about Docker The latest Perl-related posts on DEV Which articles did you like ? Perl Jobs by Perl Careers Modern Perl and positive team vibes. UK Remote Perl role If you’re a Modern Perl developer in the UK with Go-lang experience (or at least a strong desire to learn) and you’re searching for a team of dynamos, we’ve found the perfect place for you. This award-winning company may be newer, but the combined experience of their people is impressive. No doubt this is one of the many reasons their AI recruitment marketing business has taken off! Bold, beautiful, and… brainy? Senior Perl roles in Malaysia, Dubai and Malta Our client provides online trading services and with offices in Dubai, Malta, and Malaysia, they’ve got the global reach that may provide the challenge you’re looking for. For the right person, they’ve got a work-sponsored visa and relocation package — if you’ve got the expertise and an adventurous spirit, they’ve got the will and means to get you where you need to be. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe. UK Remote Perl Role. A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. Perl to Node Cross-training? Yes Please! UK Remote Perl Role The client is interested in anyone with experience building web apps in Perl, using one of the major Perl frameworks. If you’re a crack-hand with Catalyst, a Mojolicious master, or a distinguished Dancer, they want you. You’ll be deploying apps your work to AWS, so experience would be handy, and the company’s big on testing, so they’d like you to know your way around Test::More. Perl Developer and Business Owner? Remote Perl role in UK & EU Our clients run a job search engine that has grown from two friends with an idea to a site that receives more than 10 million visits per month. They're looking for a Perl pro with at least three years of experience with high-volume and high-traffic apps and sites, a solid understanding of Object-Oriented Perl (perks if that knowledge includes Moose), SQL/MySQL and DBIx::Class. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (153 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 149 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution Top comments (3) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Rob Lauer Rob Lauer Rob Lauer Follow Over 30 years of hands-on experience, leading IT departments, managing dev teams, developing software in various languages, and now back again to my programming roots... Location Pawleys Island, SC Education The College of New Jersey Work CTO @ USGN Joined Dec 6, 2022 • Dec 6 '22 Dropdown menu Copy link Hide Thanks Gabor for sharing your experience blogging on DEV.to. I have been an on and off again blogger on blogs.perl.org but found the experience of using that platform so frustrating I recently turned to plerd to try my hand at blogging again. I'll take your advice and start posting on DEV.to... dev.to/rlauer6/the-observer-effect... Keep up the great work promoting Perl! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Yujia Zhai Yujia Zhai Yujia Zhai Follow Joined May 29, 2024 • Aug 12 '24 Dropdown menu Copy link Hide I started learning Perl 3 months ago when I found a book Programming Perl by a rubbish bin outside my office. I guess, it is from one of my colleagues. After that, I bought 4 books from eBay on Perl (5 pounds for each approximately). As a middle-age man in education industry, I found I quite like this language, and maybe, because of it looks like C language, and has some strength on text manipulation. Computer languages are used by people to understand/practice knowledge and express their ideas. As a teacher, I like Perl, GNU, and etc. If I can choose (freedom), I don't use a tool from a company. I read an article days ago, from Perl Weekly, the guy talked about new technologies using the words (hot shxt). I see this is kind of rude, but it really make sense in its way. Just like fashion, some (most) people want to be different, and want to follow the trend, the new things, and no matter what kinds of differences they would be. But, who is driving this, and what purposes it is about? We might need to think. Just some sharing. Thanks. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand William Torrez William Torrez William Torrez Follow An user more in this world! Location Managua, Nicaragua Education UNI | National University of Engineering Work Technical Support at LAFISE Joined Nov 12, 2021 • May 28 '23 • Edited on May 28 • Edited Dropdown menu Copy link Hide In my country nobody use PERL, only use .NET, C# and other frameworks. Like comment: Like comment: 1 like 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming Perl 🐪 Weekly #752 - Marlin - OOP Framework # perl # news # programming 💎 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:48:42 |
https://www.youtube.com/channel/UC3_cJM5UxFUYCi3n39vvvCw | fine - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:48:42 |
https://m.youtube.com/@thisisfinedev | fine - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:48:42 |
https://docs.suprsend.com/reference/cli-schema-overview | Commands and Flags - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Schema Commands and Flags Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Schema Commands and Flags OpenAI Open in ChatGPT Reference for managing schemas in the SuprSend CLI. OpenAI Open in ChatGPT Schema define the payload structure and validation rules for workflow and event trigger. You can use CLI command to manage schemas - list, pull, push, commit. Syntax Copy Ask AI suprsend schema [flags] Commands Command Description schema list List schemas in a workspace schema pull Pull schemas from workspace to local schema push Push local schemas to workspace schema commit Commit a schema to make it draft changes live Inherited Global Flags This command also supports Global Flags , such as: -w, --workspace – Workspace to use (default: staging ) -s, --service-token – Service token for authentication (default: $SUPRSEND_SERVICE_TOKEN ) -v, --verbosity – Log level (debug, info, warn, error, fatal, panic) (default info ) --config – Config file path (default: $HOME/.suprsend.yaml ) -n, --no-color – Disable color output (default: $NO_COLOR ) Was this page helpful? Yes No Suggest edits Raise issue Previous List Schemas List all notification schemas in your workspace. Next ⌘ I x github linkedin youtube Powered by On this page Syntax Commands Inherited Global Flags | 2026-01-13T08:48:42 |
https://sapegin.me/ | Artem Sapegin Skip to content Artem Sapegin About Blog Book Color scheme Photos Hey, I’m Artem! Write to me , ask me anything , follow me on Mastodon , Bluesky , GitHub , or Dev.to , or keep reading about me: I write about frontend development My books Washing your code Clean code for frontend developers SurviveJS: Maintenance JavaScript open source project maintenance (co-author) Recent blog posts Thoughts on using AI for software development August 20 Washing your code: don’t make me think November 28, 2024 Washing your code: divide and conquer, or merge and relax October 10, 2024 Better autosave and autoformat in Visual Studio Code September 16, 2024 Modern React testing, part 5: Playwright May 1, 2024 How I stay (more) focused with ADHD February 22, 2024 Typewriter 2.0: search for the perfect writing experience on iPad February 12, 2024 More writing Jest cheat sheet Everything you need to write Jest tests Vitest cheat sheet Everything you need to write Vitest tests Frontend pull request checklist Or how to get looks-good-to-me on your pull request seven times faster Sometimes, I also speak at conferences . I do things sometimes Squirrelsong Dark and light themes for web developers Color scheme Blank Sky Beautiful twilight sky inspired new tab page Browser extension Emoji Console Log Insert `console.log()` statements with a random emoji VSCode extension Just Blame Git Blame annotations, inspired by JetBrains editors VSCode extension Mini Markdown A minimalist kit for comfortable Markdown writing VSCode extension New File Now Create new files from the command palette VSCode extension Notebox Take quick notes in the panel VSCode extension Todo Tomorrow Highlight TODO, HACK, FIXME, and so on comments VSCode extension Named CSS colors All named CSS colors on one page Web Coffee timer Pour-over coffee recipe and timer Web React Styleguidist React component development environment Open source Mrm Codemods for your project config files Open source React Group Render React children with a separator Open source Richtypo Typography enhancer for Node.js Open source Textlint rules Check and fix your tech writing with Textlint Open source git-friendly Scripts for a better Git workflow (maintainer) Open source See many more projects on GitHub . I make photos of trees, buildings, and things See more of my photos and my photography zine . I learn how to cook great food My favorite cuisines to cook are Russian, Mexican, Korean, and Italian; my fiancée and I are collecting recipes . I make things from leather Check out my digital leather patterns on Etsy . I drink lots of coffee No milk, no sugar, preferably filter. Dark and bitter, like life. Check out my pour over coffee timer . I may (or may not) look like this This page is best viewed in: © Artem Sapegin, 1999— 2025 Powered by Astro and Tâmia , hosted on Netlify . Source code . RSS | 2026-01-13T08:48:42 |
https://javascript.info/import-export | Export and Import Sorry, Internet Explorer is not supported, please use a newer browser. EN AR عربي EN English ES Español FA فارسی FR Français ID Indonesia IT Italiano JA 日本語 KO 한국어 RU Русский TR Türkçe UK Українська UZ Oʻzbek ZH 简体中文 We want to make this open-source project available for people all around the world. Help to translate the content of this tutorial to your language! Buy EPUB/PDF Search Search Tutorial map Light theme Dark theme Share عربي English Español فارسی Français Indonesia Italiano 日本語 한국어 Русский Türkçe Українська Oʻzbek 简体中文 Tutorial The JavaScript language Modules January 18, 2023 Export and Import Export and import directives have several syntax variants. In the previous article we saw a simple use, now let’s explore more examples. Export before declarations We can label any declaration as exported by placing export before it, be it a variable, function or a class. For instance, here all exports are valid: // export an array export let months = ['Jan', 'Feb', 'Mar','Apr', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec']; // export a constant export const MODULES_BECAME_STANDARD_YEAR = 2015; // export a class export class User { constructor(name) { this.name = name; } } No semicolons after export class/function Please note that export before a class or a function does not make it a function expression . It’s still a function declaration, albeit exported. Most JavaScript style guides don’t recommend semicolons after function and class declarations. That’s why there’s no need for a semicolon at the end of export class and export function : export function sayHi(user) { alert(`Hello, ${user}!`); } // no ; at the end Export apart from declarations Also, we can put export separately. Here we first declare, and then export: // 📁 say.js function sayHi(user) { alert(`Hello, ${user}!`); } function sayBye(user) { alert(`Bye, ${user}!`); } export {sayHi, sayBye}; // a list of exported variables …Or, technically we could put export above functions as well. Import * Usually, we put a list of what to import in curly braces import {...} , like this: // 📁 main.js import {sayHi, sayBye} from './say.js'; sayHi('John'); // Hello, John! sayBye('John'); // Bye, John! But if there’s a lot to import, we can import everything as an object using import * as <obj> , for instance: // 📁 main.js import * as say from './say.js'; say.sayHi('John'); say.sayBye('John'); At first sight, “import everything” seems such a cool thing, short to write, why should we ever explicitly list what we need to import? Well, there are few reasons. Explicitly listing what to import gives shorter names: sayHi() instead of say.sayHi() . Explicit list of imports gives better overview of the code structure: what is used and where. It makes code support and refactoring easier. Don’t be afraid to import too much Modern build tools, such as webpack and others, bundle modules together and optimize them to speedup loading. They also remove unused imports. For instance, if you import * as library from a huge code library, and then use only few methods, then unused ones will not be included into the optimized bundle. Import “as” We can also use as to import under different names. For instance, let’s import sayHi into the local variable hi for brevity, and import sayBye as bye : // 📁 main.js import {sayHi as hi, sayBye as bye} from './say.js'; hi('John'); // Hello, John! bye('John'); // Bye, John! Export “as” The similar syntax exists for export . Let’s export functions as hi and bye : // 📁 say.js ... export {sayHi as hi, sayBye as bye}; Now hi and bye are official names for outsiders, to be used in imports: // 📁 main.js import * as say from './say.js'; say.hi('John'); // Hello, John! say.bye('John'); // Bye, John! Export default In practice, there are mainly two kinds of modules. Modules that contain a library, pack of functions, like say.js above. Modules that declare a single entity, e.g. a module user.js exports only class User . Mostly, the second approach is preferred, so that every “thing” resides in its own module. Naturally, that requires a lot of files, as everything wants its own module, but that’s not a problem at all. Actually, code navigation becomes easier if files are well-named and structured into folders. Modules provide a special export default (“the default export”) syntax to make the “one thing per module” way look better. Put export default before the entity to export: // 📁 user.js export default class User { // just add "default" constructor(name) { this.name = name; } } There may be only one export default per file. …And then import it without curly braces: // 📁 main.js import User from './user.js'; // not {User}, just User new User('John'); Imports without curly braces look nicer. A common mistake when starting to use modules is to forget curly braces at all. So, remember, import needs curly braces for named exports and doesn’t need them for the default one. Named export Default export export class User {...} export default class User {...} import {User} from ... import User from ... Technically, we may have both default and named exports in a single module, but in practice people usually don’t mix them. A module has either named exports or the default one. As there may be at most one default export per file, the exported entity may have no name. For instance, these are all perfectly valid default exports: export default class { // no class name constructor() { ... } } export default function(user) { // no function name alert(`Hello, ${user}!`); } // export a single value, without making a variable export default ['Jan', 'Feb', 'Mar','Apr', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec']; Not giving a name is fine, because there is only one export default per file, so import without curly braces knows what to import. Without default , such an export would give an error: export class { // Error! (non-default export needs a name) constructor() {} } The “default” name In some situations the default keyword is used to reference the default export. For example, to export a function separately from its definition: function sayHi(user) { alert(`Hello, ${user}!`); } // same as if we added "export default" before the function export {sayHi as default}; Or, another situation, let’s say a module user.js exports one main “default” thing, and a few named ones (rarely the case, but it happens): // 📁 user.js export default class User { constructor(name) { this.name = name; } } export function sayHi(user) { alert(`Hello, ${user}!`); } Here’s how to import the default export along with a named one: // 📁 main.js import {default as User, sayHi} from './user.js'; new User('John'); And, finally, if importing everything * as an object, then the default property is exactly the default export: // 📁 main.js import * as user from './user.js'; let User = user.default; // the default export new User('John'); A word against default exports Named exports are explicit. They exactly name what they import, so we have that information from them; that’s a good thing. Named exports force us to use exactly the right name to import: import {User} from './user.js'; // import {MyUser} won't work, the name must be {User} …While for a default export, we always choose the name when importing: import User from './user.js'; // works import MyUser from './user.js'; // works too // could be import Anything... and it'll still work So team members may use different names to import the same thing, and that’s not good. Usually, to avoid that and keep the code consistent, there’s a rule that imported variables should correspond to file names, e.g: import User from './user.js'; import LoginForm from './loginForm.js'; import func from '/path/to/func.js'; ... Still, some teams consider it a serious drawback of default exports. So they prefer to always use named exports. Even if only a single thing is exported, it’s still exported under a name, without default . That also makes re-export (see below) a little bit easier. Re-export “Re-export” syntax export ... from ... allows to import things and immediately export them (possibly under another name), like this: export {sayHi} from './say.js'; // re-export sayHi export {default as User} from './user.js'; // re-export default Why would that be needed? Let’s see a practical use case. Imagine, we’re writing a “package”: a folder with a lot of modules, with some of the functionality exported outside (tools like NPM allow us to publish and distribute such packages, but we don’t have to use them), and many modules are just “helpers”, for internal use in other package modules. The file structure could be like this: auth/ index.js user.js helpers.js tests/ login.js providers/ github.js facebook.js ... We’d like to expose the package functionality via a single entry point. In other words, a person who would like to use our package, should import only from the “main file” auth/index.js . Like this: import {login, logout} from 'auth/index.js' The “main file”, auth/index.js exports all the functionality that we’d like to provide in our package. The idea is that outsiders, other programmers who use our package, should not meddle with its internal structure, search for files inside our package folder. We export only what’s necessary in auth/index.js and keep the rest hidden from prying eyes. As the actual exported functionality is scattered among the package, we can import it into auth/index.js and export from it: // 📁 auth/index.js // import login/logout and immediately export them import {login, logout} from './helpers.js'; export {login, logout}; // import default as User and export it import User from './user.js'; export {User}; ... Now users of our package can import {login} from "auth/index.js" . The syntax export ... from ... is just a shorter notation for such import-export: // 📁 auth/index.js // re-export login/logout export {login, logout} from './helpers.js'; // re-export the default export as User export {default as User} from './user.js'; ... The notable difference of export ... from compared to import/export is that re-exported modules aren’t available in the current file. So inside the above example of auth/index.js we can’t use re-exported login/logout functions. Re-exporting the default export The default export needs separate handling when re-exporting. Let’s say we have user.js with the export default class User and would like to re-export it: // 📁 user.js export default class User { // ... } We can come across two problems with it: export User from './user.js' won’t work. That would lead to a syntax error. To re-export the default export, we have to write export {default as User} , as in the example above. export * from './user.js' re-exports only named exports, but ignores the default one. If we’d like to re-export both named and default exports, then two statements are needed: export * from './user.js'; // to re-export named exports export {default} from './user.js'; // to re-export the default export Such oddities of re-exporting a default export are one of the reasons why some developers don’t like default exports and prefer named ones. Summary Here are all types of export that we covered in this and previous articles. You can check yourself by reading them and recalling what they mean: Before declaration of a class/function/…: export [default] class/function/variable ... Standalone export: export {x [as y], ...} . Re-export: export {x [as y], ...} from "module" export * from "module" (doesn’t re-export default). export {default [as y]} from "module" (re-export default). Import: Importing named exports: import {x [as y], ...} from "module" Importing the default export: import x from "module" import {default as x} from "module" Import all: import * as obj from "module" Import the module (its code runs), but do not assign any of its exports to variables: import "module" We can put import/export statements at the top or at the bottom of a script, that doesn’t matter. So, technically this code is fine: sayHi(); // ... import {sayHi} from './say.js'; // import at the end of the file In practice imports are usually at the start of the file, but that’s only for more convenience. Please note that import/export statements don’t work if inside {...} . A conditional import, like this, won’t work: if (something) { import {sayHi} from "./say.js"; // Error: import must be at top level } …But what if we really need to import something conditionally? Or at the right time? Like, load a module upon request, when it’s really needed? We’ll see dynamic imports in the next article. Previous lesson Next lesson Share Tutorial map Comments read this before commenting… If you have suggestions what to improve - please submit a GitHub issue or a pull request instead of commenting. If you can't understand something in the article – please elaborate. To insert few words of code, use the <code> tag, for several lines – wrap them in <pre> tag, for more than 10 lines – use a sandbox ( plnkr , jsbin , codepen …) Chapter Modules Lesson navigation Export before declarations Export apart from declarations Import * Import “as” Export “as” Export default Re-export Summary Comments Share Edit on GitHub © 2007—2026 Ilya Kantor about the project contact us terms of usage privacy policy | 2026-01-13T08:48:42 |
https://docs.suprsend.com/reference/cli-quickstart | Quickstart - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Getting Started with CLI Quickstart Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Getting Started with CLI Quickstart OpenAI Open in ChatGPT Get up and running with SuprSend CLI in minutes. Complete setup, authentication, and start using right away. OpenAI Open in ChatGPT Step 1: Install the CLI Install the SuprSend CLI using your preferred method: Homebrew (Recommended) Binary Releases Source Build For macOS or Linux users Copy Ask AI brew tap suprsend/tap brew install --cask suprsend Best for Windows users, servers or CI/CD environments Download the binary from GitHub Releases and then install it using: Copy Ask AI # Linux/macOS chmod +x suprsend sudo mv suprsend /usr/local/bin/ # Windows: Extract suprsend.exe to your PATH Best for project contributors or advanced users who want to always have access to the latest binary. Requires Go (version 1.20 or later) Copy Ask AI # 1. Clone the repository git clone https://github.com/suprsend/cli.git cd cli/cmd/suprsend # 2. Build the binary go build -o suprsend # 3. Move the binary to your PATH for easy access sudo mv suprsend /usr/local/bin/ Step 2: Authentication Get your service token from SuprSend Dashboard → Account Settings → Service Tokens . There are three ways to authenticate the CLI: Setting environment variable Using profiles Passing service token as a command flag We generally recommend setting up profiles to ensure that service token is not exposed in the shell history but if you’re setting up CLI to start using MCP server, then you can use environment variable or command flag. Setting up environment variable: Copy Ask AI export SUPRSEND_SERVICE_TOKEN = "your_service_token_here" Using profiles: Copy Ask AI suprsend profile add --name "my-workspace" --service-token "your_service_token_here" suprsend profile use --name "my-workspace" As command flag when starting MCP server: Copy Ask AI suprsend start-mcp-server --service-token "your_service_token_here" Your setup is now complete 🎉 You can start using the CLI by running suprsend command. Copy Ask AI suprsend workflow list Step 3: Enable Autocompletion (Optional) Enable autocompletion to get command and flag suggestions with tab and prevent typos. Was this page helpful? Yes No Suggest edits Raise issue Previous Installation Steps to install the SuprSend CLI Next ⌘ I x github linkedin youtube Powered by On this page Step 1: Install the CLI Step 2: Authentication Your setup is now complete 🎉 Step 3: Enable Autocompletion (Optional) | 2026-01-13T08:48:42 |
https://youtube.com/ | YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:48:42 |
https://docs.suprsend.com/docs/integrate-go-sdk#installation | Integrate Go SDK - 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 Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Node.js SDK Java SDK Go SDK Integrate Go SDK Manage Users Send and Track Events Trigger Workflow from API Tenants Lists Broadcast SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Go SDK Integrate Go SDK Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Go SDK Integrate Go SDK OpenAI Open in ChatGPT Install & Initialize SuprSend Go SDK using your workspace credentials for sending notifications. OpenAI Open in ChatGPT Installation Install suprsend-go sdk bash Copy Ask AI go get github.com/suprsend/suprsend-go Initialization For initializing SDK, you need workspace_key and workspace_secret. You will get both the tokens from your Suprsend dashboard (Developers -> API Keys). Request Copy Ask AI package main import ( " log " suprsend " github.com/suprsend/suprsend-go " ) // Initialize SDK func main () { opts := [] suprsend . ClientOption { // suprsend.WithDebug(true), } suprClient , err := suprsend . NewClient ( "__workspace_key__" , "__workspace_secret__" , opts ... ) if err != nil { log . Println ( err ) } } Was this page helpful? Yes No Suggest edits Raise issue Previous Manage Users Manage user profiles and communication channels programmatically with the Go SDK. Next ⌘ I x github linkedin youtube Powered by On this page Installation Initialization | 2026-01-13T08:48:42 |
https://golf.forem.com/t/mentalgame#main-content | Mentalgame - 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 # mentalgame Follow Hide The psychological side of golf, including focus, confidence, and mindset Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton # golfyoutube # livgolf # rydercup # mentalgame 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 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:48:42 |
https://docs.suprsend.com/docs/tenants-go | Tenants - 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 Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Node.js SDK Java SDK Go SDK Integrate Go SDK Manage Users Send and Track Events Trigger Workflow from API Tenants Lists Broadcast SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Go SDK Tenants Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Go SDK Tenants OpenAI Open in ChatGPT Learn how to create, update, fetch, & list tenants using Go SDK. OpenAI Open in ChatGPT Tenants (previously named as brands) are used for white labeling notifications, personalizing template content or capturing admin preferences for another entity/organization. Tenants are workspace-level entities and by default, a tenant with tenant_id="default" (representing your organization) is created your workspace. Read more about tenants here . Create / Update Tenant This method will create a new tenant or update an existing tenant. Request Copy Ask AI tenantPayload := & suprsend . Tenant { TenantName : suprsend . String ( "Tenant Name" ), Logo : suprsend . String ( "Tenant logo url" ), PrimaryColor : suprsend . String ( "#FFFFFF" ), SecondaryColor : suprsend . String ( "#000000" ), TertiaryColor : nil , SocialLinks : & suprsend . TenantSocialLinks { Facebook : suprsend . String ( "https://facebook.com/tenant" ), Tiktok : suprsend . String ( "https://tiktok.com/tenant" ), X : suprsend . String ( "https://x.com/tenant" ) }, Properties : map [ string ] interface {}{ "k1" : "tenant settings 1" , "k2" : "tenant settings 2" , }, } res , err := suprClient . Tenants . Upsert ( context . Background (), "__tenant_id__" , tenantPayload ) if err != nil { log . Fatalln ( err ) } log . Println ( res ) Get tenant Request Response Copy Ask AI tenant1 , err := suprClient . Tenants . Get ( context . Background (), "tenant_id" ) if err != nil { log . Fatalln ( err ) } log . Println ( tenant1 ) List tenants By default, limit=20 . The maximum value for limit is 1000 . Request Response Copy Ask AI tenantsList , err := suprClient . Tenants . List ( context . Background (), & suprsend . TenantListOptions { Limit : 10 }) if err != nil { log . Fatalln ( err ) } log . Println ( tenantsList ) Add tenant in Workflow Request Copy Ask AI wf := & suprsend . WorkflowTriggerRequest { Body : wfReqBody , TenantId : "tenant_id" } Add tenant in Event Request Copy Ask AI ev := & suprsend . Event { EventName : "__event_name__" , DistinctId : "_distinct_id_" , Properties : map [ string ] interface {}{ ... }, TenantId : "tenant_id" } Was this page helpful? Yes No Suggest edits Raise issue Previous Lists Manage subscriber lists with Go SDK: create or update lists, and modify users in the list. Next ⌘ I x github linkedin youtube Powered by On this page Create / Update Tenant Get tenant List tenants Add tenant in Workflow Add tenant in Event | 2026-01-13T08:48:42 |
https://golf.forem.com/privacy#9-supplemental-notice-for-nevada-residents | Privacy Policy - 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 Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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:48:42 |
https://docs.suprsend.com/docs/node-tenants | Tenants - 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 Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Node.js SDK Integrate Node SDK Manage Users Objects Send and Track Events Trigger Workflow from API Tenants Lists Broadcast Java SDK Go SDK SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Node.js SDK Tenants Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Node.js SDK Tenants OpenAI Open in ChatGPT Learn how to create, update, fetch, & list tenants using NodeJS SDK. OpenAI Open in ChatGPT Tenants (previously named as brands) are used for white labeling notifications, personalizing template content or capturing admin preferences for another entity/organization. Tenants are workspace-level entities and by default, a tenant with tenant_id="default" (representing your organization) is created your workspace. Read more about tenants here . Create / Update tenant This method will create a new tenant or update an existing tenant. Request Copy Ask AI const { Suprsend } = require ( "@suprsend/node-sdk" ); const supr_client = new Suprsend ( "workspace_key" , "workspace_secret" ) const tenant_payload = { ... } // prepare tenant datastructure payload // ---- Optional Parameters ------- const requestData = { secondary_color: "#00ff00" , tertiary_color: "#0000ff" , timezone: "America/New_York" , // blocked channels will be skipped triggering notifications for this tenant. blocked_channels: [ "email" ], social_links: { website: "https://suprsend.com" , facebook: "" , linkedin: "" , x: "" , instagram: "" , medium: "" , discord: "" , telegram: "" , youtube: "" , tiktok: "" }, // In-product Notification center link for capturing user preferences. embedded_preference_url: "" , properties: { prop1: "value1" , prop2: { prop3: [ "value2" ] } } }; // create or update tenant const response = supr_client . tenants . upsert ( tenant_id , tenant_payload ); response . then (( res ) => console . log ( "response" , res )); Field Description tenant_id (mandatory) max 64 characters and should contains alphanumeric characters(a-z, 0-9), hyphen (-) and underscode(_). tenant_name (mandatory) name of the tenant. colors (primary, secondary, tertiary) used while designing templates. If not provided default tenant colour will be picked. social_links social links to your tenant. Pass "" if you want to remove existing link. properties Custom properties associated with the tenant. Update operation is upsert (new properties are added to existing one’s and if key is already present, value is overridden). All properties of the tenant can be referred as {{$tenant.prop}} (handlebars) or data["tenant"].prop in JSONNET format. Get tenant Request Response Copy Ask AI const response = supr_client . tenants . get ( tenant_id ) List tenants By default, limit=20 . The maximum value for limit is 1000 . Request Response Copy Ask AI const response = supr_client . tenants . list (); // default limit 20 const response = supr_client . tenants . list ({ limit: 20 , offset: 0 }); // max limit 1000 Add tenant in workflow Request Copy Ask AI const wf = new Workflow ( workflow_body , { tenant_id : "_tenant_id_" }) Add tenant in event Request Copy Ask AI const event = new Event ( distinct_id , event_name , properties , { tenant_id : "_tenant_id_" }) Was this page helpful? Yes No Suggest edits Raise issue Previous Lists Manage subscriber lists with NodeJS SDK: create/update list, add/remove/replace users. Next ⌘ I x github linkedin youtube Powered by On this page Create / Update tenant Get tenant List tenants Add tenant in workflow Add tenant in event | 2026-01-13T08:48:42 |
https://golf.forem.com/privacy#b-information-collected-automatically | Privacy Policy - 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 Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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:48:42 |
https://golf.forem.com/new/seniorgolf | New Post - 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 Join the Golf Forem Golf Forem is a community of 3,676,891 amazing golfers Continue with Apple Continue with Google Continue with Facebook Continue with Forem Continue with GitHub 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 Golf 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 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:48:42 |
https://www.youtube.com/watch?v=ytudH8je5ko&list=PLNG_1j3cPCaZZ7etkzWA7JfdmKWT0pMsa&index=2 | React 18 for app developers - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x24bd300c9cad2ec0"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtkcndRLXlNdC1vSSjnjZjLBjIKCgJLUhIEGgAgPmLfAgrcAjE1LllUPVN5bGU1OWxGUzlwX2piY0RwYUhhRm5vX3l6TW5HMTJkQXdaQ2VvRVNuTHZpaEpzOVFabUNub2VfLTVaUnp2bHItVzlOaVpWVnBCbVVZYllQUVRQUjJFVkFmMVdnbUNHRmtHempMQ1Bqdzk4YnZmaE9ibzl2S1ZoTWFTMUpkUmNzTGpjSk1YQTRiNi1VVVVWaXBCWjRTMlRqLTdlR3ZHMkhZMlhFUHFFcWVOdDJUSTBTRTR4dzNzUXBoTnZ3a3NUZ0ZVRUdwcTNkQlBfRHRocVN2SEZRYVBGazZ5bzRoZHRCRWJibGR2SVM1MzJRSFVBZ2djdkY2S0R2emJrTFpTT3ExWG1nakhMSnJsd2xNZzVGWG93VldJRW1sZ0FGOTlxN2h5NFRReXczRHdFS0UzMGJta0lEdzBscjlrM0pldElWMXlFQXpGRVhZY2xOOTNSWWdCMzVTZw%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRjXH44J7oP-cxYaojvAyoD4MA4wiXnu8O8hHRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","messageRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","continuationItemRenderer","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","adsEngagementPanelContentRenderer","engagementPanelTitleHeaderRenderer","chipBarViewModel","chipViewModel","sectionListRenderer","macroMarkersListRenderer","macroMarkersListItemRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgtkcndRLXlNdC1vSSjnjZjLBjIKCgJLUhIEGgAgPmLfAgrcAjE1LllUPVN5bGU1OWxGUzlwX2piY0RwYUhhRm5vX3l6TW5HMTJkQXdaQ2VvRVNuTHZpaEpzOVFabUNub2VfLTVaUnp2bHItVzlOaVpWVnBCbVVZYllQUVRQUjJFVkFmMVdnbUNHRmtHempMQ1Bqdzk4YnZmaE9ibzl2S1ZoTWFTMUpkUmNzTGpjSk1YQTRiNi1VVVVWaXBCWjRTMlRqLTdlR3ZHMkhZMlhFUHFFcWVOdDJUSTBTRTR4dzNzUXBoTnZ3a3NUZ0ZVRUdwcTNkQlBfRHRocVN2SEZRYVBGazZ5bzRoZHRCRWJibGR2SVM1MzJRSFVBZ2djdkY2S0R2emJrTFpTT3ExWG1nakhMSnJsd2xNZzVGWG93VldJRW1sZ0FGOTlxN2h5NFRReXczRHdFS0UzMGJta0lEdzBscjlrM0pldElWMXlFQXpGRVhZY2xOOTNSWWdCMzVTZw%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwjIwf_2kIiSAxV3U3gAHdmRCe4yDHJlbGF0ZWQtYXV0b0jKzPvG_KPn7coBmgEFCAMQ-B3KAQRlOk9d","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjIwf_2kIiSAxV3U3gAHdmRCe4yDHJlbGF0ZWQtYXV0b0jKzPvG_KPn7coBmgEFCAMQ-B3KAQRlOk9d","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjIwf_2kIiSAxV3U3gAHdmRCe4yDHJlbGF0ZWQtYXV0b0jKzPvG_KPn7coBmgEFCAMQ-B3KAQRlOk9d","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"React 18 for app developers"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 70,675회"},"shortViewCount":{"simpleText":"조회수 7만회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CLQCEMyrARgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC3l0dWRIOGplNWtvGmBFZ3Q1ZEhWa1NEaHFaVFZyYjBBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDNsMGRXUklPR3BsTld0dkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CLQCEMyrARgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}}],"trackingParams":"CLQCEMyrARgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"968","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CL8CEKVBIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}},{"innertubeCommand":{"clickTrackingParams":"CL8CEKVBIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMACEPqGBCITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMACEPqGBCITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"ytudH8je5ko"},"likeParams":"Cg0KC3l0dWRIOGplNWtvIAAyDAjojZjLBhCFk7nnAQ%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CMACEPqGBCITCMjB__aQiJIDFXdTeAAd2ZEJ7g=="}}}}}}}]}},"accessibilityText":"다른 사용자 968명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CL8CEKVBIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"969","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CL4CEKVBIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}},{"innertubeCommand":{"clickTrackingParams":"CL4CEKVBIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"ytudH8je5ko"},"removeLikeParams":"Cg0KC3l0dWRIOGplNWtvGAAqDAjojZjLBhDfqbrnAQ%3D%3D"}}}]}},"accessibilityText":"다른 사용자 968명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CL4CEKVBIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CLQCEMyrARgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","isTogglingDisabled":true}},"likeStatusEntityKey":"Egt5dHVkSDhqZTVrbyA-KAE%3D","likeStatusEntity":{"key":"Egt5dHVkSDhqZTVrbyA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLwCEKiPCSITCMjB__aQiJIDFXdTeAAd2ZEJ7g=="}},{"innertubeCommand":{"clickTrackingParams":"CLwCEKiPCSITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CL0CEPmGBCITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CL0CEPmGBCITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"ytudH8je5ko"},"dislikeParams":"Cg0KC3l0dWRIOGplNWtvEAAiDAjojZjLBhD9lLznAQ%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CL0CEPmGBCITCMjB__aQiJIDFXdTeAAd2ZEJ7g=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLwCEKiPCSITCMjB__aQiJIDFXdTeAAd2ZEJ7g==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLsCEKiPCSITCMjB__aQiJIDFXdTeAAd2ZEJ7g=="}},{"innertubeCommand":{"clickTrackingParams":"CLsCEKiPCSITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"ytudH8je5ko"},"removeLikeParams":"Cg0KC3l0dWRIOGplNWtvGAAqDAjojZjLBhDZw7znAQ%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLsCEKiPCSITCMjB__aQiJIDFXdTeAAd2ZEJ7g==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CLQCEMyrARgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","isTogglingDisabled":true}},"dislikeEntityKey":"Egt5dHVkSDhqZTVrbyA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"Egt5dHVkSDhqZTVrbyD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLkCEOWWARgCIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}},{"innertubeCommand":{"clickTrackingParams":"CLkCEOWWARgCIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgt5dHVkSDhqZTVrb6ABAQ%3D%3D","commands":[{"clickTrackingParams":"CLkCEOWWARgCIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CLoCEI5iIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLkCEOWWARgCIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CLcCEOuQCSITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLgCEPuGBCITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DytudH8je5ko\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLgCEPuGBCITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=ytudH8je5ko","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"ytudH8je5ko","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr5---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=cadb9d1fc8dee64a\u0026ip=1.208.108.242\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CLgCEPuGBCITCMjB__aQiJIDFXdTeAAd2ZEJ7g=="}}}}}},"trackingParams":"CLcCEOuQCSITCMjB__aQiJIDFXdTeAAd2ZEJ7g=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLUCEOuQCSITCMjB__aQiJIDFXdTeAAd2ZEJ7g=="}},{"innertubeCommand":{"clickTrackingParams":"CLUCEOuQCSITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLYCEPuGBCITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DytudH8je5ko\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLYCEPuGBCITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=ytudH8je5ko","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"ytudH8je5ko","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr5---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=cadb9d1fc8dee64a\u0026ip=1.208.108.242\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CLYCEPuGBCITCMjB__aQiJIDFXdTeAAd2ZEJ7g=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLUCEOuQCSITCMjB__aQiJIDFXdTeAAd2ZEJ7g==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CLQCEMyrARgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","dateText":{"simpleText":"2021. 12. 9."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"4년 전"}},"simpleText":"4년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"React Conf","navigationEndpoint":{"clickTrackingParams":"CLMCEOE5IhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CLMCEOE5IhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 3.43만명"}},"simpleText":"구독자 3.43만명"},"trackingParams":"CLMCEOE5IhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UC1hOCRBN2mnXgN5reSoO3pQ","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CKUCEJsrIhMIyMH_9pCIkgMVd1N4AB3ZkQnuKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"React Conf을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"React Conf을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CLICEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CLECEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CKoCEJf5ASITCMjB__aQiJIDFXdTeAAd2ZEJ7g==","command":{"clickTrackingParams":"CKoCEJf5ASITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CKoCEJf5ASITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CLACEOy1BBgDIhMIyMH_9pCIkgMVd1N4AB3ZkQnuMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQRlOk9d","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFESAggBGAAgBFITCgIIAxILeXR1ZEg4amU1a28YAA%3D%3D"}},"trackingParams":"CLACEOy1BBgDIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CK8CEO21BBgEIhMIyMH_9pCIkgMVd1N4AB3ZkQnuMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQRlOk9d","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFESAggDGAAgBFITCgIIAxILeXR1ZEg4amU1a28YAA%3D%3D"}},"trackingParams":"CK8CEO21BBgEIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CKsCENuLChgFIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKsCENuLChgFIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CKwCEMY4IhMIyMH_9pCIkgMVd1N4AB3ZkQnu","dialogMessages":[{"runs":[{"text":"React Conf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CK4CEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuMgV3YXRjaMoBBGU6T10=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"CgIIAxILeXR1ZEg4amU1a28YAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CK4CEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CK0CEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CKsCENuLChgFIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CKUCEJsrIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CKkCEP2GBCITCMjB__aQiJIDFXdTeAAd2ZEJ7jIJc3Vic2NyaWJlygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DytudH8je5ko%26continue_action%3DQUFFLUhqbDVXcmtLWlVHeG85Q0U1N3ZFS1dvbE8yYUZKd3xBQ3Jtc0trRV9FU3F4bDJob3Mza0ZsYVNhZUlnVWtUSEtpNnowb0ZTc29DXy1zMUxaSnZ2dGtNM2NoQW1va0JFQkVwYnpuekNOVEp1YzRLVVJOMWJIQkh4LXU0SDVQY0YxcnhXcUxVQlpVVV8yRHU1NjNZUzR0TjlTNVowUW9faFZLQ3JXckxMSXF0YmRHQmw2bU5wY05VNS1sTjBqMkdhZU1rQ1NrdTdQVmNnT2ZiSEFFam5kbF8wWDBhYzlzTXVRWEQwRl9kNEZDd0w\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CKkCEP2GBCITCMjB__aQiJIDFXdTeAAd2ZEJ7soBBGU6T10=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=ytudH8je5ko","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"ytudH8je5ko","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr5---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=cadb9d1fc8dee64a\u0026ip=1.208.108.242\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbDVXcmtLWlVHeG85Q0U1N3ZFS1dvbE8yYUZKd3xBQ3Jtc0trRV9FU3F4bDJob3Mza0ZsYVNhZUlnVWtUSEtpNnowb0ZTc29DXy1zMUxaSnZ2dGtNM2NoQW1va0JFQkVwYnpuekNOVEp1YzRLVVJOMWJIQkh4LXU0SDVQY0YxcnhXcUxVQlpVVV8yRHU1NjNZUzR0TjlTNVowUW9faFZLQ3JXckxMSXF0YmRHQmw2bU5wY05VNS1sTjBqMkdhZU1rQ1NrdTdQVmNnT2ZiSEFFam5kbF8wWDBhYzlzTXVRWEQwRl9kNEZDd0w","idamTag":"66429"}},"trackingParams":"CKkCEP2GBCITCMjB__aQiJIDFXdTeAAd2ZEJ7g=="}}}}}},"subscribedEntityKey":"EhhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFEgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CKUCEJsrIhMIyMH_9pCIkgMVd1N4AB3ZkQnuKPgdMgV3YXRjaMoBBGU6T10=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"EgIIAxgAIgt5dHVkSDhqZTVrbw%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CKUCEJsrIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKUCEJsrIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CKYCEMY4IhMIyMH_9pCIkgMVd1N4AB3ZkQnu","dialogMessages":[{"runs":[{"text":"React Conf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CKgCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuKPgdMgV3YXRjaMoBBGU6T10=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"CgIIAxILeXR1ZEg4amU1a28YAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CKgCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CKcCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CKQCEM2rARgBIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CKQCEM2rARgBIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CKQCEM2rARgBIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CKQCEM2rARgBIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CKQCEM2rARgBIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CKQCEM2rARgBIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Shruti Kapoor","styleRuns":[{"startIndex":0,"length":13,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"}]},"headerRuns":[{"startIndex":0,"length":13,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"messageRenderer":{"text":{"runs":[{"text":"댓글이 사용 중지되었습니다. "},{"text":"자세히 알아보기","navigationEndpoint":{"clickTrackingParams":"CKMCEJY7GAAiEwjIwf_2kIiSAxV3U3gAHdmRCe7KAQRlOk9d","commandMetadata":{"webCommandMetadata":{"url":"https://support.google.com/youtube/answer/9706180?hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://support.google.com/youtube/answer/9706180?hl=ko"}}}]},"trackingParams":"CKMCEJY7GAAiEwjIwf_2kIiSAxV3U3gAHdmRCe4="}}],"trackingParams":"CKICELsvGAMiEwjIwf_2kIiSAxV3U3gAHdmRCe4=","sectionIdentifier":"comment-item-section"}}],"trackingParams":"CKECELovIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/pj5N-Khihgc/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLBe418zAEgrK8nz2lVa5hfLGw12-Q","width":168,"height":94},{"url":"https://i.ytimg.com/vi/pj5N-Khihgc/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLAox6aKNoDup6er69UGEUVApcrr6g","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"18:36","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"pj5N-Khihgc","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"18분 36초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CKACEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"pj5N-Khihgc","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKACEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CJ8CEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"pj5N-Khihgc"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJ8CEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJgCENTEDBgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CJ4CEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJ4CEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"pj5N-Khihgc","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CJ4CEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["pj5N-Khihgc"],"params":"CAQ%3D"}},"videoIds":["pj5N-Khihgc"],"videoCommand":{"clickTrackingParams":"CJ4CEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=ugUHEgVlbi1VUw%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","playerParams":"ugUHEgVlbi1VUw%3D%3D","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-jwwe7.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a63e4df8a8628607\u0026ip=1.208.108.242\u0026initcwndbps=3695000\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJ4CEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJ0CEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJgCENTEDBgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"스트리밍 서버 렌더링(서스펜스 기능 포함)"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"React Conf 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJgCENTEDBgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"React Conf"}}]},{"metadataParts":[{"text":{"content":"조회수 5.2만회"}},{"text":{"content":"4년 전"}}]}],"delimiter":" • "}},"menuButton":{"buttonViewModel":{"iconName":"MORE_VERT","onTap":{"innertubeCommand":{"clickTrackingParams":"CJkCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","showSheetCommand":{"panelLoadingStrategy":{"inlineContent":{"sheetViewModel":{"content":{"listViewModel":{"listItems":[{"listItemViewModel":{"title":{"content":"현재 재생목록에 추가"},"leadingImage":{"sources":[{"clientResource":{"imageName":"ADD_TO_QUEUE_TAIL"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CJwCEP6YBBgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEP6YBBgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJwCEP6YBBgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"pj5N-Khihgc","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CJwCEP6YBBgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["pj5N-Khihgc"],"params":"CAQ%3D"}},"videoIds":["pj5N-Khihgc"],"videoCommand":{"clickTrackingParams":"CJwCEP6YBBgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=ugUHEgVlbi1VUw%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","playerParams":"ugUHEgVlbi1VUw%3D%3D","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-jwwe7.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a63e4df8a8628607\u0026ip=1.208.108.242\u0026initcwndbps=3695000\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}}}}}},{"listItemViewModel":{"title":{"content":"재생목록에 저장"},"leadingImage":{"sources":[{"clientResource":{"imageName":"BOOKMARK_BORDER"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CJsCEJSsCRgBIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJsCEJSsCRgBIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJsCEJSsCRgBIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtwajVOLUtoaWhnYw%3D%3D"}}}}}}}}}}},{"listItemViewModel":{"title":{"content":"공유"},"leadingImage":{"sources":[{"clientResource":{"imageName":"SHARE"}}]},"rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJkCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtwajVOLUtoaWhnYw%3D%3D","commands":[{"clickTrackingParams":"CJkCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CJoCEI5iIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}}}}}]}}}}}}}},"accessibilityText":"추가 작업","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJkCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","type":"BUTTON_VIEW_MODEL_TYPE_TEXT","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}}}},"contentId":"pj5N-Khihgc","contentType":"LOCKUP_CONTENT_TYPE_VIDEO","rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CJgCENTEDBgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","visibility":{"types":"12"}}},"accessibilityContext":{"label":"스트리밍 서버 렌더링(서스펜스 기능 포함) 18분"},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJgCENTEDBgAIhMIyMH_9pCIkgMVd1N4AB3ZkQnuMgdyZWxhdGVkSMrM-8b8o-ftygGaAQUIARD4HcoBBGU6T10=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=ugUHEgVlbi1VUw%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","playerParams":"ugUHEgVlbi1VUw%3D%3D","nofollow":true,"ustreamerConfig":"KgkKBxIFZW4tVVM=","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-jwwe7.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a63e4df8a8628607\u0026ip=1.208.108.242\u0026initcwndbps=3695000\u0026mt=1768293662\u0026oweuc="}}}}}}}}}},{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/FZ0cG47msEk/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLDH5r7Pql2X_EahvH-14ODdUVWJ5Q","width":168,"height":94},{"url":"https://i.ytimg.com/vi/FZ0cG47msEk/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLCTtuJn7VO4tBUlWnafyCq1IkkwwQ","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"33:49","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"FZ0cG47msEk","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"33분 49초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CJcCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"FZ0cG47msEk","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJcCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CJYCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"FZ0cG47msEk"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJYCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CI8CENTEDBgBIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CJUCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJUCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"FZ0cG47msEk","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CJUCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["FZ0cG47msEk"],"params":"CAQ%3D"}},"videoIds":["FZ0cG47msEk"],"videoCommand":{"clickTrackingParams":"CJUCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FZ0cG47msEk","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FZ0cG47msEk","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-jwwy.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=159d1c1b8ee6b049\u0026ip=1.208.108.242\u0026initcwndbps=4130000\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJUCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJQCEPBbIhMIyMH_9pCIkgMVd1N4AB3ZkQnu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CI8CENTEDBgBIhMIyMH_9pCIkgMVd1N4AB3ZkQnu"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"React 18 Keynote"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"React Conf 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CI8CENTEDBgBIhMIyMH_9pCIkgMVd1N4AB3ZkQnuygEEZTpPXQ==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"React Conf"}}]},{"metadataParts":[{"text":{"con | 2026-01-13T08:48:42 |
https://docs.suprsend.com/docs/integrate-go-sdk#initialization | Integrate Go SDK - 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 Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Node.js SDK Java SDK Go SDK Integrate Go SDK Manage Users Send and Track Events Trigger Workflow from API Tenants Lists Broadcast SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Go SDK Integrate Go SDK Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Go SDK Integrate Go SDK OpenAI Open in ChatGPT Install & Initialize SuprSend Go SDK using your workspace credentials for sending notifications. OpenAI Open in ChatGPT Installation Install suprsend-go sdk bash Copy Ask AI go get github.com/suprsend/suprsend-go Initialization For initializing SDK, you need workspace_key and workspace_secret. You will get both the tokens from your Suprsend dashboard (Developers -> API Keys). Request Copy Ask AI package main import ( " log " suprsend " github.com/suprsend/suprsend-go " ) // Initialize SDK func main () { opts := [] suprsend . ClientOption { // suprsend.WithDebug(true), } suprClient , err := suprsend . NewClient ( "__workspace_key__" , "__workspace_secret__" , opts ... ) if err != nil { log . Println ( err ) } } Was this page helpful? Yes No Suggest edits Raise issue Previous Manage Users Manage user profiles and communication channels programmatically with the Go SDK. Next ⌘ I x github linkedin youtube Powered by On this page Installation Initialization | 2026-01-13T08:48:42 |
https://docs.suprsend.com/docs#benefits-of-using-suprsend-as-your-notification-stack: | What is SuprSend? - 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 GETTING STARTED What is SuprSend? Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog GETTING STARTED What is SuprSend? OpenAI Open in ChatGPT Learn about SuprSend and how you can use it to power multi-channel product notifications. OpenAI Open in ChatGPT SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack: You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritise vendors and channels from your SuprSend account, You can design powerful templates for all channels together and manage them from a single place, You can leverage powerful features to experiment fast with notifications as well as take care of end user experience without writing a single line of code. Introduction to Workflows Communications are made up of multiple components - trigger, logic, content, variables, target user, channels, vendors, etc. Typical communication solutions have one or more components intertwined with each other. SuprSend solves communications from a different and more powerful approach, which we call Workflows. At SuprSend, all the constituent components are decoupled from each other, making it modular in nature. The components can come from any source. All these components are configured as nodes in Workflows, where the processing happens for delivery and optimisation. This allows Workflows to handle any complexity possible in your communication use cases. How do you trigger notifications? You can trigger notifications in one of the two ways: Send events to SuprSend from your frontend clients (android app, website, etc) via SuprSend Client SDK, and create a Workflow on SuprSend platform to trigger notification on an event. Create workflow and trigger notification from your backend itself using an omni-channel HTTPS API method, or you can use our Backend SDK. All the other components (like vendors, templates, optimisation, scaling, etc.) are created and managed on SuprSend platform. You can check the ‘Core Concepts’ section that lists down the components used in the platform, so you can navigate the platform and use all the features with ease. SuprSend APIs You can try out SuprSend APIs from our Postman collection Was this page helpful? Yes No Suggest edits Raise issue Overview Start setting up your notifications with SuprSend by following quick start guides for one of the mentioned channels. Next ⌘ I x github linkedin youtube Powered by On this page Benefits of using SuprSend as your notification stack: Introduction to Workflows How do you trigger notifications? SuprSend APIs | 2026-01-13T08:48:42 |
https://golf.forem.com/t/seniorgolf#main-content | Seniorgolf - 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 # seniorgolf Follow Hide Golf for the senior community, focusing on adapted play and gear 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:48:42 |
https://m.youtube.com/@thisisfinedev | fine - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:48:42 |
https://golf.forem.com/youtube_golf/golfcom-warming-up-with-jon-rahm-and-tyrrell-hatton-1m4l | Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton - 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 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 YouTube Golf Posted on Jul 10, 2025 Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton # golfyoutube # livgolf # rydercup # mentalgame Jon Rahm and Tyrrell Hatton team up on GOLF.com’s Warming Up series, showing why they’re golf soulmates both on and off the course. They share plenty of laughs—Hatton calls Rahm a “big teddy bear” despite his fierce on-course look, while Rahm insists Hatton is “one of the funniest people you’ll ever meet.” Beyond the jokes, they dive into their game-day mindsets: Rahm says he’s “irrationally positive,” whereas Hatton warns that too much positivity can drain you. Their chemistry and contrasting approaches make this rare two-player interview a must-watch for golf fans. 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 YouTube Golf Follow Joined Jun 22, 2025 More from YouTube Golf No Laying Up Podcast: Everyone Only: The Gimme Golf Club Origin Story | NLU Pod, Ep 1033 # golf # golfpodcasts # golfyoutube # localgolf Golf.com: Bringing the Anthem to the PGA Tour: One Family's Story of Service # pgatour # historyofgolf # golfyoutube # golfmedia Golf.com: Secrets of Long Island Private Golf: A 1-Member Club, Hamptons Hideaways and Caddie Confessionals # coursereviews # golfdestinations # localgolf # golfyoutube 💎 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:48:42 |
https://git.afpy.org/AFPy/python-docs-fr/src/branch/3.13/CONTRIBUTING.rst | python-docs-fr/CONTRIBUTING.rst at 3.13 - AFPy/python-docs-fr - La forge de l'AFPy This website requires JavaScript. Explore Help Register Sign in AFPy / python-docs-fr Watch 10 Star 11 Fork You've already forked python-docs-fr 81 Code Issues 7 Pull requests 10 Activity 3.13 python-docs-fr / CONTRIBUTING.rst c24b 1b2e729d89 Update CONTRIBUTING.rst ( #311 ) ... Updated version 3.11 to 3.13 Reviewed-on: #311 Reviewed-by: Christophe Nanteuil <christophenan@noreply.localhost> Co-authored-by: c24b <4barbes@gmail.com> Co-committed-by: c24b <4barbes@gmail.com> 2024-11-01 13:39:02 +00:00 32 KiB Raw Permalink Blame History Guide de contribution à la documentation Prérequis Outils souhaitables Pour pouvoir participer à la traduction en commun, il est souhaitable d'installer : un client git Linux , MacOS ou Windows ; un éditeur de fichier .po (comme Poedit ). Outils facultatifs De plus, il peut être utile de s'équiper d'utilitaires pour faciliter la manipulation des fichiers .po et la traduction. Poutils est un paquet PyPI qui regroupe un certain nombre d'outils liés à la traduction. Dans un environnement disposant de Python 3.7 ou plus, installez-le avec : python3 -m pip install poutils Dans notre cas, les utilitaires de Poutils qui nous intéressent sont : Pospell Vérificateur d'orthographe fondé sur Hunspell. make spell exécute Pospell. Pour l'utiliser, il vous faut installer Hunspell. Attention, dans Debian notamment (et ses dérivés comme Ubuntu), il existe plusieurs dictionnaires français qui diffèrent en raison de l'orthographe réformée. Installez celui qui contient les deux orthographes avec : sudo apt install hunspell hunspell-fr-comprehensive Potodo Permet d'identifier les parties de la documentation qu'il reste à traduire. make todo fait appel à Potodo. Pogrep Permet de rechercher dans la documentation des termes. Utile si on a un doute sur comment traduire un terme ou chercher la traduction d'un terme dans d'autres fichiers. Pour connaître les options disponibles, tapez : pogrep --help Powrap Formateur de fichier .po . C'est l'outil qui se cache derrière make wrap . Padpo (beta) Analyseur de code qui encapsule notamment Grammalecte et qui vérifie la grammaire, l'orthographe et la syntaxe des fichiers .po . Configuration des outils Configuration de Poedit N'oubliez pas de configurer votre nom et votre adresse de courriel (Édition → Préférences → Général). Vérifiez également qu'il est configuré pour passer à la ligne à 79 caractères (Édition → Préférences → Avancé → Passer à la ligne à 79). Configuration de Git (rendre plus lisible l'affichage des modifications) Le résultat de git diff est souvent encombré de changements inutiles de numéros de ligne, comme : -#: ../Doc/library/sys.rst:406 +#: ../Doc/library/sys.rst:408 Pour dire à Git que ce ne sont pas des informations utiles, vous pouvez faire ce qui suit après vous être assuré que ~/.local/bin/ se trouve dans votre PATH . cat <<EOF > ~/.local/bin/podiff #!/bin/sh grep -v '^#:' " \$ 1" EOF chmod a+x ~/.local/bin/podiff Allez ensuite dans le répertoire du dépôt récupéré ( python-docs-fr ) et faites : git config diff.podiff.textconv podiff Pas d'inquiétude, cela ne change la façon dont Git affiche les changements que sur les fichiers de la traduction, sans incidence sur les autres. Première étape : créer et peupler son dépôt Si ce n'est pas déjà fait, créez un compte sur le serveur Git de l'AFPy . Puis, allez sur le dépôt python-docs-fr et cliquez sur le bouton « Bifurcation » en haut à droite. Vous créez ainsi sur Gitea une copie privée du projet où vous avez le droit de faire des modifications. À ce stade, il est recommandé, bien que facultatif, de vous créer une clé SSH si vous n'en avez pas encore, et de l'ajouter à votre compte Gitea. Pour générer la clé, consultez le guide de GitLab ou celui de GitHub . Pour l'ajouter à votre compte Gitea, il suffit d'aller dans le menu de votre compte en haut à droite et de cliquer sur « Configuration », puis d'aller dans l'onglet « Clés SSH / GPG », et de copier la clé SSH. Si vous le préférez, vous pouvez également vous passer de cette configuration et utiliser le HTTPS à la place du SSH. Néanmoins, sachez que vous devrez taper votre nom d'utilisateur et votre mot de passe Gitea à chaque fois que vous ouvrez ou modifiez une contribution. Enfin, faites une copie locale du dépôt sur votre ordinateur afin de pouvoir éditer les fichiers, avec ces commandes : # Clonez votre copie sur Gitea avec `git` en utilisant SSH : git clone git@git.afpy.org:VOTRE_NOM_DE_COMPTE_GITEA/python-docs-fr.git # ... ou bien avec HTTPS : git clone https://git.afpy.org/VOTRE_NOM_DE_COMPTE_GITEA/python-docs-fr.git # Allez dans le répertoire cloné cd python-docs-fr/ # Ajoutez le dépôt officiel (nommé upstream), # ceci permet à `git` de savoir quoi et où est *upstream* git remote add upstream https://git.afpy.org/AFPy/python-docs-fr.git Deuxième étape : choisir et réserver le fichier sur lequel travailler Note liminaire Il est vivement conseillé de ne pas travailler sur fichiers des répertoires c-api/ , whatsnew/ , distutils/ et install/ : c-api/ car c'est une partie très technique ; whatsnew/ car les anciennes versions de Python sont pour la plupart obsolètes et leurs journaux de modifications ne sont pas les pages les plus consultées ; distutils/ , install/ , et quelques autres parties qui seront bientôt obsolètes. De manière générale, il n'est pas utile de traduire un module que sa documentation mentionne comme obsolète. Trouver un fichier sur lequel travailler Pour vous aiguiller dans votre choix, vous pouvez utiliser potodo , un outil recherchant des fichiers .po à traduire. Une fois installé, utilisez la commande make todo dans votre clone local. La liste renvoyée contient tous les fichiers qui ne sont pas encore complètement traduits. Vous pouvez choisir n'importe quel fichier non réservé dans la liste renvoyée (notez que ceux mentionnés plus haut sont automatiquement exclus). Vous pouvez commencer par des tâches faciles comme réviser les entrées fuzzy pour aider à garder la documentation à jour (trouvez-les à l'aide de make fuzzy ). Une entrée fuzzy correspond à une entrée déjà traduite mais dont la source en anglais a été modifiée depuis (correction orthographique, changement d'un terme, ajout ou suppression d'une phrase…). Elles sont généralement plus « faciles » à traduire. Vous pouvez également relire des entrées déjà traduites pour vous faire une idée, et passer ensuite à la traduction de celles qui ne le sont pas encore. Nous vous conseillons de choisir, si possible, un fichier traitant d'un sujet que vous maîtrisez, cela vous aidera grandement à produire une traduction de bonne qualité. Si c'est votre première contribution, commencez par une toute petite traduction, de quelques paragraphes maximum, pour vous familiariser. Il n'est pas nécessaire de terminer un fichier lorsqu'on le commence, vous pouvez donc prendre n'importe quel fichier, mais ne traduire que quelques paragraphes. Réserver le fichier Chaque fois que vous commencez un nouveau fichier, suivez cette procédure. Une fois que vous avez choisi un fichier sur lequel travailler vous pouvez nous le signaler par différents moyens : Soit en ouvrant un ticket sur Gitea en indiquant dans le titre Je travaille sur DOSSIER/FICHIER.po (par exemple « Je travaille sur library/sys.po »). Ceci permet à potodo de détecter via l'API Gitea les fichiers .po réservés dans les tickets et les demandes d'ajout. Soit en créant un sujet sur le discuss de l'AFPy dans la section Traduction en indiquant sur quoi vous travaillez et l'URL de votre dépôt. Soit sur IRC en venant sur le canal irc://irc.libera.chat/#python-docs-fr pour nous le signaler. Création de la branche de traduction Chaque fois que vous commencez un nouveau fichier, suivez cette procédure. Vous êtes maintenant prêt. Pour travailler, nous avons besoin d'une branche, basée sur une version à jour (fraîchement récupérée) de la branche « upstream/3.13 ». On met donc à jour notre version locale. git fetch upstream On crée ensuite la branche, en la basant sur « upstream/3.13 », fraîchement récupérée. Il est pratique de nommer cette branche en fonction du fichier sur lequel on travaille. Par exemple, si vous travaillez sur « library/sys.po », vous pouvez nommer votre branche « library-sys ». git switch -c library-sys upstream/3.13 Troisième étape: Traduction Avec Poedit Ici, remplacez « library/sys.po » par le fichier que vous avez choisi précédemment. poedit library/sys.po Ou lancez simplement Poedit puis « Fichier » → « Ouvrir ». Il n'est pas obligatoire de terminer un fichier, ni de le travailler de haut en bas, chacun traduit ce qu'il souhaite. Cependant évitons de changer plus de 200 lignes par pull request (pour le confort des relecteurs). Faire plusieurs pull requests est bien sûr autorisé. Vérifications après traduction Après avoir modifié les fichiers, vérifiez que vous respectez les conventions du projet. Pour vous y aider, la commande : make verifs vérifie la longueur des lignes et l'orthographe (mais pas la grammaire, pour cela utilisez padpo (beta) ). En cas de doute, un glossaire répertorie déjà les traductions retenues pour certains termes techniques ou faux amis en anglais. Si make verifs trouve des problèmes de longueurs de ligne, vérifiez votre configuration poedit (Édition → Préférences → Avancé → Passer à la ligne à 79) ou utilisez make wrap . Une fois la traduction finie, il faut compiler la documentation, c'est-à-dire générer les fichiers HTML affichés par le site, pour les relire. Si la commande précédente s'est exécutée sans erreur, la compilation ne devrait pas échouer. make Vérifiez alors le rendu de la traduction « en vrai ». Lancez un serveur de documentation local : make htmlview La documentation est publiée à l'adresse http://localhost:8000/library/sys.html . Attention: le port TCP/8000 ne peut être changé, il convient d'arrêter tout service qui écouterait sur celui-ci. Vous pouvez recommencer les étapes de cette section autant de fois que nécessaire. Poedit donne beaucoup d'avertissements, par exemple pour vous informer que « la traduction devrait commencer par une majuscule » car c'est le cas pour la source. Ces avertissements ne sont pas tous fondés. En cas de doute, affichez et relisez la page HTML produite avec make htmlview . Quatrième étape : publier sa traduction Une fois que le make verifs ne lève pas d'erreur et que vous êtes certains de bien respecter les Conventions de traduction, vient le moment d'envoyer votre travail sur le dépôt local. git add place nos modifications dans l'index de Git en attendant d'être propagées dans le dépôt local. git add library/sys.po git commit permet de les propager : git commit --message "Traduction de library/sys.po" # Ou un autre message plus inspiré :) Poussez ensuite vos modifications sur votre bifurcation ( fork ) avec git push . Le -u n'est utile qu'une fois pour que votre client git se souvienne que cette branche est liée à votre bifurcation (et donc que vos futurs git pull et git push sachent quoi tirer). git push --set-upstream origin Sur Gitea La commande précédente vous affiche un lien pour ouvrir une demande d'ajout sur Gitea. Si vous l'avez manqué, allez simplement sur https://git.afpy.org/AFPy/python-docs-fr/pulls et cliquez sur le bouton « Nouvelle demande d'ajout ». Mettez dans le commentaire de la demande d'ajout le texte suivant : « Closes #XXXX » où XXXX est le numéro du ticket Gitea créé pour réserver le fichier traduit. Cela permet à Gitea de lier la demande d'ajout au ticket de réservation. Il peut arriver que vous ayez besoin de reprendre votre demande d'ajout sur votre ordinateur après avoir fait des modifications en ligne sur Gitea, par exemple lorsque Gitea vous offre la possibilité de faire un commit automatique contenant les suggestions proposées pendant la revue. Cela fonctionne bien, mais le résultat n'est pas toujours accepté par powrap . Si cela arrive, vous pouvez récupérer le commit fait par Gitea puis relancer powrap : git pull powrap < fichier.po > git add < fichier.po > git commit -m "Formatage après commit automatique" git push Vous avez peut-être remarqué que cela ressemble à un triangle, avec un segment manquant : vous récupérez depuis upstream (le dépôt commun public sur Gitea) ; vous poussez sur origin (votre clone sur Gitea). C'est le travail de quelqu'un d'autre d'ajouter le dernier segment, de votre origin au upstream public, pour « boucler la boucle ». C'est le rôle des personnes qui fusionnent les demandes d'ajout après les avoir relues. Vous avez peut-être aussi remarqué que vous n'avez jamais commité sur une branche de version (3.9, 3.10, etc.), seulement récupéré les modifications à partir d'elles. Toutes les traductions sont faites sur la dernière version. Nous ne traduisons jamais sur une version plus ancienne. Par exemple, si la dernière version de python est Python 3.10, nous ne voulons pas traduire directement sur la version Python 3.6. Si nécessaire, les traductions seraient rétroportées sur les versions les plus anciennes par l' équipe de documentation . Conventions Certaines conventions ont été édictées pour homogénéiser la traduction. Il faut suivre les règles de style imposées, les règles rst et les traductions déjà définies dans le glossaire . Style Une bonne traduction est une traduction qui transcrit fidèlement l'idée originelle en français, sans rien ajouter ni enlever au fond, tout en restant claire, concise et agréable à lire. Les traductions mot-à-mot sont à proscrire et il est permis — même conseillé — d'intervertir des propositions ou de réarranger des phrases de la documentation anglaise, si le rythme l'exige. Il faut aussi chercher des équivalents français aux termes techniques et aux idiotismes rencontrés, et prendre garde aux anglicismes. Utilisation du futur Dans la description du comportement de Python (au sens large, c'est-à-dire l'interpréteur lui-même mais aussi toutes les bibliothèques), la version originale utilise souvent le futur : « if you do this, it will produce that… ». En français, l'utilisation du présent convient tout à fait et le présent est souvent plus facile à lire : « si vous faites ceci, il se produit cela… ». On ne conserve le futur que si la seconde proposition se situe réellement dans le futur (par exemple, on peut penser qu'un processus de compilation n'est pas immédiat) ou pour des raisons de concordance des temps. Utilisation du conditionnel La version originale est très polie envers le lecteur ; elle lui intime rarement des obligations, préférant employer « you should ». Cependant, en français, il est d'usage d'être plus direct pour être correctement compris : « vous devez ». Vous devriez est en effet généralement compris comme quelque chose dont on peut de temps en temps se passer, alors que c'est très rarement le cas pour les « you should » de cette documentation. De la même manière, « can » est souvent mieux traduit sans introduire de notion de possibilité, en particulier quand la phrase est à la voix passive ; la phrase « these objects can be accessed by… » se traduit mieux par « on accède à ces objets en… ». Utilisation du masculin Dans un souci de lisibilité et en accord avec la préconisation de l'Académie française, nous utilisons le masculin pour indiquer un genre neutre. Par exemple : l'utilisateur ou le lecteur. Règles rst Prototypes et exemples Il ne faut pas traduire le nom des éléments de la bibliothèque standard (noms de fonctions, paramètres de ces fonctions, constantes, etc.) mais les laisser tels quel, entourés d'astérisques dans les blocs de texte. Si la documentation contient des exemples, vous pouvez traduire les noms utilisés, en prenant garde d'être cohérent. Vous pouvez ainsi traduire : def sample_function(): result = thread.join(timeout = ...) ... en def fonction_exemple(): resultat = thread.join(timeout = ...) ... mais pas en def fonction_exemple(): resultat = fildexécution.attendre(délai = ...) ... Liens hypertextes Il faut transformer les liens hypertextes qui redirigent vers une page dont il existe une version française (c'est notamment très souvent le cas pour les articles de Wikipédia). Modifiez le lien et sa description dans ce cas. Si aucune traduction de la cible n'existe, ne traduisez pas la description. Par exemple, `Conway's Game of Life <https://en.wikipedia.org/wiki/Conway%27s_Game_of_Life>`_ doit devenir `Jeu de la vie <https://fr.wikipedia.org/wiki/Jeu_de_la_vie>`_ . Balises Ne traduisez pas le contenu des balises comme :ref:... ou :class:... . Vous devez cependant traduire les balises :term:... , qui font référence à une primitive ou un concept défini dans le glossaire Python . La syntaxe est :term:`nom_français <nom_anglais> `. Par exemple, traduisez: :term:`dictionary` en: :term:`dictionnaire <dictionary>` Comme le glossaire est déjà traduit, il y a forcément une correspondance à chaque terme que vous pouvez rencontrer. Glossaire Afin d'assurer la cohérence de la traduction, voici quelques termes fréquents déjà traduits. Une liste blanche de noms propres, comme « Guido », « C99 » ou de certains anglicismes comme « sérialisable » ou « implémentation», est stockée dans le fichier dict à la racine du projet. Vous pouvez y ajouter une entrée si cela est nécessaire. Si vous devez absolument utiliser un mot anglais, mettez-le en italique (entouré par des astérisques). Pour trouver facilement comment un terme est déjà traduit dans la documentation, vous pouvez utiliser pogrep . Terme Traduction -like -compatible abstract data type type abstrait argument argument (à ne pas confondre avec paramètre ) backslash antislash, backslash backtrace trace d'appels, trace de pile backport rétroporter base class classe mère bound lier bug bogue built-in natif bytecode code intermédiaire callback fonction de rappel call stack pile d'appels caught (exception) interceptée code points points de code daemon daemon debugging débogage deep copy copie récursive (préféré), ou copie profonde double quote guillemet deprecated obsolète e.g. p. ex. (on n'utilise pas l'anglicisme « e.g. », lui-même issu du latin exempli gratia ). On sépare les deux mots par une espace insécable pour éviter les retours à la ligne malheureux. et al. et autres, à accorder suivant le contexte export exportation expression expression framework cadriciel frozen package or set paquet ou ensemble figé garbage collector ramasse-miettes getter accesseur i.e. c.-à-d. (on n'utilise pas l'anglicisme « i.e. », lui-même issu du latin id est ) identifier identifiant immutable immuable import importation index indice (en particulier quand on parle de chaînes de caractères) installer installateur interpreter interpréteur keyword mot clé keyword argument argument nommé library bibliothèque list comprehension liste en compréhension (liste en intension est valide, mais nous ne l'utilisons pas) little-endian, big-endian petit-boutiste, gros-boutiste mixin type type de mélange mutable mutable namespace espace de nommage (sauf pour le XML où c'est espace de noms) parameter paramètre parse, parser analyser, analyseur syntaxique pickle (v.) sérialiser prompt invite raise lever regular expression expression rationnelle, expression régulière return renvoie, donne (on évite « retourne » qui pourrait porter à confusion) roughly approximativement, à peu près (on ne traduit pas « roughly equivalent » par « sensiblement équivalent ») setter mutateur simple quote guillemet simple slot emplacement socket connecteur ou interface de connexion sort trier (préféré), ordonner, classer specify définir, préciser (plutôt que « spécifier ») statement instruction subprocess sous-processus support prendre en charge, implémenter (« supporter » n'a pas le même sens en français) token (parsing) lexème thread fil d'exécution traceback trace d'appels, trace de pile tuple n -uplet (avec n en italique), on peut traduire 2-tuple par « paire » ou « couple », 3-tuple par « triplet », 4-tuple par « quadruplet » etc. typically normalement, habituellement, comme d'habitude (plutôt que « typiquement ») underscore tiret bas, underscore , sous-tiret whitespace caractère d'espacement Ressources de traduction les canaux IRC sur irc.libera.chat : #python-docs-fr — communauté python autour de la documentation française, #python-fr — communauté python francophone, #python-doc — communauté python autour de la documentation anglophone ; les listes de diffusion relatives à la documentation (courriel) : de l'AFPy , de CPython ; des glossaires et dictionnaires : le glossaire de la documentation Python , car il est déjà traduit, les glossaires et dictionnaires de traduc.org , en particulier le grand dictionnaire terminologique de l'Office québécois de la langue française, Wikipédia. En consultant un article sur la version anglaise, puis en basculant sur la version française pour voir comment le sujet de l'article est traduit ; le guide stylistique pour le français de localisation des produits Sun donne beaucoup de conseils pour éviter une traduction trop mot à mot ; Petites leçons de typographie , résumé succinct de typographie, utile pour apprendre le bon usage des majuscules, des espaces, etc. L'utilisation de traducteurs automatiques comme DeepL ou semi-automatiques comme reverso est proscrite. Les traductions générées sont très souvent à retravailler, ils ignorent les règles énoncées sur cette page et génèrent une documentation au style très « lourd ». Caractères spéciaux et typographie La touche de composition Cette touche , absente par défaut des claviers, permet de saisir des caractères spéciaux en combinant les caractères déjà présents sur le clavier. C'est à l'utilisateur de définir la touche de composition. Avec une touche de composition, vous pouvez utiliser les compositions suivantes : Compose < < donne « Compose > > donne » Compose SPACE SPACE donne une espace insécable Compose . . . donne … Comme vous l'avez noté, presque toutes les compositions sont intuitives, vous pouvez donc en essayer d'autres et elles devraient tout simplement fonctionner : Compose C = donne € Compose 1 2 donne ½ Compose ' E donne É etc. Comment définir la touche de composition ? Cela dépend de votre système d'exploitation et de votre clavier. ⇒ Sous Linux, Unix et *BSD (tel OpenBSD), vous pouvez la configurer à l'aide de l'outil graphique de configuration de votre clavier ou avec dpkg-reconfigure keyboard-configuration (pour Ubuntu ou Debian et distributions assimilées). À tout le moins, vous pouvez configurer votre fichier ~/.Xmodmap pour ajouter l'équivalent de : # key Compose keycode 115 = Multi_key Utilisez xev pour connaître la bonne correspondance de la touche que vous voulez assigner ! Ensuite, dans votre fichier ~/.xsession , ajoutez : # Gestion des touches clavier xmodmap $HOME/.Xmodmap ⇒ Sous X, avec un bureau graphique, tel que Gnome, ou Xfce, il faut aller modifier dans les « Paramètres » → « Clavier » → « Disposition » → « Touche composée ». Pour finir, redémarrez votre session. ⇒ Sous Windows, vous pouvez utiliser wincompose . Le cas de « --- », « -- », « ... » La version anglaise utilise les smartquotes , qui fonctionnent en anglais, mais causent des problèmes dans d'autres langues. Nous les avons donc désactivées (voir #303) dans la version française. Les smartquotes sont normalement responsables de la transformation de -- en en-dash ( — ), de --- en em-dash ( — ), et de ... en ellipses … . ⇒ Si vous voyez : | « -- » ou « --- » : faites Compose - - - | « ... » : faites Compose . . . Le cas de « "…" » Les guillemets français « et » ne sont pas identiques aux guillemets anglais " . Cependant, Python utilise les guillemets anglais comme délimiteurs de chaîne de caractères. Il convient donc de traduire les guillemets mais pas les délimiteurs de chaîne. ⇒ Si vous voyez : | « "…" » : faites Compose < < ou Compose > > Le cas de « :: » Du point de vue du langage reStructuredText (ou rst ) utilisé dans la documentation nous voyons soit « bla bla:: », soit « bla bla. :: ». :: collé à la fin d'un mot signifie « affiche : et introduit un bloc de code », mais un :: après une espace signifie « introduit juste un bloc de code ». En français, nous mettons une espace insécable devant nos deux-points, comme : « Et voilà : ». ⇒ Traduisez mot deux-points deux-points par mot espace-insécable deux-points deux-points . Pour saisir une espace insécable faites Compose SPACE SPACE Les doubles-espaces La documentation originale comporte beaucoup de doubles-espaces. Cela se fait en anglais, mais pas en français. De toute manière, ils passent ensuite à une moulinette et le rendu des espaces est délégué au HTML et au PDF, qui n'en tiennent pas compte. Nous avons décidé de ne rien changer pour les doubles-espaces coté traduction : nous ne les retirons pas et ce n'est pas grave si des traducteurs en retirent par accident. Les énumérations Chaque paragraphe d'une énumération introduite par un deux-point doit se terminer par un point-virgule (bien entendu précédé d'une espace insécable) quelle que soit sa ponctuation interne. Seul le dernier paragraphe de l'énumération s'achève par un point ou, si la phrase continue après l'énumération, une virgule. Si l'un des paragraphes est lui-même une énumération, chacun des sous-paragraphes se termine par une virgule et le dernier par un point-virgule. Par exemple : le premier paragraphe de l'énumération ; le deuxième paragraphe, lui aussi une énumération : premier sous-paragraphe, second sous-paragraphe ; le dernier paragraphe. Malheureusement Poedit n'aime pas les différences de ponctuation finales entre un paragraphe et sa traduction ; il faut passer outre ses avertissements. Vous pouvez aussi rajouter un commentaire dans le fichier .po pour avertir les traducteurs suivants et éviter qu'ils ne « corrigent » par erreur ces avertissements. Migration vers Gitea En novembre 2022, le dépôt de cette traduction a migré de GitHub à une instance de Gitea hébergée par l'AFPy. Si vous contribuiez auparavant sur GitHub, voici comment s'y prendre pour la migration : Suivez le guide plus haut pour faire une bifurcation ( fork ) du dépôt sur Gitea. De manière facultative mais recommandée, ajoutez votre clé SSH à votre profil Gitea comme expliqué ci-dessus (vous aviez probablement une clé sur GitHub, auquel cas il suffit de réutiliser la même, qui doit se trouver dans le fichier ~/.ssh/id_ed25519.pub ou un nom similaire). Exécutez ces deux commandes pour mettre à jour votre dépôt local afin qu'il interagisse avec Gitea au lieu de GitHub : git remote set-url upstream https://git.afpy.org/AFPy/python-docs-fr.git git remote set-url origin git@git.afpy.org:VOTRE_NOM_DE_COMPTE_GITEA/python-docs-fr.git Si vous avez choisi d'utiliser le HTTPS à la place du SSH, remplacez la deuxième ligne par : git remote set-url origin https://git.afpy.org/VOTRE_NOM_DE_COMPTE_GITEA/python-docs-fr.git Powered by Forgejo Version: 13.0.3 Page: 1863ms Template: 5ms English Bahasa Indonesia Dansk Deutsch English Español Esperanto Filipino Français Italiano Latviešu Magyar nyelv Nederlands Plattdüütsch Polski Português de Portugal Português do Brasil Slovenščina Suomi Svenska Türkçe Čeština Ελληνικά Български Русский Українська فارسی 日本語 简体中文 繁體中文（台灣） 繁體中文（香港） 한국어 Licenses API Mentions légales CGU | 2026-01-13T08:48:42 |
https://golf.forem.com/privacy#b-administrative-purposes | Privacy Policy - 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 Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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:48:42 |
https://youtube.com/ | YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:48:42 |
https://golf.forem.com/privacy#4-how-we-disclose-your-information | Privacy Policy - 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 Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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:48:42 |
https://golf.forem.com/privacy#d-other-purposes | Privacy Policy - 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 Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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:48:42 |
https://golf.forem.com/youtube_golf/golfcom-warming-up-with-jon-rahm-and-tyrrell-hatton-1m4l | Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton - 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 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 YouTube Golf Posted on Jul 10, 2025 Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton # golfyoutube # livgolf # rydercup # mentalgame Jon Rahm and Tyrrell Hatton team up on GOLF.com’s Warming Up series, showing why they’re golf soulmates both on and off the course. They share plenty of laughs—Hatton calls Rahm a “big teddy bear” despite his fierce on-course look, while Rahm insists Hatton is “one of the funniest people you’ll ever meet.” Beyond the jokes, they dive into their game-day mindsets: Rahm says he’s “irrationally positive,” whereas Hatton warns that too much positivity can drain you. Their chemistry and contrasting approaches make this rare two-player interview a must-watch for golf fans. 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 YouTube Golf Follow Joined Jun 22, 2025 More from YouTube Golf No Laying Up Podcast: Everyone Only: The Gimme Golf Club Origin Story | NLU Pod, Ep 1033 # golf # golfpodcasts # golfyoutube # localgolf Golf.com: Bringing the Anthem to the PGA Tour: One Family's Story of Service # pgatour # historyofgolf # golfyoutube # golfmedia Golf.com: Secrets of Long Island Private Golf: A 1-Member Club, Hamptons Hideaways and Caddie Confessionals # coursereviews # golfdestinations # localgolf # golfyoutube 💎 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:48:42 |
https://docs.suprsend.com/reference/cli-profile-remove | Remove Profile - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Profile Remove Profile Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Profile Remove Profile OpenAI Open in ChatGPT Delete unused profile from Local configuration file. OpenAI Open in ChatGPT Syntax Copy Ask AI suprsend profile remove [flags] Flags Flag Description Default -h, --help Show help for the command – --name string Name of the profile to remove (required) – Example Copy Ask AI suprsend profile remove --name unused-profile Was this page helpful? Yes No Suggest edits Raise issue Previous Sync Assets Merge assets from workspace to another workspace Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example | 2026-01-13T08:48:42 |
https://docs.suprsend.com/reference/cli-translation-pull | Pull Translations - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Translation Pull Translations Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Translation Pull Translations OpenAI Open in ChatGPT Fetch translations from SuprSend workspace to local directory OpenAI Open in ChatGPT This action does not delete existing translations; instead, it overwrites translations with the same identifier or creates new ones. By default, pulled translations are stored in the suprsend/translation/ directory, but you can change the destination using the -d, --dir flag. We recommend specifying a directory when working with multiple production or staging workspaces. Syntax Copy Ask AI suprsend translation pull [flags] Flags Flag Description Default -h, --help Show help for the command – -d, --dir string Output directory for translations – -f, --force Force pull to default directory without prompting the user. Use it in your CI/CD pipeline to avoid manual intervention. – -m, --mode string Mode of translations to pull from live Example Copy Ask AI # Pull all live translations to default directory suprsend translation pull # Pull translations into custom directory path suprsend translation pull --dir dev-environment/translations # Pull translations from production workspace suprsend translation pull --workspace production # Pull draft translations suprsend translation pull --mode draft # Force pull to default directory without prompting suprsend translation pull --force Was this page helpful? Yes No Suggest edits Raise issue Previous Push Translations Push translations from local directory to SuprSend Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example | 2026-01-13T08:48:42 |
https://golf.forem.com/privacy#12-contact-us | Privacy Policy - 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 Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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:48:42 |
https://golf.forem.com/t/livgolf | Livgolf - 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 # livgolf Follow Hide Discussions about the LIV Golf league, its players, and format Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? # golfyoutube # roundrecap # dpworldtour # livgolf Comments Add Comment 1 min read Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton # golfyoutube # livgolf # rydercup # mentalgame Comments Add Comment 1 min read Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? YouTube Golf YouTube Golf YouTube Golf Follow Jul 9 '25 Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? # golfyoutube # roundrecap # formats # livgolf Comments Add Comment 1 min read Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? YouTube Golf YouTube Golf YouTube Golf Follow Jul 8 '25 Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? # golfyoutube # roundrecap # dpworldtour # livgolf Comments Add Comment 1 min read Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? YouTube Golf YouTube Golf YouTube Golf Follow Jul 7 '25 Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? # roundrecap # golfyoutube # livgolf # dpworldtour 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 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:48:42 |
https://twitter.com/survivejs/ | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:48:42 |
https://www.anaconda.com/distribution | Download Anaconda Distribution | Anaconda Skip to content Products ANACONDA PLATFORM Platform Overview Enterprise Python and AI Anaconda Core Python package management Anaconda AI Catalyst AI development suite Deployment Options Cloud, self-hosted, and more FOR DEVELOPERS Anaconda Distribution Navigator Notebooks Excel Toolbox PLATFORM BENEFITS Security & Governance Trusted Distribution Actionable Insights PLATFORM & LICENSING Pricing & Plans Buy Starter Licenses Buy Business Licenses Solutions CAPABILITIES AI/ML Model Development Team Collaboration Code Assistance View All Capabilities → INDUSTRIES Education Financial Services Healthcare Manufacturing Technology SERVICES & SUPPORT Professional Services Support Resources FOR USERS Community Forums Documentation Download Distribution Getting Started Guide Tutorials & Learning MEET US Events Podcast Webinars ARTICLES Blog Case Studies Guides Topics Whitepapers SUPPORT Help Center Professional Services System Status Company ABOUT US Our Story Leadership Team Partners PRESS Press Releases In the News CONTACT Contact Us Sales Inquiries CAREERS Join Our Team Free Download Sign In Get Demo Distribution Register to get everything you need to get started on your workstation including Cloud Notebooks, Navigator, AI Assistant, Learning and more. Easily search and install thousands of data science, machine learning, and AI packages Manage packages and environments from a desktop application or work from the command line Deploy across hardware and software platforms Distribution installation on Windows, MacOS, or Linux Distribution Register to get everything you need to get started on your workstation including Cloud Notebooks, Navigator, AI Assistant, Learning and more. Easily search and install thousands of data science, machine learning, and AI packages Manage packages and environments from a desktop application or work from the command line Deploy across hardware and software platforms Distribution installation on Windows, MacOS, or Linux For students and researchers, create an account for free using your education domain. Learn more about Anaconda for Education plan . Download Now Get access in 30 seconds. Completely free.* Get Started Returning Users *Subject to our Terms of Service . Use of Anaconda’s offerings at an organization of more than 200 employees/contractors requires a paid business license unless your organization is eligible for discounted or free use. See Pricing . Distribution Free Download* Register to get everything you need to get started on your workstation including Cloud Notebooks, Navigator, AI Assistant, Learning and more. Easily search and install thousands of data science, machine learning, and AI packages Manage packages and environments from a desktop application or work from the command line Deploy across hardware and software platforms Distribution installation on Windows, MacOS, or Linux *Subject to our Terms of Service . Use of Anaconda’s offerings at an organization of more than 200 employees/contractors requires a paid business license unless your organization is eligible for discounted or free use. See Pricing . Provide email to download Distribution Don't miss out! Get access to: Cloud Notebooks, Anaconda Assistant, easy application deployment, learning resources, and updates from Anaconda. * Email Address: Please enter your email address. * Opt In: Agree to receive communication from Anaconda regarding relevant content, products, and services. By continuing, I agree to Anaconda's Privacy Policy and Terms of Service . Submit Skip registration Success! Please check your email for the download link. Manage Trusted Packages and Environments with Ease Spend more time developing and less time managing package updates and dependencies Open Source Access the open-source software you need for projects in any field, from data visualization to robotics. User-friendly With our intuitive platform, you can easily search and install packages and create, load, and switch between environments. Trusted Our securely hosted packages and artifacts are methodically tested and regularly updated. Powered by the Most Recommended and Trusted Open-Source Packages Get Started Today Data Exploration and Transformation Numpy pandas Jupyter Intake Dask Visualization Matplotlib seaborn Plotly Bokey HoloViews AI and Machine Learning scikit-learn TensorFlow Keras PyTorch XGBoost Natural Language Processing NLTK Gensim Transformers SpaCy GUI and Front-End Development Flask CherryPy Streamlit Panel Discover More Millions of developers and data scientists research, innovate, and discover using Anaconda Distribution Repository Over 8,000 open-source data science and machine learning packages, Anaconda-built and compiled for all major operating systems and architectures. Learn More Conda Open-source package and environment management system that runs on Windows, macOS, and Linux. Install, run, and update packages and their dependencies. Learn More Navigator Desktop application lets you easily manage integrated applications, packages, and environments without using the command line. Learn More Cloud Environment Backup Connect Anaconda Navigator to our community portal to securely store your local environments in the cloud. Learn More Miniconda Installer Miniconda is a free minimal installer for conda. It is a small bootstrap version of Anaconda that includes only conda, Python, the packages they both depend on, and a small number of other useful packages (like pip, zlib, and a few others). Download Miniconda Installer Company Press Careers Contact Us Press Careers Contact Us Products Anaconda Platform Capabilities Professional Services Pricing Anaconda Platform Capabilities Professional Services Pricing Customers Cloud Login Support Center Learning Catalog Docs Community Cloud Login Support Center Learning Catalog Docs Community Popular AI Governance Guide AI Platform Guide Python Data Structures Guide State of Data Science Report AI Governance Guide AI Platform Guide Python Data Structures Guide State of Data Science Report Create Account Contact Sales Create Account Contact Sales Facebook X-twitter Linkedin Github Instagram Youtube © 2025 Anaconda Inc. All rights reserved. Legal Accessibility Privacy Policy Terms of Use Legal Accessibility Privacy Policy Terms of Use | 2026-01-13T08:48:42 |
https://highlight.io/blog/launchdarkly-migration?utm_source=highlight-banner | Migrating from Highlight.io to LaunchDarkly Observability Pricing Customers Blog Careers Docs Migrating from Highlight.io to LaunchDarkly Observability Sign up Back Sep 30, 2022 • 9 min. read 3 Levels of Data Validation in a Full Stack Application With React Engineering May 9, 2023 • 7 min. read Supporting Outside Contributions at Highlight Engineering Oct 18, 2023 • 10 min. read Migrating from OpenSearch to Clickhouse Product Updates Nov 13, 2025 • 11 min read Migrating from Highlight.io to LaunchDarkly Observability Company Product Updates Jay Khatri Co-founder & CEO TLDR All of the Highlight.io features you know and love are now available in the LaunchDarkly Observability product. Highlight.io will be deprecating services on February 28, 2026 and moving 100% of our infrastructure and services to LaunchDarkly. Instead of logging into https://app.highlight.io , we recommend creating a new account and migrating your SDK snippets to use LaunchDarkly Observability (at https://app.launchdarkly.com ). Customers will need to update their Highlight SDK Snippet to use LaunchDarkly before March 1, 2026 to avoid any disruption of service. If you have any questions about the process please reference the FAQ below! If you don't see your question answered, feel free to contact the team at observability@launchdarkly.com . Migration Example (JS) Before H.init('YOUR_PROJECT_ID', { privacySetting: 'strict', networkRecording: { enabled: true, recordHeadersAndBody: true, }, tracingOrigins: ['pri.highlight.io'], enableCanvasRecording: true, samplingStrategy: { canvas: 1, canvasFactor: 0.5, canvasMaxSnapshotDimension: 480, }, serviceName: 'web', environment: 'env', version: 'version', }) After const client = initialize('LD_CLIENT_SIDE_ID', {user: {key: 'abc123', email: 'bob@example.com'}}, { // copy settings values based on what you had previously configured plugins: [ new Observability({ tracingOrigins: ['pri.highlight.io'], networkRecording: { enabled: true, recordHeadersAndBody: true, }, serviceName: 'web', environment: 'env', version: 'version', }), new SessionReplay({ privacySetting: 'strict', enableCanvasRecording: true, samplingStrategy: { canvas: 1, canvasFactor: 0.5, canvasMaxSnapshotDimension: 480, }, contextFriendlyName: (ctx) => ctx.user.email, serviceName: 'web', environment: 'env', version: 'version', }), ], }) FAQ Q: Will my pricing change? If you are a Highlight self-service customer, you are expected to choose a LaunchDarkly self-service tier: Developer or Foundation. The Developer plan is $0 per month, and includes the following (monthly recurring) allotments: 3 service connections (for feature flagging) 5,000 sessions 5,000 errors 10,000,000 logs 10,000,000 traces No "overages" The Foundation self-serve plan is billed per service connection and per observability unit. Please refer to the pricing page here . If you are a Highlight customer who is on an invoiced plan or MSA, we will reach out personally. If you don't hear from us, please reach out to observability@launchdarkly.com . Q: When will services officially end on Highlight.io? February 28, 2026 Q: Will I need to migrate my existing data in Highlight to LaunchDarkly? Not necessarily. But if you would like to migrate your existing data / configuration, please reach out to our team at observability@launchdarkly.com . Q: Do I need to purchase a new LaunchDarkly self-serve license? When you sign up for a LaunchDarkly self-serve plan, you will be expected to accept the LaunchDarkly licensing terms. If you exceed the free tier limits for any of the LaunchDarkly products, and (like in Highlight), you'll pay for any monthly overages. Q: Can I connect my observability data to LaunchDarkly feature flags? Yes! LaunchDarkly observability connects to the rest of the LD platform. Feature flags, experiments, AI Observability and more! Q: If I want to learn more about Feature Flagging how do I get connected? We are happy to connect you to the appropriate LaunchDarkly representative. Email observability@launchdarkly.com for more. Q: I am already a LaunchDarkly customer. What does this mean for me? If you are already a usage based self-service customer of LD, you are one step ahead in the process. You will still need to change your SDK snippet to send data to your current account. If you're an enterprise customer, please reach out to observability@launchdarkly.com for more information. Q: Will my invoicing date change? Yes, LaunchDarkly invoices on a calendar month cadence. Comments ( 0 ) Name Email Your Message New Comment Other articles you may like Sep 30, 2022 • 9 min. read 3 Levels of Data Validation in a Full Stack Application With React Engineering May 9, 2023 • 7 min. read Supporting Outside Contributions at Highlight Engineering Oct 18, 2023 • 10 min. read Migrating from OpenSearch to Clickhouse Product Updates Try Highlight Today Get the visibility you need Get started for free Product Pricing Sign up Features Privacy & Security Customers Session Replay Error Monitoring Logging Competitors LogRocket Hotjar Fullstory Smartlook Inspectlet Datadog Sentry Site24x7 Sprig Mouseflow Pendo Heap LogicMonitor Last9 Axiom Better Stack HyperDX Dash0 Developers Changelog Documentation Ambassadors Frameworks React Next.js Angular Gatsby.js Svelte.js Vue.js Express Golang Next.js Node.js Rails Hono Contact & Legal Terms of Service Privacy Policy Careers sales@highlight.io security@highlight.io [object Object] | 2026-01-13T08:48:42 |
https://www.youtube.com/watch?v=8pDqJVdNa44 | How A Small Team of Developers Created React at Facebook | React.js: The Documentary - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x8264d066214363d5"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtEQzg3a2RzLV9mbyjnjZjLBjIKCgJLUhIEGgAgMw%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRjjT2a1NiqcVLMcowODr1bBFYshiY7e1a06HRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","videoMetadataCarouselViewModel","carouselTitleViewModel","carouselItemViewModel","textCarouselItemViewModel","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","badgeViewModel","autoplay","liveChatRenderer","liveChatHeaderRenderer","sortFilterSubMenuRenderer","clientSideToggleMenuItemRenderer","menuNavigationItemRenderer","playerOverlayRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","markerRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","expandableVideoDescriptionBodyRenderer","expandableMetadataRenderer","videoSummaryContentViewModel","videoSummaryParagraphViewModel","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","compactInfocardRenderer","structuredDescriptionVideoLockupRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cardCollectionRenderer","cardRenderer","simpleCardTeaserRenderer","cinematicContainerRenderer","microformatDataRenderer"]},"ytConfigData":{"visitorData":"CgtEQzg3a2RzLV9mbyjnjZjLBjIKCgJLUhIEGgAgMw%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwiS_IT3kIiSAxWi90wCHTZjB9gyDHJlbGF0ZWQtYXV0b0iO17W61cS6yPIBmgEFCAMQ-B3KAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=783ccP__No8\u0026pp=QAFIAdIHCQmjAp4VBgUm4g%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"783ccP__No8","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAdIHCQmjAp4VBgUm4g%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwiS_IT3kIiSAxWi90wCHTZjB9gyDHJlbGF0ZWQtYXV0b0iO17W61cS6yPIBmgEFCAMQ-B3KAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=783ccP__No8\u0026pp=QAFIAdIHCQmjAp4VBgUm4g%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"783ccP__No8","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAdIHCQmjAp4VBgUm4g%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwiS_IT3kIiSAxWi90wCHTZjB9gyDHJlbGF0ZWQtYXV0b0iO17W61cS6yPIBmgEFCAMQ-B3KAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=783ccP__No8\u0026pp=QAFIAdIHCQmjAp4VBgUm4g%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"783ccP__No8","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAdIHCQmjAp4VBgUm4g%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"How A Small Team of Developers Created React at Facebook | React.js: The Documentary"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 1,611,012회"},"shortViewCount":{"simpleText":"조회수 161만회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CK0CEMyrARgAIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESCzhwRHFKVmROYTQ0GmBFZ3M0Y0VSeFNsWmtUbUUwTkVBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTHpod1JIRktWbVJPWVRRMEwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CK0CEMyrARgAIhMIkvyE95CIkgMVovdMAh02YwfY"}}],"trackingParams":"CK0CEMyrARgAIhMIkvyE95CIkgMVovdMAh02YwfY","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"4만","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLkCEKVBIhMIkvyE95CIkgMVovdMAh02YwfY"}},{"innertubeCommand":{"clickTrackingParams":"CLkCEKVBIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLoCEPqGBCITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLoCEPqGBCITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"8pDqJVdNa44"},"likeParams":"Cg0KCzhwRHFKVmROYTQ0IAAyDAjojZjLBhCqtrK5Ag%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CLoCEPqGBCITCJL8hPeQiJIDFaL3TAIdNmMH2A=="}}}}}}}]}},"accessibilityText":"다른 사용자 40,293명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLkCEKVBIhMIkvyE95CIkgMVovdMAh02YwfY","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"4만","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLgCEKVBIhMIkvyE95CIkgMVovdMAh02YwfY"}},{"innertubeCommand":{"clickTrackingParams":"CLgCEKVBIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"8pDqJVdNa44"},"removeLikeParams":"Cg0KCzhwRHFKVmROYTQ0GAAqDAjojZjLBhCe6bO5Ag%3D%3D"}}}]}},"accessibilityText":"다른 사용자 40,293명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLgCEKVBIhMIkvyE95CIkgMVovdMAh02YwfY","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CK0CEMyrARgAIhMIkvyE95CIkgMVovdMAh02YwfY","isTogglingDisabled":true}},"likeStatusEntityKey":"Egs4cERxSlZkTmE0NCA-KAE%3D","likeStatusEntity":{"key":"Egs4cERxSlZkTmE0NCA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLYCEKiPCSITCJL8hPeQiJIDFaL3TAIdNmMH2A=="}},{"innertubeCommand":{"clickTrackingParams":"CLYCEKiPCSITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLcCEPmGBCITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLcCEPmGBCITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"8pDqJVdNa44"},"dislikeParams":"Cg0KCzhwRHFKVmROYTQ0EAAiDAjojZjLBhCY-bW5Ag%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CLcCEPmGBCITCJL8hPeQiJIDFaL3TAIdNmMH2A=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLYCEKiPCSITCJL8hPeQiJIDFaL3TAIdNmMH2A==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLUCEKiPCSITCJL8hPeQiJIDFaL3TAIdNmMH2A=="}},{"innertubeCommand":{"clickTrackingParams":"CLUCEKiPCSITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"8pDqJVdNa44"},"removeLikeParams":"Cg0KCzhwRHFKVmROYTQ0GAAqDAjojZjLBhDkpLa5Ag%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLUCEKiPCSITCJL8hPeQiJIDFaL3TAIdNmMH2A==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CK0CEMyrARgAIhMIkvyE95CIkgMVovdMAh02YwfY","isTogglingDisabled":true}},"dislikeEntityKey":"Egs4cERxSlZkTmE0NCA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","timedAnimationData":{"animationTiming":[3957044],"playerTimeEntityKey":"Eh4veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3RpbWUgxgIoAQ%3D%3D","playerLayoutStateEntityKey":"EiYveW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX2xheW91dF9zdGF0ZSDIAigB","playerStateEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","enableMobileTimedAnimation":false,"macroMarkersIndex":[1],"animationDurationSecs":1.5,"borderStrokeThicknessDp":2,"borderOpacity":1,"trackingParams":"CLQCEPBbIhMIkvyE95CIkgMVovdMAh02YwfY","animationOrigin":"ANIMATION_ORIGIN_SMARTIMATION","animationStyle":"ANIMATED_BUTTON_BORDER_ANIMATION_STYLE_UNKNOWN"},"likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"Egs4cERxSlZkTmE0NCD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLICEOWWARgCIhMIkvyE95CIkgMVovdMAh02YwfY"}},{"innertubeCommand":{"clickTrackingParams":"CLICEOWWARgCIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgs4cERxSlZkTmE0NKABAQ%3D%3D","commands":[{"clickTrackingParams":"CLICEOWWARgCIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CLMCEI5iIhMIkvyE95CIkgMVovdMAh02YwfY","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLICEOWWARgCIhMIkvyE95CIkgMVovdMAh02YwfY","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CLACEOuQCSITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLECEPuGBCITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D8pDqJVdNa44\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLECEPuGBCITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"8pDqJVdNa44","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=f290ea25574d6b8e\u0026ip=1.208.108.242\u0026initcwndbps=3655000\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CLECEPuGBCITCJL8hPeQiJIDFaL3TAIdNmMH2A=="}}}}}},"trackingParams":"CLACEOuQCSITCJL8hPeQiJIDFaL3TAIdNmMH2A=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CK4CEOuQCSITCJL8hPeQiJIDFaL3TAIdNmMH2A=="}},{"innertubeCommand":{"clickTrackingParams":"CK4CEOuQCSITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CK8CEPuGBCITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D8pDqJVdNa44\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CK8CEPuGBCITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"8pDqJVdNa44","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=f290ea25574d6b8e\u0026ip=1.208.108.242\u0026initcwndbps=3655000\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CK8CEPuGBCITCJL8hPeQiJIDFaL3TAIdNmMH2A=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CK4CEOuQCSITCJL8hPeQiJIDFaL3TAIdNmMH2A==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CK0CEMyrARgAIhMIkvyE95CIkgMVovdMAh02YwfY","dateText":{"simpleText":"최초 공개: 2023. 2. 10."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"2년 전"}},"simpleText":"2년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/JEY96H2ij7Xg9YaKv8vNZLu4M_Y2XzF_Zcx4GihTk0imoAdHTmwIlFWrygX0Z41rSNvP5Eud=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/JEY96H2ij7Xg9YaKv8vNZLu4M_Y2XzF_Zcx4GihTk0imoAdHTmwIlFWrygX0Z41rSNvP5Eud=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/JEY96H2ij7Xg9YaKv8vNZLu4M_Y2XzF_Zcx4GihTk0imoAdHTmwIlFWrygX0Z41rSNvP5Eud=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"CultRepo ","navigationEndpoint":{"clickTrackingParams":"CKwCEOE5IhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","commandMetadata":{"webCommandMetadata":{"url":"/@cultrepo","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCsUalyRg43M8D60mtHe6YcA","canonicalBaseUrl":"/@cultrepo"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CKwCEOE5IhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","commandMetadata":{"webCommandMetadata":{"url":"/@cultrepo","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCsUalyRg43M8D60mtHe6YcA","canonicalBaseUrl":"/@cultrepo"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 34.4만명"}},"simpleText":"구독자 34.4만명"},"trackingParams":"CKwCEOE5IhMIkvyE95CIkgMVovdMAh02YwfY"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCsUalyRg43M8D60mtHe6YcA","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CJ0CEJsrIhMIkvyE95CIkgMVovdMAh02YwfYKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"CultRepo 을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"CultRepo 을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. CultRepo 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CKsCEPBbIhMIkvyE95CIkgMVovdMAh02YwfY","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. CultRepo 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. CultRepo 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CKoCEPBbIhMIkvyE95CIkgMVovdMAh02YwfY","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. CultRepo 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CKMCEJf5ASITCJL8hPeQiJIDFaL3TAIdNmMH2A==","command":{"clickTrackingParams":"CKMCEJf5ASITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CKMCEJf5ASITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CKkCEOy1BBgDIhMIkvyE95CIkgMVovdMAh02YwfYMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ3NVYWx5Umc0M004RDYwbXRIZTZZY0ESAggBGAAgBFITCgIIAxILOHBEcUpWZE5hNDQYAA%3D%3D"}},"trackingParams":"CKkCEOy1BBgDIhMIkvyE95CIkgMVovdMAh02YwfY","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CKgCEO21BBgEIhMIkvyE95CIkgMVovdMAh02YwfYMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ3NVYWx5Umc0M004RDYwbXRIZTZZY0ESAggDGAAgBFITCgIIAxILOHBEcUpWZE5hNDQYAA%3D%3D"}},"trackingParams":"CKgCEO21BBgEIhMIkvyE95CIkgMVovdMAh02YwfY","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CKQCENuLChgFIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKQCENuLChgFIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CKUCEMY4IhMIkvyE95CIkgMVovdMAh02YwfY","dialogMessages":[{"runs":[{"text":"CultRepo "},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CKcCEPBbIhMIkvyE95CIkgMVovdMAh02YwfYMgV3YXRjaMoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCsUalyRg43M8D60mtHe6YcA"],"params":"CgIIAxILOHBEcUpWZE5hNDQYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CKcCEPBbIhMIkvyE95CIkgMVovdMAh02YwfY"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CKYCEPBbIhMIkvyE95CIkgMVovdMAh02YwfY"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CKQCENuLChgFIhMIkvyE95CIkgMVovdMAh02YwfY"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CJ0CEJsrIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CKICEP2GBCITCJL8hPeQiJIDFaL3TAIdNmMH2DIJc3Vic2NyaWJlygEEGe75gw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D8pDqJVdNa44%26continue_action%3DQUFFLUhqa0ZXQVMzU3FPRDgwcWVPTzRYWThFQmF6ZzUyZ3xBQ3Jtc0tsSER3aUhWekVhVTBvYjBXVUM5WGstUDczQmQzMXgtRElwNzR5RkFNMmo0VmhOdUp1aGxDemlGN3hsVmVkczNlYTF6YWxzLTUyYUtrbFAzZndBcEFLejU2UXpTUEpvYU9PcGdFRHRaQUZuX2ppOFk3ZkZkOXdRUzYzeHVUeUh5ZFJsTUh0ZWp1Q1dEOVRrVUtWY05EVlRwMmQxSVRILTNKY1h5eGRpcTBFYWFFRVE3X3dkeW05LVFMMFAwNWR2VG1MQjJuRDk\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CKICEP2GBCITCJL8hPeQiJIDFaL3TAIdNmMH2MoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"8pDqJVdNa44","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=f290ea25574d6b8e\u0026ip=1.208.108.242\u0026initcwndbps=3655000\u0026mt=1768293662\u0026oweuc="}}}}},"continueAction":"QUFFLUhqa0ZXQVMzU3FPRDgwcWVPTzRYWThFQmF6ZzUyZ3xBQ3Jtc0tsSER3aUhWekVhVTBvYjBXVUM5WGstUDczQmQzMXgtRElwNzR5RkFNMmo0VmhOdUp1aGxDemlGN3hsVmVkczNlYTF6YWxzLTUyYUtrbFAzZndBcEFLejU2UXpTUEpvYU9PcGdFRHRaQUZuX2ppOFk3ZkZkOXdRUzYzeHVUeUh5ZFJsTUh0ZWp1Q1dEOVRrVUtWY05EVlRwMmQxSVRILTNKY1h5eGRpcTBFYWFFRVE3X3dkeW05LVFMMFAwNWR2VG1MQjJuRDk","idamTag":"66429"}},"trackingParams":"CKICEP2GBCITCJL8hPeQiJIDFaL3TAIdNmMH2A=="}}}}}},"subscribedEntityKey":"EhhVQ3NVYWx5Umc0M004RDYwbXRIZTZZY0EgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CJ0CEJsrIhMIkvyE95CIkgMVovdMAh02YwfYKPgdMgV3YXRjaMoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCsUalyRg43M8D60mtHe6YcA"],"params":"EgIIAxgAIgs4cERxSlZkTmE0NA%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CJ0CEJsrIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJ0CEJsrIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CJ8CEMY4IhMIkvyE95CIkgMVovdMAh02YwfY","dialogMessages":[{"runs":[{"text":"CultRepo "},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CKECEPBbIhMIkvyE95CIkgMVovdMAh02YwfYKPgdMgV3YXRjaMoBBBnu-YM=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCsUalyRg43M8D60mtHe6YcA"],"params":"CgIIAxILOHBEcUpWZE5hNDQYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CKECEPBbIhMIkvyE95CIkgMVovdMAh02YwfY"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CKACEPBbIhMIkvyE95CIkgMVovdMAh02YwfY"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}],"timedAnimationData":{"animationTiming":[4680930],"macroMarkersIndex":[0],"animationDurationSecs":1.5,"borderStrokeThicknessDp":2,"borderOpacity":1,"fillOpacity":0,"trackingParams":"CJ4CEPBbIhMIkvyE95CIkgMVovdMAh02YwfY","animationOrigin":"ANIMATION_ORIGIN_SMARTIMATION"}}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfY"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfY","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYygEEGe75gw==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"React is easily one of the single most popular libraries in use today. Given that it was made within a juggernaut like Facebook, you might have assumed it was always destined for success.\nBut what if we told you that React’s first brush with the public sphere was anything but glamorous? React.js: The Documentary brings you the full story behind the early days of React, focusing on the dedicated group of developers who helped bring it to the world stage. This story is told by an all-star cast of developers like Tom Occhino, Christopher Chedeau, Pete Hunt, Sebastian Markbåge, Dan Abramov, and many more.\n\nFollow the cast:\nAdam Wolff: / dmwlff \nAndrew Clark: / acdlite \nChristopher Chedeau: / vjeux \nDan Abramov: / dan_abramov \nDavid Nolen: / swannodette \nLee Byron: / leeb \nMichael Chan: / chantastic \nPete Hunt: / floydophone \nSebastian Markbåge: / sebmarkbage \nShane O'Sullivan: / chofter and https://chofter.com/\nSophie Alpert: / sophiebits and https://sophiebits.com/\nTom Occhino: / tomocchino \nTony Casparro: / iamtonyc \n\nMany people contributed to React throughout the years and this documentary is just a little slice of that history. You can find full acknowledgements here: https://reactjs.org/acknowledgements....\n\nThanks to these amazing people for translating subtitles:\nCharlie: / charliesbot \nJose: / jbetosalinas \nGustavo Gonçalves\nAnd to @itdocru for the Russian dub!","commandRuns":[{"startIndex":639,"length":12,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqblhFcE95Rnk3RmFTQi1xb3FteTJaTUQwX1d4QXxBQ3Jtc0tsdGtGQzJJWmZFSkhuS2tFTlowMUowNXJWbXNWR21Xa2ZKZmREdngxX29Zc3JsdHNWT0tnd0EzYm5Pc2JpeG9Rd0ZrRVpaWXI0akU0MjZCcFlZU1JFNVNoQjFGb3BfTmtKcV9DV0xOS0RrLXlQeHlONA\u0026q=https%3A%2F%2Ftwitter.com%2Fdmwlff\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqblhFcE95Rnk3RmFTQi1xb3FteTJaTUQwX1d4QXxBQ3Jtc0tsdGtGQzJJWmZFSkhuS2tFTlowMUowNXJWbXNWR21Xa2ZKZmREdngxX29Zc3JsdHNWT0tnd0EzYm5Pc2JpeG9Rd0ZrRVpaWXI0akU0MjZCcFlZU1JFNVNoQjFGb3BfTmtKcV9DV0xOS0RrLXlQeHlONA\u0026q=https%3A%2F%2Ftwitter.com%2Fdmwlff\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: dmwlff"}}},{"startIndex":666,"length":13,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbjY2RkY3NDVDYkZUWmhjdE9UMFdON2syX1ktd3xBQ3Jtc0trLXhFT2ZnQTRLZEZ0azBDZXpNb3hhOXIzdjRGc3l3VHNFZkZ0WUtLOFl0Y3JDTVZ4M1VBc1ZzWXZOYU5LajdWUmNpR0F3SGVkSFlNdTBBRzRjZTRkY1hzQXNfUjI1WnJXQ2VhWmhqMUY3SHVBM0VCZw\u0026q=https%3A%2F%2Ftwitter.com%2Facdlite\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbjY2RkY3NDVDYkZUWmhjdE9UMFdON2syX1ktd3xBQ3Jtc0trLXhFT2ZnQTRLZEZ0azBDZXpNb3hhOXIzdjRGc3l3VHNFZkZ0WUtLOFl0Y3JDTVZ4M1VBc1ZzWXZOYU5LajdWUmNpR0F3SGVkSFlNdTBBRzRjZTRkY1hzQXNfUjI1WnJXQ2VhWmhqMUY3SHVBM0VCZw\u0026q=https%3A%2F%2Ftwitter.com%2Facdlite\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: acdlite"}}},{"startIndex":701,"length":11,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbGEtZjRfc1hGRU9PMEpYOFFJckh3VkhOVF9zZ3xBQ3Jtc0trd3lMMFYxMThTTnRDQkk3WWlXb0JyVldBcDA0ZDNVYkhtbHR1dDNYQ1RQLUo4enBVOGF0QS11N3djRXQ5V2UweHJIbW1MLWZBVDBWUl9TUmx0T3g1VkJaNDZlekpLdkE3VGdvS3RVcXZ4OTZyYUVJNA\u0026q=https%3A%2F%2Ftwitter.com%2FVjeux\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbGEtZjRfc1hGRU9PMEpYOFFJckh3VkhOVF9zZ3xBQ3Jtc0trd3lMMFYxMThTTnRDQkk3WWlXb0JyVldBcDA0ZDNVYkhtbHR1dDNYQ1RQLUo4enBVOGF0QS11N3djRXQ5V2UweHJIbW1MLWZBVDBWUl9TUmx0T3g1VkJaNDZlekpLdkE3VGdvS3RVcXZ4OTZyYUVJNA\u0026q=https%3A%2F%2Ftwitter.com%2FVjeux\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: Vjeux"}}},{"startIndex":726,"length":17,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqblpkSDN2OWpfNVlKUnI2Z2IyeVdBdDFERm9zd3xBQ3Jtc0tubzRicWxkZjNMSW9qMmxCS3ZiQzZlNENXWmp2eEVfOUhoLTg1WWxoODJNeEoybUl1aE9FdjNEQlQ1MXdjNlpYLUNrTFJ2UG9NQy1zbHRLQkczRmg5THk3YzVWdlFNX2FVTTNueFJxbjIwbFo4NFZoaw\u0026q=https%3A%2F%2Ftwitter.com%2Fdan_abramov\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqblpkSDN2OWpfNVlKUnI2Z2IyeVdBdDFERm9zd3xBQ3Jtc0tubzRicWxkZjNMSW9qMmxCS3ZiQzZlNENXWmp2eEVfOUhoLTg1WWxoODJNeEoybUl1aE9FdjNEQlQ1MXdjNlpYLUNrTFJ2UG9NQy1zbHRLQkczRmg5THk3YzVWdlFNX2FVTTNueFJxbjIwbFo4NFZoaw\u0026q=https%3A%2F%2Ftwitter.com%2Fdan_abramov\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: dan_abramov"}}},{"startIndex":757,"length":17,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa09VejNwdE5iaTZJenhHa0x0aFNHNEJnZTEzZ3xBQ3Jtc0ttTnJPMG9OMGt2NGdLbGh5eDBiVjA4d0ZQY0NuSk15Vmtvc1E0dWFzV1BLS1BlQzdMVXY5X2hQNmpYNGU0QWtuVTAtRTdGZEpmUDVxdkNCeERUb1Vfd3Jod0FBS2lxZ3pvS1UtZ2Fjc3BmZzVzeWd5NA\u0026q=https%3A%2F%2Ftwitter.com%2Fswannodette\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa09VejNwdE5iaTZJenhHa0x0aFNHNEJnZTEzZ3xBQ3Jtc0ttTnJPMG9OMGt2NGdLbGh5eDBiVjA4d0ZQY0NuSk15Vmtvc1E0dWFzV1BLS1BlQzdMVXY5X2hQNmpYNGU0QWtuVTAtRTdGZEpmUDVxdkNCeERUb1Vfd3Jod0FBS2lxZ3pvS1UtZ2Fjc3BmZzVzeWd5NA\u0026q=https%3A%2F%2Ftwitter.com%2Fswannodette\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: swannodette"}}},{"startIndex":786,"length":10,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbVRLUXl5ZnZ3M1MwTVl6QUdqbEtQMWtZcV9sQXxBQ3Jtc0trTzE5S3dqeGdLU29rQkJXOENRZVdFVE5Oc3ZXZVcxTnlFVW05MUd3YTYtcHdyd0hFUjVGbkZHMGdRM2xFaUZmMU4yVG1oaDNBMVgzc2tNZ3pZT0JzeTVWNmRMLVFyU0hfVGNaTWk4NFoyZl92SFVJNA\u0026q=https%3A%2F%2Ftwitter.com%2Fleeb\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbVRLUXl5ZnZ3M1MwTVl6QUdqbEtQMWtZcV9sQXxBQ3Jtc0trTzE5S3dqeGdLU29rQkJXOENRZVdFVE5Oc3ZXZVcxTnlFVW05MUd3YTYtcHdyd0hFUjVGbkZHMGdRM2xFaUZmMU4yVG1oaDNBMVgzc2tNZ3pZT0JzeTVWNmRMLVFyU0hfVGNaTWk4NFoyZl92SFVJNA\u0026q=https%3A%2F%2Ftwitter.com%2Fleeb\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: leeb"}}},{"startIndex":811,"length":16,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbWk2bHFtLVJSdU53NERpREdhQnNHMVV2Q2ViQXxBQ3Jtc0ttazM1end2dU5BOEZzUWdlSmZRUWppQzNaRlFSUVFUTk1CRmxsMmRTUzNhb1A1cm1kR3UydjN4c09qRW5WMGxlSXY3UThmTk5oOXJBcUpoY2ZFNllnZXFMaU1BMm5xQmxmdk5JeVh6b2M1dV9RSzFoTQ\u0026q=https%3A%2F%2Ftwitter.com%2Fchantastic\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbWk2bHFtLVJSdU53NERpREdhQnNHMVV2Q2ViQXxBQ3Jtc0ttazM1end2dU5BOEZzUWdlSmZRUWppQzNaRlFSUVFUTk1CRmxsMmRTUzNhb1A1cm1kR3UydjN4c09qRW5WMGxlSXY3UThmTk5oOXJBcUpoY2ZFNllnZXFMaU1BMm5xQmxmdk5JeVh6b2M1dV9RSzFoTQ\u0026q=https%3A%2F%2Ftwitter.com%2Fchantastic\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: chantastic"}}},{"startIndex":839,"length":17,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbVNDY2IwUVFYaDc5WUxRTnJhR0hfaExnZHdMUXxBQ3Jtc0ttVjB3NFFkTFhzd1Jpb3hlNzFjNVFnTmNNUlZfRjZrNmF3NkR6bHhmVEstU0l4dXZvNnplZ2NxWXl3X2dudkZfejVoWlZ1czZ6TUtZNE83a3BEVmZNQnR2ZXJRN25EaFFWTzRFemMyY2FCVFVwcXdYcw\u0026q=https%3A%2F%2Ftwitter.com%2Ffloydophone\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbVNDY2IwUVFYaDc5WUxRTnJhR0hfaExnZHdMUXxBQ3Jtc0ttVjB3NFFkTFhzd1Jpb3hlNzFjNVFnTmNNUlZfRjZrNmF3NkR6bHhmVEstU0l4dXZvNnplZ2NxWXl3X2dudkZfejVoWlZ1czZ6TUtZNE83a3BEVmZNQnR2ZXJRN25EaFFWTzRFemMyY2FCVFVwcXdYcw\u0026q=https%3A%2F%2Ftwitter.com%2Ffloydophone\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: floydophone"}}},{"startIndex":877,"length":17,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbDhTajZ0VmxuYWR5MHM2aWFYX2czWWVZUFZsUXxBQ3Jtc0tuT1I0eTJoU2NNV01mYlRFZDRXQ0tSMS1jRzN6aHVXaGR1LV93cHB1LVd0T0thWTVfU25oamdteEhELVJIVU9HcWhvVXBWNm54eHVjeXRDNjRwSVV2dVp0c1llejl4aDB6cFlaRE1CeVJVb1FDTlZ5RQ\u0026q=https%3A%2F%2Ftwitter.com%2Fsebmarkbage\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbDhTajZ0VmxuYWR5MHM2aWFYX2czWWVZUFZsUXxBQ3Jtc0tuT1I0eTJoU2NNV01mYlRFZDRXQ0tSMS1jRzN6aHVXaGR1LV93cHB1LVd0T0thWTVfU25oamdteEhELVJIVU9HcWhvVXBWNm54eHVjeXRDNjRwSVV2dVp0c1llejl4aDB6cFlaRE1CeVJVb1FDTlZ5RQ\u0026q=https%3A%2F%2Ftwitter.com%2Fsebmarkbage\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: sebmarkbage"}}},{"startIndex":913,"length":13,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0ZTamJldHplV2NUTm50X3Q2OURoeUtGNzl0d3xBQ3Jtc0trb1VYQjBZaG1mdE5ONWN1Z0NsZWhrUWIyNG5vSnh6N1NpdjRaTVlaNnZHOHFPUEl3TkNsYkFBZUZlYWFRVlFPc1NCMnJYMlJ4eXBVNTZsRFVIV3FjdFM4emRtTU9kNWlOUjFZcERmcXZOeHVhbDM3WQ\u0026q=https%3A%2F%2Ftwitter.com%2FChofter\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0ZTamJldHplV2NUTm50X3Q2OURoeUtGNzl0d3xBQ3Jtc0trb1VYQjBZaG1mdE5ONWN1Z0NsZWhrUWIyNG5vSnh6N1NpdjRaTVlaNnZHOHFPUEl3TkNsYkFBZUZlYWFRVlFPc1NCMnJYMlJ4eXBVNTZsRFVIV3FjdFM4emRtTU9kNWlOUjFZcERmcXZOeHVhbDM3WQ\u0026q=https%3A%2F%2Ftwitter.com%2FChofter\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: Chofter"}}},{"startIndex":931,"length":20,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbjlFMkhTeWg0ZXdONDdKZ1hoNkRnRGZWNWd2Z3xBQ3Jtc0tuNm00TjdSc1VKN3FacXZNOHVHMVgwOVdTcWgxTVQ0cjRxSXcxQ1BQZGx5cEVEV1pHVFZUdkJTZlFiRWFfZFplalRReHV1NkFPZ3RjTHAwdXY1b25GSklJajZpd21nN0E5UjhHRlZsQ0NuYjR3SkMwNA\u0026q=https%3A%2F%2Fchofter.com%2F\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbjlFMkhTeWg0ZXdONDdKZ1hoNkRnRGZWNWd2Z3xBQ3Jtc0tuNm00TjdSc1VKN3FacXZNOHVHMVgwOVdTcWgxTVQ0cjRxSXcxQ1BQZGx5cEVEV1pHVFZUdkJTZlFiRWFfZFplalRReHV1NkFPZ3RjTHAwdXY1b25GSklJajZpd21nN0E5UjhHRlZsQ0NuYjR3SkMwNA\u0026q=https%3A%2F%2Fchofter.com%2F\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":967,"length":16,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0F3cEZQeEhuZ3UwM0d6TUNjVU0zdTFoZ2VBZ3xBQ3Jtc0traFBGZk5DRjBFZ1hIVjFJalprZW00YUY3MHR5X1NEODFWM3VoWldMZWY3LUMxLURZb1M2UjdGNUVBX2pNV2llNDFXUUk2VGZjUnZqTHBwZlRxdDRzVzNaSXQyMjBJYXNNbTNZaTJrMzZGZHctUEozcw\u0026q=https%3A%2F%2Ftwitter.com%2Fsophiebits\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0F3cEZQeEhuZ3UwM0d6TUNjVU0zdTFoZ2VBZ3xBQ3Jtc0traFBGZk5DRjBFZ1hIVjFJalprZW00YUY3MHR5X1NEODFWM3VoWldMZWY3LUMxLURZb1M2UjdGNUVBX2pNV2llNDFXUUk2VGZjUnZqTHBwZlRxdDRzVzNaSXQyMjBJYXNNbTNZaTJrMzZGZHctUEozcw\u0026q=https%3A%2F%2Ftwitter.com%2Fsophiebits\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: sophiebits"}}},{"startIndex":988,"length":23,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbF9iOUJTbFI4SkFvUWJvRV9qTVloSVZlb1FrQXxBQ3Jtc0tuakc0N3cyY2RFQ01SYlZ5ZFlWU0djRHJNX1NPRERpTDN5MnVYSGF0cVVGVXJvWlYzUW0yTzZvOGZNcjBiRHFSMW5ZUll1bWFDMUpMZHJ1UE1GQmtpYnBENVRycUVwM3pWZU9NUWxxZFJ2anA4eW5oSQ\u0026q=https%3A%2F%2Fsophiebits.com%2F\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbF9iOUJTbFI4SkFvUWJvRV9qTVloSVZlb1FrQXxBQ3Jtc0tuakc0N3cyY2RFQ01SYlZ5ZFlWU0djRHJNX1NPRERpTDN5MnVYSGF0cVVGVXJvWlYzUW0yTzZvOGZNcjBiRHFSMW5ZUll1bWFDMUpMZHJ1UE1GQmtpYnBENVRycUVwM3pWZU9NUWxxZFJ2anA4eW5oSQ\u0026q=https%3A%2F%2Fsophiebits.com%2F\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":1025,"length":16,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbndPWHY1NHpxTVp2d2RxOGtxQ3EtN2FiaHc0QXxBQ3Jtc0ttY3ViZ0pKNUJYSVNKcHlqR3BSSDVjMk80RE9xMl9PNzk2YlVDSVVsZjJSOVZaYTdWNnJhdncxY1h3aTlnVFVWaE5iY1VnMXZoVDF6WHlKSWRGNmgzMk54T2ZjeGs5U1JLUDMza2hrajEzX2pEcHpkZw\u0026q=https%3A%2F%2Ftwitter.com%2Ftomocchino\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbndPWHY1NHpxTVp2d2RxOGtxQ3EtN2FiaHc0QXxBQ3Jtc0ttY3ViZ0pKNUJYSVNKcHlqR3BSSDVjMk80RE9xMl9PNzk2YlVDSVVsZjJSOVZaYTdWNnJhdncxY1h3aTlnVFVWaE5iY1VnMXZoVDF6WHlKSWRGNmgzMk54T2ZjeGs5U1JLUDMza2hrajEzX2pEcHpkZw\u0026q=https%3A%2F%2Ftwitter.com%2Ftomocchino\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: tomocchino"}}},{"startIndex":1057,"length":14,"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEM2rARgBIhMIkvyE95CIkgMVovdMAh02YwfYSI7XtbrVxLrI8gHKAQQZ7vmD","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbXhpYUU5dzdNM04zQjg2cnVkNlFhd1pQUEFPd3xBQ3Jtc0tuYzhhbl9NcTdWNnl6Z1R1M0dtSEZVVl9nYlpVelZpTndmOEV4OFBqcjFEeEZteV9PcER5dzl4dndtTjVFME1qTFc1cXFuMTViX3dJeTZBbnFIdWp2NG5Hcmg0RWlXT0tXOEpBV0NlUEp1Q2tSZnllVQ\u0026q=https%3A%2F%2Ftwitter.com%2FIamTonyC\u0026v=8pDqJVdNa44","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbXhpYUU5dzdNM04zQjg2cnVkNlFhd1pQUEFPd3xBQ3Jtc0tuYzhhbl9NcTdWNnl6Z1R1M0dtSEZVVl9nYlpVelZpTndmOEV4OFBqcjFEeEZteV9PcER5dzl4dndtTjVFME1qTFc1cXFuMTViX3dJeTZBbnFIdWp2NG5Hcmg0RWlXT0tXOEpBV0NlUEp1Q2tSZnllVQ\u0026q=https%3A%2F%2Ftwitter.com%2FIamTonyC\u0026v=8pDqJVdNa44","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"acces | 2026-01-13T08:48:42 |
https://golf.forem.com/privacy#c-information-collected-from-other-sources | Privacy Policy - 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 Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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:48:42 |
https://golf.forem.com/privacy#a-information-you-provide-to-us-directly | Privacy Policy - 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 Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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:48:42 |
https://golf.forem.com/privacy#6-international-data-transfers | Privacy Policy - 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 Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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:48:42 |
https://golf.forem.com/privacy#5-your-privacy-choices-and-rights | Privacy Policy - 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 Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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:48:42 |
https://dev.to/missamarakay/following-cooking-recipes-makes-you-a-clearer-writer-460a#jargon | Following Cooking Recipes Makes You a Clearer Writer - 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 Amara Graham Posted on Jul 17, 2019 Following Cooking Recipes Makes You a Clearer Writer # devrel # documentation I'm really into cooking, baking, pickling, really anything that will end in me eating something delicious. But I didn't find it enjoyable or "get good" at cooking overnight. My parents cooked most of our meals and if you planned on eating said meal, you were required to provide some amount of assistance, regardless of your blood relation to the family. After graduating out of dorm life I realized I needed to feed myself or starve, so I started getting bolder with my kitchen experiments and I'm pleased to say I'm still alive. "Ok Amara, but where is the tech components of this blog?" Hold on, I'm setting up the metaphor. "Ok fine." In the Kitchen If you stand in a kitchen and watch my dad cook - he reads a recipe, studies it, then goes through and pulls out all the things he needs to make it happen. For banana bread he usually has to pull the frozen bananas out early to thaw them enough to peel them, he portions out the spices so he can toss them in while mixing, he sprays the loaf pan before the mixture is together. If you watched me in my first apartment attempting banana bread for the first time, you would have seen someone who barely read the recipe (I've made this before, with supervision, and watched my dad make it for years, how hard can it be?) and did exactly every step of the instruction in series. Pull frozen bananas out of the freezer, immediately realize you can't peel a banana when its extra frozen, wait just long enough you can pry the peel off, smash the mostly still frozen bananas, slowly add each spice one at a time, measuring as you go, mix everything together, spray the pan, realize the oven isn't on, wait to pre-heat, blah blah blah, why did this take double the prep time? My dad has always taken the methodical approach to everything, he's a chemist and he loves math. I'm impatient and can't spend even 30 seconds idle when I know I need to complete a task, so I pretty much have the attention span of a Border Collie (have you seen those dogs stare at a ball, full body shaking with excitement?). At My Desk I'm sure you'll be shocked to hear when I sit down to learn some kind of new tech, I barely skim the tutorial or docs, immediately start the "doing", and often end up frustrated and annoyed with the experience. In some cases I tell myself things like "oh I've used an API like this before, I can just make it work" and 3 days later I'm banging my head on the keyboard. "Amara, just slow down and actually read the tutorial." Easier said than done. Not just for me personally, but for any dev, and that includes your dev coworkers, customers, community, etc. Time is precious, workplaces are more agile than ever, and people pay money for other people to stand in line for them. In My Brain Now recipes, just like tutorials, can be poorly written, but even the good ones can suffer from poor execution as I rambled on above. There are 5 things I learned from getting better at following cooking recipes that I think apply to written technical content. Ambiguous Terms Jargon Chunking Brevity Audience Let's take a look at each one. Ambiguous Terms Have you ever read a recipe, seen the word "mix" and go... with a spoon? A stand mixer? How long? Or how about "hand mix"? Did you know that a 'Hand Mixer' is an appliance and not the things at the end of your arms? Because a few years ago when we first started dating, my now husband did not. In tech, we love using the same term for a number of different things. Or we have a number of different words for the same thing. Really friendly to beginners right? Something like "Run this" might make sense to you, the engineer who built it, because its probably never crossed your mind that you run it globally and not in a particular directory (or vice versa) but that can be one of the most irritating things for a dev struggling with the worry of doing something wrong and/or irreversible. Be explicit in your use of terms and maybe consider a glossary of terms relevant to your project/product/industry/company. What does this mean in this context, right here, right now? Don't leave your reading punching out to search for answers. Jargon Every talk I've given on AI to beginners has included a disclaimer about not only ambiguous terminology but jargon. 'Fine-tuning' is not super intuitive, neither is 'hyperparameter'. 'Fold in' or 'soft peaks' in cooking is right up there too. Mastering the jargon can disrupt retention of fundamental topics. Explaining these terms early in docs and tutorials is crucial. You should not assume knowledge of jargon, so this is another +1 for a glossary. Chunking I am a huge fan of multi-part tutorials and how-to series, so long as they are done right. At the end of each part in a series, you should have a small complete something. Developers may not have time to sit down and do a 3-6 hour tutorial, but they should be able to get 20 minutes to an hour of uninterrupted time. You don't want to tackle a slow cooker recipe at 5pm expecting to eat it for dinner, but you may want to brown some meat so it is ready to toss in the next morning. If I have 20 minutes today to set myself up for success later today or tomorrow, I need to know I can get it done in the allocated time. And I need to feel like I can pick it up again without rereading the entire thing. Brevity Unlike this blog which is probably way too long for most of you, the more concise your written technical content the easier its going to be to follow. It's part of what makes the Tasty videos so appealing to watch - someone makes a sped up, top-down recipe that feels fast and easy even if its neither. This doesn't mean you can't write an introduction or a conclusion that goes more in depth about the content, but when you get to the meat of the docs or tutorial it should be a lean, mean, executing machine. Food bloggers are great at this, they may give you step-by-step pictures and commentary, but they almost always include the recipe separately. So feel free to tell me how you are going to save the world with this tutorial, but keep it out of the exact steps I'm following so I don't get overwhelmed. Audience This is maybe the most important, although I could argue that they all are. Knowing your developer audience is extremely important in technical writing. This helps you make decisions about what languages and references to use, what their workstation may look like, and maybe even things like their attention span. If your audience is students, whether they will admit it or not, they tend to have WAY more time to sit down and really study a tutorial. Or maybe they are participating in a hackathon and it just needs to work as fast as possible. But maybe your audience is enterprise developers, like mine often is. This means it has to be production-ready, maintainable, and even trainable across teams. Your maintenance team may be entirely separate from your product engineering team, so the content they follow may need to be different. Knowing or identifying your audience can be challenging, but this is a great opportunity for your devrel team to really shine. Celebrate Those Incremental Improvements Like I mentioned earlier, I didn't wake up one day and realize if I actually read the recipe, prepped ahead of time, and researched how to do certain kitchen techniques (again, ahead of time), I could maximize my time in the kitchen and feel less overwhelmed. In fact, I'm probably 50:50 in my ability to prep and run in parallel or haphazardly skim in series today. But snaps for me because this week I measured everything out before I started cooking! I'm sure you could make an argument that my dad is a 'senior' in the kitchen and I'm not (but I'm also not junior either), but he'd prefer you only use 'senior' when used in conjunction with "senior discount" at this point in his life. Let's say 'seasoned'. Whether you are a junior or senior dev, you still need the content you are consuming to prepare you for success. But with more and more folks using services like Blue Apron, Hello Fresh, Home Chef, arguably boxed Bootcamp experiences for the kitchen, we have a new generation of folks training themselves how to follow recipes and we can translate that experience into the tech world, allowing for more confident, empowered folks in the kitchen and at the keyboard. So instead of shouting "read the docs" or "follow the tutorial" make sure your content is as consumable and delicious as a home cooked meal. Top comments (5) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Author. Speaker. Time Lord. (Views are my own) Email codemouse92@outlook.com Location Time Vortex Pronouns he/him Work Author of "Dead Simple Python" (No Starch Press) Joined Jan 31, 2017 • Aug 5 '19 Dropdown menu Copy link Hide Excellent write up! I'm actually going to include this on the #beginners tag wiki for authors to read. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand JeffD JeffD JeffD Follow Code-quality 🩺 Teamwork 🐝 & everything that can simplify the developper's life 🗂️. Location France Joined Oct 16, 2017 • Sep 16 '19 Dropdown menu Copy link Hide This post is a must-read ! It's perfect 🏆 ("Hold on, I'm setting up the metaphor." 🤣) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Alvarez García Alvarez García Alvarez García Follow After more than 10 years backending, now trying to make this CSS properties work. Location Buenos Aires, Argentina Work FullStack Joined Apr 24, 2019 • Jul 25 '19 Dropdown menu Copy link Hide DevRel in construction here, thanks for this really simple and enjoyable post. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Amara Graham Amara Graham Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 • Jul 25 '19 Dropdown menu Copy link Hide Thank you! :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shashamura1 Shashamura1 Shashamura1 Follow Hi everyone my name is daniel.gentle loving caring I’am a type of person that always optimistic in every thing that I doing im very couriours and ambitious to lean I’m very new in this site Email ashogbondaniel292@gmail.com Location USA Education Technical college Work CEO at mylocallatest ...https://mylocallatest512644105.wordpress.com Joined Sep 12, 2022 • Oct 8 '22 Dropdown menu Copy link Hide Nice post I can use it to learn as project in dev.com ..to share the interest story of cooking Like comment: Like comment: 1 like 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 Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 More from Amara Graham Moving Config Docs From YAML to Markdown # documentation # yaml # markdown Moving DevEx from DevRel to Engineering # devrel # devex # engineering # reorg Bing Webmaster Tools De-indexed My Docs Site and Increased My Cognitive Load # webdev # seo # documentation 💎 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:48:42 |
https://golf.forem.com/privacy#main-content | Privacy Policy - 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 Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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:48:42 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.