Today I launched the Larder API docs and the related management bits on the site. Yay! This was the most popular request on the roadmap, although this time around I’m under no illusions that it’ll make a big difference to signups. It’s just another feature that rounds out what we offer and shows we’re serious. If some people then use it to write clients or integrations or whatever, all the better.
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
Phew! It’s been a crazy two days at #playgroundscon. It was my first ever conference, so I wasn’t sure what to expect. Overall it turned out quite well. I met quite a few people, learned a lot, and got lots of inspiration to try new things and improve my code. The organisers worked really hard on diversity and inclusion, which showed. It was great to feel part of the community, since I haven’t had that much in the past. Now I need all weekend to recover!
Editing is now underway, I’m using Google docs with revision history. I need to start pulling the edited google docs back into my local files.
Also had a nice email from a programming teacher and I’ve asked if I can use some of text of that email on the website (which I never feel super-comfortable about doing but most people are more than happy to oblige). I keep all my “endorsement” quotes in a file but I’m only using a few on the website.
A/B testing news: The warning about an imminent price increase seems to reduce click through. Possibly framing or people feel they’re being pressured in a negative way - something to tweak!
Finished a first pass on my current article. It needs a few review passes but hopeful it will go up this weekend.
Pulled copies of 2016’s web access logs and current database from production’s webserver, cut out sample/example data to share with a possible vendor. Ran 2014, 2015, and 2016 web access logs through my analytics, created reports.
Very frustrated: generally same quantity of visitors monthly over the years, but a huge decline in pages-viewed per-visitor when company switched away from my own custom #webapp & design to some outside designer house with their code the company spend a ton of money on. 15 pages per visitor down to 7 – My web app encouraged exploring, comparing, discovering. New version’s “SEO improvements” clearly didn’t make a difference in drawing in visitors, I was already there on my original effort.
Worked on: #ProductMarketing ideas, project timeline for the knowledge base redesign, reviewed slides for upcoming presentation and webinar, shopped around for simple Gantt chart apps (Chart Master might work)
Considering: how often to conduct periodic reviews of progress during a project
Last night I went to an event as part of #playgroundscon here in Melbourne. It was a screening of the documentary CODE: Debugging the Gender Gap. The film was pretty good, and it’s an important topic, but now that I’m up and getting ready for a full day of conference on a little over 5 hours sleep I’m kind of regretting going!
Yesterday: Hosted two different Michael Jackson groups/shows #rehearsals, long technical/sales meeting to outsource IT for when I leave Vegas, setup & ran a remote audition over Skype from my #stage. Sourced & curated a 6+ hour long custom playlist of Australian music, so much #didgeridoo, which reminded me of #hellocode.co and #littlelogs.
I finished the #larder #api #docs today! It’s so fiddly to include all the code samples and stuff, but now it’s done. My next steps are to build the UI for developers to create and manage their client apps in Larder, and make sure the oauth “authorise” page is all styled nicely, then that’ll be done.
In other news, I added the #changemap search field autocomplete suggestions to the “add a new suggestion” form last week, so you have to click “no, my suggestion isn’t any of these” if there are matches. And since then we’ve had zero new suggestions. It definitely works, I tried it, but I guess nobody has a new idea that isn’t a duplicate. Success? 🤔
So far this week:
- Answering emails (still behind on this)
- Finally contacted a freelance editor to go through the book
- Continued writing my next article for the site
- Working on a freelance project
I definitely don’t feel as focused as when as I was working on the book, but I’m happy with where I’m heading at the moment.
I’m below my target for sales (currently 39 for this year) but it’s a nice baseline. I’m hoping to boost this later, with ads.
Worked on: More #UserInterviews, compiling answers and synthesizing actionable insights.
Challenges: Looking for a tool to help manage (version) content in a knowledge base when product updates occur or other external changes take place.
Considering: Creating a Splunk Search Processing Language cheat sheet tool in Google Sheets with drop down menus (#Data Validation > list of items) so teammates and I could more easily craft search strings.
I’ve spent the last few days working on an engine for text-based games in #Elm, the goal being to use this engine to code the #MidnightMurderParty interactive segments. Turns out, modeling a game engine in a purely functional, strictly typed language is tricky. Since game objects have different properties and behaviors, modeling them as the same type (so they can be stored in a
Dict) isn’t really straightforward.
After some research, I decided to go with an Entity-Component-System (ECS) approach, which has been a challenge as the first time I’d heard about such a pattern was on Friday. Since then, I’ve written some terrible code, refactored many times, and only now have something that looks promising enough to move forward with. There’s still a lot to figure out (cross-entity/component messaging, for example), but at least now I have an idea of how this might work.
Worked on: Completed two excellent #UserInterviews, full of insights. Open ended questions and quiet on my part drives more thinking out loud from the interviewees.
Resources: Highly recommended reading: Lean Customer Development
Challenges: Time lost waiting for interviewees who are late or do not show up at all during scheduled times.
Not a lot was done today. I slept badly so gave myself permission to have an easy day. However, in the evening I managed to get some more done on the #larder #api docs I’m writing. Thankfully some of it can be copied from the Exist docs. There’s still a lot to do though. Literally a thankless task, but I want to write high quality docs so the barrier to people making a thing with the API is as low as it can be.
Was weekly Resolution Number One a success?! Hahahahahaha no!
- Sun: 8:18
- Mon: 8:07
- Tue: 8:09
- Wed: 6:37 (strike one)
- Thu: 5:17 (strike two)
- Fri: 2:23 (strike very much three)
- Sat: 4:31 (strike four)
The passing score was 6. I scored 3.
This week’s goal
I think I might learn a lesson from this week’s and go for something achievable and improvable. So here’s the goal.
Increase the number of commuting journeys made by bike.
So, the max possible is 10 (out and back 5 times a week).
My current best score this year is 0.
Today didn’t quite go as planned. Had some great accomplishments nonethless.
- Organized my Notion workbook to better serve my current needs.
- Walked around and planned a running route.
- Had a get-together with old friends and family.
- Cleaned the house.
- Did some big edits on #heroic (~4 hours worth). Between what I accomplished in early January and today, I’m almost ready to test it with a group. No more isolated tests with incomplete content, the real deal. 😀