If you want more data on whether you should do this, try asking customers that have canceled their subscription if they'd stay on if it was once a month. Also, think about running an a/b test with once a month vs twice a month...
513 karma · joined July 17, 2008
If you want more data on whether you should do this, try asking customers that have canceled their subscription if they'd stay on if it was once a month. Also, think about running an a/b test with once a month vs twice a month...
I've been using Flexiglass for a while now, but only really the ability to drag a window to an edge of the screen and have it size it accordingly (top is full screen, sides are vertical half, corners are quarters, etc)
One of the things I loved about freelancing was that it was really easy to find an excuse to learn a new piece of technology - I just used it on the next project I worked on.
The key to being successful on these sites is to view them as a way to meet and get to know longterm clients. It's much easier to charge higher rates once someone has gotten to know you and the quality of your work. I often did one or two projects through the site on a fixed rate while we got to know each other, and then would work directly with them on an hourly basis after that.
Details: I bought a Fujitsu ScanSnap sheet fed scanner (loads paper in a hopper like a fax machine) off of Ebay for $100. It has decent Evernote integration, such that I can drop in a sheet of paper, push a button, and have it scan both sides of the sheet of paper directly to Evernote.
Have you tried walking into local head shops and asking them if they'd stock it? If so, find out who their main distributors are, and go talk to them.
How about running banner ads on 4chan (http://www.4chan.org/advertise)? Are there other websites with similar audiences and lack of censorship?
That doesn't mean that jumping straight into writing code is a good first step. Figuring out what you're building, why you're building it (is there demand?), how it will work from a user perspective, and how you will architect it, are often useful questions to answer before diving in.
From the site: "With instruction times as low as 1400 picoseconds and consuming as little as 7 picojoules of energy, each of the 144 computers can do its work with unprecedented speed for a microcontroller and yet at unprecedentedly low energy cost, transitioning between running and suspended states in gate delay times. When suspended, each of the computers uses less than 100 nanowatts."
How does this instruction time compare to other modern processors?
It sounds to me like some of the benefit to be had here may be from the low amount of power necessary per core. Power and associated cooling is a MAJOR source of cost for datacenters, and so if this really is a significantly lower power consumption (again, I don't know how much power the alternatives use), then it could have a big impact on the cost of commodity computation power.
[scotty@Scotty-Allens-MacBook-Air ~/bin]$ spark 1,2,3,4,5
▇\c
▇\c
▇\c
▇\c
▇\c
I suspect this has something to do with my terminal settings, but I'm not sure quite what...Nifty idea, regardless.
For what it's worth, I've personally found that having the intention to write someone's name down in Namerick makes me more likely to remember in that initial exchange. Not as technologically elegant, as say, universal audio recording and transcription, but in practice it seems to still be a useful life hack around this problem:)
Namerick was built by a team of six during a BeMyApp weekend app competition. While we had everything pretty much working at the end of the weekend, we'd remiss if we didn't add that we've added a few months of beta testing, additional UX polish, and marketing efforts:)
We'd LOVE your feedback (and be eternally grateful if you'd be willing to leave an app store review). The app is free for the next few days, and then we'll likely switch it to $0.99 after that.
You can learn more about it, and see our awesome retro demo video (complete with zero gravity cats) at http://namerick.com.
- It preserves all the built up knowledge encoded in your codebase, as you're never throwing away everything and starting over.
- It makes it possible to continue feature development during the refactor. Often with big ground up rewrites, it's necessary to declare a feature freeze, often for months at a time. Otherwise, the team that's doing the rewrite is constantly trying to play catch up to the newly developed features.
- It can be done gradually over time, which decreases the investment necessary to start seeing some gains.
Many people shy away from incremental refactoring when it comes to making large scale changes to a code base. They seem messy, expensive, and time consuming. And guess what? They are. But a ground up rewrite will generally be even messier, more expensive, and in the long run, more time consuming.