skysight-inc/HackerNews huggingface dataset:
Location: Berlin, Germany

Remote: Yes

Willing to relocate: No

Technologies: Go, Perl, Terraform, Kubernetes, Docker, helm, Postgres, Redis, Aerospike

Résumé/CV: send me an Email

Email: kvzcanvas@gmail.com

I am a SRE/Developer with more than 10 years of experience. I have migrated several companies to the cloud and mainly to Kubernetes. I have done fully automated CI/CD. I am very cost conscious. As a programmer I have developed several services in Go and in the past in Perl for high traffic products. I am looking for a new company that I can join and enjoy. Please only contact from companies directly.
http://snaponair.com/ apparently got hacked :\
The style and rhythm of this article is superb. I wish they did a movie about it.
That's not what I implied. What's important is the possibility of something better having a shot at success. One could argue that a browser based on Chromium rather than Webkit, could work better for their needs on iOS. Unfortunately that can't happen on iOS.

And here's a real world example: even if v8 was a better runtime for React Native it still wouldn't be allowed into iOS.
Then you are missing a negation in the thread subject line.
But Finder isn’t lying here: it shows the ability to read or write the file, but from Finder’s perspective. Just because you can do that doesn’t mean any old app on your machine can by default. This is literally the manifestation of Apple plugging holes in the UNIX permissions model. You can complain all you want about “protected” directories being stupid, but arguing that Finder should show you whether an arbitrary app can access a file is just inane.
How long before she gets raided and her copy of the dataset and research gets taken away

... all the while as the government forgets that it’s all available on the internet ️
I wish Apple could multitask, but they haven’t in years.
To be fair, I was more curious about the mechanisms in place to avoid it. A google search just had advice on stocking up supplies (for most).

I'd really like to believe this - and I hope it is the case.

But geez, we let folks die of starvation on the best of days. We let folks eat literal trash. We let folks have cases of malnutrition, too, without fixing things. The only thing I think that saves folks in the states is that during a lockdown, it is the government's responsibility to do stuff - but I'm not really convinced so many governments have stuff in place.
It's very simple to migrate even really old Subversion repos to git. If they claim it is an insurmountable logistical challenge, then they don't know what they are talking about.

Yes, there is diminishing value in old commits, but they are far from worthless! Never ever destroy the commit history. Doing that is imho, a cardinal sin.
Rust is interesting, so I decided to include it in a 3 language prototyping project. I wanted to experience how it is to code for these languages, compared to the outcome. The project was dead simple, read 2 files concurrently and match lines by id's. Data was a bit unstructured, some lines would go unmatched, some would be duplicates, and report on that while deallocating memory for processing large filesizes.

Ruby: Quick fun building the classes and methods. A bit trial and error on dynamic errors. Processing was 40x slower than golang implementation though, so felt a bit discouraging after the fact. But was fun language to prototype OO in! Nice for quick'n dirty projects.

Golang: I didn't find need for OO or interfaces, so simplified for processing code mostly. The language helped in this regard, as it is quite imperative-driven. Golang was the fastest language to develop in, and showed Ruby version to be a bit over-engineered.

Rust: Never coded in Rust before, I searched SO for most relevant code examples and patched it up from several examples. I didn't go into the deeper end of things or optimize anything, but instead spent 90% of the time writing naive processing code while battling the compiler. If I'd been proficient, perhaps no battle, but this required the longest dev time and processing was noticably slower than Go, though not by a factor.

From this short anecdotal experience: Ruby for quick'n dirty fun or OO modelling. Golang for prototyping and initial versions. Rust for where you know you need safe parallellism and special optimizations. Right tool for the job!
The technical term for this is "water splitting" and there are about 20000 papers published on the topic per year. So at least the ones providing money to academia are convinced that it is a problem worth solving. FWIW, the professor I knew working in this field and also owning a startup in the field recently switched from a hydrogen powered car to battery power.
However as others noted, hydrogen is great to be converted to liquid fuel, because you won't be flying transatlantic on battery power any time soon.
Australian University checking in. Use your budget, or get next year’s budget cut
I mean, I follow all tenets of gun safety even when I'm handling a nail gun, or a pressure washer, or anything else with a trigger that may or may not seriously injure someone if I accidentally pull the trigger while it's pointed in one's direction (including in my own direction). Taking a nail to the face ain't pleasant.

That is to say, whether or not you do something safely has no bearing on whether or not something is designed for killing.
Their OSes have been able to since 2001, but evidently their engineering team is much less adept ;)
>"Thank you for the details, but I must still be missing something. FB shadow profiles aren't valuable to anyone unless they also know who you are, which is my point."

Shadow profiles are valuable to FB as it provides data on the interests of a FB user's real life friends. I don't doubt there's categories along the lines of "has 2 or more friends who regularly frequent wine bars in West London" or something similar.
Getting a Side Project Idea – My Story
At least once a month, when modifying some critical piece of code - git blame is the easiest way to find reasons for non-obvious lines of code.

BTW: if you sometimes move code around between two git repos (from multirepo to monorepo for example), I wrote a script to move a subfolder between the two and keep history:

https://github.com/jakub-g/git-move-folder-between-repos-kee...
EU Bank begins stakeholder engagement process on Climate Bank Roadmap 2021-2025
See example 3 in link above
Hello. That's a point to make data easy to read. Datasource is https://www.worldtradingdata.com

About P/E it could be great, but that requires to find datasource of financial reports. But, I think I know where I can get it.
Our migration journey from AWS to Google Cloud – Part 1
May I suggest to have some sample datasets in the demo. Am a bit confused as to what the tool can do as I don't mingle data frequently
Those countries tend to already have better economic safety nets / welfare systems and mental health systems, thus mitigating the reasons why someone might be driven to engage in violent crime (let alone use a gun in said engagement) in the first place.

That is: you're arguing that wet streets cause rain.
Organizational inertia cannot allow this switch to fixing issues. That just don't happen at once because now a lot of people work in an environment rewarding them to only new feature development. This can be changed by replacing the whole tech organization motivation culture. Better at once.
Thought about it, but for external security audit purposes we aren’t allowed to rewrite history.
Lobbyist bought tropical land from Biden's brother
Ok, so the thousands people at the train station it must be a one off situation, my mistake.
It's quite obvious that generalizations are always wrong, but you know our people as I do. I believe the patterns should be quite evident by now. Obviously there are outliers that do not share the common patterns among Italians too.
Finder isn't some third-party tool released before this kernel change. Why should it not know about those plugged holes?
Alibaba launch a Flutter plugin which enables hybrid integration of Flutter
If migrating all old commits is such a challenge (it shouldn't be), then a workaround could be to keep your SVN online but in read only mode. If your git blame shows "Initial migration commit" you just move over to blame in the old svn.
How should it present this information?
can anyone truly ever gitlog bigass?
Very rarely past a few weeks.

But on the rare occasions I need it, I often really need it. Especially because code that has survived sufficiently unchanged for that long ofte has done so for important reasons.

The amortized value per commit for really old code is likely low, but you get them 'for free' because you want to do them to have them for recent code, and the overall value of having them for older code to the codebase as a whole can be significant.

I'd say the SVN history challenge is an excuse - firstly there are tools that can do it.

Alternatively you can easily enough keep the SVN repo around for those rare occasions people really need to dig.
I think as a society, we shouldn't require people to be passionate about their jobs to put food on the table. Jobs should be just jobs. The days when the internet was a beacon of light are long gone, today expecting "passion" about CRUD apps or ad-tech is just fake corporate mentality.
Oh that's a cool tool. I'll try to remember it next time.
I have no experience with MDMA but this seems like an extreme position. If you have sex with someone without their consent it's considered rape, so this line of thought would imply that everyone who's had sex with a person on MDMA is a rapist.

In the eyes of the law people can usually give consent while under the influence of drugs and alcohol (significant exceptions do apply, with the most common one being incapacitation).
That domain isn't resolving.
Undocumented CPU behavior: analyzing undocumented opcodes on Intel x86-64 (2018) [pdf]
Also really impressed by your contributions history on GitHub. From the graph, you’ve literally worked every days (including Saturday and Sunday) in the last 12 months - except two days in Feb.

If this is true, you deserve some holiday!
The dead people do not give a fuck about the economy.
Nah I'm saying in the web application itself you shouldn't handle it. Python async/await or NodeJS.

You have to deal with deadlocks and race condition stuff in operations to the DB or any shared muteable state. That is obvious, but that is an external issue because web developers deal with shared muteable state as an external service that lives outside of python or nodejs code.

I mean if you count the transaction string or orm as part of dealing with locks within your web framework, then sure, I guess you're right? The locks on the DB are DB primitives though and not part of the web framework of language so I would argue that it's different. I guess reordering updates to happen on primitives in the same order could count as a web application change, but that's kind of weak as you're not really addressing the point:

NodeJS doesn't have locks, because you don't need locks in NodeJS and a deadlock should not occur unless you deliberately induce it.

The overall argument is the framework of NodeJS and python async/await is not designed for that kind of shared muteable state hence the lack of locks in nodejs std.

Also, never did I say a web developer doesn't need to understand or deal with concurrency. This is not true and I never claimed otherwise.

Additionally thank you for being respectful. (Take note
eropple)
Yeah, that was a frustrating day for me. I went from running all of my IM through my IRC client, to being forced in to a combination of my IRC client and the slack desktop native app, to eventually giving up on slack altogether as it was heavy and finicky, providing nothing more (for me) than any simple IM client.

I firmly believe we're just in a bad place on the whole in terms of IM/voip systems for personal use and org use. Nothing is really good enough. The only ones that live up to expectations are mumble and IRC - the absolute no-nonsense of them leaves expectations low and exceeds them. Had slack taken a more open route and stopped being so org focused it had the potential to do really well (in the "good ecosystem" sense, not in the financial sense as clearly they're doing fine.)

Nothing bridges the gap between personal social use, informal org use (gaming, loose projects), and actual org use. How is it that mumble and teamspeak etc. are still far superior voip clients to literally all other offerings, including the well funded and supposedly mature discord which should be excelling here. Only thing mumble/ts can't do is replace voip telco systems, which in fairness nothing else does either.

Slack can't do voip for shit, discord can't even do notifications, irc can only manage offline message history if you're highly tech savvy or pay for it, whatsapp requires a phone with an active connecion and is clumbsy for ephemeral groups (telegram is fairly similar), gitter doesn't even come in to the picture, matrix has the shittiest public servers in the history of technology, xmpp is esoteric gobbeldygook.

The whole space is a mess.
The last time I moved a large codebase from git to svn the surprising thing for me was that a git clone was _smaller_ even though it had all of the history, than svn was holding only truncated history. Everything runs faster, and the tooling is better. They will feel like they traded their gocart for a Ferrari.
Trump's mismanagement helped fuel coronavirus crisis
If the OP renamed to “HighwayToTheDangerzone”, would this help?
I think there's some indirect psychological value that shouldn't be underestimated.

People have a tendency to comment out unused code "in case they still need it". Or not delete unused stuff, because who knows what.

I have the feeling that I'm much more inclined to just delete a bunch of code lines that "I might still need in some situation" if I know there's version control. Because even if it's unlikely, "I can get it back if I want to" is a good feeling.

I think this leads to less cluttered code overall.

Also something that came to mind: When the shellshock vuln was discovered in bash noone really knew when and how it got introduced, because it was so old (literally decades) and there was no version control in that time. I don't think anyone suspects any malpractice with shellshock, but think about it: If you find a really strange bug that looks like a backdoor, and it's 10 or 20 years old. Wouldn't you want to know who committed that code?
You can, but you don't have to. Each route is built separately but it can all be a single monolithic app underneath.
You have not yet downloaded “HighwayToTheDangerzone”. You are still ok.
How about: not from Finder's point of view? There is no such thing as Finder's point of view. It must show info from the currently logged in user's point of view.
Fortunately it sounds like the tokens used by emacs-slack are supported. If not then I am going to start pressing for my company to leave Slack. Life is too short to use a browser UI instead of Emacs.
Someone from the research group says they've been funded by Intel for 2 years, and have also published papers involving 10 Intel vulnerabilities during that time.

https://twitter.com/lavados/status/1236088594584014848?s=19
Maybe the old guys didn't think there was a good reason to switch from SVN to git, if SVN had been working for them. It sounds like switching just because git became more popular.

Of course if you're young, it's no big deal since you haven't been using SVN for decades, and what's the big deal with learning something new? But when you've been around the block a few times, sometimes there's needs to be a better reason than the new and shiny.
This would sound more credible if they had the terminology right (vulnerability vs exploit).
Yes it is an important point. Postgresql does not stop deadlocks or race conditions from happening. You deal with those in Postgresql.

But this isn't the topic of the conversation is it? The topic is locks and deadlocks in Python asyncio and NodeJS so ultimately irrelevant to your initial example of the amateur diamond dependency injection where normally no deadlock should be occuring regardless.
What's the advantage of doing this over just making an experiment branch? A branch would be easier to find than a reverted commit somewhere in the mainline branch.
The entire point is that the user permissions are not accurate for an arbitrary app because of sandboxing. This is like yelling at readelf for "deceiving you" because the binary is slid around by layout randomization to somewhere else.
SVN? What's that? All you young whippersnappers keep harping on the new and shiny.

Real men use cvs.

(I kid.)
Depends on your project/business.

On my current job, I very rarely go back to see when something was changed, because the business requirements are very straight forward. A change needs to happen, and the implications are clear. Also, no one really documents discussions systematically, commit messages are rather short etc. Not much value can be extracted.

On my last job, a system with over 15 years of history, my team was often puzzled with the existing codebase and the seemingly weird things it did. "Who wants this?", "Is there a usecase for this?" and "Do any of our customers actually expect this functionality if we remove this?" was a frequent question.

Then we'd check the commit history and get the 3-4 tickets involved in the functionality's history. Long discussions and back and forth with the client, explanations why the functionality was being added etc.

This archaeology was so frequently fruitful that all the team engaged in it.
This kind of makes me wonder why PDFs can even act maliciously in the first place. Why does it have the ability to do these things?
Fluid Art String Pulling Chains Acrylic Pouring – Art Beginners Technique
It reads like a deliberate attack on MAPS and a truckload of more general FUD about using certain drugs.
It might be mere one-sided excessive attention to one case, with one therapist, in one clinical trial (failing to see the big picture, which is attempting to find a good therapy for PTSD) but the impression of dishonest bias and of some hidden agenda (competitors?) is quite strong.
The problem they are highlighting is child abuse. Child abuse is indeed a horrible thing. It's also a very hard thing to combat because it largely happens when a trusted adult abuses a child and mostly doesn't document it for posterity or share it on the internet. The victims face the double whammy of shame and social pressure not to accuse the victimizer.

Attacking the perverts sharing pictures is worthy but does almost nothing to prevent child abuse. The best case scenario is you expose a small portion of perverts and thus prevent idiots from trusting their kids with them.

Unfortunately attacking messaging services will do little to combat perverts sharing pictures as they can trivially switch to using slightly better technology.

The effect of multiplicative. Imagine you start with 1% of victimizers sharing media online. Imagine that you catch 1/10 of 1% of them before the rest figure out centralized sharing is not the best idea. You are now stuck with permanent downsides and will catch few additional people.

0.01 * 0.001 = 0.00001

The logical conclusion is that this isn't a very great way to combat child abuse.
Yes, while maintaining code which other people wrote who are no longer around I often have to figure out what they might have tried to do. Being able to see how code looked before someone rewrote it can often give you an idea what it's about. Even better if the people even used good commit messages which explain why they fixed something and why they did it the way they did it.

Sometimes code only makes sense if you can see it's evolution.

Also knowing who wrote it you can ask those people sometimes about it.
Yeah but not every job is like that.
The scary part is the WHO mission were adamant that they failed to find a large number of asymptomatic/mild cases in the population at large, and they tested 300.000 people. I can't get this to match up with my other hunches, so I might be very wrong on this.
Because internet architecture is based around transit capacity, not usage. You buy capacity like 10gbit/sec lines to interconnect with and Cloudflare has enough bandwidth to easily support their free customers and upsell on other features.

Remember they are also a security service with DDOS protection and that requires high bandwidth anyway. Other CDNs don't charge for bandwidth but rather for bytes-used, which is just more profitable, especially if you don't have a lot of other features to charge for.

I'm surprised that more CDNs don't try to compete with CF on this but apparently that's just how they want to operate.
I think it's just that Adobe wanted to add more features, even ones that have no place in the PDF format.
This is a very confusing title for this site. I thought someone had reimplemented the drum machine hydrogen in rust
Yes, the share sheet, right where I'd expect to find the install option. Of course! This must be why Apple's designers get paid the big bucks!
Everybody knows python, few people know Scala. Isn't that enough of a reason?
Not quite - it's "take away", not "take a way" as used in the article.
This comment is enlightened.
That doesn't sound right to me.

You are saying loud and clear you assess how good an engineer is fit for a role literally judging part of personal life based on your own (100% unbiased, right?) inference process.
Depending on use case, anything from weekly to very occasionally, but in all these cases it's invaluable. E.g., selectively reverting commits that are known to have caused bugs, checking something whilst preparing release notes, working out how we did X in the past, etc.

> At my current company they place a huge value on that history, so much so that they haven't transitioned from SVN to git solely because of the logistical challenge of migrating 30 years of commits.

I assume they've actually tried to do it? I ask because there's a bunch of tooling and at least one reasonably well understood process for achieving this and preserving history so it's pretty low investment to try it out and see if it works.

Here's Atlassian's version, for example:

https://www.atlassian.com/git/tutorials/migrating-overview

(I will grant you that figuring out how to navigate to the next page of the current tutorial at the bottom of the page is unnecessarily complex.)

I suspect with 30 years of history it's going to take a very long time to do the conversion (days to weeks), but you can set it off and leave it running. Once you have your initial migrate done you can set up syncing to git, and then you need to pick a time when everyone will stop committing to svn, allow a sync and verification window of a few days, and then everyone starts using git.

It gets more complex with multiple projects ongoing, and scheduling around releases, but making this happen is more a matter of will than battling complexity.
> the real problem is that Americans are just a violent bloodthirsty lot.

More like "Americans are more subject (relative to, say, Europeans) to the economic and mental health hardships that typically beget violent crime".

That is, I'm far less motivated to rob a store at gunpoint if I can actually feed myself and my family through legitimate means. I'm far less motivated to kill someone in anger if I have access to mental health resources that can help me address that anger less destructively. I'm far less motivated to join a gang if my life - and that of my family - doesn't depend on me doing so (or more precisely, if that gang is no longer able to convince me of that).

Guns are tools. Taking away the tool does not take away the desire to commit crime. I'd expect Hacker News, of all places, to understand the importance of root cause analysis.
I never lose or misplace my keys anymore now that I have keyless entry/keyless start, they go days without leaving my purse. It's really a massive improvement in my life, one I didn't know I needed until I had.