In a previous post I explored how beacons (iBeacons and any other flavour too) could be used for indoor location with certain precautions and limitations. Now I’ll explore a simpler scenario: detecting proximity from device to beacon, which is basically the purpose of beacons.
We love Ruby. We have enough experience with Ruby and web software development. But something that we love even more is being up to date. We are always trying new libraries, frameworks, designs and languages too. We like to get our own experience, contribute to as many open source projects we can. This is something that we enjoy, individually and as a team. It is part of the company’s culture.
When we think about building an application, we visualize it as a bunch of code glued together, running somewhere on the web for the purpose of providing people some value. It could be the homepage of your coffee shop, an e-commerce site or an amazing API which collects data from your watch.
This is another entry in our series of technical articles about software
development tools and libraries. Today I would like to introduce you to
HTTPie, an HTTP client which will help you to put aside cURL,
that wonderful - but not so human-friendly - tool.
Provisioning and deploying applications has become an important aspect of building scalable applications and delivering features continuously.
When designing a product or service we bring so many assumptions to the table. One of the core attributes of Lean Startup is to validate our assumptions. We first acknowledge that we have assumptions and then we do something about it. There are a lot of right answers for what actions you can take and speaking with customers is at the top of the list!
When developing software, there eventually comes a time when the team needs to start thinking about performance. Ideally this is done on a daily basis - most developers try to balance productivity, code readability and shipping features. But at some point of the life cycle of the application, the need to optimize for performance becomes evident.
This is the third part of the Protecting a Python codebase series. This time we will be playing with Python interpreter in order to protect the original code of a Python based project.