dpritchett

I like this phrasing from Wikipedia:

"The inverted pyramid is a metaphor used by journalists and other writers to illustrate how information should be prioritized and structured in a text (e.g., a news report). It is a common method for writing news stories (and has adaptability to other kinds of texts, e.g., blogs and editorial columns)."

Can confirm that I was able to reproduce after tweaking some of the special characters in the above PoC.

This is what I get on an unpatched staging server. Not sure it did anything...

    $ sudo convert file.mvg o.png
    convert.im6: delegate failed `"curl" -s -k -o "%o" "https:%M"' @ error/delegate.c/InvokeDelegate/1065.
    convert.im6: unable to open image `/tmp/magick-Yjc5q9f1': No such file or directory @ > error/blob.c/OpenBlob/2638.
    convert.im6: unable to open file `/tmp/magick-Yjc5q9f1': No such file or directory @ error/constitute.c/ReadImage/583.

I respect the idea of a vibrant job market but free pizza seven nights a week sounds a bit like hell.

I wouldn't prioritize it if I were you either ;)

We're on 8.1 I think. We are running a largeish C# project with largeish diffs; when I click "merge" the app spins for a good few seconds or more before completing the merge. Don't think I've ever seen that sort of delay on github. I wonder if you could pre-merge in a separate system branch then do some git magic to rearrange them once the user actually clicks merge?

The things I miss the most using Gitlab vs github are the instantaneous merges and the syntax highlighting within diffs when reviewing a MR. I'm on an old-ish version of gitlab though and it's running on a single VPS.

This suggests that StarFighter has some cash that is being used to keep you afloat. I don't expect you to disclose, but I'm guessing there's a silent partner or maybe just some ex-Matasano money floating things. Cool!

Was the 0% turnover due to great teammates, great projects, or above-market comp? I've never seen 0%!

I for one enjoyed these human touches in what was overall a very calm and reasonable essay.

I'll be one of the new maintainers at my newish job here in Memphis. Neat to inherit such a cleanly-managed Rails codebase!

Yes, I think you'll find that the majority of U.S. citizens will vote down a tax increase, even if the intentions are good.

They'll say "I don't trust the government to spend that money properly. Take $232/yr away from some entitlement program that services people who aren't directly related to me."

Looks cool! I just noticed the search is case sensitive - "php" returns no results while PHP returns quite a few. Same with c#/C#.

Thanks!

They must want people to always feel like every Medium article is fresh.

Meanwhile in the page source:

  <meta property="article:published_time" content="2015-07-30T17:21:08.966Z">

[0]: http://www.paulgraham.com/submarine.html

I wonder what their PR budget is like?

There are some end to end Clojure shops. Pretty sure Relevance uses cljs.

I did some brief research and I'd call it a mixed bag. Looks like he definitely had a high-tech upbringing, but not necessarily a silver spoon.

Wikipedia mentions he attended Cornell and CMU (PhD).

Freakonomics blog says "He grew up in a middle-class family that lived beyond its means, in large part because his dad was about to hit it big with a computer business and the family was banking on that success. Then the success happened, and the family lived even larger — until the business suddenly fell apart, leaving everyone devastated.

Years later, James struck out on his own and he, too, struck it big."

http://freakonomics.com/2007/05/03/james-altucher-strikes-ag...

Don't get too caught up on which job role has more risk, responsibility, or communication skills.

Salaries are apportioned based on how close a job role is to the company's revenue stream. Executives come out on top because they control the money and payscales. Sales is often second because they can very easily point to new revenues and say "I brought that in". Profit center staff (most Valley engineers) would be somewhere up there because they are at least creating the actual product that the business sells. Support staff - cleaning, office managers, accounting - bring up the rear because they have the hardest time claiming responsibility for a share of the pie.

Within each of those groups you'll see normal salary dynamics based on wider market forces and hierarchy. Engineering manager's gonna make more than most of the line engineers. Comptroller will probably make more than a line engineer too even if she's considered a cost center because she's in a position of relative authority and individual responsibility.

Study questions:

- How close are you to the money?

- How legible are your contributions to the bottom line?

- Could you get significantly more elsewhere for the same role?

- Is management incentivized to retain top-shelf people for your job role?

I have never messed with panic, I read that code and I think I'd make a function that takes functions - the error handling response is the same every time. Maybe even put the list of calls in an actual list and invoke them with an iterator.

The goimports tool can be used to automagically add and remove imports to your .go source files as you work. This streamlines the casual weekend hacking use case without compromising on the benefits of disallowing unused imports.

It's not a silver bullet but it's definitely helped our company. We are a mostly-remote Rails-focused company with tens of people throughout the Western hemisphere. I've found my communications with clients and teammates got a lot better once we added Slack to the Google Apps + Skype setup we already had in place.

I wish they'd gotten Jo's name right. Luckily her work speaks for itself.

Your title is fine, SwellJoe. I was being petty and pointing out a case where a descriptive title that didn't match the HTML <TITLE> dramatically improved the submission. I have long felt HN's title renaming policies were a bit too aggressive and I'd like to see 'em go away.

This wasn't the right venue for me to bring that up though - things have improved a good bit under dang's tenure already.

As a reference for my outdated and inappropriate axe grinding see this 2013 thread: https://news.ycombinator.com/item?id=5142851

Mea culpa.

Does HN still have those frustrating title renaming rules? If so this would be a good time to insist on using them.

This is what adjuncting is supposed to be for - folks with industry experience moonlight as professors. The benefit is not primarily salary but networking, knowledge sharing, and helping the next generation of industry professionals.

Now it's more of a way to have 2/3 or more of the department work for unliveable wages which allows for an ever-growing administrative overhead in colleges while tuitions double every decade.

The question for Google is whether Page, Brin, Bak, Buchheit, and Dean passed an algorithm interview before building Google's core technologies. Hiring doctrine after the fact does not ensure a billion dollar company.

I disagree with your assertion that lambasting Google's hiring practices is an easy sell in the market. The last time I tried I was dismissed out of hand by a talent consultant.

Bummer. Her career seems to be predicated on a correlation between algorithm tests and performance. Can't expect her to seriously entertain disagreement as long as the current model is profitable for her.

Google is no more a proof of the value of algorithm tests than Github proves the value of manager-free organizations.

I was a bit horrified at the acquisition coaching comment. I did not realize that happened but of course it makes sense. Can't manage an acquihire if your devs can't pass the algorithm tests at the big acquirers. Shame.

How does this compare with "Did you win the Putnam?"

https://news.ycombinator.com/item?id=35079

If comprehension and spelling were decoupled but still equally weighted then the aggregate score would've been significantly higher. Let's split the difference and say that 20-30% on the set of [all answers simultaneously spelled correctly AND comprehended] becomes a 25% on the "spells things correctly" axis. If we weight that equally against the "comprehension" axis then you get

  let R = 25   # reading
  let C = ?    # comprehension
  let M = 40   # reported mean

  (R  + C) / 2 == M
  (25 + C) / 2 == 40
  (25 + C)     == 80

  C == 55      # implied comprehension grade from a 40% average

If comprehension was any higher than 55% - which this anecdote certainly suggests - then the 40% aggregate score awarded is an ineffective assessment of the holistic learning picture.

This is the grade school equivalent of tossing out resumes over a single copy editing mistake.