skysight-inc/HackerNews huggingface dataset:
In Canada, representing yourself as an "Engineer" is like representing yourself as a "Doctor". There's a professional organization that gets to say who is and is not a member. That includes "software engineer" (it does not include train engineers, btw). There are, I think, a number of legal privileges and responsibilities that come with that. I dunno, I'm not an engineer.

This has almost nothing to do with "software engineering" in practice, except that in Canada we generally call the people who write software "developers" (or "coders" or "programmers"). If a given company calls their developers "engineers", it's code for "we're an American company (and we don't respect the law (until APEG sues us))".
> That's amusing, that you want solid evidence, yet you're willing to use your own anecdotes.

I'm not the one presenting my anecdotes as fact: "The fact is that, on average, design doc+code takes less time than code without design".

Anyway, you've very clearly articulated the conventional wisdom of big companies originating in a certain era of computing. Conventional wisdom isn't necessarily wrong, but it's not necessarily right for all time either. There are companies with data needs, user counts, and codebase sizes on par with Google that don't practice Google-style process, yet succeed anyway. That these companies have succeeded without Google's process is evidence that Google's process is unnecessary, at least in today's environment.

> SQL injection and XSS vulnerabilities for example

Code-level concerns. You're not going to stop SQL injection by looking at some high-level design document. The same goes for r2l text layout bugs.

> it's worth taking six months adding a checkbox to take every possible step possible to ensure that doesn't leak a security vulnerability somewhere.

Keep that in mind when smaller competitors surpass you. It's easy to say that Google's codebase represents 18 years of work. I strongly suspect that it wouldn't take so long to do starting today.

Look at self-driving cars: how long has Google been working on them? How long has Uber? Whose cars are serving real-world passengers today?

These days, we have 1) very good continuous integration systems, 2) good code review tools, 3) fast shipping vehicles, and 4) continually improving static analysis. These things were unavailable (at least at adequate quality levels) when Google started its design culture.

Maybe the conventional wisdom you articulate might have been an optimum some time ago. These days, I think it's far too process-heavy and that Google and similar companies haven't kept up with the times.

> Just because your individual progress is slow, doesn't mean that the progress of the team is slow

It means that the team is inefficient. Communication overhead goes as N^2, after all. Google's teams are notoriously huge. When you see that a startup (or even another > $1 billion company) can do the same damn thing Google does and put a quarter of the people on the task, maybe it's time to wonder whether Google is doing something wrong.

If developers feel like process is slowing them down, maybe you should listen to them.

> One breaking change in say Google adwords can undo literally man years of work.

It's easy to look at a few failures and conclude that you need to add process to fix whatever went wrong. It takes much more foresight and wisdom to see that this process probably costs more man years in overhead and inflexibility than you spend fixing the occasional mistake.
Exploratory Data Analysis Using R (Part-I)
Full Text Search with MongoDB
I commute to work 15km each way on an e-bike and I do almost all of it on bike paths away from cars. It's a very pleasant way to commute. I don't need to use any special "bike roads" - the existing bike path infrastructure in Melbourne (Australia) works for me.
Every discussion forum these days feels like walking into a classroom of second graders talking about things they have heard grad students talk about.
What sort of people provide the CSVs?

I myself have had to integrate with 3rd party logistics companies, and the way we got them to send out our inventory was to send them a CSV of our orders twice a day.
I thought this had been around forever?
(I mean some form of installer and deployment kit/admin tool)

I see other pages talking about it going back to 2010/2011
Best Augmented Reality Apps and Games You Should Try Now
I think you are seeing the effect of people who have decided for themselves to pursue lifelong learning. The Udacity/Coursera thing just clusters these people in a way that you notice them in the stats. But remember that statistics do lie. You need to dig into the reality behind the numbers, and question whether you are measuring all the right indicators.

My experience comes from several decades developing software and from time to time, hiring people. The people that worked out best, either as colleagues or hires, always seemed to be learning new things and were ahead of the curve trying out new techniques or tools before they became popular.

If you understand how a tool/technique becomes popular as the mass of software developers wrestle with new problems and finally find a way to master them, then it makes sense that constant learning makes some people stand out of the crowd. They happen to be the first ones to learn the new tool/technique and if they do not introduce it to their development team, then when management does make the decision to introduce it, the folks who know how to drive it have a chance to excel and appear to be rocket scientists.
2010 added support for Ribbon customization. I wouldn't say it changed the behavior dramatically though.
50 Innovative Wearable Products from Kickstarter and Indiegogo Campaigns
Funnier visualization: https://www.youtube.com/watch?v=w5DHU8SwYJ0
It seems kind of obvious that Nintendo would have Official Game Asset Graph Paper, but it's pretty cool to actually see it.
It's a bad analogy. Because it encourages locking up knowledge forever and results in harming progress. Taxes are a poor compensation for this damage. The whole point of copyright is "to promote the progress of science and useful arts". Extending it does exactly the opposite.
What a ridiculous headline. The Washington Post should be ashamed of themselves: Americans — especially but not exclusively Trump voters — believe crazy, wrong things

The article is clearly selecting statistics that would make Trump-voters look worse overall, only including one where Clinton-voters are more likely to believe the falsehood (that Russia likely hacked the actual election).

Just to name a few, I suspect the Clinton voters are more likely to believe these falsehoods: that women make 70-some cents on the dollar for equal work, that nuclear power cannot be safe, that police disproportionately use lethal force against black Americans.
You live in the wrong country.
Man, brings me back to my childhood. It's still disappointing to me that there hasn't been a game in the x wing/tie fighter mold - for me it would be a killer app for vr.
Nobody would believe any of this crap if it weren't for the media. The American media sucks and has 100% caused this issue. The problem isn't just "fake news" in the sense that people can share whatever "news" they want on Facebook. The problem is that we're told to trust the news when they're equally guilty of sharing fake information -- obviously, a lot of the things Trump voters believe in have been reported by Fox. Many of the things Clinton voters believe in have been reported by CNN. While fake news is certainly cropping up on Facebook, the root of the problem is the fact that none of these sources are really that much less trustworthy than the "real media".

Anyways, it's the news that created the two-sidedness of the current political atmosphere, which is what led to the whole problem of conservative/liberal echochambers (that allow for fake news to spread so rapidly).

All these articles seem to say, "look what everybody else believes because of things other people said." It would be far more interesting to see an article about, "look what all our readers believe because of things we've said."
> Forget ML, if you can't hardcode if-else, just use rules engine. What do you think?

Load data in X, model.fit(X, y), predictions = model.predict(new_X). It's not more complicated to apply ML.
The Robotic Grocery Store of the Future Is Here
ISLR was written after ESL to be an easier to read version. I guarantee you will have trouble if you try to teach yourself ML with ESL.
It’s Time for the Nobel Committee to Honor Climate Research
Oh, so like information from data.gov or other public data to verify people. That makes sense.

I'm guessing small businesses want to do integration with the web, but they didn't really have the engineers to do an API integration?
"Will Office be open source in future?"

"Yes. I give you my Word."
> break the testing infrastructure for practically every other developer in the building

Why wouldn't continuous integration have caught that bug? If a diff breaks the build, it shouldn't land. If a diff causes tests to fail, it shouldn't land. If a diff lands anyway and causes problems, any developer negatively affected should be able to insta-revert the diff.

How does a design document help?
It's a signal. It's not a binary yes/no, there are many observations we're making throughout the interview. This is just one, and the to-do list isn't the only correct answer. Asking me to email those details to them is another possible right answer. Writing a note in a notebook is fine.

The key thing to remember here is that we're asking this very much in the middle of the interview, and I just want to see that they have some sort of system in place for remembering these things.

In my experience, most of the time, simply going "sure, I'll do that" and depending on memory to actually get it done is a negative signal. Maybe they are particularly gifted in terms of memory, but in my experience that is rarely the case.

In hiring we're willing to accept false-negatives, but never false-positives. You are correct, I may let a perfectly good candidate walk, but I'm willing to accept that as the cost of hiring a bad one is just too high.
Hey I really need some help I am in a similar situation and was wondering if I can get some advice on getting a job. I just have questions regarding what to put on my portfolio page like you did, and also what was the interview like? What sort of questions did they ask.
Agree.

For people who are not familiar with TCP and UDP, the answer should be to ALWAYS use TCP.

The only exception is some subset of games (FPS, RTS), that this article is exclusively intended for.

Even there, for the average user who just wanna make a test game project, TCP may be easier to use and program around. For simple games (e.g. Connect 4), TCP is a better option either way.
Thinner phones wasn't the only reason to remove the headphone jack. It was also preventing the phone from being fully waterproof.
What are some alternative protocols?

It's been a while since my networking class, but if I remember correctly with UDP you have some serious issues where you can end up clobbering your network, filling up buffers in the middle and dropping tons of packets. The lack of congestion control is a huge no-no.

For instance in the example he gives, sure you can tolerate dropped packets for player-position data, but how do you know if you can tolerate sending at 10Hz 100Hz 1000Hz? Even with TCP you can't (I think....) programmatically adapt to the size of your pipe. That's kinda abstracted away for you so that you just say "send file A to B" and it does it for you

Are you supposed to write your own congestion control in userland???? Seems like this should be a solved problem
thanks -- do you know what graphics card that is? also you can try enabling "Override software rendering list" in chrome://flags/ -- I don't have a great handle on what gpus are blacklisted, but I know there are some that are.

putting this in the address bar can give you a lot of info as well "chrome://gpu"
Your example issues from the other side are not crazy. They are in the the domain of reasonable political discourse, unlike pizzagate and the birther stuff.
QUIC seems like it'd be kind of neat for videogame networking. Does anyone know whether one can get a QUIC channel to deliver datagram-style, as in unreliable and no retransmitting? It'd be really cool if you could set up one QUIC connection that could work across IP address changes and then use it for N reliable TCP-like streams and M datagram-style game update packet channels. If you could set up that sort of thing from JavaScript in a web browser, that'd be straight up amazing.
I think the pathologies you mention are inevitable once it becomes acceptable to address technical problems by adding process like mandatory design document signoff. The only way to avoid these pathologies is to take a hard stand against process.
Definitely my favourite! :)

http://141.84.11.4/view/viewer_index.shtml?id=1362

And this link lets you change the "feed profile"
Could it be that this is not marijuana but the chemicals used to grow it? Certanly sounds like it
Notes on Musical Notation
The biggest problem with taxing copyright is how to value it, which ranges from wildly arbitrary to completely impossible.

The most rational way would be to tax licensing revenue, but that makes it a non-solution to your problem because if nobody knows who to license the copyright from then nobody is licensing it and there is no revenue to tax.

It also seems rather unlikely that if you can't stop a completely irrational copyright term extension, you could nonetheless bring about a copyright tax on the same people. You're more likely to be able to prevent further copyright term extensions.

And there is a well known solution to the orphan works problem, which is to require copyright registration after some period (e.g. after every 14 years).
> 99% of them are idiots and have no business being programmers

I feel the same way. If you have a group of idiots, you need process as a harm reduction measure. A very high contributor bar is a prerequisite for a process-light environment, because if you can't trust people to do the right thing, you need a system to force them into a conservative approximation of the right thing, and this system is called process.
If you don't check for returns, TCP isn't going to help either.

The requirements you listed don't make sense as written. Nobody would ever use UDP.
Clarius Mobile Health Is Reshaping a $6B Healthcare Market
Glenn _Fiedler_ - Gaffer is his online name / handle.

Worked with Glenn on Freedom Force and Tribes. He knows his stuff!
> moved to xml

No people still use the obviously superior format for structured tabulary data. Why would anyone use something that is highly suboptimal for things like these?
A robust flow control that's tuned for bulk downloads, and badly adapted for small real-time streams.
Eve Valkyrie?
This is awesome ! Would love to see a doc for detailed audit logging when you have one up.

This in itself is a killer app !

EDIT: one more request, please make you docs/makefile a little more beginner friendly. For example, your get-started page (or your makefile target) does not have systemd targets in place. I think you guys take care of necessary selinux permissions inside code.. but not sure if it does so for /var/lib/teleport.
it might be useful to consider using ansible (which will make this very practical for devops)
"I'm inclined to think that if you're using `cadadar` you're probably doing something wrong."

That's nice. I'm inclined to think that you haven't written very much Lisp code.
http://www.rasmussenreports.com/public_content/politics/curr...

>Democrats in America are evenly divided on the question of whether George W. Bush knew about the 9/11 terrorist attacks in advance. Thirty-five percent (35%) of Democrats believe he did know, 39% say he did not know, and 26% are not sure. Republicans reject that view and, by a 7-to-1 margin, say the President did not know in advance about the attacks.
I used to think along these lines. Then I started doing 10+ interviews a month and realized a very clear reality: basic CS knowledge and problem skills is far more important to me and my team then knowing how to slap together some semblance of a working CRUD system.

I ask "algorithmic" questions, normally expressed as a legitimate business case (invent a real world problem, solution is implement some algorithm or use specific data structure). My warm up question typically is a simplistic "find the subset in a given collection that matches this specific criteria" (with a subtle implication of "do it efficiently"). The average coder should be able to solve this type of thing, on their own, in about 10 minutes max, 15 with some feedback on improvements.

Yet, 80% of my candidates take nearly 45 minutes and cannot deliver a workable solution without massive handholding, and I don't even get to my higher order, "real questions". The scenario of a coder who can't solve my warm-up being let loose on code I actively maintain makes my stomach churn.

Until I see the average bar for problem solving go up, I'm going to keep asking basic CS questions in my coding interviews. The job is to solve complex, typically ambiguous problems. Coding is one of the tools - and I want peers who understand the theory behind using those tools.

(I should note, I tend not to pay attention to credentials on a resume. I care more about ability to do the job then past history - though if a candidate has a masters in some field of CS, I might delve into it a bit out of curiosity... they are an expert afterall)
> I doubt your subseq works on strings (or bytestrings)

Actually, it does.
There's a big difference between the economic topics that get the most media attention, and areas in which the majority of economists work.

I studied economics for 4 years and now work as an economist. I've never met a colleague/teacher who claimed to be able to forecast inflation/GDP growth over the next four quarters or correctly identify miss-priced assets.

Some examples of the questions I have seen economists address:

- How much might labour supply change following a change in tax policy?

- What is the impact of online advertising through different channels on a company's incremental sales?

- How would a merger between two companies affect the price and quality of their output?

- How can you detect collusion between bidders in tender markets?

A lot of the work seemed convincing to me, and lead to insights beyond the common sense intuition of politicians/businessmen who were familiar with the domain.

Even if you think economists aren't helpful for predicting inflation/GDP growth or identifying miss-priced assets (I'm inclined to agree), there are lots of important questions about market dynamics and policy evaluation where economics does give us genuine insight. I also find it really fun!
That just seems like it makes it easier! You predict a recession, you're wrong, but you end up being right anyway!
This certainly isn't a problem unique to Trump voters. Many of my like minded liberal friends are starting to indulge in fantasy these days too. It's gotten much worse in the last couple of years. Some of the stuff that comes out of their mouths is just so absurd that I don't even know how to respond to it. It's really awkward when they quote numbers or stats that can't possibly be true and simply don't make any sense. If you want to challenge them on it you basically have to call them stupid. It's probably true but it's not a very polite thing to say to someone.
Explain to me what you think the key differences are between a competent and incompetent programmer; specifically, in terms of particular skillsets.
Agreed. Regardless of your opinions about the election/politics, it's quite clear that people on both sides hold the same kinds of false/ridiculous beliefs. Just the other night at a restaurant I had the pleasure of overhearing the conversation from a table next to mine. This group of people was discussing how "Black people are lazy and would rather sit around and do drugs than get a job." And within the same breath they mentioned how glad they were they voted for Clinton instead of Trump.

I'm sure that with very little work, someone could create statistics showing the reverse effect of this article. The fact that their cherrypicked selection of fake news is all about anti-Clinton things makes it no real surprise that Trump voters agreed with it. If it was anti-Trump, Clinton voters would agree with it. Trying to make any sort of "finding" out of this information is a load of bullshit, but people will eat it up because it confirms their beliefs.
> it makes the population really not give a shit about issues surrounding formal war

Soldiers are between truck drivers and lawyers. More tactile than, and similarly skilled as, most of them. The luxury of the first world is the population's ability to ignore dying soldiers.
NES clones are still going strong in India :) Summers spent playing pirated games on 8-bit cartridges - what joy!

SNES sadly was a rarity, even if it was much better (I'd personally rate SNES higher than Wii). Frankly, if there were nice touch interfaces for SNES emulators, I'd gladly pay $10. Carrying a bluetooth gamepad is definitely an alternative.
Windows doesn't use Reno. It uses Compound TCP, which is somewhat like Vegas.

https://en.m.wikipedia.org/wiki/Compound_TCP
This appears to go far beyond that though. The policy and maintenance pieces in IE/Edge were one of the biggest reasons for some of the larger companies I've worked with that they had for staying off of other browsers. This looks to fix that.
How about FS2Open? Fantastic series of games, even more fantastic engine. Someone should get on VR support, would be a good Elite:Dangerous competitor.
can we get one of these for babies please? or does unky herb still have the patent on that?
So would it have worked better to send the entire game state every frame/every N frames/etc so that a dropped UDP packet would not totally trash the game? I don't know what the maximum frame size is for UDP.
Maybe, but there are plenty of languages I would say are completely independent -- APL, Prolog, and Forth don't seem to resemble Fortran in any major way. At least Lisp shares the same notion of functions=subroutines.
I'm not sure it is appropriate to give a Nobel prize for a hypothesis that has not yet been proven.
> backtracks on a strategy decided 2 years ago

Why should anyone be bound today by decisions made two years ago? Maybe that strategy no longer makes sense.

I've seen it go both ways. On one hand, sometimes a new developer in an old codebase does something "against the grain" of the system due to unfamiliarity or JavaScript-induced brain damage. On the other hand, sometimes circumstances change and even good old designs become obsolete.

A culture of good taste and transmission of institutional knowledge helps preserve the good aspects of design. I don't think design documents help: they're just bytes on a disk. Unless you have people to enforce them, these documents won't do a thing. If you do have people who know what the system is supposed to look like and who shepherd changes to work with the original design, you don't need the design document.
Yes. A DIY home fecal transplant.
> Only 17% of Steam users have an Intel card. Not sure how you came to that conclusion :)

You're using Steam statistics as if they applied, proportionally, to the PC gaming industry when its users are majority PC gaming enthusiasts. This also means Steam makes up a small amount of most gaming company's sales. The majority is still done through big box stores. The statistics are interesting but I'm not sure how useful they are for determining target requirements from most gaming companies.
To anyone trying to work around motorcycle licensing in the US: don't. The Motorcycle Safety Foundation class is one of the most fun things you can do in a couple of weekends, and I highly recommend it. After that, getting the M1 is purely clerical (in California anyway) and reasonably fast.