skysight-inc/HackerNews huggingface dataset:
Personally I find software engineering to have the worst hiring process of any industry or type of job. Simply put it is just cancerous and detrimental to people who are passionate about computer engineering. I recently had an interview with a company where the recruiter asked me if I would rather use C or C++ even though the company worked on embedded hardware. Why would it matter if when I told them I know both and love both? I’ll obviously use whatever is needed by the company. And this was for a <3 years of experience job.
‘DeFi’ movement promises high interest and no middlemen
The "other guys" are all generating the same information though. And everyone is generating potentially actionable information even when they aren't on an operation, actively practicing tradecraft or in-country on assignment. Eventually intelligence is going to be akin to high frequency trading where small differences in timing, degree of automation and insider information/insights will be deciding factors.
I rented a 2018 Ford Explorer AWD with ~8k miles on it last year. It suffered a persistent "Terrain Management System Fault. Service AdvanceTrac." error while parked, stranding me on a mountain for 2 days. This is apparently a shockingly common problem with Ford vehicles equipped with AdvanceTrac.

It's getting tiresome that any similar issues Tesla encounters are somehow newsworthy... For example fires - according to FEMA, there's ~171,500+ highway car fires per year and if a Tesla ever catches on fire it's big news
Yeah I'm on your side here. This fear of AI medicine creating false positives that overwhelm hospitals and doctors and cause unnecessary and risky surgery is one of those ideas I see floating around comments here and there, and it doesn't seem to be backed in anything tangible. I mean maybe it's a concern, but it also seems like that if it ever happened, we'd adjust for it quickly.
>> Source? I'd assume, in fact, that in most planes that is not the case - superhuman strength is not required to trim.

https://youtu.be/aoNOVlxJmow

Showing the strength required to trim a 737 in certain circumstances.
this is a nice keming machine
If you want an “app,” it makes sense to do a lot of stuff client side — especially if you’re trying to edit or create something in the app (I.e. Google Docs, Gutenberg editor in WordPress, Microsoft office online apps). If you want a landing page for your new startup, static pages on a serverless architecture make way more sense. It really depends what the use case is.

Probably more of the confusion lies in the line between those things — like a CRUD app or a dashboard or management tools. You could do them server-side for better initial performance, but you could also get better interactivity client-side.

I think a lot of new projects go towards the interactivity and “slick UI” side of things which is partially why we see more focus on client-side things these days. Speaking to myself (a full stack dev with a front end focus), we front end devs would really benefit from caring about performance and stability more.
Look into Technical Analysis. Anyone that tells you it doesn't work doesn't know what they are doing.
If you don’t trust your employees to work remotely, you shouldn’t have hired
They have IMAP, you just have to install a program they call the bridge. I use the Linux version that's still in beta and have had no issues with it so far.
Singapore is not chinese dominated. It is 70% people of ethnically chinese decent.
Wait, i thought there was no such things as inteligence genes as inteligence wasn't a genetic trait?
How the Use of Geometric Shapes in Films Helps to Evoke Certain Feelings
I am, myself, still struggling with how un-smart I am. Not stupid, but just so much to learn from people I meet (in real life, or online) yet so little spare time.
Supposedly, it's PU238 underneath, more alpha than gamma danger. Concrete would block alpha radiation pretty well. It's also a heavy metal, so it would be poisonous without the radiation.
That's true. The problem is that most diseases occur in a very small percentage of the population (less than 1/100 or 1/1000), which means that unless the false positive rate is exceedingly small, testing the population as a whole will still produce a bunch of false positives. This is one of the reasons why doctors only order a test if there is a reasonable suspicion that the underlying disease is present.
Whatever newest Samsung tablet is probably supports this through their Dex feature.
They obviously do, as does every mail provider that filters spam, at a bare minimum.
"Technology" is just so broad as to be meaningless. Google and Facebook are advertising companies. Microsoft is a software company. Amazon is part retailer, part cloud hosting company. Netflix is an entertainment company. Apple is a luxury personal computing device manufacturer. They barely even compete with each other except for employees. Why even pretend they are the same type of company?
I can't get my diagrams to look a tenth as good as yours, even with a tablet and undo. Nice job!
Dunno why being downvoted for this. Makes perfect sense. I'm surprised the guy didn't flee earlier -- his bail money (~$15mn) would be a pittance. Pity his poor lieutenant left behind though. Nasty business.
Context and tool switching which can sometimes lower productivity of done often actually does happen. When using JS for both client side and server side it doesn't. From a position of having done both several times in the past years I can tell you it does help
When I started using the internet, I would read pom as porn given the horrible font and terminal I was using. It made for some really awkward misunderstandings.
Great concept, fun game. Wish it was more mobile friendly.
Firstly, get someone to review your resume. You should update your resume at least once a month. At two years of experience should yield good listings for resume. You can often find "resume-review" channels in Slack/Chatrooms associated with programming meetup groups.

At 2 years, you likely have a pretty bad/small professional network. If you want to leverage your network, reach out to people you worked with in university. Reach out to staff and faculty of the program that you had a good relationship with. I found that the system administrator had the most and most interesting connections.

Usually I see new engineers not applying to enough companies. Set a quota of applications to unique companies per week. I found 25 was good, but you may have a different tolerance. "I applied to google 20 times this week" DOES NOT COUNT as 20 applications, it counts as 1. Spend the first half of the week applying to positions that are interesting, and the second half catching up to your quota with whatever you are qualified for.

Remember that being "qualified" does not require 100% skills coverage. At the beginning of your career (and a university degree), you likely only need shallow exposure to ~ 50-75% of the listed skills / technologies. The longer you are in industry, the less overlap is required to land a job. (at 8 years I talked my way onto a job by starting my cover letter with 'I don't have any current overlap, but this is what I know and why I think what your doing is cool')

When you apply in this manner, it can be much harder to find enough companies to apply to. If you are not geographically bound, I strongly suggest watching conference talks that cover technology you are interested in. For every interesting speaker, record who employs them. Check them and similar companies to increase your search area.

Be aware, but less concerned about NDAs. As long as you don't share code, you are unlikely to violate them. Also if they couldn't afford to pay you then they likely cannot hire lawyer.

Practice white-boarding with people at meetups. Come with problems, and be ready to talk your way through solutions.

I have never used leetcode to asses a candidate, and don't see it as helpful. Light-Green github is a much stronger indicator of a good employee than any puzzle competition. Pick an interesting side project. If you have the resources to volunteer for a non-profit this can help keep you out of a sea without guidance/requirements. A good side project can help you control an interview. Add a section to your resume for side projects. You don't need to treat side projects as a full time commitments. These should be time-boxed to a certain number of hours a week.

Finally, always to postmortems. As long as you receive a first phone screen, the application qualifies for a postmortem. You should be changing your strategy, resume, cover-letter, and preparedness after every interview.
It's amazing that your packaged linux binary release runs without issue on my decade old Ubuntu 10.04 box.
> Is there much of that going on?

Most of that are statistical methods in statistic and not ML. We're talking about survival analysis, longitudinal analysis, clinical trial, nonparametric statistic, etc...

From my experiences ML is too dependent on large dataset. Medical data are often high dimensional and small. My thesis papers have leverage two statistician works to make decision trees and ensemble leverage more statistic to handle medical data (high dimensional data). As noted by Dr. Harrell, statistician, ML is much more suited with less noisy data, medical image. Also inference is most more important in the medical field that just prediction.
The best books I've read in the last decade (that I can remember, I've only been keeping reading lists since ~2015) are mostly important because they have contributed to my inspiration and style as a writer.

* The Road - Cormac McCarthy

* Blood Meridian - Cormac McCarthy

* No Country for Old Men - Cormac McCarthy

* On Writing - Stephen King

* 11/22/63 - Stephen King

* The Stand - Stephen King

* Hell's Angels - Hunter S. Thompson

* East of Eden - John Steinbeck

* Slouching Towards Bethlehem - Joan Didion

* In Cold Blood - Truman Capote
Yes, I know Aumasson's a highly respected professional and followed the contests, and am even, like I said, kinda sympathetic to the idea that keeping a big margin for unknown unknowns may make less sense than it once did.

What's the practical play here though? I guess lower-round ChaCha-Poly1305 TLS cipher suites could be worth it for users without hardware AES. I suspect even less-aggressive folks would be comfortable enough with ChaCha12 instead of 20 (e.g. Android already uses it to encrypt storage when there's no AES acceleration).

But trying to move to reduced-round variants of every already-standardized primitive would be a lot of effort to, for most applications, move symmetric crypto from one tiny amount of resource use to another (even if it's much smaller in relative terms!).

I do realize that people care a lot about performance, that there are applications either building on tiny microcontrollers or handling redonkulous data flows, and that any possible bit of flexibility could help someone. Still seems fair to ask: if the broad change in perspective Aumasson wants does happen, is it really going to change much about crypto in the wild soon?
oh, maybe I was wrong? sorry
Bazillionth time it’s posted and discussed. https://hn.algolia.com/?q=type.method.ac Not sure how HN even allows it.
Public knowledge of differential cryptanalysis is younger than 45 years, and was known to NSA 20+ years before its public "discovery" (and known to IBM 15 years before).

Multiple finalists in the AES competition (which selected Rijndael) had significant weaknesses found in the decade since, despite receiving relatively little attention (MARS, Serpent).
Yeah it works out OK with caching. Very easy to track down with the new initiator tab on the in Chrome Dev Tools. They have _initLightBoxItems which removes all the images/gifs from the dom and then readds them which is bound to the scroll event (with a 50ms throttle).
1) Documentation - The Flutter team has done an amazing job supporting their ecosystem with great documentation and examples. I've learned how to write production-level apps with animations, networking, bluetooth, security, and native features like Core Data integration... in EVERY instance it was easier to find the documentation for how to do it with Flutter. They also have a great YouTube channel with daily updates of quick 'how to' videos that are actually quite useful.

2) Tooling. Everything about the installation, update, package import, debugging, UI inspecting, performance monitoring... EVERYTHING about the development lifecycle is better with Flutter and that's because of its TOOLING. Straight out of the box you get debugging and performance monitoring. It couldn't be simpler. You run your app in debug mode and it ASKS you if you want to display a performance monitoring tool. Awesome.

3) "Out of the box" widgets / components. Hands down, Flutter ships with more widgets (components) out of the box. Often when looking for a component in flutter, it was supported "out of the box", whereas React Native required I npm install some 3rd party package, from some developer I'd never heard of, who probably isn't maintaining the project anymore.

4) Performance. I'm a strong advocate for writing your app in native code. I believe you will never get the same performance in a hybrid app, especially if you have complex animations, or huge lists.

With that said... Flutter has completely blown me away. For the first time, I actually can't tell if an app is hybrid if it's a flutter app. The responsiveness is on par with native. The UI / Animations are on par with native. The same simply cannot be said for React Native.
I agree a lot more with the line:

>Remove the safety nets and let the bad actors fail

But even that should be done carefully.

I don't really agree with the title as it really does take time to build up trust and even onboard and establish a relationship with coworkers ... and no amount of interviewing means you know who you hired until they have worked a while.

I was hired as a n00b web dev a while back and recently sat with my boss and the president of the company and we talked about how long it takes until you're sure about someone.

These days I work from home +50% of the time... sometimes a lot more.
Rewrote a non-trivial app from Vue to svelte/sapper. It was a success until we discovered that it turns out Svelte handles errors by freezing instead of letting you show an error page and/or report it to Sentry.
You may also want to try airplayhub with shairport-sync

https://github.com/noelhibbard/node-airplayhub
https://github.com/mikebrady/shairport-sync
Which weaknesses are you referring to? Let's look at them the same way this paper looks at attacks on AES and Blake2.
Why electric cars still don’t live up to the hype
> Singapore may be very modern, but deep down the government is still very authoritarian.

Those two really have no relation to each other, though.
I could refute a 2030 study from the flat earth society with an essay from natural philosophers from ancient Greece, if the first doesn't address the established facts of the second.

A more detailed rebuttal:
https://www.reddit.com/r/Economics/comments/ehsekb/comment/f...
for personal use, maybe? but for business use, you need email security
> Suppose that against all expectations, someone finds a 2^100 attack on AES-128 that is embarrassingly parallel and uses no additional memory. Say you have 10 billion cores, each running at 10 GHz, trying one key per cycle, and you’re aiming for a one-in-a-million success rate: it’d still take you on average more than twelve thousand years of computation to do the ≈ 2^80 required

According to the Bitcoin node on my computer, there have been ≈ 2^92.4 executions of the sha-2 compression function used for Bitcoin so far, exactly the sort of embarrassingly parallel memory-less task that the author speculates about.

So the author's example of a obviously secure attack resistance level has already been exceeded just by bitcoin mining by a factor of thousands.

> For example, “zero-sum distinguishers” [4],arguably the most contrived and meaningless type of attack ever, are about finding a set of input values whose output values sum to zero.

I realize that the author is making fun of his own prior work, but I think he exaggerates the uselessness of such an attack. Finding a set of inputs to a hash function such that the hashes sum to zero (or other specific values) can be directly turned into attacks on cryptographic systems that use those hashes. In particular, attacks like that can lead to total breaks in things like threshold signature protocols and blind signing.

When cryptographic primitives have surprising structured properties there often seems to be a greater fool hiding right around the corner waiting to build a system that almost magically is broken by the structured property. :)
gaps are only bad if you aren't doing anything. If you can confidently defend the gap, or show proof of work then that ends the questions real quick.
Bloomberg keyboards have no competition, but I understand that enormous energies are expended on their design.

I order HPE workstations for the front desk, because they invest in the thermal fluid dynamics and sound energy diffusion of their cases. The default benefits are tangible.

Keyboard quality is a factor more when it is the standard you encounter. High quality consistent keyboard experiences would be significant in broad effect, at least I'm convinced that would be the case.
This ignores a bit of history, at least in the Cold War for Russia and China. Assets were basically use once and burn. Agents could realistically last maybe 12 months in either place and could never return. The youngest would get deployed because they had the cleanest records. Russia mostly knew who the experienced spooks in the consulate were, even using cover.
Agreed that user-written isomorphic JS is probably overrated, but sharing libraries and tooling across client/server is definitely a huge productivity booster for the ecosystem.
I disagree with that. If your code base is small enough, a few redundant lines (idioms) don't matter.

To bring up k again, the language has already done about the maximum amount of abstraction possible. There's really no room for the programmer to make reusable abstractions; any useful ones have already been made. That allows you to do very useful things in very small amounts of code. Picking a random example, here's a complete Sudoku solver in 75 bytes:

http://nsl.com/k/sudoku/aw3.k
I don't agree that get/set/didSet solve actual problems. Languages without property accessors do just fine, but then they don't overload the getting and setting of variables. I would much rather right thing.setField(123), and have setField do whatever actions need to accompany the assignment; than write thing.field = 123, and then have the actions be hidden. What is so f'ing special about x = thing.field and thing.field = x syntax? Why is it so important to stuff additional semantics into that syntax?

As for reference counting: I'm referring to capture lists, and the "unowned self" hack needed with closures. E.g. https://www.raywenderlich.com/966538-arc-and-memory-manageme.... And it gets more complicated with @escaping. I sure don't view all these subtle interactions of closures and ARC to be invisible. This stuff is subtle. Get it wrong and you have leaks.
>By the early 2000s, the agency ceased running certain types of operations [...] The Singaporeans had developed a database that incorporated real-time flight, customs, hotel and taxicab data. If it took too long for a traveler to get from the airport to a hotel in a taxi, the anomaly would trigger an alert in Singaporean security systems

I don't get it. Why don't the agents act normal until after they got to the hotel?
> stole data on nearly 22 million former and current American civil servants

I see this time and again. All the data in a single database where one compromised access can get it all. Data should be compartmentalized, and rate limited.
I also think it is easier to get started with as onboarding is much simpler as the base language is the same. Going from Android to iOS development was much harder than going to JS to backend development with NodeJS
Yes but security requirements are usually inckuded
What is Elixir?
I sort of agree with the first part, though some people actually enjoy having this level of control and flexibility even when they don't absolutely need it.

I find chatty generic code where everything is nailed to the floor ugly, Rust, C++, Swift, Java etc. So I guess it depends on who you ask and their experience.

There is nothing wrong with macros, though I definitely prefer the Common Lisp kind.
The fight of single platform gardens?
https://i.imgflip.com/21aqbc.jpg
I actually don't mind that feature too much. I do appreciate that it clarifies code with even a few arguments of the same type. Although there are other ways to clarify such situations in other languages. The Swift approach does lead to exceptionally verbose code, but that's obviously subjective.

It's the $n syntax that I think is overkill. Do we really need three different ways to name parameters?
On linux all that is still around.

I think meta_l and meta_r are treated the same, but you can do all kinds of craziness with keymaps:

https://wiki.archlinux.org/index.php/Linux_console/Keyboard_...

I wonder if there's a way for apps to look for meta_l in particular

Also one level up, you can set up key bindings for the command line:

https://wiki.archlinux.org/index.php/Readline

It helps to learn the basic emacs keys, as they work most places in macos and linux.

examples would be: ctrl-a beginning of line, ctrl-e: end of line, ctrl-p: previous line, etc...
I bought a VW GTI 20th anniversary (a numbered car) and the transmission broke on my third drive (wouldn’t shift out of third) which was a catastrophic failure. This was about 50 miles deep. Took a few hours to get towed. VW said they would fly in an expert from Germany to diagnose the issue. I opted to get a different car (new number, same model) and that one worked fine. Did I have massive ill will towards VW? no. This was even a numbered car that technically “could not be replaced”. Errors happen.

Statistically, a few hundred thousand model 3s have been delivered and many are well past 6k miles. I think you should wait and hear what Tesla’s reaction is before writing them off.

Things you should consider are:

- they have sold so many cars in the past 2 years that service center growth is struggling to keep up and wait times are long

- Tesla vehicles cannot be serviced easily by third parties so you have no option if Tesla says something you don’t like or wait times are long

Choosing the one broken car out of hundreds of thousands delivered as a reason to not buy one doesn’t make much sense. All manufacturers deliver defective vehicles. Looking at statistics on how many are defective per capita from each manufacturer would be a more reasonable course of action.
“Even the largest estimates of the reduction in the costs associated with nuclear accident risk and waste disposal due to the phase-out are far smaller than 12 billion dollars.“

I doubt this number is correct, as Germany’s per capita health care spending did not significantly increase in that period. (https://www.macrotrends.net/countries/DEU/germany/healthcare...)

Also Germany still has some of the highest life expectancy, although increase slowed/stagnated recently I would question a connection there as other countries are also experiencing that...

Even if, does this account for storage in a secure place for millions of years? I doubt that cost will be higher then...

No insurance company would ever insure nuclear, because it’s simply to expensive in a worst case scenario...

I’m glad Germany is ending nuclear in 2022 for good!
Or more depressingly, maybe they do.
I think it’s a rhetorical exaggeration - hyperbole.