Category Archives: Uncategorized

You heard it through the grapevine…

We have a couple of wine aficionados in Santex – Mariano Brolio and Maxi Sbrocca! This month, we asked them to tell us a bit more about their particular taste for the subject.

When did you first discover your love for wine?

Mariano Brolio: About when I turned 22. That’s when I started noticing different varietals (wine made by different types of grapes) and observing what I liked about each one.

Maxi Sbrocca: I think I’ve liked wine ever since I was a kid in high school — probably around 16 or 17 years old. Basically it’s something I’ve always enjoyed. What’s changed over time is the quality of wine that I like!

How would you describe your expertise? Have you ever taken formal classes?

MB: I don’t really consider myself to be an expert. It’s just that over the years I’ve learned which wines I like and which ones I don’t. I never took any lessons or classes, but I have gone to different degustations and events where they teach you what kind of food pairs well with each variety of wine, but these were always in relaxed and informal settings.

MS: I believe that the world of wine is one of great dimensions. Truthfully, I consider myself to be a novice when it comes to wine. I like it a lot, I enjoy it even more, but I’m a long ways from being a person who can provide recommendations about wine. I simply like talking about the wines that I like. I’ve never taken any classes, but I wouldn’t be opposed to doing so at some point.

Which Argentinian wine would you recommend to a friend traveling from abroad?

MB: It depends on what he/she is looking for. The top selections from the most well known bodegas are all really good. One wine that I always recommend is Altura Máxima. It comes from a finca, or ranch-like estate, in the Calchaquíes Valley at almost 10,000ft above sea level and is one of the best wines I have ever tasted. It’s produced onlyin relatively small batches, so I can never find a place to get it outside of Salta. If you can’t try that one, then the collection Fincas Notables from the bodega El Esteco are also really good.

If you haven’t noticed, I almost always recommend wine from the Salta region. They tend to be my favorite.

MS: As I said with the previous question, Ithink I’m a beginner when it comes to being able to recommend kinds of wine. But if I had to recommend one to someone, it would undoubtedly be a Malbec. Ruttini and Catena Zapata are good premium brands.

Have you tried wine from other places around the world? Which regions do you prefer?

MB: I’ve tried wine from Chile, Australia, and the U.S. I didn’t really care for any of them very much – I’ve tried much better ones in Argentina. I’ve also tried a reserve wine from Spain that a friend brought over from a trip. It was pretty good, but again, you can find similar Argentinian wines that are similar or better. Maybe my palate it just used to Argentinian wine haha.

MS: I’ve tried wine from the U.S. and to tell the truth, they weren’t very good. At least the ones that I tried weren’t. I’ve also tried Australian wine which was equally bad. Obviously with the wine we produce locally in Argentina, we have very high standards. There is a really good wine from Chile that’s a variety called Carmenere. They say that it’s the only place where that particular vine can be grown. It’s really tasty.

Is wine just a hobby for you, or do you see it turning into something else in the future?

MB: Yea, for me it’s just a hobby. A few years ago, a friend and I wanted to start our own business. Some boutique bodegas began to send us their products to sell them online and to family, but for the sake of time, we couldn’t keep up with it.

MS: Today, it’s just a hobby. As a consumer it’s something I enjoy, but I wouldn’t throw out the idea of it becoming something more in the future.

What is your favorite way to enjoy a glass of wine?

MB: There are two moments that I always enjoy most with wine:
– At an asado with friends, enjoying different bottles
– Once the day is over and I can relax and drink a glass, maybe with some nice cheese or pasta.

MS: I think the best way to enjoy a glass of wine is at a great asado surrounded by friends and family. I view wine as a means, not an end. It’s something that brings friendships together even more. This doesn’t, however, exclude those special occasions when you can enjoy an excellent glass of wine alone.

Internet of Things: Challenges

By Sebastian Pereira, Information Systems & Processes at Santex

The Internet of Things, or IoT, is the inter-networking of physical devices, vehicles, buildings and other items embedded with electronics, software, sensors, actuators, and network connectivity which enable these objects to collect and exchange data.

Wikipedia states that the first discussion around “a thing” that was interconnected was a Coke machine that would determine how many drinks were available.

IoT use cases include several applications that range from connected homes, consumer electronics, industries, retail, logistics, government, automobiles, among other areas.

But if it’s been around for so many years, perhaps with different names but with the same discussions in the background, why we are not surrounded by all these things already? Jayson DeMers in his Forbes article states that part of the problem is too much competition with not enough collaboration –  something that discourages and delays the revolution. It is also encouraging bigger companies such as Google, Amazon and Apple, and taking a step into the problem, that they might drive that collaboration with their own applications and infrastructure.

This  competition and little collaboration can be seen as symptoms of a much bigger problem that pose a series of challenges that everybody will have to solve and agree upon for the revolution to come. We are talking about a potential market of billions of dollars for services and applications that range from apparent trivial things to more complex and with higher impacts on societies and economies.

Following are the top 3 challenges I think we have on the horizon with IoT:

  • Security. This is mainly based on the fact that IoT implies more and more devices will be connected through networks, and therefore there will be more opportunities for hackers to exploit. The one thing we learned over the years is that no one is secure, and basically more interconnected devices means more problems – at least more problems to be solved.

To serve as a terrifying example – one of many – take a look at this article, where hackers stopped a journalist’s car in the middle of a highway to prove their point: they can control a car remotely, mentioning this scary scenario: “Imagine last year if instead of cutting the transmission on the highway, we’d turned the wheel 180 degrees,” says Chris Valasek. I can imagine. But he spells it out anyway. “You wouldn’t be on the phone with us. You’d be dead.”

  • Connectivity. If we go back to the definition stated at the beginning of this article, IoT implies that a lot of devices are interconnected, and aside from the security challenge, this means there will be more efficient ways to have all of these devices talk to each other. The (now) classic way of connecting devices as a centralized paradigm for authorization and connection of different nodes within a network may be heading to a decentralized model, such as Fog Computing. With this,  data, computing, storage, and applications are distributed in the most logical, efficient way between the data source and the cloud. There are other solutions where the decentralization is higher, but certainly each option is tied to different security challenges.
  • Making sense of the data. Does Big Data sounds big enough? Imagine something even bigger than. IoT will pose the challenge of cleaning, processing and interpreting vast amounts of data produced by sensors. Gartner estimates that there will be 25 billion connected things in use by 2020.  Internet networking specialist Cisco ISBG’s forecast is of 50 billion connected devices. To have an example of this from the airlines industry, at last year’s Paris Air Show, Bombardier showcased its C Series jetliner that carries Pratt & Whitney’s Geared Turbo Fan (GTF) engine, which is fitted with 5,000 sensors that generate up to 10 GB of data per second.

So basically, applying analytics to IoT has the same general approach on a different scale: how data is collected and how it is interpreted/how can be used. This Forbes article states that applying Machine Learning to analyze the data will be a more efficient option. Given that the current manufacturers of sensors and IoT applications are not experts on analyzing and getting good quality information that can be actionable, new services start to appear on the horizon. One example is Machine Learning As a Service, where buyers can quickly get the insights they need without making huge investments in technologies that are not core to their business.

Of course there are many other challenges with IoT and many problems to solve, but that’s what makes this so interesting to talk about it and work on. Other challenges that can be mentioned are:

  • Power
  • Sensors
  • Standards
  • User Experience and User Interface
  • Waste Disposal
  • Data Storage
  • Laws and Regulations

It certainly states a huge opportunity for business, whether for good or bad purposes.

Sources:

Things to keep in mind before adding a Software Dependency to your project

By Agustin Aliaga, Mobile Developer at Santex

In my work experience, one basic thing I learned about software engineering is that you don’t need to “reinvent the wheel” every time you want to achieve some functionality. Open source projects have revolutionized the way we work in that we can reutilize existing software in addition to collaborating with others devs. In the web-development ecosystem, there are plenty of frameworks and tools that already simplify things like user authentication, routes, templating (client-side and server-side), state-management, database queries, web sockets, etc. On the other hand, however, sometimes the existing solutions are just not good enough or it may be that there are no alternatives at all, but that’s a completely different story.

The ability to know when to implement the feature yourself and when to use an existing solution will be a crucial asset for your team. Adopting a new library, language or technology as a dependency to build your product without extensive research could become headache in the future, so you should always ask yourself at least these questions about it:

1. Does it meet all your needs?
Sometimes you’ll find a solution for your problem that does not cover all the specific features you need. In that case, you might have to deal with forking and extending it (if it’s an open source project), and this means greater time investments and costs. Are your team and the client prepared for this scenario?

2. Is there any documentation?
If so, is it well documented? Just as an example, one of the things I like the most about Django (web framework) is the quality they put into the docs. It’s remarkably easy to find the topics you need for the framework version you’re using. https://docs.djangoproject.com/en/.

3. Is it supported by a “big” community and/or a private company? Having a company or a community behind it helps a lot when you’re having trouble and need assistance from others. You may have to send a “help-desk” ticket (probably if it’s a paid service), find information on blogs or StackOverflow, or maybe even post a question to those sites. If you’re relying on the community to help you, your chances of being helped are proportional to the popularity of the software dependency.

4. Is it an “external service”?
If you rely on services like “Google Maps API”, “Facebook Graph API”, “Google’s Firebase”, etc. be aware that they may change in the future without notice, or they could just stop working at any time (temporarily or permanently). SaaS/BaaS solutions are great but you should think twice before setting them up as a critical piece of your system. Just as an example, read about what happened to Facebook’s Parse: (https://techcrunch.com/2016/01/28/facebook-shutters-its-parse-developer-platform/).

5. Is it actively maintained and improved?
If hosted on Github, “Pulse” and “Graphs” tabs will give you an idea of the latest activity. You probably don’t want to set up an outdated library, because it could bring retrocompatibility issues to your project. Also, if it’s constantly evolving, sometimes it could mean you’ll have to update your code repeatedly.

6. Is it tested?
Some libraries use automated tools to build and test every change that is introduced (applying continuous integration tools like Travis CI, Circle CI, etc.). This makes the library more reliable.

7. Are you compromising another dependency if you adopt this new library?
Sometimes libraries don’t play well together.

8. Will it affect your product’s performance, speed, size, etc.?
You should always take this into consideration. In the “web environment”, a giant front-end library could affect the browser’s performance and also increase network transfer times. On the back-end side, you want to avoid server overloading. In the mobile world, things get even more critical because mobile phones don’t have as many resources as a desktop computer. In Android, an app that wastes memory and CPU is a real candidate to be killed automatically by the operating system.

What about Android ?

The core-functionalities that Android brings to the table are sometimes more than enough to build simple applications. You could build an entire app by using bare Activities, Fragments, Views, AsyncTasks, Services, Content Providers, Broadcast Receivers, etc.

But in my experience, sometimes this means you’ll have to write (and then maintain) a lot of repetitive/boilerplate code. In other words, sometimes sticking to the core framework means you will have to invest more time to taking care of all the details. Some examples of libraries that made me more productive in Android development are: Retrofit, Dagger 2, and Butter Knife.

You should also know that if you add too much direct and transitive dependencies (plus your own code), you might exceed the “64K-method limit”, explained by Android documentation:

Android app (APK) files contain executable bytecode files in the form of Dalvik Executable (DEX) files, which contain the compiled code used to run your app. The Dalvik Executable specification limits the total number of methods that can be referenced within a single DEX file to 65,536—including Android framework methods, library methods, and methods in your own code. In the context of computer science, the term Kilo, K, denotes 1024 (or 2^10). Because 65,536 is equal to 64 X 1024, this limit is referred to as the ’64K reference limit’.”

If you exceed this limit, you’ll have to change your application to support “multidex”, which means it will have to load multiple dex files. This will produce higher compilation times, and also performance/loading issues in the app itself. So I’d recommend to always be careful with the dependencies that you add to your Android project.

Conclusion

I have seen these concepts apply not only to Android development (a technology I use every day at work), but to all software development in general. Every product relies on dependencies (whether it’s an OS, a service, a framework, a library or some other kind of software). The goal is to pick the best ones to maximize your productivity, without affecting your product’s performance, scalability, and capacity to evolve over time.

When (in my opinion) Not to Use Drupal

By Sebastian Gonzalez – Drupal Developer at Santex

I would like to clarify first off that I love to work with Drupal. I’ve been working with the Drupal platform for about 10 years now, and through all those years of getting frustrated over the same things, I realized something. I noticed that when certain clients or businesses had a previous project in Drupal that was successful, they would want to handle any future projects in the same way, when in reality Drupal may not have been the best tool to use.

In all these years of experience, I came across various projects and had a lot of different experiences – some very rewarding and others not so great. In some of these last projects that I didn’t think were so great, I noticed that something kept repeating. Drupal was being used for any kind of project on the simple premise that “it can do everything.”

If a client needs just any sort of app, we as developers usually say that Drupal is the solution. But what we should is is that Drupal could be the solution. Changing the message from “Drupal can do that” to “Drupal should be able to do that” is fundamental to starting any project off on the right foot.

Drupal is a CMS (Content Management System) that was intended to be a content administrator. Every page in the world has content, and when we talk about ‘content,’ we automatically think that it should be able to be handled administratively. This leads one to automatically think of a CMS like Drupal, WordPress, or Joomla. For me, the important question is what you want to do with the content. Where is this going and what is it going to be used for?

A lot of people view Drupal as a CWMS (Content Workflow Management System), and I agree with this vision. In my opinion, it makes sense to use Drupal when a business’s domain entails a lot of different types of content with multiple users who have different levels of permission. All of these users can alter the state of the content, making it fluctuate through different phases of the workflow where there aren’t annotations, reports, or emails involved.

The reality is that the vast majority of websites built using Drupal should not have used Drupal. This is not because Drupal can’t do the job, but rather because it’s a waste of all its functionalities that end up not getting used. A clear case of this is with classic brochure websites or institutional sites where the content is static and hardly changes over time. There isn’t much interaction between users beyond basic contact forms or a comments section.

Our world is currently dominated by mobile devices. Drupal was able to enter into the competition with its latest version 8, which came out in November 2016. Using and integrating components with the popular framework Symfony provides a robust back-end to facilitate API development. Drupal is jumping onto this trend with something called Headless – an architecture that uses Drupal as the back-end paired with a framework to present the data, which could be AngularJS, React.js, or any other framework.

In summary, I believe Drupal should not be used for:

  • Simple brochure websites
  • Single-purpose apps (like a chat application)
  • Gaming apps

I think Drupal should be used for:

  • News websites with multiple users
  • Multi-user publishing apps
  • Any app or website that includes workflows among people with different roles/permissions
  • A mobile version for Drupal

To conclude, here are 4 more pieces of advice:

  • Choosing one tool or another has to do with understanding the business’s control over the application or website. The more you know about the project, the greater the decision power in choosing which platform to use to meet those needs.
  • Use Drupal from the start and don’t try to switch and start using it for something else when things are not properly in place.
  • Stop saying “Drupal is the solution” and starting saying “Drupal could be the solution!”
  • Always explore alternatives because new technologies are coming out everyday.

Those are my two cents.

 

About the Author – Sebastian Gonzalez is an experienced Drupal Developer at Santex,  passionate about his work.  Sebastian is a strategic team player always willing to contribute and to solve problems.

7 Tips for Automation Testing

Luckily today, the term Automation is becoming more common and popular in the immense world of IT companies. You just have to search a little bit in the web to find hundreds or thousands of articles in all languages talking about the benefits of automated testing and how much money companies can save using it, so it is not my idea to repeat the comments of my colleagues, but rather to share some of my experiences across more than 5 years of working as a QA.

I worked on 3 giant projects: the website of a major airline, a video on-demand provider, and a security application of one of the most famous antivirus services. I also participated in small projects where manually running the same test suites every day, up to 3 times a day, made me realize how necessary and beneficial it is to automate.

Automation Blog image

Here are 7 tips I learned from automating that I would like to share with you:

  1. The Code Reviews of other QA and/or Developers as well as those from POP or the BA are of GREAT importance.

  2. Reuse code. Writing the same code over and over again can be a waste of time when the changes in the data set are minimal.

  3. The tests have to be fail-proof, they should only fail due to errors in the product, environment, etc. and not because of a bad analysis made before creating it. This also includes the Unit Test.

  4. Ask for help. We are all proud people and it is a huge satisfaction to complete a challenging task without having to turn to someone for help, but sometimes pride translates into hours that only lead to losing time in the sprint, money for the client and the company, and can even delay the tasks of our peers.

  5. Respect good practices. When working as a team we must remember that our code can affect the code or work of others.

  6. Automated tests are not only a good tool for testers but also, when used correctly, can be very useful for developers.

  7. Adapting is very important. Sometimes because of licensing issues or for a number of other reasons, we may have to automate in a language with which we do not feel comfortable or simply do not like. Despite not enjoying it when it happened to me, I understood that the language was the right one for the software to be tested, and today I can say that at least I have some experience in other languages and technologies that will surely be useful again throughout my career.

Hopefully these tips can help testers and developers who are not yet familiar with Automation to understand more about its importance. At Santex, we are always open to sharing knowledge and listening to new experiences and opinions, so feel free to leave your thoughts on automation.

About the author: Mauricio Ardiles is an enthusiastic QA Analyst seasoned in a variety of testing skills. Strong background in automation testing and a certified Scrum Master. 

 

One day of Singularity University at The Tech Pub

Blog1

This month at Santex, we had the pleasure of hosting Peter Wicher, Director of Strategic Relations at Singularity University. Over his extensive career, Peter has held executive positions in Silicon Valley in the industries of consumer electronics, semiconductors, education, and integrated systems.

We asked our Director of Operations, Eduardo Coll, to tell us a bit about the experience.

SANTEX: Tell us a bit about what Singularity University is and what it stands for.

Eduardo Coll: We had the pleasure of having Peter Wicher from Singularity University (SU) visit our Tech Pub. SU is a university created and founded by Peter Diamandis and has sponsorship from Google, NASA, and Autodesk, among other large companies.

Its vision is to create technology solutions that can make a positive impact on a billion people. There are 7 billion people in the world, and SU is trying to impact 1 billion. The university has unique programs for both individuals and organizations. They also have an incubator where they work on projects across verticals, which are selected because they aim to resolve some of the great problems facing humanity today – like renewable energy and access to drinking water. One of the concepts that they promote in SU, which Peter Wicher explained to us during his visit, is the concept of “exponentiality” – exponential technology and exponential growth.

SANTEX: Elaborate more on this concept. Where does this exponential growth in technology go?

EC: For humans by nature, it’s easier to understand linear growth. We grow older lineally; we don’t pass from 2 to 50 years old without turning 3, 4, etc. We physically grow in the same way, as we gain weight in successive numbers, and therefore we tend to forget that there can also be exponential growth in certain things. SU strives to leave its students with the ideology that exponential growth can be applied to our daily lives and that we don’t have to act within a linear mindset. This enables people to more rapidly achieve their visions, and helps the university reach its goal of impacting 1 billion people.

The motto at SU is “don’t make something better by 10%, make it 10x better!” When you think about changing or creating something, you don’t have to make something new that’s 10% better than what already exists. You should strive to make it 10 times better! When you do this, your business or your technology or idea will grow exponentially. Some familiar examples that they point out are: Uber generated a revolution in the transportation industry using technology that was already over 10 years old – cell phones, GPS, web services. They simply made it into an app and the number of trips, drivers, and passengers increased exponentially. They created an exponentially better transportation system.

SU also mentions Airbnb, who also revolutionized the hospitality system with the idea of renting homes and individual rooms for a lesser cost than staying in a hotel or vacation house. These technologies and systems are disruptive, and obviously have their flaws. They have problems that occasionally  need to be fixed that need to be observed in their entirety, but we’ll save that for another article.

SANTEX: How do some of concepts learned during SU’s visit pertain to Santex currently?

EC: Peter brought us some lessons that really dazzled us, lessons that we should apply to our lives daily both as an organization and individually. With existing technology and new technologies to come, the objectives that SU presented to us will be made simple.

At Santex, we are beginning to understand and work with the concept of exponential growth and the use of technology to solve some of humanity’s biggest problems. As a company, we want to support our clients with the knowledge needed to help them grow, which in turn will help us grow as well. We’ve set the goals of improving 10x more for every new project that we take on, and striving to solve problems that help not only our clients, but us as an organization and the community we’re involved in.

About Singularity University (SU)

SU is an academic institution in Silicon Valley whose focus is to bring together, educate, and inspire leaders about the exponential power of technology to solve some of the greatest challenges facing mankind.

A journey to fitness and health

By Sebastian Gonzalez – Drupal Developer at Santex

My journey begins in early 2014, at the time I went to see a dermatologist for a few spots that I found on my legs. The dermatologist told me that it was acanthosis pigmentaria, and that they were due to my being overweight. At that time, my weight was about 110 kilos (242 lbs.) or a little more, had a very poor diet – lots of take out, lots of soda, many processed meals (bread, pastries), only a few vegetables and no fruit.

Sebastian GonzalezparablogchicaI signed up for a gym without a clear idea of what to do: that I should lose weight. At first, they recommended that I start on the stationary bike in addition to an exercise routine that was, at the very least, boring. Those were the first few weeks, and then little by little I began to like the routines that the coach was giving me and I started to enjoy training at the gym. In the meantime, the coach started demanding more and more of me.

When it came to my diet, I knew that it was the key to losing weight. Little by little I started changing certain eating habits. I started to plan my meals and set a day when I could eat more fattening foods (I still eat sandwiches and pizzas on my “cheat” days). I had to change my breakfast habits too – I used to not eat breakfast at all or just grab something quick on the way to work. I stopped drinking soda and eating certain foods at night.

Within the first 14 months, I lost almost 30 kilos (66 lbs). At a first glance, this seems like a large number, but I did some calculations and it evens out to about 500 grams (about 1 lb) per week. The truth is that weight loss is not a consistent progression. Sometimes I lost 500g per week, and afterwards weeks would go by where I would plateau and not lose even 1 gram. It’s times like that when you need to learn to be persistent and not give up, and just continue trying day after day. It’s not an easy journey that one sets out on to try to change or improve one’s life, but the people by my side supported me and encouraged along the way, and they didn’t let me fall. It’s also nice to hear when friends or coworkers comment on the weight you’ve lost and how they notice your body changing. That’s encouraging.

Today, my food plan is quite varied. My breakfasts usually include yogurt, fruit, granola, and peanut butter. My lunches focus on protein like beef, chicken, pork, and eggs, in addition to a healthy source of carbohydrates like broccoli, spinach, sweet potatoes, and brown rice. Dinners also revolve around a protein and lots of veggies like lettuce, tomato, carrots, arugula, cabbage, etc.

When people ask me how I lost so much weight and totally changed my body, the first thing I say is that you have to have persistence and the drive to keep going. There are going to be difficult moments in which you feel anxious and want to buy everything at the grocery store! But you’ll see how your body changes bit by bit and you’ll feel stronger and have more energy. You won’t get as tired at work – you’ll sleep better at night and feel more awake during the day. You can’t put a price on those feelings. I always recommend doing a physical activity, whatever it may be. If you like soccer, play it. If you like to run, go do it. If you’re a gym person like myself, be methodical with your training plan. Whatever the activity you prefer, the important thing is to stick to it.

My journey continues, and each day I strive to improve my diet and improve my training. I try to communicate my life experiences with others so that they feel motivated to become more physically active. With a little bit of perseverance you can achieve big things.

Trends for IT Execs and CIOs to Aniticipate

By Juan Santiago, CEO & Co-Founder of Santex

events_gartner

Gartner Symposium/ITxpo is the world’s most important gathering of CIOs and Senior IT executives. Attendees gain an unbiased and insightful perspective on what the future holds for the industry. This year, Santex’s CEO Juan Santiago traveled to Orlando, Florida, to attend the Symposium in October. Here’s a peek at what he learned, and what trends we can expect for the IT industry in the near future.

 What were the 3 highlights of the Symposium?

My Key take-aways are:

Data is king!

Organizations that learn to maximize the value chain of their ecosystems are the future.

Digital Platform + Leadership + Business Contribution = Your Ecosystem.

The market is Customer-Value-Centric.

Customers that get value, and feel valued, will advocate for your business:

  • Create communities, user groups, and advocacy programs for customers.

  • Embrace a wide range of advocacy activities to let customers help you in ways that work not just for you, but for them.

96% of satisfied customers said they would be willing to participate in reference/advocacy activities.

Strategic marketing, sales and practice leaders must tell their story in the customer’s context. This suggests aligning messaging to desired business outcomes and related roles of their buyers both in IT and business.

Context in this case means explaining value in terms of vertical markets and business imperatives that could be externally or internally facing (e.g., digital supply chain optimization vs. collaborative engineering).

What are the most important trends in the IT world that were discussed at the Symposium?

Product Innovation

TSP CEOs are using innovation projects and leveraging digital business to drive growth through better engagement with customers. Investment is being driven toward sales and customer-facing roles instead of toward new product development or cost-saving measures.

Cloud Strategies

Strategic planners need to identify and address the opportunities and risks associated with the shift in IT spending due to the adoption of cloud computing. Providers must ensure they are the beneficiaries of cloud shift in order to minimize legacy revenue erosion and maximize cloud revenue growth.

Go-to-Market Secret Success

Technology buying teams, in both midsize and large enterprises, work on multiple categories of purchases at the same time. To improve marketing and sales effectiveness, TSPs must develop deep understanding of accounts to ensure that their offerings stay high on the enterprise’s diverse list of priorities.

These are the key trends I see in the market today.

 Strategic Trends:

1. Disappearing Data Centers
2. Interconnect Fabrics
3. Containers and Applications Steams

Tactical Trends:

  1. Business Driven IT
  2. DCaaS – IT Delivers Services, NOT Infrastructure
  3. Stranded Capacity
  4. IoT

Organizational Trends:

1. Remote Device (Thing) Management
2. Micro and Edge Computing Environments
3. New Roles in IT

How does Latin America fit in the market?

Huge opportunities!

With globalization as it has progressed today, many Latin American countries have fallen off the wagon due to their political and economic challenges. That is rapidly changing and as technology paves the road to lower costs of easier product and services adoption. Markets become less regulated, and more investments and more reliable infrastructure set the perfect stage for more countries to jump back on the trends and take advantage of them.

At the same time, may Latin American countries, such as Argentina, are extremely well positioned to provide the necessary talented workforce when it comes to IT development, due to its higher level of education, cultural fit, and competitive cost to countries, like the US,  where IT talent is scarce. It’s a known issue and companies see this as one of their primary roadblocks to scalability.

So, I guess it’s fair to say that Latin America, for the first time in many years, has it both ways.

What are the new challenges that CIOs have to face in the industry?

  1. Fear to change and how that will ultimately affect their job and organization
  2.  Access to talent
  3. Leaner processes
Most CIOs know they need to see these new trends deployed within their organizations or they could potentially be out of business. The questions is how you go about it.

Many CIOs have their strategy in place and are eager to implement some of these changes. Yet they are faced with lots of red-tape, internal politics, cultural resistance, and the right leadership in their key people whom they rely on for a successful outcome.

How can you apply what you’ve learned to Santex?

I see that we are moving in the right direction.

A few years ago, we embarked on a path of disruption and innovation –  both internally and externally. We set out to become a composable company, and we did it!

Today, I see that the foundation can propel Santex to face all these new challenges, as strong as ever before.

Our long term vision and organizational changes that we have faced in the past two years will prove invaluable to the company in the years to come.

Despite our relatively modest size as a company, I’ve learned we are at the cutting edge of many of these trends. All that is left is to continue the path we have chosen and expand upon it.

 

Running Your Business Like a Successful Software Project

Rethinking the concept of corporate management – Business Agile Management and Design thinking approach

By Walter Abrigo & Celeste Torresi

A new tendency is emerging in which software project management techniques and principles are taken outside of the IT world and applied to other forms of business. This is the idea behind Agile methodologies and design thinking.

Agile methodologies were first introduced in the ‘90s as a backlash against the strict and structured methodologies that existed at the time that were based on the Cascade model.

Specific cultural factors carry a lot of weight in being able to successfully implement Agile methodologies. Although Agile teams, projects, and individuals exist outside of the IT world, a change in mentality is required for those businesses that want to be completely Agile.

The concept of design thinking began at Stanford University in the ‘70s, where the concept was used to analyze and solve complex problems collectively by focusing on the viability and feasibility of ideas and putting people at the center of observation.

This theoretic framework implies that organizations should forget structured responses when tackling problems, and instead address them in a new way with an innovative solution.

The reality of businesses

Corporate processes help ensure that managers and directors make appropriate financial and management decisions to lead their teams effectively and control deliverables and quality produced in the final products.

 However, such processes can quickly become strict and rigid, centralizing all of the authority and information of a project or business. Such aspects are contrasted in the Agile Manifesto, which indicates that value should be places on: people and interactions related to processes and tools; complete client requirements with documentation; client collaboration in negotiating contracts; and response to change regarding concrete plans.

Screen Shot 2016-10-14 at 4.00.24 PM

An organization that aims to adapt itself to the changing needs of its clients requires an organizational structure that is as efficient as it is functional. An Agile organization meets these needs by reducing hierarchies and minimizing excess communication, creating autonomous groups that are interdisciplinary and transverse.

Our Focus

In conjuncture with our formal and conventional structure, Santex built an Agile framework from which three teams are formed to manage the core processes of the company: Sales, Human Capital, and Development, These teams work collaboratively to achieve common objectives.

Screen Shot 2016-10-14 at 3.50.56 PM

This demonstrates how Agile methodologies can be limited not only to development teams, but can be applied throughout the entire organization as a vehicle for improving the company as a whole.

Furthermore, maintaining the quality parameters of CMMI and ISO norms as a reference, we strive to reduce inefficiencies and obstacles with daily and weekly meetings, backlogs, and metrics.

This enables us to achieve extraordinary results for the three critical processes in the company. In examining our client relationships, the Net Promoter Score (NPS) that we earned during Q2 of 2016 is 87.5. Our rate or retention for clients and collaborators so far this year is 91.21%, and our development processes have achieved an efficiency rating of 85.3%, with an annual improvement of 12% this year.

Designthinkin.png

With special emphasis on our clients and aspiring to add value to every project from start to finish, Santex creates prototypes and project models with diverse technical content and close attention to detail. We try to observe the client and put ourselves in their shoes, brainstorming and testing different ideas to create the best possible solution for them internally and externally.

Overall, we concentrate our everyday management on the concept of continuous and incremental improvement while simultaneously forging space for creativity and innovative proposals with each project. Our three core competencies are applied throughout our organizational culture to reinforce the implementation of these concepts: effective communication, flexibility, and result-oriented performance.

The Concorde Fallacy

By Annett Koegler, Co-founder at Santex

Why we finish movies we aren’t enjoying, stay in bad relationships, hold on to investments that are underperforming.

 

When you lose something permanently, it hurts.

In order to avoid this negative feeling we do irrational things. You probably have been to a restaurant and ordered something terrible, but you ate it anyway. You didn’t want to waste the money, so you suffered through it. Or you went to a concert even though you did not feel like or something else was more interesting. You still went in order to justify spending money you knew you could never get back. If you can identify with any of these stories, you fell victim to the sunk cost fallacy, also known as the Concorde fallacy.

The Concorde was a joint development program of the British and French governments that continued when the economic benefits of the project were no longer possible. It was designed to be a supersonic passenger aircraft but its lasting legacy resides mostly in game theory, where it has been adopted as a description of irrational behavior.

image-concorde presentation

The fallacy is known for valuing a project based on how much you’ve invested, its “sunk costs”, rather than on its real present value.

If its value is negative and future costs outweigh future benefits, you should abandon it, regardless of how much you’ve already invested. No decision can influence what you’ve already spent, and only future costs and benefits should be allowed to affect decisions.

It is difficult to overcome our own irrationality, we take general good rules and misapply them. We tend think of money we’ve already lost as being ‘still on the table,’ and if only we increase the commitment, we could get it back. To leave would force us to admit our mistake and deal with the cost.

“Pride goeth before destruction” – Proverbs 16:18

Why?

One explanation is the reward that is placed to fall pray of the fallacy by our institutions. In politics for example we do not pay the price for being wrong individually, since not one person decides the election. We usually make voting decisions that are biased and ill-informed. Unlike politics, the market does often punish those who fall for the sunken cost fallacy. Companies are rewarded for overcoming people’s biases, while vote-seeking politicians are rewarded for gratifying them.

Another explanation is loss aversion. From a psychological point most people prefer to keep their losses low, even if it means enduring a bad experience.

We humans are unique. We like to hang on to investments that we know are going to fail, in an effort to recuperate the money already invested.

We stay in careers that make us unhappy, since we are already with the company for 10 years and it has to get better as some point.

We don’t realize that the time and money you’ve sunk is irrelevant, because it is a backward looking decisions.

The exact reasons why people pay attention to sunk costs are not clear, but the smartest choice is most likely to walk away and cut your losses, something most are not will to do. Our decisions should be for the future and not for justifying the past.

“After a crisis we tell ourselves we understand why it happened and maintain the illusion that the world is understandable. In fact, we should accept the world is incomprehensible much of the time.’” -Daniel Kahneman

About the Author – Annett Koegler is the co-founder of Santex. Former web developer and now managing the global financial affairs of Santex. Growing up in Communist East Germany, building a company in the United States, Argentina and Peru, and living across multiple continents, her life is far from basic. If you can’t find her behind her desk or on the next airplane, she is running, paddle boarding or exploring some undiscovered parts of this world.