🔗 How to Steal Killer Sales Copy Straight from Your Prospects’ Mouths

How to Steal Killer Sales Copy Straight from Your Prospects' Mouths What’s in these 2 warehouses? Pure copywriting gold. … Also known as “customer reviews”. Warehouse #1: Amazon Reviews Most services are tied, in some way, to products. So if you offer a service, read the related product reviews, and steal from there. For example: If you offer a project management service, mine reviews for books about how to manage projects If you offer a directory of professionals – like AnyFu or Sortfolio – pull from reviews of biographies of the legends in those professions If you have a deal-of-the-day site, spend a little time on Amazon reviews for every product you host every day If you’re an unknown fashion designer on Etsy, pull from clothing reviews that highlight the things people want when they don’t care about big brands and labels If you’re a freelance graphic designer, find new ways to express your value by reading the reviews for Adobe Photoshop and for books on DIY design Warehouse #2: AppStore Reviews If you’re in the mobile app, digital product or game business, the AppStore is loaded with customer reviews that will help you write sick copy that resonates with prospects....

January 22, 2014 · 3 min · 513 words

📜 Being organized is the first and most important part of cooking (…)

Being organized is the first and most important part of cooking (…) it’s all about setting yourself up to succeed. Thomas Keller (in his book Ad Hoc at Home )

January 10, 2014 · 1 min · 30 words

🔗 Code Like a Chef: Work Clean | The Table XI Blog

Code Like a Chef: Work Clean | The Table XI Blog Interesting concept, specially the part gotten from the Ad Hoc at Home cooking book (by Thomas Keller ), which got me to dig out for the full text snippet ( emphasis added): Being organized – as we say in our kitchen, working clean – is a skill to develop. We call it mise-en-place , French for, literally, ‘put in place....

January 10, 2014 · 3 min · 532 words

🔗 playbook, by thoughtbot

playbook, by thoughtbot This is your playbook. It details how you and your teammates run our software consulting company and how we make web and mobile products together. We’ve made the playbook free and licensed it as Creative Commons Attribution-NonCommercial so others may learn from, or use, our tactics in their own companies. HELLO TIME Consulting Investment PRODUCT DESIGN SPRINT Prep Work Understand Diverge Converge Prototype Test and Learn CHOOSE PLATFORMS Web Apps Mobile Apps Programming Languages Frameworks Databases Licenses LAPTOP SETUP Laptop Dotfiles Text Editor PLANNING Daily Standups Tasks Weekly Retrospectives Planning Meeting Altering the Process DESIGNING Sketches Wireframes User Interface Interaction Design Visual Design Usability Testing DEVELOPING Version Control Style Guide Pair Programming Test-Driven Development Acceptance Tests Refactoring Code Reviews Continuous Integration PRODUCTION Checklist Domain Names SSL Certificates Hosting Performance Monitoring Error Tracking Transactional Email Payment Processing MEASURING AARRR Instrumentation Subscription Metrics A/B Testing Feature Flags SALES Leads Understanding Product Vision On Site Customer NDAs Roles No Fixed Bids Budget Rate Typical Projects Contract Invoices HIRING Recruiting Interviewing Offer and Onboarding OPERATIONS Expenses Email Calendar Documents Meetings Accounting Legal SHARING Blog Twitter Research Open Source GOODBYE

January 10, 2014 · 1 min · 188 words

🔗 Pairing vs. Code Review: Comparing Developer Cultures

Pairing vs. Code Review: Comparing Developer Cultures Prerequisites for success There are a few nonnegotiables that are common across both of these paradigms. Solid continuous integration Talented core developers Agreement on the importance of code quality Iterative self-organization The joys of pairing Everybody gets better together Pairing can balance the natural daily ebbs and flows of energy A peer generates motivation for self-improvement Tactical decisions are made more easily and with better results [Stronger] concept of collective code ownership but,...

January 6, 2014 · 2 min · 218 words

📺 Ken Robinson: How to escape education’s death valley

There are three (3) principles on which human life flourishes, and they are contradicted by the culture of education under which most teachers have to labor and most students have to endure. Human beings are naturally different and diverse . Curiosity is what drives human life flourishing. Human life is inherently creative . Education is not a mechanical system, it’s a human system, it’s about people! (via Ken Robinson: How to escape education’s death valley | Video on TED....

December 24, 2013 · 1 min · 96 words

🏞 (image)

This brings us to the magical three step process for becoming an expert at anything: Watch someone Try it yourself and experiment Teach someone else (via Programming Your Brain: The Art of Learning in Three Steps | BitNative ) See also another image representation:

December 17, 2013 · 1 min · 44 words

🔗 How To Not Suck Online

How To Not Suck Online Download a PDF poster of the below tips & tricks Clear Language Simplicity Visual Priority Create Intrigue Ten Ideas in ten Minutes Write a Good Brief Write the News Story Make me Look Good It Pays to be Remarkable Be Relevant Collaborate not Death by Committee Adapt or Die Tell a Story Use Humor Give People a Strong Call to Action

December 13, 2013 · 1 min · 66 words

🔗 The Twelve-Factor App

The Twelve-Factor App In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service. The twelve-factor app is a methodology for building software-as-a-service apps (…) Codebase Dependencies Config Backing Services Build, release, run Processes Port binding Concurrency Disposability Dev/prod parity Logs Admin processes

December 10, 2013 · 1 min · 48 words

🏞 hyphen vs. n-dash vs. m-dash

[hyphen](http://thewritepractice.com/create-your-own-words-and-other-uses-of-the-hyphen/) = connect things to be used as one word/unit [n-dash](http://thewritepractice.com/whats-an-en-dash-and-how-to-use-it-correctly/) = indicates a range, as in: X--Y (from x to y) [m-dash](http://thewritepractice.com/what-the-heck-is-an-em-dash/) = break in narration, a short aside

December 5, 2013 · 1 min · 30 words