News for hackers. Stuff that matters.

inprogress

Re:How should we price our startup? on Wednesday November 14, 2012 @01:30AM (#4782284)
That does help! What would you suggest that we start the initial prices at?
Re:How should we price our startup? on Tuesday November 13, 2012 @12:13PM (#4779100)
Cool, we will take a look and give you some feedback.
Re:How should we price our startup? on Tuesday November 13, 2012 @11:54AM (#4778949)
Thanks for giving it a try! Could you give me a little more info about the problem you saw? We just gave the system a quick test and everything seems to be working. If you have specifics please email me at doug <at> redline <dot> cc.

How should we price our startup?

http://www.redline.cc/welcome

Hello Hacker News,We need some help! We launched our startup Redline, http://www.redline.cc, into private beta a few months back. We are about ready to make it public and as part of that we want to introduce a pricing model. We have had some lively discussions about what to price it and how to determine if that is the right price but all our solutions feel like we are just guessing. The...

( Read More... | 10 comments | 15 points | on HN )
We have talked about doing this. The problem is that when a developer goes to fix a bug they want to see (at least in our estimation) an exact replica of the state that the bug occurred in. We thought that adding in anything that changes (or anything dynamic) would just be confusing when it came time to repair the bug.
We have integrated with Jira and Pivotal Tracker for now (though we plan for more in the future).

The way that replay works is that we actually take the screenshot from the current dom state (after disabling javascript and all the moving bits). So even if it is a very dynamic site (like the customink.com lab: http://www.redline.cc/bug/152570393#vdb_box_1) we are able to reproduce exactly what the bug reporter saw.

Show HN: Redline.cc, the easiest way to report visual bugs

As a developer, one of the biggest obstacles I've encountered has been how to communicate with designers - especially, when it comes to constructing their designs. Over the years, I have come to realize that Designers and Developers just see the world differently - Developers see the world as defects in code text and Designers see the world as defects in pixels. This "language barrier" is...

( Read More... | 7 comments | 12 points | on HN )