skysight-inc/HackerNews huggingface dataset:
Yes, but there is also the opportunity cost of your downpayment, the transaction costs of getting into and out of a house, and maintenance. Oh man, maintenance.

Ref - transaction costs. You have to figure it will cost you around ~8% of the value of a property to both get into and out of it. This does not include the cost of movers. With a rental your transaction costs might be $50 for the apartment application fee.
Rebase Ubuntu Touch on Android, Says Former Ubuntu Community Manager
I recently started working a 4-day work week and gained some great feedback here: https://news.ycombinator.com/item?id=9505868

Rather than use the 5th day as a casual, side project workday as it seems the author of this post has done, I decided to take the day totally off. So far it has worked fairly well, though I have had to check in a few times (as I am currently doing).

The most important factors of my decision to experiment with the new schedule was that I have a 4-month old and want to spend time with her and my wife. I was also pretty confident that I didn't actually have enough work to fill 40 hours and was spending a good amount of time reading news or whatever else from the office when I could be hanging out with my family or enjoying the outdoors.
How is that disagreement?
Probably should have come up with a better name. The natural English syllabification of this is 'wog.ram.mers', rather than 'wo.gram.mers'. That's a barrel of worms you don't want to open!... Which is a shame, because such an initiative isn't one that should be pulled down because of something so superficial.

EDIT: The natural British English syllabification, where 'wog' is a derogatory racial slur.
"Web users, that is, who also are git users – i.e. most likely programmers."

Who on earth would be a programmer and git user and not be a "web user"?
Ironically, for that reason, GitFlow would work better in Mercurial. Go figure.
The Man Who Inspired Jobs (2011)
I initially thought it was something different: https://en.wikipedia.org/?title=Wog
"wogrammer" ?

Do we really need a word that exists purely to make the distinction between male and female programmers? Seems to me you're just a programmer, sex doesn't matter.
Renting is the best option for flexibility. Want to add a bedroom? Want to change neighborhoods? Just lost your job and want to downgrade? Want to move closer to your new job, or an entirely new state? These are all good, common use-cases for renting. BTW, a lot of landlords will let you modify your place - some will even chip in for the costs or pay it all.

>Plus why spend money on somewhere you don't own?

People have this mentality that renting is throwing out money. It's not - it turns your housing into another explicit cost like food and travel. I like this, I think too many people make the biggest investment decision of their lives (often by orders of magnitude) so lightly. And anyway, when you own, the costs that would go to renting are priced in, like: taxes, upkeep, opportunity costs, and interest payments. There is no free lunch - even the home ownership tax benefits get priced into housing costs.
The long hiring times seem not to be due to lack of applicants, but due to internal hiring politics and process. Rising conservativism about making a "bad hire", perhaps.
True, but there's always the risk that where you like living changes over time and becomes HELL 20-30 years down the road. And I have seen this happen among several of my family members.

When you rent, sure, you can't stay forever, but you have visibility at 2 years down the road (depends on the country where you live, but where I do the owner cannot get you out for the duration of your lease, and that's usually 2 years).
3 models for civic hackers: green field, cloned, augmentation
The king is dead, long live the king!

I've been using quicklisp for a while. It's working just fine, as far as I'm able to use it. But I haven't found out yet where the lost “user documentation” for quicklisp is buried. Do you need to read all sources in order to understand it?
In Canada, I used to get a lot of recruiters contact me from Monster and Workopolis, but now I get a lot from LinkedIn. Just a few days ago a manager at Amazon reached out to me on LinkedIn. So it's definitely helpful, I wouldn't discount it.
> His situation was akin to you waking up one day and finding, out of nowhere, a letter in the mail telling you to come in for a 6-month jail time.

That's a complete misrepresentation. A reasonable person might expect there to be consequences for breaking into a closet while hiding your face from security cameras in order to retrieve a covertly installed laptop you put there to evade a network ban. That is not "out of nowhere". I'd even say it doesn't resemble my hobbies in the least.
I don't see Node.js and Homebrew as "web related".
This is getting more and more hilarous FFS. Will we have a special group for afroamerican women programmers ? Special group for mentally ill programmers ? Or what about vegan transgender programmers ? This kind of positive discrimination is really annoying and unfair. Using the right tool and right people should be free of all prejudices FFS
Let's imagine you want to embed parsers into your language. Choose any parsing algorithm you like, but parsers must be defined in a BNF-like syntax.

You can go slow an buggy way (Parsec and alike), or you can compile your embedded BNF into a nice, verified, optimised implementation.
Feel free to fork and contribute :)
https://github.com/idoco/map-chat
I'm just trying to give an idiot test at this point. I don't know why people still aren't passing it.
What if you are not working?
I disagree, this view is too simplistic.

It's very different to owning shares in a company. You have to either buy a house or rent. You cant opt out entirely, whereas you can with shares.

By choosing to rent, you are betting on the housing market being stagnant or falling, if house prices shoot up and you opted to rent, you will need to now pay higher rents or a bigger mortgage.

So there is risk in renting too

If you decided to rent in london instead of buying 3 years ago, you'd be tens of thousands down
It's not clear to me that, say, $500k of assorted shares + $500k of house is worse than $1M of assorted shares. You've got more in a single asset, which is bad, but you're diversified into more asset classes, which is good.

The picture is a bit different if that $500k is all your assets or even substantially more than all your assets (a common situation for a first-time buyer with a big mortgage). Which suggests you should rent until you've built up substantial investments of other sorts, and then consider buying.

Historically, I think the variability in price of a single house hasn't been any worse than that of, say, a typical index fund. (Disclaimer: I haven't actually checked the figures.)

Of course, all the above treats houses as just another investment. This is a useful perspective, but you're going to be living in your house too, and questions like "can I redesign the bathroom?" and "if there's a flood or an earthquake, am I liable for fixing/replacing everything?" and "am I bothered by the possibility that my landlord might just throw me out one day?" and "can I get up and move somewhere else with minimal hassle?" may be just as important to you as "what is likely to leave me with more valuable assets 20 years from now?".
We ask an open ended design question. For example (not a real one), when hiring an ME we might ask, "How would you design a new kitchen stove?"

There isn't a right answer. One person might ask more requirements ("electric or gas? Home or professional") while another might state themm up front ("well for this project I'll make it a gas stove since I think that's nicer to cook on in your kitchen"). One might go down more on the design or cosmetics, another safety, another weight and price...

We look at how they look at the problem and take it apart, how they react as they go down a path they later don't like and want to backtrack ("hmm you know I really should have allowed room for an oven because at home most people want both, and if I do this I can save some parts, so let me cross this part out"), how they react to questions (defensively or confidently) etc. One person might say, "I'm sure there's some safety code about XXX but just for design I'd worry about this shutoff" while another might say, "and we put this valve in here for safety code 1234..." Both are fine.

These are nice because 1> they are open ended and should be fun 2> they don't relate specifically to the company's business (we're not in the stove business) so it's not a trick question to see if the candidate knows some special safety code or something 3> they allow the candidate to show themselves off without needed to be glossy or get everything perfect.
The subset of "web users" who use git/source code control is almost 100% programmers, true. But the subset of programmers that are programming web apps most certainly isn't. I know a lot of programmers; I don't know a single web programmer.
It's a trade off.

I live in London, UK in a flat I rent for £950 pcm. This would cost me £379,000 to buy, at the very least as it's a relatively nice area.

I could scrape the deposit and get a £379,000 mortgage but the insurance, maintenance and other costs on top would result in zero disposable income.

Currently I have £1750 left over every month which is nothing but bags of freedom to do whatever I want.

If I was to drop dead on Monday, the last great event wouldn't be getting Magnet in to do my kitchen, painting the living room ceiling and sitting in all weekend eating Tesco Value food. It would be chilling next to Lake Geneva in Lausanne with my other half which is exactly what I'm doing.

Live life now before it's over.

Edit: This is based on the advice of my wife's grandparents who are just about hanging on at the age of 84 and 86 respectively. They had to cancel their cruise this year due to poor health and openly admit that they worked way too hard for a house. They have a nice £1m house in London and a pile of savings but it's worth nothing to them now because their health is gone. It's empty as the children have left and they realised the memories were more important than the bricks.

So, sod buying a house. I'll live an irresponsible yet fulfilling life now.
HR are a major problem in many large companies.

Oftentimes, they're lazy (outsourcing most of their job to expensive recruiters and agencies), obstructive (creating all manner of stupid, bureaucratic, red-tape hoops you have to jump through before they'll approve whatever it is you're trying to do), and add zero value to the actual process of recruiting an employee.

My hat of HR know no limit.
There's at least a few places out there run by Mormons who do hair-tests on their employees and won't hire you if you've been drinking alcohol. Even for high-level managers, executives and the like. (Enough of them that I've run into one person talking about her employer doing that, anyway.)
No offense, but this is a really bad license.

A. The other licenses include very explicit copyright grants. Copyright is a bundle of rights. Literally. The other licenses are explicitly mentioning what copyright rights you get and what you can do with them.

You aren't.

This opens the world up to fun arguments over what "Do whatever you like meant", with one side arguing that "no, i didn't mean the right to publicly perform" and the other side arguing it does.

It may seem like this would never happen, but trust me when i tell you this is what will happen (and in fact, it has actually happened out of court) :)

Unlike BSD/etc, it also makes things like "the scope of any implied patent grant" super unclear.
Without specifying exactly what the user can do with it, it's unclear what patent rights they are going to get with it.

2. It has no warranty disclaimer. In the US, you are opening up anyone who uses this license and produces commercial software to implied warranty claims. They happen. Without a disclaimer, you will lose.

I could go on. WTFPL is actually one of the few licenses the companies I work for ban, because it is so bad for people in practice.

I would love to live in a utopia where nobody should have to worry about these things and i could forget about the open source lawyer side of my life (and i spent a lot of my life trying to help get us there). But we aren't there, and acting like we are isn't going to help anyone, and doesn't advance any cause, either.

So, please, don't create new licenses, and if you are, take the time to understand why people have written existing licenses the way they have.
Almost skipped it due to the playful paragraph clearly written with thesaurus close at hand, but this is interesting.

Hate to be the guy complaining about design, but the fixed, vector-art background doesn't really play well with reading while scrolling.
This is actually sometimes the case, though please double-check your analyses before committing to outliers or "betting the farm". Since it does happen and can work for some people / some places it certainly complicates the simplified dichotomy presented in the OP and this topic.
You can't discount the role of applicant volume in that, though; if you have a 20 day hiring process with one person going through it at a time, the odds of it taking 40-60 days are a lot better than if you have 2-3 going through at once.
1. It wasn’t a description of IMAX, it was a description of something else by comparing it with IMAX. It was not describing IMAX.

2. It was someone else who was describing something and likened this other thing to IMAX. Ars was quoting this person, not writing it themselves.

Don’t drag out the “confusion with consumers” thing – absolutely no-one would think that this thing actually was an IMAX™ – it was a comparison. Would I be sued by Coca-Cola if I said that “Pepsi is kind of like Coca-Cola”? Would I cause “confusion with consumers”? No. Trademark law does not mean that trademark owners can control every use of the word, despite what they (and apparently you) would wish for.
"IIRC all US government contractors have to be tested on hire"

That must be a new -- post 2007 -- thing, then.
An ex-girlfriend of mine applied, on graduating, for a job at a prestigious investment bank. She heard nothing back.

Eighteen months later, after she'd been through two jobs and emigrated, they sent her a letter expressing interest.
I've worked all kinds of hours in many situations. My favorite are 4x10 shifts. They give you the full pay without the extra day of commute.

Next up would be a Sun-Thurs shift, I never do anything on Sundays that I can't do Fridays, and this is great for errands, catching up, etc.

My least favorite is overnight 10p-6a. These shifts are rare, and it's easy to feel like all you do is work and sleep.

Second least favorite is 4h Wed, 12h Thurs, 12h Fri, 12h Sat. They slimmed a 6-person team down to 4, and had an unmanned window of time on Wednesday. I drew the short straw and so worked 6p-6a. HN was my playground during those hours.
I totally agree, but If you want to use R consider also this:

install.packages("LaF")

Package for fast access to Large ASCII Files. Can be used with big files that don't fit in the available memory.
>For example, next time I could take new client is after autumn and it's now June 5th.

Sounds like demand is greater than supply. A nice spot to be in for any business! Have you considered hiring help? Are you able to figure out a way to delegate some of the additional work and someday claim another day of the week?
The key is that most of the effort is not where most of the data is. It's the small percentage of data (say, database index) that requires the biggest development effort, and you want the best mechanism to assist not where most bytes are stored, but where the most effort is invested.

> For systems where managing data is one of their reasons for existence, it creates a negative effect.

I think that people who author such systems/libraries know when to rely on the GC and when not to.

> GC'd runtimes also bloat memory consumption to support GC

When you write, say, an in-memory OLTP database (that's the use-case I know best), you keep the index -- that's where concurrency is managed -- on the heap and the user data off-heap. User data is the bulk of the RAM, but you only pay the GC footprint-overhead for the index.

> you're swimming upstream the entire time.

Going off-heap for large, known-lifespan data sets in Java has been widespread -- idiomatic, almost -- for at least five years now, if not ten. There are so many libraries that do that, that it's very, very simple. Again -- that's just where most data lies, not where the most effort is required. You end up with a very small percentage of your code that is not quite "beginner's Java" -- that's not swimming against the current; that's hitting a few strokes for one tiny section of the journey. It's managing the transactions and update to the indexes that requires 95% of the code, and where you end up thanking your lucky stars for a good GC.

I haven't measured exactly, but the entire off-heap code in our database is under 3%, even though over 85-95% of the data is stored off-heap.

> Instead, you want to delineate ownership so you have single writer and many readers, and share the data that way.

Even single writer/many readers still require a concurrent access mechanism. A GC tremendously helps with this pattern.

Besides, the best way to manage data -- and that's based on how caching mechanisms work at every level -- is single-writer/multiple-readers approximately, namely the single-writer may change identity at any time, but you ensure that it happens rarely. Once you try to make ownership permanent, system-wide locking is required. It's that flexibility that helps with amortizing the costs and making sure you're never hit with the worst case at every transaction[1]. There's some literature touching on that required flexibility, but here's my own take: http://highscalability.com/blog/2012/8/20/the-performance-of... (that flexibility is required to keep the B-tree evenly distributed across nodes -- they can be across the network or even NUMA sockets).

[1]: Changing the owner is the amortization pressure-release valve (all amortized algorithms work on that idea of slowly increasing pressure, that is then released seldom but regularly). It replaces sharding's rebalancing, which usually requires a stop-the-world lock (or most of the world).
Rebasing Ubuntu on Android
Want to live somewhere else without making a life-altering financial transaction that could lower your net worth tens of thousands of dollars?
That'd be cheap for London. It's normal to pay 1k+ a year
I should have been more clear - I agree that its more complicated. My point was that regardless, it seems to resonate. I believe its because the complications look useful at a glance and layering a rigid model on top of git frees you from having to consider its full scope of possible operation.

(I believe that git flow is definitely better than "everyone does things their way", and that's one competing "rule-book" for a team new to git.)

I'm pretty confident that understanding the tool better will help you to judge how to use it more effectively. The best way to understand git is to understand its data-model.
You don't need to implement ALL of gitflow - I see it as scalable.

Master should always be latest production code, development branch contains all code pre-release. That's the core.

The other branches let you scale gitflow - if you need to track upcoming release bugfixes etc, you can use a release branch. A team of maybe 6 or 7 would likely start to need a release branch. Feature branches at this point are best left local on the developers repository. They rebase to fixup commits, and then merge those into develop when they're ready.

If you get into bigger teams - like maybe 6 agile teams working on different larger features, then you can introduce feature branches for the teams to use on sprints to keep the work separate.

The issue with gitflow is the lack of continuous integration, so I personally like to get teams to work only on a develop branch during sprints and use feature toggles to commit work to the develop branch without breaking anything.

As I see it, gitflow and CI are at odds and that's my biggest gripe with integrating lots of feature branching for teams - everyone has to integrate at the end of the day.

So I believe the model can and should be scaled back as far as possible, using only develop and master and release as primary workflow branches, introducing the others when the need arises - doing it just because it says so in the doc isn't the right approach.
Obviously nobody will hire people who's unemployed.

/possible sarcasm
To avoid having to actually do some real human thinking. Fail a "drug" test, you can just treat those people as scum, not worth your time, disgusting pariahs. You don't have to look at them as human, and actually use your wits to decide.

People who, for example, smoke marijuana, will fail a drug test. Will they miss work because they're hungover from a Big Weekend? No, mostly not. Will some straight arrow call in sick because he or she got sick on Sunday evening? Yes. We know this. But to avoid having to cope with ambiguity or grey areas or hard decisions, we just let a "drug" test do it all.
What kind of gig was the 10p-6a?
This article (the article we're commenting on, not the article you linked) precisely points out why Streams will not save you.
The point, of course, isn't that they would think it was literally an IMAX. I'm not sure why you're arguing against that, frankly.

But that consumers could think it was IMAX certified or some such. That sort of thing is worth defending.
Indeed. If one that expression, one wonders what the ramming is all about.
And even if it still did mean "gigantic screen with impeccable quality controls" like in the days of old, it still wouldn't matter!

And that's because a trademark is exclusive rights over using the name for a commercial purpose. So the IMAX folks could make a product called IMAX-VR if they made a VR headset. But the Oculus folks, if they got some 8k phone screen, couldn't call it Oculus-IMAX without a licensing agreement, because IMAX owns the name IMAX with respect to product names.

But owning it with respect to product names doesn't mean you can prevent people from using it at all. How else would Coke (tm) be able to tell you in a commercial how much better they are than Pepsi (tm) as a result of some ridiculously staged "public tastings" where regular people prefer Coke (tm) to Pepsi (tm) three to one?

Anyone can refer to someone else's trademarked product name full stop. The only thing a trademark does is prevent other people from naming their products the same as, or confusingly similar to, the one which was trademarked first. And if someone thinks their new product name is different enough to be confusing the trademark holder still has to take them to court to prove it.
This kind of "territorial pissing" is, I'm afraid, necessary in order to maintain the validity of a trademark. Seems heavy handed. Whether you agree with it or not, if you have shallower pockets than the trademark holder then you probably lose.
I agree with you, with one addition in GitFlow's favor--it standardizes how your team works. When you have multiple team members collaborating on a project, a poor standard is better than none at all.
Those are unrealistically low applicant volume numbers, surely?

http://www.telegraph.co.uk/finance/jobs/10949825/Employers-r...