skysight-inc/HackerNews huggingface dataset:
Heck YEA. Get shit DONE. I've watched projects go in reverse because of process. I've watched people waste 5 hours a day in scrum. It's so corrosive, addictive to the scrum master/leads who benefit from tossing around their opinion, it favors the worst performers, isolates the best.

Handle process in a case-by-case basis. If something needs changing, change it, but move on and GET SHIT DONE. That's the only way to go. I don't care what people say, good programmers don't need to be babysat.
In the picture from the article I see what is basically a lot of swamp around Facebook.

If they were allowed to build let's say 10 20 story buildings there would be no need to evict current renters.
> And Netflix opted to pay instead of battling it at the time.

Netflix didn't just pay. They battled it for a huge amount of time.
Can we?

I'd be in favour of dissolving it back to counties with a senate.

The south never does anything for us up North.
As someone who is heavily invested in building web app MVPs for clients on a budget, I've been considering moving to RoR and away from Laravel if not just for the simple scaffolding Rails would give me. Given you spent time in Django where some things are a little manual just like Laravel, would you recommend me diving deep into Rails given what my business aims to do? Hope you can help!
Why should they? I could ask you to take a 30% pay cut and you rightly would ignore my request, so why should landlords decrease rent?

The solution when market price is out-of-whack is to solve the cause of that, not politely ask suppliers to change their prices or consumers what they are willing to pay.
> If you wanted to exploit this, you would have to guess the port, and it would be forwarded to a machine behind the NAT, which "owns" the open port.

Only iff you have static nat forwarding that port, which is almost never. With dynamic NAT (99.99% of setups) no machine "owns" the port before it sends a packet out, and once it does, it only "owns" it with respect to the IP it sent the packets to.
I dislike social profiles like the next person and would like a better way of verifying...

I just had an idea whilst thinking about how I was going to respond to this -- perhaps I could do e-mail signup but instead verify the user through the clearbit/fullcontact api. Need to look into that
The good thing about Rails is that there's not much to talk about it. It just does what it is suposed to do without any drama.
ICE under the supervision of past administrations has been been dealing with people entering illegally (including prosecution) for more than a decade.

It has never resulted in mass separation of families until now. For example, in 2014, when large waves of immigrants fleeing violence in central America entered the US illegally and were apprehended by ICE, they were detained in family detention centers where children and parents were together.

Your suggestion that the only two choices are support for illegal immigration or support for separating babies and toddlers from families isn't supported by reality.
Isn't it plausible that it's neither race nor class, and people just want their property values to keep climbing? I assume people like it when their property appreciates in value, but maybe that incentive is nullified by increased property taxes?
"The same folks voting for these laws have always hated poor people and immigrant families. "

Reminds me of people in affluent VA and MD suburbs. They are super liberal and for diversity but they will do whatever they can do to not allow anybody that's not well off or different even near their neighborhoods or schools. SV is probably the same.
This documentary opened my eyes to a lot of issues I didn't know existed. A good starting point that led me to read more about this. https://www.imdb.com/title/tt5895028/
Latacora, corpsec perspective: audit Google Groups and OAuth'd apps, run a phishing red-team exercise.

Finding appsec bugs matters but maybe not so much if everyone just signs over whatever privilege apps ask for and it'll exfil whatever's on Drive.
I told him that I was going home and he was fine.
Do you typically choose one over the other?
There is also no tech stack in the world that will get you to rewrite your entire application faster than RoR.
Atul gawande is based there and the Boston area is actually ahead of the Bay Area in terms of biotech startup scene and similar if not better in terms of healthcare services
Folks are getting laid for free via Tinder and others. Why would anyone pay $10/month for a smaller pool of candidates?
French government freezes assets of Hani Ramadan
> Manhattan has the benefit that you can't spread outwards

We overflow into Brooklyn, Queens and New Jersey quite easily. In any case, most of uptown is relatively low density. The density exists because of the demand in a few concentrated areas and because it's permitted.
I have to agree. Our stack is currently Node.js. After all the abstractions that we've added to make it work for us, it's basically Django now. We could have saved a lot of time just going with Django first. (Or Rails if that's your flavor)
"...but The Wealth of Nations by Adam Smith states that all country will have certain expertise they are just good at."

Weird that Porter doesn't cite Smith.
Yep. It's quite clear that there are forces trying to affect EU in the hope of breaking it up, mostly to further a right-wing agenda of some sort, but also to simply destabilise it to decrease it's influence.

For democracy as an ideology to work well, there might be a modicum of honesty necessary from it's actors, in that they try to enact only policy they actually believe in, and not aim to simply cause destruction and dissent. This is clearly nothing that is entirely unique to one ideology, as the past few years has clearly shown.

It's unfortunate that the very stability that many seek seems to be the very thing that cause them, or others to cause instability. Maybe we as a species thrive on danger, and whenever it seems to disappear we invent some new imaginary spectre to take the place of those we erased. Like how vaccinations that have prevented untold amounts of suffering, now far to many people seem to consider it the cause of any ailments short of broken legs.
As a Rails dev, I personally prefer "matured" vs "declining" – and to be fair, "mature" it's also one of those words that management would like to see associated with our choice of technology stack, too.

Some things get better with age. There's an advantage too, not being on the brand-spanking latest version of something – you get to let everyone else filter out the crap before it winds up in your production environments.

A few examples from recent Rails releases,

(1) Turbolinks is one thing that was widely regarded as absolute crap when it was released, but now I think it's a pretty non-controversial way for Rails developers to give their users a single-page experience without necessarily diving headfirst into JavaScript.

(2) If you rebuilt all of your Rails 5 apps to use the shiny new Encrypted Secrets in 5.1, ... surprise! 5.2 deprecates secrets in favor of the newer Encrypted Credentials feature.

I'm not saying there aren't good ideas in newer frameworks, but how many mature frameworks are still in active development? (Make a list) ... and how many of those would you actually like to use?

Though they may be more popular, I'm personally not seeing lots of people rallying behind Java and .NET, or making outrageous claims like that those platforms prioritize developer happiness. Rails developers like using rails.
Wondershare PDFelement Pro 6.7.1.3424 Full Crack
> a bit of paperwork

I suspect this is the difference. If this company is incapable of not firing someone, I imagine their appeals process could be equally miserable. Sure, maybe the manager and director want to repay him, but actually releasing funds to pay someone who "wasn't employed" is going involve a lengthy battle with some HR/Accounting computer system that just wants its invariants not to vary. Depending on somebody's financial position, I can see them deciding to just walk away on even a large chunk of money to avoid the mess.
Excuses my ignorance. I don't understand how we could do 99% or even 100% with "pages", but instead we still insist on "apps".
Yes there is: any JS stack.
Git itself was a bit of a red herring, even though it was somewhat relevant to that specific point. I know nothing about what hosting platform the author is currently using, so to make a quick assumption:

- hosting on AWS is not free for super high traffic (assuming the free tier can't keep up)
- serving files from S3 is not free (though it's cheap enough at low read levels, it adds up)

At a typical level of traffic, the author's current host may be sufficiently inexpensive. Assuming the author was assuming many, many times the usual traffic (even if everyone is kind enough to bare clone), it would be a pointless expense.

Of course, third party hosting can take the content down... and this is where git became relevant. Assuming the author was more interested in distributing the content than the prestige of being the distributor, even though Github etc. took down the repo, every person who has since cloned is now capable of re-publishing to any new upstream repository of their choosing, on any server.

Assuming, again, that all of this was the goal, it probably made sense to utilize the free, fast, scalable third party hosting as long as possible rather than risk self-hosting slowing down or collapsing under traffic, or creating a massive spike in cost.

That's a whole boat load of assumptions, any of which could be wrong. In the realm of possible motivations, though, I think it's a fairly logical conclusion.
I think that, it's not money per se, but as you say the number of people between the developer and the decision maker. The only person who perceives the problem of having too much code, is the developer (and then only sometimes). Organizations do well at optimizing what they track, in many cases, but they don't track amount of existing code as a negative thing that needs maintaining, so they don't do well at optimizing that.
> Net neutrality regulations were not created in the US until 2014. It is ignorant to think these stopped companies before 2014.

Such regulations were in place before that. Companies started questioning the authority which resulted in new laws needing to be made.

Saying the law is recent, unneeded, etc has been mentioned and refuted many times in previous discussions.
Actually no, it's counting the number of links with href="javascript:void(0)" (from a rough look at the page source).
Except you always have a say in whether or not Google takes any part of your site. Google have always respected robots.txt and it's trivial to block your site, or parts of it, from being indexed and shown in searches.
You are right. This bill is a disaster for smaller platforms.

My company [0] built business around Content ID-like technology, so we should be celebrating, but we don't. We are going to announce, that our services will be provided to all impacted platforms free of charge. We are hoping to facilitate licensing deal between rights holders and the platforms, preferably on pay-per-play basis, instead of completely blocking content from being uploaded to the platforms.

It still is not a great outcome, but at least it will not put smaller platforms out of business, and hopefully not completely stiff the innovation.

[0] https://pex.com
That's too generous. Even the things that work properly on every browser are usually hacks because HTML and CSS were made for documents rather than applications.
Yeah, until the very moment Canada elects a right-populist/neo-fascist government. We all know what Trump and his administration are up to.
I think Google would win that game of chicken.
Cool project, and excellent documentation. This is a truly rare combination in the security community! Nice work.
I guess I'll be the guy to remind everyone that Ruby != Rails. (I'm a Ruby dev and mostly do not touch Rails at all professionally)

$ grep -i 'ruby' hn.txt | wc -l 25

$ grep -i 'ruby' hn.txt | grep -v 'rails' | wc -l 22
This is how we'll reach the singularity. Computers won't be outsmarting us, but we'll gladly stoop to their level of throwing all judgement out the window and treating our fellow men like scum just because a program tells us to.
This is a separate debate, but id argue that consolidation, not fragmentation, is the current primary flaw in the system

It's a zero sum consolidation arms race between payers and providers with patients and physicians as pawns
Private Internet Access open sources iOS VPN app
In certain states the THC/CBD level must be posted on the packaging, but what is a safe level? It will take years to figure that out.
There’s a pretty long standing industry in California for medical, and with the recent state legalization, recreational sales. More people and more affluence.
No one might be entitled to that, but it's definitely helpful to the social health of an area if there is policy to ensure that the community stays somewhat stable.
IMO every programming language should have a web templating tool for code to documentation generation.
As I read the piece, it was a three year contract which was included in the old HR system, but not ported to the new one. If that's true, it was certainly breach of contract - "we forgot to upload the paperwork" doesn't get you out of honoring it.
> We know that some weed smokers end up schizophrenic and that in general smoking weed weakens one's will, so in many cases we end up with grown up children going only after the things attainable by easiest efforts.

I'm concerned about things like this too, but ultimately the only way forward is to let some societies experiment with it and face the consequences. I hope it doesn't become a global UN thing.
Unfortunately, such a flag would probably result in weird package install/update errors as part of the dependency graph would be missing.
Lol. Use a Java backend, that's performant and solid so it can scale beyond a million subscribers easily and write the Frontend in a framework like Angular/React/Vuejs and I see no reason why I would want a Rails app instead.
In case anyone wonders what a flanery is: https://cs.uwaterloo.ca/~plragde/flaneries/
This is exactly the same logic I heard used by many people voting for Trump. The truth is that there usually is a real downside from failure, even if it feels like our huge systems are as bad as they can get. In other words, while we do have an expensive system with worse outcomes than peer nations, at least right now we have healthcare being delivered at a first-world level, and we shouldn't take that for granted.
I am just wondering if there are any pitfalls. While not many are writing about their technical failure of React Native or whatever tech it is. You will at least know they have changed the stack, or words on the street / twitter they are retrying new things because old things didn't work etc.

But TurboLinks 5? None, not even a mention or beep. As if no one is using it. While we are happily using it someone else may be running into issues we haven't yet doubt with.

It is pretty much like Startup news, I don't want to read about how you succeed this just once. I want to read about your thousands other failure, what works, what not, and what you ( Or I could ) learned from it. By stating your problem, your intended solution, and the results I could make a better informed decision somewhere down the line. And all the time we got on the internet is everyone cheer leading mindlessly.
This is the thing that everyone seems to have forgotten. Redux didn't invent these terms out of nothing. Redux was specifically written as an implementation of the Flux Architecture, and the terms "store", "action", and "type" came directly from Flux. The term "reducer" had been in use with Clojure already, I think, and is based on the way these functions have the same signature as a callback you pass to `Array.prototype.reduce`. "State" is a generic term meaning "data in your app", and the term "tree" for a hierarchy of objects has been around for ever. (Oh, and you can write your reducer functions with _whatever conditional logic you want_ - switch statements just happen to be an obvious way to handle multiple values for a single field.)

I covered a lot of the history and thought behind Redux's design in my post "The Tao of Redux, Part 1: Implementation and Intent" [0] .

Sure, I'd agree that the terms are a lot to take in for a new learner, but claiming these were chosen or made up to make things more confusing is ridiculous. There was a lot of debate over exactly what terms to use during the development process [1] [2] [3], and it was ultimately decided that keeping the Flux-based terminology made the most sense at the time, because most people coming to Redux were familiar with Flux already. Obviously the dev landscape has changed since then, since nobody seems to remember that the original Flux concept existed, but the terms are now set in stone because we've been using them since the beginning.

[0] https://blog.isquaredsoftware.com/2017/05/idiomatic-redux-ta...

[1] "reducers": https://github.com/reduxjs/redux/issues/137

[2] "state", "store", "dispatch" : https://github.com/reduxjs/redux/issues/113 , https://github.com/reduxjs/redux/issues/137

[3] "actions" vs "events": https://github.com/reduxjs/redux/issues/384 , https://github.com/reduxjs/redux/issues/377 , https://github.com/reduxjs/redux/issues/891
There is a difference. Spring boot is not opinionated about how to do templates, persistance and DB migrations.

This means you have to go away and do some research to get your stack running.

This was enough to put me off.
I've read most of Atul Gawande's books about the medical industry (Better, Complications, and The Checklist Manifesto) and I found the three of them extremely relevant to my career as a computer scientist. The latter book is by far his most famous, but IMHO the other two are much better.

This is a bold choice by Amazon, but it seems like a good idea even if it's just for name recognition.
True, but those edge cases have to convince a court made up of humans, who will probably have similar feelings. That might be a decent check on abuses.
> No, we do not NEED Net Neutrality. The internet can/has/will survived for the short ~2ish years of really weak NN

Net neutrality was in place much longer than this. Furthermore, there were put in place because companies continuously started to abuse them.

> need to lower the barrier of entry into the market for new ISPs, not raise it

That has nothing to do with net neutrality. Treating everything pretty much the same is way easier than building complicated billing systems.
I dont have much experience, but with react native, you only need to build 1 app for iphone and android, then potentially use react for web.

Is there any competition here? I could be unfamiliar with other solutions, but I thought the purpose of using JS was to eliminate re-writing code in multiple front end languages.
Same here, and I feel more and more excited about the framework. The recent official support of Webpack was a huge addition.
Yes. It was impossible because it was always single sites doing it, and that doesn't work. To prevent that scenario, this law is for all news sites and doesn't allow free licenses.

No idea how it'll work out.
...what stops Google from just buying a newspaper, then?
>>...talent and infrastructure to support weed sales.

It is a plant, a crop like any other. As a practical matter it is no more difficult than farming apples or corn. (It actually grows wild over much of Ontario.) The only specialized infrastructure is that dictated by regulation. Sure, Canada does have a jump on building out the regulatory infrastructure, but that isn't something we can sell. We aren't going to be exporting that infrastructure to other countries because they will have their own regulations demanding a different infrastructure.

As for supporting weed sales, there are "experts" on selling pot in every country in the world. That skillset is well understood. UBC will not see a wave of foreign students looking to lean the mysteries of how to sell weed. We aren't going to see Canadians flying around the world establishing new markets and trade links. This stuff is already being grown in closets from Dubai to Alaska.
I don’t usually try to deliberately ask stupid questions, but I can’t help myself in this instance.

What counts as a EU publication? The author residing in the EU? Someone with a special “publisher” license? The author possessing EU citizenship? EU readership? .eu domain name? The domain registrar? The physical servers of the web hosting service? The backup service? What about those that use cloud services who have their physical infrastructure spread out wherever? And various combinations of the above…

Lastly, how would checking any of these be implemented by the software that’s supposed to be scanning for content that could possibly be in violation?
That's the traditional way of thinking and it might work well for traditional companies - but something as disruptive as this - I would vote for the visionary/thinker any day over the dyed in the wool, set in his ways guy.

Jobs/Sculley and later Tim Cook situation comes to mind - Sculley had the whole CEO experience but look how that turned out and look at how Tim Cook took over operations part which Jobs had no interest or knowledge of and made it work so well. If they had Tim Cook as the CEO pre-iphone days - I am not sure if we would have seen the iPhone.
Yeah, the French did a lot of things differently, the French national consciousness was matched only by its material wealth, so they could afford such frivolities.
I have mixed feelings about RoR, having seen both sides: the incredible speed of development as a startup bootstraps its MVP, and later as a mature company where the codebase becomes an immense behemoth of tech debt that's almost impossible to refactor. Don't believe the people who handwave and say you can avoid the latter by just "designing it right at the beginning". That's a lie, even the best engineers will build an unmaintainable monolith in RoR given enough time and if the business requirements are complex.

At this point I have a strong aversion to starting any product using a dynamically-typed language (regardless of framework). The initial speed and ease of development is repaid 10x later on in sheer engineering pain (if you're lucky enough to be successful, that is).
Isn't React Native end of lifed at Facebook? The effort is taking the best principles of React Native and focusing on Litho https://fblitho.com or ComponentKit - the effort to have a unified framework for both iOS and Android is pretty much abandoned.

I think React Native is in legacy support mode rather than active innovation.
This is good satire about overly-aggressive folks / jerks heh.

I guess the one nit I have is about the predilection to rag on weightlifters. It's just a hobby for many people. I don't do it myself, but I have met loads of the friendliest people that do. Working out, having protein shakes, and eating hard-boiled eggs do not make someone a jerk. /shrug
> in the new system... my contract expired

As I interpreted the piece, it was a three year contract which was stored in an old system, and not transferred when that system was replaced. So the firing was triggered by the system no longer seeing any valid contract.

If that's true, it would be breach of contract. But if it was a rolling contract expected to end after three years, then yes, it would be a weird situation but not a breach.
Elixir is an absolute pleasure. The benefits of Ruby's developer experience with a maintainable, scalable backbone.
Yes, the poster boy for the "choose a random chemical and see if it does anything useful" school of "engineering".

What's really sad is that this method isn't too far off from the way the pharma industry works today.
I hope it goes through and it truly is 'disastrous'. People who make bad laws need to be held accountable. And I'm sure they will be after the affects of this law are seen first hand.