seporaitis / lhl

Linux Ham Log - an attempt to write modern terminal linux ham radio logging application from scratch

Hi there 👋

My name is Julius Seporaitis. At the moment I hover between being head of engineering and being senior software engineer. My areas of professional interest are - DevOps / Infrastructure / Developer Tools / Developer Productivity / Backend. I recently started documenting my ideas and experience in a blog. Some of my popular posts:

• Lessons From Two Years Of Depression - on mental health;
• Build System At Genus AI - on simple, but highly efficient continuous integration setup, accessible for all;
• How To Make A Custom Service Accessible Through boto3 - a prototype of a very unconventional, but cool, boto3 usage;
• Bottom Up Problem Solving - Part I, Part II - how to approach problem solving incrementally;
• Large Scale Refactoring With PyBowler - a walkthrough on changing code - with code.

You are more than welcome to get in touch, if you'd like to share something cool, get feedback, would like advice, or informal mentorship in software engineering career. Do that through LinkedIn and mention this page in your message.

lhl's Issues

Save QSO data to a file

There are a couple of format options here:

• Cabrillo - seems to be oriented towards contests and highly customizable.
• Amateur Data Interchange Format (ADIF) - seems to cover A LOT of scenarios and is more general purpose.

However, ADIF has a lot of https://adif.org/309/ADIF_309.htm#Enumerations that, in case I decide to, say, allow import-and-use-of existing ADIF logs, would just blow up scope for me.

Since I do not have enough experience with qso loggers at all, I am not yet certain ADIF is the de-facto standard for storing logs, as opposed to just using it as data interchange format (e.g. I export it from one app to import to another). From my experience in general software engineering parsing XML file of a significant size 10-100Mb would increase app bootstrap time, even if I need only the final few records to show in the interface.

Hence, I am leaning towards SQLite or similar(?). It has the benefits:

• popular and stable format that has a lot of tools to inspect its contents
• is a library and not another software package/service to install and handle (e.g. MySQL/MariaDB/PostgreSQL)
• would simplify some tasks (e.g. "get me 10 most recent records" to show in the UI)

Some potential caveats:

• SQLite does not support concurrent writes
• managing schema changes

Add support for scripting internal events

The purpose of this is to, for instance, do custom actions when something happens (e.g. send qso data somewhere when a new qso is added).

For example have embedded Python.

Come up with a normal name for this project

Hog is ham log. LyLog is LY Log. None of them are great names.

Some keywords for consideration:

• Ham(Radio)
• Amateur (Radio)
• CQ
• QSO
• Book
• Backup
• Storage
• Database

Add form for a basic QSO information

A form should take in:

• timestamp (date + time)
• mode
• band
• callsign
• rst sent
• rst rcvd