devinblais

Seattle, Wa - Quve

Quve ("cue+move") is a well-funded, early-stage company, developing an online platform to change the nature of work for personal trainers and the nature of working out for consumers. Quve will enable top trainers to coach their clients efficiently and effectively between in-person training sessions, attract new clients who are interested in the benefits of daily fitness coaching between training sessions, and increase trainers’ income via online coaching.

We are looking for a Seattle-based senior rails developer to lead the development of Quve. You will be working closely with the entire team to rapidly build Quve, and iterate the product based on insights from ongoing user testing. This is the perfect position for an senior developer who wants to get in on the ground floor at a well-funded startup developing a stand-out coaching product that has the potential to extend to verticals beyond fitness in the future. Company founders and early employees are experienced and connected.

Responsibilities:

* Full stack development lead for Quve

* Build out and iterate on the core Quve product using Rails, Postgres, backbone.js and other technologies you determine necessary

* Help translate user research into actionable product improvement items

https://quve.recruiterbox.com/jobs/30325/

Senior Rails Developer - Seattle, WA - Quve

Quve ("cue+move") is a well-funded, early-stage company, developing an online platform to change the nature of work for personal trainers and the nature of working out for consumers. Quve will enable top trainers to coach their clients efficiently and effectively between in-person training sessions, attract new clients who are interested in the benefits of daily fitness coaching between training sessions, and increase trainers’ income via online coaching.

We are looking for a Seattle-based senior rails developer to lead the development of Quve. You will be working closely with the entire team to rapidly build Quve, and iterate the product based on insights from ongoing user testing. This is the perfect position for an senior developer who wants to get in on the ground floor at a well-funded startup developing a stand-out coaching product that has the potential to extend to verticals beyond fitness in the future. Company founders and early employees are experienced and connected.

Responsibilities:

* Full stack development lead for Quve

* Build out and iterate on the core Quve product using Rails, Postgres, backbone.js and other technologies you determine necessary

* Help translate user research into actionable product improvement items rational tasks: deploying, running, monitoring, and scaling Quve on Linux VPS

https://careers.stackoverflow.com/jobs/46701/senior-rails-de...

I agree with WSJ, and this is the first time I didn't get excited about the companies coming out of YC. But I don't think it's entrepreneur's fault. Investors are starting to go after companies that generate revenue from the beginning (as a result of the series a crunch?), which shifts the focus on what companies individuals can start if they want to find funding (unfortunately).

I think this is an important point. The fact that you can change the href after the click is irrelevant because there are other (just as easy) ways to change where the link will be taking the user. If malicious javascript is being run on your page, THAT is your problem, not the href switch.

Usability is also a big reason to not wrap giant blocks with an anchor tag. Anchor tags should be text (or an image) that clearly indicates where they are leading the user to. If you're linking all parts of a block to something, there are serious usability implications. Why not just link the title of the article? Or throw a link at the bottom that says "Read more"? You can't say the anchor tag is broken because you're trying to use it for things it's not intended for. That's like me saying my computer is broken because it can't make me a grilled cheese sandwich.

I'm pretty sure this is a result of the way google translate works and the fact that Lorem Ipsum is placeholder text. On a (very) high level google translate looks for groups of text that it knows is translated already and uses all that information to translate large chunks of text for the user. Since Lorem Ipsum is just placeholder text, people use it before they have real content, which results is random text across multiple sites. Google is picking up all those random messages and trying to make the best of it.