skysight-inc/HackerNews huggingface dataset:
Their hypothesis is that PR is a good alternative to NN

No, they are not correct, because they have not compared their model to state of the art NNs. That's exactly why I insist they use standard, canonical datasets, such as ImageNet: because it's easy to find well-known state of the art, and compare the models. Google Scholar, last 4 years: "Letter Recognition Dataset": 98 results, "MNIST": 10,000 results, "Imagenet": 18,000 results.

They aren't doing a paper on NN vs PR for image classification

If they include image classification results, and claim their model compares favorably to NNs, then yes, their paper is, at least in part, on NN vs PR for image classification. I only commented on image classification results because that's the field I'm familiar with. I suspect other results they presented would also be unconvincing to people working in those areas.

Will more research arise from this?

If they want more research to arise from that, then they should have made sure their results are convincing, or at least promising. As presented in the paper, they are not.
Reductio ad absurdum. I shoved a code base into version control and set up a super simple but safe deployment strategy. No fancy anything. It put off non critical development for a day and made development faster because I could make sure my code worked locally and not just on the live site.

Some companies value hyper-compliance, some companies value employees that speak up in cases of negligence. You have the freedom to choose your own preferences.

Furthermore, it IS possible to respectfully communicate your concerns and position without being a heroic jackass. My manager on that project and I were on good terms when I left and he served as a recommendation for my next job. The situation wasn't nearly as exaggerated as you're making it.
How Low Can Venezuelan Oil Production Go?
I expect most ads are <30s, most songs are >2m.
When I was younger Grand Rapids was seen as a dull place. Downtown closed at 5 pm and there wasn't much fun to be had for a young adult.

While the area is still pretty conservative that has changed mightily in the last forty years. The city now has a lively downtown and all those breweries have made the place a magnet for young people from the surrounding areas.

The 'lake effect' does mean they get a lot more snow than the eastern part of the state.

https://en.wikipedia.org/wiki/Lake-effect_snow
Do you argue more with those above or below you?
"we stalk people. period"
Without md5 tagging but with a reasonably configured web server, the browser gets an eTag in the response headers to the first request to load that cover image, and sends it in the headers to the second request and gets a 304 Not Modified response with an empty body. The size of the cover image is completely moot when comparing a proper Hugo config vs a proper asset pipeline config.
Patents on mp3 and RSA didn’t prevent them from being used everywhere. I guess a patent on FFT (which, by the way, was considered at the time, according to Wikipedia) wouldn’t have stopped its adoption either.

Also, IMO, a formula, which tells you what to compute, is essentially different from an algorithm, which tells you how. FFT would be patentable because it is non-obvious, even when given the formula for doing a Fourier transform.

It still might be non-patentable on other grounds, such as the fact that Gauss apparently described it in 1805 (http://www.cis.rit.edu/class/simg716/Gauss_History_FFT.pdf), two years before Fourier published his work on what now is known as Fourier series.
Something I vaguely remember from years ago in an interview: Rather like this comment [0] I just read on another submission, it's along the lines of: Don't listen to what people say, throw everything at the wall and see what sticks.

Two things that stuck crazy-well were the touchscreen on the NDS in 2004 and the motion controls on the Wii in 2006. In either case, they were the first to market with both ideas, but before that people would've said the idea was crazy.

Two other examples that didn't stick at all, off the top of my head: Virtual Boy and the Power Glove.

(Small aside: It's long enough ago that plenty of people seem to have forgotten, but the touchscreen on the NDS was a crazy idea at the time because that was nearly 3 years before the iPhone was released, let alone smartphones becoming common/popular. The got-to-have phone at the time was the Motorola RAZR.)

[0] https://news.ycombinator.com/item?id=17387468
What I find interesting are the people who are absolutely fanatical about disputing Zimbardo's conclusions. It's as if it's very important to them personally to be able to classify potential perpetrators of atrocities into two simplistic categories, People Who Do Stuff Like That and People Who, Somehow, Magically, Don't. Any experiments that might reveal human nature as the ultimate culprit are considered politically incorrect and unacceptable to perform.

Yes, the Stanford Prison Experiment was a dumpster fire. But so was the Nazi regime. When you want to study dumpster fires, you could do worse than to start a small-scale dumpster fire of your own and see how things progress.
> The advantage for AMD is that they've built a single design: the Zeppelin die. RyZen is simply one Zeppelin. Threadripper is two Zeppelins. And EPYC is four Zeppelins.

While a popular meme, this is not actually true. Epyc is actually a totally different die, stepping B2 vs the B1 die used in Ryzen+TR.

https://en.wikichip.org/wiki/amd/ryzen_7/1800x

https://en.wikichip.org/wiki/amd/epyc/7601

The 2700X is actually on a different die as well, and Raven Ridge on another. There will probably be another die for Banded Kestrel, if AMD ever gets around to releasing that. Presumably, their embedded SOC products are their own die as well.

So, about 5 dies per generation, across AMD's lineup (Epyc, Ryzen, APU, Atom, and embedded SOC). They're using about half as many dies as Intel is - still a significant difference, but far from the "one die for the whole lineup!" meme.

The big difference is that they're serving the whole server market with one small die, vs the three that Intel uses.

Of course, a small die isn't all roses either - both mfrs limit you to 8 dies per system, so right now with an 8-core die AMD systems are limited to 64-core systems (dual-socket Epyc) versus the 224-core systems that you can do with octo-socket 28-core Xeons. But, not everybody needs a million-dollar octo-socket system either.

Once AMD takes a node advantage that advantage will be diminished somewhat, but Intel's 10nm woes are a whole different story ;)
Lots of crazy complicated Outlook and gmail filters that block sales people, spam, and so on.

I wish I could do the same for my phone. Robocalls are out of control now. At least 4 a day, sometimes 20+.
If your referring to security updates in the docker images rather than Kubernetes itself, then not really. The rebuild should be automated for you, so it's as simple as triggering a Jenkins master build.

Kubernetes handles the deployment for you, bringing down the old pods and upping the new ones without any connection loss. It makes it a lot simpler to deploy these updates.
I'm not sure if SoC is breaking apart actually. I think chipbuilders are figuring out that its more efficient to combine some dies together at the package level.

Consider that EPYC is basically a miniturized multi-socket design. Infinity Fabric is really AMD's new protocol built on top of HyperTransport (multi-socket protocol from the past). Before, AMD used to support 8-sockets. But today, AMD stitches 4-chips together and only supports 2-sockets.

From a software perspective (ie: NUMA), EPYC x2 sockets looks like an 8-socket chip of old. In effect, AMD has miniturized the 4x-socket setup in the form of EPYC. And it has also miniturized the 2x socket setup in the form of Threadripper.

----------------------

These Threadripper / EPYC chips have the same downsides as all old 2x, 4x, and 8x NUMA designs of the past. High latency and poor communications between cores.

The thing is: the modern environment is a highly virtualized, highly independent set of systems. Running 8x NUMA efficiently today is as simple as spinning up 8x VMs, one for each NUMA node.

IIRC, people are finding that Intel's 28-core design is far more effective in say... unified Database performance. Intel's design has a true L3 cache which can be used by all 28-cores, while AMD's L3 cache is split between each die. 4x 8MB caches cannot function as a singular cache in a large-scale database application.

But there's enough situations (ie: VMs, multitasking, render farms) where AMD's NUMA + Infinity Fabric is good enough. And with prices anywhere from 1/4th to 1/2 the cost of Intel, AMD's chips these days are certainly worth considering.
I hates endless essays made to describe simple ideas.

Yes u need to have times of separation from the
'Leaded' group to enable the introspection which lead to rational thoughtful and more appropriatz decision making.

This is very clear in the military: a lot of brotherhoodship and fun in soldiers group, very little in officers. And both dont mix.
That helps, thanks, though I hear this kind of thing is going away in GTK4. The developers are actively hostile to retaining any functionality unused by the defaults, regardless of how impactful that functionality may be for the minority using them.

I simply don't comprehend how one reconciles that attitude with accessibility needs, when accessibility is inherently giving a fuck about the minority.

It might be a simple matter of scarcity in developer resources. I presume most of the people bitching about GTK/GNOME in forums like these are actually capable of hacking on the project but don't, myself included. So maybe we should just be more appreciative of what we do have, there's nothing to refund after all.
Agree all the large powerful tech companies need to be scrutinized. Given Zucherberg had to testify at Congress recently it seems reasonable and expected that it would result in a little more focus on them.
You need data to build technologies of the future and continue improvement of living standards. We (Western countries) should make it as easy as possible to collect and share it between businesses, and embrace it culturally if we want to stay relevant in AI-powered future.
I disagree. For use as a tool, for some use-cases, if it "works as advertised," all we really need to know is whether it's efficient enough for our purposes.

One (horrible) use for something like this is in a framework like Rails, where there's a cultural acceptance of making method and field names by pluralising and conjugating etc.

In Rails if your `House` model has a one-to-many relationship with your `Mouse` model, a `house` object probably automatically gets a `.mice` field. That sort of thing can be done with extensive rule sets, or it can be done with a black-box library.

Of course it's a horrible use-case, and you'll probably always need to deal with ambiguity and context, but for that sort of thing the implementation details aren't nearly as relevant as "the dimensions of the black box" -- how quickly does it run, how quickly does it start up, how much memory does it use, how good at its job is it, and which languages does/can it be made to support?
Great project! The hot topics tags/link are not working.
Principles of Effective Research (2004)
It's also funny, I am going to outright not even care if someone has a patent
Forget about Clean Code, Let’s Embrace Compassionate Code
I relocated to Germany but never studied German before and at work we all speak only English, so my German knowledge lacks a lot of words, though the grammar is OK. However here one has to deal with a huge number of letters, and there are always unknown words and phrases. So I have created a tool based on tesseract OCR, Qt and offline dictionaries of dict.cc to read letters and all kind of contracts. I also used www.lingvolive.com at the beginning but then the API changed and now I don't have time to update it. Nevertheless it saved me tons of hours, now I can read a tricky letter within 5 minutes instead of an hour.
There are multiple companies, and none of them have anywhere near to a monopoly share. Not only that, many companies will develop this capability in house, and the margins for this service start getting excessive, those companies will have a good incentive to offer it externally.

So yes, these services won't cheap, but that'll be due mostly to intrinsic costs, not monopoly rents.
Two things:

1. Automated indoor gardening. I used a raspberry pi hooked up to x10 devices as a way to monitor the temperature of my garden, and run the watering and light cycles. This meant I only had to worry about my garden maybe an hour a week when changing out the nutrients and reservoirs. This saved a huge amount of time, let me go on vacation for long periods of time without having to worry about things, and saved me from forgetfulness. It allowed for me to enjoy my garden a lot more, and look for real issues, like bugs/pests/nutrient deficiencies. Getting an automated process also made each cycle more reproducible.

https://github.com/cbanek/garden-squid

2. Automated billpay. This changed my life. By not having to worry about missing bills, it really just took them completely off my radar. Downside: If there was a problem with a bill, I might not notice right away, but in general, there was so little that wasn't actually my fault that it didn't matter. Fidelity has a great automated bill pay system that is free to use, and will send out checks and do e-bills for most utility / credit card companies.
The weapon system was very interesting to me. New weapons were incredibly rewarding because they were so fragile. You develop interesting relationships with your inventory cycle. It really is a survival game dressed up as a cartoon, that little joyful Link, so full of hope, repeatedly beat down and made to suffer by an uncaring world.
They really didn't. Most websites that publish articles in any form still have RSS feeds, and there are plenty of feed readers out there that work.
Funny. This is why orgs like Bain and E&Y make tons of money. They give you the answer, and if things don't work out, you have a scapegoat.
I think I used Pokora's utility for adding water to Halo 2 levels. I remember when it came out and it seemed like all of the new custom Halo 2 levels people were making on halomods.com had customized water immediately.
Is there a recommended way to handle database migrations in kubernetes? Is there a best practice or a tool for that?
I know this was ages ago, but I've created a daily dashboard for today's games using this API: http://worldcupgames.today/
That’s really cool, but from an actual life utility perspective isn’t it draining of mental bandwidth to always have this communication channel open? I could see this being useful for some Jack Bauer type activities but otherwise I want to give notifs less access to me, not more. Again - very cool, not trying to detract.
I hit a roadblock with trying to read Stata files into Pandas a few months ago. I discovered that not all versions of Stata file formats are supported by Pandas in Python. R has much better support for Stata files.

With the help of Feather, which was written over Arrow, I was able to read Stata files into R, write the dataframe out to Feather and read the Feather file into a Pandas dataframe with no manipulation.

Without Feather I would have had to resort to using CSVs as intermediate files which would have meant additional pre-processing in R and post-processing in Pandas. Feather and Arrow saved me a bunch of time on this.

I'm looking forward to using Arrow more broadly but, even with just Feather, Wes and Hadley have vastly simplified the effort of interfacing between R and Python/Pandas. I'm also very excited to see what else comes out of their partnership at Ursa Labs: https://ursalabs.org
FWIW, I achieved something like live reloading in Jekyll using an additional config file.

_config_local.yml:

html_refresh: true
html_refresh_rate: 5

Then, I appended the config via:

jekyll serve --config _config.yml,_config_local.yml --force-polling

And then did a check in my header include:

{% if site.html_refresh %}
<meta http-equiv="refresh" content="{{ site.html_refresh_rate }}">
{% endif %}

You can find a working example in my blog's repo[1].

[1]: https://github.com/woodruffw/blog
A question from a fellow diabetic hacker - what prompted your switch to the faster acting insulin and how does it compare wrt basal rates? I became aware of it not too long ago, currently using Novorapid on my pump. Have brought it up once and the endocrinologists were apprehensive of switching.

Forgetting to bolus and accounting for the dawn phenoemenon are pretty challenging in a backpackers routine. :-)
I don't have any problem with them calling it horrific, horrible, or whatever. People are entitled to their opinions, and have the right to state them. Although Twitter also has the right to delete them.

But anyway, what I'm taking issue with is the argument that archaeologists et alia don't have the right to be nonjudgmental. Also that being nonjudgmental isn't the norm for archaeology as a profession.

I don't expect your average Twitter user to know that. But at least, they should understand the concept, if explained well enough. After all, it's also the norm for physicians, attorneys, and psychologists. Even judges, who are supposed to interpret law objectively.

Edit: Oops. Forgot key "don't" and "isn't".
I mean, it's pretty clear given tweets given to us today by the US president that he'd LIKE to use it in an authoritarian manner. He literally said he wants to remove all courts and judges from the immigration process and have ICE be able to exercise deportation options unilaterally and with 0 tolerance or oversight.

So right now: yeah it's probably an authoritarian system. But in the long term, we need a better understand of the legal and social implications of facial recognition before we can really trust governments at scale to use the technology within a framework that preserves our values.

Right now, it's best to deny them access to it.
I only recently discovered Mastodon and tried it out. It works surprisingly well - and opens doors to interesting subcultures. I really wish this project well and hope it helps drive the trend to a more decentralized web again.
Yeah I'm aware of that, but I still didn't find it that great. Unfortunately it's been a few years so I don't remember exactly why.
It's the most popular sentiment but still nobody is deleting facebook, hmmm?
I am seeing a huge influx of people into tech just for the money, and personally I'm quite disgusted by that (although I get their motivations behind that behaviour).

Could this relatively huge burnout figure be a direct result of people entering tech just for the money despite not being passionate in it, and realizing being ears deep in code is just not for everyone (esp. every personality type)?

On the other hand, the kind of people that like to code tend to despise the modern management style of agile standup scrum master slack jira jockeying, so this clearly is a more complex issue.
I think one of the powerful things that something like containers offer is a happy path that's also the easy path path and it meshes well with the principles you need for a scalable or micro-service infrastructure. With "real" servers you can build infrastructure that operates and scales in similar ways but the happy path isn't as clear or enforced. Containers make you think about persistence and state as being distinct from your compute at/near the beginning. You're punished for not doing so fairly early, even on your local machine. Your AWS instance can go away but months down the line you're not wondering what you did wrong, you're wondering what Amazon or your ops team did wrong. So the happy path that was easier to deviate from before becomes much harder with containers.

It's also easier and faster to update a container image than servers. With something like Kubernetes you can even do it in stages. Yes, you still have to keep the underlying servers updated but they just need to run containers. No testing dependencies and prerequisites. And that decoupling of the app runtime makes updating the servers themselves easier. You can create a new machine image and replace outdated ones trivially.
Can't help thinking Nix and NixOps.
if we want to stay relevant in AI-powered future.

I have two arguments here.

1. The kind of data Facebook collects has nothing to do with AI, but advertising.

2. Even it mattered for AI, why do you think staying relevant in AI-powered future is more important than our privacy?
> Nevertheless, the mobile device continuously takes location and acceleration sensor readings (e.g., once every 5 minutes) and sends the location and acceleration data to server 112.

What is "server 112"? Is this some internet-ism I don't know about?
I don't like to use SQL engine because I don't understand how they work, I never really know if my query will be O(1), O(log(n)), O(n), etc, or what kind of algorithm will optimize my query.

Who really does understand how a SQL engine work? Don't you usually require to understand how something work before starting using it? Which SQL analyst or DB architect really knows about the internals of a SQL engine? Do they know about basic data structures? Advanced data structures? Backtracking?

That's why I tend to avoid systematically using a SQL engine unless the data schema is very very simple, and manage and filter the data case by case in code. SQL is good for archiving and storing data, and work as an intermediary, but I don't think it should drive how a software works. Databases can be very complex, and unfortunately, since developers like to make things complicated, it becomes hairy.

I think SQL was designed when RAM was scarce and expensive, so to speed up data access, it has to be properly indexed with a database engine. I really wonder who, today, have data that cannot fit in RAM, apart from big actors.

I tend to advocate for simple designs and avoid complexity as most as I can, so I might biased, but many languages already offers things like sets, maps, multimaps, etc. Tailoring data structures might yield good results too.

Databases still scare me.
Yes. You gotta trust the provider.
Perceptions are probably influenced heavily by your own usage and places for consumption. I'm also in the camp of "AAC is very rare, if at all"...

Considering also that YouTube uses WebM, which very explicitly is only Vorbis or Opus for audio, "basically all online video distribution" must exclude the web's most popular video distribution site...
Kalamazoo isn't doing bad these days, either. As someone who grew up in Michigan (Saginaw), I would love to move to either, but IT jobs I'm qualified for seem to be rather thin on the ground.
Branch Based Versioning
The time span of human civilization is too small to witness the emergence and extinction of intelligent civilization elsewhere. Universe is really very vast in terms of distance and time.
I don’t think that’s an accurate characterization of the criticism. The Milgram study, and its numerous replications, have pretty conclusively shown that most folks will do something they know is wrong if a perceived authority instructs them to. That’s not really in dispute.

The allegation is that Zimbardo orchestrated his project in order to produce a more dramatic narrative of spontaneous cruelty that wasn’t scientifically justified. It would be (it is alleged) as if Milgram had passed participants a note under the table that said, “FYI the subject is an actor— just go along with it, we’re trying to prove a point.”

Whether or not the Milgram results are valid, that certainly wouldn’t be a good demonstration of them.
VC don’t sign NDA do they?
An approach to software versioning that does away with manual versioning, unnecessary check-ins or dependency on environmental variables. It is mainly of use inside agile project teams set up to continuously deliver value (for example releasing on a weekly basis). It contrasts this approach with snapshot publishing in the Snapshot Anti-Pattern section.