3 ms·
It's easy, you use a language so long that you instinctually know what path to go down to find how to fix it. Either that or you take time to understand what's
by fao_ 10y ago
It's easy, you use a language so long that you instinctually know what path to go down to find how to fix it. Either that or you take time to understand what's happening in every part of the system, and you pair that with notes, a very good memory, or both. And that gives you a basis to know where to look for errors.
I took the former approach, for five or six years now (probably longer), I've been programming with lua. At some point I hit a stage where I don't have to google errors, since they're either logic errors or syntactic errors. Syntactic errors are easy to track down, since either errors are spat out, or the behavior changes in a predictable way. Hitting this stage in lua has helped me to hit it easily in other languages now as well. In my work I use Erlang, and the only thing that consistently stumps me is the architecture of the things that I deal with (Erlang happens to have fantastic warnings though, and everything else can be dealt with via tests)
- startupdiscuss 10y agoOh yes, when there is nothing to look up, I guess you won't look something up. But those would not effect the results. Presumably a good C# programmer uses less documentation just as much as a good Haskell programmer.
- unit91 10y agoWarning: anecdotes and small sample sizes ahead. True, but most people I've bumped into who write C# do it professionally, and have built up a body of knowledge. By contrast, most people I know (including me) who have messed around with Haskell, have...messed around with Haskell. I could be way off here, but I'd guess that there is a smaller percentage of mature Haskell programmers within the Haskell community than mature C# programmers in the C# community.
- startupdiscuss 10y agoI accept your view on haskell and C# distinction. I have the same view. But that doesn't mean C# users would look things up on SO more from 9-5 than they would after 5. We are talking about the same people. (The study, I assume, shows that people use C# for work and Haskell for a hobby.)