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.
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.
Hey there #littlelogs! I’m Djordje, digital designer and front-end developer from Belgrade, Serbia. Other than geeking out about typography and functional CSS, I’m spending my days cooking, doing yoga, meditating and playing with street dogs.
Hello #littlelogs! A little introduction: I’m Stefan a frontend developer from Germany who works for a Cologne-based agency by day (#dayjob) and on various side projects by night. 😉 Right now I’m working on a new theme for my WordPress powered personal #blog and the new version of shortfil.ms, a platform to discover “the web’s best short films”, which I started with some friends two years ago. The new version will introduce a new design, user logins and watchlists. I’m also working on a hybrid mobile app for #shortfilms, which I announced to be released in Q1 2016 when we were featured on ProductHunt. 🙈
Regular reminder that you can invite people to #littlelogs from your account page, and if you’d like to see a bigger, more diverse community on here, you should do that! There’s less point to logging your progress if you feel like nobody cares, so why not invite someone with similar interests who can like your stuff and post interesting stuff of their own?
Okay great, good job everyone 👍
Second evening/morning staying up ridiculously late to work on #school work. Hoping tomorrow will be different now that I’ve completed most of this session in my Informatics course. Barely touched my #website redesign in the process. Pretty sure Rufus the #kitten thinks I’m ignoring him. Thankfully I don’t return to #work until Wednesday morning! Signed up for a #littlelogs account in the meantime. It’ll log my progress in everything. Basically my life’s changelog. How exciting?
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.
Happy new year littlelogs! Wishing you all the best to do some cool things in 2017.
I’ve nearly got the #exist end of year report finished, after quite a few design iterations, but I’m not going to rush. I can’t send it for at least 2 more days, for those who are negative UTC and to give everyone a chance to sync their data, but even if it takes a couple more days after that, I think it’ll still be relevant. Hoping everyone gets a kick out of it! I think it has some fun stats.
A bit tired tonight but happy to wrap things up.
Work 1 had its to do list all cleared up and even some tasks that have been dealt with in advance for next week. I’m behind on my work 2 though, as everyday new things come up and it becomes quite hard to stick to a plan. Got stuff done anyway.
Tonight with some help from Linode I moved the #hellocode server (which has all the small things, like the hellocode.co domain, #littlelogs etc) from its legacy, memory-constrained Tokyo server to a shiny new one in Singapore with 4x the RAM (for the same price). Hopefully won’t have any more issues with out-of-memory errors now.
Day 2 of my new morning routine went okay. I got started a bit late, but managed to fit everything in to some degree. It’s nice to be doing some personal #writing in the mornings again.
Also wrote up July’s #HelloCode monthly report today, followed up a couple of #client emails, and made some changes to my productivity #book sign up page to reflect my new ideas for it. I’m going to focus it more on analogue productivity, and fold in some of the general #productivity research I’d planned to include. So it’s time to create a #littlelogs project for it! #productivitybook
Still moving slowly. I think it is due to me being tired.
I managed to get the #angular set up with the user interface. Whenever I start something in #angular my heart rate goes a little faster. I really need to set some time aside to learn it, once and for all.
I am now busy with the client-side logic. My hopes is to have most of the app finished by 6:00.
I can always just go sit at the event to fix the crucial things, the droplet is linked to the master branch, so I can theoretically just push a commit up and the site is updated.
Ah well, let’s get back to it. Back in two hours.
(Side note: Logging my dev goals on a two hour interval is definitely helping with productivity, loving #littlelogs for this in the future!)
Trying out some of our #littlelogs experiments tonight after a bit of a hiatus. There’s a new tab called Following that replaces the old Home tab, which is now composed solely of your own logs. Littlelogs is primarily about logging your own progress, so the place where you log should be the place where you can actually see your own logs.
Also, there are some headers denoting months in some lists now, making it a bit easier to mark the flow of time as you scroll. And finally, projects and their related tags now get a bit more precedence compared to tags denoting tasks and technologies. It’s kind of awkward that most of the top projects on the trending list are ones I’m working on, but you can fix this!
- Create a project description for your tags by clicking on the tag then “add a description”
- Use the tag when you log about the project!
Let me know your thoughts. I’m open to feedback, new ideas, and threats of violence if you hate it (I guess).
completed in order
1. posted obligatory first log
2. finished prep and compression of data
3. drafted #githup post
4. #testing complete
all my best, tudor
p.s. almost forgot, let’s be friends
am i doing this right?
Finally fixed the #cocoapods problem I was wrestling with yesterday afternoon! My #littlelogs #Swift app wasn’t behaving the same as the original #objectivec one, and I couldn’t figure out why. I’m still not exactly sure, but I think maybe the cocoapod I was using wasn’t working because of how I’m subclassing in Swift. I don’t know enough about it to fully understand and fix that… but I did manage to recreate the same behaviour offered by the cocoapod all by myself! Turns out it wasn’t very complicated, I was just being lazy by using a library to do it for me 😏
We have some good ideas for enhancing littlelogs, and making a stronger story out of the progress you make on a project. It might also help distinguish between posting everyday progress, milestones, asking questions, and off-topic stuff.
Larder-wise, Belle is going to put some effort into marketing short-term and later switch her time to mostly building the iOS app. The plan is that in 12 months it’ll bring in another $3k a month (at least!), doubling #hellocode income and meaning Belle can ease off on her client work.
As for Exist… we’re going to focus on adding the “event streams” stuff for custom/real-time tracking, and then stop and plan again. Maybe a pivot?
Wrestled with my #swift version of #littlelogs for #ios this afternoon. I’ve realised I can use #objectivec #cocoapods libraries, so I’ve started adding in the ones I used in the #objectivec version of the app. For some reason, the one that lets me tap the background view to make the keyboard dismiss won’t work. I also tried another library that does the same thing, and even re-implemented it myself and still can’t get it to work. At that point I gave up and had a nap, because what a silly little thing to spend all afternoon on.
In other news, I’m still not feeling great but don’t seem to have a proper cold so I’m guessing it’s all symptoms of withdrawal as I come down from all the paid meds I was on for shingles.
Despite not feeling good, I did manage to squeeze in two pomodoros of #client work. Feels good to have made solid inroads on that piece, and I learned a bit along the way, which is always nice.
Yesterday/last night I did some more #swift coding. I’m still working on recreating my #ios #littlelogs app in swift, and it’s going okay! I still have a lot to learn (e.g. I get optionals in theory, but I haven’t got the hang of using them yet).
So yesterday I added a double-tap gesture to the Home screen, because I found in my #objectivec version of the app, it’s a bit slow to tap a log, wait for it’s detail view to load, then tap the heart to like it. So now I can double-tap to like a log!
I also started working on implementing the detail view for logs, so when you tap one, it opens a new screen with the log and its comments and a comment field. So far I have just the log content showing up.
With #curo people in three different timezones at the moment, we’ve been trying to record 10 minute weekly video updates for each other, to reduce the amount we are repeating ourselves in phone calls over and over. We’ve tried emails, reports and slack for this, but there is something time consuming for us to write everything out, and there is something lost when we can’t speak our enthusiasm or frustration about things verbally. Also, sort of like the idea that will we have video recordings of our progress to look back on one day.
Anyway, it’s been helpful, but it’s painful (and slow) to upload them somewhere useful, put to a password on it, and then share the links in slack (and these things then get lost fast).
I have taken a day off, getting a diner with friends though I had to do a few calls with potential clients that ended with long discussions… BTW I am pretty much amazed by the #littlelogs effect when I see all the stuffs others accomplished today it really motivates me to accomplish even more as the first thing tomorrow ;-)
Tonight I made a tiny new addition to #littlelogs. Now you can create project details and relate them to a tag, so people browsing the tag from your profile or for all logs can see further details. Anyone can add details to any tag, so it’s basically an honour system until someone abuses it — but I’d encourage you to only add more detail to tags relating to your own projects, not generic tags. I hope you folks find this useful for providing more context on your work, as a way to link to your projects without feeling spammy by casually dropping links into your logs, and as a reminder to tag your logs each time they relate to a project ;)
As an example you can see my tag description for #exist.
Last night I played with #swift a bit more. I’m slowly porting my #littlelogs #ios app from #objectivec to #swift. It feels good to actually write some swift code, because the ideas really aren’t sticking in my brain just from reading about them. I’m really enjoying the syntax so far, but I’m a bit frustrated at the extra coercion needed to get swift to play nicely with #json, since I deal with #API results a lot. #laterlog
Going to try to get back on #littlelogs a bit now that i’m in back Australia for a few months. Been back for one week, and haven’t had much of a chance to get my head on straight yet! So, let’s say:
Finally finished my review of #exist, #littlelogs, and #podcast progress in 2015 for the #hellocode blog. It’s long! Turns out there was a lot to talk about. There is a TLDR though, and some graphs that sort of go up and to the right. I hope if you read it you find it informative and educational.
- User Stories - I will use #Trello as my agile storyboard / user story management and change management
- Wireframes - I will use #Axure for wireframes and mock prototyping.
- Environment setup - I will use #XAMPP on a local machine with #MySQL as the chosen database and #PHP as my chosen programming language.
- Code Management - I will use #bitbucket to practice the behaviour of managing code branches and merging.
- Other Technologies - I will employ #css but most probably a bit later once the functional aspects have been covered. The likelihood also is, if I find another technology which assists in meeting the use case and it can be implemented I will. i.e. #JSON / #JQUERY.
Thanks #Littlelogs community for the opportunity to share this with you, sorry the post is too long.
MME – ManageMyEnergy #MME
ManageMyEnergy is a project which will use the hashtag of #MME in future. ManageMyEnergy aims to take much of my consulting experience to date and apply real world use cases to help maintain the flow of both momentum and enthusiasm in this project. I guess the more you think about it (relating it to work and real world) the more your likely to trigger the want/need to progress it further.
I will use #littlelogs as my client/public accountability and blog on a set frequency (for which I’m yet to agree). I aim to be as agile as possible in terms of going through the various stages of design and implementation but I also don’t want to be too rigid that it kills my inspiration or enthusiasm. I will use #Trello for storyboard and related task management. I will utilise a number of technologies for which, I would be happy to take suggestions from the #littlelogs community on alternatives as I progress.
Just checked my email to find a flurry of #littlelogs signup requests in there. Turns out @jerzy submitted @belle’s last blog post about littlelogs to hacker news, where it hit the front page! Woo, thanks! And welcome everyone, looking forward to reading your logs about all sorts of different projects 😊