Usually when we think of Information technology architecture, we think about UML diagrams, patterns and practices, reference architectures, technology transformations, and lot more technical stuff.
Let’s start with a small exchange, experienced by almost all of us; developers at some point in their life.
Rookie Dev 1: What is that architecture diagram and the document?
Dev 2: Nothing bro, just that architect and BA had fun for 4 weeks on-site and gave us this 1 document and now expect us to design and develop the application in 8 weeks!
Recently having a discussion over a few things and career growth came to fore. As the discussion was with few of my older students (was a college teacher, in some other life… ) and colleagues, naturally it tended towards how can one grow in their career. Surprisingly, the answer from most of them was one day to become a “Manager” and manage a large team.
As you know, I have been dipping my feet in Unity3D for sometime now and have been talking to a few people. Unity has been attracting users/developers from a vast range of backgrounds, from artists to Ph.D holders and hard core developers. As with any 3d package, you need to rely quite a bit on Maths to do basic operations.
…and here is the last day of the year 2015. As the year comes to close, it is time to reflect on what has transpired during the year.
Every now and then, we, the people in IT field keep on hearing stuff about the next big thing or the latest buzzword. Be it Analytics, Big Data, Cloud and more recently Internet of Things (IoT). Every year or two, new buzzwords come up and start defining the timelines.
Truely, things are moving at speed of light and innovation is happening at break-neck speed. Things are getting connected. More and more data is being generated with each passing day. More and more sensors are getting affordable and getting placed everywhere and keep track of our life.
With release of SharePoint 2013, Microsoft has been promoting isolated space idea for the code written for SharePoint 2013. Take example of workflows, which are now hosted in a different workflow service rather than within the SharePoint server.
Similarly, Microsoft has been promoting creation of apps for SharePoint rather than deploying Farm or Sandbox solutions. This model for apps works fine for most of the times. But at times this model of running the code out of SharePoint can be a pain in the neck. E.g. There are lots of files/content that needs to be deployed within the SharePoint site itself (remember, your SharePoint team site/mysite etc. becomes the host web for the app).
Earlier we used to create Modules to deploy files into SharePoint or if we wanted to deploy any content type etc. But that model is no more available within SharePoint apps.
In my last post about the cloud, I had left out a question discussing about scalability and elasticity. During my discussions and reading about cloud and learning more about it, I was always confused about the words “Scalability” and “Elasticity” in context of cloud. Most of the times, I had found these are being used interchangeably.
But what we need to understand is that Scalability IS NOT Elasticity. Now what do you mean by that? Let’s start by examining what are the meanings of these words.
This was the question pointed right at me, while at a party, when I told a bunch of guys that I work on SharePoint solutions on cloud. It was an awkward situation to be in and somehow an image installation by Berndnaut flashed in front of my eyes.
Today’s water cooler discussion revolved around Document ID management system of SharePoint. It is a nice feature and can actually help to find the documents quickly and in a predicted manner. Basically you get a short URL in SharePoint for your document, rather than a cryptic one and SharePoint will find the document no matter where you moved it.
But there is a catch, it will be able to find it if you move it within the Site Collection. If you move it out of the site collection, a new Doc ID will be generated and assigned to the document. BOOM!! your short URL is pointing to nothing now.
So how do we move documents without changing their Doc ID?