mattyfo

Something doesn't add up with this story and I suspect it's going to come out in the lawsuit.

If the doctor REALLY did want to lower testosterone levels in the 16 year old, there's a slew of medications that would have been more effective (Spiro, Lupron, Bica, etc). That amount of Estradiol isn't going to do much to lower T levels.

Well I'll tell you what, you had me a little concerned when you launched. We're working on similar challenges over at Smartsheet. Please reach out if you're interested in staying in this space!

Have you considered therapy? It sounds like you need some self-reflection skills and a therapist could help you develop those skills.

This is really helpful with understanding where data analysis goes wrong but he totally mis-characterizes proper segmentation strategies.

"These average people who are content with the default" are going to be your customers. My grandpa has an iPhone and his friend uses uber all the time. Both are very conservative and might fall into that realm of 'average people' yet use disruptive game changing ideas.

Get out there and empathize with real people with real problems. You'll find that even the most boring, ho-hum, run of the mill person will be happy to lay down hard cash for your game changing idea if it fixes THEIR problem.

That being said, focus groups are a horrible way to get meaningful feedback. Customer interviews and other more in depth ethnographic techniques are going to deliver what you're looking for.

You're so young, enjoy the ride.

Cultivate a rich life and identity outside of work. It's hard but what we do doesn't have to be what defines us.

An HTML/CSS prototyping framework that is dead simple for designers to use. They would only write the code in an easy to organize way (layouts and snippets) and the tool would take care of building everything, live reloads, creating documentation from comments, collecting feedback from stakeholders, and serving it up.

I've been wireframing for a while and have yet to reach a solution I really like.

I'd disagree on the JS part. I think given the timeframe and context it's fine as is. He did do a lot of things right such as not leaking globals and using gulp/browserify.

I think your product managers are doing it all wrong. They should be showing up with "this is the problem we've identified" and asking how the makers can solve it. Product management looses out big when they show up with "this is the solution we demand".

From reading the description if you need this functionality you should move to something else as the functionality you mentioned is out of it's scope.

As a UX Designer and front-end guy a lot of the appeal is being able to build something functional without a lot of help.

You are correct about the taking off part. If any of my ideas were to take off then I would need to swap out one of these services for an actual back-end.

Catshirt, I actually would love to get feedback on this comment:

>> initialize models and controllers, then pass that data to newly initialized views. at any scale, this hardly differs.

Where do you find it makes the most sense to initialize models & controllers? I've done it in the router function but that feels really heavy and gets big.

Alternatively, since I use require.js I have used a view wrapper that initializes everything and then puts together the sub-views and models/collections as necessary. I like this approach because it feels more organized having it delegated out to my various view files.

Thanks in advance :)