The article shares practical QA techniques and project‑progress strategies for a mobile DSP advertising team, emphasizing paper‑based documentation, rapid test case execution, clear test design using XMind, and the potential of AI‑driven bug analysis, while also highlighting the importance of versatile testing roles.
This article explores how project management’s cost‑schedule‑quality triangle, ISO quality definitions, the software quality “iron triangle” of process, organization, and technology, and the six quality characteristics guide developers and testers in improving product quality through systematic thinking and practical testing methods.
This article introduces the npm package tree-node-cli, explains how to install it globally, demonstrates its powerful visual tree output, customizable options, and how it can efficiently help developers understand and manage complex project file hierarchies.
This comprehensive guide outlines the seven essential abilities—system design and modeling, broad and deep technical expertise, global and systemic thinking, effective communication and collaboration, project management, quality assurance with technical debt control, and innovative foresight—that together define a successful software architect.
This article compares the traditional Waterfall development model with Agile methodologies, outlines Scrum roles and processes, and discusses how teams can balance documentation‑heavy and people‑centric approaches to improve software project efficiency and adaptability.
This translated article shares 42 practical lessons from Mahesh Balakrishnan’s experience building a production database, covering customer focus, project management, design principles, code review, strategy, observability, and research practices for reliable infrastructure development.
This guide outlines practical project‑management practices and tool configurations—such as using Cursor rules, Notepad, milestone documents, and regular code‑base re‑indexing—to maximize the effectiveness of the Cursor AI assistant in large‑scale software projects.
The article explores why software estimation is inherently difficult, discusses the pitfalls of striving for perfect plans, highlights the difference between accuracy and precision, and presents practical techniques such as small‑step development, historical reference, and T‑shirt sizing to improve estimation reliability in software projects.
This article explains the purpose and interpretation of cumulative flow diagrams in lean software development, illustrates how WIP and lead time affect delivery, and discusses common pitfalls such as code coupling, optimistic estimates, and non‑project activities that hinder iteration progress.
The article shares candid insights about the real‑world life of software engineers, emphasizing that most work involves maintaining large codebases, understanding domain logic, writing good documentation, focusing on business value, handling incompetent colleagues, coping with uncertainty, and assuming everything can fail.
This article explains the differences between remote and distributed teams, outlines the benefits of a distributed model, and provides practical tips, communication strategies, meeting structures, video documentation methods, and team‑management practices for successfully running a distributed software development project.
The HTTPie project lost over 54,000 GitHub stars after its maintainer accidentally made the repository private, revealing shortcomings in GitHub's confirmation dialogs and backup policies, and prompting recommendations for better UI/UX and soft‑delete mechanisms to protect open‑source projects.
This article presents a structured recommendation of Java books covering introductory syntax, intermediate refactoring and TDD, advanced architecture, software development processes, and project management, helping Java developers progressively deepen their knowledge and improve coding practices.
After nearly a decade of work in embedded, web, mobile, consulting, and integration projects, the author outlines four major knowledge areas—engineering methods, system integration, project management, and development—detailing essential practices, design principles, and technology stacks such as C, Android, cloud services, and big data.
This article provides a detailed overview of Maven, covering its purpose, project structure, build lifecycle phases, dependency coordinates and scopes, repository types, plugin mechanisms, aggregation and inheritance, as well as flexible configuration using properties and profiles, all illustrated with practical code examples.
This article compares the traditional Waterfall development model with Agile methodologies, outlines Scrum roles and workflow, highlights each approach's strengths and weaknesses, and emphasizes the importance of team consensus for effective software project management.
The article explains the distinction between defined and high‑uncertainty work, outlines traditional waterfall planning versus adaptive agile approaches, compares their processes, costs, and success rates, and presents data from the Standish Group showing agile projects outperform waterfall ones.
This guide explains how to plan an application by identifying the problem it solves, its users, and goals, then maps the entire business process with visual flowcharts to ensure the solution fits within and improves the overall workflow.
This article explains the distinction between well‑defined and high‑uncertainty project work, compares traditional waterfall planning with modern Agile practices, and presents data showing Agile’s higher success rates while also providing practical guidance for teams transitioning to more exploratory development approaches.
This article explains why developers should master project management, outlines common pain points such as inaccurate estimations and dependency issues, and provides practical guidance on progress, quality, and risk management through clear processes, checklists, and collaboration techniques.