About Fingers Crossed Driven Development

The Idea Behind FCDD

Let's be honest: we've all written code that made us cringe later. The gap between what we learn in books and what we ship in production is often... well, let's just say it's wider than we'd like to admit.

Fingers Crossed Driven Development is a collection of real-world code examples found in public GitHub repositories. These aren't meant to shame anyone - they're here to help us all learn in a relatable, non-judgmental way.

Why This Matters

With over 15 years of software development experience, I've seen (and written) my fair share of questionable code. The truth is, learning what NOT to do is just as valuable as learning best practices.

This site exists because:

  • Real examples are more memorable than textbook explanations
  • We can learn together without taking it personally
  • Understanding WHY something is wrong helps us write better code
  • Sometimes we need to see the problem to recognize it in our own code

The Prayer Level System

Not all code issues are created equal. Our prayer level system helps categorize the potential impact:

🤞
Fingers Crossed
Minor issues, mostly harmless.
🤞🤞
Double Cross
Could cause problems down the line.
🙏
Thoughts & Prayers
Serious code smell detected.
🙏🙏
Emergency Prayer Circle
Critical issues, fix immediately.

How Content is Curated

Every example on this site comes from real, publicly available open source code. The process:

  1. Code snippets are found through GitHub searches and repository exploration
  2. Examples are selected based on educational value, not severity
  3. All repository and author information is anonymized
  4. Each post includes the problematic code, explanation, and better approach
  5. A "Prayer Level" indicates the potential severity of the issue

A Note on Ethics

This project is built with empathy and respect for fellow developers:

  • All code is from publicly available open source repositories
  • Repository names and author information are never shared
  • The goal is education, not ridicule
  • We acknowledge that context matters - sometimes "bad" code is a pragmatic choice
  • Everyone writes imperfect code sometimes (including me)

We've All Been There

If you see something here that looks suspiciously like code you've written, join the club. That's the point - these patterns are common because they're easy to fall into, not because developers are careless.

The best response isn't embarrassment - it's learning and growing. That's what this site is all about.

Ready to learn from real-world examples?

Browse All Posts