https://github.com/adamsiekierski/ddd

Dupa-Driven-Development Standards
https://github.com/adamsiekierski/ddd

ddd debugging development dupa js standard

Last synced: 4 days ago
JSON representation

Dupa-Driven-Development Standards

• Host: GitHub
• URL: https://github.com/adamsiekierski/ddd
• Owner: AdamSiekierski
• License: wtfpl
• Created: 2020-11-07T22:09:26.000Z (about 4 years ago)
• Default Branch: main
• Last Pushed: 2020-11-08T12:44:23.000Z (about 4 years ago)
• Last Synced: 2024-11-22T20:26:40.182Z (2 months ago)
• Topics: ddd, debugging, development, dupa, js, standard
• Homepage: https://siekierski.ml/ddd
• Size: 22.5 KB
• Stars: 3
• Watchers: 1
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.md

Awesome Lists containing this project

README

        


  



Dupa-Driven-Development


## What is DDD

Dupa-Driven-Development is a set of standards for writing JavaScript code. It focuses on debugging techniques, development process and developer's workflows.

### What does *dupa* mean

Dupa *[ˈdupa]* is a polish word used when an issue occurs. For example, you find that your app has crashed on production - "Dupa!". Or your PC had a BSOD but you didn't save your work - "Dupa!". Or something doesn't work and you don't know why - "DUPA!".

Dupa-Driven-Development Standards aim to lower the amount of frustration which comes when dealing with unexpected errors during programming, by implementing special techniques for developers to follow in order to find and debug the issue. 

## Debugging

The best debugging tool is no tool. The important thing when developing Dupa-Driven apps is writing as simple code as possible, so that we can debug it using the simpliest practices. Our best friend is `console.log`.

Although advanced debugging tools may seem helpful, they're hard to set up and take a lot of time to learn using all of their features. Dupa-Driven apps must be light and the development process must be agile, so we need to use the built in tools, which don't require any setup. The best tool is of course the `console.log`.