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.
When I first ask someone this question, I usually get a brutal answer: not a chance!!! This is what I’ve learned the hard way: true innovation is a process. Accidental innovation is not a process, but a fortunate mistake. 😉 In order to innovate, you have to follow a recipe because innovation must be consistent.
Organizing a software company can look like rocket science nowadays. But it shouldn’t be!
Apparently, most startups are unorganized. In other words, when someone who previously worked for a large entity joins the team, they are surprised at the lack of organization. Later on, they are even more surprised to learn that many things actually work better that way.
VoipNow 3 GA is finally here! In fact, even more than this, the first maintenance release is available, as we had a private release for customers. More information in the Release Notes.
While many of you already had some experience with the new VoipNow SPE, I want to share some interesting things about it.
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.
