That doesn't mean you stare at it in stupefied awe. If you can't remember what you're working on you close your computer and walk away.

i never said i stared at code in a stupefied awe. that’s your stuff, not me.

the point i was trying to convey with the phrases was my ideal attitude when writing code.

this code matters. lets think about it, get it done right and not throw it over the fence for the poor schmuck who comes along in two years time after we’ve all left.

i’ve been that schmuck. it was horrible. i don’t want to put other people through that. ever. (this is now my stuff, but hopefully explains some of the attitude).

our attitudes, intentions and motivations count when it comes to code quality. look after your code and it will look after you.

that’s what i feel. you feel different? that’s fine.

What does this have to do with a language server? It is not a tool that blinds you, nor one that puts a gun to your head and forces you to ship prematurely.

I'm just very confused how the conversation took a turn away from pragmatism and towards the aesthetic.

> > every line of code is a liability. every line of code needs to be thought about. every line of code is precious.

> I personally think this is ridiculous. It's code. It's just formal instructions. You process them and move on. It's not describing the face of god. If you need to think so much write less clever code.

you called my attitudes to writing code ridiculous. i thought i’d provide you some information on why i hold that attitude. maybe it might help you understand. maybe you may consider your own attitudes as a result.

it seems to me that you are not ready yet.

it’s nice to be able to fall asleep and someone else does the reply you wanted to do. you saved me a job. =p