As we have mentioned in a previous post, among many other important things, the Apps Team builds specialized Apps for end-users.
An App must be able to run on various devices like smartphones, tablets and desktops and offer an outstanding user experience on any of these devices. We have an interesting approach – we build an App once and we are able to deploy it anywhere. Apps are written in JavaScript and they use a specialized stack framework.
The March day was slowly unfolding over the garden. The air was fresh and cheerful birds were singing up in the trees. Flowers of all colors turn their heads towards the sun to catch the warm spring rays.
If only words could let you feel the amazing fragrances everywhere…
There is almost nothing more hip than Apps these days. Just read there’s an App to turn your Harlem Shake videos into guaranteed success 🙂
JavaScript App development, less visible to the end-user, is very much aided by something developers call Containers. The Container component arranges its items in a special layout.
Software users get critical when confronted with an issue. There is also a good chance they will tell their friends they hate your software.
If you are a technical writer, the time when a customer can’t make head or tail of what you wrote is the best time to receive feedback. A technical writer’s challenge is to deliver the right information at the right time, without adding frustration.
Defining a baseline is one of the best things you can do if you want to deliver things fast. It sounds like a pretty simple concept, but the truth is that many software engineers do not understand that there should be a baseline in everything.
I personally try to find and impose baselines in everything I do, as this helps me improve work products. This happens in a pretty simple way – the baseline “forces” me keep track of modifications I make and at the same time it makes me more responsible about them. Let’s review some use cases.
In a previous article we detailed on the team called Team Support. This is basically the team that provides the other 4PSA teams with input and resources so that they can work more efficiently.
Our latest opening in the Team Support (Bucharest, Romania) is quite an interesting one – Senior Security Engineer. What is this position doing in Team Support, you might ask… Two reasons: the person filling this position is going to report directly to upper management and in order to be efficient she/he should not be “corrupted” by a product team.
In the Apps Team we develop a wide variety of SPAs. Do not think about any nice hot-springs resort, SPA stands for Single Page Applications. The main reason why SPAs have been gaining a lot of popularity these past few years is because they provide a more appealing user experience. Just take a quick look at Gmail, Official Gmail Blog, The New York Times to name a few. The content is retrieved in a single page load. This means that page sections get dynamically changed.
It all started about 10 hours ago and I am still fresh, hopefully due to the amazing coffee. And nothing compares to the feeling of being useful on your first day at work, then receiving your first task as a trainee. I am used to “The Writer” nickname. I always like to write down things, it helps me keep them organized and up to date.
I remember I woke up early in the morning to be one of the first to come to the office. First impression as I entered the door: young team, smiles on their faces, a friendly mode of saying “Welcome!”.
We do a lot of REST in the Pineapple team. We love REST. Why? There are many reasons:
Recently, our Infrastructure team received a task that involved restricting access to a service only from certain countries. To make things even harder, this had to be done on Cisco IOS devices with relatively low performance. We will review in this article how we were able to solve this.