31–40 of 49 posts
There is high value in pieces where the author uses himself as a case study in achieving something and provides a lesson for others to learn from. In this case, however, it just reads like braggadocio. What's the take-away for us?
Wow, a simple blog post that could be served and rendered to me in less than a second (mobile iOS) takes ages to load with a spinning disc, ages to render everything and some charts are lazy loaded when in view and take a long time, and an unresponsive scroll bar. I suggest get your posts on your own domain not this coda thing whatever that is. Stick on CDN hosting like netlify for free. Use simple images or svg. Esc…
Coda is a knowledge base, much like wikis such as Confluence. It's mostly used inside businesses, so I imagine he just made this page public. Making it hyper optimised for anonymous web traffic is almost certainly a non-goal.
I am suggesting that if you want to blog, and want people to read what you blog, to host it somewhere where it is readable on the widest range of devices. If a iPhone 6 with a 20Mbps mobile connection is too antiquated to render the site, then they are probably cutting out a lot of audience.
I don't know Coda, so I'll use the Confluence (which you suggest is similar) as an example. If I am using Confluence it is because I have to, for work. I will make a provision that maybe I can't read it on mobile and I need to be at my desktop. If I am reading a blog post from hacker news, I probably wont go to the effort of bookmarking it later to read on a desktop PC.
Some friendly advice: your charts are almost impossible to understand. They may make sense to you, but they are utterly meaningless to most anyone else. I suggest that as you continue writing, you should take a step back and try to read it from the point of view of someone that has no previous knowledge of anything about you. This could help you focus what you write about and make things more succinct, because most p…
First one is obvious.
Second one becomes quickly clear when you realize that it has to be total of hours over some period of time. Otherwise it would not make sense.
Third one is quite interesting. It is very informative and interesting to observe.
These charts could be made better naturally.
Title and short description would definitely help.
For the second one I would also include totals - for each day, for each time period and most importantly grand total that has to be the same for days and periods. Also small explanation that this is hours distribution over period of this and that.
For the third one I would fix units of the duration. Current ones are difficult to interpret. Hours scale would make the most sense probably - 10, 20, ..., 40 (a normal work week, in the middle), ... 80.
I do not think that there is nothing bad in having multiple interests. Distributing ones time between multiple interests is a difficult task to tackle but it does not make it automatically meaningless. It is actually a good idea to have some time management and good data always helps.
I've been tracking my time in great detail as I work on various projects and I am hoping others will find this interesting!
I would have liked to make the charts a bit clearer but the customisation in Coda is quite limited. Nobody I showed it before posting it on HN had any complaints. I can add some more context to the bits that aren't clear.
As for how long I spend tracking my time... not too long really? I've been tinkering with my document here and there as I go, and now generally I just switch to the right project and hit "Start activity", pressing "Save" when I finish. I've been using Coda rather than bootstrapping (yet another) private time tracking web server because it provides a different sort of agility to what I'd get if I was programming everything myself.
There is high value in pieces where the author uses himself as a case study in achieving something and provides a lesson for others to learn from. In this case, however, it just reads like braggadocio. What's the take-away for us?
Take-away: Starting a business is hard. Contracting is much much much more profitable in the short term. I wish the author compared his contracting value creation with his project's value creation.
I'm most impressed by how detailed the tracked time is- what app or method did you use and how did you stick to it?