ozuly

You can buy replacement backlight spreaders off of etsy. I did it to mine and the backlight is now usable..

I fixed this on my A158 (basically a silver F91) by replacing the backlight spreader. Super simple mod and only costs about $12. Granted that's close to the cost of the watch itself.

https://www.etsy.com/listing/1448973768/back-light-spreader-...

There is a Github Discussion where he goes into more detail. He also talks about it on his twitter:

https://github.com/lucia-auth/lucia/discussions/1707

https://x.com/pilcrowonpaper/status/1843258855280742481

If I'm not mistaken, this is written by the author of Lucia, a popular auth library for TypeScript [0]. He recently announced that he will be deprecating the library and be replacing it with a series of written guides [1], as he no longer feels that the Lucia library is an ergonomic way of implementing auth. He posted an early preview of the written guide [2] which I found enjoyable to read and complements The Copenhagen Book nicely.

[0] https://github.com/lucia-auth/lucia

[1] https://github.com/lucia-auth/lucia/discussions/1707

[2] https://lucia-next.pages.dev/

I'm continuously impressed by Costco. Not only is it one of my favorite places to shop, but I also recently recent to the Acquired episode on Costco[0] and was super impressed by how they run their business. They've continuously been able to align their unique advantages to reenforce each other and make their advantages even stronger. I highly recommend this episode to everyone.

[0] https://www.acquired.fm/episodes/costco

In case it’s helpful to anyone who has to jump off vercel:

I recently had to transition my company off of vercel for reasons unrelated to this (wanted to use cloud infra primitives that vercel does not provide, and wanted to leverage the large amount of AWS credits my company received) and found sst.dev [0] to be easy to migrate to and a joy to use in general. It leverages open-next to deploy next.js projects on AWS in a serverless way.

I’ve been enjoying using it so much that for my next project I think I’ll skip vercel altogether and use sst from the start.

[0] https://sst.dev/

For me personally, I find a functional programming to be the most productive when working on a project as a solo dev or as part of a very small team that I've hired. But the downside is that it's much harder to onboard devs without experience in functional programming. It takes a while before they can be productive when introduced to a codebase that's mostly written in a functional style — one that's written in Effect for example.

I recently started a company and was tempted to use Effect as I felt I would be able to build faster and higher quality than Standard TypeScript, but decided against it since I felt that I would pay the price when it came to grow the team. So far the decision has paid off.

I did indulge myself a little bit though and do make heavy use of remeda and ts-pattern across my code.

I use a similar pattern in my typescript code by using the Remeda library[0]. Like the patterns described in the article, the util functions can be used in both a one-off data-first way:

    R.map(arr, (x) => x + 1)

and as part of a pipe in a data-last way:

    R.pipe(
      [0, 1, 2, 3, 4, 5, 6],
      R.map((x) => x + 1),
      R.filter((x) => x % 2 === 0),
      R.take(1)
    )

I've really enjoyed using it and would recommend it to anyone who would like to write their typescript in a more functional way.

[0] https://remedajs.com/

Although this article was adapted from the author's newest book, she also has an older book[0] where she writes more about this topic and how it relates to emotions. I thought it was a little longer than it needed to be, but it was still the most interesting no-fiction book I read that year.

[0] https://www.amazon.com/How-Emotions-Are-Made-Secret-ebook/dp...