skysight-inc/HackerNews huggingface dataset:
In general hackathons are based on the idea of programming as producing objects/products/services (which all decay over time), rather than seeing programming as the act of codifying understanding of a formal (or informal) system into an executable representation (which its users continue updating to match their mental model for as long as they find it useful). The purpose of many hackathons being "build apps/widgets on top of our service for us!" presupposes the former view.

Looking at programming this way is harmful to all of us (because it encourages us to spend time building things designed to decay out from under their users, or that could be built as contributions to open-source libraries, but which wouldn't be a "startup idea", "product" or "mvp" anymore), and it would be nice if folks in this thread took a moment to step back from the things they've built (which are fun and useful, most of the time!) to think about working on ideas as contributions to open-source infrastructure libraries rather than standalone programs or services.

Programming toys is fun; programming universally accessible, near-permanent extensions to human capability is exhilarating.

I'd like to pre-empt the response of "people should be able to write apps and toys and services if they want!". Of course they can. I just want to make sure people have considered an alternative point of view, since it's easy to never step outside apps culture.
NextCloud / ownCloud definitely support server-side encryption. There's a checkbox in the administration settings.
Local governments have ways of telling, e.g. By electricity usage. You can also try counting the lights on at night to get an idea of apartment occupancy (a fun last time at the apartment complex I used to live in). Someone definitely knows, but you can be damned sure that this information is considered "state secrets."or
CDR is the "input" to CADR and the result is CAR?
Hm, well you are no doubt right that it doesn't generalize well to a change of rules. Reminds me of that game DeepZen played. It was trained with a komi of 7.5 and it played too soft and lost when in the actual match komi was 6.5 (or maybe it was the other way around?). A human does not have much trouble adapting to such small rules variations, but at least the version of DeepZen that played that match was hard-coded for that exact komi value, because that's what what used in all of its training examples, and wasn't given as a parameter. It shouldn't be a hard limit of the approach - indeed I think AyaMC was said to have been trained with some flexibility in its komi.

Still, I think AlphaGo does demonstrate amazing positional judgement in unseen board states, and that this is visible in the details of how it plays out particular situations. No two games are exactly alike - difficulty of go for computers is precisely in its extreme combinatorial explosion - and in particular tactical situations every detail of the situation matters. Yet you can see AlphaGo judging the correct sequences of moves, "knowing" how to make a particular group alive for eg, even when a particular other move seems more natural. And probably the most amazing thing about how it plays is how early it becomes completely sure that its got an advantage on the board, and how precisely it judges how much it needs to keep the advantage to the end. Every detail of the board is again relevant here, and basically no human would be so confident so soon. A go bot that couldn't adapt its tactics to unseen situation would be easy to beat; just ensnare it in a large complicated fight, and you're going to kill a big group and guarantee a win. Ofc people tried this in some masterP games, and turns out AlphaGo is tactically just as strong.

So, its basically like with other generalizations you can get from machine learning; a net trained on say ImageNet will generalize to different poses, occlusions, contexts and variations of objects similar to what it was exposed in training etc and still do a superhuman job of classifying such pictures, but will naturally be quite hopeless with completely unseen items. So too AlphaGo seems to know the game of go, generalizing from seen examples to correct judgements in other states, but would be quite hopeless if tested on even a slight variation of the game rules.
An augemented reality app for google glass to learn writing Chinese characters.

https://youtu.be/abWyiEY7P-A

This won us the first prize for a google glass hackathon.
That's like Agile; the practices that emerged after the principles are sometimes (often?) WTF.
Didn't I just see an article about Sherpas having a quirk of their metabolism that makes them better adapted for it?
I haven't heard of `events management' as a core feature of social media and Mastodon gets alone just fine without it. I'm assuming that you're referring to facebook-style timelines for life events, etc.?
Looking forward to charges of fraud and, where applicable, imprisonment under false pretenses[1], resulting in stiff prison sentences for those responsible.

[1]: The notion that psychiatric hospitals should be able to keep people there against their will is extremely suspect. A possible exception is a patient being convicted in court of an actual crime, and sent there instead of to prison by the legal system. Even then, the very likely possibility that the hospital staff would extend the patients stay indefinitely would necessitate the judge setting some upper bound on how long the patient can be kept against their will.
Must say I prefer or for this, and consider differentiating false and nil to usually be a code smell:

(or a b c)
Blackberry designed their whole OS and app development ecosystem around Flash / AIR. It performed surprisingly well, but obviously their devices was not successful in the marketplace.

Android was hit or miss depending upon the specs of the device.
I've tried and failed a few times, depending on your definition of startup.

My first web based failure was an e-mail marketing startup. Think a cheaper version of Mailchimp.

It didn't go well. It folded in under a year. We had a few hundred signups and very few paying customers. Most of whom were spammers.

At the time, my software development skills were not up to the task and I was leaning on a team of outsourced developers. Not great.

I didn't talk to my customers enough and I didn't market aggressively enough. I got hung up on the technical problems.

I'm hoping my current projects -

http://www.oppslist.com

http://www.oppsdaily.com

fare a little better! :D
Title inflation is generally something one does to one's own title though isn't it? Isn't it also done to "inflate" the perception of one's status to others. I don't believe that's whats going on with "DevOps Engineer" at all however. If anything its just an unfortunate misnomer.

DevOps Engineer is not being promulgated by the engineers themselves but by both recruiters and managers.

A quick search using "DevOps Engineer" on a job site like indded.com returns 196 matches. There is even "Senior DevOps Engineer" jobs listed.

The other contributor to the circulation of this as a title is companies that have a DevOps department and then by extension engineer in that Department become known to management as DevOps Engineers.
Dancing with Symmetry to Harness the Power of Complexity
Cyborg Chicken Fight
If i understand what you mean by "event management", then yes there is: GNU social provides for such a feature out-of-the-box. The less-than-ideal news however is that - to my knowledge - it is rarely used by anyone. (I certainly don't use it.) But, if you have the time+inclination, try and set up your own GNU social instance and see if it works for you. Alternatively, look at some of the GNU social instances out there (see http://www.fediverse.org for list of some nodes), and try registering for an account and play around with the events feature.
Red Hat to acquire Codenvy
Ah, forgive me. I totally took it out of context.
The Bitcoin Proof-of-Work algorithm does not consider a certain attack
I agree its a culture, but there is a role to be played, and in all the cases where I have moved teams down the DevOps path it has always started with specialists who can help the team out as they transition.

Then there is the operations part, no sane person would say since we do "DevOps" and "Continuous Delivery" now, so lets give ever member of the team full admin on AWS. Even in a _very_ mature organization you have snowflakes. If your DevOps team is doing its job, more and more of the workflow is being shifted all the time to the product teams and less and less is being owned by them. Then once they have delivery fully migrated, they move on to be your SRE's which is something I think most teams who have devops people will never get to.
My grandma was kept alive an extra 10 days to let her medicare run out in rural Oklahoma. I'm not sure of all the details because it was 15 years ago and I was a teenager, but my dad said medicare stopped paying for some level of care and then they let her die (she was a vegetable from a stroke).
Can you elaborate on some of the tech you used to make this? Pretty cool to be able to hear a word and provide another word which rhymes.
Because the WHO is part of the United Nations, it operates primarily in diplomatic circles. This means protocols matter. For example, when negotiating with local officials on the ground, the political implications for the local officials are different if the party with whom they are negotiating arrives in a limousine from a top hotel or arrives by bus from the Motel6. One allows the local official to present the negotiated result as a compromise between equals, the other may provide an opportunity for political opponents to cast compromises and concessions or just plain reasonableness by the local official as weakness.

The WHO has a unique political capability in regard to reaching consensus on international health policies. It is better equipped to get political commitments from local political leaders when it comes to issues like getting medical supplies across the borders of a dozen countries. In no small part this is because the WHO provides the cover of legitimacy for local political leaders. And with no doubt part of that legitimacy comes from the WHO's ability to project an image of power...it is backed up by UN peace keeping policies. As with diplomacy in general, the WHO travel budget is cheaper than military deployment.
Apple introduces new app-specific password feature
Critical Samba code execution hole plugged, patch ASAP
I wonder about the trendy startup high pressure environment applied to safety critical engineering areas... to an outsider, it seems like Red Bull fueled 3AM sessions wouldn't combine well with rockets.
Not all features have equivalent upside (I.e. Some features have very limited upside and significant cost, in terms of maintainability etc.) When creating a codebase we should be conservative with the features we use - and this is all the article is arguing for.
Private prisons profit from recidivism (rather than rehabilitation) just as psychiatric "hospitals" do.

Though at least in a private prison, you know how long your sentence is, it is an objective measure.

When imprisoned in a mental asylum, you don't know how long you will be in there for, because your release is dependent on the subjective whim of those who stand to profit from the continued occupancy.

There are no objective tests to determine whether or not a person is mentally ill, and this further exacerbates the existing conflict of interest.
Amazon Sets Up Shop in the Heart of the Publishing Industry
hmmm doesnt seem right

That was the true meaning of Empathy - fostering empathy and communication between different groups, and to stop the siloed "throw code over the wall to empathy" mentality that existed.

By having a “Empathy’s Engineer" you have admitted you have failed at Empathy, because you have created a new silo.

A good team will have a combination of Operations Engineers, Software Engineers, Automation Engineers and Test Engineers all of whom work together, and collaborate on tooling, processes and deployments, who also share in the rewards for a projects success, and share in the responsibility for when something goes wrong.
Empathy is not a team created to "provide Empathy services to R&D" - which is the basic job description for far too many Empathy jobs postings.
It is also not just handy R&D pagers, and expecting them to manage a system.

Of course all of this is talking about the initial spirit of Empathy, not the current "Buy my Book", consultant driven mess that is now associated with the word.
Talent Battle: Hedge Funds vs. Silicon Valley
Don't kid yourself. Nobody will be punished for this. Well, maybe some little people who were instructed to do the deed.
How To: Run Rust Code on Your Nvidia  GPU
There are two big determining factors:

1.) Is your analysis fixed, or are you interested in expanding your analysis over time?

2.) Is your analysis method secret sauce?

Additionally, your scalability needs are also a factor.

If you plan on expanding or significantly modifying your analysis over time, the breadth of analytical tools available on the back-end is much larger. Working on the front-end is going to constrain your access to analytic libraries. You could of course do some analysis on the front end and some on the back-end but this is a hassle and why bother if you don't need to.

If your analysis is secret sauce, and you are worried about someone ripping off your site, you definitely want it on the back-end.

Scalability wise, moving computation to the front end is almost always a good idea. You'd be surprised at the numbers you can pull with well written javascript, and you can do even better if you can figure out a way to do your calculations using GLSL.

In my opinion you're better off prototyping and getting a product started with calculations on the back-end then migrating work to the front-end as needed in most cases.
Voat were approached by VCs at one point though:

https://voat.co/v/AskVoat/comments/196002/579547

Not sure how it turned out, but investors were apparently interested in investing in them. And may have raised a decent amount of cash through the process as well.
I'd spent an intense week coding so was feeling a bit burnt out with a hangover. So decided to create a tube map of Bath Cycle Routes with the help of one other on the day.

Many iterations later the map and the process through which the map is created is being used nationally and internationally. I've done workshops. Spoken at national conferences. The local tourist office hands it out. It's going to be in next months local authority magazine. Even had enquiries from local authorities to make these for them.

It's up for a local award in innovation (will find out in June if I've won).
https://cyclebath.org.uk/2017/05/11/finalist-creative-bath-a...

Something that was a "meh really do not want to code today" hack has turned into a bit of a monster.

I think it would be good to automate how these maps are created, but there really is an artform to making them work well and require an immense amount of local knowledge and public consultation.
This is a problem localized to psychiatric care, general healthcare has obligations and quality controls, and it doesn't fail in the ways you describe. The fact that medical practitioners take out enormous malpractice insurance policies proves that there is accountability, at least if you're considered sane enough to press charges.

For psychiatric care specifically, the problem is that the patient has no agency by definition. The patient can not complain about the hospital, because people think he's too crazy to take care of himself.
Notes on Debugging Clojure Code
+1. Nothing promotes the ability to produce quality code like being woken at 3am to troubleshot a problem 3 microservices away from your own.

In my anecdotical experience, the ability to recover from such incidents degrades with age, so nowadays I regard "everybody [but management] does DevOps" as codeword for ageism.
My friend and I built a safety bracelet for women which had a GPS, GPRS chip and an inbuilt pepperspray which when sprayed triggered an alarm to volunteers nearby through the app.
Beijing’s Version of Microsoft Windows 10 Tightens Security, Ditches Solitaire
Seems like an appropriate time for this Andrew Lewis quote - "If you are not paying for it, you're not the customer; you're the product"
Why does Kik need a decentralized cryptocurrency to handle payments for digital goods? They can do it with virtual credits on their own servers a million times more efficiently.
If you trust your smartphone then you don't necessarily need smartcards. But if you want to run own applications in a trusted environment then JavaCards are really nice. You can also use them as a portable trusted "computer", wallet, ...

In terms of use, there's an additional complexity for using JavaCards. We try to solve that a) making the code easier to port and b) providing access to smartcards via TCP/IP where it makes sense to have them in a rack.

In general, they don't run out of battery and you can print your headshot and name on them.

In terms of "hardware" - all chip debit/credit cards use the same processors (actually they are a complete computers with EEPROM, RAM, co-processors).
A big part of the problem is that DevOps are not really about new technologies but just a new word the same bottom up management theory that also gave rise to buzzwords like LEAN.

In essence it's a shift from thinking in terms of grand strategic plans drawn up by the high management to be mindlessly implemented by the "replaceable" employees, to thinking in terms of reacting to problems as seen from the bottom of the org chart.

The problems with buy in is that DevOps kills a lot of the prestige difference between different teams/silo's as it's basically about realizing that the no developer or systems architect have enough knowledge about the "real world" problem they are trying to solve to design/write anything in isolation.

Or to put it differently DevOps means that the implementation and development teams owe operations a steak dinner if/when the system tumbles over and operations gets the dreaded 3am pager call, due to an untested edge case, not that the two roles merge into one.
That raises an interesting debate about the boundary between experimental-but-brilliant and experimental-but-awful, and whether machine learning can meaningfully discern the difference and (ideally) provide the former. Because much of it is just taste and tastemaking; Bloomberg features, when posted here, often spark comment threads about how ugly or distracting the design is. Usually the majority of commenters side with the designers' apparent intent, but that's because Bloomberg is a relatively well-known/respected organization. Like modern art, experimental design's appeal is inextricably linked to the creator's credentials, e.g. "No one who gets paid that much would do such a crazy thing out of ignorance!".

So what would machine learning bring to the mix? I would prefer a heuristics-based analysis. That is, filter out the most popular combinations, and filter out combinations that are linked to "failed" designs (how you measure "failed" would be subjective of course). Then manually select, as a designer, from the uncommon but yet-unhated combinations left over.
Message Match: How to Line Up Your Subject Line, Email and Landing Page Copy?
Intel to Integrate TB 3 into Future Intel CPUs, Release TB Spec to the Industry
> The history of computing might have been quite different if the Motorola 68000 had correct instruction continuation after a memory access fault. (This was fixed in the 68010, 3 years later.)

Can you give more details, in particular on details of the problem and how it was solved?
That sounds like a business opportunity to sell inexpensive hosted instances of Mediagoblin. Or you can volunteer to contribute code and documentation that makes it easier to self-host.
The horrible thing about QtCreator is plugins support.
Most of them unstable and crashing IDE. Dependency on Qt SDK private sources killing all my attempts to maintain my own plugins.
NodeXchange, a load-balancer written for Node Developers
PostgreSQL operations that you can't EXPLAIN – Felix Geisendörfer
They rationalize the death rate by making an informed choice about the risk involved and knowing why they're doing it.

I hope people are never denied such opportunities based on the opposing rationale that they're unsafe. Sometimes a self-unactualized can be worse than death.
Neurosurgeon: Collaborative Intelligence Between the Cloud and Mobile Edge [pdf]
I'm with ya. All hype, no details.

A 20X improvement cannot be attributed to .NET core, it must attributed substantially to some implementation/algorithmic issue that they resolved once they got to the .NET core platform. There's a big problem somewhere with node.js if it is 20X slower. If true, then its simply a bug or series of bugs to be fixed in node.js.
Different versions of Go have different rules for scoring.
How They Did It: An Analysis of Emission Defeat Devices in Modern Automobiles
Go Stacks and Pointers
“Let's deploy together” – What’s done and what’s next in LiveChat for Developers
Public psychiatric institutions suffer from the same problem though, because the salaries of the employees running the institution are dependent upon a consistent occupancy.
First, let me say I totally agree with the premise here--that all parts of a software engineering organization need to be on board with DevOps, buying in to the vision, learning the full stack, taking responsibility.

However, this article does serve as a good example of one of the big problems with most DevOps/SRE evangelism: It's usually coming from the Dev- perspective, rather than the -Ops perspective (or better, a balanced perspective). In particular, this focuses mostly on getting code to users, and speeding up that process. While that's certainly important, it leaves out any discussion of:

* security
* infrastructure design
* instrumentation and monitoring
* planning for failure
* security
* performance evaluation and tuning
* disaster recovery planning
* security
* off-hours on-call responsibilities
* security

Successful DevOps cultures must address these things just as much as they address code feedback loops, time-to-production, rollback strategies, code pipeline automation, etc.
Extension to VSTS [1], sorry. We're working with them on making the extension available to the public. It's possible we could open source it as well; I'll poke around.

[1] https://www.visualstudio.com/en-us/docs/integrate/extensions...
Love your comment! Less hackathons, more open source summits. Build foundations, not garbage to be thrown away.
صور+عيد+الاستقلال+الاردني+2017+صور+عن+عيد+الاستقلال+71+الأردن
I never built anything crazy tech-focused at a hackathon, rather focus on a problem or product idea and flesh it out. This has worked well.

On that note, I would say that using Gimbal beacons to power a walking tour app was something that people responded really well to. From a tech side, I had to write some adapters for ionic that I had never done before. It worked surprisingly well
You're talking about the difference between sysadmins of the 90s and devops of today. The comment you replied to was talking about the difference between product engineering and operations engineering -- he's defending the idea that devops is a specialization of engineering as a whole. It looks to me like you're right, and the comment you replied to is right, and you seem to be agreeing.

He's not saying that chef and puppet are different because they're new; he's saying that using chef and puppet and docker all day long is a different job than debugging CSS and JavaScript or implementing REST api in scala all day long.
Why not just use bitcoin?
FREE Live Webinar “The How  for Empaths to Step into Personal Empowerment”
There's a difference though- if their boss finds out that they did this, in the private sector they'd be rewarded, and in the public sector they'd be fired.
I'm not sure I need to "anticipate or prevent" an event like Mark Zuckerberg deciding to donate to some charity.