Before you automatically disagree, stop a bit and think about it. Can you think of any code you have ever written that did not handle data of some sort? Of course not. This is not about relational data either, it is about any data. There is no software that does not process data. Even the textbook example of some function that squares a number is processing the parameter and returning a value. The first line of that function, in most languages, names the input parameter and its type. That is a schema.
This remains true as you climb out of the toy textbook examples into simple one-off programs into small packages and ultimately to apps that build to megabytes of executables running on a rack (or a floor) of servers. Just as each method call has parameters, so does each class have its attributes, every table its columns, every XML file its XSD (or so we hope) and that code works if and only if everybody on the team understood what was supposed to happen to the data.
Are We Talking UI or Platform or Middleware?
Generally today we are talking about the server side of things. This is about any project that is going to take a user request and consult a data store: the file system, a search engine, a database, a NoSQL database, or an XML database. If you go to the disk, that is what we are talking about.
New Versions Are (Almost Always) About Schema Changes
So imagine you've got some working code. Maybe a single script file, or perhaps a library or package, or maybe some huge application with hundreds of files. It is time to change it. In my experience new code means some kind of change to the schema.
I cannot prove that, nor do I intend to try. It is a mostly-true not an always-true.
Schema Here Does Not Mean Relational
This is not about relational schemas, though they are included. If you are using Mongo or some other NoSQL Database which does not manage the schema for you, it just means you are managing the schema yourself somewhere in code. But since you cannot write code that has no knowledge of the structure of the data it handles, that schema will be there somewhere, and if the code changes the schema generally changes.
Does It Need To Be Said?
Sometimes you will find yourself in a situation where people do not know this. You will notice something is wrong, they first symptom is that the conversation does not appear to be proceeding to a conclusion. Even worse, people do not seem to know what conclusion they are even seeking. They do not know that they are trying to work out the schema, so they wander about the requirements trying to make sense of them.
Order and progress can be restored when somebody ties the efforts down to the discovery and detailing of the schema. The question is usually, "What data points are we handling and what are we doing to them?"
Update Contact :
No Wa/Telepon (puat) : 085267792168
No Wa/Telepon (fajar) : 085369237896
Email : Fajarudinsidik@gmail.com
No Wa/Telepon (puat) : 085267792168
No Wa/Telepon (fajar) : 085369237896
Email: Fajarudinsidik@gmail.com
atau Kirimkan Private messanger melalui email dengan klik tombol order dibawah ini :
