The article explains the true meaning of 'refactoring' in software development and argues for its proper use to avoid client misunderstandings.
A developer announces the return of their technical blog after a 3-year hiatus, hinting at future posts on databases, cloud, AI, and more.
A software engineer shares stories of taking initiative to meet colleagues and Alan Kay, leading to career opportunities and collaboration.
Distinguishes between Functional AGI (replacing knowledge workers) and Technical AGI (true generalization), arguing Functional AGI's societal impact matters most.
A developer shares insights from Jfokus 2025, highlighting talks on Java performance optimization and AI agents in software development.
Argues that learning to code remains essential in 2025 despite advanced AI, emphasizing critical thinking, debugging, and career value.
A personal review of 2024 focusing on open source project goals, financial earnings, and productivity reflections from a full-time developer.
A developer explores adapting coding styles to different situations, inspired by the 'Six Thinking Hats' framework.
A developer's experience with the Cline AI coding assistant, exploring its capabilities for bug fixing and the implications for programmers.
A developer shares personal experience and reasons for contributing to open-source projects like GitLab, highlighting non-coding contributions and benefits.
A software engineer explores using LLMs and R code to analyze GitHub activity to track and summarize their weekly work, addressing the challenge of remembering tasks.
Critique of modern dependency bloat in software development, advocating for simpler, minimal-dependency designs.
A call to discuss transparency and governance issues at FOSDEM '25 following the cancellation of a controversial sponsored keynote talk.
A developer reflects on career transition struggles, exploring tech stacks like Rust and Elixir, and the challenge of focusing on a single path to build products.
A reflection on the concept of 'theoretical software engineers' and the tension between ideal best practices and pragmatic, real-world development.
A guide to common mistakes developers make when building applications with generative AI, including overuse and poor UX integration.
Argues that politeness markers like 'please' weaken technical documentation and should be replaced with direct, actionable instructions.
An analysis of three common reasons why funding models for open source software projects often fail, based on the author's long-term experience.
Explains why developers should split unrelated changes into separate pull requests for faster reviews, cleaner Git history, and better automation.
A senior developer shares eight key lessons on writing clean code, conducting effective reviews, and professional best practices from decades of experience.
