Click any tag below to further narrow down your results
Links
This article outlines effective techniques for selling to engineers. It emphasizes understanding their technical mindset and providing clear, data-driven solutions. Practical tips include focusing on problem-solving and avoiding jargon.
Joel shares his journey from junior to staff engineer at GitHub, outlining what the staff role entails and how it differs from senior engineering. He discusses the challenges and opportunities that come with this position and offers insights on thriving in it.
The article details how ChatGPT's memory system functions, highlighting its four layers: session metadata, user memory, recent conversation summaries, and current session messages. It explains how these components work together to create a personalized experience without the complexity of traditional retrieval systems.
This article discusses advancements in supersonic flight technology, focusing on Boom Supersonic's Overture aircraft and its new "Boomless Cruise" feature. It also highlights the engineering behind the high-pressure turbine disk made from Inconel 718, essential for jet engine performance.
This article explores how commercial decisions can create technical debt that hinders long-term scalability. It highlights patterns that lead to architectural fragility and offers strategies for engineering leaders to align revenue goals with technology strategy.
The article explores the future of the "10x engineer" and how generative AI might impact engineering productivity. It argues that while top engineers could become even more productive, the gap between high-performing engineers may not widen as much as expected. Key skills for engineers will likely shift, emphasizing stamina and work ethic.
This article discusses how Netflix adopted Temporal, a durable execution platform, to enhance the reliability of its cloud operations. By transitioning from a complex orchestration system that led to deployment failures, Netflix reduced its transient failure rate from 4% to 0.0001%. The piece highlights the integration process and lessons learned during this migration.
In 2025, Patreon focused on maintaining features for its millions of users while overhauling its infrastructure. Their Year in Review highlights 12 projects that emphasize architectural changes, data model refactoring, and consistency trade-offs in distributed systems. Key strategies included defensive migrations, decoupling data relationships, and improving analytics through a new transformation layer.
The article argues that while bash is useful for simple CI tasks, it falls short as project complexity grows. For larger teams and intricate pipelines, a dedicated orchestrator is necessary to manage the requirements effectively.
The article discusses Robinhood's SERA platform, which allows engineers to approve requests securely from any device without needing a VPN. This solution improves the speed of access approvals while maintaining strong security standards, enhancing overall engineering efficiency.
Marina Miller shares insights from her time at Palantir, focusing on the importance of engineering partnerships in product development. She emphasizes accountability, fieldwork, and the need for alignment between product and engineering teams to create effective solutions.
The author reflects on their experience during the recent Cloudflare outage, highlighting how system limits and complex failures can lead to unexpected problems. They emphasize the importance of understanding the context behind decisions made during incidents and the value of detailed incident writeups for learning.
The article contrasts two engineering paths: one focused on high-visibility projects and quick pivots, and another grounded in long-term stewardship of developer tools. The author emphasizes the value of context and trust in infrastructure roles, arguing that prioritizing systemic innovation over short-term gains leads to greater impact.
The article discusses recent trends in the data engineering market, suggesting that consolidation is happening due to its limited size. It raises questions about the sustainability and growth potential of the industry.
Agent Composer is a new tool that allows teams to create custom AI agents, significantly reducing the time needed for complex engineering tasks. It integrates multi-tool coordination and multi-step reasoning to automate workflows, freeing engineers to focus on high-value work.
Pinterest's Observability team is developing an AI-driven system to improve how engineers analyze and resolve issues. They are using the Model Context Protocol to unify disparate observability data, allowing AI agents to provide actionable insights and streamline the troubleshooting process. This approach aims to reduce the time engineers spend navigating tools while enhancing the overall efficiency of observability practices.
This article explores the benefits and challenges of being on-call as a software engineer. It discusses how the experience can enhance skills like stress management, leadership, and system knowledge, while also highlighting potential health risks and lifestyle constraints.
Duolingo explains how it integrated financial awareness into engineering workflows, enabling developers to assess the cost impact of their decisions in real-time. This cultural shift involved collaboration across teams and the use of specific metrics to prioritize cost efficiency alongside technical performance.
This article outlines the role of machine learning engineers, detailing their responsibilities in transitioning ML models from research to production. It covers essential skills, methodologies, and career paths in the field, emphasizing the importance of collaboration between data science and engineering.
This article explores "Engineering-as-Marketing," a strategy where startups create free tools or resources that provide value to users while subtly promoting their products. It highlights successful examples, like HubSpot and Shopify, showing how useful tools can attract leads and build trust over time.
This article critiques the trend of using obscure and whimsical names for software tools, arguing that they hinder understanding and efficiency. It references Richard Stallman's emphasis on memorable names and compares naming conventions in software to those in other engineering fields. The author calls for a cultural shift towards clearer, more descriptive naming practices in programming.
The article argues against the common use of "tradeoffs" in architectural discussions, suggesting that this term oversimplifies decision-making by failing to capture the impact of individual pros and cons. It emphasizes the importance of focusing on upgrading problems rather than merely listing negatives and positives. The author shares insights from their experience at Netflix, where shifting to global personalization models presented better challenges than regional ones.
The article discusses the challenges faced by Fontana Dam due to alkali-silica reaction (ASR) in its concrete, which caused unexpected expansion and cracking. Engineers at the Tennessee Valley Authority decided to create a relief slot within the dam to accommodate this growth, a proactive solution to a persistent problem.
This article clarifies the key differences between prototypes and final products, highlighting common misconceptions among product creators, especially those without engineering backgrounds. It discusses the complexities involved in developing commercial-quality products and the limitations of current prototyping tools.
This article promotes a webinar focused on improving collaboration between product and engineering teams. It features a panel of experienced speakers discussing how shared visibility can lead to quicker decision-making and better project outcomes.
The article discusses the rise of growth engineers, who blend marketing and technical skills to build and maintain growth systems independently. As software development costs drop, these professionals will increasingly take on roles traditionally held by engineers, enabling faster experimentation and innovation. Canva's success in programmatic SEO exemplifies this new approach.
This article discusses the challenges and strategies involved in deprecating obsolete software systems. It emphasizes the importance of planning for deprecation from the start and the costs associated with maintaining outdated systems. The piece also touches on emotional resistance to deprecation and the need for careful management of the process.
This article advises early-stage founders to avoid managing their engineering teams directly. Instead, it emphasizes focusing on hiring motivated engineers and building a strong product, highlighting common management pitfalls and when to consider adding structure.
Nubank faced challenges with its external logging vendor as it scaled, leading to high costs and limited control. The engineering team built an in-house logging platform in two phases, focusing on ingestion and storage, to enhance reliability, scalability, and cost efficiency.
This article discusses how AI coding tools struggle with legacy code due to missing context and institutional knowledge. It highlights the productivity challenges faced by engineers when using AI on outdated systems compared to new projects. The piece also outlines strategies for improving AI effectiveness through better documentation and restructuring.
The article details the author's journey of manufacturing their first hardware product, a high-lumen lamp, after a successful crowdfunding campaign. It highlights the challenges faced during production, including unexpected technical issues and geopolitical factors, along with key lessons learned in planning, communication, and testing.
This article discusses how Coinbase uses AI to enhance their engineering processes, allowing teams to manage production operations effectively. It highlights the benefits of AI in identifying issues, optimizing costs, and improving shipping speed while maintaining system resilience.
This article discusses how advancements in AI are shifting engineering roles. Traditional skills that defined senior engineers are now expected from all levels, as AI takes over implementation tasks. The focus is on maintaining context, effective planning, and enhancing code review practices.
The article discusses how advancements in AI tools have lowered the barrier to software creation, leading to a rise in personal, disposable software that addresses specific problems. While code generation has become cheap, the challenges of maintaining software remain high, emphasizing the ongoing need for skilled engineers to manage complexity.
The article discusses the concept of "Wolves," or high-performing engineers, and how managers should approach them. Instead of trying to direct their efforts, managers should create environments that allow these engineers to thrive while stepping back to avoid interference. It emphasizes understanding when to let talented individuals work independently for the benefit of the organization.
The article analyzes 1,000 job postings for forward deployed engineers, revealing three distinct roles within this title. It highlights the significant demand growth, salary averages, required skills, and common responsibilities, particularly emphasizing that these positions are primarily engineering-focused rather than sales-oriented.
The article critiques common shortcomings in post-mortem reviews, emphasizing that many recommended actions are merely aspirational and fail to address systemic issues. It advocates for concrete changes to the system that prevent recurring problems, rather than relying on team members to simply "try harder."
This article details how Atlassian revamped its engineering processes to enhance developer productivity and streamline workflows using AI. It discusses the challenges faced and the steps taken to create a cohesive work system that benefits teams throughout the software development lifecycle.
The article discusses how Mercadona Tech improved their software release process by implementing FeatureOps. Before using Unleash, their releases were infrequent and stressful. Now, they can deploy over 100 times a day, allowing for quicker feedback and more confident experimentation.
This article discusses how engineers can set effective goals using the SMART framework and tiny experiments. It highlights the challenges of maintaining motivation amidst work chaos and offers insights on overcoming goal-setting failures.
Srihari Sriraman shares his experience in refining prompts for language models, shifting from complex 300-word inputs to effective 15-word versions. He emphasizes understanding the strengths and limitations of LLMs, particularly in tasks like segmentation and categorization.
This article discusses the importance of choosing the right AI tools for specific problems, cautioning against over-engineering. It emphasizes that while AI can enhance development, simpler solutions may be more effective in certain situations.
This article discusses the role of forward deployed engineers (FDEs) in software and AI companies, highlighting the difference between effective and ineffective deployment. It emphasizes the importance of leveraging FDEs to improve products rather than merely filling gaps that should be addressed with code.
This article discusses how AI will reshape engineering by enhancing prototype development, improving documentation quality, and increasing compliance focus. It emphasizes the need for strong data practices as engineers leverage AI to streamline workflows and tackle complex challenges more efficiently.
This article argues that effective software design requires a deep understanding of the specific codebase, which generic design advice often lacks. It highlights the importance of concrete discussions among engineers familiar with the system, while acknowledging that generic principles can still guide new projects or help in decision-making. The author critiques the role of software architects who provide high-level designs without real accountability for implementation.
The article discusses the misconceptions around operations (ops) in software development, arguing that ops is essential for efficient systems and shouldn’t be viewed negatively. It emphasizes the need for a clear distinction between development and operations roles, highlighting how both are vital for successful engineering outcomes.
This article explains how AI coding agents are transforming the software development lifecycle. It covers their capabilities in planning, design, and building phases, emphasizing the shift in engineers' roles from routine tasks to complex problem-solving. It also provides actionable steps for teams to adopt AI tools effectively.
This article details how Yelp developed its AI assistant to provide direct answers from business pages, overcoming challenges in data retrieval and generation. It explains the architectural decisions made to ensure accuracy and speed, including strategies for handling data freshness and content separation.
The article discusses why large software systems are often poorly understood, even by their creators. It highlights the challenges of documenting complex features and the reliance on engineers' tacit knowledge to answer basic questions about the software's functionality. As software evolves, keeping track of these details becomes increasingly difficult.
This article discusses the shift from valuing high-output engineers to recognizing the importance of those who focus on code quality and structure. With the rise of coding assistants, effective code management is becoming more challenging, leading to a demand for engineers who can curate and organize code thoughtfully. The author predicts that the future will celebrate these meticulous 0.1x engineers.
Ably outlines its transformation into an AI-first company, emphasizing internal adoption and practical integration of AI across teams. The article details their three pillars for success, the implementation of the Model Context Protocol (MCP), and the tools selected to enhance productivity and collaboration.
The article explores the concept of the "reverse ivory tower" in software engineering, where decision-making occurs in a detached environment, leading to systems that prioritize internal coherence over user needs. It follows a new product engineer, Cassandra, as she navigates a complex platform and its bureaucratic processes, highlighting the disconnect between developers and real-world applications.
This article outlines how the Sora Android app was developed in just 28 days using Codex. It discusses the challenges and advantages of integrating Codex into the engineering workflow, emphasizing the importance of clear guidance and context for effective collaboration.
This article discusses a practical approach to handling engineering crises by balancing tactical wins with strategic investments. It emphasizes the importance of transparency with stakeholders about prioritization and tradeoffs to build trust and maintain alignment.
This article introduces a tool that enhances incident response by integrating AI across various tech stacks. It offers features like incident investigation and debugging, allowing engineers to maintain focus on product development without overhauling their existing systems.
Daniel Lemire argues that scientific progress relies heavily on the tools we create and the methods we use. He critiques the bureaucratic nature of current research, advocating for a more agile and experimental approach to foster innovation. The article emphasizes the need for balance between speed and careful, deliberate exploration in scientific endeavors.
This article discusses how Planview helps engineering and product leaders overcome challenges like scattered data and fragmented workflows. It highlights features that improve delivery predictability, align roadmaps to strategy, and provide real-time visibility into risks and bottlenecks.
The article explores how Notion embedded AI engineer Theo Bleier into its sales team to identify and address workflow challenges. By understanding the sales process firsthand, Bleier developed targeted AI tools that improved efficiency and success rates in outreach efforts.
The Octopus Platform Hub streamlines software delivery for platform teams by providing reusable templates, governance policies, and centralized management. It aims to reduce duplication of effort and standardize deployment practices while maintaining developer autonomy. This tool is geared towards Enterprise tier customers looking to enhance their platform engineering processes.
The article discusses how 37signals achieves cleaner code through a focused engineering strategy that emphasizes small teams, strict scope management, and hiring top talent. Most companies struggle to adopt this approach due to their mindset that more features equal more revenue. Ultimately, 37signals' success lies in their commitment to quality over quantity.
The article discusses how AI is reshaping software development by enabling the creation of small, personalized applications instead of large, complex ones. This shift allows for simpler coding practices, reducing costs and improving user experience. It highlights the potential for "vibe coding," where AI handles most coding tasks based on user input.
The article explores how poor communication and information filtering in organizational hierarchies lead to employee dissatisfaction and resignations. It emphasizes that engineers often leave not for better pay, but because their expertise is ignored and their concerns go unaddressed. A direct connection between executives and engineers can uncover issues before they escalate into crises.
The article outlines practical strategies for adopting AI tools at Imprint, focusing on understanding and removing barriers to usage. It emphasizes the importance of documenting prompts, sharing tips, and ensuring leadership support to foster a culture of AI integration across all teams.
This article details how Hightouch created its Agents product, a marketing tool that automates complex tasks using AI. It explores the engineering challenges the team faced and how they tackled issues like context management and dynamic planning to improve agent performance.
This article introduces SWE-Universe, a framework designed to automatically create verifiable software engineering environments from GitHub pull requests. It addresses issues like low production yield and high costs by using a custom-trained building agent that ensures reliable task generation. The framework scales to nearly a million environments and demonstrates effectiveness through reinforcement learning applications.
TierZero offers AI production agents that streamline incident management, alerts, and support queries for engineering teams. By automating investigations and providing context-driven insights, it reduces the time engineers spend troubleshooting, allowing them to focus on development. The system aims to enhance efficiency while maintaining security through auditable processes.
Guillermo Rauch discusses the advancements in AI's ability to write complex software, questioning whether these developments indicate true super-intelligence. He outlines specific challenges for AI to tackle, such as identifying security vulnerabilities and rewriting compilers, as benchmarks for assessing AI's capabilities in software engineering.
The article outlines a detailed plan for developing antimatter propulsion technology, likening it to a new Manhattan Project. It discusses the challenges of antimatter production, storage, and engine design, emphasizing the potential for faster interplanetary travel.
This article discusses the benefits of owning a data center instead of relying on cloud services. It covers practical aspects like power, cooling, server setup, and software management, based on comma.ai's own experience. The author emphasizes self-reliance, cost savings, and engineering challenges.
The article highlights recurring issues in microservices, emphasizing that complexity and chaos are inherent in distributed systems. It discusses common pitfalls such as excessive services per engineer, poorly managed gateways, technology sprawl, and the problems of aligning architecture with organizational structure.
Salesforce has integrated Cursor into its engineering workflow, resulting in over 30% gains in development speed and code quality. The tool has been particularly beneficial for both junior and senior engineers, helping them automate tedious tasks and improve understanding of the codebase. Metrics like cycle time and bug count show significant improvements since adopting Cursor.
The article critiques the practice of deploy freezes, especially on Fridays or before holidays. It advocates for freezing merges instead of deploys to allow developers to continue working on other tasks without accumulating risks that could lead to issues in January.
This article outlines key engineering insights gained from building a database replication tool for Amazon RDS Postgres using Rust. It addresses challenges like compatibility issues, deployment complexities, and the need for proactive network management. The authors stress the importance of customizing solutions for the specific constraints of managed environments.
This article discusses the clopus-watcher, an autonomous agent designed to monitor applications in Kubernetes and apply hotfixes as needed. The author argues that such systems could eventually replace many roles currently held by 24/7 on-call engineers.
This article discusses Codemaps, a new tool designed to enhance engineers' understanding of complex codebases. It helps users navigate and analyze their code more effectively, facilitating better debugging, onboarding, and feature development. Codemaps integrates with existing tools to provide a clearer view of code structure and data flow.
The article outlines a Staff Engineer's strategy for staying informed about the tech industry and leveraging insights from multiple mentors. It emphasizes the importance of avoiding common engineering pitfalls like missed deadlines and bottlenecks. The author also highlights the use of DevStats to align engineering efforts with business goals.
The author shares their journey to becoming a compiler engineer, detailing their education, job search, and the unique challenges of breaking into this niche field. They provide insights into the interview process and preparation strategies based on their experiences.
The article explores how large tech companies often produce poor-quality code despite having skilled engineers. It attributes this issue to high turnover rates and the constant shifting of engineers between projects, which limits their familiarity with specific codebases. The author argues that the structure and priorities of these companies contribute significantly to the problem.
FluidStack is hiring for 48 positions across various fields, including legal, engineering, operations, and finance. Locations include major cities like New York, Austin, and San Francisco, with some roles available for remote work. Each position is full-time.
Google released an upgraded version of Gemini 3 Deep Think, aimed at solving complex challenges in science and engineering. The update improves reasoning capabilities and is now available to Google AI Ultra subscribers and select researchers via an API. Early users report significant breakthroughs in fields like mathematics and materials science.
This article outlines Monarch's philosophy on integrating AI into software engineering while maintaining quality and accountability. It emphasizes understanding the latest developments in AI without rushing to adopt every new tool and stresses the importance of individual ownership of work.
This article discusses how AI is reshaping software engineering, leading to a divide between high-performing and mediocre teams. It emphasizes that the real challenge lies in understanding user needs and making strategic decisions, rather than just coding. The author argues that those who adapt will thrive, while others risk becoming obsolete.
In 2026, coding will accelerate dramatically due to advanced AI tools, allowing developers to produce vastly more code. However, organizations must adapt their processes to handle this increased output effectively; otherwise, they risk bottlenecks in review and deployment. The future of software delivery will depend on optimizing the entire pipeline, not just the coding phase.
This article outlines how Olivier Pomel, CEO of Datadog, built the company to $100 million in annual recurring revenue by prioritizing customer feedback over initial product development. It discusses key strategies like open beta testing, month-to-month contracts, and involving engineers in customer support to maintain a customer-focused approach.
The article discusses the impressive capabilities of Claude Code's development experience (DX), but raises concerns about its potential drawbacks. It explores how the tool's efficiency may lead to over-reliance and reduced critical thinking among users.
This article explains how to build a scalable business by focusing on three key growth curves: exponential growth in users and revenue, linear growth in bugs, and logarithmic growth in support needs. Engineers play a vital role in managing these dynamics to ensure long-term success and sustainability.
This article shares key lessons from a decade of frontend engineering, focusing on how to optimize testing for better development velocity. It emphasizes the importance of minimizing maintenance costs and choosing the right scope for tests to enhance coverage and reliability.
The article explores how large tech companies often produce poor-quality code due to high turnover and engineers frequently working outside their expertise. It highlights the challenges faced by engineers in unfamiliar codebases and the lack of support for long-term ownership, leading to subpar software outcomes.
This article explains Data Bridge, Netflix's new platform for managing data movement across its various data storage systems. It highlights how Data Bridge addresses challenges like tool fragmentation and user confusion by providing a unified interface for data operations. The platform aims to streamline processes and enhance governance.
This article discusses how modern software products rely on a complex web of external dependencies, making supply chain risk a critical concern for product engineering teams. It emphasizes the need for trust verification and security measures to prevent compromises from third-party components. The framework SLSA is presented as a solution for establishing software integrity.
The author reflects on a decade in observability, highlighting the rampant waste in data and the vendor's lack of support for cost management. They reveal that many companies experience significant data waste, leading to inflated bills and operational challenges. The article argues for a shift in how observability is approached, emphasizing understanding over sheer volume of data.
Zenflow is an orchestration platform designed for AI-driven engineering. It enables teams to manage workflows through spec-driven development, allowing multiple AI agents to work simultaneously on tasks while maintaining code integrity and quality. The platform includes built-in verification and supports both pre-built and custom workflows.
Ben Horowitz recounts a conversation with Mark Zuckerberg about firing his executive team for the second time. Zuckerberg faced challenges with a growing engineering team that led to performance issues, prompting him to realize the importance of structured training for new hires. Horowitz highlights Zuckerberg's management skills and understanding of people in leadership.
This article outlines key lessons learned from a long career at Google, focusing on the importance of user-centric problem solving, collaboration, and clarity in engineering. It emphasizes that technical skills alone aren't enough; navigating people and processes is crucial for success.
The article argues that we are entering a new phase in software development, likening it to the Cambrian explosion in biology. AI coding tools have advanced significantly, allowing rapid creation of software, but they still fall short in critical areas like system architecture and security. As a result, skilled engineers will be essential to manage the influx of new software and ensure quality.
This article discusses how the promise of DevOps often overlooks governance, leading to a lack of accountability in automated deployments. It highlights the emerging role of GRC Engineers, who integrate governance, risk, and compliance directly into DevOps practices, ensuring that security and compliance are built into the development process.
Amazon laid off over 14,000 employees, with nearly 40% in engineering. The cuts reflect a shift in company culture under CEO Andy Jassy, who aims to reduce bureaucracy and focus on AI investment. Further job reductions are expected in January.
This article discusses an interview with Mai-Lan Tomsen Bukovec, VP of Data and Analytics at AWS, focusing on the engineering behind Amazon S3. Key topics include S3's scale, strong consistency, durability measures, and the use of formal methods to ensure system correctness.
This article explores the trend of startups emulating Palantir's model of embedding engineers within client organizations to deliver customized software solutions. It critiques the scalability of this approach, highlighting the unique factors that make Palantir effective and the challenges faced by other companies attempting to replicate its success.
This article outlines 21 key insights gained over 14 years at Google, emphasizing the importance of understanding user problems, collaboration, and clarity over cleverness in engineering. The author shares lessons that focus on navigating workplace dynamics and improving productivity, rather than just technical skills.