skysight-inc/HackerNews huggingface dataset:
Toronto, Ontario, Canada | Achievers http://www.achievers.com | ONSITE | Developers

My company has built a kick-ass employee recognition platform and we're looking for developers of all shapes and sizes. Please don't apply if you're a jerk though, we don't hire assholes. He are some of our current requisitions:

Information Security Analyst

PHP/MySQL Web Developer

Senior Software Developer

Software Developer

Software Test Developer

Sr. Android Mobile Developer

Sr. iOS Developer

Sr. UI Developer

Technical Support Engineer

Windows Systems Administrator

Full details at http://app.jobvite.com/m?3TLHgiwo
Even if the authors of such services are highly knowledgable about security, they're going to rely on reports from hobbyist security researchers to fill in the gaps. There are major companies out there right now with dedicated infosec departments - and even they have bug bounty programs, because they know they can't catch everything.

I don't imagine this service gets an enormous amount of traffic. You might be among the handful of visitors to the site who are capable of noticing the CSRF issue, and maybe even the only one to go in and look at the source. He's had an email address up on his site for a while (hi@stochastictechnologies.com). Did you report the vuln to the author when you first found it?
> Better students are more likely to get all answers correct, worse students are more likely to make mistakes.

Yes! Until you brainfuck them, by putting the correct answer in the column B for the first 10 questions. Once the doubt is there, it's not gonna go anywhere.
Ottawa, Canada | ONSITE | FULLTIME | Network / IT expert

http://networkradius.com/

While we do RADIUS, a good portion of our work is designing and building networks. RADIUS, SQL, fail-over, load-balancing, replication, VRRP, virtual machines, etc.

We are looking for someone who is expert in networking and Linux administration. Someone who is self motivated, and interested in expanding their work experience.

Our customers are large enterprises and Telcos. Pretty much everyone you've heard of. Some travel to customer sites may be necessary, but not often.

We're a small team, but friendly and highly focussed.

We're looking for not just an IT admin. But someone who helps design networks, and keep systems at 99.99% uptime. Understanding systems and an ability to debug esoteric problems is more important than rote knowledge.

Email careers@networkradius.com
The Apple Watch’s unlock feature could turn the smartwatch tides
The Swede leading the way to a cashless society
Building a Custom Linux Distribution
Because he can.
Then you should just say, "hey, I'd like a raise, and I can prove I'm worth more to others". If you have to go as far as, "I am quitting!", you've got a problem.
Please note a lot of our focus on performance is around server side rendering (universal js/ isomorphic js). I'm trying to write a blog post around our performance improvements on a per module basis (it takes time to get good data and writing good content is hard :D).

You can use these specific SSR performance enhancing modules without the rest of Electrode:

http://www.electrode.io/docs/above_fold_rendering.html

http://www.electrode.io/docs/server_side_render_cache.html

http://www.electrode.io/docs/redux_router_engine.html

I agree, there are tons of platforms and when your starting out fresh, it's difficult to grasp the millions of ways to do things. We tried to focus heavily on documentation and building an application together for the folks that are new to the ecosystem. If you look at our docs, we try to build an application with you and we break it down from basics (get app running and deploy), to more intermediate (make plug ins, add routes, we will add material UI docs), to more advanced (lets do SSR rendering, above the fold rendering only, etc).

For small apps, we try to have a more barebones app using `yo electrode` instead of the boilerplate (which has everything), and get you deployed to Heroku or Google Cloud quickly (our docs break down how to do it, step by step).

The big thing we are missing for folks that are new to the ecosystem is what's inside our archetype and what goes inside a production app (the webpack configs, linting, css modules, and so much more). We are working on this part.

The benefit of WalmartLabs backing this project and actually using it internally to power walmart.com (and samsclub.com + grocery.walmart.com next year) - we are extremely sensitive to breaking changes. If we release a breaking change, we hear lots of groans around our desk and a line of folks expressing themselves :).
Proper project scoping (or to rephrase: identifying the true core business needs) is truly one of the hardest problems in tech. Over-scoping makes you end up with a ponderous system that doesn't serve core business needs very well, while underscoping can lock you into poor initial decisions that cripple your ability to expand into other related functionality.

What's the expression? "Plan your system for 100x growth, but build your system for 10x growth". Something like that except for functionality rather than scalability.

That and supporting the system. Junior engineers tend to think about building the tech, which is honestly the easy part. Keeping it working until the last of your customers are finally ready to upgrade 10 years later is harder than junior engineers tend to think.
I think you describe the tone quite precisely -- it is the same tone the author may have used to describe someone who built an Eiffel tower out of matchsticks -- the premise being that we get an objective description of a subculture (SV technologists) somewhat alien to the main readership of the magazine. But I do think that this objective tone is somewhat fake, because by the choice of examples and their juxtaposition the author does seem to occasionally take sides and actively (and subtly) parody certain attitudes. It is telling how many in this forum seem to have missed this and saw the article as unilaterally flattering.
I'd guess it is probably for Project Euler.
To me, freezing yourself to death seems like a case of 'danger to self' but I'm neither a lawyer nor a doctor.

But in other situations, the question arises just like in the article. At what point do you want to dose the individual with a sense of reality? If their mentally-ill self is content with the life they lead and "curing" them of it will leave them empty, sad, and hollow (in addition to the side effects of medication), is the arguably a better option?

If you factor in the fact that the hospital won't be there to help him rehab back into society, I can see the decision being difficult to make, as the author mentions.
L2L (http://github.com/meric/l2l)

A new programming language that is a superset of Lua and Lisp. You can write code in Lua or Lisp syntax and quasiquote/unquote both Lua and Lisp expressions.

The presentation of the project is minimal and off-putting to new contributors. It would be great to change this.

A lot of work needs to be done to make it more attractive to contributors, and to make it easy for people to contribute. It requires more documentation, improved documentation, more comments in existing code. I would love some advice as to where and when that documentation and comments be most useful.

Can you help?
A lot of the work is convincing people:

1. Convince customers to download the app, give their credit card, and then trust their rides and selves to a driver

2. Convince drivers to clean up their cars, download the driver app, and turn it on, and wait for customers to ask them for rides
Same way you would host anything else potentially unwanted by authorities.

You pay for it ahead of time in bitcoin and build redundancy.
I think that a lot of this is because things that seem quite pointless on an individual level are actually very important at scale. When I started at Google my job was pushing pixels around on the search results page, and when I left my job was leading a team pushing the pixels around (in the middle I got to do actual cool stuff). On an individual level, this is pointless and boring. On a corporate level, some of those pixels were worth literally $1B+. I would love to have a billion dollar business, but I can't get there from scratch by pushing pixels around on a page.
He can do lots of things. Why that thing?
I agree, using PostgreSQL logical decoding is a good solution.

MySQL can do something similar using a replication stream (https://github.com/siddontang/go-mysql-elasticsearch) and MongoDB by tailing the oplog.
Looking for advice on startup compensation for early employees
Yes, it's definitely worthwhile moving past jQuery, but no you don't have to do everything described in this article.
There's a lightweight framework called Mithril that when used with MSX will give you the feel of React, i.e. the state of your app flows in a straightforward way from the state of your objects, rather than from a series of imperative jQuery operations.

Just start with this example and customize to what you want to do:

https://github.com/insin/msx/blob/master/demo/index.html
Inconsistently used here, but it's the historical present:

https://en.m.wikipedia.org/wiki/Historical_present

For some reason, I hear a old-style narration over a documentary film when I hear this tense.
Have you looked into stateless React + Redux? These libraries are interesting in their suggestions for app architecture, and their api's are minimal.

One day perhaps React and Redux will be replaced by something else, but I think the strategy of a GUI functional layer consuming a stream of events is here to stay, and I wouldn't be surprised if it spread to native app design.
Hear you loud and clear, thanks!
A brief guide to mapping the user experience
Kolide | https://kolide.co | Boston, MA | Full-Time | Remote

Kolide is a platform that enables you to ask computers important questions, get back immediate answers, and take decisive action. Kolide does all this by leveraging the awesome power of Facebook’s osquery framework and extending it with built-in security and operations expertise. Mike Arpaia, the creator of osquery at FB is a co-founder. Investment was lead by the creator of Snorby, Dustin Webber, and that investment was matched new practitioner lead Hack/Secure investment syndicate.

Anyone interested in joining a dream team cyber security company at an early (yet well funded) stage should consider reaching out.

Stack: Golang, React, Docker

We need Golang back-end engineers and we need a front-end dev comfortable with React. Check out the job details at https://angel.co/kolideco/jobs.

Get in touch with me directly jason@kolide.co
New lower Azure pricing
yes, clicked the wrong thread - oops, Thanks :-)
That's so unbelievably false it makes me sad that you, a respected member of the security community, are touting it like a clear and present danger to anyone reading this site.

You stop.

Edit: I'm being absolutist because it's easier, rhetorically, but if I have to be explicit, I'm saying that the realistic occurrence of murder as a result of privacy tool usage, one way or another, is low, to understate things. To talk about murder as a problem in cybersecurity is like talking about meteors hitting car windshields.
Take Command 20 Crack Patch and Serial Key Download
Voter-fraud-elimination programs generate many more false negatives than there are false positives under the current system.
> "I have guns, gold, potassium iodide, antibiotics, batteries, water, gas masks from the Israeli Defense Force, and a big patch of land in Big Sur I can fly to.”

Imagine this coming from an ultra rightwing prepper nutball. Do you still love that quote?
We're usually there, but helpless. When you watch somebody slipping, even into dangerous territory, you're left with a limited set of options. Unless the family can prove "Imminent Danger to Self and others" or the person in question consents to treatment, we're just as helpless as the doctor here, even in concert with the person's care provider. So, much like the recent Michigan "poisoning" case (http://www.mlive.com/news/ann-arbor/index.ssf/2016/07/man_ac...), you just have to watch until the person crosses a line where they can be legally held. And often, that's after somebody's hurt.

I suspect that in many of these situations, particularly where a person has lost touch with reality, but not quite at the "I am the angel of death" level, the family is in the background and well aware, but simply out of legal options to help.
Health Recovery Solutions | Hoboken, NJ | FULLTIME | ONSITE

Health Recovery Solutions is looking for talented Software Engineers who are eager to solve big problems with cutting edge technology in order to improve the lives and promote the well being of patients who use our platform every day. We are a venture-backed software company that supplies leading medical centers with platforms that help reduce readmissions and improve clinical results. We are looking for people with
PHP, Java and web application experience.

Roles: Senior Software Engineer

If you are interested please visit our website and apply - http://healthrecoverysolutions.com/job-listing/9
I think one reason why React is so popular is that it forced you into an object oriented approach whereas before many developers used innerHTML everywhere. It is possible to write object oriented, structured "class" based vanilla JavaScript with imperative DOM manipulations though, witch is more performant then popular frameworks.
I skimmed the article, and all the comments here, and I still have no fucking idea what "gcj" is. It's apparently related to java. Maybe at least define your acronym once?
I'm not sure you can achieve good event sourcing performance using a regular database engine. Better to view it like writing logs.

If you really must expose an SQL API, perhaps you could read the journal on another thread or process and then make changes to the db based on the incoming "diffs" that the threads determines from the journal?
> It's tempting to throw every new fancy technology at the problem when that is suddenly an option, but it's better to focus on the goal of splitting it apart only.

Splitting it apart involves:

(1) Dividing the data and functionality into a legacy component and a new-implementation component,

(2) Making changes to the DB and application code for the legacy component,

(3) Implementing the new-implementation component.

In a monolith that you are breaking apart, the reusability of legacy code for the new-implementation component is likely to be low (you'll actually likely have to do extensive changes to the larger "legacy component" as well, but the reusability should be somewhat higher there.)

You have to use some technology for the new implementation component, and what you should aim for is whatever is the best fit for the job, whether it is similar to what existed before or not.

> If you have split it out, and it's now simple to convert to ES CQRS, then you are probably in a situation where you don't need to do that, as it works quite well.

I disagree. The hard part of converting to ES/CQRS for the components that are broken out ("new implementation" components, not the "legacy" reduced-monolith) is done in the analysis phase of what you are breaking out. Once that is done, implementation in a ES/CQRS manner is fairly straightforward, since defining the events that the component will handle is a core part of analysis, as is defining the impacts those events have on stored, reportable data (the query side of CQRS).
I don't really do eventsourcing for technical reasons. To me it's about creating an environment for project delivery where teams can succeed because they own more of their stack, from an org chart & organizational perspective.

As far as code is concerned, I see that as coming down to managing coupling & cohesion in such a way that the various pieces can be designed, built, supported, deployed and enhanced by the same team, with minimal need to wait for, coordinate with or be on the same page with any other team.

I think event sourcing & CQRS are great for enabling that because they result in the lowest form of coupling: Commands are fire and forget. You don't care who subscribes to your events. You don't care who publishes events you subscribe to. You never query anything you don't own in order to get information you need for your business logic. While the system is still small, we seem to get these advantages just fine when we do in-memory and in-process. Once package management, performance, units of deployment, etc. become an issue, we build out to add infrastructure, as needed. Because the pieces are pretty standalone within the code, it's not all that complicated to do, compared to "traditional" CRUD systems.

Not testing distributed: It's possible to deduce a lot with testing locally if it's simple to understand what's coupled to what and if good shared contracts for commands and events are in place, but ultimately the proof is of course in the pudding. When the time comes, there is a big advantage: The system is already fully operational and testing comes down to "does it still work?" If one were to do the plumbing before the business functionality and tests that in isolation ... does that really amount to knowing that it'll still be OK once it actually runs what it needs running ...? For starters, there is a danger of over-engineering because the required performance characteristics of the end products are more difficult to asses if there is no end product yet.
I thought this was a standard service as an add on to having a will held by a solicitor. That is passing on documents or a key to a safe-deposit box?
SEEKING WORK - Los Angeles, Remote Only

I am a full-stack (front-end focused) developer with 6 years of experience developing web apps. JavaScript is my tool of choice, and I have built large applications that scaled to hundreds of thousands of users in Angular, React + Redux, and Node.js. On my most recent project, I employed a serverless architecture that allowed the app to scale horizontally with ease at a low cost to the client.

I can also provide design resources at cost (which means you save a ton of money on design)

I am open to part-time or short-term freelance work and willing to meet up once a week in Los Angeles.
SharpSpring.com | Gainesville, FL | Full Time | Onsite

Hiring Site Reliability Engineers, Front-end and Back-end developers (Javascript/PHP).
We are a publicly traded company that still feels and operates very much like a startup.
Our flagship product is our marketing analytics and automation platform, and our developers are provided an opportunity to work on a wide range of interesting projects.
Contact lillian.vargas [at] sharpspring.com or visit http://sharpspring.com/careers/
Yes, you can. No, there's no real reason not to.

But honestly, I'd go with React if you can. The reason is, if the app starts taking off, and you end up with a team maintaining your app, you're much less likely to end up with an unmaintainable mess in two years than if you use just jQuery.

All applications, especially websites want frameworks. The framework is essentially a way to organize the massive amount of complexity boiled in. If you just roll with libraries, then you end up cobbling together a framework on top of it. You will then have to maintain this framework. This is fine when it's just you, it will coalesce into a bunch of conventions that's fairly easy for you to reason about.

But once you start involving others, then you're going to see your nice conventions get rekd like a bull in a china shop. Not everybody sees problems the same way you do.

If you pick the framework beforehand, then you don't need to maintain it, you can let the nice people at Facebook / Google do it for you. And whenever you finally get others involved, they're limited in the amount of architectural damage they can do because they have to stick to the conventions of the framework.
How else would you define corrupted state than “losing track of the objects in your app”? Not crashing as a consequence hardly makes it better.
Conversable | Austin, TX (onsite) | Full Time

http://conversable.com

We build chatbots and conversational experiences for big brands. We've launched bots for Whole Foods (http://m.me/Wholefoods), Wingstop (http://m.me/Wingstop) and Fridays (http://m.me/TGIFridays) and many more are coming soon.

This space is exploding and we need your help to keep up with demand. Backend, frontend, ops, whatever - we'd like to talk to you to help design, build and scale and our platform.

Send me a message at isao[at]conversable.com if any of this interests you.
Ditto. I switched years ago, largely because the last two HP printers I'd bought were crap, right out of the box.
Slack Bot Tester/QA | San Francisco CA | Remote OK | INTERNS OK

Slack Bot testers are needed for extending testing overall functionality of new slack bots and other messenger bots. Must be familiar with slack and at least the functionality of our current slack bot: http://sumve.com/slack/cc

Required: - Previous testing, curating or Quality Assurance work Optional: - Python and some scripting experience

Contact: biomimic@gmail.com
Sure, but some of these are due to real economies of scale for safety.

It can be hard to produce food safely, and ensuring food safety often has fixed costs (like buying safety/lab equipment, etc.)
I feel it's kind of different. Frankly, not freaking out over nuclear seems to be crazy thinking - even though it's also required to live a normal, sane life. I wonder how many things people shut off in their lives this way in order to cope.
Wouldn't the dog have trouble waiting out the ~70 day delay? It seems pretty hard to make it timely but not overzealous. It seems like this would work better as a mobile app that can pick up more signals that life may have ceased.
I'm doing live video ingestion. Transcode to DASH/HLS at 5 different qualities + alternate audio/subtitles where provided.
The lead developer was involved with angular 2, and basically left to develop Aurelia because he did not agree with the way angular 2 eventually went with.

Mostly it's a different take on the next step for Angular that many Angularists that are unhappy with how angular 2 turned out are putting hopes in.
Are you suggesting it's "unbelievably false" that broken privacy tools have gotten people tortured and killed? A lot of us in the "security community" know this to be true, with specifics.
Link Building Strategies That Work for ECommerce Businesses
On desktop I reflexively zoomed in to %125 and didn't think about it until I read your comment.

It also has a reasonable default font size my phone, so it's easy to read quickly. This is pretty rare since browsers gave up on text reflow.
NEXEDI | Lille/Munich/Paris/Tokyo | ONSITE | 6/12 months INTERNS and FULLTIME

We are looking for new colleagues and trainees to help on our free software solutions and contribute to research and industrial projects. If you are passionate about FOSS software and like one of our current topics (http://www.nexedi.com/jobs) get in touch! All candidates will do a programming test followed by an interview. We're looking for:

- Big Data/Machine Learning Developer (fulltime/intern)

- Out-of-Core-PyData Engineer (fulltime/intern)

- Site Reliability Engineer (intern)

- Help prototyping a Personal Search Engine (intern)

- Help prototyping an Artificial Intelligence Accountant (intern)

- Help prototyping an AI-based Business Bot (intern)

- Port the Linux Kernel to Javascript (intern)

About Nexedi: We are a small, international team (headquarters in Lille, France) creating free software since 2001. We spend time on client and research projects with ERP5 (Enterprise software), SlapOS (Cloud Hosting) and Wendelin (Big Data platform) being our main solutions around which we provide services. We all work with Chromebooks, our offices are paperless and we have no meetings. We mostly hack in Python and (vanilla) JavaScript. Come join us!