So I’ve finally been doing a little more work for #1331blog rather than just tossing up a #1331SotW and not doing anything else. I’m finishing up the most recent #TuesdayTunes so that I can post it this week, and then I’m writing this week’s SotW post, which isn’t part of my backlog, surprisingly. Typoattack and I have already figured out what we’re doing for the holiday season, and I’ve already got a guest author locked in for that. Next thing on the list is figuring out a Song of the Week for Halloween.
What's this then?
It's like keeping a journal of your work progress, but in public.
It's somewhere to talk shop and be part of a community of people making and learning cool things.
As a two-person startup Hello Code, we wanted somewhere to share what we're working on in public. This gives us accountability to ourselves and to our users. As a small team, sharing our work ideas, struggles and daily efforts also helps us feel supported and part of a community. It's the missing ingredient that gives us a place to share what we learn, and talk shop.
Also, we support Markdown formatting for posts, meaning you can include things like blockquotes, images, and code snippets.
Does this sound like your kind of thing?
Recent public logs
Ah, what the hell. I’m outing our next project for the sake of having a tag to track it. There’s not many of us here anyway so it’s not a big deal. So our new idea is called #changemap. It’s a tool for transparent businesses to manage their public product roadmaps and changelogs (yeah, hence the super-clever name). Mostly people seem to use Trello for this task at the moment, but they take suggestions via email, or UserVoice, or GitHub issues, or comments on a specific card — it’s a huge kludge because Trello isn’t made for this purpose. Changemap tries to rectify that by handling new suggestions, turning them into tasks that then move through the system, and the inevitable changelog of everything that gets completed. We’ll be using it for our own products for a while, then open it up to other businesses (that’s right, B2B baby) once it’s solid.
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 👍
I’ve been refreshing the Google Store orders page all day, waiting for my new Pixel phone to ship! It’s finally shipped now, so I’m refreshing the parcel tracking page instead 😏
In other news, I did quite the catch-up today on #client #content work. I drafted two of my three articles due this week, and followed up all my client emails. Looks like with another productive day tomorrow I’ll have the weekend free for #exist for #ios work.
Been working on some designs for my next project, #lybrary. It’ll be a totally open source web app but is being used for a #uni project. Yesterday and today I’ve been doing some mockups in Sketch and I’m actually really happy with how they’ve turned out. I’m nothing close to a designer but I feel these are quite simple and pleasing to the eye. They also convey the content quite well and centre the important bits.
I’m hoping to get a blog post up about it soon!
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.
Feeling pretty good about secret project progress this weekend. Still a lot to go, and I’d better get back to real work this week, but it’s inching closer to being usable for Hello Code, at least. 👍
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.
This week has been going much better in terms of my mood and motivation. I did lots of small tasks, emails, etc. on Monday morning and spent Monday afternoon doing #research #sketchnotes for a #client #content article.
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.
Been a while since I posted a log. I haven’t been doing much other than building a backlog of #1331SotW posts. At the moment I’m trying to tie posts into something of note that is happening or has happened that week. Lucky for me, Christmas and New Year’s are both Sundays this year. The latter is written, the former is up in the air still. I have two written for other weeks in December, which I think just about covers that month, actually. Thanksgiving is planned, but not yet written, and Halloween is up in the air. I may not be working on much else but at least keeping up with the SotW series keeps #1331blog active. Going to start thinking about soliciting guest posts for the series soon, so that it gets more diverse and isn’t just my favorite songs.
HUGE day of #exist for #ios today. I made a new settings screen to handle all the new #healthkit data I’ve been adding, made some changes to how I get HealthKit data to make it more generic, fixed some bugs, and added a bunch of new constants to replace hard-coded values.
I also sent a new build of the #location branch to #TestFlight for beta testers, and took up a big chunk of @josh’s day trying to figure out why I kept getting intermittent 412 errors from the Exist server. (Turned out to be an issue with the default cache policy of