An interesting new feature in VoipNow 3 is called extension virtualization. As it might prove useful in many cases, let’s review it. This feature is going to be available in all editions of VoipNow 3.
The basic idea is that we want to separate the phone (device) from the functionality stack, which is setup by the user (features offered by VoipNow).
We continue our series of VoipNow 3 articles with another important improvement introduced by VoipNow 3 – account level reorganization.
This reorganization will affect any software integration you might have with VoipNow. Although we tried to preserve compatibility, it was not totally possible, therefore you have to modify your SystemAPI calls to match the new concepts.
In the past week, we reached an important milestone – less than 100 bugs opened for the VoipNow 3 release. I know, it might sound a lot, but judging on the release size, they are a just few.
As the release could not take much longer, we are opening a series of short blog articles that describe the most important technical changes in VoipNow 3. We will focus on the changes that can affect you in a way or another.
Let’s start with the APIs. Many deployments use the APIs for provisioning operations (SystemAPI) or for controlling calls (CallAPI).
Interaction with students made me understand that computer science graduates need some guidance. Every teenager knows that an architect designs structures, a doctor heals people, and a professor teaches students. These jobs are easy to understand. Still, it’s not so obvious what a computer science graduate does. Sadly, many students remain pretty much confused about their mission, even after graduation.
I watch TV only when I have to, and most times I switch to Discovery or National Geographic. In the past weeks I’ve switched on the TV when they were running some programs about Maya civilization. There are plenty of interesting things to say about Maya, but instead all these programs were focused on the Maya calendar and the end of world.
The problem seems to be that all Maya calendars discovered end in 2012… And guess what, we are close to the end of 2012.
We’re closing this race with a set of problems that rely heavily on context.
The Cool Summer Internship Race has been a driver of great attitude, since most of what we published left room for creativity, in every sense. What is more important though is that it turned into a driver of entailing actions.
What are we going to do next: we want to offer those who would like to become interns at 4PSA the chance to know us in a competition.
This is the title of a famous book of Stephen Covey. In many online tests we use in the recruitment process we ask a simple question – “What’s the title of the best book you have ever read?”. Frankly, for me this would be a pretty difficult question, mostly because it’s quite impossible to flatten (I have a good definition of best) books based on topic. I can name a few very good books regarding engineering process, product management, architecture etc. But these books cannot compete with War and Peace, Karamazov Brothers, poesy or philosophy.
Do not forget about the rules. The deadline to submit your solutions is Tuesday, May 8th, 10 am GMT. Results must be submitted here. You can solve the problem in a small team!
The Cool Summer Internship Race is getting closer and closer to the finish line. A big thumbs-up for all those who have already sent their solutions to previously posted problems and a piece of advice to those willing to do so: hurry up, we only have 2 sets of problems left! But we still have positions to fill. 🙂
This week is going to be more social. 🙂
We are thrilled to see that we rose some enthusiasm with the problem sets published so far. This fourth problem set is dedicated to strategy. We would like to see more of the “how”, and to this purpose, we are publishing approach-based challenges.
Do not forget about the rules. The deadline to submit your solutions is Monday, April 23rd, 10 am GMT. Results must be submitted here. You can solve the problem in a small team!
