DEV Community

loading...

Self Oriented Programming (SOP)

aiosifelis profile image Andreas Iosifelis ・2 min read

It's the first day at your new job.

You have been waiting for a job like this for a long time. You're eager to get github access and checkout the code of the project you have been assigned.
You open your vscode, open the embedded terminal and type git clone blah blah.

You first look at the folder structure and you realize that something is very wrong with this project. There is no particular logic in the naming of the files and folders.
Then you open a file to take a look at the code. Oh, my, goodness...

With that said, I would like to introduce a term for describing a very old coding style. SOP aka Self Oriented Programming.

Like OOP (Object Oriented Programming) SOP has a very particular logic behind it.
When you first see code written in the SOP methodology, immediately you have no clue what the heck is going on.

Variables with no particular naming pattern, Method names that are misleading and logic that just works but you can't figure out why.

In SOP, the most important thing is that only you and only at that moment, understand how your code is written and what it does. I mentioned only at the moment, because it doesn't really matter if you open the project again after a year to fix a bug.

Bug?
Bugs are enemies of the SOP pattern. They don't actually exist when you use SOP. If something doesn't work, you don't try to fix it by changing the code, you fix it by changing the mindset of your user.

Here are some examples of the SOP methodology. I'm going to be using java_script! =)

class Ajax() {
    constructor(first_name, lastName, e_mail, password) {
        this.firstName = first_name;
        this.last_name = lastName;
        this.user_email_address = e_mail;
        this.password = password;
    }

    public makeRequestTo_Server(url, params) {
       return axios.post(url, params);
    }

    private sendRequest() {
      return axios.get(url);
    }

    private sendRequest2() {
      return axios.post(url);
    }

    public makeRequest_V2() {

    }

    public login() {
      let pmrs = { 
         email: this.e_mail, 
         password: this.password,  
      } 
      return axios.post('/api/login', pmrs)
    }
}

function writeDataToUser(userIsNotDeactivated = false, usr) {
    if(!!userIsNotDeactivated) {
       var req = new Ajax(usr.fn, usr.lnm, usr.eml, usr.pwd)
       req.login()
    }

    const dt = usr.items.forEach((item) =>  
         req.items.push(item))

}
Enter fullscreen mode Exit fullscreen mode

In the above example it's pretty obvious that the developer used the SOP methodology. Them and only them understand why this code was written and what it does.

Can you think of other examples/cases of the SOP methodology?
Drop a comment below.

Discussion (0)

pic
Editor guide