Switching from sqlx to db.v3 Short post – ended up switching from sqlx to db.v3 since I felt that the sqlx layer was more likely to be error prone. db.v3 example func (u *UserService) UpdateUser(user *model.User, args struct { Name *string Email *string Password *string }) (*model.User, error) { update := make(map[string]interface{}) if args.Password != nil { user.HashPassword(*args.Password) update["password"] = user.Password } if args.Name != nil && *args.Name != user.

Performance of JavaScript object reduce Just a short post to look at assumptions. A few weeks ago was having one of those classic debates with a co-worker about the performance of object construction. Since with ES6 it is very easy to write: const obj = data.reduce((acc, [k, v]) => ({ …acc, [k]: v }), {}); I had internally always made the assumption that JavaScript’s runtime was making some tail call style optimizations on object reduce.

I’ve been working on an react-native application which has been a very interesting and fun learning project. While there are always the challenges of getting a product built and ready, it’s been a very interesting learning process about app stores and releasing products. The app OneSnow is a tool to help Vail Resorts Instructors review their schedule, so it’s not an app that will take over the world. Google Play Store and SEO The biggest challenge that I’m having is that the google play store isn’t taking the product name as a searchable keyword.