263 karma · joined May 11, 2009
http://twitter.com/bouldrmatt
It's annoying to have to run the stylesheet combine when testing as when I find problems, I have to sort through a mass of css and rerun the combiner in order to test fixes.
OR
http://www.i-marco.nl/weblog/archive/2006/06/24/time_breakdo...
(But without the red section).
I tend to miss the doodles as I search from the address bar, and only end up on Google's homepage when I'm looking at them.
* They will uncover bugs that have been missed
* They will show you where usability is poor in your app
* You will build an audience of people that actually use your app, giving you an crowd to sell to
* You'll get the opportunity to see how the app performs under working conditions
If you wait until your app has the paid stuff in, then the first paying customers may have to put up with problems that could have been ironed out during the free-only period.
This seems to be a common scenario - people hear about or see the site, go to it, get excited, then forget about it. I think I'm losing out because my message is confused or not consistent enough to stick. Maybe I don't have a clear message at all?
I saw your post a few days ago - moving stuff. Hope you're getting better as each day passes.
I'll put this into practice, and I'm going to start by building the survey you describe. Do you have any pointers as to what questions I should be asking, or know of an example I can learn from?
How did you go about finding your marketers?
My point is; I dont think I have the skills or experience to market Bouldr alone. I think I need to find someone that has experience, otherwise I'll faff it up.
It came down to me to find and fix the problem, and it was subtle. The clue lay in the fact that all of the sites that crashed did so within about a minute of one another.
Turns out that some of the old, old sections of the software had been written by the MD, who, despite referring to himself as 'the emperor of c', was in fact an atrocious programmer.
The actual trigger was the comms system looking at a byte that determined as to whether a message had been received. This byte was set to the character 'A' if a message was received. It just so happened that the first byte of the current value of the number of seconds since 1970 evaluated to 'A', and had been written into that memory location a negative index into an array that hadn't been initialised.
This negative index into an array that shouldn't have been empty caused a section of memory to be overwritten that made the comms system think that it had received a packet. This snowballed quickly, and took down the system within about five seconds of boot.
Took the best part of two days to track down, and, of course, it was everyone else's fault but the emperors.
I don't think there is any problem in posting the same article to both of your blogs if it makes sense to. It depends on whether your startups blog audience would find dev articles interesting, I suppose.