You build up a library from your physical books by scanning them in or discover OpenLibrary books to read in app. Then as you mark books in your library as read, it starts building a rotation and recommending books you haven’t read recently. I’ve been using this nightly to track my son’s 1000 books before kindergarten for the last couple of months.
Currently, I’m working to get the app out on Google Play and adding multiple story time attendee support.
I've been working on an app to track my son's 1000 books before kindergarten. I've also added QOL features like barcode scanning for adding books to the library and creating a rotation based on the last time the book was read and whether I actually enjoy reading it. (The books I don't like make it through the rotation just with less frequency.)
This was an excuse to ship a mobile app for the first time and get familiar with supabase.
After these last few bugs are fixed, its ready for a semi-public TestFlight with our friends who have kids.
I’m really curious about your experience, what distro you used hyprland on, what dotfiles did damage to your install etc.
I just installed hyprland yesterday and outside of having to switch back to i3 once to install what they had set for a terminal in their default config(kitty), I haven’t had to leave again.
Asahi and hyde. "Nasty damage" isn't irreparable, but it would be significant effort to enumerate every small touch that affects defaults from other DEs and restore them. There is no "restore all touched configs to default" afaik. Since my asahi install was a lightly used toy anyway I just reinstalled. My next attempt will be with a VM that I make image backups of.
Location: St. Louis, MO
Remote: Hybrid or Remote (5 years of WFH)
Willing to relocate: No
Technologies: Java, Typescript, Javascript, Cassandra(NoSQL), AWS, Terraform, Python, Guice, Spring, SpringBoot, Angular, GWT, JUnit, Cypress, React, React Native, Docker, Kubernetes, Keycloak, Kafka, RabbitMQ
Résumé/CV: https://philljanowski.com/PhillJanowskiResume.pdf
Email: philajan <at] pm <dot] me
I'm Phill, a backend leaning, full stack software engineer with 7.5 years of experience building enterprise SaaS solutions. I have extensive experience planning and leading implementation of large scale features from cloud infrastructure to user interfaces. I have a strong background in software stability improvements, algorithm optimization, and K8s resource management using OpenTelemetry, Grafana Tempo, and Splunk. In my free time, I build software including GreekUtils[1], a Greek Life centric, cloud based CRM.
I'm capable of learning anything when met with the challenge. I'm looking for a full time position where I can contribute to meaningful projects while learning new technologies and methodologies in software engineering.
Location: St. Louis, Missouri, USA
Remote: Yes
Willing to relocate: No
Technologies: Java, Typescript, Javascript, Cassandra(NoSQL), Terraform, Python, Guice, Spring, SpringBoot, Angular, GWT, JUnit, Cypress, React, React Native, Docker, Kubernetes, AWS, Keycloak, Kafka, RabbitMQ
Résumé/CV: https://philljanowski.com/PhillJanowskiResume.pdf
Email: philajan <at> pm <.> me
I'm Phill, a backend leaning, full stack software engineer with 7 years of experience building enterprise SaaS solutions. I have extensive experience planning and leading implementation of large scale features from cloud infrastructure to user interfaces. I have a strong background in software stability improvements, algorithm optimization, and K8s resource management using OpenTelemetry, Grafana Tempo, and Splunk. In my free time, I build software including GreekUtils[1], a Greek Life centric, cloud based CRM.
I'm capable of learning anything when met with the challenge. I'm looking for a full time position where I can contribute to meaningful projects while learning new technologies and methodologies in software engineering.
I'm on my fraternity's alumni board. The chapter has been using spread sheets for everything since I was an active member. Every year, information about recruitment gets lost in the shuffle between officers.
I've been working on a bespoke CRM for them to prevent the spreadsheet rot while providing some helpful visualization and making their data easier to use in the feature. The goal is to make the entire recruitment process self documenting.
Its slowly evolving into a way to keep track of actives and alumni, as well as ways for actives to interact with the recruitment process.
