It’s time that I got a bit more real with you guys. Pretty much ever since I learned Python, I’ve been touting it as a super amazing language. I’ve been doing the same with Kotlin, but this is about Python.
Now, this doesn’t mean I’m going to be changing my tune from here on out; after this, I’m not really going to bringing up the weak points of Python. I’m just going to continue talking about strong principles, practices, features, and tips and tricks. But this article was just inspired by a small revelation, and I decided to just roll with it.
That inspiration was due to the revelation that the official Python logo looks vaguely like a yin yang symbol (apparently, it’s called the Taijitu). To prove it, I made an alteration to the symbol, changing just the colors.
So, let’s look at the pros and cons of Python. Continue Reading
Oh yes; another article that attempts to defy traditional thinking. First it was that static methods are fine. Then I told you that Singletons are fine. Now, I’m saying a case can be made for multiple assertions in a single test. This will be a short one, too. Continue Reading
My book can now be found in Kindle format on Amazon!
Since I don’t have a way to send any mass emails or anything to my followers, I’m going to have to require my followers to contact me in order to for them to get their free pdf copy of my new book.
If you’re a follower of my blog and want a free copy, email email@example.com, mention that you’re a follower and give your wordpress/gravatar id (so I can verify that you’re a follower), and I’ll send an email back with the book.
I’m sorry that you have to 1) go through the small hassle of sending me the email and 2) see this post to even know how to get the book.
This one’s gonna be short. Honestly, I don’t know how last week’s article about static methods went so long.
Singletons get a bad rap, being called Anti-patterns, and for good reason. The biggest reason given against Singletons is that they’re global state, which is bad. If you want a stateful “Singleton”, there are ways to restrict the application to only having a single instance, even if the class can have multiple instances. While this still largely equates to global state, at least it opens up the possibility of test doubles and makes the “Singleton” itself that much easier to test. Continue Reading
Hey readers! I finally finished publishing my book, Python Descriptors: A Comprehensive Guide! It is currently available on Lulu, and will eventually be available on Amazon, B&N, and other sites. It comes in both a Digest size paperback or ebook. So, go check it out and buy a copy, if you’d like!
For my followers, I’ll work on getting the deal out soon. Also, if anyone who has a blog, podcast, or other public content and would like to do a review of my book, I’ll get you a free pdf copy of the book to do the review from! Email me at firstname.lastname@example.org and let me know.
I’ll soon get an additional blurb on the site’s sidebar so that it’s easy to find a link to the book.
Today, we’ll be talking about something controversial: static methods. I have yet to read anything that says static methods are good and useful, other than Effective Java recommending them in the use of static factory methods. There are some really interesting (and somewhat dumb) arguments out there against them that rarely, if ever, even get explained. Notably, I’m providing a rebuttal to the article, Utility Classes Have Nothing to do With Functional Programming.
Today, we’re going to look at the good and bad of static methods; what they’re good for and what they’re not.