About me and the Lumpo story
My nickname is Lumpster, Lumpy, Lumporama, Lumpty Dumpty, Lumplestiltskin... the list goes on. Here's a story for you... I made Lumpo.ca. My journey to Lumpo started with a TRS-80 MC-10 that I had gotten as a present in elementary school. I learned to code in BASIC because that was the only option, and I made games from books and magazines. My first program was a Lotto 6/49 number generator; I was pretty proud of it. My dad eventually bought an 8086 clone, and it had 512KB!!! I remember when BBSes were big—2400 baud, baby. I don't actually even like computers that much, honestly; the joy-to-frustration ratio is debatable. I had a Geocities page, then it migrated to Yahoo!, and I upgraded to a Yahoo! Small Business account. I took the LumpyScams name as a tribute to 90s blog names, and the layout is inspired by when I used Notepad as my editor.
partyyourway dot com
I didn't really know the implications of what I was building and how bored people were. I just thought it was cool I had custom email addresses and a website. The funniest part is I modified a guestbook script to be a message board, letting people post anonymously. It was hilarious! I had no idea how many people would use it, and the flame wars started, eventually ending with me taking the whole thing down and girls crying. LMFAO! It literally became the "who's sleeping with whom" spot for my town. Bwahaha! Honestly, it's not my fault; I didn't know how the internet was going to be used. I thought people would say hello, not discuss their exes with the whole town and world.
Some books
Some books that aren't computer books that probably helped with my ability to read and interpret data objectively:
- The Freakonomics Book series by Steven Levitt and Stephen J. Dubner
- The Drunkard's Walk by Leonard Mlodinow
- How Not to Be Wrong by Jordan Ellenberg
- Naked Statistics by Charles Wheelan
Chapter nine in Leonard Mlodinow's book, The Drunkard's Walk, has some interesting insights into randomness and how the absence of it can indicate something is not correct. It would be a funny pivot to take Lumpy Scams and use the absence of expected variations in data to show there is a scam going on. Preventing scams is noble, and it interests me to think about how to use data to do that, and a good excuse to learn R and RStudio!
Lumpo future plans
None for now—it rests and I take a break! Maybe a small JSON file to save workout data, and PIP so you can leave the app to answer a text and then come back and the connection is still there and your data is still there. Maybe a metronome feature for cadence? Calories burned seems like an easy one to add but seems commercial and commonplace to me, and would require weight being entered. Entering MaxHR manually and having a MAF zone chart seems like a fit though.