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
The #Editorial about editing is scheduled to go live on #1331blog, and now I’m exhausted and should go to sleep. That’s what I get for leaving it to the last minute. Next stop is probably a new #TuesdayTunes. I suppose I could also keep working on #ProjectBS as well, it’s only been about 9 months since I had planned to start posting it…
Oh yeah, I never mentioned that, that’s a long-running, top secret project… except for the people who know about it…
It’s late, and I haven’t slept much all week, so I’ll keep this one brief. I intended to fix one little bug in the #midnightmurderparty #reader and then take the night off since I’ve burnt myself out really hard this week. But instead of just fixing one bug (which I did), I ended up finding a ton more. Too many to handle tonight, and almost all cross-browser issues that have no simple solution. Ugh.
I did manage to close a few issues I didn’t expect to while climbing down the rabbit hole, but I’ve been toiling with IE’s interpretation of DOM element placement in CSS column layouts for hours now with very little progress. Looks like I’m calling it quits here for the night. This is gonna bug me, though.
Have made incredible process with the #Heroic book. Second chapter already reads incredibly well to my ears. Writing the book at this stage is perfect, as it’s really affirmed that I have a viable product budding into existence.
Also had a revelation on how I’m going to simplify the Storyteller tools. Instead of providing different tools for plots, areas, characters, monsters and more - I’ll combine them all into one. That takes the prize as my best shower thought this month.
Yesterday I had a call with a lady from a US food delivery startup who wanted to talk about licensing and building on #exist to make a tracking and reward platform for their customers. I’m cautiously optimistic — they want a fair bit in a short time, and they seem like they don’t want to pay a lot, but I think Exist’s a decent fit for it so perhaps it’ll work out. It would be nice if Exist could make us a lot of extra income in this way given the consumer approach is a slow burn. We’ll see I guess.
Today I deployed the food tracking additions to Exist and started testing them with @belle. Maybe some issues to sort out, but once that’s done we can roll it all out for everyone.
Hello Littlelogs! I’ve been sick with a nasty cold for a while so I haven’t had anything to log, but today I got back to work (a bit). I wrote some #research #sketchnotes for a #client #content article, got back on top of my inbox which had been piling up, and sent a new version of #exist for #ios with a bug fix in it to the App Store for review.
Finished writing the #Editorial on editing for #1331blog tonight. There’s marginalia. There are sentences marked for revision. Basically there’s still work to be done, but all of that will be done in the page-to-screen transcription process. Theoretically, it’ll be posted on Friday. If not, then Saturday, I suppose. Then all attention can be turned toward other endeavors, both blog related and otherwise.
Tonight turned out to be more of a cleanup night than a dev night.
- Cleaned up all the #midnightmurderparty todos and consolidated them as issues and milestones on #github
- And, as a bonus, washed the dishes, unpacked from vacation (finally), and tidied up my apartment
Tonight was not as crazy as last night, as described in my last post, but it was still quite a crazy #midnightmurderparty dev night. Events worth noting:
- Upgraded my internal network by changing by Bell router into a bridge and hooking up a new router I picked up yesterday. Down with 2.4GHz WiFi congestion, 5GHz AC or bust!
- Fixed the Raspberry Pi staging server, which was completely out of commision with the aforementioned network changes.
- Stripped out all environment variable usage in favour of a secrets YAML file.
- Upgraded our DigitalOcean droplet to 1GB of RAM. Hot deploys work!!!
Basically: physical infrastructure, virtualized infrastructure, and code infrastructure.
The last few days have been busy with a bunch of micro tasks. I’ve done a lot, but hardly anything I can point at and say to myself, “look at what I achieved.” For example, reviewed a bunch of UI text for warehouse, added logging configuration to one of my bots, and set up backups for my Raspberry Pi. It’s good to be knocking things off my to do list, but it’s frustrating to have so much attention residue.
Last night, @rhitakorrr and I jumped on a voice chat so we could discuss his monstrous build system changes for the frontend of #midnightmurderparty and then deploy it. The discussion went well. Our build system is now super powerful and will prevent browser caching, which is great considering how JS heavy the site is.
We decided to profile the RAM usage as we’ve run into our asset build process being killed before and assumed we may be running OOM since we only have a 512M box and we’re running hot deploys (server still running). Well, suspicions confirmed, we are indeed running OOM during hot deploys. Total usable RAM is 489M. Number:
- Idle server - 88M
- Deploy building - 250M
- Fully running - 355M
Simple math: 489M (total) - 355M (running) - 250M (deploy) = -116M. We end up with -116M of RAM during a hot deploy. Thus, we’ll be upgrading our droplet on DigitalOcean to the $10/month box, which has a full 1GB of RAM. Oh, also, #Ruby Sinatra routing is garbage. Give me abstract named routes!
Sleep is for the weak. Time to do some (very) late night #1331blog work. Looking to post the editing #Editorial by Thursday or so. #TuesdayTunes can wait, there’s a whole week for it. Or two. Or three. Or whenever, I’ve already gone long past when I’d anticipated posting it.
Here, have a preview, I’m feeling generous:
Saying “I like this” to an author for whom you’re editing does approximately nothing.
I like that because saying “for whom” feels fancy and important. It also feels a little weird, but it was the clearest way to phrase the sentence. I originally had:
Telling a writer you’re editing for “I like this” does approximately nothing.
Which is technically grammatically correct, but also ambiguous and awkward, since it separates the act of “telling,” and the thing you’re saying. It’s not as clean and clear as if you were to say:
Telling Mary “I like this” does approximately nothing.
Things like this are the exact reason I’m writing this post in the first place.
- Needing to dynamically create script tags on the page based on config (which leads to all sorts of script loading order mayhem)
- Needing to pass static data around in the #Elm model
- Build system upgrade
- Now injects values from config file directly into the source
- Allows specifying
--devin terminal to run in dev mode, prod otherwise
- Dev and prod mode both have their own values in the config file
- If running in prod, the build script will remove console logs, debuggers, alerts, etc.
Took a break from my logging / journalling in various places lately to focus in on my work itself. It was a nice change but I’d like to return to logging if possible.
Some things achieved lately
- Had several iterations of #Relate Things are slowly improving with feedback and internal use
- Started writing the official rulebook for #Heroic In a week or two I may complete a first draft
- Finished drafts of all the Storyteller sheets for #Heroic , they now need to be extensively tested on a weekly basis, perhaps until release
Released the weekly email feature for #larder tonight. Each week you’ll get a report on any of your starred #github repos that have had a release in the last week, along with the release notes. I hope it’ll be pretty handy! You can also use it as a “read later” feature, if you bookmark things to come back and read — users can choose to include a list of all bookmarks added for the week, per folder.
I emailed everyone with github connected, even users with expired trials, and got one happy tweet and one upgrade out of it so far which is a good start :)
It’s been on the HN homepage most of today and it even reached as high as spot 8 briefly. The site is still getting plenty of traffic so I’ll have to watch it a little overnight.
As a side note: Daniel, one of the HN moderators, did send me an email when I first posted the link to help me make it look less like spam/a product promotion. This was the first time HN has done this for me and it was really good of them.