Seven releases in two weeks
The library worked. I spent two weeks rewriting large parts of it anyway, and broke compatibility on the way.
The library worked. I spent two weeks rewriting large parts of it anyway, and broke compatibility on the way.
Every client wants one small thing that no other client wants. It is always a few lines of code, and it never belongs in the main code base.
I like profilers. I also cannot use one where I need it most, which is in production, on the request that is slow right now.
Spring has a decorator that keeps your cache honest when a transaction rolls back. It does that by lying to you until the transaction is over.
I want to know where users are, and I do not want to know where users are.
I do not like software that tracks where people are. I have started on an app that does exactly that.
In May I imported the world into MySQL. In October I deleted the database, and the library got simpler.
1488153600. Is that seconds or milliseconds? You find out when the date lands in 1970 or in the year 49,000. APIs send timestamps like that since a number is fast to parse. I wanted to see how much of that is real, so I wrote a parser this weekend.
Everybody knows you should not build a message queue on a database. I just did, and I think it was the right call.
When core data changes, something else has to happen. A cache entry must go, a search index must be updated, and an audit log wants to know what the value was before. I had one mechanism for all three in my previous job, and missed it in the new one. So I built it again from scratch.