Posts Tagged Under: JSON

Learning Through Exposure – It Started with an Internship

It’s a commonly accepted fact that in order to succeed in something, you have to surround yourself with people and ideas that push you in the right direction. To that effect, I want to make it clear that, when you become a 4PSA Clouder, nothing can stop you from becoming the next rock star in software.

The Early Years

When I started writing code for a living, everything seemed freakishly complex. Why? Because there was no one around to guide me through the rough terrain of learning different APIs at once, to point out the mistakes in my design, and offer advice on how to code better and faster.

Read More

REST Best Practices: Managing Concurrent Updates

In a previous article, we described how to choose a HTTP method when implementing operations that affect resources. Today, we are going to explain how to implement services that manage concurrent operations on a resource and how clients should use such services.

The Problem

Sometimes, Apps must handle concurrent updates on a resource. Just imagine an application that acts like a Wiki, where users read, write, and edit articles.

Read More

The Apps Team Takes The Scene

In one of our previous articles, we provided a short intro on 4PSA’s internal organization. Today, you can have a closer look at the Apps Team.

Who We Are

We are a bunch of passionate young developers who like taking up new challenges. Ranging from interns to seniors, from designers to coders, from cheerful to introspective, and from inquisitive to amenable, there is one thing we all have in common: we want to build great Apps.

Read More

REST Best Practices: Choosing HTTP Methods

We do a lot of REST in the Pineapple team. We love REST. Why? There are many reasons:

  • It is standard, so that creating services always follows a pattern
  • Developing clients is super easy, in all programming languages
  • Programmers can easily understand it
  • Testing (of all types) can be easily automated
  • Because it relies on HTTP, it’s highly scalable infrastructure wise
  • We can choose the preferred data format for sending and receiving information – usually JSON 🙂

Read More