Lifelog

📈 Total one-off revenue: $600
📊 MRR: $30

"Find an industry that still uses fax machines, and build a high tech, digital business there to compete with them..."

"It’s difficult to say that it’s difficult. I think it’s typically not easy to be open and vulnerable in public, and even harder to do so in front of your peers, customers and competitors...."

Rest is a form of productivity too...

On the surface, 1% improvement don’t seem like much. But 1% compounded daily over a year means you’ll be 37.8 times better than when you started. The power of compounding is the reason why consistency matters as much as—or even arguably, more than—intensity....

📈 Total one-off revenue: $600
📊 MRR: $20

Savvy Time had been super useful so far!

https://savvytime.com/converter/ca-los-angeles-to-az-phoenix-ny-new-york-city-trinidad-and-tobago-port-of-spain-brazil-sao-paulo-utc-switzerland-zurich-finland-helsinki-kuwait-al-ahmadi-india-kolkata-sgt-australia-melbourne

For indie hackers/makers, namely, developing, designing and marketing.

Taking a step back, to solve this new Date() doesn't apply offset issue, there seems to be 3 approaches I can take.

1. Patch date-streaks module directly by adding offset to new Date(), seems least effort, but hard to understand their code
2. Make my own streak.js plugin - making from scratch feels time-consuming but more control and less downstream gotchas
3. Use afterCreate lifecycle hooks within Strapi to save a new content-type streaks, so it's not calculated on the fly every time but saved as an integer as each post is created.

OK...... looks like the streak bug is still not completely dead, just like how cockroaches die hard. At least I identified the problem within a day, which is something to celebrate over. The first step to solving any bug is to isolate and identify, so that's a pat on my own back at least. My date streaks module uses `new Date()` in UTC to set the current day/date, and it doesn't apply user's timezone offset. So the array of published dates are offset to user's tz but it's always referenced to the the current date in UTC, which is why sometimes the streak breaks but restores when the user posts (e.g. if the user happen to write past the UTC midnight but still within his tz's midnight).

📈 Total one-off revenue: $480
📊 MRR: $20

'What feels like play to you, but looks like work to others?'

Turned out, the culprit was a sort function for the comments v-for loop.

v-for="comment in sortedComments"
:key="comment"
>
...
computed: {
sortedComments() {
const x = this.post.comments
return x.sort(function (a, b) {
return a.id - b.id
})
},
}

Changed that function to using lodash's sortBy function and it works now!

import _ from 'lodash'
computed: {
sortedComments() {
return _.orderBy(this.post.comments, ['created_at'], ['desc'])
},
},

All thanks to @yuyu 's suggestion to comment out everything in _slug! That got me down the right path to debug this eventually! Note to self: always fall back to fundamentals when debugging - just comment out code first to isolate the bug. But the deeper mystery remains:

* why this worked before but not now
* the behaviour should be consistent on local and production, but it worked on local
* the function didn't crash the page if I entered the site via a different child page by directly typing in the url
* why lodash worked but a vanilla JS script didn't