Yeah, I did it again; I went several weeks (more than a month!) without posting anything. This time, it’s not laziness, I promise 🙂
I started a new book! This book will be on how design patterns evolve when functional programming (specifically first class functions and lambdas) mix in with an object-oriented language. I’ve already got several chapters written!
I also got a new job! I’ve been pretty much unemployed (and underemployed) since July of last year (so, for over a year now), but I finally found a job! It’s an exciting opportunity, but I have to move 2.5 hours away, so a lot of my life will also be devoted to getting ready for that.
I have a few blog posts planned out for you guys, and maybe I’ll get to them soon, but don’t expect anything before I’m done settling in, early in September.
Lastly, I’d like to get my spare book copies out, so I’ll just go with the simplest way to get rid of them: ask for them in the comments! I have 8 left. Just comment below, include your email address, and I’ll contact you privately to get your shipping details. This is first-come-first-serve.
Hello, dear readers, and welcome to my thoughts on the MVP (Model-View-Presenter) pattern, which I finally got around to learning. I had tried before, but everybody always explained it so abstractly that, even when compared to MVVM abstractly, I couldn’t tell what it was. But I recently got to see the pattern being implemented in some live-coding episodes I don’t really have a whole lot to share; I’m focusing on one mini anti-pattern within the typical implementation that I’d like to provide alternative ideas for.
General Thoughts on MVP
First, I will give you my overall thoughts on MVP. My first thought about it is, “Is this really any different than MVC?” And truly, MVP is pretty much what I had always thought of MVC to be. The problem wasn’t MVC, in my opinion, but what so many people had come to think MVC was. Having heard what Uncle Bob has said about MVC, it’s clear that there has been severe “evolution” to the community’s understanding of MVC, but the MVC I was taught in college is almost exactly the same thing as MVP, with all the differences being negligible compared to the differences between my understanding of MVC and so many others’ understanding. Continue Reading
Last week, I showed you my new implementation for instance-level properties in Python. This week, we’ll take another look at it by implementing a few Delegated Properties and helpers to make using them just a hair nicer.
Recreating Kotlin’s Built-In Delegates
For inspiration of what Delegated Properties to create, we’ll start by recreating the ones built into Kotlin, starting with
Lazy. Continue Reading
A while back, I did a post on making instance-level properties in Python where the implementation of it required inheritance as well as messing with
__setattr__(), which are a little dangerous to mess with. Then I had another idea last night (as of the time of writing this): Use normal descriptors to delegate to “Delegated Properties” (name taken from Kotlin, the original inspiration). These Delegated Properties can be designed very simply in a way that they only have to worry about the value on one instance, instead of figuring out how to store the value per instance. Continue Reading
Well, my Watch Later playlist on YouTube is extra full now! A bunch of videos from really big programming conferences have just dropped.
PyCon 2017: 144 Videos!
Google IO 2017: 158 Videos!
Now, obviously not all videos are going to interest everyone, but there’s something for just about any Python programmer in the PyCon list, and I only went through the Android videos for GoogleIO and I got 10 videos added.
With Google IO came a really cool announcement for Kotlin-Android developers, too: Kotlin is now getting first class support from Google for Android!
Sorry about being terrible at keeping up to date with my blog; Legend of Zelda Breath of the Wild is partially to blame, but it’s still all my fault 🙂 Even this new post isn’t a proper post.
I just wanted to make sure as many people as possible have heard about the latest Humble Bundle! At the $1+ level, you get Automate the Boring Stuff with Python (a pretty decent book; I’ve looked through it), Doing Math with Python, Teach Your Kids to Code, and the No Starch Sampler (No Starch Press is the publisher of most, if not all the books in the bundle). At the $8+ level, there’s Gray Hat Python, Python Playground: Geeky Projects for the Curious Programmer, and Python for Kids. In the final, $15+ level, you get Black Hat Python, Invent Your Own Computer Games With Python, and Python Crash Course: A Hands-On, Project-Based Introduction to Programming.
This is a crazy deal, since most of these books are worth more than $10 individually. PLUS, the money you pay can be divided however you like between No Starch Press, HumbleBundle.com, and the Python Software Foundation! I focused mostly on supporting the PSF, but made sure to share some with the other two as well. I hope many of you go and purchase some level of this bundle and help support Python and Python publishers!