Over several years I've tweaked a spreadsheet. My wife and I budget by forecasting. The goal is to make that forecast more accurate by applying seasonality statistics to variable costs...like an electric bill. Everything else that stays the same would be a constant and can easily be used.
We look at our finances like what is the minimum amount in our bank account on any given month and move money around based on that.
I'm using this app to learn Serverless architecture and use my front end developer experience to make it pretty.
I love that you've established the tag on-site and are walking folks through the journey. I think if you make it opensource, it could be a really strong lasting project. I'd immediately start looking for ways to contribute.
Ok, you've convinced me. I'm going to do it. I'm going to make this open-source. I guess I need to make the repo public, outline all of the features and notes I've taken and put them in GitHub issues to track features, then just attack it KanBan style.
If people join in, sweet. If they don't, then at least I got organized.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think open sourcing it would be a great idea.
Can you give me the short overview of how the app works?
Over several years I've tweaked a spreadsheet. My wife and I budget by forecasting. The goal is to make that forecast more accurate by applying seasonality statistics to variable costs...like an electric bill. Everything else that stays the same would be a constant and can easily be used.
We look at our finances like what is the minimum amount in our bank account on any given month and move money around based on that.
I'm using this app to learn Serverless architecture and use my front end developer experience to make it pretty.
I love that you've established the tag on-site and are walking folks through the journey. I think if you make it opensource, it could be a really strong lasting project. I'd immediately start looking for ways to contribute.
Ok, you've convinced me. I'm going to do it. I'm going to make this open-source. I guess I need to make the repo public, outline all of the features and notes I've taken and put them in GitHub issues to track features, then just attack it KanBan style.
If people join in, sweet. If they don't, then at least I got organized.