Just waiting for The Rise of Skywalker to start. šæ
You are most welcome Nicholas
A thank you note from fellow blogger, Nicholas Bate.
I forget how I came across Nicholas Bateās blog. I discovered him, and a few other great blogs, while I was a heavy user of Google Reader.
Today, Iām still a daily reader of his blog and a select number of other blogs that I find are essential to my daily reading.
Iāve been a bit quiet this year in terms of blogging, but itās starting to pick up again. Without the daily posts from Nicholas, Michael, Kurt and Curtis, Iām sure I would have packed in blogging years ago. So, thank you guys for your time.
Itās these fine blogs and many more that keep me writing and ultimately posting to the Internet. Long may it continue.
The Ruby cost at Basecamp
David Heinemeier Hansson breaks down the cost of the operations at Basecamp with a spotlight on the cost of running a Ruby on Rails product.
Working with Ruby and Rails is a luxury, yes. Not every company pay their developers as well as we do at Basecamp, so maybe the rates would look a little different there. Maybe some companies are far more compute intensive to run their apps. But for most SaaS companies, theyāre in exactly the same ballpark as we are. The slice of the total operations budget spent running the programming language and web framework that powers the app is a small minority of the overall cost.
For years Iāve heard arguments that Ruby on Rails is too expensive to run, but Iāve never seen costs for anything as big as this. And to be honest, I was surprised that this was all it was.
Sure, every SAAS product is different in what it does, how itās built and how itās run. But, the fact is that Ruby on Rails is an ideal web framework for most SAAS products and has been for years.
Iāve watched the JavaScript hype train trundle on now for a couple of years and I canāt see any clear advantage of it over Ruby on Rails or any other non-JavaScript framework for that fact. And I think developers are starting to realise this.
Given the choice between Rails and any other framework for an application, I will keep going with Rails. It doesnāt have the big hype around it that it did ten years ago, but itās still proving to be a developer-friendly and therefore business-friendly framework to build your SAAS product with.
I am catching up on some podcasts this morning.
This Rework episode with Dave Teare from 1Password is worth a listen. Especially if you are a 1Password customer.
Nighthawk sounds like a good Twitter client with its smart filters, close friends and a chronological timeline.
Lightsabers done right
A look at the different techniques used to make the lightsaber work on screen through the different Star Wars movies.
Enter the sequel trilogies, which would achieve the pinnacle of lightsaber effects by merging the various techniques from over the years. Like the prequels, the blades of the lightsabers on-screen would be added digitally, with the on-camera fights taking place with plastic prop stand-ins. Also like the original trilogy, the battles were still fought on actual sets as part of the Star Wars sequelsā commitment to trying to embrace more practical effects.
Of course, youāre bound to hit on the right combination after numerous attempts. The sequel trilogy does get it right though with the lighting effect from the lightsabers.
Itās just a shame though, that we havenāt yet seen any other colour of lightsaber than the blue and red done with this effect.
I had one of those mornings on the train where I could have just kept writing and writing. Sadly, it came to my stop and I had stop and head to work. I hope I can pick up tonight where I left off this morning.
Action versus motion
Standing on the platform waiting for the train this morning l, I opened up my Kindle app and started reading through another chapter of James Clearās Atomic Habits.
In the chapter that I was reading James clarifies the difference in behaviour that leads to habits. Thereās motion which is a behaviour that doesnāt yield a result and an action that does produce a result.
Outlining a handful of articles I want to write is motion but writing a single piece is an action. Actions are steps towards a defined outcome. Not only did I find this insightful for building habits but also how I categorise tasks.
Much of the coding work I am doing just now can be put in the action category. I implement a feature or a bug fix, and I deploy it. Deploying the change is the result of the action.
Then thereās the marketing work that I am preparing. I say preparing because that is all I seem to be doing right now, preparing. This is motion. While I am planning out something, Iām not getting any closer to the desired outcome.
The difference between the two is clear now, and it sheds new light on what I need to do to move forward.
Iāve been using a similar form of this Gitmoji for a couple of weeks now. Itās good because you can identify commits a lot easier in your history.
Life reminders continue with Nicholas Bate.