Computer guys tend to lack imagination, especially when they work with acronyms. This may lead to a lot of funny stuff. Let’s look at the following acronyms, for instance: URI, URN, URL, and IRI.
In interviews I like to ask this question and only once a guy was able to give an almost 100% correct answer. Somehow, I was not particularly surprised about it, as even widely adopted specifications contain subtle mistakes.
The most important thing parents should teach kids are the mechanisms for self-improvement. This is basically what differentiates people from computers. When computers will be endowed with such a power, they will become more powerful than humans. And most likely humanity will disappear 🙂
We thought that you might be interested in a couple of software engineering positions opened in Bucharest, Romania. We will start sharing them on the blog.
In a previous article, we mentioned 4PSA’s Pineapple crazy team. Pineapple is the code name for a new product; the kind of stuff everyone needs, but not many know how it’s going to look like.
In a previous article, we promised you a better insight on how we are organized internally, namely the product-oriented teams we built. So, let’s start to review the teams 🙂
This software engineering team is handling the low-level aspects of our software engineering, i.e. most of the stuff other teams need in order to develop their products. Because we are lazy, we like to keep things standardized. 😀 This means that all frameworks (with one exception) are developed at this level.
Most programmers think they know what this means. I’ve heard it many times because I often ask developers on job interviews to tell me what they prefer.
Might sound like a trivial question, but it is quite relevant. Programming languages are just tools and we want to know whether our possible future colleague is able to understand how things work.
Until recently, 4PSA has had a pretty standard organization, with function-based departments – Sales and Marketing, Software Development (with many teams), Technical Support, Administration, Human Resources etc. This worked decently for many years and that is why I still recommend it as the default organization for any company really focused on a single product.
VoipNow 3 passes another important milestone. Yesterday, the Release Candidate version was made public, which means that the GA version is going to be launched soon.
VoipNow 3 is almost feature-complete. We say “almost” because the final “twist” will be a surprise to our users, and will be wrapped up in the final release.
Another interesting feature in VoipNow 3 is related to storage.
The industry has known many changes over the past years, but storage has remained a hot topic to the majority of Service Providers who consider scaling (read growing) their businesses.
Irrespective of how much storage space was available, sooner or later one would find herself / himself going out of space. This can apply to a personal computer, but also to the service provider’s environment when dealing with customer information.
We live in the era of apps. We have apps everywhere. Easy to use and performing very specific tasks, apps are the way to go. And with VoipNow 3, we introduce the support for apps.
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).
