Introduction

This is a fully functioning trading BOT that can monitor and automatically buy and sell multiple cryptocurrencies.

Note: I ran this on my local machine and did not deploy for public consumption. Front end is simple Bootstrap and JS to call the API endpoints that I created with Node.JS. Backend is Node.JS which includes the Binance APIs (retrieving OHLC, making buy orders, sell orders, etc.) and computations for detecting candlestick patterns, and targets. I had to read a book on trading fundamentals to code this correctly. The front end displays results and sets alarms based on the API responses. For example, everytime a crypto shows a bullish pattern, a sound goes off. The same applies for when a crypto is bought and sold.

Overview of Steps

• Retrieve OHLC via Binance API
• From the logic and computations written in Node.JS, detect various bullish patterns and points of entry
• Automatically make a buy order when targets and conditions written in Node.JS are met
• Once the purchase is verified, make a sell order using the target price computed in the backend.
• If target price is reached, detect if it has already been sold. If not sold within the set period, automatically cancel the sell order and sell at current market price. This is to lessen the chance of further decline and loss.
• Note that the steps described above can run on various frequencies depending on the set period (1m, 5m, 30m, etc).
• Also note that the code is structured in a way that can run as much as 20 cryptocurrencies. It should be able to run more but I only tested up to 20.

Introduction

This is a fully functioning essay checker that I created in an AI competition while I was with Cambridge University Press & Assessment.

Note: I ran this on my local machine and did not deploy for public consumption. Front end is simple Bootstrap and JS to call the API endpoints that I created with Node.JS. Backend is Node.JS and connects to OpenAI API and another language API that I liked.

Overview of Steps

• Exam moderator or checker inputs the essay via the simple interface
• From the score guide provided by Cambridge University, I created the logic to help the backend make the necessary computations to correctly score the exam.
• After multiple API calls to the OpenAI API, the backend then provides the score to the front end.

Introduction

This is a fully functioning online sports betting platform (except for the payment and disbursements of real Philippine peso).

Overview of Steps

• Users can view in real time upcoming sports events from different types of sports and leagues including the odds
• With gems (not real money), users can place bets.
• Also in real time, users can check if their team(s) have won and will be able to see their winnings.
• Note that this also includes a few casino games such as Slots, Roulette, Bingo, and Blackjack.

Introduction

This is a fully functioning asset management system. In a nutshell, an IT administrator can CRUD product lines and the corresponding assets, and employees can view and request for assets. Users and admins also have a transactions page to view and update the status of the requests. Users can cancel their own requests while admins can approve, reject, and complete all requests.

To test the functionality as a user, simply click the link, register, and login. To test as an admin, use [email protected] and 12345678 for the password. Note that this application and its database are hosted for free via Heroku and db4free so the speed might not be optimal.

Link (already taken down by Heroku): https://assetmgtdennis.herokuapp.com/

Work Breakdown:

1. Generate Laravel web app, set database connection in env, authentication scaffolding, database design
2. Creation of models, migrations, controllers, policies, and gates
3. Create product line and create individual asset functionality for admin
4. Retrieve and view product lines functionality for all roles (non-admin only has to see product lines, no need to see individual assets)
5. Update and disable product line / asset functionality for admin
6. Create request for non-admin
7. Retrieve and view requests by all roles
8. Update request status functionality for non-admin (cancel pending) and admin (approve, reject, complete)
9. Heroku hosting

Features / Requirements:

• Users may have the role of an admin or a non-admin
• Admin users may create, retrieve, update, and disable product lines
• A product line may have many assets
• An asset must be uniquely identifiable
• An asset can either be available or unavailable at any given time
• Similar to the product line / asset category, admin users have full CRUD functionality over assets
• Non-admin users may retrieve product lines
• Non-admin users may request for a specific product line for a specific borrow and return date
• Requests have a default status of "pending" upon creation
• Pending requests may have their status changed to the following:
1. Cancelled by the user who made the request
2. Rejected by an admin
3. Approved by an admin, at which time an asset will be assigned to the request
• An asset assigned to an approved request will have its status set to unavailable for the duration of its assignment
• Approved requests can have their status changed to completed only by an admin user
• Upon being set to completed, the asset assigned to it will be made available again
• Requests / transactions may only be created by non-admin users but may be updated by all roles given the conditions above
• Retrieval / viewing of requests may be done regardless of user role
• Admin users should be able to view all requests
• Non-admin users may only view requests that they made
• Both views should have 3 tables:
1. Pending requests table with the following columns:
• Request ID, product line requested, borrow date, return date, request date, action (cancel for non-admin, approve or reject for admin)
2. Approved requests table with the following columns:
• Request ID, assigned asset ID, borrow date, return date, approval date
3. Completed requests table (cancelled, rejected, and returned requests will fall here) with the following columns:
• Request ID, asset ID (N/A if rejected or cancelled), borrow date, return date, status, completion date

Introduction

I've developed a bartering platform (similar to a buy and sell platform) that combines features from Facebook, Instagram, classic forums from the 2000s and eBay. It has the usual intuitive board set-up where users can make public posts and send private messages to other members. Admins can create main categories or boards, and move or delete posts that don't follow guidelines.

To test the functionality as a user, simply click the link, register, and login. To test as an admin, use [email protected] and 12345678 for the password. Note that this application and its database are hosted for free via Heroku and db4free so the speed might not be optimal.

Link: iBarterMo PH

Features:

• Superadmins can easily add main categories. This will immediately show up in the navbar as an item and in the website's home page as one major board category.
• The home page will display all major board categories while previewing the recent 8 topics (aka threads) per category.
• Clicking on a major board category will take you to a separate page that will display all threads under that category.
• Clicking on a topic will take you to the detailed view of that topic and users can make discussions there. The discussions are more similar to Facebook and Instagram replies than the posts or replies in classic forums. I made this shift in design on purpose.
• Users can easily add threads or posts and they can upload multiple photos in one post.
• Uploaded photos are automatically renamed and resized for preview and also resized for a slightly bigger modal view.
• Users can delete/deactivate their own threads/posts
• Users can view profiles of other registered users.
• Users can also send private messages to other users and they can open them in their inbox.
• Visitors can read public posts but they need to register or login to create new posts/threads or reply to posts.
• Footer includes a simple count of users, posts and images.
• Users can easily seach for keywords and the application will return all results have those key words in both the post title and the post body.
• Users can update their avatars
• Clicking on a user's profile will also display a summary of all their posts.

Features under development:

• Pagination
• Deletion of own replies to posts/threads
• Enable sending of images in private messages
• Enable sending of images in post replies
• Likes for posts and trophies for users.
• User Profile enhancements

Better care starts with CareConnect!

Existing features & rules:

• There are 3 user types: facility admin, clinician, and patient.
• Facility admins can CRUD patient records that are assigned in their facility. They can CRUD only basic information of patients but they cannot update patient's medical records because only clinicians can do that.
• Patients can only view their own patient records but are unable to edit anything.
• Clinicians can be assigned in multiple facilities
• Clinicians can view patients that are under those facilities.
• Clinicians can edit only a patient's medical records but cannot update patient's basic records.

Features in the product backlog:

FOR FACILITY ADMINS
• Dashboard with an overview of key performance indicators, such as patient volume and bed occupancy
• Patient and doctor management
• Billing and insurance management
• Inventory management for medical supplies and equipment
• Integration with electronic health records (EHRs)
• Reporting and analytics capabilities to track performance and identify areas for improvement

FOR PATIENTS
• Personal health record (PHR) with medical history, allergies, medications, and other relevant information
• Appointment scheduling with doctors and other care providers
• Secure messaging with doctors and other care providers
• Access to educational materials and resources
• Prescription refill requests and medication reminders
• Ability to view and pay bills online

FOR DOCTORS
• Patient management, including access to medical records, test results, and treatment plans
• Appointment scheduling with patients
• Secure messaging with patients and other care providers
• E-prescribing and medication management tools
• Ability to view and manage patient referrals
• Access to clinical decision support tools and other resources

Features

• Users can register / login
• Users can view, filter, choose and book cars on available dates
• Unavailable dates are shown in the calendar as well
• Users can view a summary of their bookings and can edit upcoming bookings
• Admins can view and edit all bookings by all users