Want to get advertisers on your blog? Gary V explains how. This 11 minute video shows how to get advertisers on your blog, vlog, podcast or other niche content site. Be warned, it is simple, but not easy.
I enjoyed Ben Horowitz’s ‘The Hard Thing about Hard Things’. It was an in depth view of the lonely life of a CEO going through hard hard times. I was only recently out of school when the dotcom bust happened, but I still remember layoffs–the company where I worked was going to be huge! “offices in Singapore and London!” until it wasn’t–which happened the week before Thanksgiving.
I cannot imagine what it was like to be in upper management in those times.
Must have been pretty wretched.
My favorite part of the book, though, is this section:
One very hot day my father came over for a visit. We could not afford air-conditioning, and all three children were crying as my father and I sat there sweating in the 105-degree heat.
My father turned to me and said, “Son, do you know what’s cheap?”
Since I had absolutely no idea what he was talking about, I replied, “No, what?”
“Flowers. Flowers are really cheap. But do you know what’s expensive?” he asked.
Again, I replied, “No, what?”
He said, “Divorce.”
Something about that joke, which was not really a joke, made me realize that I had run out of time. Up until that point, I had not really made any serious choices. I felt like I had unlimited bandwidth and could do everything in life that I wanted to do simultaneously. But his joke made it suddenly clear that by continuing on the course I was on, I might lose my family. By doing everything, I would fail at the most important thing. It was the first time that I forced myself to look at the world through priorities that were not purely my own. I thought that I could pursue my career, all my interests, and build my family. More important, I always thought about myself first. When you are part of a family or part of a group, that kind of thinking can get you into trouble, and I was in deep trouble. In my mind, I was confident that I was a good person and not selfish, but my actions said otherwise. I had to stop being a boy and become a man. I had to put first things first. I had to consider the people who I cared about most before considering myself.
It’s a beautiful vignette.
As a father with a lot of interests, this really resonated with me. Kids (or, I imagine, other major challenges such as a sick relative) take so much time that they force you to re-evaluate everything and think about your priorities and life focus.
I wrote an ebook last fall. It’s about the Cordova command line tool (Cordova CLI). Cordova is a way for web developers to build mobile apps that are distributed via the various app stores and can access app fucntionality (your list of contacts, for instance). The CLI is the main method of interacting with Cordova–managing your files, building apps, etc. It’s a niche, but one that I felt passionately about. I love the command line and I love webapps. I find the whole native app experience distasteful. (“Didn’t we already watch this movie?”)
I thought I’d share some lessons from this experience. This post will be about the writing, the next one about the marketing, and the final one about the results.
I wrote a series of blog posts, gathered here, to determine if I would enjoy writing a book, and to give me a head start on the content. Those blog posts were primarily written in July when my wife was away visiting family. I figured that if I didn’t want to write the book, the blog posts would have value anyway–writing clarifies issues for me. If they were useful and shared, then I would have some market validation.
On August 1, weeks after publishing my first Cordova blog post, I received an email from a reader who said the posts were useful, and asked a question. This was enough validation that I decided to start the book. It was five weeks from creating the project on leanpub to completing it (late August to early October).
During the book writing, I focused on expanding on the blog posts to make sure they were authoritative, adding new content as I came up with questions, and verifying all the claims using the Cordova software. I remember spending an hour trying to confirm one part of one sentence in the book. I also spent time answering and asking questions on the Cordova/Phonegap Google group. I also monitored the Cordova developer list, more for interesting topics than for dialog. And a new version of Cordova (3.1) was released just a week or so before I was done with the book, so I spent some time double checking how the new version of the CLI worked.
As far as time, I averaged an hour a day for that five week period–remember, a good chunk of the content was already written and I was simply revising it. I found time on the weekends and in the early morning.
I ended up finding a flickr image to use for the cover page–thanks Marc!
In the end, the writing was fun and a grind all at the same time. You just have to make the time.
I am doing some research for a possible client engagement. The client has invested in their Shopify storefront, and are extremely reluctant to move away from it. Updated 8/27: the client is MM Local Foods, and the issue is with their Harvest Share.
However, a significant subset of orders placed through this system have ‘pickups’ associated with the order–these are events where the customer picks up the product. There are multiple locations and multiple dates, and the customer can switch from one pickup to another at no cost.
Shopify, to put it mildly, doesn’t handle this use case well–it is about at easy to modify an order in Shopify as it is to read that Aztec calendar to your left.
Edit Order is the only Shopify app that I could find which will let anyone modify orders, and it has significant limitations:
- only staff with access to /admin can modify orders.
- it doesn’t actually modify an order. Rather, it deletes an order and replaces it with a modified order (order #204 becomes order #204A). This means you have to re-run the payment process.
I also looked at BookThatApp, which specifically handles ‘bookings’ within the Shopify framework, for services like tours or piano lessons. Unfortunately, this service doesn’t let the customer reschedule the booking themselves (I asked BookThatApp support to be sure).
So, I spent a fair bit of time wandering the internet, looking for scheduling and booking SaaS apps that:
- had an API that could be integrated with Shopify
- would handle events at specific dates, times and places rather than letting the customer pick freely from from a weekly availability calendar (such as for piano lessons or massage appointments)
- let the customer modify their pickup without calling customer service
- looked professional
- wasn’t too expensive
- wasn’t too cumbersome to manage from the business side
The bad news is I didn’t find any software that fulfilled all requirements, even after hours of searching and signing up for about ten different applications (at least they all had free trials!).
I was astonished–was I not searching the right keywords? Is this such a niche need? A lot of scheduling software failed on criteria #2. Eventbrite failed criteria #6 and #3. Most booking software failed #5 and #3–which makes sense as they are aimed at tour companies who don’t want customers changing their tour dates without talking to someone. I looked at some class scheduling software, but couldn’t figure out how to make it work.
The good news? I found one solution that does almost everything above–it does fail criteria #1, but I think it is the best of the worst. The other alternative is to write custom code, and that always worries me.
Why does writing custom code worry me? One word: maintenance. Especially for a small, non software focused business, maintenance of custom software is costly. Instead, it is better to conform your business processes to the SaaS application which best fits them, and let someone else shoulder the burden of maintenance. This is not always the case–sometimes needs are so precise and static that custom software is the right answer. But my default is always to look for other solutions.
I’ve outlined some of the pros and cons to the customer and am waiting to hear back on how to move forward.
And if you know of any solutions that might be better options for this customer, I’d love to hear of them.
As I wrote over at the Geek Estate Blog, if you build your business on vendors, you should monitor them. In the past, I’ve used a variety of services to monitor vendor services, from pingdom to wget/cron to nagios. These services are great about telling you when some external service is unavailable, but are not so hot at telling you when a service is going to be down (for planned maintenance) or back up.
For that, you need to be monitoring, and reading, vendor announcements, however the vendor has decided to provide them, whether that is as a blog/RSS feed, twitter feed, email newsletter, a status page or something else.
However, it can be tough to monitor and read announcements in two or more places. Here, Zapier or a similar service can help. Pick one place to be notified. For me, that’s typically an email inbox, because, frankly, other data sources can be ignored (except phone texts), but I’ll always check my email.
Then, use Zapier’s zaps to transform any announcements from the other sources to emails. For instance, there is an RSS trigger for new items in a feed and a Twitter trigger for tweets from a user. Status pages often provide RSS feeds (Google’s does). If the service provider doesn’t provide a structured method like an RSS feed to notify you of changes, but does provide a webpage of announcements, you could look at a service like changedetection.com and have the email sent to your inbox or parsed by Zapier and pushed to your notification location.
And for the output side, you can just use Zapier’s ‘send outbound email’ action. If you want to have all notifications pushed to your phone, an RSS reader or Twitter acount, you can use Zapier to send texts, create RSS items or tweets as well.
VC Brad Feld of the Foundry Group defines this concept in this 90 second video:
The internet has let one thousand, nay one billion, flowers bloom, so many flowers that it can be overwhelming at times. Brad suggests picking one or two or three flowers at most and really understanding them, rather than trying to smell all the flowers.
One of my most recent projects was writing a system to deliver real estate listing data to a content management system. The CMS was not in my control. Since the listing data source was bursty and I wasn’t sure how the CMS would handle the load, I decided to use a message queue, where the messages would have a JSON payload. Message queues are great at decoupling components of a system.
For the queue, I used IronMQ. The company already was using it, it has a free tier (up to 24 messages a second), the service has been stable and reliable, it has great language SDKs, and setting up a durable message queue is something I’d rather outsource. (I do wish Zapier supported it.) In other situations (when posting messages from mobile apps), we ran Varnish in front of IronMQ so that it could be replaced easily. In this case, we didn’t because there were fewer moving pieces (it was server to server communication and it would be easier to swap out IronMQ should that be required).
I wrote the bridge code from the listing database to the message queue in python. The shop was mostly Java and some python, and python seemed a better fit for a small ‘pull from here, push to there’ application. I used pytest for unit testing, jenkins to run the unit tests in a CI environment, and autopep8 for formatting. My colleague was a more experienced python programmer, so I was able to lean on him for questions. I didn’t find python hard to pick back up (I’d scripted in python a little years ago), and it was a fun language to code in. Reminded me of perl w/r/t packages and quick developer feedback. I did miss Java’s dependency management, though (my college recommended virtualenv as a possible solution).
The JSON payload would allow developers writing the message consumer to use almost any language they wanted–any language if they used the IronMQ REST API rather than an SDK.
I can’t share the code, but for this kind of problem, python was a great solution. And I’ll reach for IronMQ any time I need a message queue. This pair of technologies was quick to implement, easy to deploy, and high performance wasn’t really a requirement, since the frequency of the listing delivery was the real bottleneck.
I spent a fair amount of time in the spring working on Google forms. If you have Google apps for your domain and are doing any kind of data entry at all, you should use Google forms. With this, you can create a web and mobile friendly data entry form easily, with validation, for free.
And by you, I mean ‘you, the non technical user’–a big win. I’m a big big fan of anything that removes developers from the loop because they are too often the bottleneck. Of course, as you’ll see below, Google forms is not entirely the land of milk and honey.
Any data entered typically goes into a Google spreadsheet for easy batch processing. You can limit use of the form to your Google apps domain, too.
Here are some ways that I’ve seen Google forms used to eliminate manual re-keying of data:
- Event RSVPs
- Contact forms
- Order forms for collateral
- Transaction reporting
- Timesheet or vacation tracking
Google forms are extremely flexible, but do have some significant limitations (which is why other form building companies like Wufoo haven’t had all the air sucked out of them).
Some limitations and issues are:
- If you post to a Google spreadsheet, the typical use case, you are bound by spreadsheet limits: 400k rows, 256 columns.
- You can’t host the form on your domain. The best solution to this issue I found was to do a URL redirect of a domain name. For example, from someform.example.com to the Google form URL. This lets you replace the form while still sending people to the same URL.
- You can’t have a form email an arbitrary address on submission without custom code.
- Multi page forms are possible, but clunky.
- Validation is limited, though using regular expressions gives you a fair bit of power (but then takes form creation/maintenance out of the realm of the non developer).
- UI customization is limited. A Google form will always look like a Google form (short of serious server side gymnastics). It will always have the ‘powered by Google forms’ link, the same crappy ‘response received’ page, and the same horrible handling of closed forms (an unmodifiable message from Google, with no way to customize it).
- Option lists are static (though if you use formRanger, you can alleviate this issue).
- File upload is not supported. Seriously. Even though Google wants you to use Google Drive.
As alluded to above, you can use Google Apps Script to alleviate some of the issues with Google forms. However, doing so pushes the maintenance of that form into developer land (or at least ‘power user’ land).
Even with all the warts, Google forms is a powerful tool. And did I mention it is free? If you or anyone in your business is currently doing manual data re-entry, and the limits above haven’t scared you away, I’d take a long hard serious look at Google forms.
I was reading this Ask HN post about a consulting arrangement that seemed a Sisyphean task. Here’s an excerpt:
I have been asked to consult a company in how they should speed up their development process.
Today the application which in the end of it all is a web application, consists of a lot of old ASP classic code, a COM+ bridge for being able to function within a mix of a lot of different .NET libraries written in .NET 3.5 (CLR 2). COM+ acts as a bridge between the two technologies.
The teams cannot compile code inside the development tools, it can’t debug unless they do it with some obscure hacks and workarounds and it seems that no one is really in control of what is going on in the core code base and no one really want to touch the original code base to clean it up and refactor/re-write it.
Seems pretty hopeless, right? “Teams can’t compile code”?! Unfortunately, this type of task is more typical of consulting engagements than not. After all, if there was a simple solution, why would the company have engaged a high priced consultant? (If you are consulting and not ‘high priced’, well, that’s a problem, but a different one better left for another post.)
The comments on the post are interesting and worth reading. I left one, but wanted to expand on it. Now, I’m not familiar with the tech stack at all, but I am familiar with a large codebase (where large is relative to the size of the team supporting it–100K LOC can be large to two person team) with a lot of technical debt that was crucial to the business. I have also consulted for years.
Whenever you are consulting, the first task is always to ascertain the real problem. Hint–it’s often not what you were explicitly hired to do. In this case, I’m guessing the real issue is that the web application needs to change to meet business needs, and that it can’t do so fast enough because of the accretion of complexity. But a guess isn’t good enough, you need to find out what you are being hired to do–it could be you are being hired to provide cover to spend money to rewrite the app or to be blamed when a development team misses dates or to actually speed up compilation.
Then, you need to learn who wants the task done, and who is writing the checks. They are sometimes the same person, but not always. You also need to learn how these folks want to be communicated with, including method, verbosity and frequency.
Finally, you can start to dig into the (software) problem. (This process assumes you are doing time and materials billing.) Do a preliminary investigation and look at some of the following:
- given the end goal, what are intermediate steps that can get you there? How long would it take to get one or two of these steps?
- are there third party solutions that can get you 90% of the way to solving the business problem–this can include framework upgrades?
- are there subsystems of the current hand coded solution that are isolated and can be reworked with minimal impact on the system?
- are there one or two huge issues that would be a relatively easy win (version control, big bugs, moving configuration from code to a database, etc)?
Prepare ballpark estimates on the level of effort to accomplish some of these. After that, you need to sit down with whoever wants the task done and whoever is paying for it. Present your options, making it clear that any time estimates are truly SWAGs.
Let them decide.
If they ask for a recommendation, be prepared to make one, but the decision must be theirs. They have the business context to know how much to invest in this system.
After that, either withdraw or start executing against the plan you and the decision makers have decided on.
If you are a software developer in the real estate space, here are some useful blogs to follow to understand the industry.
- 1000 Watt is a consultancy that focuses on brokerages and realtors. If you like inside baseball, this is the blog to read. If you want to know about politics between portals and realtors, or high level strategies that 1000 Watt thinks will work for local brokers, or brokerage branding ideas, you should read this blog. They also do a good job of featuring the latest software startup to rock the real estate world. This blog is written by several members of the consultancy, but they all get bylines.
- Calculated Risk is all about the big picture, the numbers and graphs. Bill McBride monitors the economy so you don’t have to. His real estate focus tends to be either nationwide or California, so he’s probably not going to write a post that is useful to your specific market, but his overall analysis of economic trends, whether positive or negative, is required reading. For instance, check out his job chart, which shows just how bad the great recession was, or the list of troubled banks (done by a contributor) or his graphs of other economic indicators like restaurant or trucking indices. If you are interested as a person or a developer in the mortgage market, read all of Tanta’s articles about mortgages–there’s a lot of money and lot of of complexity in that business (she passed away, but was a contributor for years).
- The Geek Estate Blog is a unique fusion of technology and real restate. Drew Meyers was with Zillow and has done few startups outside of the real estate space. Because of this experience, he has a unique perspective on the real estate space and startups therein, and shares his perspective. Drew also takes guest posts (I’ve written a couple) and while sometimes they seem like thinly veiled sales pitches, other times they can clue you in to other technologies, startups or trends in the real estate world. I haven’t found a better source of real estate news that is focused on technology.
- Your local excellent real estate blogger. In Boulder, that’s Osman Parvez of House Einstein, and no one else (I really like 8z’s market updates, but that only comes out once a month). I can’t tell you how to find this blog beyond searching for ‘[your location] real estate blogger’. They will most likely be a realtor (but they could be someone else–Dave Fratello wasn’t a realtor for a long time). They are using blogging as a bizdev tool and can give you a great view of your local market (for instance, check out this post about poptops in south Boulder, and this sample of his market stats).
Bonus read if you are a software developer looking to get into real estate: Game Plan is a book, not a blog, but I found it tremendously useful because it covers the recent history of the real estate business and will serve as a primer to get you up to speed on the various players and their concerns.
Finally, I also subscribed to some of the big tech giant tech blogs (Redfin, Zillow) but didn’t find much value in their sporadic posts.
If you are a software developer who is working in the real estate space, I’d love to know what you read.