Made good progress today on #exist #manualtracking — this time, making the necessary changes to the web interface. Back on the productivity wagon! A little more to do so users can edit and manage custom tags from the web, then some better custom entry UX in the Android app, then beta testing time.
Today I spent the day on #changemap and got comment and vote adding and deleting done along with nailing down some styling. Inching closer to having it ready for our own use.
Got a lot done today on #manualtracking for #exist. The generic logic for turning a bunch of events per day into a single value (a total, or an average, or whatever) is all done. Next will be lots of testing for all the various event types, then I’ll add the new attributes we decided on. Once that’s all done, I guess it’ll be time to start working on the web interface for actual manual tracking. Making good progress 👍
Got some more #manualtracking stuff done for #exist today. Sorted out the shape of the metadata for all the current events, and picked out some new attributes we’ll add so there’s more to track manually. This includes some more affect measures, like energy levels, anxiety, etc. Hope people will dig that. Also adding a 1-10 pain scale attribute for some basic pain tracking for the chronic pain folks. A couple of people have asked for that (everyone who emails us these days always says “I can’t BELIEVE you haven’t added MY SPECIFIC THING already!!!” but they’re always different things) and it isn’t hard to help them out by adding one extra attribute.
Also tonight I got social login working for my secret project (gonna have to name and tag it soon!) although the docs for
python-social-auth are very poor and confusing and it might’ve been quicker to just write it myself.
Yesterday I made really good progress on #exist #manualtracking. I can now submit certain events via the API and have them validated (via
jsonschema) and saved to the database. Yeah! I think next I need to finalise all the event types and their schemas. Then I’ll work on the logic that chooses how to turn them into one value per day (eg. sum them, last value, biggest value, etc).
Today I was also very productive, but on my secret new project instead. Productive procrastination baby. I got the db models set up and started rendering a complete view of a “map”. It’s all coming together.
I’m still attempting to make progress on #manualtracking for #exist, but other things keep getting in the way. Today I fruitlessly tried to track down a weird timezone bug a user is experiencing, and fixed a few other little issues that have come up since the upgrade. Then after dinner I finally got some more manual tracking changes done.
Also an article I was interviewed for was published today, but I’m not impressed with it so I can’t be bothered linking to it. Oh well. Hope it sends us some signups anyway.
Well, my #exist upgrade is complete. The site was offline for a little over an hour, a bit longer than I intended thanks to some things I missed in my pre-flight checklist and which subsequently made things very confusing, but not too bad really. I had a few little bugs to fix afterwards that I’d missed earlier, but it all seems good now. Onward to new event streams and #manualtracking!
Sort of related, I’d definitely have fewer issues in a scenario like this with a strongly typed language. I think upgrading to #python 3 would be at least as stressful as this upgrade has been, but it would mean I could take advantage of type hinting. Something to ponder.
My work on upgrading #exist from #django 1.6 to 1.10 is actually going okay. It’s both a bigger job than I anticipated, thanks to a bunch of third party dependencies that need to be upgraded too and have breaking changes (Django Rest Framework being the biggest) and smaller, because I thought it’d take me longer to get to this point. I can render all my views again! Next step is switching from South to Django’s built-in migrations, then making sure the API works, and then maybe the upgrade will be complete.
In the meantime @belle and I came up with a bunch of easy, useful changes that I think would help explain users’ data better, but I must put them off and power through adding #manualtracking. It’s always the way.
This week I’m finally, really, seriously getting into adding #manualtracking to #exist. This is a big architectural change, and due to various requirements, will necessitate upgrading a lot of dependencies with all of the massive screwing around that’ll entail. I started setting up a new cloned copy of the codebase in a new virtual env, and started working through all of the things that are now broken after upgrading dependencies, but there’s still a lot to do before I can write any new code. Fun times.
Deployed the #exist graph additions on the server. So much hassle to get cairo installed so I can render svg to png, but all sorted. Soon @belle will have the food tracking additions done for the iOS app and we can launch that too, but in the meantime I guess it’s time to start work in earnest on #manualtracking. See you again in 6 months!
Somehow I’ve picked up a cold again. I felt very sluggish today and didn’t get much done, but improved a little in the afternoon. Tonight I got the basics of editing and deleting working for #larder #android, so it’s almost a full CRUD client now. Just noticed we got another yearly subscription too, which is fantastic. I really think at this stage what Larder needs to grow is more people seeing it, rather than more features. Hopefully some interesting interviews on the blog will help that.
#exist-wise I am tossing up between trying to do some stuff for the weekly email this week (like including some graphs), and getting stuck into the architectural changes for #manualtracking. I think probably the email could benefit from some more useful trend info, but I don’t have a clear idea of what exactly so there’s a chance I could waste days trying various things and have nothing to show for it at the end.
Anyway, hopefully I feel a bit better tomorrow so I can get something done, regardless of what I pick!