tanin

Imagine you go to the DMV. The DMV has a waiting time of 3 hours. One employee walks up to you and says "oh well hey we have a new beta program for you, and you'll only need to wait 1 minute instead of 3 hours."

When building a web application on Playframework, there is no good way to integrate a JS framework like Svelte. The only way is to run Play and run the npm watch in 2 separate terminals. One is to build the backend code, and the other is to build the frontend

Repository: https://github.com/tanin47/lilit-sql At the company I work at, we are building an analytics product on top of Presto, which supports SQL as its interface. We have a lot of long SQL statements to power charts, tables, and CSVs. When I say long, a final SQL statement

I've launched Superintendent.app 6 months ago. Initially, I built it to make me more productive at work since I work with a lot of CSV files, and I loathe using Excel. After building it, I've realized that having a Desktop app that can handle GBs

Since starting at a new company, I've been working on an accounting report that comes in the form of CSVs, so I've worked with a lot of CSVs. As a person who knows SQL well but isn't good at Excel, working with CSV files

Several months back, I've started a new job and immediately found myself perform some repetitive micro-workflows like: * Copying an ID, pasting it on the browser URL's bar, typing some url, and hitting enter * Copying a millisecond-from-epoch number, visiting a website that can convert it to human-readable

Even if we use a great timezone library like tzinfo, a bug might still happen. That's exactly what happened to me. I was building a graph whose x axis is of day frequency. Our database stored data in UTC. Since I wanted the days to be in accordance

Yesterday I've spent 5 hours debugging a strange issue when using the Algolia's Scala client with Playframework during local development. That is, the period where auto-reloading happens when code is changed. For a long time (~9 months), we've experienced a DNS error "flakily&

In my previous post on parallelising tests in SBT, it doesn't work well in practice or, at least, on CircleCI. The main disadvantage is that it doesn't balance the tests by their run time. Balancing tests by their run time would reduce the total time significantly.

SBT, the official build tool for Scala, is a very complex build tool. It's one of those things that makes me wonder if I am stupid or the tool's complexity surpasses average human intelligence. I've done a few things with SBT (e.g. printing