← Blog

Full library access

Unlock every article — and keep reading each month

Create a free account, pick a plan that fits how you read, and use monthly credits for deep dives on engineering, products, and founder reality. Cancel or switch anytime from your profile.

Blog

It all depends what you assume by when a project was born.

Hi, my name is Tom Smykowski, I'm a staff full-stack engineer. I build and scale SaaS platforms to millions of users, working end-to-end from system architecture to frontend to mobile. On this blog I share what I learn about software engineering, project timelines, and defining success in tech ventures.

What This Article Covers

This article delves into the intriguing question of when a project can be considered truly "born." Using Django as a case study, it explores various ways to pinpoint the inception of a tech project, from conceptual establishment to the availability of a downloadable version. The discussion highlights the complexities and subjective nature of defining a project's start date.

Questions This Article Answers

  • What are the different criteria for determining when a tech project is born?
  • How does the case of Django illustrate the complexities of defining a project start date?
  • Why is there no universally accepted rule for when a project begins?
  • How can different perspectives on project inception affect project management and historical accounts?

Length and Time

A thoughtful exploration with historical insights and practical considerations. Approximately 6 minutes to read.

Want to unlock the full story? Log in

Full library access

Unlock every article — and keep reading each month

Create a free account, pick a plan that fits how you read, and use monthly credits for deep dives on engineering, products, and founder reality. Cancel or switch anytime from your profile.

← All posts