The author argues that a technical manager should devote about 80% of their time to coding and only 20% to management, warning that abandoning hands‑on development erodes technical judgment, team trust, and long‑term career competitiveness.
Over two years I promoted a junior developer to mid‑level, raised his salary, and increased his bonus after he consistently delivered clean DDD‑styled code, handled simple tasks flawlessly, proactively addressed third‑party integration challenges, and demonstrated the ability to take on greater responsibility, illustrating the true criteria leaders use for advancement.
A newly appointed leader identifies the symptoms of a fragmented software team, wins a few hard‑fought projects, restructures the core system, rewards key contributors, and adopts a front‑line leadership style to restore morale and deliver results.
The article argues that persuasion is unnecessary for leaders, who should make final decisions, and for non‑leaders the proper approach is to clearly present ideas to the leader for decision‑making, illustrated with a microservice request case.
The article argues that blaming code quality masks deeper issues such as uncontrolled requirements, missing engineering systems, and weak management, and it outlines a 2026 quality‑governance framework with practical steps for leaders to create an environment where high‑quality code can thrive.
This article explores why agile teams must interpret measurement data holistically, showing how focusing on a single metric can create trade‑offs, and offers a systematic approach to analyzing productivity, stability, and quality indicators for continuous improvement.
This guide compares Ubuntu and Kubuntu 23.04, highlighting differences in desktop environments, software management, built‑in applications, release cycles, installation experience, and system resource usage to help users decide which distribution best fits their workflow.
The iDesk service platform is a comprehensive internal tool that evolved through three development phases, adopts a BS+Service architecture with modular local services, offers extensive software management and self‑service utilities, integrates tightly with TripPal and service accounts, and implements robust operational monitoring to achieve high availability and user satisfaction.
This article recounts a twelve‑year‑long French government software project that amassed over six million lines of C++ code, suffered from outdated technology, chaotic version control, absurd management policies, and ultimately collapsed, offering stark lessons for developers and project leaders.
This article analyzes how Kubernetes’ API‑first design, inspired by cloud‑computing principles of programmable and declarative infrastructure, creates a universal control plane that transcends container orchestration and reshapes software management across clouds.
This guide explains why Windows 7 users should migrate, recommends Linux Mint as a beginner‑friendly distro, and provides detailed instructions for creating a bootable USB with Rufus, installing the OS, configuring dual‑boot or full replacement, and managing software via the GUI or command line.
This article shares practical insights from a Tech Connect keynote on how technical leaders can understand developer psychology, avoid conventional management pitfalls, bridge decision‑consequence gaps, and foster a culture that empowers engineers to deliver high‑quality software while meeting business goals.
After years of mastering code, I shifted from solo programming to leading a software team, discovering that technical skill alone isn’t enough; effective management demands communication, big‑picture thinking, and nurturing a strong team, while still preserving enough technical insight to stay relevant.
