nairteashop

That's correct (I used to mess around with this stuff several years back). There's a bit more detail in part 1 of this series as well: https://mixxx.org/news/2021-11-21-dvs-internals-pt1/

Let's set aside specific terms like "fascist" for now. Below is one of the demands from the government:

> the University shall commission an external party, which shall satisfy the federal government as to its competence and good faith, to audit the student body, faculty, staff, and leadership for viewpoint diversity, such that each department, field, or teaching unit must be individually viewpoint diverse.

Do you feel this is ok for the government to demand of an educational institution? This isn't about specific political ideologies. If the Biden administration had threatened to withhold funding from a university because, for example, their hiring policies weren't left-leaning enough or something, it would be equally outrageous.

The way I interpret "#1 Company, #2 Team, #3 Me" is that faced with a decision that benefits the company as a whole (i.e., all teams at the company) one that benefits only your team or you, you should favor the decision that benefits everyone.

For example, say your team has a huge hardware budget, and you notice another fledgling team that's working on something potentially more impactful to the company is struggling to get a decent budget. Ideally, you should transfer most or all of your budget over to them to benefit the company overall. (Mind you, I have never really seen this happen voluntarily, but again... we're talking about ideal/desirable behavior.)

It does not mean that if the company is acting in bad faith and is, for example, putting policies in place to force people to quit to save on severance or something, you go along with that and throw your team under the bus.

I think of "OKRs" as just a fancy name for two things: (1) What are you going to do in the next quarter/year/etc? i.e. what are you & your team's "objectives" (2) How are you going to achieve that? i.e. what are the "key results" you're going to hit to achieve your objective.

I hope most people will agree that, in an organization, having an understanding - and agreement - of what each team plans to work on, along with the trust that they have reasonably well-thought steps on how to achieve that objective, is incredibly helpful.

The problem is, as with "Agile", "TDD", etc, people will run with this and lose track of what the actual end-goal is, i.e. to build things that matter while ensuring coordination between teams. So, you will see things that don't make much sense, like OKRs for individual contributors, OKRs that change monthly, objectives that aren't necessarily right for the company, key results that don't really tie into the objective, etc.

I'm not sure what the solution is. At a previous gig, I tried asking management plainly to state publicly what they're going to do and how they're going to do it, and no one did it. Then I tried, let's do OKRs "just like Google" and everyone jumped on, even though IMO it's the same thing...

Sponsor is perhaps a strong word. You need another WeChat user to verify your account by scanning a QR code displayed on your app using their app. You need to do this when you create an account, and also if you haven't used your account in a while. I assume this is some sort of anti-spam/anti-bot feature.

Note that the above is just for the chat feature. You have to jump through more hoops if you want to make payments using the app.

Wordpress is actually not that hard to setup these days, but maybe a better approach is to start with hosted WP (e.g. wpengine) just to get the site up and running asap, and then later transition out into your own WP install when you have the time/resources.

There are a ton of websites built on WP (https://wordpress.org/showcase/), so it's not just a blogging-only platform.

For what you're trying to do, I'd definitely bet on a hosted CMS + a nice theme. You'll get a pretty website that's easy to manage, and it will cost very little in terms of time and money.

> why would you want to snooze an email?

I use my Gmail inbox as sort of a todo list. If a conversation is in my Inbox, it needs attention from me - I need to do some work related to it, reply to it, forward it, etc. Once I'm done with an email thread, I immediately archive it.

If you use this workflow (many do), snoozing an email is useful. I use it primarily for threads where I'm not able to reply and provide information immediately (so removing it from my inbox until I can reduces distraction), and for threads where I'd like to follow-up in a few days, if for example I don't get a reply.

Just back from a trip to India (from there originally), and don't quite agree with you that data plans are expensive. There is a lot of competition, and both talk time and data are quite affordable IMO. I pre-paid for 1GB of data and ~4 hours of talk time for just 250 INR (about $4).

Pretty much everyone in India - rich or poor - has a mobile phone these days. However, unlike the service, phones cost just as much as they do elsewhere so the poor usually end up using crappy feature phones with limited data support. A $25 smartphone with full web support would make an incredible difference IMO.

A few reasons why I'd like to pay by phone:

- It's a bit easier to pull out my phone from my pocket vs. pulling out my wallet, then locating my card, and then pulling that out

- Tapping my phone is an easier process than aligning and sliding my card through a narrow slit

- I'd love it if coin-like functionality is one day integrated into my phone, so I can select a specific card to use vs. digging through my wallet for it, or switch cards quickly and try again if the first one gets denied, etc.

These are all admittedly minor, but many successful technologies are about increased convenience anyway.

> I'd love to see optional typing in Python, I wonder if there is any official reasons about why it never got introduced.

Here are a few from Guido himself (not really anti static-typing, but just walking you through pros/cons as he sees them). Great reads:

http://www.artima.com/weblogs/viewpost.jsp?thread=85551

http://www.artima.com/weblogs/viewpost.jsp?thread=86641

http://www.artima.com/weblogs/viewpost.jsp?thread=87182

I was wondering the same thing, but I'm sure they ran the numbers and gauged driver interest before launch. Quite curious to see how it turns out.

Looks like they're staying out of that. The plan seems to be sell these cars to their top Lyft drivers, with the promise of more ride money.

From: http://www.theverge.com/2014/5/8/5694720/lyft-goes-after-ube...

"[Lyft is] purchasing the vehicles and having them outfitted, but then drivers have the opportunity to buy them and drive in them. The first crop of drivers given the chance to buy into that are some of the oldest and most active, Lyft says; how much they'll pay for that privilege, the company won't say."

We used to OEM HP ProLiant DLs at my last gig. Great hardware. The new DL320e starts at $579 list, so will definitely fit within your price point:

http://www8.hp.com/us/en/products/proliant-servers/product-d...

If you plan to buy a few of these, definitely give their OEM / enterprise sales guys a call - they give very good discounts off list (based on volume, of course).

> I've gone back and forth on whether managers should code and my opinion is: don't stop coding... Over time it means you'll have a harder time talking to engineers because you'll forget how they think and how they become bored.

For me, this is the money quote. Like rands, I've gone back and forth on this over the years as well, but I do strongly believe that you cannot effectively manage a team if you do not understand what it is that they do, at least at a high level.

You don't need to be as good at coding as the engineers who work for you, but you must know enough to empathize with them, and to help mediate dead-locked discussions.

I'll admit that there are exceptions, and effective s/w managers who can't code do exist, and I'll also admit that finding such managers is probably not a scalable task, but I feel it's something that every company should strive for.

I agree that "untracked" is probably the better term. The point of such policies is that if you need to take say, 90 days off because of family issues, the official company policy stipulates that this is ok to do.

If this had happened in a company with a fixed e.g 20 day vacation policy, then the outcome depends on your manager. Now, many would have no issue giving the extra time off "unofficially" in such cases, but there are also many who might deny that request - see other example in this thread about a company denying an extra 1 day of vacation!

This policy is a way to empower employees against such managers. Now, there are several other downsides to this policy, as OP has pointed out, and as I've witnessed first-hand as well, but unlimited/untracked vacation policies certainly merit a discussion vs. outright dismissal.

> The tricky part is striking a balance between usability and power.

Yeap, this is indeed the big issue. One thing that helps is to tune the UI for your specific domain so that it has just enough power to be usable in that domain, but no more. We had to build a query tool for retailers in my last gig, and tuning the UI just for retail helped a lot.

For example, make it easy to specify a BETWEEN operation in your UI if that tends to be used often, provide commonly-used domain queries as templates so your customers can learn by looking at and modifying these templates, etc.

For inspiration, you may also want to look at other products that have query building as core feature. Two that stand out to me in terms of usability are mixpanel and chart.io: https://mixpanel.com/segmentation/ (see "Goodbye SQL" section) http://chartio.com/product/tour (see "Drag and Drop Chart Creation")

> An optimal diet includes a mixture of foods that provide dozens of different nutrients in appropriate amounts and in the right proportions.

I wonder if we're any close to understanding what these "right" proportions are, and whether they are at all close to what is recommended by the USDA (which I believe is 45-65% carbs, 10-35% protein and 20-35% fat).

For context, this entry just won Google's DevArt competition: http://googledevelopers.blogspot.com/2014/04/devart-winner-a...

I have "product guy" in my profile :) so just a counter-point:

> Working on "Product" could mean you’re a PM, a designer, an engineer, or a bunch of other things I’m probably forgetting right now.

All of this is exactly what I did when I started my company, so I'm not sure how else to convey what it is I'm actually good at. Now, I was not the best at any of these, and we subsequently hired people who are to replace me in all of those roles, but for many months I had end-to-end responsibility for our product: the feature-set, design, engineering, QA, etc.

I do think that being a "jack of all trades, master of none" is a unique skill set as well. For example, I'm not a good designer, but I was good enough to build a decent looking MVP, and also to identify and hire a designer who is actually great. Same goes for engineering, QA, etc.

And the "guy vs. gal" thing... well, "product person" just sounds awkward, and "jack of all trades" sounds arrogant, so I'm not sure what else to use.

He actually posted this link yesterday as a comment: https://news.ycombinator.com/item?id=7581868

I really like "Reading Tip #1" in the "Links 2013" page, reproduced below:

It's tempting to judge what you read:

I agree with these statements, and I disagree with those.

However, a great thinker who has spent decades on an unusual line of thought cannot induce their context into your head in a few pages. It’s almost certainly the case that you don’t fully understand their statements.

Instead, you can say:

I have now learned that there exists a worldview in which all of these statements are consistent.

And if it feels worthwhile, you can make a genuine effort to understand that entire worldview. You don't have to adopt it. Just make it available to yourself, so you can make connections to it when it's needed.

I believe this is the news release from Cochrane that the BBC article is based on. There is more detail there on why they believe Tamiflu is ineffective:

http://www.cochrane.org/features/tamiflu-relenza-how-effecti...

Those are numbers for filed LCAs (a necessary step prior to filing for an H1), and not the actual numbers for approved H1s.

Does anyone know why the number of visas isn't capped on a per-company basis?

Last year, apparently 40,000 of the 85,000 available visas went to outsourcing companies, and one outsourcing company, Cognizant, got 9,000 visas!

http://www.npr.org/blogs/alltechconsidered/2013/04/03/176134...

At my last job, we tried to get an H1 for just one person, and failed in the lottery!

I feel there would be much less abuse of the H1 if each company could receive only say 100 visas a year max, or a % of their US workforce size max, or something.

It's a nicer javascript object based API for interacting with WebRTC. WebRTC by default uses an SDP offer/answer based approach.

Here is a more detailed rationale for this API: http://tools.ietf.org/id/draft-raymond-rtcweb-webrtc-js-obj-...

Serial entrepreneurship is not for everyone. Once you've put in nearly every waking hour of 5-10 years of your life into building a company, it is easy to see why doing that all over again may not be all that appealing. Especially once you've got a family and other competing commitments.

However, many entrepreneurs still want to help create and bring new and exciting things into the world. Becoming a VC is one relatively low-stress way of doing this. It is also a way of "giving back to the community".

The few ex-entrepreneur VCs I know have been amazingly helpful, and frankly I don't think any of them are in it for the money - they have quite enough already.

I'm sure that this has been brought up before, but I've always wondered whether it makes sense to split karma into comment karma and submission karma, reddit-style, and grant this new endorsement power only to folks who cross a certain comment karma threshold.

Since now users with high karma will have a lot of power (than just downvoting, which IMO was relatively innocuous), I think it makes sense to ensure that this power goes to folks who have gained that power by contributing meaningfully to the community over a long period of time, and not by by a few - oftentimes lucky - submissions.

Am I totally off-base here? Or maybe this has been considered, but was too big of a code change?

More details from the linked FT article (which is behind a paywall):

- Official announcement will be made at next week’s Geneva Motor Show

- Integration includes Siri, phone calls, maps, music and video.

Acquisition offers are a great external validation of both your product and the market you're in. So my take is that it's a very positive thing to talk about any potential acquisition offers, as long as you stress that that's not your end game.

Take for example Drew Houston turning down the acquisition offer from Jobs/Apple back in the day; probably did wonders for Dropbox's valuation in the following round (and very rightly, if so).

I think the point others are making is that unlike, say, your height, "vision" is actually a combination of raw input from the eyes, and the subsequent processing of that input by the brain.

Therefore vision can be improved by making the eyes better - contact lens, lasik, etc - or by making the brain better - presumably what this app is doing.

A (very poor!) analogy would be how you you can use post-processing in software to capture better images, even without changing out the lens or the camera. Upgrading the algorithms in the software will result in better images.

Note that I'm pretty skeptical of the claims as well, but I also acknowledge that this falls within the realm of possibility. About to download the app so I can verify for myself...