skysight-inc/HackerNews huggingface dataset:
In my opinion there would be two benefits to widespread coding literacy. The first one is that a wider range of people get in touch with the concept of programming and can consider it as a career option. This would IMO also help diversity. This does not mean everybody has to make a career of it, just like with all other subjects. The second benefit would be that a lot things people do manually right now could be helped along by simple ruby or python scripts. If more people had that tool on their belt, they could use it when it's beneficial for them. They don't have to be a full-time dev for that.
Can someone who upvoted comment on what this is supposed to do? I searched `car sales in Europe` and the first chart I got is `new startups valued at 1bn or more`
If you run on not the latest version, make sure to check for updates twice in order to see the free minor version upgrade.
This was a really well written piece. Always enjoy reading these on HN.
It feels like the inmates are running the asylum to me.
Kickstarter scammer promised a $100 3D printer, built a house with funds
Hidden Settings Panel in WordPress
We self-host GitLab as well for ~20 users and are very happy with it.

We install every incremental update, which GitLab publishes very frequently -- weekly or several times a month. They are always seamless. The GitLab team is working so hard.

https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELO...
What VCs mean by the term 'blue flame'
Ask HN: How did you get started with OSINT?
I am interested in learning more about OSINT.
If you are an OSINT Analyst with experience from law enforcement, military, cyber security or the private sector, please share what your work entails. How did you get started? Where do you see OSINT going in the future?

What blogs, courses, tutorials do you recommend? Do any of you have experience with the AutomatingOSINT.com online courses?
Calling someone a MILF is at best socially awkward. Using it on a coworker is grossly inappropriate. Plus if someone is problematic this early then they will likely continue to cause problems.

With that said, I worked with very stupid people. Great programmers but under-socialized. These people have no idea how much harm they are causing but will snap out of it if reproached by HR or management. I know that doesn't sound fair but there are a lot of dumbasses in our industry.
What? APKs are signed by the developer before they uploaded to the store and the signatures are verified by PackageManagerService which is a part of AOSP.
I get that, but and most of these companies do offer paid alternatives. My point is that if you are able, why not self host? There will always be companies that cannot self host which pay for the hosted solutions.
Like the left-wing extremism that SJW's practice - misandry and calls for genocide based on race (white), gender (male), sometimes even sexuality (straight) run rampant in that movement. Those are harmful.
An Imposing Building That Hums with Life-Saving Capacity
Certainly, most websites have no obligation to serve me as a customer, but if they tell me that my name is "invalid", they shouldn't be surprised if I take my custom to a competitor who isn't quite so rude.

But you seem to be missing the fact that "Gijs in 't Veld" is perfectly valid Ascii, as would be names like "O'Leary" or "O'Reilly" that are perhaps more common in the English-speaking world.
You forgot this tweet or image: https://twitter.com/thomasfuchs/status/708675139253174273

That seems to be required when mentioning React since you can't learn just React, you have to learn React + at least 5 other things to get the same featureset of Angular 2.
Ask HN: When you are learning a new PL what do you create as your first project?
Why use the word sketchy when you simply don't agree with his opinion?

The post described a pretty different situation that just disagreeing with him. Not that I'm taking it at face value, since it wasn't described in enough detail to evaluate it for myself.
This actually used to be the way of parenting until a couple of generations ago. Just stay out of kids way and they'll figure it out. Be there to make sure they don't kill themselves or others. But otherwise you don't curate their lives.

We're infantalizing everyone now. I was in a law school class (everyone 25+) where the federal judge lecturer called us all "kids." The age of majority seems to have inflated up from 18 to around 27 in America.
Works well for me. I have like 10 or 12 private repos for personal projects I'm not ready to release publicly yet (or ever).
QtQuick is definitely a step forward with respect to touch input and slick animated UIs, but there are things I really dislike about it.

* Javascript. Ew.

* Deployment is a bit of a nightmare. They have windeployqt.exe which helps, but it doesn't automatically copy the MingW DLLs, and all the QML files aren't compiled as resources which is a bit ugly.

* The apps are huge. It's like 50 MB for hello world.

* There isn't very good encapsulation of QML components. All object IDs seem to go in one big namespace.
The Mole Rat Prophecies
Is this a library? Or some kind of data service? How does this compare to http://www.highcharts.com/ ?
The author of JSON.NET has decided to "wait until there is documentation". I found out about this when another library author linked to this issue as his reason for not creating a NuGet package for .NET Core:

https://github.com/JamesNK/Newtonsoft.Json/issues/618
I used this: https://awesometoast.com/downgrading-to-itunes-10-7-from-itu...
Isn't the value of the article completely divorced from the time it took to write it? (I don't pay more for a movie that took five years to make than one that took a week.)

News is one of the more obvious examples that things become less valuable as more people have access. If I am the only person in a room to have read an article, I am more interesting at a party. If everyone read it, I might as well be discussing the weather. If I find out about an earnings report a microsecond before other investors, that news is much more valuable to me than it is to them.

Journalists also have to deal with instances where weeks of effort failt to uncover anything worth writing about. The patron/artist model might be the only way to support individual journalists. It might turn out that journalism looks a LOT like private investigation or corporate espionage.
What an odd front page. "Type to search", with no indication of what to search for. I typed in 4 searches, got "No results found" for all of them. Strange.
This is awesome. Qt Creator is one of the best C++ IDEs there is (I'd say second only to Visual Studio, and that's debatable).
"Everyone should learn to code" makes at least as much sense as "everyone should learn trigonometry." To me, it makes much more sense, actually.

I'm a software engineer. I might not be if I wasn't exposed to it in high school. Exposing more people to software is a decidedly good thing because it gives people agency. Teaching coding in high school also can enhance math and science that's already being taught. It gives students another interface to the curriculum that's far more exploratory than pen and paper. Everyone should learn to code.

Everyone should not be a software engineer. Obviously. People should do what interests them. That doesn't mean bootcamps are bad. Actually, I work at one! I think we do a really good job. There are problems with the market that Basel correctly identified. Its hard for consumers to assess the quality of bootcamps. There are certainly are snakeoil salespeople out there. But, I've watched hundreds of my students go on to start fulfilling careers in tech because of their hard work and ours. The market will sort itself out. The bad actors will eventually go out of business.
Here are the why/hows as I understand them:

1) This is an informal shorthand agreed between people who already know each other in the particular context of work, so there is no surprise or ambiguity. Outside this context, I would use, and expect to see the dictionary sign.

2) It functions as an 'in-group' slang, boosting cohesion and good will.

3) There is a certain humorousness in bending a symbol into an informal use. This is more pronounced in cases where the alternate meaning is irreverent or vulgar. I have no intention of expanding on the second point.

4) One does not have to be facing the SL speaker. The 't' symbol can be recognized from beside the person or even behind. Point 5 gives the rationale for this.

5) It can be communicated without changing focus or posture, allowing concentration on the task at hand without breaking the workflow.

6) Though 'thanks' is a brief gesture, 't' can be signed and understood even more quickly. Just a flash of meaning.

7) The sign for 'good', while it is also used to communicate thanks and has advantages 4,5,6 listed above, can be ambiguous, violating the principle of least surprise (see point 1 above). It is more generic, while 't' is specific.
Strictly speaking, the closest thing to a "team lead" would be the ScrumMaster. In a scrum, all team-members are just "developers", there's no hierarchy or differentiation in status between them.

The ScrumMaster is less of a PM, and more a "Servant Leader"; their role is to empower the the other team members, get road-blocks out of their way, and keep stakeholders/product-owners from butting in during a sprint.

Hope that helps.

For more info, I'd recommend starting here:

http://www.scrumprimer.org/scrumprimer20.pdf

And then jumping into this book if you're really interested in the topic:

http://www.amazon.com/Agile-Project-Management-Developer-Pra...
How Amazon Is Becoming a TV Powerhouse
It seems like these are the (manually created) charts used in qz.com articles.
> If you need to give Epic Games special treatment just because they have a huge amount of outside collaborators, then your pricing model is broken.

This is an unfair thing to say. Exceptions to otherwise simple rules does not at all mean that the simple rules are "broken".

It is also an unfair thing to say since he clearly says that not only is Epic Games getting this treatment, so is everyone in a similar situation. Furthermore, it has always been possible to negotiate special pricing for special cases. Just send them a message. That is how sales works at almost every company.
Since you are talking about proofs, will you now provide evidence that it was criminal in roman law to unintentionally cause someones death? They had mines and work accidents, so it should be easy for you to find.

I mean, I only recited what I heard from a professor of law and legal history, but I am sure that as a random person on the INTERNET as yourself has more validity. That extraordinary evidence you provided is all I needed.
That was very well said. Statements like this attempt to find common cause and allow us to come together for a solution. Calling someone a member of "The Patriarchy" is dismissive and removes men from the conversation.
Maybe, open an issue? It is still a work in progress after all. Lot's of open issues for Linux so far. [1]

[1] https://github.com/nylas/N1/issues?utf8=%E2%9C%93&q=is%3Aiss...
I'm not sure you need to put a geographic bracket around that statement. I very rarely see C++ for web development.
What's interesting is that Chris Sacca[1], Paul Graham[2] and Marc Andreessen[3] all say they've never heard of this term.

[1] https://twitter.com/sacca/status/730281280806346752

[2] https://twitter.com/paulg/status/730404581469884421

[3] https://twitter.com/pmarca/status/730256638938996736
>an even greater number are run by modern snake-oil salespeople tapping into the average American’s desperation.

I need to see some data on this.

It is true that whenever code is being written, someone on the team needs to understand the problem well enough to ensure that the requirements are being met with an appropriate architecture and design. In many organizations, these roles are filled by experienced persons, and the project just needs programmers.

Boot camps should do two things: 1) Identify persons with a mind for programming and the will to learn it; 2) accelerate that learning far beyond what a person can self-teach, with a focused curriculum that will enable them to contribute to a team on completion.

The point of the 'everyone learn to code' movement is to address the long term loss of better-paying manufacturing jobs with jobs that pay better than minimum wage. For sure, not everyone qualified for manufacturing is going to be a good programmer, but manufacturing automation is expanding, our competitiveness will depend on it, and the manufacturing robots and systems need to be programmed by someone.
Don't forget about how native apps can integrate into the unique features of the underlying platform.

On the Mac: Can an Electron app be scripted with AppleScript? Can it hand off to a mobile app using the Handoff API? How is the accessibility?

Windows has similar things with COM and Continuity. Can an Electron app play nice with these technologies?
Programming is the profession with the least barriers to turn into a career. Most others has mandatory licensing, degrees, training, etc. How long does it take to be a doctor? A Lawyer? Most traditional engineering degrees? Heck working as a barber takes more effort in most states.
This is true given a dedicated enough programmer. Since most programmers aren't quite this dedicated, however, this isn't 100% true.

From what I am aware, in lower level (C++) development there are some definite strategies to "deter" piracy even at a technical level. Stuff that Urs (developer of u-He software synthesizers) talks about here, eg:

https://www.kvraudio.com/forum/viewtopic.php?f=4&t=400768&st...

Basically:
A) Make the protective schemes as non-obvious as possible in a disassembler (obfuscation, making the copy protection part of some core routines etc.)
B) Provide a few obvious "sweeteners" that "pretend crack" the software for a period, but then show a "whoops your copy is pirated here's a offer to purchase it" later. (EG: a time bomb.) This allows the crackers to get their 0 day warez thrillz, without actually truly cracking the program.

Of course, none of this is 100% insurmountable. That's not the point of this exercise. The goal is to basically make cracking the software a chore more beyond usual, and therefore, not worth the typical cracker's time.

I am not sure how one would approach this with managed software or web-wrapped software (although if you can run the copy protection in a native module, that would be the way to go.)
Add Groovy to that, and you have the dynamic typing and flexibility you see in Python and Ruby with Java. JDBC with Groovy SQL or JSON parsing with Groovy's JsonSlurper is a joy to work with.
He's got a lot of karma (#2 according to her blog post). She makes a big deal of the date when she reached 10k. I think it's a safe assumption that's an important metric to her.
>>It is very nice that in your instance and outcome that was so mutually agreeable was reached by all parties. However, it could have easily gone differently, and can go differently in the future.

Exactly. It was a big risk and her company frankly got lucky that it worked out.
Recently I upgraded a project from Rails 3.2.x to 4.0.x... 4.0.x -> 4.1.x... 4.1.x -> 4.2.x

It was, and still is, a nightmare.

Technically speaking Rails itself upgraded in a reasonably straight-forward way, just follow the documentation (well and a few blog posts here and there for the things missed in the official docs). But all the additional Gems, and dependencies of those Gems (and so on) made the process excruciating. Many things broke in subtle ways at runtime (no compilation, so no compiler errors) and there was no clear path to upgrade; because whilst Rails' upgrade path is documented, there's a plethora of Gems that also needed to be upgraded separately (some in contradictory manners).

You might wonder why I was so out of date in the first place. Two reasons:

1. I inherited this code-base.

2. I've attempted this (or a similar) upgrade about 5 other times in the past; spending hours upon hours debugging crashes (or just weird behaviour) with enormous stack-traces where my application's own code often doesn't even appear in the stack trace. It's only now after making several failed (or rather overly time consuming) attempts I was able to come up with a "workable" upgrade path.

Gems dynamically generating methods left, right and centre, Gems replacing methods of seemingly unrelated classes (when they definitely do not need to), and crazy "conventions" that hide all the actual logic make debugging any sizeable Rails project a complete disaster. Don't even get me started on the poor performance, much of which is to do with poorly designed Gems and not even the Ruby interpreter's fault.

That said... I still turn to Rails when I want to get a new project (with users, database, login, admin etc.) up and running quickly. It's a shame, but in terms of development speed, it's hard to beat Ruby (and Rails). For small projects Sinatra is very solid, and Padrino is interesting - but honestly I can't wait for the day I can move to a compiled language and still achieve this sort of development speed.
I was about to make the exact same comment. People should automate their most boring and mindless tasks, that's the only way to achieve large further productivity gains. It's never going to be economical to pay a developer salary full time to analyse and automate everyone's little tasks. But for that coding needs to be simpler, easier to do occasionally. VBA-style (but VBA was a 90s language that was never updated since). In that spirit, teaching C++ in school is counter-productive.

Exactly like everyone shouldn't need to be a professional carpenter, but have a basic DIY tools and know how to assemble some ikea furniture. Or basic physics understanding to know what to do and not to do with an electrical socket!
Has Rails ever been for "complex, large-scale web apps" though?

My understanding of it has always been that it was for the vast majority of web apps, which are neither particularly complex nor particularly large-scale. Rails was there to help those projects get started easily and iterate rapidly. If your Rails app turned out to be a hit you'd probably need to rewrite it, but that was OK because (1) very few apps qualify as "hits" and (2) only apps that actually get written can become hits, and with Rails it was much easier to turn ideas into functioning code.

Large-scale web apps have their own unique types of problems. New tools may be needed to cope with them, but that's a whole different thing than the problems Rails was created to solve.
My needs are pretty standard. I run an NGO and have some amount of paperwork and data tracking to do in a word processor and spreadsheet application. Due to the collaboration requirements, we're stuck with Google cloud suite (the choice was made back when there were zero reasonable cloud-enabled alternatives). Google's office suite is theoretically capable of doing most of the things I need[0], but the omnipresent lag when you try to work with a bigger document or (more often) several documents at once is very annoying and slows things down. Half a second here, five seconds there, and it all adds up to significant frustration.

There's a significant difference between "theoretically X can be done with it" and "it is useful for doing X". You can drive nails with a plastic hammer after all (and most people don't even need the "additional" feature of pulling them out).

[0] - which is partly because I reduce expectations of what I can do. Think of it as generalized Blub paradox - you think in terms of the tools you use. Get a better tool, and suddenly you can do more, do it better and do it faster.
The newfangled approach is something like HashiCorp's Vault, which is a dream when you're looking at more than half a dozen systems with similar roles. A different approach that I like to use for single or smaller cluster systems is Ansible's Vault and rolling out config files based on templates per environment. All actual config files are gitignored so I don't have do deal with conflicts on the server if I use a git-pull style deployment, and ansible itself can backup/version whenever they change.

Additionally, git does keep that history (as it's supposed to), so if you just delete the key from a private repo as you're trying to make the repo public, it's trivial for someone to walk the commit history looking for historical API keys that might not have been rotated. In order to purge that information from git, you then have to go re-write the commit graph from the point of the key's insertion (with it removed) all the way to the present. It's not impossible to do, it's just a major pain.
Exactly. If you work in an office with a computer at any job, learning basic coding can save you a week of work every year.
Could you point out where the author of this post even came close to suggesting that Rails is for great developers who don't need static typing?

Or did you accidentally post this unrelated opinion in the wrong thread?
> With Rails, you end up in the weeds in the long run, but the alternatives put you in the weeds right off the bat (with the promise of eventual salvation). The reality of most product development (ymmv) is that the former is highly preferable to the latter.

You're absolutely right.

And yes, Rails has quirks and I agree with most of the criticism of the other article

Option 1: Twitter is built on RoR, have growing pains and lots of whales when it has an established product (when it gets the investors and the money to invest in a rebuild)

Option 2: Twitter is built on Clojure, product takes more time, iteration gets slower, hiring is slower, some other competitor gets ahead. Ooops
In response to HN feedback, you can now use systemmeasure.com as a solo developer for free.
Swift Compilation Time Reporting at Tumblr
never store sensitive data like API keys in a repository. Or you can do that but encrypt it so that nobody which can view your repo (even if it's private) can use that data immediately. It's like storing passwords in plaintext in a DB. Every (DB) admin will tell you: Don't/Never do that.

I've recently also have to do with this problems while doing server setup with a private repo. I'm using Ansible and Ansible Vault to encrypt sensitive data and the encryption key itself is only accessible (a password safe) to certain members of our team http://docs.ansible.com/ansible/playbooks_vault.html
Thank you for sticking your neck out and actually sharing your real-life practical experience, something that seems to be exactly what the submitter was looking for!
I believe the common form is "X is child's play (next to|compared to) Y".