I find it interesting how during the daytime hours, most languages are in the Microsoft camp...
What programming languages are used late at night?
61–70 of 244 posts
Re: What programming languages are used late at night?
#62Otherwise 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.
Whoah! 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 ha…
I'll go!
Day job is C#, and C++ mostly, with a good bit of Java, bash, perl tossed in. Personally, I find MSDN sufficient for most of my questions re: C#. For the rest, mostly blog posts, TBH.
Side projects I use Python. Again blog posts and docs are all I need.
I wouldn't say I never use SO, but I can't remember the last time I posted a question and I rarely use it as a resource for looking up information.
Re: What programming languages are used late at night?
#63Re: What programming languages are used late at night?
#64What I'd really like is the correlation between different kinds of tools, languages etc. and forced overtime...
Re: What programming languages are used late at night?
#65"Learning haskell" is pretty much in the same category as "Write that novel I've been thinking about."
Learning Haskell has been made much easier with Haskell Book[1]. Unlike LYAH, it actually has a ton of exercises and in-depth explanations so you understand the why behind things as you make progress. That said, it requires discipline to read through. [1] http://haskellbook.com/
The big problem I've had with Haskell is that even after gaining a pretty good understanding of the language (including monads and such) I still can't fathom how to do anything real with it.
Exercises are great and all, but once I try to go past exercises, I start getting lost in layers of monad transformers, and I struggle to figure out the "right" way to do anything. It just feels like there are all these layers of abstraction and complexity that are required for even simple applications, and I can't seem to reach the point where it all clicks for me and becomes manageable.
Reading the TOC and chapter notes for that book, I'm not convinced it'll help me. Even the "final project" at the end of the book is described as "a little weird, but small". I don't need more weird, small examples, I need a full-fledged application! I've tried picking out random Haskell OSS apps and studying them, but without newbie-friendly documentation to walk me through the code, I find it very hard to follow what's happening....
Re: What programming languages are used late at night?
#66Earlier quoted context omitted.
Whoah! 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 ha…
1) Python, Bash, and Go in a mix of Vim, Sublime text, and PyCharm. 2) Look at the docs (of which I always keep a local copy), and the source code (of which I try and keep a local copy). I want to understand not only how to solve the problem at hand, but what caused the problem. Not understanding the cause of the problem will lead to a solution which will only sometimes work, because it misses some other leak in the…
Agreed with this 100%, reading the source code of well documented libraries is highly valuable. I feel that personally it helps be better understand the internals and what I can leverage. The documentation in Spring's source is really great, along with their reference docs online.
I've had similar experiences with SO being out of date or kind of poor - when I run across those I have been trying to add a newer answer (I do a lot of Spring so I run across this a lot).
Re: What programming languages are used late at night?
#67"Learning haskell" is pretty much in the same category as "Write that novel I've been thinking about."
Except in his 5th chart (the animated one), all the enterprise technologies and Haskell all pulsed up in the morning and afternoon local time, while Haskell was the only one to also pulse up in the evening. In fact, Haskell's evening pulse was smaller than its daytime pulse.
It's easy to miss the explanation there. Everything tops in the working hours, the article is about the relative size of those tops.
Re: What programming languages are used late at night?
#68Earlier quoted context omitted.
There have been a bunch of 20% projects; but only recently have they started any full-time Haskell work, as far as I know.
One of the biggest(.) Google projects with Haskell is probably Ganeti ( https://github.com/ganeti/ganeti ), which is a mix of python and Haskell and has been around since 2008ish (although Haskell was introduced later, iirc). We recently moved our main development to github so the repo seems a bit empty, we're certainly happy to get more contributors if you are interested, as the community is fairly small and special…
[deleted]
Re: What programming languages are used late at night?
#69Earlier quoted context omitted.
I very rarely use stackoverflow as well. Last time was probably week ago when googling something bash related. AMA
Well, let me ask you the same questions: 1. What is your development environment? 2. What you do when there is an issue?
I'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
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