7 ms·
Otherwise written as "what programming languages are being asked about late at night." To me, who rarely pulls up SO, correlating SO questions and page views w
by falcolas 10y ago
Otherwise written as "what programming languages are being asked about late at night."
To me, who rarely pulls up SO, correlating SO questions and page views with usage is a bit biased.
- jacquesm 10y agoAnd also, languages with good documentation will be referred to less on SO.
- TimJYoung 10y agoIndeed. Likewise, software with good commercial support, software that is older and more stable/having less churn... There's a lot of SO content regarding working around JS/DOM incompatibilities between browsers. Without those incompatibilities through the years, SO might (incorrectly) think that JS usage is lower than it is.
- hsivonen 10y agoThere are also other forums. I prefer Rust’s own user forum over StackOverflow, because the latter is polluted with stale pre-1.0 answers.
- matt4077 10y agoThe article is about fluctuating interest dependent on time of day. Unless Haskell's documentation is worse at night than it is during the day, your perfectly parroted talking-point is controlled for.
- Ronsenshi 10y agoSeems to me like a perfectly reasonable correlation. During the day people might stumble on a problem that they aren't sure how to handle. They search that problem in google and end up in SO. You might not be an average SO user?
- moomin 10y agoIt's more of a problem for the "morning people" hypothesis. There's an alternative hypothesis that people work on something, get stuck, think about it overnight and are more likely to decide to ask a question in the morning.
- startupdiscuss 10y agoWhoah! The big news for me is that there is a programmer who rarely uses SO. I use it constantly. Can you say more about: 1. What your programming set up is. 2. What you do when there is an issue? I didn't know there was a reasonable alternative. I do the Google -> SO a lot. The only time Google brings up a different page is if the question is REALLY basic like how to use a function. Edit: added this postscript: I have found a lot less need to look up things like "are there optional parameters in .len()?" because the IDE helps with that. I need to look up strange errors that I don't understand. (Like when you install a new library and your code breaks). Those are almost never in the official documentation because they didn't plan for it.
- scalatohaskell 10y agoI very rarely use stackoverflow as well. Last time was probably week ago when googling something bash related. AMA
- startupdiscuss 10y agoWell, let me ask you the same questions: 1. What is your development environment? 2. What you do when there is an issue?
- cstrahan 10y agoI'm not the parent, but here's what I'd do (and, indeed, have done): Read the manual: https://www.gnu.org/software/bash/manual/bash.html https://www.gnu.org/software/bash/manual/bash.html Just sit down one weekend, and read it from beginning to end. The information contained therein is just about exhaustive. Assuming you touch bash scripts daily (as I do), there's really little excuse for not mastering the language. Referring to SO every time you stumble into an issue is inefficient compared to the one time cost of actually developing working knowledge of the subject at hand, and it also limits you to the canned solutions that a bunch of random people on the internet have proposed. I'd bet my money on you being more capable than a random stranger -- assuming you've read up first. When I was at an earlier stage in my career, I'd hit up SO every time I ran into an issue. And then I had the realization that I could just read up on: * The spec for your language(s) * The source code for the compiler and/or VMs that power your language(s) * The manual for the software you use * The RFCs that apply to you * Both the public API and the internal source code of the libraries you use * Etc
- matt4077 10y agoSelf-selection by, for example, inexperienced users is probably a valid criticism of using SO data for inferring a ranking of languages–although my impression is that they are at a scale where this is less and less relevant. In this case, the point the article is trying to make is actually something different: "What languages do people use for fun", and I'm having a really hard time coming up with any plausible alternative explanations for their data.
- onion2k 10y agoPlus someone who is doing dev work at night is more likely to be working alone and they won't have an office full of coworkers to ask before they Google. That's bound to skew the results a little.
- matt4077 10y agoUnless there are some secret Sharepoint Nightclubs or Subversive Subversion Speakeasies I have yet to find, that would affect all languages, and couldn't explain these day/night patterns.
- ikeyany 10y agoI was thinking that some languages like C++ take a lot longer between "tests" (e.g. compile times) and are thus more prone to be worked on at odd times.
- soheil 10y agoI always feel guilty asking questions from coworkers when the answer literally takes me a fraction of the time if I Googled it and opened the first SO link.
- falcolas 10y agoIMO, if it's something that I'm asking a coworker about, SO isn't going to have an easy (or correct) answer. For example, I am attempting to use a namespaced library installed with Pip in my Lambda function. It doesn't work - can't import the library. Google gives a bunch of noise. SO gives a bunch of noise. The solution? Asked a coworker, got an answer back immediately. Import the 'site' package, and set up the current working directory as a site directory. This makes the library .pth files work properly.
- Jtsummers 10y agoNo reason to feel guilty. Questions are good, and it keeps communications within the team going. Silence is worse. As I said in a cousin comment, it also helps your office/team discover what knowledge is lacking. I used git there, but linux (unix in general) is another example in my office. So many of my colleagues have only done Windows-based applications, or embedded (running a one-off RTOS or an off-the-shelf RTOS). We've been moving workload to embedded linux (for reasons), along with moving some development work to linux (because of tooling available there). If everyone googled it, they may get their answers. But no one would realize that it was a systemic issue because there's no communication.
- johndubchak 10y agoThere are some languages, like C++, where the first place to go seeking answers isn't SO. C++ devs tend to look at http://en.cppreference.com http://en.cppreference.com (using an English locale in this example). To me, it tends to bias the sample towards the subset of developer population using SO, which would not be a representative sample size for a true population sampling in a statistical problem - it would be oversampled in one group to the exclusion of all other groups.
- startupdiscuss 10y agoWell, what kind of things do you look up? I have found a lot less need to look up things like "are there optional parameters in .len()?" because the IDE helps with that. I need to look up strange errors that I don't understand. (Like when you install a new library and your code breaks). Those are almost never in the official documentation because they didn't plan for it.
- johndubchak 10y agoI was speaking partially from my experience and, as another poster put it, IDEs help considerably in areas of syntax usage. Besides, with more stable languages (C++ has a 3 yr standardization cadence and new features are not covered well on SO) you can find in-depth answers on SO. Otherwise, many mailing lists (yes, they still exist) are a better source of more current and more detailed treatment of the topic than, "hey, how do I do X so that I can move on to my next thing at work." Don't get me wrong, I love SO, but I feel it's more about, "how do I solve this problem now?" vs "I want to learn more about this topic." It's real value is in the comments that others contribute "around" the accepted answers.
- falcolas 10y agoYup, cppreference is a great resource, and fast to find answers in (I've found).
- smitherfield 10y agoDespite the name, cppreference is the best online (there's always `man 3`, of course) resource I've found for C, too. MSDN is good for C++ as well (usually the second place I check). And the GCC and Clang documentation is generally pretty comprehensive about compiler-specific stuff. The C and C++ sections of StackOverflow are good for finding language lawyers who can give you an exact answer, with citations, to "is this snippet well-defined?" type questions (the TL;DR is usually "if you have to ask, then it isn't"). But they'll scold you for tagging those sorts of questions with both C and C++, even though it's perfectly reasonable to do.• — • If you're asking about C, it's helpful to know whether your program will still have the same behavior when compiled as C++; if you're asking about C++ but your snippet doesn't have anything C++-specific, it's helpful to future viewers if the answers for both languages are in the same place, since more often than not they're the same (which also means it's helpful to make it clear when they aren't).
- bradleybuda 10y agoAn alternative interpretation is that C# devs are willing to ask for help at any time, while Haskell devs can only summon the humility to ask for help after they've been suffering all day. :-)