The dependency inversion principle is one of the cornerstones of object-oriented programming. Without it, there is no object-oriented design. It’s that important.
Continue reading “OOP Fundamentals: The Dependency Inversion Principle”Windows Subsystem for Linux, or WSL for short, is a quite impressive piece of technology, and one of the best moves Microsoft could have made to attract developers. Particularly web developers.
Continue reading “Integrating your dev workflow with WSL”What is nothing? nil? null? undefined? A vast void of emptiness that fills your soul with dread? Oh sorry, that’s just my stomach.
We often think of nothing as… well, nothing. It’s when something doesn’t exist and therefore cannot be interacted with. So in our code, we try account for having nothing. No User? No problem.
&.?Ruby devs are probably all too familiar with seeing this error:
|
1 |
NoMethodError (undefined method `foo' for nil:NilClass) |
Most of the time, it’s probably due to a typo, but every now and then we end up having to do something like:
|
1 2 |
defined?(bar) && bar.foo # returns nil if bar is nil |
If you’re on Rails, or are using ActiveSupport, you can use present? or try():
If you are into object-oriented programming, you most likely have heard about composition over inheritance. The concept itself is simple: Whenever possible, prefer to compose objects rather than introducing inheritance.
Continue reading “Composition over Inheritance, with JavaScript examples”FileMaker supports bidirectional communication between a web viewer and data or scripts. So, you may find yourself doing more development using plenty of web code and JavaScript integrations.
If you’re having difficulty getting your HTML, CSS, or JavaScript to render in a FileMaker web viewer, there’s a great way to help inspect and fix it. You just need to know the hidden option to enable WebKit debugging in FileMaker web viewers.
Continue reading “How to enable WebKit and JavaScript debugging in FileMaker Web Viewers”
Over years of reviewing Ruby code, the same things tend to come up over and over. In this post, I’d like to address some of the most common code smells I find when reviewing OOP code (and Ruby code in particular).
Continue reading “Common Code Smells in OOP”I have ulte
rior motives.
Continue reading “Beezwax Web Team Code Review: a blog post with ulterior motives”
Over time, without structure, things fall apart. So give them structure, a few conventions, and start to make them more maintainable. Let me say more, at least in the context of JavaScript in your applications (or did you think I was talking about gardens or buildings or such? lol.)
Continue reading “Modularizing The JavaScript You Already Have”
