"Money-Burned" is a pool of examples that should serve as a starting point for everyone who wants to develop an application from scratch in various target environments using different frameworks and technologies.
The background of "Money-Burned" is trying to answer the question of the comparability of different technological approaches when selecting a tech stack for a set of identical specific requirements.
"Money-Burned" is somewhat ambiguous here. On the one hand, the name refers to the basic requirements that we want to implement in our various technology-specific examples:
The result should always be a tool that visualizes the money spent over time by knowing the resources used and the time elapsed.
On the other hand, it is a humorous allusion to the amount of time that is often pointlessly wasted trying to find a suitable entry point for a new project.
We are pleased that you are interested in "Money-Burned", software development or both! Perhaps you simply choose a project/repository from the list of examples below that is using a framework or programming language you are already familiar with. Maybe you choose one, you'd like to get familiar with. And if there's nothing for you yet, simply choose one of your preferred operating system.
All sample repositories should come with a description of the chosen development concept, design considerations and a simple explanation of how to run the application.
Yay, happy to have you with us! We're so excited to see what the implementation of "Money-Burned" will look like on your favorite platform and how it will be created. Please refer to our intro for contributors and the code of conduct to get involved.
| Repo Name | Technology | Language | OS | Dep. Repo | Maintainer |
|---|---|---|---|---|---|
| mb-dotnet-console | dotnet | C# | x-platform | mb-dotnet-lib | roschinsky |
| mb-dotnet-winapp | dotnet WinForms | C# | Windows | mb-dotnet-lib | roschinsky |
You will then find all the information in the README file of the respective project. In addition to the description of how to get the application running and what you need for this, you should also learn something about the approach used to create the program.
This includes details about the degree of coverage of the requirements, information about the data model and persistence as well as any special challenges during development.