Skip to content

Developer everyday life

How does an idea become a task list? Why does a small change sometimes take a lot of time? These texts show the way of working behind a software project — useful for anyone who works with developers.

Recommended reading order

  1. How developers turn an idea into concrete tasksThe five steps between idea and actionable task.
  2. Bug or change request: why the distinction helpsThe question that determines urgency, sequence and cost.
  3. From prototype to production applicationWhat lies between a convincing demo and use in live operation.
  4. What does clean code mean in everyday project work?Why readability is the price of your next change.
  5. Code review: what is checked?The second look before release — and its checklist.
  6. Why software tests need concrete failure casesWhat a green test proves and what it does not.
  7. Git and version control explained clearlyA project's memory — and what is missing without it.

All articles in this section

From idea to tasksWhy follow-up questions arise and what a good task description contains.Collaboration · about 6 minutes
From prototype to applicationSix areas that lie between draft and deployment.Project planning · about 6 minutes
Bug or change request?Not a question of blame, but of expectation — and what belongs in a report.Collaboration · about 6 minutes
What does clean code mean?Five verifiable properties — and where the term is overused.Background · about 6 minutes
Code reviewThe checklist in order of importance.Collaboration · about 6 minutes
Why software tests need concrete failure casesThe counter-check, and why a coverage figure says little.Understanding · about 7 minutes
Git and version controlA project's memory and what does not belong in it.Introduction · about 6 minutes

Collaboration that works

Tell us about your project and who makes the business decisions. The task list is created together.

Discuss a project