programing

It makes it easier to work with the same programing language, but it's still possible to not do so.

This kind of blog posts are super interesting and depressing at the same time:) makes me question my programing skills.

Your comment is about pure functional programing, which the linked article does not explicitly talk about.

They just define their operations/results/etc in terms of the programing language they are a JIT for.

That might be a good thing if the idea of programming in Forth excites more people than programing in TCL does.

Having a clean bridge from dynamic programing to typed programming gives us an important way to document our own learning process.

I mean, not for programing but more for another, art-oriented, tasks.

This is what I have settled into using because it is the best statistic programing tool out there.

The programming may even prove to offer more authentic and aspirational programing to blacks everywhere bypassing hollywoods imprimatur --which can only be good.

I've got a master in computer science myself, but have more respect for good programing skills than formal education.

I feel being more open minded in terms of programing languages will make you a better and more powerful programmer.

How is it that python is less amenable to functional programing?

That one single statement "systems programing language" bit Go more than anything probably as far as expectations and the number of words generated in blog posts talking about Go.

So, all the "two week programing camp" developers launch their 12-hours-from-idea-to-launch apps on top of the work of _actually_ skilled people, and all the reward goes to the final layer, not the underlying support.

Finally, some basic thinking about propositional logic can really help to elevate your knowledge above simple boolean expressions, so that you can start to think of "foralls" and "there-exists" symbols, especially when you start to talk about type theories or logic programing.

This article, and those like it, all state that the problem with multi-threading and synchronization is inherent to the programing paradigm/language/architecture you're using: > "Buggy multi-threaded code creates race conditions, which are the most dangerous and time-consuming class of bugs in software" > "because the traditional synchronization primitives are inadequate for large-scale systems." Ok.