hist-prototype VS Manji

I have 2 projects that I'm looking to eventually adapt into a database backend that's API compatible with RocksDB (with enhancements!). The first of which is a Extendible Hashing Implementation in Rust (it was my first attempt at Rust, so it's kinda messy): https://github.com/chiefnoah/MehDB

It achieves very promising performance for u64 sized types (which will eventually be an offset into a log).

The other is a similar concept using modified B+Trees that have subtrees for all writes to a record: https://github.com/chiefnoah/hist-prototype

This one is implemented in Python for fast iteration, as I realized I wasn't happy with how fast I could iterate with Rust. This one is, IMO, a more complete approach towards full historical query-capable systems. I'm slowly chipping away at it, though I haven't had progress lately. I spend no real money to host them, just the code, though I'm certain I've shortened the life of my NVMe drives due to writing and rewriting large files for testing.

A hacker news client I made: https://github.com/Livinglist/Hacki

Also a kanji learning app if anybody is interested: https://github.com/Livinglist/Manji

depends on what kinda specialization you are interested in, at least for me it’s mobile app development. I have been making apps since college, I was interested in Japanese language so I made a kanji learning app [0], then because I’m a bodybuilder, I made a workout log app [1], recently because I started reading hacker news, I made a Hacker News reader [2]. I learnt a lot from the process, from architecture, design pattern to code quality control. I would say learning is the key, usefulness is secondary.

[0] https://github.com/Livinglist/Manji

I wrote a app for learning Japanese kanji when I was in college learning Flutter, I didn’t have any experience working on real world projects and barely have any knowledge of design pattern, architecture, clean code etc… I was young and naive, but had passion, so I started collecting data using scrappers I wrote in Python, organized them into a SQLite database, put a lot of example sentences and vocabulary on Firebase, then made an app using Flutter. I gradually added more features into the app after I released the first version, things like handwritten kanji recognition using Tensorflow lite and image text extraction using Google OCR api… I learned a lot, and by a lot, I mean a lot lot of stuff from making this app. The app is functioning just fine but the code is ugly as hell…for example attributes in data model classes are not final, doesn’t support dependency injection, etc….

After I started working, I learned a lot about how to write clean code and I always wanted to refactor/rewrite the whole app which gonna take a lot of effort and time of course. But every time I sat down, opened the old codebase, I hesitated, thought about it and told myself that it wasn’t worth it then continued my life.

do you have any personal project you always wanted to refactor/rewrite but still haven’t done or probably never will do so?

if you are interested, you can come see and compare the code of the kanji app and a new app I wrote recently:

https://github.com/Livinglist/Manji

Same here, I used to develop apps for Windows Phone back in 2014... then after I got into college, there was UWP, I made Japanese dictionary using it: [Kanjirin](https://www.microsoft.com/en-us/p/kanjirin/9pfwxjr41x4d?activetab=pivot:overviewtab), then I started learning Flutter, Dart was really easy to pick up, syntax is quite similar to C#, and I think what you need to practice on is state management and learn about widgets and useful thrid party packages. I made many mistakes when I was making my first flutter app - [Manji](https://github.com/Livinglist/Manji), but at least it got me my first Flutter related job. Here is my latest app using best practices if you are interested: [Hacki - Hacker News reader](https://github.com/Livinglist/Hacki)