This might be old news to you, but new to me:

In order to solve this problem, we decided to try to understand pages by executing JavaScript. It’s hard to do that at the scale of the current web, but we decided that it’s worth it. We have been gradually improving how we do this for some time. In the past few months, our indexing system has been rendering a substantial number of web pages more like an average user’s browser with JavaScript turned on.

I just ran into indexing of JavaScript that was embedded inside an iFrame. I figured no way they could index that, I was wrong.

Typekit Typography Lessons:

Lessons walk through specific topics or methods in the practice of typography, with a clear objective or takeaway skill that can be immediately applied to design work.

A great resource for typography, one of things in web development that I struggle to get exactly right.

A writer with no head for business isn’t going to make a living with the words they write, no matter how glorious, how well-crafted, how extraordinary they are, outside an incredible run of good luck.

— Kameron Hurley on Writing as a business

This applies to developers as well. Even if you have no aspirations to start your own business, knowing about options, employee contracts, personal finance, and retirement would do you well.

The Wardrobe Diaries

I have been working on building a new version of Wardrobe, my little blogging app, and development has stalled as I’ve been swamped with other things. I have thought about it for a few months now and I’ve decided I’m going to do a complete rewrite. Lots of new features have been added to Laravel and with 4.3 on the horizon I think now would be a good time to revisit some of my original goals, and also add new features. Instead of just building it and releasing the finished product I want to do something a little different. I’m going to journal the entire process on this site – from blank screen until completion. Continue reading “The Wardrobe Diaries”

Pluck The Weeds In Your Code

Back in the spring, as I was walking back from the mailbox I noticed a tiny little green weed inside a purple bush. The bush hadn’t bloomed yet and was still bare from the winter. I briefly thought about going and pulling the weed, but I kept thinking:

  • I have 10,000 other things I need to do
  • It will still be their tomorrow
  • When the bush blooms it will block out the sun, and without sun it will die.

The third thought was partially right. The bush bloomed and the weed seemed to miraculously be gone. Out of sight, out of mind, they say.

Fast forward to the fall and I’m making my same trip to the mailbox and this time I see a huge green leaf coming out of the top of the bush. The little weed that would have taken 30 seconds to pull has now turned into a massive tree like structure.

I tug and I tug, it’s impossible to remove, the roots from both are all intertwined.

Now pretend that weed is a piece of nasty weird code that you come across in your app. Don’t be lazy, go improve it before it grows out of control.

This post is an excerpt from my Laravel News digest. A weekly email about the Laravel framework.

Building a jQuery Plugin with Gulp

With the current design of this site I wanted to have images in the content that stretch out beyond the container. I’ve seen this pattern used quite a bit recently and I think it gives a nice little visual “pop”. Implementation wise this is a pretty easy problem to solve by using negative margins. I decided I would use this as an opportunity to put together a little centerImg jQuery plugin and document my steps along the way. Continue reading “Building a jQuery Plugin with Gulp”

The latest Bootstrapped.fm podcast had myself and the rest of the UserScape developers on as guests.

In this episode, we sit down with the developers of Userscape; Eric Barnes, Chris Fidao, and Taylor Otwell, to talk about weird dreams, Eric’s, Chris’ and Taylor’s backgrounds and how they got started at Userscape, supporting open source, Forge, newsletters, servers, building Scribbleton for Linux, content-based products, deploying desktop apps, and TV shows

Dear Morning

I glance out my window, scared to open my blinds. I know that once I do I will see how beautiful you are, how I will get lost in the chirping and glimmering dew.

I’ll have to wait to enjoy you later when my writing is done. I only have a few paragraphs. It shouldn’t take long.

I sit down at my desk. Start up my computer with the best equipment you can buy. I open a new document, the wonderful clean slate.

All I see is a blinking cursor, nothing is coming to mind. I should brainstorm, maybe that will inspire.

The light bulb is far from me. I’m left sitting thinking about everything else. I start a mindmap, that quickly becomes a maze.

Oh morning maybe I should come visit you, and step away from this artificial light. It’s only a few paragraphs though, it shouldn’t take long.

I hear the kids awaken. My mind drifts to them. Now it’s breakfast and I can’t focus.

Daddy will you play with me? Not now sweetheart. I only have a few paragraphs, it shouldn’t take long.

I sit and I ponder. Maybe Twitter has inspiration? Maybe Google? I get tangled in a web.

The kids come running, Daddy it’s lunch!

I’m sorry morning, but I have wasted you.

Losing Weight and Feeling Great

The other night my wife and I were watching a photo slideshow and a picture of me on the beach from 2011 popped up. I was honestly amazed and couldn’t believe that’s really how big I was. I decided I would do a before and after picture and post it on instagram. I’m usually hesitant on what I share on social media because I always feel like people will take it the wrong way. I did this not for people to congratulate me but instead to hopefully inspire someone else. Just as I had been inspired.

I did have a few people ask me how I did it and decided to write this post to share my steps. Of course this could just say, eat better and exercise, but that helps no one. We all know that’s all it takes but changing those habits are hard, so hard! Hopefully this gives a little inspiration for you if you are wanting to slim down.

It all started at the beginning of 2012: I weighed 182lbs, I wasn’t sleeping well, I was snoring, and all around I just felt bad. But none of those made me really want to change my life. It wasn’t until I came across a post by Jack McDade which simplified it so much for me:

This is so much easier than following a diet plan. I literally can eat absolutely anything I want, as long as I don’t eat more than 2,200 calories a day.

I thought to myself yes I can do that. I downloaded the Lose It app just as he recommended and inserted my weight and desired goal. In the beginning I calculating everything. Literally! The first week was so disappointing I was eating and drinking so much junk that I was going over my calorie count before noon.

The second week I got serious, I cut out soft drinks completely and switched to coffee. I never drank coffee before but I needed, ok wanted, that caffeine. I still remember that week and how much cream and sugar I used. 🙂 But it wasn’t long until I just went to straight black coffee to save on those extra calories.

After a few more weeks I started seeing my weight go down and I wasn’t missing out on a lot of the food I really enjoy. This was the start of it all. I kept tracking calories and finally settled on a routine that fit me. Then I added exercise. It was summer by this point and I live very close to some excellent mountain bike trails. I kicked the dust off the bike and began riding at least 3 times a week. I love mountain biking and had forgotten how fun it is.

When the time changed, in the fall, I couldn’t go riding like I was so I had to find another excersise routine. I’ve done the gym before and meh I just can’t get inspired for that. I’m lazy and I know for a fact I wouldn’t commit. Instead I bought the Insanity workout DVD and did it all winter. I enjoyed not leaving the house and would do it immediatly after work every day. It just became a routine.

By the end of 2012 I was down to 144. By BMI standards this was right at the upper limit for my height and I was happy about that. As you know the more you lose the harder it gets. I’ve just kept the same plan since then and I’ve currently stabled out between 132 and 136. I’m no longer doing Insanity because it got boring. Now I still Mtn. bike, do some cardio kick boxing, and road riding with friends on the weekends.

Typically my daily weekday routine is Oatmeal or protein bar for breakfast, Special K cereal for lunch, and eggs for dinner. On the weekends I eat whatever. So no, I’m really eating healthy but it’s better than before. Then I do hard cardio at least three times a week.

In the end what worked for me was very small steps that eventually turned into a life style change. I’m sure this is the same for everyone but it’s so important to change forever. Not just for a month or two.

Open Source Marketing Tips

It’s 1 am, I’m unable to sleep and have all these crazy ideas running through my head. As I start to doze, I have a spark of genius. I think to myself this would be an awesome open source package. I guarantee others would love this. It’s so useful why hasn’t anyone else thought of it.

Over the next two weeks I spend hours and hours thinking, building, refactoring, and creating this package. I think it’s going to be the best ever. Seriously it has to be, it’s so useful.

I’m finally ready to release it. I spend at least an hour crafting the best tweet I can. Secretly wishing it will go viral, hoping others will love it, and just from one single tweet Hacker News will have it featured all day. It’s time! I hit “tweet”, sit back, and watch in great anticipation.

After the first five minutes nothing happens. Sure, some friends retweet it but it’s not gaining momentum. So now I think I’ll just wait till tomorrow when more people have seen it. But still nothing.

Where did I go wrong? Was this a dumb idea? Why doesn’t anyone like it? Is the code horrible and no one told me?

As software developers we tend to look at things from our own perspective. Assuming everyone else will see it the same way. I’ve spent all this time developing but I didn’t take those extra few minutes to really polish the marketing text. This is the big mistake. I know you are thinking it’s open source, do I really need marketing? Without a doubt yes you do!

Your readme is the first page people see when they find your package. It’s important to clearly define what the package does. List out benefits not features. Features are important but only after you’ve sold me. I need a quick overview of why your package is going to make my life easier.

The fact is you have very little time to sell someone and people do not read. They glance. If nothing stands out, they move along faster than a cheetah chasing a gazelle.

I’ve seen it time and time again where I find something that sounds cool only to have this be their main section of the readme:

  • Includes awesome package
  • Uses x design pattern
  • BDD, DDD, TDD
  • And on and on.

What does that tell me? Nothing. I really don’t care about this. Instead show me the benefits. Show or tell me why my coding life is horrible without your package.

Here are a few packages I found that I believe excel with this:

Intervention Image

Look at the demo code which is the first thing you see:

// open an image file
$img = Image::make('public/foo.jpg');

// now you are able to resize the instance
$img->resize(320, 240);

// and insert a watermark for example
$img->insert('public/watermark.png');

// finally we save the image as a new image
$img->save('public/bar.jpg');

I think to myself. WOW. That’s all it takes to upload and resize an image? I’m using this!

Carbon

Both Carbon and Intervention use the same style by letting the code speak for itself. Here is a portion of their main page:

printf("Right now is %s", Carbon::now()->toDateTimeString());
printf("Right now in Vancouver is %s", Carbon::now('America/Vancouver'));  
$tomorrow = Carbon::now()->addDay();

Dispatcher

Dispatcher is a package for scheduling tasks inside Laravel:

dispatcher

Notice how these packages explain and demonstrate why I would want to use them. It’s really that simple!

Take the extra 30 minutes and ensure your readme is clear, precise, and tells me why I should care. Be specific. Sell the benefits. Take a screen shot. Wow me.

Single Page Laravel Application

Michael Calkins asked me on Twitter the following question:

I would love to see the processes and techniques you use when designing a SPA. UI/UX, API considerations, and those things.

I thought it was an interesting question and the answer could be a benefit to the community so I’m going to do my best to answer it by outlining how I setup a brand new single page Laravel application. My last two projects have been with BackBone but I’m not going to focus on the actual framework, more so, just the setup and techniques.

Directory Structure

First I setup my directory structure by putting all my files that need to be processed inside app/assets. Then sub folders for each major area such as javascript, styles (less/sass), vendor (bower or manually copied components), etc.

From here I used Grunt, Gulp, or whatever is the new hotness and setup all the processing tasks. This will output to the public directory and I recommend spending the time on setting up source maps from the beginning. This is something I wasn’t doing and it would be so nice to have now.

First Changes

I always use Blade templates and in my master layout.blade.php I set the following meta tags:

<meta name="env" content="{{ App::environment() }}">
<meta name="token" content="{{ Session::token() }}">

I use the environment as a flag for any features that should only be in production or for testing only in development. I typically use this for things like analytics tracking or in weird cases.

The token is used for CSRF when posting from your JavaScript. Here is an example app/javascripts/plugins/ajax.js:

$.ajaxPrefilter(function(options, originalOptions, jqXHR) {
  var token;
  if (!options.crossDomain) {
    token = $('meta[name="token"]').attr('content');
    if (token) {
      return jqXHR.setRequestHeader('X-CSRF-Token', token);
    }
  }
});

As you can see this just pulls in the token and is always included on any ajax requests.

API Considerations

For both Snappy and Wardrobe I put all my controllers in the app/controllers/api folder and these are only used for javascript communication. I do recommend keeping these very thin so you can easily reuse code in the future when you need a mobile app. 🙂

A side benefit of putting them all in their own folder is the ability to utilize Laravel’s routing and request filters:

Request::is('api/*')
Route::when('api/*’)

Here is an example of one of my controller edit methods:

public function putEdit($id)
{
  $response = $this->post->update(Auth::user(), Input::all());

  return $this->handleJsonResponse($response, ‘Your post has been saved’);
}

Then handleJsonResponse() is defined in the BaseController and simply finds out the type of response and returns based on this:

protected function handleJsonResponse($response, $success = 'It worked!')
{
  if ($response instanceof IlluminateSupportMessageBag)
  {
    return Response::json($response, 400);
  }

  return Response::json(['msg' => $success]);
}

This keeps everything really DRY and easy to maintain. Also by returning the validator it gets converted to JSON and is easily consumed in your JavaScript.

JavaScript

This area really depends on the framework you have chosen on how you set it up. I only have the following two tips:

  1. Pre-seed all your primary JSON.
  2. Abstract plugins

By pre-seeding all your primary models/collections this will save you on that initial load time of fetching all the records and getting the app up and running.

Plugins are a necessary evil. I recommend always wrapping them in your own code with a simple api that way it’s easier to replace out later.

In BackBone a common pattern is to use views for this and just instantiate it when you need it. Here is a good presentation that goes more in depth on this.

CSS

I’ve struggled writing good clean CSS. If I’m being completely honest a lot of times I end up with a mess on big projects. It starts off great but then a new feature here, a new feature there, and wham! a mess. 🙂

If I was starting a new app today I would follow an existing style guide such as the one GitHub published or Smacss.

Since I’m not a CSS wizard I do not want to steer anyone in the wrong direction. However, I do have one tip to share and that is use slightly obtrusive javascript. What this recommends is adding a js- class to all elements your JavaScript interacts with:

<a href=“#” class=“js-edit edit”>Edit</a>

On small apps this is over kill but if you plan on maintaining this for years to come this is very helpful for refactoring and noticing when selectors are used elsewhere.

UI/UX

I could be off base with this, but I feel the terms UI/UX are a little open for interpretation. If I ask 5 engineers to define it off the hip, they all would give me different answers.

To me this is the most important area of any application and I feel UI/UX is what drives emotion and leads people to an action. Most engineers are generally weak in this area. If thats you then your goal should be to get everything related to the design uniform and plan from the beginning for adjustments. This area is rarely static.

The design and usability is so important in any app. No matter if it’s open source or commercial this is where users spend 100% of their time. Users do not care about your code and all your fancy design patterns. They have a goal in mind and need the simplest and easiest way to achieve it. This is what makes or breaks a product. It’s also the hardest to get right.

The closer you are to the development of a feature the harder it is to notice little nuances. I’m no different. Anytime I complete a new feature I always ask for feedback before deploying. 9 times out of 10 the reviewer will spot something that I totally missed.

To reiterate, if you are week in this area get everything uniform and bring an expert in. If you don’t have the means of getting an expert then plan on spending lots of time thinking and getting feedback.

Is it really different?

I do not believe it’s that much different from building a “traditional app”. Instead of one you now have two, a backend for api endpoints and auth then the front-end or client for the end user.

Over a thousand words later I hope I’ve answered Michael’s question without opening up many more. 🙂 Nevertheless if you do have questions don’t hesitate to get in touch.

Working Remote With Kids

Ian just made a post sharing 9 tips for working remote with kids. I thought it was a great list and the tip for making exceptions reminded of a great memory I got to share with my youngest daughter a few months ago

//platform.twitter.com/widgets.js

I couldn’t fit everything in the tweet but she came running into my office with a princess dress on and batting her eye lashes telling me I was cordially invited to a royal ball. It was unforgettable for me and a memory I will cherish forever.

These are the quick moments that I wouldn’t get to experience first hand if I didn’t work remote. While my kids are small I can’t imagine working in an office. They grow up to fast and then it’s gone. No turning back the clock on what you should have done.

Switching to PhpStorm

A few months back I retired Sublime Text from my day to day coding and have since switched to using PhpStorm as my go to editor. I do keep Sublime around for quick editing, writing blog posts, but I haven’t missed it otherwise. PhpStorm has a lot of nice features that you don’t realize sublime is missing until you switch. Here is my mini review on what I’ve found in the few months of using PhpStorm.

Git and Github

I have found the git and github integration brilliant. I really like opening issues right in the ide and it creating a new branch/workplace. At UserScape we do a lot with Trello and only use GitHub Issues for bugs so I don’t get to use this as much I would like. Maybe one day some one will integrate Trello. 🙂

Committing is also something I really like doing without having to leave my editor. It has this integrated via command + k. Or if you are old school you can just open the terminal tab. My personal preference is to visually commit so I only use the terminal when I have small changes.

Find Anything

Another huge feature is the search everywhere. I have this mapped to “command + t” to match Sublime but the original is a Double-Shift. This is way more powerful than Sublime though. You can find files, classes, actions and preferences. I really like the actions searching because I have a mental block and can never remember them. This is probably why I don’t enjoy VIM or anything else that requires me to learn key maps. As an example I like splitting the window so I just “command + t” type vertical and BAM the action shows and it splits. Maybe I want to diff the file, again command + t type annotate. These are huge time savers for me.

Terminal

The terminal integrated is brilliant. We use grunt for all our js and css and have a simple watch/reload task. So when I start editing I just open terminal run grunt watch and then open a new terminal tab for anything else I may need. Deploying, artisan, composer, etc.

Code Complete

PHP code completion is very nice but believe it or not I find the code complete in html and less way more beneficial. It works just as nice as the php auto complete and does a very good job filtering css classes to find the one you want without having to hunt it down. It also has great support for CoffeeScript (The ONLY way to write JS). 🙂

Themes and Interface

This is one area I do find frustrating at times. The default theme is Darcula and it is a huge improvement over previous versions and you can find a ton of themes at PhpStorm-Themes or my recent favorite Spacegrey. What frustrates me is the font adjustment and line-heights. Fonts typically look good at bigger sizes but when you set the size to 10 or 11 they just don’t feel crisp like Sublime. The line height is also crazy. You set it to 2.0 and then you get a monstrous cursor.

Tips

If you are currently using Sublime and want to try PhpStorm here are some tips I have. I would hide all the panels and just move in slowly. I started with just as a code editor and then slowly experimented with features until I found my ideal workflow. It has a huge number of features that I don’t understand and/or haven’t cared to fully investigate.

Expect it to be slower than Sublime. A lot goes on under the hood for finding things, auto completing, etc and it’s always going to be slower than sublime. I only really notice this at times but that first launch you will.

Laravel is my framework of choice and the code completion doesn’t work great with the facades. A work around is to add this composer package

"require-dev": {
    "barryvdh/laravel-ide-helper": "1.*"
},

Next go and watch some videos and read some posts that highlight features and show you tips you would otherwise miss.

All in all so far the features outweigh the annoyances I have so I am going to stick to using it for the foreseeable future. Big IDE’s aren’t for everyone, but I encourage you to give a PhpStorm a chance. I think you might just like it.

Write A Love Letter

The holidays are approaching fast and what better gift to give than a “love letter” to your loved ones. When I say love letter I’m not meaning the sappy kind that you are probably thinking about. No, I am talking about a letter from you to your family that outlines all the very personal important things they need to know in the event of your untimely death.

This is something much more personal than a legal contract such as a Last Will but would still be highly important to your family. I have seen a few examples of this letter but it’s easy enough that you do not need a template.

What I did was include three primary sections. The first a few paragraphs telling them what they mean to you, how much you love them, etc. The middle would have important private information about yourself. For me and I assume all my readers almost everything is in the computer so having the login and the password for 1password would be essential. These are the only two passwords they would need and from here could get access to pretty much anything. Then the final section describing how you want your funeral. Your favorite songs, favorite Bible verses, basically anything that would be important to you for your funeral.

For those that handle all/most of the finances it will be important to also have contact information on any of your advisors and any investment accounts. I have heard stories of families where one primarily handles all finances and the other not knowing or caring. This means if the one handles everything passes then the other will be in for a crazy life change. Anything you can do to make this easier would continue to show your love.

Finally, I would also start a journal if you haven’t. Three out of four of my grandparents have passed away and none of them kept a journal. Of course in my younger years this wouldn’t have meant anything to me but now as I’m getting older I would love to read all the stories they had. I’ve personally been using DayOne for the past year and it works well. It’s nice to have a place to keep your private thoughts, images of important events, and memories that would be forever lost otherwise.

Announcing Wardrobe

This site has always been my own little personal playground. I am constantly changing the design, the platform, and just experimenting.

Over the past few weeks I started building a brand new backend that I named Wardrobe. This was built from the ground up using Laravel 4, and Backbone.js with Marionette for the admin. The main goal was to create something minimal and simple to use.

Features

Even though it is minimal it still includes what I feel as the most critical features.

  1. Content
  2. Tagging
  3. Post Slugs
  4. Post Scheduling
  5. Post active/draft

Even though these are core features I only think content is a priority so everthing is hidden away but still quickly editable via the content toolbar.

Technologies

Because Laravel is awesome and very flexible I used that for the backend. The administration area is built using Backbone and Marionette to make everything feel super fast.

I have the luxury of being friends with the author Taylor so he made sure the backend was architecturally pure using service providers. Currently the backend only supports content stored in a database but because of the service providers swapping this out for flat files or some other service will be very easy.

I have used flat files with Jekyll and Statamic in the past but at the end of the day a database is so much easier to work with and I didn’t want to force a square peg in a round hole. 🙂

All the administration is written using CoffeeScript and follows a lot of the same principles as Brian Mann covers in his BackboneRails tutorials. I then use grunt to compile and concat everything.

Care and Feeding of a Robot

 

I had the honor and privilege to speak at the first ever Laravel conference. After my talk, I had a few people ask me about my slides so I wanted to share those and give little insight into how I created them.

First off, I was doing my presentation on an actual product. So I wanted to be sure that it wasn’t presented as a sales pitch. Instead, I wanted to just share some good tips and some of the things we had learned throughout the process of building it. So for that I wanted to step away from all the branding that we currently use for Snappy.

For the design, I based everything around two fonts. Veneer as the primary and Thirsty Script as a secondary font. Once I locked in my fonts I decided on using the color scheme that Yellow Design had in the font screenshots. I knew it would compliment the fonts nicely and look professional. From here I just made everything match and be super big.

Slides

Video