littlelogs

Keep a social journal of your work progress as you make and learn things.

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?

Sign up


Recent public logs

Kraahkan
Kraahkan

A short update on what I’ve been working on lately

  • Paused development on #Chronicle as it’s going to take more time than I have savings to burn at this point. Now focusing on developing smaller apps, aiming to have one done by the end of this month.
  • Brought #Heroic to a fully playable private alpha state. That’s finally happening next week.
  • Been puttering away on #music the odd night here and there. Finally, have the equipment to start recording and publishing little bits each night. Going to try that tonight if my dentist appointment doesn’t leave me ruined.
  • In personal news, starting a #keto diet. Doing the shopping in an hour, should be fun!
rhitakorrr
rhitakorrr

Haven’t logged in a while since this site has felt like it’s been slowly coming to a halt for the last month or two, but this is a log that @larouxn and I have been waiting to write since we joined this site almost a year ago. Here goes…

🎉 🎉 🎉 #MidnightMurderParty development is done! 🎉 🎉 🎉

I fixed the last (known) major bug last night a little before 10:00pm, just in time to meet @larouxn’s 5-week deadline. There’s plenty more to do—video editing, music, promo, social media, content creation…the list goes on—but development is done after more than a year and a half of hard work, long nights, and ridiculous cross-browser hacks, and I couldn’t be more excited to share it with this community! Thanks for being so awesome, everyone! 😀

josh
josh

FYI I’ve turned off nightly emails for anyone still with that option turned on. Still debating what to do about #littlelogs overall, we could leave it going if people really wanted to keep using it — it’s not a hassle to host it or anything — it just seems pretty pointless if it’s only 2 or 3 people other than us.

rushmayo
rushmayo

Insurance and/or workers compensation should include spouses with debilitating chronic incurable illnesses. It sure stops you from working too. But some good attorney would say that it’s your choice to take care of yourself and not work. And that attorney probably does not have a life or children or property or a spouse. #WorkFromHomeProblems

josh
josh

Hey littlelogs. Sorry we haven’t been around lately. @belle and I have been debating shutting #littlelogs down, actually, because it was only ever a side project and it’s clear that it’s not of use to many people. We sort of half-heartedly meant for our logs to be useful to our users in seeing what we’re working on, but in practice I’m not sure many of them ever look, which is fair enough. We’re going to try adding the ability to write progress logs to our public roadmap thing https://changemap.co, where users will be more likely to see them, which means there’s little need to keep this around. Nothing certain yet, of course, but that’s why we’ve not been diligently logging — doesn’t feel like much point any more.

You’re all still lovely though. Don’t take it personally.

rhitakorrr
rhitakorrr

Tonight I started working on the #MidnightMurderParty reader again. It was a bit of a rocky start as an error in the back-end prevented me from testing my front-end code. I ended up debugging #Ruby—fun since I don’t really know Ruby—and after some fumbling and frustration, fixed the problem.

Interactive links are now supported. I plan to add one more feature tomorrow, and then the reader is done aside from testing and small enhancements.

larouxn
larouxn

おはよう、心配しない、これは短いログだけ。

(Good morning, don’t worry, this is only a short log.)

Just wanted to stop by to mention that @rhitakorrr and I merged the new PureScript editor into master and deployed to both #MidnightMurderParty staging and production last night. Ran into a strange Postgres vs SQLite difference based bug and had to drop databases and what not due to some model refactoring but overall it was a pretty straightforward deploy considering the change was +2000 lines. Anyway, this our new language breakdown (20.3% PureScript, Elm is 52.2%, Ruby 5.3%): languages

じゃね (See ya later) ✌️

rhitakorrr
rhitakorrr

Finished the #MidnightMurderParty editor with @larouxn tonight. Google login is in place with session-based auth for our endpoints—way better than sending a raw string! Also fixed the automatic release date generation, which was buggy and slow for no good reason. Still no luck getting the backend auth to work on my Windows machine, unfortunately. Lost a couple hours installing certificates, updating gems, uninstalling and reinstalling #Ruby, etc. to no avail. Oh well.

larouxn
larouxn

こんばんは, just a quick update here from the #MidnightMurderParty backend team, aka, me. We (@rhitakorrr and I) have successfully setup frontend to backend Google auth validation with built-in validation that it’s either @rhitakorrr or I logging in as well as session storage to store said auth status which we then use for our authenticated endpoints that we hit up after login. No more server side yaml key and (unencrypted) browser cookie garbage for us! 🙃

The backend is done, for now and thus, I will move on to writing MMP animation soundtrack v1.1 next, taking into account @rhitakorrr’s awesome feedback. 🎹

rhitakorrr
rhitakorrr

As it turns out, my CSS styles were bad but not beyond reuse. Finished the UI and worked with @larouxn on authentication. Login verification on the server with a Google id_token now works—well, on Nick’s machine at least. Apparently my Windows machine is missing some certificate, so I have to comment out the auth code locally still. But that’s a problem for another night.

For tonight, I’m happy to say that the #MidnightMurderParty editor front-end is in perfectly usable shape, leaving a few days to work on auth with Nick, tweak some things, and play some Dark Souls III before I have to get to work on the reader again.

rhitakorrr
rhitakorrr

I was supposed to finish the #MidnightMurderParty editor UI tonight, but I got distracted and spent 5 hours making a type system for my Google API FFI. The API code now has two main types, Gapi and AccessToken.

These types then contain (sort of) other types. For example, an access token retrieved with the “drive.readonly” and “email” scopes will have the type AccessToken (driveReadOnly :: DriveReadOnlyScope, email :: EmailScope) where DriveReadOnlyScope and EmailScope are also types. This way I can prevent passing an access token without the right set of scopes into an API call on the type level; it becomes a compiler error instead of a runtime error!

The Gapi type tracks functions involving Google’s gapi variable such that the compiler will stop me from using features I haven’t set up yet. A completely set up Gapi type for this app looks like: Gapi (auth2 :: Auth2 Ready, filepicker :: GooglePickerObject).

Way cooler than a UI. 😁

rhitakorrr
rhitakorrr

Four hours of messy CSS and long compile times later, I’ve done the entire UI for the ChapterSync module of the #MidnightMurderParty editor. One more module to go, but it’s probably the one that will need the most complicated styles. Hoping I can reuse some of the styles I made tonight, but the CSS is such a mess that a lot of it probably isn’t easily reusable. That’s the price of working fast, I guess. Can’t wait to be done with UI, though; I want to get back to stuff that isn’t awful!

larouxn
larouxn

👋 こんにちは littlelogs 🌊. As @rhitakorrr stated in his last log, I gave a talk of #MidnightMurderParty this past week. Last Thursday I broke down, to the best of my ability and memory, the history and learnings of MMP to a sizeable group of Shopify employees, both in-house and over the livestream. presentation_slide

Also, we’re planning on finishing up MMP, everything except story, within the next month or so, woo!

rhitakorrr
rhitakorrr

After a weekend gaming binge (my brother got me Dark Souls III, ‘nuff said), I just got back to coding. Last week, @larouxn gave a dev talk at his job about #MidnightMurderParty and what we’ve learned from doing this project. He sent me the slide deck, and when I got to the last slides, I saw it said that we planned to finish by June. I messaged him and said, “We planned what?” First I’d heard of it.

But I’m all for deadlines, so mid-late June is our goal. We had a meeting to roughly plan out how to tackle it. Week 1: Finish editor. Week 2: Update reader. Week 3: Integrations & testing. Week 4/5: Extra features, more testing, bug fixing, and pad time for whatever we horribly underestimated the complexity of.

I was tempted to play Dark Souls tonight, honestly, but managed to not get distracted. Good thing, too, because adding all the functionality I wanted to the editor’s main dashboard took all night.

joseph
joseph

Now that #school is finished for the summer and it’s the weekend, I’ll be working on the #website a lot. In fact, it’s currently down for construction right now! It’ll be back soon… And hopefully significantly simpler. :)

josh
josh

More work on my #go parser/compiler today. I can now parse function calls, the last rule left in my minimal grammar that’ll let me make an MVP. Woo! The next step will be to actually start turning the AST into Go code.

Unfortunately I also discovered a bug in the parser library I’m using. Someone else had already submitted an issue about it last year, and the project author replied, “I’m not using this for my own work any more, sorry, you’re on your own.” I get that, but it’s still frustrating that I’ll now have to understand and fix his code to proceed with my own.

belle
belle

It’s been a crazy week! Appointments and events have been cutting into my afternoons all week, so I’ve barely had any time to work on #exist for #ios. I’m still struggling with a really annoying bug that’s affecting one user in the #applehealth #sleep integration version, so I still can’t release it to all our users. @josh is going to help me implement a fix because I’m all out of ideas.

rhitakorrr
rhitakorrr

Got the #MidnightMurderParty editor back in working condition! As I thought, tonight was dedicated to entirely rewriting the #JSON encoding/decoding using #PureScript Argonaut. Mostly, it was pretty simple—just a lot of rewriting—but I did run into one super sneaky “gotcha!” right at the end. For some reason, my encoding was leaving out a field, no matter what I was encoding.

"secretKey" := secretKey
~> "data" := postData 

This was leaving out the "data" field, for example. I only figured out what was wrong because, after the server got mad at me for sending bad data (or no "data", rather), I dumped my other JSON to the console and dug through the keys until I spotted the correlation. Whichever field was encoded last just didn’t get encoded at all.

Turns out the fix was simple:

"secretKey" := secretKey
~> "data" := postData
~> jsonEmptyObject

Yup, just slap an empty JSON object onto the end of the extend (~>) chain, and it works.