Intermediate Python Developer with MongoDB Expertise
Budget: $30 – $250 USD
Looking for a professional who possesses intermediate level Python skills along with MongoDB expertise.
Key Responsibilities:
- Designing a MongoDB database
- Importing/Exporting data
- Optimizing queries
Ideal skills include:
- Proficiency in Python
- Extensive understanding of MongoDB and related tasks
- Capability to work independently with minimal supervision.
Please note that the specific functionalities to be implemented will be discussed as we move forward with the project. Suitable candidates should be prepared to begin work immediately.
Please note that the successful bidder will be expected to have:
* Solid Python development skills.
* Experience with asynchrony and OOP.
* Proficiency in MongoDB.
* Knowledge of Docker and docker compose.
* Excellent debugging skills.
* Exceptional organization
* A strong sense of responsibility.
We appreciate swift responses and expect regular progress updates throughout the project. If you fit this description, please bid. Let's enhance this bot together!
I need to humanize the balance and ideally the next step is to make a referral system.
that's it in a nutshell
In concrete terms, here it is:
Remove the threshold value - that would small transactions a person could not go into a deep minus
to make that before the transaction would be checked whether the person has enough money - here it is necessary to do in several stages - from the beginning some preprocessing - that there would be some default values.
1e we need a separate module to work with balance - which itself takes money and answers whether there is enough money for the transaction and also gives the history of balances.
This module answers whether the user has enough balance (the sum of real and bonus deposits).
The balance is stored in a table and this table stores all the history of deposits and withdrawals of this balance with links to specific debits (transactions).
We also need a good system of calculations (tokenization) - that would find out before the moment of debiting - whether the user has enough money or not.
Structure of the write-off table:
user id
date (time stamp)
write-off type (bonus deposit accrual / bonus deposit write-off / real money accrual / real money withdrawal)
debit link (in transactons collection)
Flag - that this is an actual record
Value of virtual balance
Value of real balance
Balance history (i.e. directly write real deposit + virtual deposit = balance)
Record the date when the virtual balance should be burned (Separate table??)
Key Responsibilities:
- Designing a MongoDB database
- Importing/Exporting data
- Optimizing queries
Ideal skills include:
- Proficiency in Python
- Extensive understanding of MongoDB and related tasks
- Capability to work independently with minimal supervision.
Please note that the specific functionalities to be implemented will be discussed as we move forward with the project. Suitable candidates should be prepared to begin work immediately.
Please note that the successful bidder will be expected to have:
* Solid Python development skills.
* Experience with asynchrony and OOP.
* Proficiency in MongoDB.
* Knowledge of Docker and docker compose.
* Excellent debugging skills.
* Exceptional organization
* A strong sense of responsibility.
We appreciate swift responses and expect regular progress updates throughout the project. If you fit this description, please bid. Let's enhance this bot together!
I need to humanize the balance and ideally the next step is to make a referral system.
that's it in a nutshell
In concrete terms, here it is:
Remove the threshold value - that would small transactions a person could not go into a deep minus
to make that before the transaction would be checked whether the person has enough money - here it is necessary to do in several stages - from the beginning some preprocessing - that there would be some default values.
1e we need a separate module to work with balance - which itself takes money and answers whether there is enough money for the transaction and also gives the history of balances.
This module answers whether the user has enough balance (the sum of real and bonus deposits).
The balance is stored in a table and this table stores all the history of deposits and withdrawals of this balance with links to specific debits (transactions).
We also need a good system of calculations (tokenization) - that would find out before the moment of debiting - whether the user has enough money or not.
Structure of the write-off table:
user id
date (time stamp)
write-off type (bonus deposit accrual / bonus deposit write-off / real money accrual / real money withdrawal)
debit link (in transactons collection)
Flag - that this is an actual record
Value of virtual balance
Value of real balance
Balance history (i.e. directly write real deposit + virtual deposit = balance)
Record the date when the virtual balance should be burned (Separate table??)