skysight-inc/HackerNews huggingface dataset:
But during the 50 years, you are probably paying in a lot of little ways for the less robust system. In my experience that takes the form of 5 engineers working for two weeks to accomplish something one engineer could do if he/she fully understood the system. Not to mention work done fixing bugs that would never exist in the system with a solid foundation.
Game 'pre-bunks' political misinformation by letting players undermine democracy
https://www.militaryperiscope.com/weapons/naval-minestorpedo...
Tl;dr: real screen shot, but there was a data entry mistake on the website and was fixed after they were aware. Pic got wings.
The pervasive problem I've seen is bad accountability models, where the person who knows how to do something is not the one officially responsible (but ultimately it is because they get fired of course, however they're not responding to higher management about it). This causes huge tension and also miscommunication. Knowing how to do something should at least give you more decision power on how to move forward with a problem, but what ends up happening is extra overhead explaining solutions and options just so a decision is made by someone else that might still not understand and make the wrong decision anyway. This also causes a bottleneck and compounds the problem by making the org. very slow to respond to changes in direction.

Unfortunately I don't see an easy solution, and bad managers tend to be the ones that have the least understanding of the problems, but somehow make the most decisions.
DeepMind Proposes Graph-Theoretic Investigation of Multiplayer Games Landscape
Right. The only thing that can potentially carry over across DCSS runs is a "player ghost", which actually makes the game much harder rather than easier. In any case that's a very small part of the game.
There is a lot of strange stuff around badges in US industrial relations its probably partially an anti union thing.

Bet Amazon is hoping that the Daily Mail or a UK MP doesn't pick this up - not going to help with lobbying against the revenue tax that.
Your understanding is correct. Waterfall (may it die a fiery death) is at an extreme that assumes it's possible to know everything upfront. What most people fail to understand (who like it) is that Waterfall fails to scale. Agile is (almost) at the other extreme.

Waterfall cannot scale beyond either well-understood domains (a web shop that uses RoR could probably apply Waterfall to a new project at this point, with over a decade of experience for each member of the team) or smaller systems (I'd say no bigger than around 100k SLOC of C code, beyond that your system usually becomes too complex) or short time lines (less than 3-6 months, which implies smaller systems). The assumption of complete and proper understanding will bite you on either a larger project or novel domain (novel to you or the world) or a longer timeline.

Agile (I'll take Scrum's 1-2 week cycle + extreme programming) aims to shorten the feedback loop so you know that not only have you built what you thought you built (verification) but also what your customer wanted you to build (validation) on a regular basis.

If you're wrong with Waterfall, you've wasted years. If you're wrong with Agile, you've wasted weeks.

And boy can you be wrong with Waterfall. I joined at the tail end of a 5-year Waterfall project, and they had fucked it up. Over 300 people had worked on it, and it was the wrong damn thing (had half the features needed by the time it shipped, and those half barely worked, and if they worked they were too slow to actually be useful). 1500 years, let's say an average of 75 years per lifetime. That was 20 human lifetimes wasted. And let's not talk about the billions of dollars that went into it. (300 is probably a low estimate, once you get into the subs of the subs of the subcontractors it's hard to get a good tally.)
Your PV would likely still exist but the `mount` command on the pod's cgroup will fail and you'll get into a crashloop with a NotReady (I think).
Well Samsung has quite a bit of top-notch fabrication, in South Korea and elsewhere. Not that what you're suggesting wouldn't still be a good idea.
I don't think anybody disagrees that json is wasteful and costly, it's just that most people see it as the necessary evil to make the data portable and easy to integrate with different SIEMs or databases.

I don't have a ton of experience with unified2, but it's certainly not as simple to bring into something like Elasticsearch compared to JSON where you basically just point fluentd at it and let it do all the work. All of the common log management tools are built for text files, so why not play to their strengths?
I was given a used HP printer with instant ink cartridges installed. When the time to actually make use of it, I had to:

-Connect printer to the internet

-add a credit card to the account the ink came with

-Create a new account since I did not 'own' the account associated with the cartridges in hand

-wait 5 business days for new cartridges that were linked to my account, even though the ones installed were full.

rent seeking in the form of antiquated document acceptance policies
I found something like splitting a string into words not very intuitive...

Just use a couple of accumulators (one for the current word, one for the list of completed words).

Also the classical (recursive) fibonacci function everyone shows has accidental complexity of O(2^n).

That's moving the goalposts. If you want a really fast fibonacci function then the classical iterative algorithm [which is O(n)] is not what you want either. Better to use matrix exponentiation which you can implement nicely with recursion using a divide-and-conquer approach similar to mergesort, giving you fibonacci with time O(log(n)).

I never saw a recursive version of bresenham's line plotting algorithm so this might be a good candidate as well ;)

There's nothing special about Bresenham's line algorithm that would make it particularly challenging to implement with recursion.
More like an FTC complaint.
Second suggestion: be involved in local government. Go to the city council meetings, zoning and variance boards, etc. We all love to complain about the local government not having enough money, but lots of local governments end up wasting money on projects that nobody needs simply because they don't know the communities needs. They can do studies to try and figure it out, but it's a lot better if a significant portion of the community just shows up and tells them.

Yes, it's boring, and of course it can be hard if you have work and what not, but that's civic life for you and it can improve the situation drastically. If you don't want to go to every one, or have work on some days, etc. try to get a few neighbors together and just make sure you send a single representative from your neighborhood to every meeting.

EDIT: also, thank you for asking the question. It made me very happy to see someone thinking about this!
This is rapidly becoming GNOME’s most famous bug. The developers still claim it’s working as intended.
TL;DR: If you have "FIPS-mode" enabled (i.e., "fips=1") on a RHEL 8.2 host, expect to have a bad day when you "yum update" to 8.3!

--

The bug links to KB #5542661 [0] which, unfortunately, isn't "open to the public" (login required). Here's the gist of it:

> Issue

> After upgrading to RHEL 8.3 the system is unable to boot, and we see errors similar to the following:

systemd[1]: Freezing execution

> Root Cause

> This issue is caused when updating to RHEL 8.3 with fapolicyd enabled, as well as FIPS enabled. To ensure that this issue is not seen, you should stop fapolicyd prior to upgrading to RHEL 8.3.

# systemctl stop fapolicyd

> Alternatively, you may lock version to 8.2 until a fix is in place. If you are using RHSM/Satellite the process for that is the following

# subscription-manager release --set=8.2

--

[0]: https://access.redhat.com/solutions/5542661
They are more selective.

Most management classes are really glorified accounting. Staring at budget and spreadsheet trying to cut costs.
The main benefit of peppering is that if your password hashes are compromised (read: stolen) ... they can't be brute-forced. Password hashes such as argon2 make brute-force cracking more expensive, but nothing can help you all that much if the password is "letmein" or something quite high up on the guess list. With well implemented pepper there's just no way to even check one password, never mind brute-forcing.

If you go beyond peppering and also use encryption to protect the whole password database you can get additional benefits like keeping the list of usernames secret.
The Xerox Phaser solid ink printers produced really pretty images. It's a shame they are discontinued. I think you can still buy the ink blocks but they are probably going to phase them out.
There's a split happening right now in the market between Data Scientist and Machine Learning Engineer roles. The former is generally a more soft-skills heavy role with results that are meant to drive human decisions. The later is about building systems that automatically make decisions (ie: recommendation systems, etc.). Data Science is over saturated while ML Engineering is less so.
Coulda sworn it was 2 weeks ago.
I can't remember for sure whether Toolpack's revision control component actually operated with ASTs, but I think it did. Certainly there was a semantic diff and patch. (Toolpack was quite an advanced a Fortran77 engineering tool set from the 1980s.)

I don't know how general they could be, but darcs can have different patch types. However, the only extra one implemented, as far as I know, is token replacement.
I'll add my favorite:

You put the 'b' in subtle.
100 Years on a Dirty Dog: The History of Greyhound (2013)
Do the measurements for PS2/PS3 take into account their specialized hardware? Or the former's VU and the latter's Cell designs aren't really the same sort of thing as the PS1 or PS4.
No one talks about the fact that one of the biggest stoics, Marcus Aurelius was a terrible emperor the roman empire. He settled the goths inside roman land with a forced migration - which didn't turn out too well not too long later. Teleological thinking is built into Stoicism that is the kink in it's armour.

He 'taught' you how to live a good life, in a journal that was 'his personal journal, not meant for publication'. It clearly reads like it was meant to be published and his son turned out to be commodes, easily top 5 worst emporers of all time.
(c) is why I suspicious of Gantt charts – sub-project separation is never this clean !
Interestingly, one place I worked we had a 20% set-aside for technical debt. This resulted in endless arguments with product owners who wanted to categorize bug fixes as technical debt. Sadly, some of the less experienced engineers would take this side in the argument, as well.
Since we're all naming our favorite metaphors, I guess I'll name mine: It's the ol' Dull Axe analogy. There are a lot of variations and even little fables/stories around it, but the gist of it is, don't be the guy who spends all day chopping wood with a dull axe, and who doesn't have time to sharpen the axe because chopping wood takes all day.
It also has the opportunity to ignore knowledge we already have, for example that elections over an internet cannot be both secret and trustworthy. Other countries manage to conduct an election and count the votes within a day or two – using paper ballots.
It’s a process to get there. To reach ecosystem scale people need to buy things. You can spin your own RISC-V chip but to get exactly what you want inexpensively you will need to get lots of others to buy it also.
Writing tests without fixing the lack of understanding first is even worse.

Now the next cycle will have to understand not only the code, but why some test is validating some unused endpoint with data you never thought possible
If the universe is expanding, are we expanding too?
https://m.youtube.com/watch?v=OP8PCkcBZU4

Here is a documentary on wootz produced by al pendray and how they think vanadium from one mine was the key.
Try to ignore that intermediate party and see what happens.
Learning From Quibi
I tend to agree with him. It takes too long to tell that story. In a boardroom meeting type environment people don't have time or the attention span to settle in for story time. You need to be able to illustrate your point in 3 sentences or less.
A simple one, that perhaps doesn't scale (unless you open multiple gyms) is to provide a boxing/MMA/BJJ gym with good coaches.

It's so cliche, but giving teens a physical outlet, where they can begin to understand that consistency leads to results, can sweat together, socialise and build comradery and true confidence will go a long way.

It's simple, and you might only be helping a few teens a year, but it's a good start. I've seen it transform some troubled kids (and grown ups) over the years (drug addicts, and extreme anti-social cases).
Ward talks about this occasionally, but generally there's a frustration among the original agile manifesto authors about how the principles they were after became distorted by the consultant industry that spawned behind the terms.

The financial metaphor above is definitely what Ward meant when coining the phrase technical debt, and it dovetails into agile in the sense one should be making conscious decisions about balancing upfront investment vs uncertain goals. Technical debt can be an opportunity in the sense of doing the learning on the cheap, but you can't run up that debt indefinitely.
I think lopmotr is from my country, and here people have attempted to politicise the poppy in exactly this way, transforming the meaning from a remembrance of the stupidity of war to a glorification. In small numbers Canadians were present at Gallipoli, the battle at the centre of the politicisation to which I believe lopmotr is correctly referrring
It's sad what's become of Hong Kong and the rich Culture over the years.
And that does not even take into account rate of endebtment. Nor the fact that the US has several historical advantages, like the role of the dollar, or the fact that they emerged out of WW II with 'only' 250k dead and their economy and infrastructures intact.
Agree - I came here to say the same thing.

Most engineers have an eye for quality and maintainability which is great, however what they sometimes fail to see is that in a commercial reality, rapidly iterating on features to be first mover advantage is "worth" the piles of dirty dishes incurred, even if it's a huge headache later on maintaining it.

Often it's an existential threat - you either move fast (and often do the 95% solution to ship) or you are gone.

I find quite often engineers without the big picture/reality of the business can often forget that everything is an engineering tradeoff and maybe copy+paste and a bit of spaghetti is your friend today because your firm just expanded.

All of the previous analogies about libraries and dishes need an added layer: if they shut down for a week at the start to re-organise and clean, perhaps they would have gone bankrupt and the stupid solution may have actually been the best one all along.
I like this idea in theory, but... I wonder if the mDL apps can be generic enough that you can implement one and load a credential from any issuer into it, or if it's going to be a single (probably proprietary) app per issuer.

This is something I'd like to be able to use on non-Android and iOS platforms, but that's unlikely if it's not possible for anyone but the issuer to write an mDL app.
Communication, however, is much faster.
Google has a project called Lovefield [1] that is a SQL-like thing on top of IndexedDB. Not exactly SQLite and I'm not sure what its status is now but might be of interest.

[1]: https://github.com/google/lovefield
So who does that leave? Linux, Android and Stadia? And maybe Nintendo? There is about as much not supporting it as are.
> presumably because they don't want webapps competing with their iOS ecosystem

Or because trackers are using indexeddb to bypass Safari's anti-tracking and privacy measures.
JSON is widely used. There is no arguing that. And for small to medium networks, JSON is fine. However, when you are monitoring multiple 100 Gb links and you produce hundreds of GB of logs a day, JSON is the wrong format. Especially if you want to search in a reasonable period of time.

Zeek can output JSON as well (in addition to plaintext). I've done comparisons. Using jq to search zeek JSON is five times slower than using the C++ simdjson library (fastest JSON parser known to humankind). And simdjson is three times slower than bro-cut on the plaintext logs. This may not sound like a lot, but it is extremely important when monitoring multiple 100Gb links and you have 40 GB JSON conn logs every hour and you need queries to run in a reasonable period of time.
I would not consider FTL to be a roguelike because (a) you can't go back to previous levels, you can only explore the current map, and (b) you're forced to progress to the next level on a timer.
No. Most gamers now have a different definition of roguelike vs roguelite. They consider action games to fall into both categories and the distinguishing factor is only that "roguelikes" have no metaprogression.

This is totally different than the understanding among the traditional roguelike community (and the author) in which a roguelite is not a turn/grid based game, but a roguelike is. Unfortunately, these words are now rather meaningless unless you know who you're speaking to.
This starts from the premise that you have to do it alone. Cynicism and isolation make it impossible to change things, but if you get together with 5 neighbors I'm sure you'll be able to move the 500lbs. Start a co-op, or a neighborhood civic group and you won't have to go it alone.
I'm in industry, and sorry, I think most of industry is far too stupid for large-scale feedback to be a good idea.

Please stick to your ivory towers unless you are really sure of who you are talking to.
YOU PUT THE I IN TEAM

I probably screwed that up. Oops, I just made that up.
" For additional protection, mDL apps will have the option of both requiring user authentication before releasing data and then immediately placing the phone in lockdown mode, to ensure that if the verifier takes the device they cannot easily get information from it."

That's an interesting feature. I wonder if it's going to result in pressure from law enforcement to unlock the device.
As a site owner that is somehow not my problem. It's not my fault that you have a shitty ISP. I can understand and support that argument.

I do TLS only for my stuff however.
Thanks! It makes my day that this could make someone laugh!
Yes, siding with you on this.

Biggest fault of the Gtk/GNOME ecosystem these days is a small bunch of atrociously toxic people centering around RedHat shouting "Nobody besides me works on this, and that! So sit tightly, and shut up with your feedback!," while completely forgetting that it was them who scared off, and trolled out most normal people out of the GNOME community, including some of the best devs they had.
Horizontal totalitarianism in life and literature
Sometimes encouragement and positivity help too, not every answer has to have specifics and detailed plans :)
By definition, most companies can't afford the top talent.

Your advice boils down to "pay people more", which, I mean, might seem like it works in the individual case, but it's clear why most won't be able to follow it.
Company forced to change name that could be used to hack websites
The "how computers work" part nowadays involves understanding things like cache efficiency, and quite possibly even knowing whether it's more efficient [1] to compute something locally or transmit it over the network.

These things aren't static, and you can't just have e.g. an understanding of theoretical algorithmic efficiency and call it a day, even if you couple that with an understanding of e.g. CPU tech at time t.

Various levels of abstraction of course fuzzy things up further. You'd then have to understand not only how things work at the low level, but also how your particular layers of abstractions affect things.

With today's tech stacks, that becomes nontrivial real fast.

With that said, yeah, writing at least superficially efficient code isn't really much harder than writing grossly inefficient code if you have a good base understanding.

[1] In this case, in terms of energy efficiency, which is even harder to judge without specific knowledge. Time efficiency is easier to test.
The Rise of the ‘Monologue’ Interview
The takeaways (for me) were that:
1) a small number of high-status parents with different priorities than the broader community will often (without malice) influence a school's administration such that the community's more fundamental priorities get lost,
2) political action to enable racial integration of public schools has been a symbolic goal in NYC for generations, but there's been a repeated lack of follow-through due to ... lack of courage and commitment.
Awesome resource.

A quick plug and reminder that a learning roadmap for data engineering that is detailed with resources is available here: https://awesomedataengineering.com

For those who wish to focus on data engineering.
You put the RUSTED in DISTRUSTED.

You put the PYHRRIC in EMPIRICALLY.

You put the ALLAH in CLIMATOLOGIST.

You put the ICING in ENTICING.

You put the SCENT in DISINCENTIVE.

It includes names though, which are almost never interesting:

You put the REECE in RECENTLY.
That's why I'm using Nemo as file manager in Ubuntu. Unfortunately the files dialog is still Nautilus but it's okish there, given I don't have to do much when picking a file or deciding where to save it.
They really didn't. The Soviet space program operated with around a third of the US Space program (about one 200th of the USSR economy in 1970), or the equivalent of, give or take, 30 billion 2020 US dollars, or around 10 times the budget of SpaceX, notwithstanding technological price deflation.

With 1970s tech and only ten times the budget, the Soviet space program certainly innovated a lot more than SpaceX did, in all fields, from computer science to basic physics, to metallurgy, to jet engines, and built more ambitious missions.
We also insist that we're different instead of examining the lessons learned from related disciplines. Perhaps the closest to software engineering is systems engineering. They have a huge body of work that closely parallels what we've done in software engineering, along with many ideas on how to model and understand both our systems and our approaches to development and organization.

But as an industry, we seem to want to make our own path, rather than learn from others.
The primary purpose of the tool to is to surface what a software application is good at by bench-marking the features & functionality across the whole category(s) that the app in question belongs to.

Most of my time goes into normalizing feature set across a category of software so that you can do apples-to-apples comparison. Then I am quantifying how well that feature is implemented within the product, hopefully extrapolate that to the whole category, essentially a ranking system for the features. To do that, I need to collect and normalize those feature sets.

W.r.t. treemap, I am trying different visualization techniques and seems like treemap is pretty good in answering these questions quickly:

1. Which product is a dominant product in a particular category?

2. Which feature dominates a product/category?

After doing a few user interviews people honestly don't care about the ranking or a better framework to search for software. They mostly care about how can software evaluation and procurement can be less painful.

Thanks for the comment and sharing the link of eoc. That's pretty much what I am trying to do for apps.

I hope to extend this to libraries/packages which can be very helpful in knowing what are the strengths of a particular library or package in a snapshot.
It's written in rust, in the off chance that is important to anyone on this site.