1,042 karma · joined March 26, 2016
Also, that cost of living for Portland seems high.
https://www.coursera.org/specializations/algorithms comes to mind.
How is this different than toning down the ego a notch when trying to make platonic friends, while trying to be confident when looking to make romantic partners?
'-ese' is also used heavily in Italian.
The reddit mobile site takes 13 seconds to load on my Nexus 6 over wifi. Then it has the nagware ad to try to get me to install the app, which only has a tiny 'go to mobile site' link directly underneath the large 'continue [to download]' button. Once reddit has finally loaded, every link will then first ask you if you want to view the link the app, before allowing you to continue. Meanwhile the UI, while cleaner, is debatably worse off UX wise as everything is now small and laggy.
So to summarize, it is terribly unperformant app, filled with dark patterns and dubious UI improvements.
I wind up doing a ton of array/collection manipulation in my daily work, and I'd want to make sure any new members of the team could at least speak the same language.
My advice to the author is: choose ImmutableJS, Ramda, OR lodash. Don't choose all three.
I think that is his anti-pattern.
> I could be more productive if I didn’t have to wonder things like ... “Should I mutate this variable?”
If you're doing FP the answer is likely 'No.'
I imagine they correlate an over interest in CS concepts with said group.
You're saving a few characters to make the code less obvious. Please correct me if there's some other benefit.
One more question (restated from below):
Coming from FP where immutability is sacrosanct, I often wind up writing classes that are largely immutable, which doesn't seem like correct OOP. Is there a proper way to marry immutable data structures with OO?
So you attach functions that operate on a data structure to the data structure solely for organizational purposes?
Seems almost identical to defining a record and module of functions that operate on said record. Except that in OO, by attaching the functions you create new copies of each function with a bound reference to the instance of data structure. Are there other advantages?
But what if I don't want to mutate the source data? I always wind up writing classes that are largely immutable, and it seems wrong from an OOP perspective. Is there a correct way to marry immutable data with OOP?
Functional programming in general clicks with me, however.
This is obviously an anecdote, but I think it's logical those who had bad experiences and did not end up developers most likely do not read HN.
This is what I'm betting on. The 'creases' story may have some truth to it, but I suspect its primary goal is to take over the narrative and distract from the actual methods of identify the leak.
Is this assuming the car is parked outside the entire day or just the 8 hour work day?
Linux, a reasonably memory efficient text editor, and some chrome tab discipline is all it takes.
In end, however, Docker dependencies eventually forced my hand to upgrade.
Speaking of which, I'm kind of blown away Apple hasn't tried to take all their touch expertise from the iPad and add it to MacBooks in some fashion.
At this juncture (1.2 and rather successful) is there any feasible way for the maintainers to switch the nomenclature to something a tad more literal/expressive?
Learning Scheme as my first language scared me away from programming for years. Yes, solutions to problems were often elegant and puzzle-like, but accordingly, the tools and patterns often felt constrained and roundabout. For example, consider recursive patterns vs conventional looping patterns.
In that class I often felt I wasn't learning a 'real' production programming language, but rather a language designed to teach me programming concepts.
To that point, I think Python offers a much more robust and straight forward tool set, while also being friendly enough for the young developer to sink their teeth into.
However, in retrospect I was just a bratty kid, who was learning a lot of valuable fundamentals. I'd like to think some of those have stuck with me to this day, esp. as functional patterns have come into vogue.
Not sure about these days, but ~10 years ago, my friend's family's company did not require a high school degree. To your point, however, I know this because he specifically complained about dealing with under educated employees.
From some rudimentary googling, it seems requiring a HS degree is the norm, but there are plenty of cases of forgoing the degree/GED.