"Code of Duty" — Every line of code has its own mission. We avoid shortcuts and quick fixes, focusing on authentic coding reflections and the joys and challenges of technical growth. The journey of learning matters more than any destination. Join us as we humbly forge ahead in the world of code.
This step‑by‑step guide shows developers how to install Cursor, configure its settings, open a project, use Tab completion, Inline Edit, Ask mode and the Agent, and set project rules while highlighting safety best practices.
The article explains that a Pull Request is a request for the team to review and merge code, outlines the risks of bypassing PRs, details a standard PR workflow, describes what reviewers check, offers tips for writing high‑quality and small PRs, and lists post‑merge actions.
Git conflicts occur when multiple branches modify the same code; this guide explains why they happen, how to interpret conflict markers, step‑by‑step resolution commands, three common resolution strategies, tool‑assisted fixes, and post‑merge checks to ensure clean, error‑free integration.
This article explains what Git rebase does, compares it with merge, shows concrete command examples, outlines when to use it safely on personal branches, warns against rewriting shared history, and introduces the safer --force-with-lease option for forced pushes.
This article walks through the full LLM pipeline—from tokenization and embedding to transformer attention, pre‑training, instruction tuning, RLHF, inference, context windows, Retrieval‑Augmented Generation and agents—explaining each component, its role, and the engineering challenges such as hallucination and safety.
The article explains why force‑pushing after a commit has been shared can corrupt team history, contrasts reset and revert, shows safe alternatives, and outlines scenarios where force‑push might be acceptable.
The article explains why Codex needs explicit project rules, distinguishes between collaboration rules in AGENTS.md and command‑permission rules in .codex/rules, and provides concrete examples, templates, and a checklist for writing effective, specific rules that keep Codex aligned with team conventions.
The article explains how the shift from traditional search‑engine optimization (SEO) to Generative Engine Optimization (GEO) changes content strategy, requiring brands to make their information understandable, trustworthy, and citable by AI assistants rather than merely ranking on search results.
The article examines why many programmers voluntarily purchase AI coding tool tokens, arguing that the real value lies in saving time, reducing the frustration of being stuck, and gaining a more certain, efficient workflow despite the lack of corporate reimbursement.
This guide walks through Git's reset command, detailing the differences between --soft, --mixed, and --hard modes, when each is appropriate, and how they affect commits, the index, and the working tree for commits that haven't been pushed.
