# Retrospective Published articles for Retrospective. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## One Decade of Rustls: Evolution, Benchmarks, and Future Roadmap DevFeed: [One Decade of Rustls: Evolution, Benchmarks, and Future Roadmap]() Original publisher: [Read original article]() Author: Olimpiu Pop Published: 2026-09-12T07:07:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Cryptography](), [Security, Privacy and Abuse Prevention](), [interoperability](), [Refactoring]() Tags: [benchmarks](), [development](), [memory-leaks](), [memory-safety](), [news](), [open-source](), [performance](), [post-quantum](), [release](), [retrospective](), [rust](), [rustls-one-decade](), [security](), [tls]() ### AI overview Rustls marks its tenth anniversary with a retrospective on its growth, funding, security work, and performance. The article compares Rustls 0.23.37 with OpenSSL and BoringSSL and notes architectural changes planned for version 0.24. ### Source excerpt Rustls, a Rust TLS library, marks its decade-long progression from a grassroots project to a funded open-source initiative. Key contributions from organisations boosted development, resulting in features like post-quantum cryptography and robust performance. The upcoming 0.24 release aims to enhance architecture and flexibility, including new input buffering and improved session handling By Olimpiu Pop ## Adapting open source practices to an AI-first world: A retrospective on 2025 DevFeed: [Adapting open source practices to an AI-first world: A retrospective on 2025]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-08-03T18:30:00Z Content type: article Language: en Sources: [Google Open Source Blog]() Topics: [Open Source](), [Google](), [A2A protocol](), [interoperability](), [GitHub](), [linux foundation](), [Protocol (disambiguation)](), [LLVM](), [Rust](), [vllm](), [gRPC](), [Kubernetes]() Tags: [2025](), [a2a](), [a2a-protocol](), [agents](), [ai](), [ai-agents](), [github](), [google-open-source](), [interoperability](), [kubernetes](), [linux](), [linux-foundation](), [open-source](), [report-card](), [retrospective](), [rust](), [security](), [vllm]() ### AI overview Google reviews Alphabet's 2025 open source activity, including employee and external contributions, collaboration on the Agent2Agent protocol, and the maintenance and launch of public repositories and tools. ### Source excerpt by Sophia Vargas, Google Open Source Even as AI adoption accelerates and transforms the global technology landscape, open source remains foundational to how Alphabet builds, uses, and collaborates on products for billions of users. Our commitment to open source remains broad and consistent, including sharing our work year-over-year, and reflecting on what we've learned. In 2025: Roughly 10% of Alphabet's full-time workforce actively contributed to open source projects. This contribution ratio has remained steady over the past five years, scaling to match our growth. These open source contributions are not just solely focused on Google. Our top projects by unique contributors at Alphabet include community-led projects such as LLVM, vLLM, Envoy, and Rust, as well as Google-initiated projects like Kubernetes, Apache Beam, and gRPC. In addition, Alphabet projects received commits from more than 20,000 non-Alphabet affiliated user accounts. Working together on emerging standards Open source communities continue to provide vital collaborative spaces to define emerging standards, ensuring the interoperability and extensibility for the next generation of technologies. In 2025, we worked with more than 50 partners on the Agent2Agent (A2A) protocol to enable AI agents to communicate with each other, securely exchange information, and coordinate actions on top of various enterprise platforms and applications. Within weeks of our initial announcement, Google donated the A2A project to the Linux Foundation as part of our long-standing commitment to develop "open, collaborative ecosystem - offering greater autonomy and multiplying productivity." Launching tools with transparency Open source licenses provide a framework for anyone to explore, test, fork and expand on our technologies. Over the last 15 years, Google has created more than 15,000 public repositories on GitHub. Today, Google continues to maintain more than 5,000 public repositories on GitHub, and more than 1,500 publi ## Flock 2026 Afterburn: a retrospective DevFeed: [Flock 2026 Afterburn: a retrospective]() Original publisher: [Read original article]() Author: Ananya Nalavathu Published: 2026-07-28T08:00:00Z Content type: article Language: en Sources: [Fedora Magazine]() Topics: [Fedora](), [Matrix](), [Artificial Intelligence](), [Hardware](), [Arm](), [Amazon Web Services](), [Meta](), [Microsoft]() Tags: [2026](), [ai](), [arm](), [aws](), [azure](), [community](), [conference](), [contributors](), [czech-republic](), [design](), [engineering](), [enterprise](), [event](), [events](), [features](), [flock](), [flock-2026](), [infrastructure](), [linux](), [meta](), [post](), [retrospective]() ### AI overview A Fedora community intern recaps Flock 2026, a three-day contributor conference held in Prague. The article describes the event's planning, record sponsorship, four organizing themes, community-driven additions, and hybrid participation through Matrix. ### Source excerpt A Fedora community intern shares a firsthand look at Flock 2026 in Prague. The annual Fedora contributor conference broke sponsorship records and strengthened community bonds. Attendees praised the invaluable hallway conversations that unite the globally distributed project. Discover the behind-the-scenes planning, post-event survey results, and what makes this gathering feel like a family reunion for Fedora contributors. ## Zed Guild: What We Built, What We Learned DevFeed: [Zed Guild: What We Built, What We Learned]() Original publisher: [Read original article]() Author: Esther Trapadoux Published: 2026-06-16T00:00:00Z Content type: opinion Language: en Sources: [Zed Industries - Blog]() Topics: [Open Source](), [D](), [pull-requests]() Tags: [community](), [contributors](), [pull-requests](), [retrospective](), [rust]() ### AI overview Zed reflects on its first 12-week Guild cohort, a contributor program in which participants triaged issues, fixed bugs, and shipped features alongside the team. The cohort ended with 33 active contributors merging 148 pull requests, and feitreim received the grand prize. ### Source excerpt A retrospective on the Zed Guild - what we built with our community contributors, what we learned, and what comes next. ## Stytch & Latacora: A Security Partnership Retrospective DevFeed: [Stytch & Latacora: A Security Partnership Retrospective]() Original publisher: [Read original article]() Published: 2026-05-22T16:00:00Z Content type: article Language: en Sources: [Latacora]() Topics: [Security](), [Authentication](), [Incident response](), [SIEM, Security, Observability](), [supply chain attacks](), [MFA]() Tags: [2025](), [acquisition](), [authentication](), [incident-response](), [integration](), [partnership](), [retrospective](), [security](), [siem](), [supply-chain-attacks]() ### AI overview A retrospective on Stytch and Latacora's security partnership from 2021 through Stytch's acquisition by Twilio. It describes building security into passwordless authentication infrastructure, scaling detection and response, addressing SAML vulnerabilities and supply chain attacks, and maintaining monitoring during the acquisition. ### Source excerpt From growing startup to Twilio integration # Stytch and Latacora worked side by side to ensure that the developers and end users relying on Stytch's platform benefited from a security program built for the sensitivity and criticality of the data involved. This journey, which began in February 2021, saw Stytch grow from an ambitious startup building passwordless authentication infrastructure into a mature platform, ultimately acquired by Twilio. ## 10 Years of Wasm: A Retrospective DevFeed: [10 Years of Wasm: A Retrospective]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-01-22T00:00:00Z Content type: article Language: en Sources: [Bytecode Alliance]() Topics: [wasm](), [WebAssembly](), [Web](), [browser](), [JavaScript]() Tags: [browsers](), [javascript](), [retrospective](), [wasm](), [web](), [webassembly]() ### AI overview A retrospective on WebAssembly's origins, standardization, and adoption over its first ten years. It covers the project's 2015 beginnings, the W3C's 2019 recognition of Wasm as the "fourth language of the web," and its use in web applications, streaming video, game engines, embedded devices, and cloud serverless functions. ### Source excerpt In April of 2015, Luke Wagner made the first commits to a new repository called WebAssembly/design, adding a high-level design document for a "binary format to serve as a web compilation target." ## How to Make Team Retrospectives Effective DevFeed: [How to Make Team Retrospectives Effective]() Original publisher: [Read original article]() Author: Domenico Luciani Published: 2025-11-02T23:00:00Z Content type: opinion Language: en Sources: [Domenico Luciani]() Topics: [retrospectives]() Tags: [continuous](), [effective](), [retrospective](), [self-improvement](), [team](), [team-dynamics]() ### AI overview This opinion article explains how team retrospectives can support learning, self-improvement, idea sharing, celebration, and continuous improvement. It emphasizes psychological safety, focusing on processes rather than blaming people, and adapting the retrospective format to the team's situation. ### Source excerpt A team retrospective is not just another useless meeting, and if you feel so, it means you are doing it wrong, and this article is for you. ## My Graduate Career in Math DevFeed: [My Graduate Career in Math]() Original publisher: [Read original article]() Published: 2025-05-12T18:35:57Z Content type: opinion Language: en Sources: [Jeremy Kun]() Topics: [Mathematics](), [Computer science](), [graph theory]() Tags: [computer-science](), [education](), [essay](), [essays](), [game-theory](), [graph-theory](), [group-theory](), [linear-algebra](), [math](), [mathematics](), [retrospective](), [topology](), [university]() ### AI overview An autobiographical essay about the author's transition from computer science to mathematics at Cal Poly, including university coursework, study abroad in Budapest, and reflections on the intellectual environment and an early group theory project. ### Source excerpt Editor's note: This essay was originally published on Medium on 2016-03-05. I have made minor edits in this republishing and added a few small retrospective notes. 2010-2011 (Year 0) I had just switched my major at Cal Poly State University from computer science to math. I wanted to double major but California was in a budget crisis and a few weeks before I tried submitting my double-major request the Provost for the CSU system put a blanket ban on double majors. ## Decompiling 2024: A Year of Resurgence in Decompilation Research DevFeed: [Decompiling 2024: A Year of Resurgence in Decompilation Research]() Original publisher: [Read original article]() Published: 2025-01-29T00:00:00Z Content type: article Language: en Sources: [mahaloz.re]() Topics: [Programming](), [Software Engineering]() Tags: [graph](), [publications](), [research](), [retrospective]() ### AI overview A retrospective of decompilation research in 2024, covering academic and broader field progress. The article reports that 2024 produced an unusually high number of top-tier decompilation publications, including eight papers that represented nearly 30% of all such work. ### Source excerpt The year 2024 was a resurgent year for decompilation. Academic publications from that year made up nearly 30% of all top publications ever made in decompilation. In this post, I do a summarization and retrospective of both the academic and ideological progress of decompilation in 2024. Hint: decompilation research is back. ## How to run postmortems effectively? DevFeed: [How to run postmortems effectively?]() Original publisher: [Read original article]() Author: Peter Bergman Published: 2024-09-17T08:49:33Z Content type: tutorial Language: en Sources: [Volvo Cars Engineering - Medium]() Topics: [incident](), [systems](), [context]() Tags: [blameless-culture](), [errors](), [how-to](), [incident](), [mistakes](), [organization](), [outages](), [postmortem](), [postmortem-documentation](), [postmortem-report](), [processes](), [retrospective](), [retrospectives](), [software-development](), [systems](), [teams]() ### AI overview This article explains how to conduct effective, blameless postmortems after incidents such as outages, production bugs, or service disruptions. It emphasizes identifying root causes, examining systemic factors and context, and improving processes rather than assigning individual blame. ### Source excerpt Incidents are inevitable. As we all know, system outages, bugs in production, or service disruptions, can all have significant impacts. When that happens, the company pays the price. It's better to see it as a chance to learn instead of pointing fingers. This is where postmortems come into play. A postmortem, also referred to as an incident analysis, or retrospective, is a vital practice for understanding what went wrong, why it happened, and how to avoid such occurrences in the future. Understanding postmortemsWhat is a postmortem and why is it important? An incident postmortem is a review process carried out after an incident. Its purpose is to determine the root causes and identify strategies to avoid similar future incidents. What does blameless mean? In a blameless postmortem, the emphasis is on learning from mistakes and improving processes, rather than pointing fingers. By focusing on systems, components, roles, processes, procedures, and not individuals, we can foster a blameless culture where teams feel safe to openly discuss incidents and contribute to meaningful solutions. The aim here is to reframe the discussion to focus on the systemic factors that contributed to the incident which let teams uncover deeper insights and implement more effective solutions. What about the human factor? Even though many incidents can be attributed to being caused one way or the other by humans, due to the human factor, so to speak, it is important that we aim to shift the conversation towards understanding the "second stories" behind the incident. The "first story" of human error focuses on individual mistakes, while the "second story" examines the systemic factors contributing to errors. To do so, we focus on the underlying factors and context that may not be immediately apparent. Through the use of "second stories", human error is seen as the effect of systemic vulnerabilities deeper inside the organization. If we assume that all actions are made in good faith, then what ## An update on our Make Designs feature DevFeed: [An update on our Make Designs feature]() Original publisher: [Read original article]() Author: Noah Levin Published: 2024-07-17T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Artificial Intelligence](), [AI Models](), [User interface design](), [amazon](), [OpenAI](), [Simulation and Design]() Tags: [ai](), [ai-models](), [amazon](), [components](), [context-window](), [design](), [design-systems](), [desktop](), [diffusion](), [examples](), [feature](), [figma](), [mobile](), [model](), [models](), [openai](), [retrospective](), [ui](), [ui-design](), [update]() ### AI overview Figma explains why it temporarily rolled back Make Designs, a Figma AI feature that generated first-draft UI designs from prompts and design-system components. The rollback followed an issue in newly added design-system assets that caused some outputs to resemble existing applications. The article describes the feature's use of off-the-shelf models, design-system metadata, examples, prompts, and Amazon Titan's diffusion model, and outlines the review failure that led to the issue. ### Source excerpt After learning about an issue with Make Designs, part of Figma AI, we temporarily disabled the feature. Here's our retrospective. ## Migrating 500+ tests from Mocha to Node.js DevFeed: [Migrating 500+ tests from Mocha to Node.js]() Original publisher: [Read original article]() Author: Emanuele Stoppa; Bjorn Lu Published: 2024-03-25T00:00:00Z Content type: article Language: en Sources: [The Astro Blog]() Topics: [Node.js](), [migration](), [ci]() Tags: [astro](), [ci](), [cli](), [migration](), [node-js](), [performance](), [retrospective](), [testing]() ### AI overview Astro recounts migrating more than 500 test suites from Mocha to Node.js's built-in test runner, evaluating CI speed, configurability, and developer experience. ### Source excerpt A retrospective of how Astro migrated more than 500 test suites from Mocha to Node.js test runner. ## A Packwerk Retrospective DevFeed: [A Packwerk Retrospective]() Original publisher: [Read original article]() Author: Gannon McGibbon Published: 2024-02-07T21:40:35Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Rails](), [Dependency management](), [Ruby](), [Command-line interface](), [Code](), [Shopify]() Tags: [analysis](), [article](), [blog](), [command-line](), [dependencies](), [modular](), [retrospective](), [ruby](), [shopify](), [tool]() ### AI overview A retrospective on Packwerk, a Ruby gem released by Shopify in 2020 to enforce boundaries and modularize Rails applications. It describes Packwerk as a static analysis and dependency management tool that analyzes constant references, organizes code into packages, and identifies violations of declared dependency relationships. ### Source excerpt This article was originally posted on the Rails at Scale blog. In September, 2020, our team at Shopify released a Ruby gem named Packwerk, a tool to enforce boundaries and modularize Rails applications. Since its release, Packwerk has taken on a life of its own, inspiring blog posts, conference talks, and even an entire gem ecosystem. Its popularity is an indication that Packwerk clearly filled a void in the Rails community. ## Teleport's 2023 product retrospective highlights Device Trust, automatic agent updates, agentless access, and Teleport Team DevFeed: [Teleport's 2023 product retrospective highlights Device Trust, automatic agent updates, agentless access, and Teleport Team]() Original publisher: [Read original article]() Author: ben@goteleport.com (Ben Arent) Published: 2023-12-14T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Security](), [releases](), [Software as a service](), [Device Trust](), [Amazon Web Services](), [Amazon EC2](), [Amazon EKS](), [trust]() Tags: [aws](), [device-trust](), [ec2](), [kubernetes](), [releases](), [retrospective](), [saas](), [security]() ### AI overview Teleport's 2023 retrospective reviews releases and product highlights, including Device Trust, Windows host support, automatic agent updates, TLS routing, identity and security features, agentless access, and the Teleport Team SaaS offering. ### Source excerpt A quick retrospective and focus on a few highlights for 2023. ## Better learning from incidents: A guide to incident post-mortem documents DevFeed: [Better learning from incidents: A guide to incident post-mortem documents]() Original publisher: [Read original article]() Author: Luis Gonzalez Published: 2023-09-27T18:45:18Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Post Mortem](), [incident](), [Incident response]() Tags: [guide](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [learning](), [outage](), [post-mortem](), [report](), [retrospective](), [slack-incident]() ### AI overview This guide explains post-mortem documents as a way to capture information after an incident, understand contributing factors and risks, and plan actions to prevent or reduce the impact of similar incidents. It distinguishes documents from post-mortem meetings, discusses disagreement about when they are appropriate, and describes blameless post-mortems as an approach that avoids scapegoating. The article also notes alternative terms such as incident debrief documents, Incident Retrospectives, and After Action Reports. ### Source excerpt Post-mortem documents are a great way to facilitate learning after incidents are resolved. ## 2022.5 in Review DevFeed: [2022.5 in Review]() Original publisher: [Read original article]() Published: 2023-07-05T00:00:00Z Content type: article Language: en Sources: [Una Kravets]() Topics: [devrel](), [CSS](), [Web Development](), [Tooling](), [Gulp](), [Jekyll]() Tags: [jekyll](), [less](), [personal](), [podcast](), [retrospective](), [tooling](), [web](), [year-in-review]() ### AI overview A delayed retrospective on 2022 covering personal highlights, a new personal website, growth of the Web UI and Tooling DevRel team, and content production. It also discusses the CSS Podcast's third season, which focused on new and upcoming CSS APIs. ### Source excerpt Catching up on last year's year-in-review post ## 3 common pitfalls of post-mortems DevFeed: [3 common pitfalls of post-mortems]() Original publisher: [Read original article]() Author: Milly Leadley Published: 2022-07-27T00:00:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Post Mortem](), [incident](), [Template](), [Automation](), [Tooling]() Tags: [automation](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [post-mortem](), [retrospective](), [slack-incident](), [tooling]() ### AI overview The article explains common pitfalls that reduce the value of post-mortems. It recommends applying them selectively, reducing the manual effort required to compile incident information through tooling and automation, and reflecting at the right level to address underlying classes of problems rather than only individual fixes. It also emphasizes blameless analysis and provides a post-mortem template as inspiration. ### Source excerpt Reasons why a post-mortem might not deliver the value it deserves. ## Postmortem: Removing all users from github.com/trivago DevFeed: [Postmortem: Removing all users from github.com/trivago]() Original publisher: [Read original article]() Author: Andy Grunwald Follow Published: 2021-10-05T00:00:00Z Content type: opinion Language: en Sources: [Trivago]() Topics: [GitHub](), [incident](), [Post Mortem](), [Entra ID](), [pull-requests](), [ci](), [Deployment]() Tags: [azure](), [bugs](), [culture](), [engineering](), [engineering-culture](), [github](), [incident](), [mistakes](), [post-mortem](), [postmortem](), [processes](), [pull-requests](), [retrospective](), [slack](), [systems]() ### AI overview This blameless postmortem explains how trivago's automatic synchronization between GitHub and Azure Active Directory removed all synced user accounts from the company's GitHub organization. The root cause was deletion of the Azure Active Directory security group controlling access. The group was restored, users were reinvited, and the incident lasted 1 hour and 19 minutes. ### Source excerpt While engineering, we fix bugs, create new systems, build workflows and establish processes. Our job is to change things. Changing things can involve mistakes that ultimately lead to the failure... ## How the Figma PM team builds products and processes DevFeed: [How the Figma PM team builds products and processes]() Original publisher: [Read original article]() Author: Beez Africa Published: 2021-07-22T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Product Management]() Tags: [collaboration](), [figma](), [product-development](), [product-management](), [retrospective]() ### AI overview The article provides a behind-the-scenes look at how Figma's product management team brainstorms, develops, prioritizes, and reflects on products. It emphasizes transparency, trust, inclusion, and collaboration with cross-functional partners, including the use of FigJam for brainstorming and a "Buy a Feature" exercise for prioritization. ### Source excerpt A behind-the-scenes look at how the Figma PM team brainstorms, builds, and reflects, and what it means to open their process up to cross-functional partners along the way. ## Taking Control of One's Workaholic Tendencies - The IT Anonymous Edition DevFeed: [Taking Control of One's Workaholic Tendencies - The IT Anonymous Edition]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-04-20T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Agile](), [Requirements](), [Amazon Web Services](), [Slack](), [zoom]() Tags: [agile](), [aws](), [jira](), [messages](), [requirements](), [retrospective](), [services](), [startup](), [team](), [technology](), [work](), [zoom]() ### AI overview A personal, humorous account of workaholic behavior during an MVP delivery, including severe sleep deprivation, pressure from a manager, shifting Jira epics and requirements, and poorly timed meetings about AWS services and handoff. ### Source excerpt Please start by picturing a support group similar to Alcoholics Anonymous; Let's call it IT Anonymous: A dingy room in a church somewhere A coffee pot Cookies or donuts Chairs in a semi circle A place for people to stand and address the group We all know the drill - we've seen this scene a thousand times in movies or TV. And then you see me stand and address the group: Hi. I'm Scott. and the group responds with a chorus of: Hi Scott! and then begins the confession: "I ... have a problem. I need help!" and then: "Tell us more" I respond with: "I work in technology and I'm a workaholic. Last week I, the throes of getting an MVP out the door, with a boss that has been asking me daily Is It Done Yet? / Got Anything for me to See?, I got it done by all the Gods and Goddesses but I slept less than 8 hours out of the final 72 - I delivered. And yes I was late but by 2 days. But, at the end of our Weekly Agile Retrospective, I got to demo working code to our team. This occurred at 2:55 pm on Friday at which point I was close to falling over tired. And the reward for all this was to be scheduled into a 7 person Zoom meeting at 4:00 pm on a Friday to discuss AWS Services we use and AWS Key Handoff. This was NOT an important thing that had to be done after successfully completing my goals. And then, in a show of personal stupidity on my part, I noticed my boss was online Saturday night at midnight my time. And, in an effort to be a dutiful corporate solider, I, yes I'm a moron, asked him What epic should I start on on Monday morning?. My boss is three hours time offset from myself so this actually made some sense. And I had, per his direction created epics for all the outstanding tasks that I was aware of. I put them into Jira as I struggled mightily to get this MVP done. And, rather than being told to complete one of my existing Epics, a new Epic was named on the spot and a series of requirements were delivered to me via slack messages. And then there was the fateful question: ## Retrospective on Using Jumpstart Pro for a Rails Side Project DevFeed: [Retrospective on Using Jumpstart Pro for a Rails Side Project]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-01-21T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Template](), [Development]() Tags: [app](), [back-end](), [css](), [development](), [email](), [front-end](), [html](), [jumpstart](), [projects](), [rails](), [retrospective](), [side-project](), [tests]() ### AI overview The author reflects on choosing Jumpstart Pro, an application template for Rails projects, as a major development decision in 2019. They describe its prebuilt features, including Devise, Tailwind CSS, transactional email, HTML templates, and tested scaffolding, and recommend it for new projects. ### Source excerpt I don't generally do the retrospective (save in an agile context) - I prefer to look forward. And, yes, I'll admit that given some of the crap in my personal life these days, there's a reason for that. Now, that said, I've been thinking back over my 2019 year and I wanted to comment on my single best development decision of 2019: Buying Jumpstart Pro was my single best development decision in all of 2019. Like a lot of developers out there, I'm a back end guy. Yes I can do front end stuff but it tends towards a local maxima that might best be defined as ugly or even, perhaps, fugly. And, now, I can happily say never again. Jumpstart Pro is an application template for your next Rails app that gives you: A prebuilt starting point where the things that you are going to do anyway are already done like devise like a CSS grid (Tailwind) like transactional email like html templates that look good like a scaffolding generator that is all setup including tests like ... I bought Jumpstart Pro back in August when I had a side project that I was already pretty deep into and since Jumpstart Pro is best for new projects, well, I put it aside - and that was stupid of me. I should have trusted that Chris Oliver, the author of Jumpstart, made Jumpstart awesome - because he did. When I finally realized how good Jumpstart was, well, I started a different side project because I wanted to experience Rails from his perspective. And now that I'm about to ship this new side project, the only thing I have to say is absolutely worth it. Best damn development decision I made in 2019. Recommended. ## 2019 in Review DevFeed: [2019 in Review]() Original publisher: [Read original article]() Published: 2020-01-10T00:00:00Z Content type: opinion Language: en Sources: [Una Kravets]() Topics: [Development](), [Front end](), [Google](), [CSS](), [Material Design](), [W3C](), [color]() Tags: [color](), [css](), [developer](), [front-end-development](), [google](), [material-design](), [retrospective](), [w3c](), [year-in-review]() ### AI overview A personal retrospective covering 2019 travel, work, projects, content production, and professional contributions. The author discusses joining Google as a Developer Advocate for Material Design, producing podcasts and web series, publishing front-end development content, contributing to the W3C CSS Working Group, and launching CSS Houdini and Material-related projects. ### Source excerpt 2019 was a massive year for me. I like to reflect on the year and set some goals for the future. ## Year in review 2019 DevFeed: [Year in review 2019]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2020-01-09T00:00:00Z Content type: opinion Language: en Sources: [Jeroen Mols]() Topics: [Android](), [Job](), [GitHub]() Tags: [android](), [blogs](), [career](), [community](), [conferences](), [contributions](), [remote-work](), [retrospective](), [review](), [year-in-review]() ### AI overview A retrospective on 2019 covering career milestones, work at Philips Hue, a period of unemployment, subsequent roles at TransferWise and Plaid, Android community activities, remote work, and personal goals for 2020. ### Source excerpt Getting up without being rushed, cycling my kids to school, cooking healthy salads for lunch, kids running into my arms when they get home... I'm quite happy with my new daily routine! ## 2019 Retrospective DevFeed: [2019 Retrospective]() Original publisher: [Read original article]() Published: 2020-01-01T00:00:00Z Content type: opinion Language: en Sources: [Alex Korbonits]() Topics: [Learning](), [Natural language processing](), [Hugo](), [bert](), [math]() Tags: [bert](), [books](), [hugo](), [japan](), [learning](), [math](), [nlp](), [poetry](), [retrospective]() ### AI overview A personal retrospective on 2019 covering sailing, travel, reading, writing, language learning, fitness, organization, technology use, and relationships. The author reached a goal of reading 50 books, explored NLP papers including BERT, and attended fiction courses at Hugo House. ### Source excerpt Looking back on 2019 -- sailing, travel to Japan, books, and the best surprise of the year. [Next page]()