You are here |
tyrrrz.me | ||
| | | |
adventures.michaelfbryan.com
|
|
| | | | One of the first things I learned when programming professionally is that global variables are bad. We all take it for granted that its bad practice to write code that relies heavily on global state but the other day I was working with a 3rd party native library, and it reminded why these best practices come about. There are a couple factors which made this particular librarys use of global mutable state rather ugly to work with, | |
| | | |
degoes.net
|
|
| | | | Functional programming has a bit of jargon, but that doesn't have to stop you from understanding core concepts | |
| | | |
journal.infinitenegativeutility.com
|
|
| | | | Something I've had puttering around in the back of my head for ages now is My Perfect Application Language. There are languages out t... | |
| | | |
bmbumpus.com
|
|
| | Many real-world problems can be formulated and modeled in the language of graph theory. However, real-world networks are often not static. They change over time. These structures are called dynamic or temporal graphs. Here's an example of temporal star with four leaves; each one of its edges is active twice except for $latex cz$ which... |