Reminds me of this:

I think HN's ranking system penalizes submissions with too many comments because those tend to be controversial articles where upvotes mostly come from people wanting to express agreement as opposed to approval of quality.

Money's not an issue for us at this price range, but a lot of GitHub's strengths (lots of contributors and open-source projects) don't matter to us and the chance that we'll open source any of this is somewhere between slim and none. We also use Confluence and Jira already though I don't know if that matters. I've used both GitHub and Bitbucket, but very lightly and had pretty good experience with both.

It seems to me that we can't really go wrong between these two, but wanted to see if others had specific recommendations or insights.

Btw, there's this for those who like stuff that generates lots of discussions:

https://news.ycombinator.com/active

Thanks. I see you have a new HN account! Upvoted.

We use Confluence, Jira, Github, Gitlab, Gerrit and Jenkins. The combination of Github, Gerrit, and Jenkins works awesome.

Very strongly against IQ testing in any way shape or form. I was tested...lead to all sorts of nuisances.
[thinly vailed brag or beat]

Prolog and Emacs are the most common combination. Web stack is meh (would be fun to build a decent one in theory...skipping the typical DB for a fact/rule DB...declarative seems to be the all the rage in webdev these days)

Edit: someone PM me the HN title

Jira.... *shudder*

Seriously though I love GitHub pull requests and code review functionality. We've been using it for about the last 4 years. Never found anything I didn't like but I've never tried bitbucket.

GitHub has had some problems getting DDoS'd in the past and having service blips because of it. But nothing lately.

Do you have any recommendations for alternatives? What issues did you have with Jira? This is our "new" stack that we're evaluating and we haven't really started using much of it, except Confluence, so we're pretty much open to whatever.

I don't actually know what new jira looks like for you guys. My only exposure to it is through Apache projects - and its ****ing horrible. Extremely unintuitive UI, design style from the 90s, and a clunky process management style.

We've used pivotal/trello before to track issues and bugs.

Currently we're using GitHub issues to track bugs and trello for bigger picture things. It's actually working pretty well.

Edit: I'll add that I'm in love with GitHub pull requests and code reviews. I can't imagine many things better.

Edit2: Didn't realize I'd already written the exact same thing about GitHub...

2p2.com is back in the good graces of my work filter. Somewhere my boss is trying to figure out the source of my amazing productivity spike last week.

Oh wow. I was absolutely positive daveT's post was a parody. What. The. ****.

Haha. I couldn't believe that made the front page of Hacker News. 102 points and 96 comments?

I could just see it: when they got into work today, they see 1,000 emails and think, "woah! Look at all of that interest!" Then they start reading a bunch of trolling and angry emails.

I love the theory on HN about this being created by an outgoing disgruntled employee. It does seem unlikely that all of that stuff popped up via random Googling.

Nice work, candybar. Someone submitted it to Reddit 4 hours ago, but it isn't quite getting the bang it had on HN.

Do I need a certain amount of Dap to post my node framework to HN?

Another job I can't apply for because my Prolog isn't up to standard. I'll never reach the dizzy heights of $12/hr.

Where do you guys use prolog?

It's a joke. Prolog is useless except in specialised fields (AI mostly).

The addition of Prolog to necessary skills for a web developer job does make me a bit suspicious that it's a fake ad.

There's quite a few like that on my school's jobs board. Also, plenty of local governments in the area advertising similar positions/pay.

I often feel that many employers vastly overstate their real requirements, possibly because they assume applicants will also overstate their skill set.

I think it is a combination of several things actually.

1. It gives companies built in reasons for rejecting a candidate. We are not moving forward with your application because you don't have enough of this or that experience. Many job postings are ridiculous in the skill set they're seeking and what they're willing to pay.

2. It is intended to attract a wide range of candidates in the hopes of finding a candidate(s) that have an acceptable level of skill and pay requirements. If a company finds many attractive candidates that fill the bill on skill and pay they can select their highest rated candidate.

3. In a lot of companies the hiring process requires that a consensus be reached to bring on a developer. The hiring manager, the program manager, the team lead, and the team itself have to reach a consensus. A bad hire is pretty much a disaster and thus nobody wants to be held accountable for a bad hire. Once the various stakeholders in the hiring process have their say, the wish list can have a lot of items on it.

The above applies mostly to companies seeking experienced developers. I'm fairly certain that companies are willing to take more chances with new grads because of their pay demands but not sure.

ChrisV,

Good then. Had prolog last semester, felt like I'd be studying ancient cartography.

Anais,

Most C++ jobs I see are like that. C#/.NET jobs so far seems to have most reasonable requirements.

This is a big part of it. I wouldn't even say "overstate" - most people feel that rules only apply to other people and them being a special snowflake makes up for their apparent lack of qualifications. Maybe not most people, but people with this attitude are highly over-represented among job seekers, because they are often unemployed or unhappy with their jobs. This is even more true outside of technical fields - at least programmers tend to be fairly literal-minded and are bad at hustling.

I think you can submit regardless of your karma, but it takes a bit of effort to even give your submission a chance to get eyeballs - most submissions die a quiet death, and getting upvoted a few times at the beginning to make/stay on the front page is very important. Having some kind of promotional capacity (a popular twitter account, co-workers, etc) is useful. If you post something, definitely let us know here, so we can upvote it!

Up to a couple of months ago...daily for any programming task (mostly gameserver+AI).

Awesome! Thanks. I'm hoping to finish my blog post aimed at node novices this weekend.