Desire Kaleba's repositories
way-farer-backend
WayFarer is a public bus transportation booking service
v3.ocaml.org-server
Server-side of the next version of the ocaml.org website. See https://github.com/ocaml/v3.ocaml.org for the frontend.
your_first_code
A very simple snippet of C code, for Holberton School's admissions.
expenses
An expenses tracker app built with Flutter.
boilerplate-advancednode
A boilerplate for the freeCodeCamp curriculum referenced in 'Advanced Node/Express Introduction'.
boilerplate-project-timestamp
A boilerplate for a freeCodeCamp project.
covid-19-tracker-chrome-extension
A covid19 chrome extension
desirekaleba.github.io
My Portfolio Website
developer-roadmap
Roadmap to becoming a web developer in 2020
freecodecamp-curriculum-projects
FreeCodeCamp Curriculum
full-stack-interview-questions
🔴 More than ~3877 Full Stack, Coding & System Design Interview Questions And Answers sourced from all around the Internet to help you to prepare to an interview, conduct one, mock your lead dev or completely ignore. Find more questions and answers on 👉
github-slideshow
A robot powered training repository :robot:
gitignore
A collection of useful .gitignore templates
loruki-website
Cloud hosting website
react-progs
simple react projects
ruby-practs
Ruby practices
rust-guessing-game
Rust guessing Game. the program will generate a random integer between 1 and 100. It will then prompt the player to enter a guess. After a guess is entered, the program will indicate whether the guess is too low or too high. If the guess is correct, the game will print a congratulatory message and exit.
season-less-repayment
Each season, clients purchase products on credit, and over the course of a season, they repay their credit, and so clients have credit associated with them on a season-by-season basis. In our data model, we associate a client’s payments with a season for which they have outstanding credit. These payments are made either through cash to a Field Officer or through a mobile money platform (ex. M-Pesa). A member of our HQ staff then takes a list of payments that clients have made, and uploads them into our application, which saves each payment, and each payment must be associated with the correct client and season in our database. When a client makes a payment, we need to know which season the payment will be applied to, as sometimes clients can have outstanding credit (debt) in more than one season. Traditionally, we required each payment in a payment upload to be associated with a season, so that the application doesn’t have to figure out to which season(s) the client’s payment needs to be applied to. But to make it easier on clients, Field Officers, and HQ staff, we’re moving away from this model, and dropping the requirement that seasons must be associated with each payment contained in a list of payment uploads. Since we still require that each saved repayment must be associated with a season in our database, this means we need ‘seasonless repayment’ logic to dynamically determine which season(s) the client’s payment should be applied to.
socket.io-website
Socket.IO website and blog