mmaia

> The engineer in question was instructed to download malware masquerading as an "assignment" during a second interview, that deployed malicious code with "obfuscation techniques" evading detection.

Quick feedback: a lot of the job descriptions are Markdown that gets displayed as plain-text. If you rendered them it would be a lot more readable.

On the backend side, Cal Henderson published the details of Flickr's architecture in "Building Scalable Web Sites". It was a reference at the time, the "Designing Data-Intensive Applications" of another generation.

Interesting concept.

I've been doing the same kind of drill with ChatGPT. The disadvantage is the interface, but I can direct it to focus on what I'm learning or want to reinforce, etc.

> If your work isn't ready for users to try out, please don't do a Show HN. Once it's ready, come back and do it then. Don't post landing pages or fundraisers.

https://news.ycombinator.com/showhn.html

That's a cool tool.

FYI: There's a typo in the URL you posted, an extra `n` :)

Exactly. The post screams about all the issues I've seen in multiple companies between DS/MLE and SE/DevOps.

A suggestion for addition:

> Plausible Analytics is a standard Elixir/Phoenix application backed by a PostgreSQL database for general data and a Clickhouse database for stats.

https://github.com/plausible/analytics

A characteristic of the field since the beginning. Reading What Computers Can't Do in college (early 2000s) was an important contrast for me.

> A great misunderstanding accounts for public confusion about thinking machines, a misunderstanding perpetrated by the unrealistic claims researchers in AI have been making, claims that thinking machines are already here, or at any rate, just around the corner.

> Dreyfus' last paper detailed the ongoing history of the "first step fallacy", where AI researchers tend to wildly extrapolate initial success as promising, perhaps even guaranteeing, wild future successes.

https://en.wikipedia.org/wiki/Hubert_Dreyfus's_views_on_arti...

When asked to provide real life examples from the paper conclusion:

Workplace Example

Scenario: An employee has a colleague who tends to send aggressive emails if they don’t receive updates on time.

Healthy Active Avoidance: The employee learns, “If I send a quick status update every morning, I avoid the stress of hostile emails.” They adopt this as a habit.

Depressive Active Avoidance Deficit: A person with depressive symptoms may take longer to make this connection or fail to act even after realizing it. They know sending updates might help, but initiating the behavior feels too effortful or pointless. As a result, they keep receiving stressful emails, reinforcing the feeling of helplessness.

Published: October 8, 2014

More recent work indexed in Google Scholar: https://scholar.google.com/citations?hl=en&user=TVozLNoAAAAJ...