Coding in an IDE is a jarring experience in comparison to writing one's thoughts, ideas to make it better [in_progress]

In comparison to writing, coding in an IDE is a jarring experieince,. there is so myuchj that is happenng mentally that it appears there is something constantly playing in our mindfs,. what makes this different from typing out our experience? what are the key differences between the two? when typing out our experience, there is one flow, flow from thoughts to wiriting, the faculty of memeoty is not employted. as and when thoughts are coming up they are bing wruitten. there is no additional element of thinking invoilved. thinking processing is not required. but you type as move you move through the mental image, as we move through the experience. whereas when we are coding in an ide the experience is very different, the communication although similar is broken due to a variety of easonas, reasons such as auto-completion, failing to remember the order in which arguments need to be passed to a function. moving back and forth between what was typed and then making edits, the direction of editing is not one. the direction is up and down both. whereas when typing out our thoughts, it is linear. it is in one direction. what was written before is not edited. but in coding that is not the case. there is another element of lookup that is required. solutions need to looked up parameter order needs to be looked uip, one needs to deal with having sent the parameters in the wrong order. there is strong element of emeory recall involved here. since it is a different language memort recall cannot be relied as much as when typing out in english. because in english it clear, one knows what to write to express what one is going through. however, that is not the case when writing code. there is translation required . one needs to translate tghe instructions in the programming lanugage that one writes,. and if the memory is not strong, it does bhave information about functions their parameters orders, there is constant obstruction in the flow of writing code. one needs to switch hop onto a new tab search, hunt and peck. this is an entirely type of operation when compared to writing code from memortm, or to be more preceise when typing our instructions in plain english. this branch out, hunting and pecking is not required. there is a free flow. there are no obstructions because of memory absence or memeory recall failure. the scope of failures when writing driectly in ebnglish is also less. however, writing in english is more wordy too. writing in prgoramming language is simpler, instructions are simplief. it is a sign language. it is as if a mother is signalling a child that the child is going top get it from her for the mischief that he is doing. this reduces the total numbers instructions that need to be given to get a task done. this translation layer helps in communicating more efficiently. hwoever, the symbols need to be committed to memeorty for this to operate efficiently. otherwise this hunting and pecking mechanism obstructs the overal process. then there is an element of autocompletion too that obstructis the flow. in phpstrom when i am typing dash after an object it automatically adds the angle bracket that is the right angle brakcet, so in this case the enviroment that i am typing in filling out what needs to be written. the input from the neviroment in obstructing the flow of information, the flow is interrupted. actions in the environment are magically assisting me in writing. these forms of assistance are not deliberate, due to which the communication flow is interrupted. because i wasi ntetnding to type dash and right angled bracket however, the nevironment comes in and fills up the infromation. this assistance in unasked for and it interrupts. of course this is very different, much different from the assitance that is a resukt of deliberate seeking, it is like invoking a magical mantra and getting access to an astra from a universe. this is intentional. it is not magical. one knows that something is going to come up because one asked for it. hoqwever, in the case of writing dash after an object one ends uop getting a right anfgle bracket without even having asked for it,. there is a jolt. a minor jolt in the communication. that, hey! i did not even intend to do this and it happened automatically. this automatic event in the environment is interruopting,. whereas other things that such as function auto generation are not. one is asking for it. this is not much doing everything by hand. writing everytihjng step by step. it is about how the enviroment is assisting in the overall wirting process. whenever autocompletion happens automatically when it is unasked for it has jarruing experience. jarring uin the context of not being trayumatic but in the context of interrupting the flow of communication. however, whenever autocmpletion is asked for, it is a powerful device, it helps in writing faster. one knows what is coming, one asked for it. it is not a surprise. surprises obstruct the flow of communication because in the flow of communication writing the right angle bracket or a character was essential, however, t hat took place automatically. this adds a break. but hey during our tough times do we not need some magic to occur and help us? help us unasked for. this is always happening in the natural world, unasked for elements are arising in the enrivonment - pleasant or unpleasant. however, this is much different from communication. communication or speaking is a different activity. there are no obstructions that are influencing the process of communication in itself. atleast in most of the cases. of course if the air content were to change one may need to cough and there will be an obstcution. but this is very different from the obstuction that is created when tyoubng code. it is as if one wanted to speak about a certain topic and before uttering a word some voive in the environment in the same voice as yours auto-completes it. you are stumped for a moment. the flow is interrupted. you need to recoup and then start agasin. there is a hop. so this needs to be eliminated. these automatic assistances need to be eliminated. and then one needs to exercise their memory to make sybmol language communication efficient. the functions that are useed need to become second nature to make communication flow seamless and eliminate the steps that are a result of wanting to hunt and peck the parameter order, the parameter purpose. this needs conrete effot to make the symbol lanuage communication efficient. otherwise one will alway be stumped when communicating the symbol lanuage. a mother will always need to recollect what needs to be done to communicate syumbolically, this step will burdne the entire process. one will rather using the ‘normal

‘ lanugage and communicate.

another element that is obstructing the overall coding experience is our typing efficiency. how easy it is for us to type how typing has become an ingranied part of ourselves. how keyboard has become integrated into us. the more keyboard becomes a part of us and extenoin of us. the more simpler the overall typing experience or the cfoding expereince becomes. there are no errors. no error correction tracks that our mings needfs to constantly rake. in the case of speech there is no error correcftion tracke required. there is a free flow. and the other element is removing obstructions in the IDE. the ncironment in which we type also needs to remain consiustent. as coinsustent as possible. in the case of speech there is very little from the environment that obstructs the process of spearkin. of course in some contexts this might occue, ie: when the temperatue changes. we it becomes colder it might become difficult to speak. but such changes are rare. if the ide is good, good in the context of the IDE understanding how humans operate, this wilkl be rare. however, ig it is not, it is best to change the IDE or make modifications if they allow suych mdofgiciations to be done. now look at this articvle in the present state, it has vbeen typed. there are errors,m but there are no corrected. because correcting them will require me to swtich into an error correction tracfk which will obstruct the overall expression of thought. of course i am not type code as fast as this. but the ibstcdution that correcting errors creates is clear and the ebenfits that one might reap oiin not correcting these errors would also become evident if one is willing to reflect upon the overall rtyping experience. one could write their thoughts on something without correct typing mistakes and with correct typing mistakes and then see how they overall expereince is. there is going to be distinct difference in how the mind or the branin feels. this is connected with the way in which wer alsoi realted with failures. once that becomes better. correcting mistakes should also not become or ramin that bursendome however, the overall epxerssion of the thought flow will still become interrupted. perhaps something that can be minisned, or something that one should train for./ because obnstructions are alwayus beinmg created in the enviroment and it is best that we train ourselves for the natural evnrionment thatn train ourselves for isoloated envionrments,. train ourselves such that it onstruicts our ability to function in the natural enviroment. which is full of surprises.