Developer Tools | Techlist.io

gitlabJan 14, 2026Original article

Introduction to GitLab Duo Agent Platform (opens in new tab)

GitLab Duo Agent Platform introduces an AI orchestration layer designed to move beyond simple code generation into full software development lifecycle (SDLC) automation. By utilizing specialized agents and asynchronous flows, the platform enables teams to delegate complex tasks like code reviews and pipeline fixes to AI "team members" who possess full context of the project. This transition from linear workflows to multi-agent collaboration allows developers to maintain oversight through detailed session logs while focusing on high-level innovation. ### Core Functionality and SDLC Context * The platform acts as an orchestration layer that enables asynchronous collaboration between human developers and specialized AI agents. * It utilizes deep SDLC context, pulling data from issues, epics, merge requests, CI/CD logs, wikis, and security scans to inform AI actions. * Automation is designed to understand and adhere to specific organizational standards, practices, and compliance requirements. ### Agent Interaction and Interface Methods * **GitLab Duo Agentic Chat:** Provides a real-time, synchronous interface via a persistent panel in both the GitLab Web UI and supported IDEs. * **Triggered Foundational Flows:** Users can invoke pre-built GitLab workflows, such as "Fix CI/CD Pipeline" or "Convert Jenkins to GitLab CI/CD," directly within the platform. * **Custom and External Flows:** Automated workflows can be triggered asynchronously by @mentioning agents or assigning reviewers in issue and merge request comments. * **External Agent Support:** The platform supports third-party models like Claude Code and OpenAI Codex, executing them on GitLab platform compute via runner execution. ### Distinguishing Agents from Flows * **Agents:** These are specialized assistants defined by unique system prompts and toolsets; they are best suited for interactive tasks and instant feedback within the chat interface. * **Flows:** These are autonomous, multi-step workflows designed for complex background tasks, such as multi-file refactoring or event-driven automation. * **Execution Environment:** While agents are interactive, flows run asynchronously on platform compute, triggered by specific GitLab events or user assignments. ### Platform Management and Transparency * **AI Catalog:** A centralized library for discovering, creating, and sharing custom agents and flows across an entire organization. * **Automate Hub:** A management center used to configure triggers, monitor active flows, and manage agent permissions. * *Sessions:** Every interaction creates a session log that provides a transparent "decision trail," including agent reasoning, tool calls, and pipeline execution status. * **Model Selection:** Starting with GitLab 18.4, users can select specific foundational models for their conversations within the Web UI to better suit the task at hand. Teams looking to implement the GitLab Duo Agent Platform should begin by utilizing foundational flows for common tasks like pipeline debugging before moving toward custom agent creation. Reviewing the transparency logs in the "Sessions" view is highly recommended to refine agent prompts and ensure that automated actions align with internal development standards.

Developer Tools Gitlab Duo Agent Platform Event Driven Automation Gitlab Ci Cd+4

metaDec 22, 2025Original article

Python Typing Survey 2025: Code Quality and Flexibility As Top Reasons for Typing Adoption (opens in new tab)

The 2025 Typed Python Survey highlights that type hinting has transitioned from an optional feature to a core development standard, with 86% of respondents reporting frequent usage. While mid-career developers show the highest enthusiasm for typing, the ecosystem faces ongoing friction from tooling fragmentation and the complexity of advanced type logic. Overall, the community is pushing for a more robust system that mirrors the expressive power of TypeScript while maintaining Python’s hallmark flexibility. ## Respondent Demographics and Adoption Trends * The survey analyzed responses from 1,241 developers, the majority of whom are highly experienced, with nearly half reporting over a decade of Python expertise. * Adoption is highest among developers with 5–10 years of experience (93%), whereas junior developers (83%) and those with over 10 years of experience (80%) show slightly lower usage rates. * The lower adoption among seniors is attributed to the management of legacy codebases and long-standing habits formed before type hints were introduced to the language. ## Primary Drivers for Typing Adoption * **Incremental Integration:** Developers value the "gradual typing" approach, which allows them to add types to existing projects at their own pace without breaking the codebase. * **Improved Tooling and IDE Support:** Typing significantly enhances developer experience by enabling more accurate autocomplete, jump-to-definition, and inline documentation in IDEs. * **Bug Prevention and Readability:** Type hints act as living documentation that helps catch subtle bugs during refactoring and makes complex codebases easier for teams to reason about. * **Library Compatibility:** Features like Protocols and Generics are highly appreciated, particularly for their synergy with modern libraries like Pydantic and FastAPI that utilize type annotations at runtime. ## Technical Pain Points and Ecosystem Friction * **Third-Party Integration:** A major hurdle is the inconsistent quality or total absence of type stubs in massive libraries like NumPy, Pandas, and Django. * **Tooling Fragmentation:** Developers expressed frustration over inconsistencies between major type checkers like Mypy and Pyright, as well as the slow performance of Mypy in large projects. * **Conceptual Complexity:** Advanced features such as variance (co/contravariance), decorators, and complex nested Generics remain difficult for many developers to implement correctly. * **Runtime Limitations:** Because Python does not enforce types at the interpreter level, some developers find it difficult to justify the verbosity of typing when it offers no native runtime guarantees. ## Most Requested Type System Enhancements * **TypeScript Parity:** There is a strong demand for features found in TypeScript, specifically Intersection types (using the `&` operator), Mapped types, and Conditional types. * **Utility Types:** Developers are looking for built-in utilities like `Pick`, `Omit`, and `keyof` to handle dictionary shapes more effectively. * **Improved Structural Typing:** While `TypedDict` exists, respondents want more flexible, anonymous structural typing to handle complex data structures without excessive boilerplate. * **Performance and Enforcement:** There is a recurring request for an official, high-performance built-in type checker and optional runtime enforcement to bridge the gap between static analysis and execution. As the Python type system continues to mature, developers should prioritize incremental adoption in shared libraries and internal APIs to maximize the benefits of static analysis. While waiting for more advanced features like intersection types, focusing on tooling consistency—such as aligning team standards around a specific type checker—can mitigate much of the friction identified in the 2025 survey.

Developer Tools Python Static Typing Type Hints+4

figmaJun 11, 20242 min readCurated summary

The Long and Short of It: Issue no.5 | Figma Blog

Issue no. 5 of Figma’s newsletter, “Come together,” argues that progress depends on community, collaboration, and shared inspiration. Ahead of Config, it highlights creators and leaders whose work shows how connection—whether in person or online—helps turn ideas into reality. The issue spans product development, design quality, creative experimentation, AI, and community events. ## Building tools that feel magical - Charmaine Lee, product manager for Snap’s Lens Studio, shares principles for creating developer tools that delight creators. - Her approach emphasizes hands-on involvement, collaboration, and understanding the creator’s experience rather than following rigid product-building rules. - The feature presents creator-focused product development as an “all-hands-on-deck” effort. ## Craft, beauty, and product quality - Leaders from Stripe, Linear, and Figma discuss how to define and measure craft and beauty in digital products. - Katie Dill, Karri Saarinen, and Yukhi Yamashita explore the relationship between form and function. - Their central argument is that thoughtful design is not merely cosmetic: quality and beauty can contribute directly to product adoption and business growth. ## Designing quilts in Figma - Former product designer Nicole Boettcher uses Figma to plan and design handmade quilts. - Her process demonstrates how digital design tools can support physical, artistic work beyond conventional interface design. - The project playfully extends the idea of “moving rectangles,” connecting her former profession with her current craft. ## AI and creative tools - David Hoang, formerly of Replit, discusses how AI is changing creative tools, product design, and development workflows. - He recommends responding to rapid change through shared learning and strong communities. - Cohorts that combine accountability with fun can help people stay motivated as they develop new skills. ## Config and community opportunities - In-person Config tickets are sold out, but virtual attendance and local watch parties remain available. - Readers can follow the live blog for speaker highlights and event coverage. - The issue also promotes illustrator Thomas Colligan’s artwork, new Config merchandise, and the upcoming Figma Store release. Figma’s overall recommendation is to stay connected: creative progress is strengthened by mentors, collaborators, peers, and communities that make learning and experimentation possible.

Read original

Developer Tools Figma AI Product Design+3

figmaJun 6, 20242 min readCurated summary

Charmaine Lee’s 10 Rules for Building Developer Tools | Figma Blog

Developer tools feel “magical” not because of polished interfaces, but because they help users quickly become confident creators. Charmaine Lee argues that teams should optimize what happens after the initial “aha moment,” shorten the path to meaningful creation, and build products through close, authentic engagement with developers. ## Prioritize lasting adoption over onboarding - The first-time user experience (FTUE) should not be overloaded with every product capability. - The real measure of success is whether users understand and continue using the product after the initial discovery moment. - Lens Studio 5.0’s public beta omitted a formal FTUE, testing whether the product was intuitive enough to use independently. ## Shorten the path to “magic” - Teams should identify how long it takes users to move from downloading a tool to creating and sharing something valuable. - Lens Studio’s team mapped a 19-step journey from visiting the website to submitting a first project. - By removing unnecessary steps and avoiding guidance for actions users already understood, they reduced the experience to four key moments. - User-journey mapping and testing help reveal which steps create delight, friction, or confusion. ## Meet developers in their communities - Product managers should engage directly with developers at meetups, conferences, hackathons, livestreams, and online communities. - Charmaine monitors AR discussions and attends events to learn developers’ language and gather candid feedback. - Building long-term context from these conversations enables better product decisions and more informed responses to user needs. ## Replace traditional marketing with DevRel - Developers tend to respond poorly to conventional marketing and prefer authentic communication. - Effective developer relations includes: - Real experiences and detailed product-building stories - Transparency about mistakes and limitations - A balance between accessible explanations and technical depth - DevRel should be a company-wide responsibility, not limited to a specialized team. - When employees advocate for both the product and its users, they can foster a more loyal developer community. The excerpt’s central recommendation is to design for users’ sustained progress, not merely their first impression: remove unnecessary friction, understand developers firsthand, and communicate with them honestly.

Read original

Developer Tools User Experience Augmented Reality Unity+3

figmaSep 21, 20232 min readCurated summary

What Codegen Is (Actually) Good For | Figma | Figma Blog

Code generation is most useful as an augmentation to the design-to-development process, not as a replacement for developers. Figma found that fully automated design-to-code output often fails because teams use different frameworks, codebases, and patterns. Instead, codegen works best when it provides context, suggestions, and a useful starting point that developers can refine themselves. ## Codegen’s Broad Ecosystem - Codegen automatically produces code from rules or specifications. - It ranges from: - IDE completion tools such as Microsoft IntelliSense - Reusable templates and snippets - Visual programming and no-code platforms such as Bubble - AI assistants such as GitHub Copilot and Replit Ghostwriter - AI codegen adoption is high: 82% of developers surveyed by Stack Overflow in 2023 said they already write code with AI tools. - Trust remains low, however; fewer than 3% reported highly trusting the accuracy of these tools. ## Why Fully Automated Design-to-Code Falls Short - Figma initially envisioned Dev Mode as a way to automate design-to-code conversion. - Early results were promising, but developers often found the generated code impractical or not useful. - Producing code that fits a wide range of frameworks, architectures, and team conventions is difficult. - The better goal is “intelligence amplification”: technology should extend a developer’s capabilities while keeping the developer in control. ## From 0 to 0.5 - Codegen is particularly effective at helping developers move from a blank screen to a partial implementation. - In products with established design systems and component libraries, it can: - Suggest the appropriate component - Surface component names and property values - Reduce guesswork during design handoff - Rather than generating a complete solution, codegen helps developers reach a useful starting point faster. ## Applying Codegen to Existing Design Systems - Codegen delivers the most value when customized for a specific team, company, and workflow. - If a design system and component library already exist in Figma, teams may not need a separate automated design-to-code application. - More useful alternatives include: - Referencing design tokens and variables - Viewing component documentation - Building a Figma codegen plugin - Generating custom code snippets - These tools help developers understand a design quickly while allowing them to write code that matches their own codebase. The practical recommendation is to use codegen as a guided assistant: provide suggestions, reusable patterns, and context, but leave architectural decisions and final implementation to developers.

Read original

Developer Tools Figma Design Systems Design To Code+4

figmaApr 28, 20202 min readCurated summary

Bridge design and development with the new Zeplin integration | Figma Blog

Figma and Zeplin introduced a redesigned native plugin to improve design-to-development handoff. The integration lets teams export Figma frames, components, colors, and text styles directly to Zeplin, where developers can generate specs, assets, and code snippets. Rebuilt for better performance and maintainability, it addresses issues with large files and high-resolution exports while opening the door to automatic component updates. ## A Growing Design-to-Development Workflow - Zeplin provides advanced handoff features and acts as a bridge between designers and developers. - The original Figma integration launched before Figma officially launched. - More than 300,000 Figma files were exported to Zeplin each month, with usage increasing by 30–40% during the shift to remote work. ## Rebuilt as a Native Plugin - The second-generation integration was rebuilt from the ground up as a native Figma plugin. - This creates a more seamless export experience for users. - It also makes the integration easier for Zeplin to maintain and extend with new features. - Performance problems affecting large Figma files, frames, and export resolutions were addressed. ## Exporting Designs and Generating Handoff Materials - Users can export: - Frames - Components - Color styles - Text styles - In Zeplin, product teams can automatically generate: - Accurate design specifications - Assets - Code snippets - Exported assets can also appear directly in Zeplin style guides. ## Future Possibilities - Figma’s web-based architecture offers advantages over integrations with other design tools. - Zeplin was exploring automatic synchronization, allowing changes to Figma components to be pushed to Zeplin without manual exports. - Users could install the plugin through the Figma Community, and Figma customers were offered three free months of Zeplin’s Organization plan. The new plugin is recommended for teams seeking a faster, more reliable handoff between Figma and development, especially when working with large files or shared design systems.

Read original

Developer Tools Figma Zeplin Design Handoff+2

figmaMay 3, 20172 min readCurated summary

New faces at the Figma helm | Figma Blog

Figma is entering a new phase as demand for design and collaborative tools grows across the technology industry. To support that growth, CEO Dylan Field announces Eric Wittman as the company’s first COO and Kris Rasmussen as Vice President of Engineering. Their experience scaling collaboration-focused businesses will help Figma expand its operations, revenue, technology, and team. ## Figma’s Growth Opportunity - Companies increasingly view design as central to creating products customers value. - Large organizations such as IBM and GE are expanding their design teams, while Facebook has pursued a high designer-to-engineer ratio. - Figma argues that the tools available to designers have not kept pace with this demand. - Improving collaboration remains the company’s guiding priority. ## Eric Wittman: Operations, Strategy, and Revenue - Wittman joins after leading Atlassian’s Developer Tools business, including Bitbucket. - As COO, he will focus on: - Recruiting and finance processes - Go-to-market strategy - Revenue and business operations - Company strategy and values - His career spans: - Customer support and product management at Macromedia, where he eventually led Flash product management - CEO of music player company Songbird - General manager of Developer Tools at Atlassian - Figma highlights his unusual combination of operational expertise and strong product enthusiasm. - Before the announcement, he had already helped Figma launch its pricing model and refine its strategic direction. ## Kris Rasmussen: Engineering Leadership - Rasmussen initially joined Figma as a part-time contractor but quickly became an influential, informal leader. - He is appointed Vice President of Engineering and will oversee major engineering initiatives and technical-team development. - His background includes: - Leading engineering at Asana during its early growth - Scaling engineering at Aptana, a web-application developer-tools company - Building personal projects involving 3D graphics - Figma values his ability to resolve disagreements, identify necessary actions, and combine technical skill with leadership. - His primary mission will be building a world-class engineering organization and infrastructure for collaborative design tools. ## Continued Hiring - Figma says it is still early in its development and expects significant opportunities and challenges ahead. - The company invites engineers, designers, writers, and product managers who are passionate about design to apply for open roles. Figma’s leadership changes are intended to turn growing demand for collaborative design software into scalable business and technical execution. Wittman will strengthen operations and commercial strategy, while Rasmussen will lead the engineering organization needed for Figma’s next stage.

Read original

Developer Tools Figma Design Collaboration Saas+2