skysight-inc/HackerNews huggingface dataset:
> Humans simply don't need that, which must be some indication that what we're doing isn't quite right.

Not really. DNNs are much simpler and need to be much more specialized towards specific tasks than the human brain. They're more like a nematode that was optimized by evolution for millions of years to tell cats and dogs apart because it preferentially infects dogs. It's the only thing it does. It does it via some shortcuts and it won't be able to learn chess without a radical redesign.

Not to mention that primate brains take some time to get bootstrapped. A toddler has to be fed visual input for many months before they can be left unsupervised for reasonable amounts of time. And have you seen what those "optical illusion" things do? It's a miracle that those humans can self-navigate at all considering those failure modes!
The biggest threat facing humanity is 1000+ years away?
In a functional scrum team everyone on the team should be empowered to advocate this. In turn the product owner should be receptive to technical improvement because it is in the interest ultimately of the overall project success.

Yep, I fail to understand the problem with this. A product owner who doesn't respond to pressure for technical quality is a bad product owner – end of story.
They will figure that they need process if they want consistent quality. Really.

Besides, smart people still have egos, personal ambitions not lined up with project, biases, weaknesses, personal antipaties and make mistakes. Good process with accountability and responsibility makes wonder with all those.
> Input Manager for macOS: done.

Funny you should say that, it literally just took me hours to create a new kb layout (my keyboard has a broken P key that I wanted to substitute). It was a mess of error messages and "keyboard already existing" problems. Ugh.
For me Scrum is like training wheels for agile. It’s restrictive and hinders progress at any real speed, but gives you the framework to start producing stuff in an agile way. Once you out grow it there are plenty of better methodologies, include the proper agile way which is that the structure of your product management is also a component to be iterated. It’s difficult to jump straight in at that point though.

Just a shame that most teams’ processes crystallise around Scrum. Working with self described Scrum masters is painful as they’ve built themselves into a box they can’t see out of.
I don't consider censorship as a standard tenent of my developer career, and supporting such actions directly goes against my principles, this is why I wouldn't do such a thing, as I'd rather change jobs than fight that.

The sole concept of blocking part of the world from accessing your service because you don't want (or can't) let them access what you have on them, or remove said data, is pretty weird per se.
Overly collecting data without consent sure is a problem, and excluding citizens under protection laws made to avoid abuse of said data can only considered as either censorship or law-bypsas.
The teams I've been on that just 'jive' usually start with some process framework but then evolve to just work well together.

There are strong philosophies in Scrum and Agile that should be kept as guidelines. The key is being agile (lower case 'a') so you can adapt to changing priorities. Continuous Integration/Continuous Delivery go a long way towards empowering developers.

Two ways to tackle technical debt in projects:

1. Tech debt sprint. If scrum master and product owner can't get onboard then they need to realize somewhere in the near future, a feature they want will either break things or take forever.

2. Break up tech debt into small efforts someone can do in short time boxes. Even do feature flags or something to make slower progress towards a goal rather than tech debt sitting in a backlog for months.

An example of a guideline is estimation with planning poker. We completely ditched estimation activities. The estimates were usually off and not good predictors of completion. The team has a cadence of ticket completion and the 'sizes' of the tickets vary some but you don't need to waste time estimating. Developers (humans) are horrible at estimating. Having a good PM/PO set expectations with the business helps.
Uyuni: Forking Spacewalk with Salt and Containers
What I meant specifically is that Italy elected a government that promised - and wanted to implement - a currency parallel to the Euro, and then the Italian president exploited a loophole (effectively claiming there was no agreement between the parties that made up the government) to avoid putting this government in power. He made it no secret that this is exactly why he did that.

So Italians wanted a parallel non-EU-controlled currency in Italy and elected a government to do that, and this was denied, by a pro-EU politician. This was already a do-over election of sorts so that makes it even more of a farce.

Several BIG costs have to be carried by the Italians as a result. First, the actual monetary cost already paid: 1.5% on 6.5 billion euros, or about 100 million euros, effectively charged to them by the ECB. This will keep growing. Second is the fact that there is no government in charge, and the legitimacy of the "experts" (picked -surprise !- by pro-EU parties) that will be in charge until the next election (July or September) is heavily in question, and that government's only loyalty is to the Italian president who got kicked out by the electorate.

Of course, several EU commissioners have called out for punishment of Italy for these election results, and although Oettinger has now apologized, it shows you just what kind of people they are.

All of that, just to protect the EU. Again.
> Those that use facial recognition reported false positive rates of >95%.... Mass surveillance with facial recognition is nowhere near levels where it can be used unsupervised.

Is this deep neural networks with the latest technologies?

While yes, deep learning isn't going to solve everything, we'll probably see significant changes in the products available as this technology discovered the past few years makes into the real world.

Most scanners that do OCR and most forms of facial recognition isn't using deep neural networks with transfer learning, YET.

This is not to say that discoveries will continue, winter is probably coming :)
it seems my information was outdated...

https://news.ycombinator.com/item?id=17186124
If you do so, don't hesitate to contact me so I can also advertise it, and send the information to the service's owner, a friend of mine.
A human might not be able to, but a computer can. Isn't the explicit reason research shifted to using Go the fact that you can't just number crunch your way through it?
Shameless plug, but if you’re interested in this sort of thing, I published a proof of concept docker container that makes packet analysis with scapy very easy. [0] The trick is to leverage iptables nfqueue to filter packets you’re interested in, and have scapy listen to the queue.

[0] https://github.com/milesrichardson/docker-nfqueue-scapy
> Average U.S. wedding cost $30k in 2014

Averages are mostly useless for this kind of things where some people can go crazy on prices. What is the median? Are other deciles available to check?

But I think the most important would be with the cost of a wedding / current capital owned and cost of wedding / revenues ratios.
These types of replies always strike me as No True Scotsman fallacies, which are rife in Agile & Scrum.

“No true Scrum team would do X.”

“No functional team would disempower people...”

At some point though, Agile & Scrum cannot be propped up like that.

When the same failures happen again and again all across the industry, it’s time to admit that the tool facilitates that failure.

The tool (Agile & Scrum) is the correlate here. Somehow it’s always showing up co-located with these problems, but we’re never honest enough to step back and admit maybe, sometimes, with enough evidence, correlation can be related to causation in this case.
You pretty much too the words out of my mouth - I was talking with someone about this just yesterday. I suspect that when interfacing with 3rd parties that are over-burdened with inefficient processes it means that he/they have to stoop to their level and dumb down their production line to work with said party.
Awesome software development process that is not about communication: testing by testers. Also code and documentation review. Also, keeping tasks in tracker and having version controll. Etc.
We use Chef (Ruby). Cookbook version solving has been a repeatedly painful experience, occasionally never finding a solution. When this happens, you get to manually dig around and find the culprit.
Holy shit 30k? Hopefully the average is just skewed up by rich people. If middle class people are plunking down that much, it would be insane
I think that's exactly why they called it a "baby".
The cost of context switching is near zero. No need for expensive TLB flushes, for instance. No need for paged memory whose overhead sometimes accounts for up to 50% of program runtimes. Better isolation properties, since you can sandbox individual objects instead of whole processes.
> But if I understand correctly, out-of-the-box, Zig's `union` doesn't get a tag type, right? That's what I meant by Rust's `enum` being safer: you can use it safely in Zig, but you have to actually request safety, because that's not the default behavior.

Sure. I think that's more an effect of the choice of keyword defaults here. A straight union is very uncommon and is typically solely for C interoperability.

> And the "more powerful" is about the fact that a Rust enum can actually carry data, while it doesn't seem to be the case with Zig.

A tagged union can store data as in Rust. See the examples in the documentation [1]. Admittedly Rust's pattern matching is nicer to work with here.

To summarise the concepts:

- `enum` is a straight enumeration with no payload. The backing tag type can be specified (e.g. enum(u2)).

- `union` is an unchecked sum type, similar to a c union without a tag field.

- `union(TagType)` is a sum type with a tag field, analagous to a Rust enum . A `union(enum)` is simply shorthand to infer the underlying TagType.

> So, it sounds like deallocations are not checked by default, right?

If referring to if objects are guaranteed to be deallocated when out of scope then no, this isn't checked. There are a few active issues regarding some improvements to resource management but it probably won't result in any automatic RAII-like functionality. This is a manual step using defer right now.

[1] https://ziglang.org/documentation/master/#union
Has cruise control been improved so that it takes into accounts reduced visibility when going over hills?
A main component of the paradox is time, but this paper solve that. Life existed from the beginning, but only now has become complex enough.

So, we don't see or hear artificial signs in other galaxies because light is from the times when there was not complex life in the universe.

Now, we only have to solve why we don't see or hear artificial signs in our galaxy. But the problem is not so perplexing because we are talking about one or two million years.

If, for instance, a big part of the galaxy is bad for complex life (after all, we are far away from the center and that could be relevant), Fermi's paradox is solved.
Have bootcamps succeeded in dumping talented developers on market?
Is there any study regarding the effect of bootcamps on developer wage.
I am wondering if dumping lots of developers using Bootcamps in the market can suppress developer wage. (which are already quite high)

Large funds who own parallel businesses in the tech sector (developers are the biggest cost for them) can keep investing into bootcamps even at a loss to suppress overall developer wage.

There is simply no point in relying on universities to meet this demand for talented developers. The developers coming out of universities already have a large debt, so they'll require high wages to cope which again keeps the developer wage high. Often, universities do not have aligned interest to set you up for a good developer career.

So, my grand plan is that major US funds should join hands and open many bootcamps (with affordable costs), dump a large amount of talent on market. The US already is one of the most expensive markets for developers so there is no risk of talent leaving for greener pastures as those pastures simply do not yet exist.

Since rent account for a major portion of wages, there is a possibility of shorting real estate market. Rents will go down.

This will also solve the immigration issue by increasing local supply of affordable developers.

This can work if it's done in the market with high demand (high wage) for developers.
I’m a consultant and I have a client on an arrangement like this, where I don’t really do much actual work but just give advice. I structured it as an up front retainer that I bill hourly against as I’m needed.

I wouldn’t do it without a retainer because the extra friction of an hour here and there is not really worth it unless I can get a nontrivial amount of cash up front, which helps balance my cash flow while working on other longer term projects.
The private companies which are killing the whales are just a proxy of the Japanese government, which are officially allowed by the government. They aren't allowed by the government to hunt as much as they want to maximize the benefits. To build a sustainable business in such regulated field, of course it is important to obey the laws and also care for the environment.

If the killings of 122 pregnant whales severely affect the environment and if there is a clear evidence to support such claim, the company should stop killing them. But if the company is obeying the laws and it's just an emotional thing, I consider it some other people's business.
> Despite working in a a Scrum team, I recognise literally nothing of the problems that are described.

Same. This process takes work, requires buy in by all levels of the company and needs to be fully understood including its error cases. It takes time and requires course correct and attention. Its not easy but done right it is effective.
Bleh, no it isn't.

I am 100% in agreement with the author on the thesis: deep learning is overhyped and people project too much.

But the content of the post is in itself not enough to advocate for this position. It is guilty of the same sins: projection and following social noises.

The point about increasing compute power however, I found rather strong. New advances came at a high compute cost. Although it could be said that research often advances like that: new methods are found and then made efficient and (more) economical.

A much stronger rebuttal of the hype would have been based on the technical limitations of deep learning.
Please can you explain what you mean by manually braking? At its core, ABS releases the brakes for a wheel when it detects that wheel skidding. Braking is still manual until the locking point. Having ABS enables a driver to slam the brakes and know that won't result in a skid, where a vehicle without ABS may lock the wheels and skid.

The effect when ABS kicks in when braking on snow or ice is for the wheels to maintain slightly (or more) better traction. Sometimes this is undesirable - you'll brake in a shorter distance on loose snow if you lock the wheels - but you generally keep better steering control.
Why would you let yourself get so stuck in the minutia of SCRUM? Use the parts you need and not the parts that work against you.

The value usually listed first in the agile manifesto is "Individuals and interactions over processes and tools".
Not surprising: https://www.cnbc.com/2018/05/30/electric-vehicles-will-grow-...

>The number of electric vehicles on the road around the world will hit 125 million by 2030, the International Energy Agency forecasts.
I recently presented my tool HTTPanalyzer at RIPE76.
It's a C tool I developed in 2016 available at Github for processing HTTP traffic up to 10Gbps from PCAP files or straight from the interface. I recommend the branch "revisited", much better coded in my opinion. Of course, it's limited to the first packet of the request and first packet of the response. It's aimed to aggregated statistics like response codes, user agents, response time (immediate one, not full load of the resource) etc.
More info here: https://carlosvega.github.io/httpDissector/

Only HTTP traffic, you can process decrypted HTTPS traffic (like some devices do, i.e. IXIA network devices) which is transformed into HTTP traffic. Regarding HTTPS or HTTP2 etc. The current approach is to correlate the application information from log events against traffic measurements.
Naive comment here, but wouldn't it be highly unlikely to encounter such a planet given your low relative velocity to it?
Those who made you that feeback are wrong. Package managers suck (especially npm). Do what's comfortable for you not the others.

Customers don't care about git and such things. I don't use git because I find it useless for the projects I'm working on.
Buy a yellow rubber duck. Describe to it where you've gotten stuck.
7 Top Time Management Fundamentals for Expert Medics
Nothing says "Marry me! Marry someone who wastes lots of your shared money!" like a diamond.
This mentality "lets add a daemon to run in background 24/7" to provide some service thats sits mostly unused is unacceptable.
Its not only gnome developers, its widespread in open-source. The competitive edge of Linux is reduced quite a bit when there is enough bloatware running around by default.
> Isn't it amazing (and scary) how brainwashed people are about the "value" of diamonds, even though they're not actually worth that much?

It seems to me that the same strategy is curently used in the crypto ecosystem.
If I might ask, why was this flagged? It was last discussed in 2016 [0], and though it needs a [2006] tag, it is otherwise a really valid and interesting post.

[0]: https://news.ycombinator.com/item?id=12944464
I would say that estimation isn't so much about predicting completion as understanding hidden assumptions in the team.

We sometimes find that engineers have entirely different concepts of how a particular feature or change needs to be implemented. Estimation – planning poker in particular – is a great way to reveal that and start exploring what the reasons are.
I got my fiancee a great looking engagement ring from a Chinese Etsy store. Cost including shipping was a little bit above $100.
Can you give an example of a way in which we’ve gotten worse?
Sorry, I went to bed!

The original google report was discussed here a few weeks ago:

https://news.ycombinator.com/item?id=16813766
I wondered the same thing.
Putting NPM on a pedestal of badness is unfair. NuGet deserves to be right up there next to it, but also holding the bouquet and wearing the tiara and waving to the crowd
> Sure. I think that's more an effect of the choice of keyword defaults here. A straight union is very uncommon and is typically solely for C interoperability.

Fair enough. That's why Rust also has a `union` keyword, which is always `unsafe`.

> A tagged union can store data as in Rust. See the examples in the documentation [1]. Admittedly Rust's pattern matching is nicer to work with here.

Ah, right, it could be any struct instead of being a bool or integer. I missed that.

> If referring to if objects are guaranteed to be deallocated when out of scope then no, this isn't checked.

I was wondering about that and double-deallocations.

> There are a few active issues regarding some improvements to resource management but it probably won't result in any automatic RAII-like functionality.

Out of curiosity, what kind of improvements?
We very well might be in a deep-learning 'bubble' and the end of a cycle... but I don't think this time around it's really the end for a long-while, but more likely a pivot point.

The biggest minds everywhere are working on AI solutions, and there's also a lot in medical/science going on to map brains and if we can merge neuroscience with computer science we might have more luck with AI in the future...

So we could have a draught for a year or two, but there will be more research, and more breakthroughs. This won't be like the AI winters of the past where it lay dormant for 10+ years, I don't think.
'(MULTIBALLLL!)'

Reminds me of a Budweiser advert shown in the UK a long time ago:

https://www.youtube.com/watch?v=sjI-qh37xf0
I would say it's a dangerous road. Child or not!

Imagine being challenged at work... in a sales team, for example. Make a sale, get to do a lucky dip. Say two people make an equivalent sale, one wins and the other doesn't. I would personally feel less motivated if I lost.

I wonder if you did it to kids, they would learn to weigh up whether doing any given task was worth some arbitrarily set lost/win.

It's the difference between learning that "washing a car is worth $10 of my time because it will takes x hours and the cost of soap is y and so on" vs "washing a car is 50/50 worth nothing or $10".
How does a diamond represent "fuck you money" if everyone has them?
It’s often impossible to talk productively about this because of all the No True Scotsman fallacies uses to defend Scrum, e.g.:

“No true Scrum master would do X.”

“A product owner who doesn’t Z is just a bad product owner. Not Scrum’s fault.”

“If X is disempowering people then X is not Scrum.”

These are not valid defenses, and they just distract us from the elephant in the room, which is Scrum’s constant presence everywhere these problems occur.

At some point if the tool cannot do its basic job without requiring perfectly scrupulous product managers and “real” Scrum masters, etc., then it’s Scrum’s fault, and we need to think of less prescriptive, less inflexible models that cannot be so easily subverted politically to merely pay lip service to technical quality, while bastardizing reasonable principles to serve quarterly JIRA datamining expeditions and Dilbert-style management practices.
A poor organization will find out how to fail in many processes. The problems are much deeper than at the scrum level.
Ok, got it. Apparently, espeed was using an unusual definition of "memory safety", which made their comment a bit odd :)
I think the article confuses what Scrum is and what some (probably most) companies make out of it. I agree that there are scary things happening in practice and I've seen a lot of scrumBut and scrumAnd that really endangers a lot of projects.

My experience is that this is often caused by a lack of understanding of the methodology and how it can be applied and integrated into existing structures.

Also existing structures need to be integrated with Scrum to make it work. That is, they need to be transformed to match agile workflows.

The latter is not easy. Especially not in larger companies. I am not surprised that most do not even try to tackle this.
Well, sure it stumbles into this fallacy but so does the roll out of any process involving humans that has a set of normative criteria with a given critique in hand. I always feel this fallacy is a weak response as norms can always be applied well or less well. This is what makes them norms.

I've seen it work very well. I've seen it work badly. Where it has worked badly it was because the process was not fully understood, badly implemented and not iterated upon. For reasons I can detail on reflection. These are explicable and fixable reasons that given the right company ecosystem and desire to honestly reflect upon them and fix them could have been fixed. A bad process tout court would never see highly effective result in some cases.
I filled it out for you.
I disagree. Even if there are a number of big customers for mass surveillance, self driving cars fundamentally changes the platform of our economy for everyone.
So go is about recreating the wheel, over and over again
To be fair, "buy and hold" is probably one of the best investment advice there is.
झोळ म्हारी “Banadi” की #Latest Haryanvi Songs Haryanvi 2018