After getting the GPD Win Max 2 and using it as my everyday machine bothe for work and for personal use, I’ve started enforcing the philosophy of not installing any project dependencies locally, and instead leverage containerization technology (mostly via docker). I’ve talked about this in a previous post and you can probably think of this post as an improvement on top of that.
I’ve been successfully using this following pattern both for work projects as well as personal ones, and I thought I’d like to share them.
This particular blog for example is using this configuration:
I needed to analyze some data regarding the costs of my client’s current CI system, and CircleCI’s insights dashboard–while itself is impressive–isn’t quite up to task.
Sometimes you just need the plain old “spreadsheet analysis technique” to make progress.
Here’s a quick ruby script I’ve written to get data from all the workflows for a particular project, and write them down into a csv for easy importation into a spreadsheet program.
It’s that time of the year again when I get a larger drive, refresh my operating system, and back up important files.
Ever since I’ve settled on having my home folder always be on a separated drive, it’s been really easy to change operating systems, and even moving to a different (more powerful) computer isn’t as much of a chore. If I need to upgrade storage capacity, I just copy everything in my home folder onto the new drive (either by imaging or rsync) and then make sure that when I setup the new OS, that new drive is mounted in /home.
One thing that’s been really convenient for me is the ability to even move database data along with my home folder. This has been largely because I’ve been using docker (and docker-compose) more and more on my projects.
For example, one of the docker-compose.yml configurations I have for work looks like this:
Braintree has just recently released v3 of their Javascript SDK offering a lot of improvements. Searching online for tutorials on how to integrate Braintree with Rails tend to show older articles, so I decided to write an updated one :)
This is the talk I presented during the first Ruby Conference in Kuala Lumpur, Malaysia. It’s not a word-for-word transcription, but this is mostly the same material I wrote to prepare for the talk.
The secret to creating cross platform apps is something you already know, but probably not doing.
Whenever you use a method that you know might throw an exception but shouldn’t, the rescue-log-rethrow pattern is useful to figure out what happened while preserving the contracts implied in the code.
TDD’s mantra is the following: Red, Green, Refactor. In other words: write a failing test, write code to make the test fast, and then make the code better (having the test as a safety net).
Note that some of the information on the diff presented here has been redacted or removed, due to it being proprietary. But the full idea of the refactoring is present.
While working some code to work with the Zuora SOAP API, I got bit by a strange case of inheritance behavior. It would seem that this is related to what self is bound to during the execution of the statement. Here it is, distilled to its essentials:
We’ve commissioned Dekatku to train some developers here at Mindvalley on Javascript, and it’s been a great experience so far! Today is Day 2 of the the training and we’ve covered some really deep topics.
I’ve started wearing my whitebelt again and I thought I’ll put up my thoughts and notes here for future reference.
At the start of the session we had one hour to make a TODO application. The caveat being that we’re not allowed to use any libraries or frameworks; just pure javascript.
The Student was arguing with his Colleague about a piece of code they have written.
“Master, please settle our argument,” the student said. “My Colleague insists that the return value of a method should always be an object.”
The Master was expressionless. After some a few minutes, he finally replied. “Nil.”
The Student’s face contorted into a frown, for he was confused at the Master’s reply. “Master, I don’t understand,” he stammered.
The Master saw the Student bewildered. Apparently, the Client complained that the temple construction being supervised by the Student is not going according to spec.
“I don’t get it,” the Student sighed, “the specs are right here; they are clear, complete, and in black and white. How can he tell me that I’m not following the specs?”
The Master replied “I will answer your question, but first you must help me hang a portrait.
One night during a walk, the Master visited the Student during a project. “Master,” the Student said, “why do we have to write a failing test that exposes a bug before fixing the bug itself? Isn’t it easier to just fix the bug; our Client has complained about it, I’ve tried reproducing it myself, other colleagues can reproduce it too. It’s plain as day that the bug exists.”
The Master then asked the Student for a favor.
I was working on a feature for upcloudify that will use Slack notifications instead of email notifications. One of the challenges I faced was how to build-in flexibility for generating messages. I would want that the user be able to provide their own custom notification message, but at the same time be able to provide placeholders for items like the S3 download link.
