An analysis of why many corporate engineering blogs fail to attract readers and the key processes used by successful ones like Cloudflare and Segment.
A software engineer argues that effective performance optimization requires understanding system bottlenecks and applying a scientific, evidence-based approach.
Discusses the challenges of scaling software development over time, emphasizing the need for automated enforcement of code properties as projects grow.
Argues for starting web projects with simple, traditional HTML/CSS/JS instead of over-engineering with complex modern frameworks and build tools.
A software engineer critiques algorithms interviews, arguing they don't reflect real-world problem-solving, despite providing value by fixing such issues on the job.
A personal blog post reflecting on the author's journey from a struggling college student in 2010 to a software developer, sharing lessons learned.
Author announces a new personal blog built with Hugo for open source, project updates, and software engineering topics.
Developer announces a new personal blog built with Hugo, focusing on open source projects and software engineering topics.
Explains why premature optimization in programming is inefficient, using the Pareto Principle and power laws to argue for data-driven performance improvements.
A personal reflection on the author's life journey through the 2010s, covering career, family, and personal growth.
Applying mental toughness principles from elite sports to software engineering, focusing on overcoming mental barriers and personal excellence.
The article critiques the overuse and devaluation of the titles 'Engineer' and 'Scientist' in modern IT, focusing on data science and engineering roles.
A software engineer argues that understanding business operations is crucial for career growth and making a greater impact.
An article challenging the '10x engineer' myth and proposing the concept of a '+10% engineer' who boosts team productivity through collaboration and support.
A software engineer shares practical advice for managing stress and handling on-call production support incidents effectively.
Explores intrinsic reasons why a senior software engineer might choose to remain an individual contributor instead of pursuing a management career path.
Explains memory unsafety in programming languages, its security risks (out-of-bounds reads/writes, use-after-free), and contrasts unsafe languages like C/C++ with safe ones.
A software engineer explains that experience comes from solving diverse problems, not just time, and suggests ways to find them.
The article argues for the importance of developing code reading as a critical skill for software engineers, alongside writing code.
Analyzes the debate on the best location to start a tech startup, arguing the Bay Area's advantages are concentrated and not accessible to most founders.
