This post is a companion to our earlier blog on What is digital transformation. These articles, together, will help an enterprise evaluate the need for a digital transformation and how to go about finding a partner for the same. In this article, we present important objective & measurable ways to select your technology partner. We highlight certain requirements that are mandatory and a few “good to have” traits. As we highlighted here , Digital transformation is the planning, analysing, conducting & support of business operations via technology.
To understand Hadoop and it’s working, it is necessary to know what Big data is. As the internet grew and with the advent of Web 2.0 & 3.0, demand for data grew. Data collected and shared increased. Particularly with social media and IoT , there is an exponential growth of data stored, transacted and accumulated. Big data is an umbrella term for a large volume of data.
Data is information. Information that is used for planning, for scheduling, forecasting, budgeting, mitigating, etc. The larger the data set, more accurate the information. Hence the importance of Big data. Big data helps an enterprise to uncover information like buying patterns, demographic preferences, trends, correlations, etc. This in turns helps an enterprise discover new streams of revenue, provide better customer service, improve processes, etc. …
Uncertainty is the new normal today, with no clear end as well. Businesses, small and large, have been besieged with unprecedented challenges. Any business is constantly in a state of improvement, upgrade and transition. This is necessitated primarily by the current pandemic, then changing market economics, customer preferences, government policies etc. Business transformation is inevitable. It can be defined as changes or modification to business operations necessitated by the need to improve or due to external factors such as Covid. Digital transformation is one of the key steps in Business transformation
Is it simply the adaptation of technology in an organisation? …
CI/CD is a central part of software engineering. It is a well defined, automated life cycle for code integration and delivery to stakeholders(QA’s, Customers, Business heads etc). Central to this is automation. CI/CD or the lifecycle is built on automation. Software development teams usually consist of people with diverse skill sets. Such as engineering, quality, business associate, CxOs, designers, administrators etc. CI/CD as a discipline helps these diverse groups to communicate effectively by continuously integrating and delivering. For e.g.
Are Design artefacts available in the code repository?
Great, The CI,CD pipeline will automatically send a mail notifying the development team.
Has the latest feature merge has broken the existing flow? …
What exactly is the workplace?
Historically, a workplace was a physical location where a group of people, contractually bound, assembled to perform a set of tasks in return for something. Like a factory, a tannery, a wood cutting mill, etc Workplaces also had or provided tools, resources, machinery, and instruments that would be required to perform the tasks. Then came the digital era, or the start of computers and the internet. In this era, a new wave of jobs was created which redefined the workplace as we knew from the previous era. Instead of physical labor and the use of huge complex machinery, work began to be accomplished behind desks and desktops, laptops. Moore’s law captured this evolution very well. As electronic devices became smaller and yet more effective, digitalization revolutionized every aspect of our lives. …
How we speak to others, convey our thoughts and views, influence our quality of life to a high degree. Across cultures and geographies, voice-based communication has been the most effective way of expressing oneself. Your voice is a part of you, and it’s the most intimate form of contact with the world. No other form of communication can convey emotion and personality as our voice. One could argue in favour of haptic inputs like the sense of touch, head movement, hand gestures, etc being equally effective. But the scope of voice communication is much more extensive compared to touch-based communication.
When it comes to interaction with external systems, as with everything, things have evolved. Primitive beings used everything from thin feather quills, pigeons, fire, and smoke. The advent of printing was perhaps the greatest achievement of humankind as a whole. We then graduated from type systems, print sets to modern electronic devices to the present generation of hardware-driven input/output devices like monitors, keyboard, trackpads, mouse, etc. …
We are experiencing a period of uncertainty in our lives, the likes of which have never been seen before. Coronavirus pandemic has upended our lives. There are no fixed answers. No structured institutions or established routines or a magic wand to make all this go away. We are challenged at a level that is forcing us to introspect on a deeper level.
The first signs of the economic fallout from this are becoming evident. From global manufacturing giants to the humble household. From sprawling warehouses to gleaming corporate offices, demand is plunging everywhere. …
This article, the fifth of the 5-part article on S.O.L.I.D design principles, is about the “D,” Dependency Inversion principle made famous by Robert C. Martin (Uncle Bob)in his paper, https://web.archive.org/web/20150924054349/http://www.objectmentor.com/resources/articles/Principles_and_Patterns.pdf.
D — Dependency Inversion Principle
Robert C Martin defines DIP as
Depend upon Abstractions. Do not depend upon concretions
A. High-level modules should not depend on low-level modules. Both should depend on abstractions.
B. Abstractions should not depend upon details. Details should depend upon abstractions.
In our previous discussions with OCP, we have seen that the goal of an OO architecture is to reduce the amount of change to a module, preferably have no change. A primary source of change is a concrete implementation of a module, i.e a particular type or A specific implementation. Usually, a higher-level module will have dependencies on lower level implementations without really any need to know about it. …
This article, the fourth of the 5-part article on S.O.L.I.D design principles, is about the “I,” Interface Segregation principle made famous by Robert C. Martin (Uncle Bob)in his paper, https://web.archive.org/web/20150924054349/http://www.objectmentor.com/resources/articles/Principles_and_Patterns.pdf.
I — Interface segregation principle
An Interface is a point where two disparate or similar systems meet to exchange information. The simplest example is this article on Medium, which is an interface for you, the reader, to learn and share something with another user or from another user. When it comes to object-oriented programming and objects, an interface is a description of the behavior of a class. …