Re:How knowing Lisp destroyed my programming career (2006)
by sedachv on Wednesday March 14, 2018 @06:04PM
(#16588738)
> I'm not sure if you must be able to use strace to be productive
You will be productive until whatever runtime/library you are using has a serious bug or performance issue. Then you either use tools like strace or your productivity drops to 0. It is not a matter of marginal or order-of-magnitude productivity differences. You don't "understand stuff" for sentimental reasons, you "understand stuff" because the alternative is your manager has to call in people like me that "understand stuff" and pay them tens of thousands of dollars to fix things that you can't.
> It always puzzled me how people can be comfortable using this kind of stuff.
It's called learning.
Re:How knowing Lisp destroyed my programming career (2006)
by blablabla123 on Thursday March 15, 2018 @02:47PM
(#16595483)
Wow nice. I want to do this one day too ;)
> It's called learning.
Haha
Yeah and then there's actual code writing: the heavy lifting has been done, all the functions/classes/modules/... are still small and wait to be stretched with a lot of nice code. In well sorted projects the latter is a trivial tasks for simple features.
But yes, I agree with the sentiment that there is a lack of general "understanding of stuff". I'm not sure if you must be able to use strace to be productive but it sure helps if you're able to get to know tools that are installed on most systems. Coming back to the OP's topic: LISP is a language that uses formalisms (ways to plumb ;)), tools (ever heard of asdf?) and syntax complete alien to even long-term computer addicts. It always puzzled me how people can be comfortable using this kind of stuff.