skysight-inc/HackerNews huggingface dataset:
That's all is not a change of "the methods, management style and ethical boundaries", is it? For example, to change it to a strict enforcement of certain ethical boundaries.

As you said it also applies to Google, and nobody to my knowledge ever claimed that all departments and all people in them a e.v.i.l., not even criticis of all sorts of things Google did and does.
NYT spam?

I'll bite. What makes a (generally considered) reputable news outlet such as the NYT reporting on relatively major news spam?
Did you look at the screenshot? The small, greyed-out “Sponsored” text is quite small and everything else is identical to a real listing.

Really is a dark pattern. Especially given that the purpose of the list is to avoid unwanted/unneeded items. The user is already doing the work of directing purchases to your platform already.

Not cool.
How Postgres is more than a relational database: Extensions
Learn how to animate your own short-story with this step-by-step guide
Interesting. There's definitely a benefit, though:

MCMLXXIX -vs- MDCCCCLXXVIIII
I was hired for this exact reason at my last company and tasked with rewriting it while maintaining bit-for-bit identical output.

The company itself was in biotech (cancer diagnostics) and was relatively new, spun off from a rather well known research lab. They quickly realized that their system was incapable of scaling (or being maintained properly...) to the needs of a business.

The code itself was written primarily by one man. He was quite bright, but not really a software engineer by trade. Usual stuff; no source control, mish-mash of technologies, spaghetti code, and home grown algorithms and hardware to solve well understood problems with available solutions. New management wanted me to rewrite everything in C# (against my protests. Not because I dislike C#, only because the code dealt primarily with image analysis and hardware control/robotics.)

I began by doing exactly as you proposed; I reverse engineered every bit of code. I took extensive notes (it was hard to follow) and walked through each step from sample prep to image acquisition to analysis to result. I started writing each sub-system only after I understood how everything pieced together.

The real bitch of it was that the original developer relied on automating ImageJ for nearly all of the image analysis. As my original requirement was to not alter the results in any way, I literally rewrote large swaths of ImageJ in C#. Bugs and all.

Well, turns out ImageJ (Java) is compiled with /strictfp. C#/.NET does not support this, so my floating point results were oh so close, but not identical. This was initially a problem for management... until the CEO was replaced, along with my boss, and the new team thought the entire project was a dumb waste of money and had me build a new system from the ground up.

That system was released (successfully) early this year. I began work on it nearly five years ago now, with many detours along the way. I now work elsewhere.
I inherited a project based on more than 10,000 lines of poorly commented, undocumented 8088 assembly code used on a shopping-cart attached radio+LCD panel product. It wasn't that bad an experience except the product took code updates over the air and the guy decided to use his own block checking code instead of a CRC or even a checksum on the 256 byte blocks.

The custom algorithm was a suboptimal choice as it was prone to passing badly corrupted blocks as correct. Worse, the first stage bootloader was in masked ROM so a true fix wasn't possible, only workarounds.
Where the culture is all centered around respect.
You should look at the Auvi-Q product made by kaleo. If you have insurance (even if it is not covered at all) or you are unable to afford insurance, kaleo will send your the product for free. End of story. My insurance does not pay a a cent, and I don't either. That's several thousands of dollars given away for free to each patient over just a few years.

kaleo was founded by twin brothers with food allergies and they've worked from day one to improve patient quality of life, unlike other pharmaceutical companies. Sadly, the media has recently criticized them, paradoxically, for their "high prices" that are paid only by the huge insurance plans with the deepest pockets--they do not receive donations, after all, and this strategy helps make their products free for both the underprivileged and middle classes.

https://www.auvi-q.com/getting-auvi-q/
Or even macro
If you tie a user to a uuid separately from where you are logging the transactions, you can nullify the existing UUID link to the given user and be in full compliance with GDPR.
This particular idea wasn't born in Google; it traces back through previous secure OSes like EROS and KeyKOS maybe with a dash of Plan 9 thrown in.
What would a real-life use case for this be?
No it's not. It's just great marketing. There are tons of users who aren't privy enough to call attention to it on social media channels. If they're not privy enough, they just don't.

My friend had all her luggage lost by Iceland Air a few summers ago. She spent a week without it. She reached her destination and had just the clothes on her back and her carry-on. She talked to everyone she could. "Have you yelled at them on Twitter yet?" "No why would I do that?"

She did, and 12 hours later she had her luggage.
Those things don't scale up. What works in a toy won't work in a larger aircraft. Look at rotor disk loading versus power efficiency for example.

To gain a better intuitive understanding of the problem, consider why we can't use selective breeding to create a mouse the size of a horse.
The (Type-)Faces of Microsoft
The Million Dollar Dissident: iPhone 0-Days Used Against Human Rights Defenders
"most desirable cities will always be most human happiness/friendliness focused cities"

No, they will be the richest with the coolest stuff to do.

Paris is not a happy/friendly city.

In fact, most places are happier than NY, Paris, London.

Also, most people don't move so functional cities are not so much aspirational as the people that live there are lucky!
You're right, a lot of new construction is trash. To maximize margins they use the lowest quality / cheapest materials allowed under code.

Houses are turning into Ikea furniture.
“A Stalker’s Paradise”: How Intimate Partner Abusers Exploit Technology [pdf]
I wouldn't say the Amiga was little known, though it did lose the war over the desktop.

I like that syntax by the way, kind of like drive letters but much more descriptive and not limited to A-Z. Netware also used it for full path specs.
> i.e. odds are it will never happen to you

In the reality of the situation, odds are that it will eventually happen to you.
Under the guise of "immutable ledger" (basically just a honest scout promise by Amazon) Amazon gets into industrial provenance business. Genius. No sarcasm. Like that satellite ground station business yesterday. Basically "own the platform of the future" strategy the same way like spinning up the AWS 10 years ago. While companies like Google struggle to find any new business, Bezos just "printing" it non-stop (does he have a separate area in his brain labeled "Bezos X" ?).
48 Hours of Interactive React Programming Tutorials
It's not the drug, it's the FDA approved one use delivery system. Epinephrine is dirt cheap.
Movement.

I'm lucky in that I have a university campus to range around on, so this probably isn't an option for everyone, but I find that changing locations every two hours or so helps keep me on track, be it for homework or client work.
yes, it wasn't meant to make a claim on rightness or wrongness (although i can understand why it might come across that way), but to make a point about perspectives.

and that point was not so much "different strokes for different folks", but "different strokes for the same folks", as we each embody multiple perspectives and our conscious brain can choose among them (a lesson i keep learning over and over).
First, you need to choose if you are going to improve it, or ultimately abandon it. That's not an easy decision. If you decide to abandon it, you need some very convincing arguments, and lots of them. Before making that decision, work with the codebase, at least until you understand it well enough. It will allow you to uncover arguments either way.

Improving a codebase is a well-known subject, so I'm not going to comment on it further.

If you decide to ultimately abandon it, you need to understand it won't happen tomorrow, and perhaps not before a few years (for example, I'm 2 years in with a codebase I decided to abandon, and it's probably going to be at least 1 more year in production). Stakeholders hate when you spend time just rewriting it for the sake of it (from their perspective).

What you want to do instead is use a strangler pattern: your new codebase should "strangle" the old one, and deliver value VERY quickly, which will convince the stakeholders it was the right choice.

First, all new features are in the new codebase. If possible, start with easy features that have as few dependencies as possible with old codebase. Any call between the two should be in a special wrapper in your new codebase, so you can start having a sense for what code will need to be rewritten, at some point.

Then, start to "strangle" the old codebase: wrap ALL calls so they go through the new codebase first. That will allow you, somewhere in the future, to cut off the old codebase part by part, and avoid the full rewrite effect, as well as quickly revert to old codebase if bugs are uncovered.

Once you have that, you can more easily identify which parts should be replaced first: performance issues, too many bugs, new features needed...

When you reach the end, it's a matter of convincing stakeholders you absolutely need to go to the last mile, with good arguments. If you can't find good arguments, you probably don't need to go to the last mile yet.
This should probably point at the upstream page by the fuchsia project (https://fuchsia.googlesource.com/docs/+/HEAD/the-book/dotdot...) rather than a mirror source repo
We totally do, that's why most peoples opinion is irrelevant, and voting a rather limited direct influence, not to say useless.
Chinese Scientist Claims to Use Crispr to Make First Genetically Edited Babies
Keys Under Doormats: mandating insecurity by requiring gov access to data [pdf]
OK, valid point of about whether it's fair to call Roman numerals decimal. They're similar because all the symbols (except I) are multiples of 5 and 10, but it's not really the same thing as true base 10.
I suspect this effect depends on who you are. Within the sphere of casual chess players, playing a lot of blitz or rapid chess will make you a better chess player across the board, and any specialisation towards the format will likely be offset by the increase in general skill. For International Grandmaster quality chess players, they're already very good, so specialisation might be unhelpful. Cf. a similar effect in Google employees with programming competitions - https://news.ycombinator.com/item?id=9324209
So encouraging to see people promoting represent.us here!! Thank you!
That Wikipedia article doesn't draw any connection between modern policing and the slave patrols, though it points out the well documented connections between militia efforts and enforcing slavery. Similar institutions date to the Romans[1], which would suggest that slave catchers and the like may not be directly linked to our idea of a municipal police department.

The second source seem to support the connection, but doesn't document any actual institutional connections. It relies on similarity, and bald assertion. The existence of overlap between the KKK and local law enforcement is evidence that policing in the US is racist. It isn't actually evidence that the institutions of policing were descended from slave patrols.

I'm not a huge expert on criminal justice, but my degree is history, and these kinds of assertions seem to ignore the parallel developments in NYC, Boston, and other Yankee cities in policing and crime solving that established our idea of a municipal police department. That such departments may have been racist isn't a surprise, virtually every institution in 1880 was, but they were in states that did not practice slavery(abolished in 1799 in NY) and as a result had no institutional history of enforcing it.

Consider that Federal Marshals were so reluctant to enforce laws on the return of escaped slaves that it took an act of congress, with severe financial penalties, to get them to actually enforce the "property claims" of southerners.

1 - http://www.bbc.co.uk/history/ancient/romans/slavery_01.shtml
See how bad are software companies at creating reliable pieces software/services that don't crash and are without security flaws.

Now imagine Companies where software development is not a priority and/or is not in the set of core competencies.
As long as it functionally (kind of) works, it will be good enough.
Generally, community property will be split 50/50. Alimony would generally be set as a percentage of all income. Judges have a lot of leeway, though, and may lean considerably towards whomever seems more sympathetic (according to lawyers).

One bit that surprised me is that there is no reluctance to set alimony (considered on an NPV basis) larger than your net worth. It kind of sucks to have every dollar you've ever saved wiped out in one stroke, replaced with a nice pile of debt.
From Wikipedia looks like they are below the national average, but I'd posit that means the upside is that much larger.

My favorite example of this process is booming South Florida, where more than half of adults are foreign born. Houston is another great one, with 23% foreign born.

https://en.wikipedia.org/wiki/Demographics_of_Metro_Detroit#...
> 5% of people within the city of Detroit are immigrants, making the percentage of immigrants in Detroit the lowest such percentage out of those of the 25 largest cities in the United States. The national average is about 13%
> Upstream

Ironic
On the topic of sleep, I found Matthew Walker's "Why We Sleep" to be a really good read. I've spent about a month actively working on my sleep hygiene and I've seen a noticeable improvement in my productivity.
Mobile input types (and their virtual keyboards)
I will refute your list of quotes by (again) pointing to the results of the world championships, just concluded.

The world crown was lost because Fabiano cracked under time pressure and lost a position in Game 1 of tiebreaks that he easily could have drawn in classical chess.

Skill in blitz chess does translate to classical, people.

It's not just about developing intuition. It's training your mind to see clearly under non-optimal situations, like when you are exhausted or, say, drunk. Not that you would ever play a serious game of chess while drunk, but still.

Being good at slow 100% does NOT lead to being good at blitz. I mean, yes, a grandmaster will beat a noob at blitz, but that's obvious.

I know what I'm talking about. I am a lowly national master who "punches above my weight" by regularly beating strong IMs and GMs at blitz and bullet.

@whatismindgam3 on LiChess, feel free to add me there or challenge me if you want to put my theories to the test.
Developers who don't use a command-line shell, at least some of the time, aren't much of a developer.
Technology is a force multiplier.
The "easy" way to fix this is to take the market out of the equation.
> If this continues, at some point it may be necessary to consider limiting new construction. But that would have a substantial impact on the economy.

Lots of housing no one wants, but, we still need to keep building other housing that people do want.

Reminds me of the US labor market. Lots of people companies don't want to hire so we gotta bring in other people that companies do want to hire.

But, what should the US do with those unwanted people?
You’re dramatically overstating the advantage Carlsen had in Game 12. It was not decisive or obvious in any way and afterwards various engines played out the position to a draw. It might have been possible to win, but it might also have been possible to blunder and miss the chance to go to rapid tie breaks (a format where Carlsen had the advantage).

You’re also not doing Caruana justice. He worked Carlsen into badly losing positions in two games, but just blundered away the winning continuations allowing Carlsen to save a draw each time.

I think the better player won the match, but that Caruana played toe to toe with Carlsen, including attacking chess that caught Carlsen off guard and caused him to respond poorly. Meanwhile, Carlsen made absolutely the correct choice (best strategic choice) to draw in Game 12.

Very nice championship match, probably my favorite one of Carlsen’s era.
"but understand the business that the code was being used in/by."

From my experience(currently on a 10MM line of code, 15 year old codebase) in software the code is the business so it's important to understand it.

First trap: "Oh, I'll just document everything."

I could say just do it, but do it for yourself. I could say that it won't be maintained over time and it'll rot and may do more harm than good when someone goes to reference it and thinks it's still an up-to-date understanding of the system.

But I'd rather just tell you to not waste your time doing it in the first place and focus on not falling into the second trap.

Second trap: Rewrite.

I could say it's easier to write new code than it is to understand it. I could tell you to be ambitious and stay up nights and weekends rewriting some view layer logic bullshit.

But I'd rather tell you that you're not as smart as you think, your solution may be more complex than the currently impenetrably complex behemoth before you, and that you should instead focus on not falling for trap 3.

Third trap: Replacement.

I could tell you there's cheaper off-the-shelf solutions available that solve the same problem; it's simply a matter of spending money and reading documentation.

But I'd rather encourage you to really, truly embrace the final realization.

Final realization: You are dumb and will never, ever understand all the complexities of this system as there are too many interdependent moving parts and other similarly complex subsystems.

And that's okay!

This is a system built over many years that consists of hundreds of thousands of tiny decisions made by hundreds of different "very smart" individuals just like you solving complex business problems giving the climate of the time it was built in.

So approach it like you would approach a beast in the wild, with caution and grace.

Heroes are at the morgue, and just make sure the thing doesn't go down.
This is the response I'd have written if not for the movement thing.
Yes, don't inform others of sleazy practices, and especially don't lobby for legislation to curb corporate abuses. True power lies in acting as isolated individuals.
You are now in the platform business.

I have to assume someone is using the software therefore there is some tribal knowledge of what it does? Otherwise this is maybe SAAS software that users use and some functionality is exposed that would allow you to begin decomposing backwards toward expected input/output. You're almost black-boxing at that point.

I will admit that I have, on very rare occasion, scream tested a piece of software running on a server that nobody would claim ownership or knowledge of either on the eng. team or within the org.
The linked article mentions how helpful it is to have the right analogy (e.g. a number line, which you reference in your explanation of its intuitivenes). That's the main point: given the right analogy, things that otherwise seem arbitrary or nonsensical become clear and even intuitive. :)
Definitely longer than I've had time to read overnight, but interesting, and it looks like it may cover the claims of union busting. Though I thought that part of the reason the Pinkerton's thrived is that many police forces wouldn't engage in anti-union activities.
I think he means that people who use IDEs don't use shell file navigation as often.
If you only care about legal liability, cryptoshredding is generally recognized as an effective measure for secure deletion.
Agreed. That's why there's a separate championship title for blitz (which is Carlen's)
Maybe. However your representation isn't without drawbacks either: All fields are typed by strings, and are thereby not strongly typed. And each additional level (in an array or object) requires mandatory boxing and allocations. The codegen variants on pure structs don't have this drawbacks.

I would say your representation is favorable when someone wants to work with arbitrary JSON in a flexible fashion. However if schemas and code generators are available, I would prefer to use those.
What you describe is called "namespaces". Plan 9 and Linux have them already.
tl;dr: you have probably not thought through all the ways this system is used. Make damn sure you have both rollback plans and a phased release in the works. Otherwise, all your bravery and effort will be at risk. My experience follows.

I took over a suite of flash video players/recorders for a company years ago. The variable names were exclusively 2 and 3 letter acronyms. No one on the team even knew Actionscript. Up until my hire, the various builds were all considered immutable since no one had any idea of where to start. Given their integral nature to the business, this effectively stagnated entire areas of product and business development.

What you put in our question was precisely my approach. I did my best to reverse engineer requirements by code review and sale people interviews. Once i had a confident list, i got approval and killed off what i can only assume were swaths of unused features no one knew about. Rewrote + rearchitected the entire thing from the ground up.

The release was worse than you would have expected. Turned out there were lots of these players linked outside of our website. These versions of the app were ones we had considered deprecated and were unknown to everyone in the company including the cofounding CTO. This required immediate rollbacks and hastened development to re-add features that were being used by a subset of our longest lasting clients.

While the releases themselves were rocky, the entire effort was an unquestionable success. The effort consolidated all the features into a single reusable player and opened up years of feature dev that enabled millions in new sales.
EU consumer groups hit Google with location tracking complaints
In the context I work, I expect external software to be audited when incorporated into a project. It should be a significant decision backed by clear rationale to depend on someone else’s code not simply a convenience because we’re all lazy devs. I review diffs when updating library versions and guide people to prefer writing in-house solutions over including pop-software libraries. I hold my team accountable for the software they produce. I don’t disagree that everything works better when we all play nice, but I also don’t agree with deflecting the blame when your software is compromised because it doesn’t actually solve the problem and allows the same poor habits to continue unchecked. If you don’t understand a dependency enough to implement it yourself were it to disappear or break, you shouldn’t be using it.
This is like the second law of thermodynamics applied to code.
For the reasons you gave: as a litmus test for whether a politician is a statesman or a shill, I look at whether he/she supports public education or not.
L4Drop: XDP DDoS Mitigations