Since I've launched my 12 startups in 12 months challenge, the #1 question I get asked is about my work flow and how I can ship so fast. I don't work particularly longer hours than most people (I think). I do work fast and rough. In this post, I'd like to show you the basics of how my I build my minimum viable products (or MVPs).
First, a public service announcement, I don't do things conventionally and probably not according to the rules. Especially not with these 12 projects. So it'd be a bad idea to follow how I do things exactly. It's probably better to just figure out your own workflow. That's what I did.
Solve your own problems, or not?
I start with an idea. I built GoFuckingDoIt so I stopped procrastinating and was fined money if I didn't finish what I said I would. Tubelytics was there to get a general overview of all my different YouTube channels performance. And when I wanted to know which cities had the best cost of living for a traveling nomad like me, I built NomadList.
Is that good though? As this article points out, we might need to consider that a majority of us doing this stuff are young white males. So if we only solve our own problems, we limit ourselves in audience and problem settings. I don't think that's bad necessarily. It's great to start off by solving your own problems. Personally, in the long run, I'd like to build more stuff that has a wider impact though.
My development philosophy
In terms of development I sympathize highly with Colin from Customer.io whose site is aptly titled I Am Not A Programmer. I'm not and I don't want to be one either. I just want my stuff to work and not break. Programming is not my passion. Making stuff is my passion. Just as I don't like mathematics, but I like how you can apply it to build a skyscraper.
If something potentially takes off, I do want my code to be easily readable by other coders to refactor and/or scale it.
If you look at any of my sites, they're very minimal  and basic . That's on purpose. I don't have as much as time to build things big and I don't see the point of building things big immediately. And I like minimal user interfaces. I don't think a site needs to be filled with functionality from top to bottom.
My development environment
To give you an idea, two years ago I was still using Notepad++ on Windows 7:
Sublime Text is great since it has auto completion, linting (e.g. live debugging of your code) and dark themes (like Soda) that don't burn your eyes. The auto-completion and linting especially now saves me incredible amounts of time. If I type this:
and press tab, Sublime auto-completes it into:
Sublime's linting will visually show where I have errors in my PHP, JS or SCSS code. I also use CodeKit to compile/minify my JS and SCSS files. Like Sublime, it also supports linting. So if I don't see the error in Sublime, CodeKit will simply pop up a window and tell me what's wrong:
A year ago, I didn't have any of these features. I didn't even have a local server, so I'd make a change to my code, then upload it to my development server (on DreamHost) and see if it worked. I developed entire sites like this. It would take 1000x more time though. I know, I know! Ridiculous. But what do you do if you don't know?
I'd recommend anyone to use a MacBook or Mac to develop your stuff on. It helps so much that OSX is a lot like Linux. That means I can have an almost exact duplicate of my production environment (e.g. the actual Linode server where the live website is running) on my development environment (e.g. my MacBook). So I can code and test stuff without breaking the live site. It also allows me to develop my sites when I don't have internet. To show you, above is my MacBook, below is my server:
You can do all of this in Windows too, but it's not as smooth and your production and dev environment will look a lot different — that is, if you use a Linux server, which you should (you say Microsoft .NET? I say lulz were had!)
When designing I usually start off with an idea of how it should look in my head already. I usually draw it out on paper first. For example, this is GoFuckingDoIt.com (I know, it looks terrible!)
And then I just build it in Photoshop and evolve it further. If I need a stock photo, I always get a mock first from Stocksy. They have amazing, beautiful, authentic stock photography. Really special stuff. Then when I actually decide to use it, I pay $10 and I have it licensed!
Then I build it in HTML and CSS. That's when things start changing. For example the name went from Just Fucking Do It to Go Fucking Do It, and I switched around the picture with another one from Stocksy:
I then tweak it until the interface looks great. Then I make it responsive for mobile. I use Chrome's new emulation feature to see how it looks on mobile. It's quintessential right now to make sure your site looks great on any mobile device. 40% of my traffic comes from mobile now. People will simply leave your site if they can't use it! Take it serious.
When the front-end is finished, I usually start building the back-end (the stuff on the server) and making it actually interactive.
Shared vs. private hosting
A year ago, I used to host all my sites with DreamHost. I was on there for years. My sites weren't that special though so they didn't need a lot resources. When I started doing intense background cron jobs though, I started getting messages telling me I should probably stop doing that and get my own server. Fair enough I thought, I'll get my own.
I didn't even know how a Linux shell worked back then. And it probably took me a week before I had a working server set up on Linode. But when it worked, it felt so much better to have my own server. I now owned the entire stack. From front-end, back-end to the server itself. That meant if something didn't work, I could quickly find the problem, instead of relying on some hosting company fucking up their shit and me debugging it for 12 hours to then figure out it was their fault.
I have a very basic stack. It's Nginx on Ubuntu on Linode with basic PHP, Node.JS, JS, CSS and HTML.
My server is hosted by the awesome guys and girls at Linode (yes that's a referral link). I run all my sites (even this blog you're looking at) on one virtual private server (VPS).
To show you how cheap it is: I pay $40/m for a Linode with 4 GB RAM, 4 CPU cores, 96 GB SSD storage and 4TB transfer i/o. You think that sounds slow and tiny? Yep, that'd be a slow MacBook, but as a server it's really quite fast. It takes floods of users easily. To give you an idea, every time one of my sites gets press or is featured on Hacker News or Product Hunt, it'll get flooded with users (often>1000 concurrent users per second).
It's never went down yet either, except for the cases when I broke it myself :)
I love Linode's dashboard too. I've tried AWS's but it's just too complicated for me. Like when I shut down an AWS instance, it loses all data? Sure that might sound logical to an engineer, but not to me. To me that's just not very user friendly. Linode has a lot less features than AWS but in my case that's good. It's simple. You can deploy a server instantly with one button, install a Linux distribution on it and it'll be up and running in 5 minutes.
My server runs Ubuntu 14.04 LTS as its OS. Why? It seemed like the most common Linux distribution when I picked it. And LTS stands for long-term support, which means even if you don't upgrade to the next versions, it'll receive bug fixes for quite a few years.
On top of that, I run a basic Nginx server with the PHP-FPM gateway installed to enable PHP to run. I love Nginx because it's very maintenance free and even if you don't tweak it after installing, it's usually just crazy fast out of the box.
The back-end of the sites itself are mostly written in PHP. I'm always embarrassed when I have to tell people this, but to be fair PHP has gotten a lot better these days. I am feeling the pressure to start moving over to Node.JS though, although I've been saying that for awhile (it's hard to switch engrained habits).
The front-end of the sites is written in hand-coded HTML (like most people still do) and just raw JS. I do use jQuery to make stuff easier. I use some parts of SCSS to speed things up, but mostly it's just me typing raw CSS code.
I like this setup, because I can deploy sites very fast. I'll register a domain with NameCheap, use their FreeDNS to add DNS entries to point to my Linode VPS IP address. I'll clone an existing nginx.conf (Nginx config file) from another domain, change a few things and upload it. Then I connect to my server, enter the command below:
sudo ln -s /srv/http/domain.com/app/nginx.conf /etc/nginx/sites/domain.com
sudo nginx -s restart
This links the nginx.conf file to the nginx server and then reloads the server and it'll be live. I can do that in about 15 minutes. Which is crazy cool to me.
I remember it used to take me hours to add a new site/domain to DreamHost because I needed to get through their horribly slow web panel. SSH-ing into a server is definitely superior to a web panel. I figured that out fast.
Last year, I was obsessing about how my folder structure was supposed to look. My projects had become quite a mess and I started looking at popular frameworks to base a structure on. After months, I slowly evolved into using this structure:
This is the folder I start with. It contains all the rough pre-dev assets like mock ups in Photoshop and Sketch of the interface and logo designs. Then when the site is developed, I put stuff like screenshots of press mentions in this folder. It's pretty much everything that shouldn't be on the server.
This includes all public asset files. That means pretty much everything used by the front-end. CSS for styling, JS for client-side scripting, images in PNG etc. This should all be publicly accessible. All JS/CSS files are pre-processed from the /app/ folder.
This includes all front-end (SCSS, JS), back-end code (PHP, Node.JS) and also the server configuration in the nginx.conf file that Nginx uses. This folder isn't accessible publicly by itself (only /public/ is accessible publicly). Instead, I use Nginx's config file as a natural router to route specific URLs to specific PHP files. That allows me to control what applications are accessible by clients.
I use CodeKit to monitor this folder and automatically pre-process/minify/compile the SCSS and JS files to the /public/assets/ folder:
This includes all back-end server-side libraries and stuff I didn't make myself and don't want to edit. For example Stripe's library for payment processing and Twitter's OAuth library. Libraries are included from this folder by apps in the /app/ folder.
This includes all app files that are scheduled and do stuff in the background by cron jobs. Think about sending out email queues or downloading/uploading data on a daily basis, like scraping or backing up files. I guess you could call them agents or daemons too.
This includes simple .txt files to log stuff. If I do a scheduled cron job, I usually do it like this:
* * * * php -f /srv/http/domain.com/workers/doStuff.php> /srv/http/domain.com/logs/doStuff.txt
This enables me to quickly check up on the result of any scheduled jobs.
This includes all data used by the app. I actually shy away from using real database systems in the 12 startups. Instead I use JSON text files. Wow. Yes. What a shocker! So this is for example how NomadList's data looks. Every text file usually just contains a JSON encoded array of data. The string in the filename is an MD5 hash of what it's about. With NomadList, that's the city + state + country name.
So yep very rough. Is this a horrible idea? Sure. But I'm not a programmer and at this scale it's fast to develop with. If there's anything I hate more, it's setting up a database structure. How the hell am I going to know what fields I will want to use? It's slow and for me it seems super counter intuitive. Especially if you like to code fast.
You can always write a script that puts this in a MySQL/MariaDB/PostgreSQL database later. I'd say if you're getting sensitive user data though you will want to secure it in a more decent fashion.
My coding style
Except for jQuery, I don't use any frameworks. Why? Because many times, they just make things more complex. I kind of just write code. I do want to keep things clean and fast though. I like DRY KISSes: Don't Repeat Yourself and Keep It Simple Stupid. When I need a function or piece of code I already wrote before, I grab it from a previous project. That saves some time.
So how do I know what I'm doing in a day? I used to have serious difficulties getting tasks done. Trello helps a lot. It's a kan-ban type system that lets you make lists with cards in it. Each card can be a task. You can arrange lists whichever way you want. And you can have multiple boards for different projects. Just go try it now, it's free and awesome.
I have a particular workflow with Trello. I think I saw somebody else on Hacker News do this and that's where I copied it from. I have a list for this year, this month, this week, today and now. When I go do something I drag it in to the 'now' list. That gives me an immediate sense of action and knowing what to focus on.
When I finish the task, I drag it to the list on the left. This list holds all completed tasks for this week. At the end of the week, I move this entire list out of the 'to-do' board to the 'finished' board.
Now it's out of my way. This list is important because it gives you a sense of satisfaction and loose measurement of how productive your week is. And the fun thing is, after a while of doing this, you can go to the 'finished' board and see everything you did for the last X weeks. And it makes you feel quite productive and proud of yourself! ^_^
So that's how I work! Not really special but since many people asked I thought this might help.
Like I said it's probably not following any best practices. But it works. I actually ship products.
I think the most important thing to remember is that it doesn't really matter how people do things. When I used to make electronic music, the forums would be full of people asking "which tools do XXX use?" and "which program do you make this bassline with", and in the end it wouldn't matter. It doesn't matter if you use PHP, Node.JS, Ruby or whatever hip new language. Everyone uses different tools and has their own ways and tricks. It's really about what you're best, quickest and most comfortable with.
When you are unified with your tools, you can really make anything ^_o
How I build my minimum viable products