I'd say that if you have some programming experience, about half an hour would be reasonable to implement and understand each tutorial - but there's a lot more to be had squeezing or polishing if you have the time.
Also, it doesn't matter if you do some late, or decide to skip any.
I found Tiny Code Christmas last year. It was easier for me to get into than other code advent series, and introduced me to active participation in the demoscene, which I'd admired since the Amiga days.
I continued on, and it's been an extremely enriching - and slightly consuming - hobby for me this year, with a wonderful, supportive community.
As folks have said, you can start any time.
If you hop on now (you can still start with Day 1) then post your stuff to your preferred social network (#lovebyteTCC) - Lovebyte (and friends) will appreciate your creations.
There are some folks who are going hard on sizecoding, but it's also an opportunity to get inspired and just play to make the prettiest thing you can.
I adore my original Pebble and Pebble Time Steel. I'm curious to see whether Rebble [1] can pull together a new ecosystem.
I was under the impression Eric and the original Pebble team had deliberately ensured enough openings for that to happen, when the Fitbit acquisition news broke. Thanks to them if so.
Same thing happened with the first Pebble Time Steel I bought. I took it back to the shop and swapped it. This one's been perfect for years, so I put it down to a batch problem.
It's just how Hacker News works - people like older articles to be tagged by year. It's to make it easier to spot things that they may have already read, or that may be interesting but not as current.
I started this as a Twitter game a few years ago; it felt like a compact idea with a good hook. Earlier this year I automated it- so it picks its own words and collates the stories on the website itself (mostly successfully).
It doesn't have a big following, but the people who play are passionate about it. Some people play every day, and the most prolific author has written ~650 of them.
I've seen people get better as writers, some experimental stuff (like an improvised longform story built over many daily prompts), and occasionally I see a microstory that knocks it out the park. That makes it worthwhile.
> Active Pebble watches will work normally for now. Functionality or service quality may be reduced down the road. We don’t expect to release regular software updates or new Pebble features.
I hope they open source Pebble OS, maybe even the assets that drive the Pebble store.
Cloudflare works at the DNS/routing level. You can use their layer to communicate via HTTPS with the browser. The connection between your site and Cloudflare won't be encrypted... which is a bit of an antipattern (as discussed elsewhere).
panic() in a web serving route (e.g. signupPage here) is bad practice - an error will bring down your web server. Panics should be reserved for errors that invalidate your system, e.g. missing view assets or db connection on system startup.
Also, it doesn't matter if you do some late, or decide to skip any.