tanin

I was working on a Desktop app and encountered a log error as shown below: SLF4J(E): A service provider failed to instantiate: org.slf4j.spi.SLF4JServiceProvider: Provider org.apache.logging.slf4j.SLF4JServiceProvider not found SLF4J(W): No SLF4J providers were found. SLF4J(W): Defaulting to no-operation (NOP) logger implementation

I've followed this tutorial: https://github.com/JetBrains/compose-multiplatform/blob/master/tutorials/Signing_and_notarization_on_macOS/README.md There were 2 problems that I've encountered. Unable to build chain to self-signed root for signer The command that failed: /usr/bin/codesign -vvvv --timestamp --options runtime

Why are people amazed that she likes her own music? Like, how are you going to make music if you don't like what you're doing? If you don't like it, you just change it until you do like it, that's art. (source)

A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over with a working simple system. This quote is from his book:

I just encountered an interesting UX issue regarding pressing a shortcut. I was using the KeyUp event for some of the shortcuts, and I've found it to be flaky and counter-intuitive. The main reason is that it's rather difficult to trigger the key up event when

Since I've moved to zsh, the history searching using the up arrow hasn't been working. Today I've decided to sit down and investigate. It turns out that set -o vi needs to be executed before history-search-end as shown below: # This need to be above

After leaving Stripe, I've experimented with a few other mediums for recording meeting notes. To name a few, I tried Google Doc, Slack, and paper notebooks. Even at Stripe, I did experiment with those mediums and didn't like them. They often miss one or another aspects

I have a small PlayFramework app (https://superintendent.app) that I just migrated to Scala 3. Here are my learnings: The goods 1. Scala 2 syntax is still valid in Scala 3. Basically, 95% of the code still works as-is. 2. Cross-publishing one of my libraries to work with Scala

Almost always, I'd choose Postgres over any database for a new project because it's flexible and support multi-variances of scenarios that may require different performance characteristics. However, I don't generally feel strongly about MySQL vs. Postgres. Either seems fine.... until I've learned