Redux is one of those concepts that is so damn hard to explain, and even harder to understand. For me at least, React was a lot easier to understand at a high level. I mean, React at a high level is basically just objects minus inheritance plus one way data flow. Or function composition with some enclosed state if you’re into functional programming. Sure, there’s a lot more to it once you get into the nitty gritty, but really that’s all you need to know to start writing React code.
I’ve gotten approached by a fair amount of “entrepreneurs” recently. Granted this is completely my fault; I put my name up on the NYU Entreprenurship Lab’s wall under developers. And putting all the jokes and snarky remarks aside, there’s a lot of genuine misunderstanding between these entrepreneurs and developers. I want to clear some of them up with some “rules of engagement” for developers.
So let’s say you are the founder of a startup called Breakr, Tinder for break dancers.
I’ve become interested in programming languages recently. This interest stemmed from Bob Nystrom’s wonderful book Crafting Interpreters. Reading the book, with all the wonderful diagrams and simple code snippets, has given me the idea of writing my own language. However, what kind of language should I make? Right now it feels like the programming world is bursting at the seams with new languages. Golang, Kotlin, Swift, and Rust have all appeared within the past few years.
Hi! This is my first post on the new Horribly Underqualified. I created the original version of this blog last year. However, it quickly fell out of use, partially because I found a job and partially because I couldn’t be bothered to maintain the Rails app it was built upon. For this blog I’ve decided to take another route. I’m using Hugo, a static site generator. That way I can have a blog with minimal effort, while also having it look (significantly) nicer than the previous iteration.