Last year, I did a talk at try! Swift NYC on the state of Swift on Server in 2018. Since then, Swift on Server has evolved quite a bit. This blog post is my opinion on where Swift on Server stands at the end of 2019.

I recently encountered a somewhat unusual Swift problem. I had a struct that looked something like this:

I recently came across this paper: “When, How, and Why Developers (Do Not) Test in Their IDEs” written by Moritz Beller, Georgios Gousios, Annibale Panichella, and Andy Zaidman.

My team recently started using BitBucket to collaborate on a project. We didn’t make the choice - it was made for us. Historically, we’ve used GitHub. However, since we were going to be using it, I figured we might as well make the most of it. On the surface, BitBucket seems like a good deal. It’s got pipelines and deployments built in. Being made by Atlassian, you’d think that it integrates better with JIRA than any other source control system. It’s also significantly cheaper than GitHub. All of this sounded great, until… Code Review.

I wrote about a problem I was having with Kotlin data class constructors a few days ago. I sent it to a few people and asked for thoughts on how they might address the issue.

Recently, a lot of iOS and macOS apps have switched from a pay once and use until next major version pricing model to a subscription model. The latest example I’m aware of is Ulysses. I don’t use Ulysses, but one of the apps I use that has also made the switch is 1Password. There’s been a lot of discussion about this all over the internet.

I’ve been trying to do something with a model class in Kotlin that I’ve done many times before in Java, and I’ve been left without a clean way to do what I need.

Problem

Earlier today I was writing some code that looked like this: