behind-storage-os-cover-9

Behind the Scene: The Right Tool for the Job – Multiple Language Development (#9)

In our previous blog post we have seen how each language in a multiple language development environment has its own culture and how this culture can transcend into other languages. This borrowing of philosophy is a great way to enhance both your spoken language capabilities as well as your programming language skills. Using the right programming language for the right task can be a powerful asset. Each programming language is …

Continue reading

syneto-at-cebit-2015-2

Syneto at CeBIT 2015 #2

I’m writing at the end of day 1 of CeBIT 2015, and what a day it’s been! We had some very interesting storage talks and took on the great vibe of this giant event. We will be at the Syneto booth in Hall 6, Stand B49 until the end of CeBIT on Friday March 20th. If you stop by, we have one of our flagship ULTRA Series 220 storage array …

Continue reading

syneto-at-cebit-2015

Syneto at CeBIT 2015 #1

Hey folks, We’re just setting things up here at CeBIT 2015. If you would like to meet Syneto in person, you are more than welcome to stop by our booth in Hall 6, Stand B49. We are available for technology demos or simple discussions regarding data storage throughout the event See you around!

Continue reading

polyglot-programmer-cover-image

Behind the Scene: Polyglot Programmer – Multiple Language Development (#8)

Most frequently, programming languages are compared to one of two things: spoken languages or professional tools. Today we will analyze the former, and make an analogy between programming and spoken languages. This will allow us to see the advantages and challenges of polyglotism in programming, or multi-language software development. Spoken languages identify groups of people that belong together. In our society these groups are usually, but not necessary, nations. People …

Continue reading

responding to change over following plans

Behind the Scene: Agile by Responding to Change (#7)

The forth principle of the Agile Manifesto tells us that we should value “Responding to change over following a plan”. This seems pretty strait forward, right? If a client wants a specific feature we implement it, if he wants something else, we do that too. It should be the perfect way to work. We are not subject to any plan, instead we just react to whatever changes the client wants. …

Continue reading