3 ms·
> using a language with _very_ limited expressiveness (C#) is not very productive. o_0. Think you need to check yourself mate. I believe the productiveness
by Quarrelsome 8y ago
> using a language with _very_ limited expressiveness (C#) is not very productive.
o_0.
Think you need to check yourself mate.
I believe the productiveness of more "expressive" language tends to be undermined by the loss of productivity that occurs when you're compelled to write blog posts or comment on hacker news about how amazingly productive and expressive your language is.
- btschaegg 8y ago...as if we wouldn't be writing comments on HN anyway. ;-)
- rubber_duck 8y agoI can do like 3-4 hours of productive work a day realistically - after that I lose focus. I can push this in some periods - but that's the ammount of time I limit myself to be functional over long term. If I need to waste that time sifting trough boilerplate than I'm pretty upset because I get less shit done in that time window. Chatting on forums is a casual brain teaser and keeping up to date on industry stuff.
- Quarrelsome 8y agoI would suggest using more personal language when expressing personal opinion and toning down the force (very). > [I find that] using a language with limited expressiveness (C#) is not very productive for me. Like, I'd figure you can be mad productive in any language (even COBOL?) although I'm only completely cosy in a couple. There's no need to be so dismissive of the tools that others use.
- weberc2 8y agoI don't think "expressiveness" or "boilerplate" are the things that slow me down. I use Go, and I find that it is both expressive and a little verbose, but it's still very simple and there's usually one clear way to do things, so I find that I can move a fair bit faster than I can in C# _or_ Haskell (in the latter case, it might just be that Haskell has a huge learning curve and I'm nowhere near over it).