There are times in programming when you think "I wish I knew that from the beginning". Building an SDK is quite different from making an app. You have more things to remember about and the distribution is more tricky. It's also a big responsibility, because if you screw something up, you can't just update right away - you might have a lot of users, and you don't control when they update your library...
Close
Popular Posts
-
Although the title is an exaggeration, all code I've seen in my (short) professional career did indeed suck . Because it's m...
-
Often times instead of just smoothly bashing away at the keyboard to produce fresh lines of code I hit the creative block. I sit in front...
-
While reading the web I've stumbled upon an interesting article " Reusable Software? Just Don't Write Generic Code" th...
-
Every programmer must've struggled with Dependency Carrying , even though he might've not known that it has it's own name. Dep...
-
Decoupling and cohesion are phrases that are thrown around in software very often. You kind of know what they mean, but do you really? D...
-
Soroush has created a blog post that describes my funny feelings when using MVVM. MVVM is an evolution of MVC. It's "better...
-
The View-Controller in MVC is responsible of interpreting the Model (business logic) and managing UI. See that " and" in the mid...
-
There's been a heated debate about technical interviews lately. More specifically, about whiteboard interviews. The first time I've... -
When learning advanced features of Objective-C I learned how much power does knowing about it's runtime give you. I've decided to st...
-
There are times in programming when you think "I wish I knew that from the beginning". Building an SDK is quite different from mak...
