This is about definition and classification in the codes
because there was lots of wrong words in plain meaning in English, Korea, etc in codes
What happens is we sometimes use languages for variance purposes in everyday life. but we do not really touch indepth in code and computational thinking.
In 2011, 12-Factor app distributed “12-Factor App methodology” in cloud. this was for Cloud developers who are working with Native cloud apps
but The problem started when they suggested in terms.
Here is what bugs come when they write it like this; “Config should save into environment variables”
Explaination was perfect. because dev, staging, production environment is different in every config so it needs to be done all the time.
but the confusion starts when the terms come into the code. What Setting means is that program reads and translate in behaviorial option. but Environment is something that externally definite by its existance. but “Environment variable” is in between of setting and environment.
when the 12-Factor said that config should save into environment variables” it completely confuses the meaning between setting and environment.
so When some coders says “I put env file into setting” like that. it makes all the wrong concept and all the confusion starts when developing and distribution stage.
So My Solution is ..
Very simple. We do not touch on the things that are too rooted in the codes but make a different definition and terms in the right way. so that we are no longer confused by it
Now Let’s make the terms more accurately
-
Setting -> Preference: Programs read and write and modify it
-
Environment -> Substrate: Program lives by it, cannot change it because its conditional existance like Earth
-
Injection: Substrate gives value to Preference in one-way. not both ways.
That way we can classify all the terms more exact way. and think more exact ways. I am going to continuously make the terms in dictionary ways. so that everyone who gets to read the files and codes more efficiently.