littlelogs

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

#github

January 2017

rhitakorrr
rhitakorrr

Yesterday was a mess. What was supposed to be two quick commits for #MidnightMurderParty and the rest of the day off became a 5-6 hour dev session where I discovered some pretty nasty bugs, at least 3 of them fairly serious front-end issues. @larouxn had to create a new endpoint on the back-end for one of the features I was working on, and while I was testing that, I found out that our release scheduling wasn’t working properly either (it was releasing content that wasn’t yet scheduled to be released; I’ll leave that log to Nick).

Long story short, I did close the last two #GitHub issues, but now I have to spend tonight fixing bugs in the most volatile part of the application and hopefully not introducing new ones in the process. So much for not fiddling with it until after the beta test!

rhitakorrr
rhitakorrr

Let’s see if I can get back to daily (or at least near daily) logging again. Today, I:

  • Closed two #GitHub issues for #MidnightMurderParty. Both were small aesthetic things related to the user resizing the book, but because of some race conditions that could occur between #Elm and #JavaScript (and did occur last time I tried this), I’d been putting the issues off for a while.
  • Got some #writing done on my current #shortstory—about 700 words on the manual typewriter, which I’m enjoying quite a bit so far.

Now, I’ll probably read for a little bit and maybe play some Osu! or Overwatch. Something that starts with an ‘O’ anyway.

August 2016

rhitakorrr
rhitakorrr

After all of @JorfimusPrime’s talk of blogging, I got it in my head to convert my portfolio website into a portfolio website / blog. It’s seriously due for an update anyway. Spent a good portion of the day looking at Jekyll, a simple Ruby-based static blog generator which #GitHub will build for you automatically on push. But, me being me, I had to look up a #Haskell alternative. And what do you know? I found #Hakyll, which is basically a #Haskell clone of Jekyll with a bunch more configuration options. Neat.

Spoiler alert: #GitHub does not support automatic #Hakyll builds to gh-pages.

So, tonight I dug through a bunch of #Hakyll + #CircleCI build tutorials, spent several hours configuring git submodules, orphan branches, and SSH keys as well as fixing mismatched dependency versions, and finally got the first automatic build and deploy of my #hakyll_portfolio_blog working!

rhitakorrr
rhitakorrr

Tonight turned out to be more of a cleanup night than a dev night.

Also made a repository to publicly track my #midnightmurderparty writing progress!

josh
josh

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 :)

June 2016

belle
belle

Drafted a #client #content article today that took way longer than expected. It’s not even extra long, but I’ve touched on the topic before so I drilled down into all the research rather than relying on any of my previous work too much, and it took ages.

Also set up a paid #github account so I can connect it to #exist and try to push myself to do more work on my iOS projects. Just looking at my Exist for #ios commits graph on GitHub after pushing up my existing repo, I’m disappointed at how long it’s been since I pushed any new commits. I wish I wasn’t so slow at programming, because I tend to put it off since I know I need a full day even to do something small.

May 2016

josh
josh

Today I finished off the privacy policy for #larder (based on Exist’s) and submitted it to Hacker News as a Show HN. Although the comments are almost all disparaging, it did fairly well in the upvote stakes, topping out at about #13 on the front page, and caused a huge number of signups (still steadily coming in). So ner to the rude commenters. Later someone from Product Hunt put it on there too, where nobody cared. Different audiences, I guess.

While all this was happening I got the #github integration for #exist working and supplying number of commits. I’ll test this a little more before deploying but I think it’s nearly done. Nice and quick.

April 2016

josh
josh

Spent today and yesterday doing #exist #support and working on its upcoming #github integration. Turns out there’s no easy way to get a count of total commits for a user across all their repos, but it is at least possible with some effort. Hopefully won’t take too long to get finished as the commits attribute already exists, and this integration won’t provide any other data.

josh
josh

After recording a new podcast episode on #Larder’s positioning in the market with @belle, I updated the homepage to reflect our angle of “bookmarking for developers”. Then tonight I deployed the first iteration of showing related release and commit info for #GitHub repos you’ve starred. I find this a handy way to see which repos are active and keep on top of their new releases.

March 2016

February 2016

josh
josh

Today I did some more fixes for the teething problems in rolling out the heart rate data for #exist, and later worked on #larder to make the #github starred repo import a little nicer, along with fixing some bugs. I’ve decided links in Larder need a description field, as well as a title, because project titles in github are of the form username/repo which isn’t always very descriptive. I’m not sure I’ll ever need or use the description field for manually added links, but it definitely helps for imported stars.

josh
josh

Today turned into a surprisingly productive day. Well, night. In the afternoon I ticked off my #exist #support and fixed a bug, but this evening I got stuck into #larder. I thought I’d start working on a #github integration. In the end, mostly because their API is pretty straightforward, I have a working script to import starred repos as links, complete with dominant language as default tag and project description! It’s pretty cool to have my stars in there and searchable. 🔭🌟🌟🌟

Just need to implement paging for that initial import of all stars and put the update script into a cron and we’re golden.

josh
josh

Also tonight I did some more work on #larder. Updating and deleting links is done, so next step might be our #github stars integration! I’m really keen for that one, as I’m so used to starring something on github vs bookmarking it elsewhere that most of the time I check my starred projects before I check my bookmarks (you can tell I mostly save coding thingies). It’ll be nice to combine the two.

January 2016

December 2015

peter
peter

Question for @josh and @belle, what are your thoughts on using a #GitHub webhook (attached to the repo of the main project that one is currently working on) to write commit messages directly to #littlelogs via your API?

I’m thinking that this may only be in the littlelogs spirit if the commit messages are descriptive enough, and maybe contain the project hashtag as well?

November 2015

anneliese
anneliese

Today's #latergram cont'd:

  • had our first customer journey mapping meeting wherein we had 1 user/customer type walk us through the buckets of work they do and the process within each of those respective streams of work. Crazy how many opportunities we already spotted for automating actions in a more centralized environment. #UX #CX
  • Day 3 using #Slack - the product team started playing around with #Github integration and created a channel where Issues and Commits feed into which will hopefully lead to less of me bugging them in disruptive IMs on whether a fix has been deployed to prod, heh 😜. Pretty neat to see how robust their integrations are; I'm excited to see more apps integrated into a single environment so there's less of a disconnect. #internalcomms #teamcomms

September 2015

July 2015

March 2015