HN user

tsmith

221 karma
Posts9
Comments77
View on HN

Anecdotally, I have never heard of anyone getting a job at a FAANG with that kind of salary working remotely from day 1.

The cities the parent comment mentioned (Ann Arbor, Boulder, Toronto, Tel Aviv, Boston, Seattle) are all cities where Google has offices. So, the folks they mention weren't working remotely, but rather working locally in remote offices.

Source: Google San Diego employee

I am guessing OP was able to decrease his/her taxes owed by $1500 (e.g. by deducting marginal income by $3000 at a combined state and federal marginal tax rate of ~50%).

*Edit: or, as cbhl points out below, OP is married filing separately, in which case the deduction limit is $1500/year (multiplied by marginal tax rate to yield actual tax savings).

more losses than the capital loss deduction limit ($1500)

Currently you can deduct up to $3000 of short term capital losses per year against other types of income (e.g. regular employment income), and any remaining balance can be carried forward indefinitely.

History has taught us that diversification efforts (i.e.: initiatives to correct systemic inequalities) unfold like this: White men "let" white women into the halls of power they created, and little changes for the rest of us. Such is the case in politics, in elite universities and in corporate America.

Well tickle me Elmo, and here I thought we'd just gone through two terms with a non-White president.

Hiring for cultural fit is just laziness, and interviewers should stop using it as a "metric".

Assessing for ability is extremely difficult - in the case of programming positions, technical interview processes either suffer from a large number of false negatives (e.g. the "Google filter") or a large number of false positives (e.g. "this person doesn't know how to write a for loop; how did they get hired?").

Per the article, most interviewers interpret "cultural fit" as "personal fit" - how well do you like the interviewee? The example heuristics (going out for a beer with the candidate, spending a snowy night in an airport together, etc) have very little to do with company culture and very much to do with answering the question: "Do I like this person?".

Any 4 year old can tell when they like somebody. It's one of the easiest things in the world for a human being to assess.

Technical ability, on the other hand, is one of the hardest things in the world for human beings to asses, at least in the context of an interview. Assessing for "cultural fit" - which on the face of it makes perfect sense as a hiring metric - devolves into a way to avoid doing something difficult (assess technical ability) by doing something easy (assess personal affinity).

Also missing: put it in the bank (i.e. do nothing).

The answers to the "greatest satisfaction" question are also telling. They are all job/business related. There's not even a single "spend time with my friends and family" catch-all.

I'm moving to Seattle, and impulsively ordered 1Gbps residential internet service "just because" (from CenturyLink - IIRC it's ~$110/mo).

I since realized that I had no idea what to do with a 1Gbps residential pipe, other than "download things really, really fast."

So, I Ask HN: does anyone have any ideas for interesting use cases for Gigabit home Internet?

I always thought MADD (Multiply + Add) made a great candidate for a single instruction set computer, if the program counter was usable as an operand to the instruction.

I Quit 11 years ago

Is HN depressed? Two ragequit posts on the front page at the same time?

Folks, the software industry is cyclical, and we are currently in the "good times" phase. Non-software people in other industries are seeing their occupations become obsolete while we we are getting increasingly higher wages, shuttle busses, and microkitchens.

If you are not happy working in software now, you probably won't ever be.

People understand that the compiler/executable doesn't run any faster the less newlines there are, right?

This is cute, but as others have pointed out it, it isn't really a correct implementation of a hash table. Also, it wouldn't pass a code review anywhere I've ever worked.

Impending kOS 12 years ago

Sounds great! Where's the documentation on IPC / mutexes / threading?

todo

files, procs, tcp/ip, usb, ..

Oh.

[dead] 12 years ago

The only aspect that seems like it might fall under the category of anything except for age discrimination is the photo requirement.

Summarizing the highlighted passages:

  - they want a go-getter
  - they want someone who enjoys working long hours
  - they don't want people who do things only for the perceived social benefit
  - they don't want people who have no social skills
a.k.a. a culture fit.

Granted, the job requirements are a bit hefty for the salary (US $3.2-4k/mo), and the 1+/2+ ratio of years managing vs. years developing seems a bit... naive, but maybe that's market in Singapore (which IIUC has a flat, low income tax), or maybe perhaps they are just trying to underpay - like most un-/under-funded startups everywhere.

If you have a pilot license, and call into the ATC to get clearance, can you operate a drone for commercial purposes (e.g. taking photos for real estate listings)?

In the OP, double-entry accounting is taken to mean that the two parties to a transaction each keep a record of it (and by extension triple-entry accounting is if three parties keep a record of it). This is a mis-use of the term "double-entry accounting" to mean "two-party recordkeeping".

Double-entry accounting means that for each transaction, there will be two (sometimes more) entries in the ledger (set of accounts) - one on the "credit" side, and one on the "debit" side. For example, when you withdraw $100 from your bank account, from the bank's perspective it is crediting an Asset (Cash) and debiting a Liability (Customer Accounts), so a credit entry of $100 would go into the Cash "account" and a debit entry of $100 would go into the Customer Accounts "account".

Triple-entry accounting implies that a third entry would go... somewhere else in the ledger; but OP isn't describing a classic set-of-accounts ledger.

We eventually gained each others trust, and our visions started to coalesce, but only after spinning our wheels for 6 months.

Everyone on the team suffered from burnout.

11 months later, our team decided to cancel the project.

My guess is that the lack of a singular clear vision caused everyone to become disenfranchised / burnt-out in the first six months, and it took another 5 months for people to realize the project wasn't going anywhere.

I think the story underlines the importance of having product leadership - it's all well and good to have a flat organization when the product is already defined and the only thing left is adding features / fixing bugs (as is the case with the github platform), but if you are starting from scratch you can't expect a product grow to grow organically from the combined whims of individual contributors.

The best software comes from a team where everyone shares a vision, cares deeply about the result, and are motivated to make it happen.

Definitely!

That level of caring and motivation can only come from people that had a role in crafting the vision and own a piece of it.

Yes, but Design by Committee is a cliché for a reason.

Isn't that an example of a "diversification" strategy, similar to the "join many clubs/activities in high school" approach? The fact that it's a strategy (and therefore involves prior decision making - specifically the decision to follow the strategy) doesn't make it a "determinate" strategy.

I believe the lecturer (Thiel) is advocating for determinate strategies - which, practically speaking, reduce the surface area for luck since time is a finite resource. My interpretation is that he is advocating for "moon shot" approaches (examples given: Tesla, Space-X, AirBNB) where the plan/vision is laid out from the beginning.

This contrasts with the iterative "lean startup" approach whereby an initial product is launched followed by an iterative customer feedback loop. The evokes raises an interesting question: is the "lean startup" methodology an artifact of "Indeterminate Optimism"?

"Every new idea or piece of feedback about your start-up has immense value and it's up to the founder(s) to prioritize these ideas and suggestions and utilize them."

The author seems to be in the fortunate position of never having suffered from feedback overload.

In my experience, anyone is willing to give feedback when asked for it, and most of that feedback will be wrong and/or conflicting with the advice of others and/or inapplicable to the situation at hand.

As a founder, it is your privilege and your duty to free yourself from the opinions of others and blaze your own trail.

I'd been wanting something like this as I have a few physical mailboxes but rarely need the physical mail itself. Do you have any useful links to the 1583-based providers?

+1

I transferred midway through my undergraduate degree, and was surprised to discover that Karnaugh maps weren't taught at my destination school - they are such an intuitive and straightforward mechanism for whittling down complex logic into its simplest form.

I don't think the point is so much around what the CEO says about the engineering team publicly. It's one thing to proclaim that your engineers are the smartest in the world/industry/space; it's a completely different thing to expect them to work miracles.

The toplevel post is a warning to not drink your own kool-aid when making executive decisions about what your team can and should accomplish; e.g. your team may be extremely smart and talented, but so are the teams of everyone else, therefore don't think your team will be able to accomplish miracles.

Pretty sound advice.