Credit: This article is based off of the templating library mote. I was inspired by the simplicity of the library and it makes a great study piece for those who haven’t looked into the internals of templating engines before.
The very nature of Python makes the task of protecting the source code complicated. As an interpreted language, the source code must be available in some form in order to execute it.
“Product-Market Fit” is the buzzword of today. The digital revolution is upon us and success is up for grabs for those companies that can just nail the product-market fit thing. Right?
Imagine you arrive at an airport for the first time and you are in a hurry to find the gate; or you’re in a museum and are interested in a specific section; or you’re about to meet someone in a big hall but have no idea how to give indications to each other about where to meet: Indoor positioning to the rescue.
This post is an update from my previous post Is Swift production ready?, with some advice to remedy the slow compile times (as of Xcode 6.1.1 and Xcode 6.3 beta) you may be suffering with the new Apple language.
Most ORMs out there include model validations as part of the features they provide. I think that’s kind of cool and very useful, but sometimes it’s better to abstract that responsibility away from the model, especially in cases where validations are tightly tied to other factors or flows.
This is a question that I sometimes get: Why don’t you use Bundler?
When writing code, our classes often go through a series of transformations. What starts out as a simple class will grow as behavior is added. And if you didn’t take the necessary precautions, your code will become difficult to understand and maintain. Too often, the state of an object is kept by creating multiple boolean attributes and deciding how to behave based on the values. This can become cumbersome and difficult to maintain when the complexity of your class starts to increase.