mzarate06

That bit me w/their 2007wfp, which was a great monitor mostly for 1 reason: it was IPS at a great price point. Overwhelmingly positive reviews convinced me to purchase 2 of them.

Then buyers started noticing picture quality issues not described in previous positive reviews. After some research, it was found Dell had silently started shipping the 2007wfp with cheaper PVA panels, not IPS. After noticing similar issues with the 2 I purchased, I eventually confirmed they were PVA monitors. I was fairly upset.

There's a good thread on Hard Forum about all of this here.[2]

And despite very frustrated customers, Dell never acknowledged any problem. In fact, a Dell rep can be quoted: "... a 2007WFP is a 2007WFP ... It does not matter what panel is installed." [3]

I stopped buying Dell products after this experience.

[1] http://en.community.dell.com/f/3529/t/18107050.aspx

[2] http://hardforum.com/showthread.php?t=1111100

[3] http://en.community.dell.com/f/3529/t/18286693.aspx

I'm positive I'm not co-founder material though. I'm still going to keep eye on you guys, primarily b/c I hope you succeed, though I also want to see what future developer opportunities may arise.

Are you open to sharing what stack your team will develop with? I didn't catch that here, on your site, or your HN profile. As someone that's interested in this, that's one of the first questions I have; others may as well.

I'm not co-founder level, but I'm going to keep an eye on this.

Best of luck, I really hope you guys knock it out of the park.

Have you considered intermittent fasting? I typically only eat 5 or 6 days out the week. Aside from the health benefits, IF lends itself to productivity; I love having days where I don't need to worry about food or cooking at all.

There are various IF approaches, and it does take some getting used to, but I've found it worth it.

Are you referring to the opening note of the track? I'd argue that's a pickup note.

Edit: Either way, I just tapped out to 13/16 and see how that fits perfectly. Thanks for explaining.

1 & -- & 3 -- 4 & -- -- 6 7

I hear that through the entire track, and counting with 7/8 has each new bar starting nicely on the first eighth note.

My vote is 7/8.

Because I can't remember how to phrase an up beat in an */8 time signature, think in terms of 7/4 for a moment. You can clearly hear the repeating percussion pattern on these notes throughout the entire track:

1 & [rest on 2] & 3 4 & [rest on 5] 6 7

I distinctly hear 7 downbeats each bar.

I disagree. Not wanting to code is not the same as not knowing anything about the product, or wanting to. There's so much more that goes into a successful product or company than time spent coding (marketing, design, testing, sales, industry/market immersion, etc.). As a developer and co-founder, ideally I want complimentary skill sets. Being able to write code may be an overlapping skill, but it's not required.

Though in practice I've experienced too many cases where I couldn't imagine non-technical founders I've worked with learning enough, and fast enough, to launch a v1 on their own. It's possible, but between OP's suggested flow vs. yours, I'll side w/the OP's. As a developer and co-founder, I'd much rather a non-technical founder concentrate on finding paying customers (or other cash flow), marketing, becoming immersed in the target market, etc. than learning how to code.

To supplement, the article's Where it went wrong and Where it went REALLY wrong sections cite non-technical reasons for failure. So while you raise great points, it's not clear that the OP's situation would have been better if he had learned to code first.

Question: what are you going to do with the product now?

In one case I left after about 3 months, only b/c I knew right away that my place wasn't in that particular environment, or with that particular team.

If you're asking due to relevant circumstances, what don't you like about the job, and how long have you been there?

I agree w/the advice given, but learning to save and limit expenses is just half the battle. Learning to get better at generating revenue is the other. All too often I hear the former advised without mention of the latter.

I agree w/other comments that taking breaks helps, but I haven't found that to be as important as those two (passion and team). You can take as many breaks as you want throughout the day, but if you're stuck having to return to non-interesting work or a team you'd rather not work with, you'll still find it hard to get motivated and maintain focus.

Great hiring requires evaluating more thoroughly than that. Have no less than one conversation with any candidate you're considering. Get a feel for their history, how they communicate, if they've any experience or passion in your domain, etc. E.g. All else equal, I'd more likely hire a candidate for my music start up that had experience integrating music apis, was an avid music lover, etc. That's not required, but helpful.

And yes, I'd still have any candidate write code in an interview. Too many times simple sql queries, OO, or basic understanding of data structures have defeated candidates, despite code samples that implied otherwise. If a candidate can't write simple code to solve simple problems, they likely can't help the company solve much bigger problems efficiently.

SQL also offers powerful aggregate functions to assist. Much simpler to use something like AVG() or SUM() in a SQL query than having to worry about deriving the same calcs in application code.

Point taken, but if you're referring to Loeb's firing plan that Mayer supported, the firing would have been towards roughly 2,400 - 3,600 workers, not 12,000.

From the article:

"... Loeb’s plan was to fire between 20 percent and 30 percent of Yahoo!’s roughly 12,000 workers — an idea Mayer initially supported ..."

Edit: yep, I agree it's still a lot, just wanted to point out the difference.

For example, in LAMP context, I hit the problem you mention w/the Zend Framework 1 -> Zend Framework 2 upgrade path, as well as with Kohana 2 -> Kohana 3. ZF 2, in particular, pushed a lot of loyal ZF devs away, and after trying to upgrade existing projects, and use it for new projects, I'd say rightfully so. Now I'm stuck maintaining a large handful of projects built on top of unsupported frameworks.

I love JavaScript, but I hate having to switch between BackBone, Angular, Dojo, etc. between projects. Learning each one, as well intentioned as they are, winds up being a productivity hit at some point, if not semi-regularly.

In a way I feel as if I've spent more time learning how to get things done w/JavaScript frameworks, than actually getting them done.

1. Error Tracking. I'd also recommend catching JS errors that are happening client side. Whether they're sent to 3rd party analytics or bug tools, or sent to your server for logging (what we do) is up to you. A JS error can prevent your app from working just the same as a server side bug can, so definitely do this.

2. Setup your support email. Yes, but also include a very easy to access support form inside your app. Even though I include our product's support email address on our website and in account verification emails, 95% of support emails come from w/in our app through the built in support form.

3. Get a few friends to test the app first. We were fortunate to have friends very eager to do this, that also represented our target audience. In addition to finding bugs, we also found they re-emphasized features we left out or thought weren't important. They also downplayed features we decided to include instead, either b/c they didn't work as expected, or weren't as important as we thought they were. But use good judgement when acting on their feedback, depending on how much they represent your target audience.

5. Uptime Monitoring. OP, what are your uptime reports saying? I test drove Digital Ocean for about a week, but their network was the least reliable out of all 5 hosting providers I tried.

Consider this:

A popular belief is that 1 lb. of fat contains about 3500 calories. [1] By that measure, and assuming you regularly eat at maintenance calorie level each week, eating 3500 calories below what will result in about a 1 lb. reduction in body weight that week. (which realistically turns out to be mostly fat, but can also include small amounts of lean muscle, too).

Whether you create that deficit from removing sugar, fat, carbs, or protien doesn't matter.

But that's solely for weight loss. When you simultaneously want to increase lean muscle, exercise and protein become more important. Also consider medical conditions that require adhering to certain diet regimen.

So I'm not saying that, globally, what you eat doesn't matter, only that weight loss primarily comes down to maintaining a caloric deficit. To supplement, of all the diet programs out there ... Atkins, South Beach, and even intermittent fasting ... the one thing they all have in common is that they promote a caloric deficit, somehow. And they have to, other wise they wouldn't work!

[1] Some argue the 3500 calories = 1 lb. of fat is bs. All I can say is that I've based my caloric deficit on it and it seems to hold true. I dropped my weekly caloric budget by 7k calories, and have been losing about 2 lbs. a week.

He does make a clear, recurring, point in his book: the fitness and diet industry focuses too much on things that don't matter that much. E.g. low carb diets, avoiding "bad foods", cardio being the key to fat loss, and yes, metabolism.

My belief is that he mentions metabolism on his site to arouse curiosity, or calm worries, on one myth that fasting skeptics have: not eating frequently slows your metabolism, and to the point that it affects weight loss.

In fact, fasting doesn't affect your metabolism that much, if at all. Research shows it stays pretty steady during periods of fasting.

And through that fact, he's able to push your focus away from worrying about metabolism and on to what really matters: calorie consumption.

The true formula for weight loss is simple and well understood: consume less calories than your body requires. When you create a caloric deficit, you'll drop weight, certainly. Focusing on metabolism is a red herring.

What's more, is that your body doesn't care how the deficit is achieved. I'm eating fast food, sweets, and consuming diet soda more often then when I was a "healthy" eater ... you wouldn't guess that I've since dropped 30 lbs. All while getting stronger, and only eating 1 - 2 meals a day. Who cares what my metabolism is, or what I'm eating? The bottom line is that I'm consuming amounts that adhere to a caloric deficit, so I'm leaning down.

So for weight loss, how much you eat will always trump what you eat. Consuming more calories than your body needs will always lead to weight gain, even if they're "clean" calories that come from lean meats and veggies.

I'd encourage you to read Eat Stop Eat: http://www.eatstopeat.com/ (warning, the site looks spammy, but you won't be dissatisfied w/the book)

It's a great read on intermittent fasting that presents a lot of research that debunks metabolism and other hype factors the fitness industry relies on to complicate how simple weight loss really is.

Digitial Ocean makes provisioning new servers incredibly easy (as does Linode). The process is near instant. Scaling a server up and down is also near instant, especially compared to Rackspace (it took over an hour the last time I scaled a server down with them).

But their network has proven the least reliable (I'm in their NY DC). My site monitors have reported a few outages, anywhere from 1 - 6 minutes a piece. By comparison, ServGrid and Linode haven't had any outages during my trial.

But their customer support is really fast, and I love the documentation and community they have around their offerings. I really wish they had a Dallas DC though.

I avoid that situation at all costs. My advice to anyone asking themselves this question is to simply stop working for, or around, people you don't care about. Solving that doesn't require a change in your economics, either.

No, we want to be servants for a large portion of our lives, apparently. We grovel at the foot of a master so that we can try to paint over the deadness we feel inside with bullshit...

There's a difference between being a miserable servant, and feeling enriched when put in a position of service. It really does have to do w/the type of person you are, and the type of people you surround yourself with. There are some people I truly enjoy working for, whether that be due to friendship or respect, or both, and I'll gladly devote hours of my life to their cause if they ask it.

At no time, however, have I drawn the conclusion that OP did. In cases when I've worked around people I'd rather not be around, I simply looked for better people or teams to work with. I didn't change my purchasing or other economic habits.

http://www.ubergizmo.com/2013/06/internet-explorer-11-ie11-m...

"We aren't sharing anything around which versions of Windows IE11 will be available on at this time."