Are those also considered anti-patterns, or simply "bad practices"? The examples in the article seem to have a wider scale than the ones mentioned in your collection.
My question is, where is the line the line between an anti-pattern or simply a "bad practice", or if they are the same?
It seems a bit late for the Nintendo 3DS. I wonder if it has anything to do with shared code between this and the upcoming Nintendo Switch. Nintendo has a had an amazing year and I'm really glad they're doing this nonetheless.
This is not an American thing, it is even worse in Japan and Korea, where kids are forced to study from 6 am until late (8pm ish), and this goes on into the workplace as well. I attended an international high school in South Korea (I'm Latin American) and I felt utterly sorry for my Korean classmates. I've heard worse from the Japanese work ethics.
The reason why some languages are more suited for some things than others is due to paradigms like callbacks in JS that were fit to certain applications (the web in this case). Python is incorporating newer "paradigms" like asyncio into its language, but it feels convoluted at this point. The preference of certain semantics for different application types brings forth the same problem (convolution) if we tried to implement a single API that fits all purposes.
While I do agree that live coding can be quite boring, it is helpful when trying to demonstrate coding conventions. Learning code from a live tutorial is far easier than from a wall of code (that can be copy pasted better from a website and such). A lot of people attend these talks to learn, and it is up to the presenter to judge what best fits of the type of presentation.
I am very interested in the benefits of DNA studies and their application to cryptography. I don't know much about biology but It would be interesting to know if there's a relation between code breaking through quantum computing and DNA, and if quantum computing would ever help in figuring out DNA
I think it is the same documentary that my music technology professor showed us. While a simple instrument, it's implications were quite outstanding for its time. I wonder why it is no longer widely known.
As a recent computer science student graduate I can relate to this. It's worrisome how many of my classmates are graduating with very little knowledge on how to actually build something, rather than solving little math/CS problems. I was lucky to have taken a startup programming course they taught for one term, in which we were required to build a scalable startup from ground up. Wish me luck finding employment now!