skysight-inc/HackerNews huggingface dataset:
This is not my experience. I interviewed in the Bangalore office, and I had 5 algorithm rounds straight in the on-site interview. I was exhausted after R3, and screwed up R4 and 5. Me being an experienced candidate, it seemed ridiculous that they'll judge me on the basis of algorithmic ability alone (No design, no behavioral questions, nothing).
In my team, we do stand-ups in chat. It's basically just to get a sense of what the UX guy is doing, how the UI is coming along and what APIs that I need to build or fix for them are, etc.

Since we do stand-ups in chat, it takes a whole 30 seconds of my time, and I just read what the other guys are doing when it's convenient.

The only in-person planning we do now is our sprint planning.
Solve your own minor problem.

For me it would be be searching in source for anything that is built in release not debug mode.

Or more generally a better local search solution for source code. Powerful enough to find what I need without resorting to regex.
The fact that this parent comment is clearly up-voted and this comment is "greyed out" is emblematic of what I personally think is wrong with HN commenting. The above comment is not helpful, productive, and is unnecessarily negative in tone. The below comment is unhelpful, unproductive, and playful and (if anything) positive in tone. We can't have playful comments but we can have useless negative comments?
This is a huge pet peeve of mine. Ideally, technical articles written online would include the versions of software they write about.

When referring to webapps or other software with difficult to find version numbers, a prominent date at the top of the page is a workable substitute.

Things written online can easily outlast what they were written about. Think of your future readers, and provide some context to your writing.
yaml was awful to work with? can you provide explanation
Hands on with the Surface 3: It’s not an iPad killer
I agree with this. Standups for our team don't replace regular communication, but they do help to focus on what's important: knocking off tasks.

There's the implicit motivation in saying "I got this done!" for the first part, even if it is a review. There's an opportunity to prompt offline discussions when you talk about what you're going to address today.

With regards to "blockers should have been brought up already", of course they should have! The standup, however, is the opportunity to make everyone aware, not just those involved in the blocking issue. Perhaps someone was going to pick tasks today which would have hit that blocker, and can change their plans. Or perhaps someone in another discipline has a solution they now know to bring to you after the meeting.

Summaries are really important, in acedemic papers, technical writing, forum posts (TL;DR), and daily life. Explain to someone what you're about to tell them. Tell them. Explain to them what you just told them.

Sure, I saw you walk up to the board 5 times yesterday, but I was too busy doing my own work to understand the implications. Sure, I know what's still on the burn down list, but are we thinking about taking the same tasks? Glad I now understand that the database problems prevent us from picking up one of the ten widget tasks on the burndown list.
And tomekw added various others to the ... contributers list, or whatever, so pull requests are accepted in a timely manner. (I'm on that list and occasionally do the deed, though new PRs don't come in as often anymore.)
Here's something I need -- a `tar` command for Windows that stores Windows-specific acl entries (dacl I think they call them?). As for the tar format that would hold this -- take a look at PAX format tar files, and how the Red Hat patches to GNU tar store Linux acl and selinux entries.

If you need a jumpstart on how the various tar file formats work, let me know and I'll do a good write up on it (I had to learn all this when I created my backup system).
i would say json is better because it is natively supported by browsers. assuming yaml was as well, would it come out a winner?
It'll be interesting to see the exact code flaw (the bug appears to be private at the moment). I'd imagine things like this are just the result of one wrong if or a variable set at the wrong time.
In the past we've documented interpersonal issues in the performance review and developed goals around fixing any glaring issues. But coworkers are also expected to be professional and raise issues that are actually affecting team effectiveness, and not just complain about a person because they are not fun or personable.
This is actually harder than it seems.

Are you familiar with The Dark Mail Technical Alliance?

https://darkmail.info/
The anti-immigration sentiment often seen in the US (sometimes even on HN), and in a lot of European countries seems to say otherwise.
>What if Linus made the Linux master repository world-writable?

Goodbye Linux.
Looks great!

On a side note, your web design made me smile. Subtly reminds me of the old Trapper Keeper designs of the 90s: http://i.imgur.com/dGF57ff.jpg
Your view is one of the worst types of conservative inhumanity and I honestly am repulsed by it.
Extensive discussion 5 months ago:

https://news.ycombinator.com/item?id=8561080
A lot of workplaces don't work like that! I know my small non-profit can't go buying appliances, but we recently went in as a team on a sodastream and it would have been great to have a system to track it more than someone putting the cash up front.
Coinbase CEO: “Something weird is going on”
I can confirm this anecdotally with my father's factory. Even with documented piece rates, documented averages from all employees, and having a very racially and gender positive hiring policy, it became a running issue of having to spend time in court every time someone was fired for cause. Over a 15 year span they were sued 18 times and lost 'none' of them because they were very strict in documenting everything.

While not a the 'major' factor, it was a factor in reducing the size of the company and specializing rather than growing it and working on more generic product lines. by reducing the size of the company they were able to reduce the need to hire and plan for being sued at least once a year by someone in a protected class that decided that they had been discriminated against.

Based on conversations with him and others in similar positions this is not uncommon.
Similarly, I send my resume out as a PDF. If they ask for it in Word format, I know it's going into that kind of system. I may or may not send it in Word format, but it's definitely a mark against them.
This is the real composite output of an IBM CGA card and 4.77MHz 8088 PC
I cannot agree with any of the specific points (1., 2. and 3.) being generalizable enough as arguments against standups. They may be valid notions where the author works. Perhaps this writing was intended rather as tool in office politics than general rumination on the topic?
Perhaps you should read your own link, which says that 'men' is not gender neutral. "By the 18th century, man had come to refer primarily to males; some writers who wished to use the term in the older sense deemed it necessary to spell out their meaning.". The US was founded in the 18th century. So whether you want to use the 18th-century term supported by your own link, or modern usage, "men" is not gender-neutral.

When did I lionize the institution of slavery?

You didn't lionise the institution of slavery, but you were lionising people that made a system that supposedly was all about individual rights but was at the same time supporting slavery.

You don't get to talk about how awesome the Founding Fathers were about the rights of individuals if you get to hand-wave away the multitudes of individuals whom they had no problems putting in chains. I mean, you even specified "absent coercion" about a society with legal industrial-scale slavery!

Edit: to be clearer, the Founding Father's philosophy quite happily allowed for slavery in practice. Perhaps you shouldn't talk of it in such reverent tones - the 'welfare state' you complain of is clearly better at being fair to all individuals, not just the blessed ones that are pre-approved.
This has to be one of my all time favourite IT related stories. Nice find!
Define "dick".
Well we know what they claimed, which is that they were a pregnant woman who was laid off because of outsourcing but mysteriously she was the only one who lost her job. It may not have been a discriminatory firing, but that would be one hell of a coincidence.

We don't know if what she claims is accurate, true, or even if this company exists. Any comments made are in the context of her statements and assuming they are accurate. Obviously, if she is mistaken then consulting with a lawyer would help reveal that. Telling her to investigate a lawsuit is the correct course given the information we have, and I don't feel any need whatsoever to give the employer a benefit of the doubt. If they are in the clear, then that will be revealed if said employee's lawyer states she has no case.
The de-duplication is very handy, but I think the main point of a wedding registry is so you know the thing you're gifting is something the couple will actually get use out of.

If you know the couple well enough to get a meaningful gift that is not on the registry, go for it, but I've been to plenty of weddings where I was not close enough to the couple to know their tastes/needs for something as personal as homegoods. No one wants to embark on their new life as a married couple with a bunch of stuff cluttering their house that they'll never use and just have to drop off at Goodwill (or worse, go through the hassle of returns - how many different stores would the gifts come from with no registry?), and no one wants to buy a present knowing that's what will most likely happen to it.
"Self-starter" is one of many good qualities for a developer. Here are some others off the top of my head:

* Creative
* Detail-oriented
* Outside-the-box-thinker
* Insightful
* Meticulous

.. and so on. I've found that with any such list, people will already excel in some, and still be growing in the others. Oftentimes these attributes are contrary to each other -- your most creative developer is probably not your most detail-oriented developer, for instance.

If you restrict your hires to all excel in a single attribute, such as "self-starter", you may be missing out on some fantastic developers who excel in other things.

In short, some of your developers may very well find daily accountability to be helpful, and this doesn't necessarily mean they aren't fantastic developers in other ways.
Childcare offered at Brooklyn coworking space
Though they say, "No SID, no problem", and it is better than anything I can recall ever hearing from a PC without a sound card, I will note that the music in this is a far cry from the SID. But, the graphics are pretty much unbelievable.
Plans like this sound cool, but I think it would be helpful to make a visualization so people could see how the payouts change for different exits, thresholds and % redistributed. Visualizations are an easy way to reduce uncertainty so people understand what they're buying into.
I have mixed feelings about that article.

To get anything done, I feel like the general programmer[1] is allowed to assume, at a bare minimum, a Proleptic Gregorian calendar. Anything else just makes handling early (pre-Gregorian) dates madness. (Various geographical locations adopted the calendar at different times, so you end up needing to know where you are to compute the "local" date. Even further back in history the rules get even more odd, and unknown. [2], if I read it correctly, includes a table of when scholars _think_ people inserted leap years.)

Once you go with "Proleptic Gregorian calendar", I think points such as

> Months have either 28, 29, 30, or 31 days.

…are actually always true. Of course, two bullets down is,

> There is only one calendar system in use at one time.

Which is essentially what we're using as axiom here. It's true because we've defined it as such. (Cheating, I admit, but if you're building the next great mobile app, do you care?)

I do wish that site included fold-out sections to de-mystify some of the points.

> Non leap years will never contain a leap day.

Your definition of leap year isn't "year with a leap day"?

> Unix time is the number of seconds since Jan 1st 1970.

> Unix time […] is […] defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970, not counting leap seconds.[3]

Again I wish for pop-out explanations, because I'm left to wonder whether POSIX's lack of leap seconds is what the author is hinting at.

I'm bored though, so perhaps I should write a gist showing which of these I believe to hold (and why) and which do not (and why).

[1]: I think anyone breaking this rule would know that their area of interest requires them to break it, and thus know that they need attention.

[2]: https://en.wikipedia.org/wiki/Julian_calendar#Leap_year_erro...

[3]: https://en.wikipedia.org/wiki/Unix_time
A couple of reasons might be: Motivation, and political power.

"Motivation" is the idea that certain factors motivate people to compete harder in the workplace. One of those factors is having kids. A colleague of mine was dissatisfied with his advancement, and I suggested that he should become a project manager. His response: "Why should I take that horrible job when my engineer job lets me go home at 5 every day?" He had no kids, but lots of social activities.

An amusing story about motivation at my workplace, a Fortune 500 company, is that our management jobs tend to be pretty thankless, even if they pay more. Everybody I've known who has applied for those jobs, has kids.

I've read that after the birth of their first kid, there's a 50% chance that a worker will change jobs in pursuit of higher pay. I also read about a study of unskilled, single women living in the south side of Chicago. Those with kids tended to earn higher wages, and traveled further to their jobs, than those without.

It may be that the choice is not so much children versus art, but career versus art.

Providing family benefits might be one way to effectively pay people more without creating an overt caste system where all of the higher level jobs are held by people with kids.

Political power relates to motivation. From what I've read, people with kids tend to vote. Unsurprisingly, we vote our interests. And there are certain interests that can only be met, within our system, by influencing employers.
The 500-mile email (2002)
That was 755 days ago. Bitcoin updates are handled much more carefully since then.
"Sydney’s mother, Jennifer Smoot, said she helped her daughter with the speech but the 9-year-old wrote most of it."

...yeah, I'm sure. The words fit a 9-year old, but the whinging is pure helicopter mom.
I mainly resent standups because most employers I've ever had scheduled them at 9am, and I'm not really ready to talk to other humans yet at that hour.
a lesson for the author xor the reader.
Border Village, a roadhouse on the other side of the WA/SA border, also observes Central Western Time Zone. However, the next stop on the Eyre Highway does not.
I've been on three different teams in my career and each had different needs in terms of daily stand ups.

team 1)
At my first job I had a manager who spent his entire day putting out fires. I would sometimes go weeks without speaking to him. During that time, I would run out of work, be waiting on meetings he was supposed to arrange, work on the exact same piece of work as another programmer, fall asleep in my chair, etc. That team desperately needed a 5 minute meeting in the morning just so I could touch base with him and let him know what I needed and stay on task.

team 2)
My second job was at a large company. Stand ups were regularly derailed by one or two people droning on about trivial details. The room had white noise generators which made it impossible to hear soft-spoken introverts (almost all of us). Management used it as a platform to inform us how to properly fill in time sheets and that was probably the most useful information anyone ever gained out of those meetings.

team 3)
My current team is small with several remote employees. We communicate regularly through various channels on Slack. We recently decided to sync up once a week, and that seems to work well. Daily stand ups have been considered, but it really feels like a solution seeking a problem.

I'm personally not a fan of the daily stand up. Team 1 needed them, but only because the manager wouldn't take 5 minutes away from his insane excel macros to check up on the team. While the meetings did nothing for me on team 2, I do think they were helpful for management. Team 3 has no need for a lot of the same reasons outlined in this blog post.
I have a personal distaste for the whole standardised testing and ranking scheme ever since NAPLAN was introduced in Australia. Every time it comes up im reminded of this: http://informed.s3.amazonaws.com/informed/wp-content/uploads...
"Data privacy is biggest challenge of our time. Your personal data like email is owned by service provider and that data is used for things like ads you don't want."

Not everyone uses Gmail. I use Fastmail for my e-mail, and they neither show me ads nor read my e-mail. (They charge a modest fee for the service instead.) And as far as I know, they don't claim to own my e-mail.

"Imagine UPS, USPS, FedEx etc reading your mails to send you ads and keeping your mails with them? Sound bizarre, right? It is to us."

It is to me too. That's why I've never used Gmail (or other ad-supported web mail providers). And I use Thunderbird to download e-mails to my machine, so my messages don't stay on Fastmail's servers if I don't want them to. (I trust them to not keep copies of my e-mails forever after I delete them, and they have little incentive to do so.)
The Open Data Movement’s Turbulent Teenage Years
Here are a couple things we tried for our scrum teams.

We let them choose the time of the day for the daily stand-up. One team agreed on 11am. Another on 5pm. Some people see this 15 minute stand-up serves as a major interruption. I see it as a way to consolidate some of the tiny interruptions throughout the day into one.

Also teams have individuals of varying experience so we consider the stories to be a team goal. This makes the more experienced individual more willing to help those still learning since they are no longer making a trade-off for their own stories vs somebody else.

Lastly, I've worked on projects from 1-20 people and beyond a certain size, daily meetings are just mandatory or things fall apart. In a previous project, I ran these big daily status meetings and they tended to run long. Everyone hated it so I dropped it for a few days but then the code started breaking due to lack of communications. We decided to split the meeting into smaller groups and they ran quicker and there were less complaints. However we were still able to keep the code quality.

But I think the most important things is "one size doesn't fit all." If something is not working, have an open discussion within the team and suggest some alternatives. If there is no avenue to give feedback, that is the fundamental problem.
That looks much less.. exciting than the trolling that's taking place in OP's repo.
>And, frankly, what's wrong with that?

That it doesn't solve OUR problem, which is "help us chose if Haskell if better", even though it pretends to?
Australians and Brazilians: your bits are upside down. Try flipping them over and then running the tests again.
Three-Strikes Anti-Piracy scheme launched in Australia
Calling Out the High-Tech Hypocrites
Doesn't matter.

When the top guy leaves, that signals to the rank and file it's OK to leave. It tends to look bad when the rank and file leave before the boss. It's an extremely well understood social signal (whether you buy into that or not, doesn't matter. It's the signal).

So there is a strong understanding of this in aware managers - they will leave in the 4:30-5:30 bracket, so their employees don't feel compelled to work long hours.
There is a lot of open data: http://transitfeeds.com

(Disclaimer: it's my site)
> What is an employer to do? Never fire anyone in a protected class?

FWIW, in Brazil it's illegal for an employer to fire a pregnant woman.
As a dev living in one of those half-hour offsets (ACST +9.5 Adelaide, South Australia) i think the only thing it's changed is our awareness of timezone issues, although there's discussion about moving us into AEST or back to AWST which … well … will be painful
Did you miss the "not" in "not running on a VM"?
Agree with everything you've said, but keep in mind non-Proleptic can still be found. Java splits on 15 Oct 1582 by default:

https://docs.oracle.com/javase/7/docs/api/java/util/Gregoria...
It is not completely true. See for instance what PNaCl is doing: you can compile C++ (or any similar compiled language) to (LLVM) byte code, and then JIT it at runtime.
No. but, I'll read about it.
I don't agree with this. People who aren't motivated or didn't do anything just make things up. One day I helped another developer fix a simple bug. By help, I mean I sat on his computer and fixed it while he watched. It took me ~20 seconds. He then talked about how he fixed the bug in detail for a minute and a half the next day. Apparently that was all "he" accomplished. Everyone (myself included) stood silently and nodded our heads.
> but what's stopping you from going out at 6:30 instead?

It's not about going out, it's just nice still having a few hours of daylight in the early evenings after I've finished work.
I agree. I am just providing a charitable reading of the quote, assuming that the phrasing of the general point was poor.
That sounds egregious. Is there any way of substantiating this? Or online photos of the readers?
Well that makes sense in the real-world; Broken Hill gets South Australian television and radio and is much closer to Adelaide than Sydney (500km to 1200km), it makes sense to be on ACST not AEST
you accept anything and end up being nothing.. lol
There are plenty of talented, productive people who aren't self-starters. Your company will be missing out on them. You can easily say they're the wrong people, but you could also say you're the wrong leader.

Rant: Not everyone is an isolation-loving codemonkey. Some people need the feelings of team involvement, urgency and repercussions. If I'm just left to sit in the corner all day, and no one knows what I'm doing, and no one gives a shit if I do nothing... guess what? I'm going to end up doing nothing. Perhaps people like me are flawed, but we're still very talented and capable -- and not every company can afford to pass over the extroverted developers.
Thanks greenyoda,

Great to know that there are users who see value in it.

If I may ask, what is something more that you wish from the service provider you already use?

appreciate your comment,
also fades curtains
My current team does the daily standup and we discuss only "what's changed" (no changes - move along). It takes 15-20 minutes usually and I find them very useful: they bring everybody on the same page, help spotting issues earlier, prompt for deeper discussions after the standup.
I don't think its any more wrong to fully devote yourself to a job that is the important thing you want to do with your life than it is to have a job that exists to enable other important things you do outside of the job.
Unlocking the secrets of a successful marriage. Key 1: his needs