VimTip 26+ Clipboards(registers)

Some related commands

Some common commands that use the register are:

yank-line: y y
delete-line: d d
yank-selection: y (when in visual mode)
delete-selection: d (when in visual mode)

There are a lot of combinations so I wont go through all of them. But let’s get to why they are so powerful.

When you delete a line using dd it goes to the common primary register.

As soon as you use it again or use a related command like yy, the previoud value on the common register is replaced. This is where you can decide on and use your own established registers.

As far as I know you can use any other alphabetical key for a register (and some punctuation, but we’ll stick with alphabet)

Here is how it works

# double-quote + alphabetical character + register command
" <letter> <command>

Instead of just hitting dd next time you delete a line, try this:

" m d d

This will effectively delete the line and store it both on the common register as well as the "m register. To recall this later, even after you have overwritten the common register, try this:

" m p

This will paste the contents of the "m register the same way it would from the common register just by pressing p

Bonus: Advanced - Appending registers

Once you get the hang of managing your registers. You can actually append your registers by presing shift when pressing the alphabetical register key. That sounded confusing… try this:

" shift+m d d

this will append the contents of that line you just deleted to the contents of the "m register. Note: it will not automatically append a newline to each append

It’s not what you know, it’s who you know that matters

You may or may not have heard this saying in your time around in business, or jobs or what have you. Most common place I heard it was before graduating college. Getting a good job is not about what you know, but who you know. I would say for a majority of corporate American jobs, it’s true. However in “our industry” (design, development, technology) as an employee, the balance is a bit the other way. It’s less about who you know, and more about what you know (or what you can do). It’s all about the skills.

We know why it’s all about the skills right? More and more, we(internet consumers) love the impressive sites with the fancy (yet typically useless) animations and parallax scrolling and other effects or non-backward-compatible “HTML5” implementations that make us go “ooo” and “ahhh” and will get the company recognized with a badge that says “Captain Awesome”. That’s why they want your skills. But yes you’re right, and I won’t leave them out, there are also companies that just want a ‘simple, easy-to-use, intuitive, and beautiful’ software solutions that will solve a real problem for people. Still…it’s about your skills.

So why is the title of this article It’s not what you know, it’s who you know that matters ? It’s because I’m talking about a different context. Not if you are trying to get hired by a firm, or agency, or small startup team. I’m talking about if you want to be a successful solopreneur, or small bootstrapped startup with yourself and a buddy. When you’re in charge of the success of the business. Then, and especially then, who you know because a huge factor.

Bouncing back again - it is true no matter the publicity, a bad product is a bad product, so skills still matter - But when you need to get that product that solves a real problem for people out into the market, its ALL about who you know. When you depend on “word of mouth marketing” - you best know some people with some really big mouths.

It’s not to be said that it can’t be done without knowing these loud-mouthed individuals or groups, but it’s a whole heck-of-a-lot more difficult.

Where is all this coming from?

Being an aspiring solopreneur myself (building my own web apps or SaaS) I’m learning this in my attempts, endeavors, and failures to find that success. I’ve got network connectivity problems. I can design things - sometimes well, sometimes not - and I can build things, servers, rails, php, html, css, javascript. But I’ve got no network. No community I’m tied into that I can throw my ideas, and services and products out to in order to help me. No set of 20k followers that are watching my every move on what i’m going to build next. So how does one get that network? In first-part, I pose this question to any of you potential readers. I’ve got my own theories.

How do you get a network, or group of followers to be interested in what you’re doing?

Well one common thread between people like Orman Clark, Drew Wilson, and others that have found their solopreneurial path of success is that they Execute and they ship stuff. They produce things that no one knows about for long enough until people start to notice them.

We all just hear about them when they hit success. But the fact is, they put in long hard hours creating things over and over again, until finally they get traction, and have shipped enough for people to notice. So I guess we have come full circle back to skills.

It’s not about what you know, but who you know that determines your ability to achieve success. But who you know (or who knows about you really) depends on what you have done and can do.

So the final conclusion of this rant is: Build stuff. Incessantly. Not stupid stuff. Useful stuff. Your skills will grow. And people will start to notice. And the more people notice, the more feedback you get. And with more feedback, you will get more productive iterations. More productive iterations will translate into accelerated success in making something that has worth to others.

Weekend on Rails 4

Two weeks ago I decided to build my first Rails 4 app in one weekend. It should be simple enough right? If you are familiar with any developers, you know that typically things seem much simpler when they talk about it than when it comes to actually building it. That’s why most project managers have a formula of sorts to factor these sorts time estimates.

A PM might go to a developer and ask “How long do you think it might take to build in features A, B, and C”. The developer then responds, “I bet that will only take me roughly 20 hours or so” The PM might take that 20 hour estimate and multiply it by his preferred factor (ie. E*1.6 + 5). Do the math of the example there and you multiply the 20 hours by 1.6 to make up for the developer’s optimistic view of his own abilities, and then ad 5 hours for communication, questions, and just for good measure. That puts you at a nice round 37 hours.

The reason I bring this up, is that I am guilty of it myself. I am terribly optimistic, and always forget about all the little things required in every project I jump into. Inspired by the Execute Book and various other people I follow online, I endeavored to create an app on a short and tight deadline.

I set out when I had a friday off to get it done in a single weekend. It’s a simple app, just a few views, and an email to send. Piece of cake. Between tending to my family and church life, I was lucky to have gotten 6 hours in on the project over the weekend.

No problem, nothing is going to stop me, i’ll wake up early and crank on it before i get to work, then I’ll hammer away some more after work. Surely I can finish this bad boy before the week is over.

Friday rolls around. Ok really i’m going to town on this all day saturday, since I don’t have friday off. Got a solid 5 hours in on saturday, then realized how much I still have left to get the whole app done.

Another week rolls around, and here we are on the weekend again. Today is friday, and I got in a good 6 hours today (It’s my friday off) and made some good progress. So over the past 2 weeks, during my available outside-of-work time I’ve put in exactly 41.30 hours. My goal is to finish it before the end of monday. But I could be underestimating once again, as we developers love to do.

If you would like to check out the app and give me your feedback, just let me know @misterparker

Access BitTorrent Sync with CMD+Tab or the Dock

Occasionally a really handy menubar app (ie BitTorrent Sync) doesnt allow you to access the window via cmd+tab because it is not a “Dock” app but only a menubar app. If you know a little about how Mac apps work, you just need to edit the Application is agent property to be NO in the Info.plist file of the app. If that means nothing to you, here are some steps to follow.

It’s pretty simple, just stick close and carefully follow these steps listed:

Read More

The Best Things in Life Are *Not* Free

There’s the age old saying the best things in life are free. This came to mind today as I was reflecting on the fact that my car’s engine died yesterday and I now have the task of finding new transportation before me.

So what does it mean the best things in life are free.

Read More

3 Steps to Execution I’ve Learned by Watching Drew Wilson

If you are a developer in some bureaucratic company aspiring to jump more red tape and climb the management ladder, there is a good chance you have never heard of Drew Wilson.

If you are a designer, running your typical 9-5 schedule, have never heard of and only get on twitter maybe once a month, there is a good chance you have never heard of Drew Wilson.

If you are some form of an entrepreneurial spirit with a skillset including some combination of both design and development abilities, and you have thought or tried to build a web app of your own, there is a good chance you might know who Drew Wilson is.

Read More

Gathering Quality Feedback

Communication is Key

Receiving quality feedback from whomever it is you are seeking it, depends heavily on a pure and quality communication of ideas. Then being the one who is requesting or in most need of the information that is being communicated, it is your role to fine-tune and set the stage for the best communication possible.

So in order to facilitate better communication, I’ve found it’s best to first identify the problematic parts of communication and work on overcoming those first. Here I’ve identified 3 points during the course of any communication where the potential for miscommunication is higher than other points of the conversation.

Once we cover the common fail-points of communication, then we’ll move on to getting the actual feedback, and you’ll see how it will be a lot easier to pull that feedback out of someone who otherwise does not know how to communicate to you the information that you are looking for.

Read More


An iMac

cdixon tumblr: Things startups do and don't need

Things startups do need

Sunny office

Windows that open

Democratically controlled music system

Two forms of internet access

Beer on fridays

EVDO cards

Video game system

Good coffee maker

Proximity to public transportation

Proximity to park

Heating that goes all night

Health care plans…