Praeteritum Devlog 0

Praeteritum :: Devlog 0

You’ve probably seen the blog post the Hackathon 2023. If not, don’t worry, because we’ll cover all the important parts here anyway.

At the hackathon we were part of some time in 2023, we chose a theme that involved creating a web application to streamline retrospectives, either as part of AGILE or as a general tool to gather feedback from clients, students, and others.

While we did have a „working“ prototype that allowed us to authenticate, add, and view feedback on a single board, the backend codebase was a mess, and the frontend’s CSS was different for every route. As a result, although it was functional, we didn’t want to continue maintaining the codebase.

Where to from here

Since the codebase is a mess rivaling only that of Project Sapphire, we archived our progress in a legacy branch, locked it, and have abandoned it to never be committed to or merged ever again.

We have decided to undertake a complete rewrite of Praeteritum, starting with project setup. As of writing this blog post, we are reorganizing tasks on our kanban board.

One of the issues we encountered during the hackathon was that tasks were either too generic or overly large. This led to the developer assigned to the task not being sure about what to do. Another issue was that our codebase had almost every possible naming convention, and, lastly, although we did use branches, we could utilize them more effectively this time.

We will post new devlogs as the project progresses. If you are interested in observing this endeavor or would like to contribute your self, checkout the GitHub repository at ProjNull/Praeteritum