matthias509
Joined 6 years ago
Joined 6 years ago
One surprising benefit was that re-learning the intro stuff well enough so I could teach it crystalized my understanding of some fundamental concepts like the difference between the stack and the heap which I kinda glossed over my first time through.
At the other end of the continuum, I was able to gain a level of skill in parallel and distributed programming and network programming much deeper than undergrad.
Was it worth it? For the price of $0 and 2 years, yes. If I was paying full price, not sure.
And do those who say the degree erodes, fundamental concepts endure. A race condition is still a race condition and a socket is still a socket even all these years later.
As you said, being aware of this lets you optimize away cache misses by controlling the memory access pattern.
Disclaimer: I work for HERE Technologies.
I get that there is a learning curve for Unix. However, a complaint about a "proliferation" in the context of a tool which is decades old seems a bit off. The response here of "just install Python" doesn't work for $random_unix for a variety of reasons. Such reasons include lack of root access or business rules which prevent modification (such as for a production system where you do have root access).
> Python can be substituted with another Turing-complete language. Why not just use libraries and abbreviate them for command line use?
This suggests that we take a tool such as awk which is decades old, stable and efficient and replace it with an equivalent implementation based on an interpreted language. This process would take years to complete and then would end up with a tool which consumes more resources and is slower than the original. I don't see the payoff here.
Both of these would be serious issues for operating a modern, large scale farming operation.