The problem with programming in a language that is bad (in some way) isn't just that the language is bad (in that way), but that the other programmers it attracts are OK with it being bad (in that way). Which is itself bad unless people in charge recognize it and work to fix it.
-
-
I don't think I would want that in a team setting. You can alter it for the better .. or for the worse. I prefer not to live in a company specific programming language full of tribal knowledge I can't prepare for.
-
There is always company specific software knowledge. In most companies, the knowledge is not language-encoded and programmers must manually do the job of macroexpanding the actual domain language into their rigid framework. And changing the domain representation is unaffordable.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!