Confused On COFFEE Lead Fullstack Developer & DevOps Engineer

Biography

My name is Oskar. I began my career as a computational linguist and acquired expertise in national language processing and machine learning at Ludwig Maximilian University (LMU) in Munich. In the past, I enjoyed creating machine learning models using datasets and web scraping techniques from the internet. Upon completion of my bachelor's thesis, I sought a new challenge in an area where most internet users engage with the web. As a result, I decided to focus on web development as my area of interest. I love the web stack, it endures the time, it still works. Of course it has pros and good, but it's still awesome. However personally, I a not great in UI/UX design, so most of my hobby projects lack a good design. Nowadays, I try to build applications using Rust and Golang programming languages. Sometimes, I present a UI next to it.

Skills

Web

Continuous I/D & IaC

Providers

Systems

Favourites

Loving

More

Hobby Projects

CHORESCORE

Description

This application facilitates a competitive environment for users by allowing them to form teams and participate in tasks and quests based on scoring systems and specified intervals. The ultimate goal is to determine which team has amassed the highest score on the leaderboard. The user can gain experience and compare his achivements with other players.

Primary Features

  • User: Each user, who signs up for the app, can become a member of one or more teams, provided they are invited to join.
  • Team: A team consists of quests, tasks, and members that work together towards achieving common goals.
  • Member: A member is an individual user, who has been accepted into a specific team. They collaborate with other members to complete assigned tasks and quests.
  • Task: A task can only be completed by a member of the team and must meet certain criteria, such as being public or private, having a specified time interval for completion, awarding points upon completion, and potentially being part of a larger quest.
  • Quest: A unique task created by a team member that requires completion within a given time frame by an individual user. Once completed, it cannot be repeated.
  • Task History:Tracks the history of when a task was completed, archived or marked as in progress.
  • User Settings: Settings specific to each user are stored in the backend database, encompassing their recently used artifacts, favorite items, and preferences regarding the layout of the team dashboard.

Secondary features

  • Manual: A lookup view for videos on how to use the application.
  • Status:Inform users about ongoing stuff.
  • Event: Set an event to change icons based on specific events(holiday, eastern).
  • Changelog: Changelog for the user to see about fixes and features.
  • Health: Health monitor for active features.

Developer Features

  • Issues: Create issues, when a problem occurs.
  • Error: Logging to analyze issues for admins.
  • Developer portal: Manage API tokens.
Instance Documentation

Stack

  • Golang
  • Redis
  • Angular@17
  • Docusaurus

WEKAN CLI

A CLI to view, create, delete board, list and cards. Cards can also be updated.

Stack

  • Rust

VOTERS VERDICT

Description

User can select on a range of dropdowns on a specific category. In this case we are voting on a beergarden. In the end, he can expect his own result and can compare against different voters.

Stack

  • Rocket
  • Tera
  • PostgreSQL (optional)
  • VanillaJS (packaged via webpack)
Test instance

BULLETIN BU

Description

The objective of this application is to enable users to effectively manage their shopping lists by marking essential items and crossing off completed tasks.

Features

  • Add shop to the app
  • Include individual items in a specific shop
  • Incorporate items into the overall app list
  • Designate item as required or importnt for a particular shop
  • Delete an item from a shop
  • Visual indicators for important (Orange), required (Green), and non-essential (Grey) items
  • Shops with the highest number of items are displayed first.
  • Items within each shop are organized based on their importance (important, required, not needed)
  • Each group of items is sorted by usage frequencey (how often an item was used)

Stack

Test instance (Github login required)