I was listening to the Post Status Draft podcast from about a year ago where Brian, the founder of Post Status, interviews Matt Mullenweg. In their discussion they Brian mentioned the Drafts with Friends plugin and how he’d like to see something like Google Docs collaboration, editing. That got me thinking about what the MVP, minimum viable product, for that would look like… and I came up with the Request Post Feedback plugin.
To being, check out the project here. This is a work in progress, but I got enough done this weekend that I’d like to share. I wanted to work on a project using ReactJS and Redux. I’ve heard a lot about it, and wanted to explore it on my own. I do that with every technology before I bring it to the office. Since WordPress incorporated the WP REST API in the core for version 4.
Finished reading “Who” this week. I found it an interesting approach to hiring. I’d read it if I were looking for a job as well to prepare for interviews, though it’s not designed for that. Takeaways: Take hiring seriously, this should be obvious but it’s easy to let it get lost in all the other work. Manage the task of hiring as your would any other project with a clearly defined role, and process in advance.
Get a Mac! Kidding. (I actually think Microsoft has been more innovative lately.) Run the flag –no-bin-links when you install anything with npm and it will fix your issue. I have a dev Vagrant that I share with my team. I tend to mock things up when I’m playing around at home in the evenings. I work on a Mac at home. So when I confidently came into work with the plan to set up a box for my team to work on, I lost a bunch of time trying to figure out why the npm development tools I wanted, would not install.
I recently dissected an Object Oriented WordPress plugin boilerplate. This exploration was part of a project I am undertaking to explore best practices for implementing Object Oriented principles in WordPress development. When it comes to implementing coding principles, I’m generally not a purist — I aim to be utilitarian. One of the dictums I drum into my team is: “Make it work, then make it work well.” Do not take that to mean I’m sloppy, the second half of that statement holds as much weight as the first.
I’m writing this from my iPad Pro with the Smart Keyboard. It’s a beautiful experience. It’s also a natural evolution of where technology has been going. This past week Microsoft has displayed that it understands this. Apple has not. Writing here is not a perfect experience: I still think multitasking on iOS could benefit by some improvements. But I enjoy being able to reach up, touch the screen and do things.
TLDR; nano ~/.gitignore git config –global core.excludesfile ‘~/.gitignore’ Background Git is all the rage, why wouldn’t it be? You can save every iteration of your work; it’s the persistent undo button for developers. Seriously, if you’re not using it, start now. Find a tutorial, stop everything you’re doing and get on that. It will make your work 1000% more efficient. One issue I came across with my workflow is that my Mac, like everyone else’s, places a .
On August 28, 1963 Dr. Martin Luther King Jr. gave one of the most powerful speeches of all time. I know I cannot do this speech justice. But to be honest, I’m not doing any of these speeches justice. I’m studying and I’m practicing. I’m studying history, and what makes a great speech and I’m practicing my oratory. I’m doing so with the words of masters in my mouth, and I’m grateful for the opportunity to study these great words.
Writing tests for sorting algorithms are interesting. The main issue is that the tests would be the same regardless of which algorithm you chose: Given [1], sort returns [1] Given [1,2], sort returns [1,2] Given [2,1], sort returns [1,2] Given [1,2,3], sort returns [1,2,3] Given [2,1,3], sort returns [1,2,3] In Test Driven Development, when writing code for a test, you are supposed to write the least amount of code necessary to make the current test pass.
I explored in a previous post the idea of a coding kata. I explained that I thought that data structures, design patterns, and fundamental algorithms are ideal for such practice. I think a good way to practice them is to start with the tests, and practice the kata from there. In this light, last week I put forward the tests for the Stack kata. This week it’s Linked Lists. Background