We will change your SSH keys and you will like it
In preparation for a new post, I logged in to GitHub recently. I created my account two years ago in anticipation of being able to open-source more code and I wanted to reserve my name; I had a couple of forked repos but that's it. A new baby and a wife with major back surgery will do that to you.
Imagine my surprise when I logged in . . .
I hope you like public key cryptography
Let's break down a
.mobileprovision file piece-by-piece:
1 - The app ID prefix
<key>ApplicationIdentifierPrefix</key> <array> <string>X00X0X000XX</string> </array>
2 - When the profile was created and when it expires
3 . . .
the post in which I swear a lot
UIPopoverController, why must you be such an odd duck?
I am finally trying to get Storm Sim updated for iOS 7 and since I need a dark theme the default behavior of "dim the background views" is useless. But you can't just turn that off... oh no sir! You have to subclass
UIPopoverBackgroundView and do the whole thing from . . .
wherein we make a compiler do the work
The very first question any programmer has when they hear about immutable data structures is "how the hell can that possibly work when I can't change my data?"
The answer is rather simple, at least in an object-oriented language like C#. Instead of setting properties and fields, you call a method that returns a new object . . .
mutable state is the devil's handiwork
This is the first in a series of posts I plan regarding immutability (edit: yay, follow-through!). In this post, I want to cover some of the reasoning around why you'd want to use immutability and some of the awesome things that just fall out of an immutable design naturally. Future posts will cover making the compiler create immutable . . .
or how not to cry yourself to sleep
Storm Sim has a free and paid version. It supports six languages. Two devices at three resolutions. If the UI changes in any significant way, it needs 180 screenshots. Uploading them in iTunes Connect is bad enough, but navigating through the app in each language is just killer. I find myself not wanting to make a change because I know it . . .
hint: it isn't technical
A recent slashdot post was discussing a privilege escalation hole in Android and by looking at the comments, it was obvious to me that most geeks just don't get it when it comes to security.
Android has a huge, gaping security hole but it isn't a technical one, it's the design. The flaw is the same one that afflicted ActiveX in . . .