skysight-inc/HackerNews huggingface dataset:
> This business unit has a pretty aggressive roadmap as management and HQ has no real understanding of these blockers. And post COVID, budget is really tight

In my view, as long as management believes this, a fix is not possible at all.

You should forget about improving the code but see your job as a kind of consultancy thing where you teach management about what they have and the consequences of that are.

And probably look for a new job. If you are completely successful with teaching management, it may be working on this, but it'd probably need to be renegotiated as if it were a new job
Wikipedia hands down because it includes about all the information I could ever need from the internet at any given time
I always thought Phabricator was closed source. I was completely out of the loop about it closing.

Any tldr articles about the whole thing?
succeeding in college calculus is highly dependent on a good precalculus foundation. (it's the actually hard part). consider picking up a good precalculus textbook. (if the author or publisher of the calculus text has one, definitely get that one.)

avoid test prep or quick refresher books. you want the longform text that has examples of all the tricks needed.
Drag animals from one node onto another.

Some edges are one-way (marked with an arrow).

Some edges are only open when an animal is (or is not) on a certain space, as indicated by the text on that edge.

More than one animal may share a node at the same time.
No. Hate-speech is illegal, not a "viewpoint we don't agree with".

Your restaurant analogy falls short too. Dress-code is the equivalent of "civility" in discussion, and is a neutral bar that is set. It doesn't favor cotton shirts over linen shirts, which is what censoring a viewpoint would be.
jira is a project tracking tool, and has no native code review capabilities. It can be plugged into various suites of software that does have code review capabilities (such as bitbucket (both cloud and on-premises)), and display links to those software suites.
I recall an episode where it's all going to hell due to the holodeck, and Picard asks what happened. Geordie, I think, explains they asked the holodeck to create a character that could outsmart Data...at which point Picard lowers his head into his hands and mumbles "Merde!" (pretty clear, despite the mumble).
There are definitely periods, sites, and cultures where we believe the majority of finds that would have existed are already lost to us from decay processes (usually modeled exponentially). An example is the category of classic mimbres black on white pottery depicting animals. This is a type of artifact that certain archaeologists would like to study and also has a high black market value. The scarcity of examples with secure provenance indicates that few remain to be found as a result of looting and relevant experts don't expect to find many more.
I have them on for games so I can read the conversation and skip to the next sentence. For open world RPG games that are 50+ hours long it really helps staying engaged, as some quest lines are not that interesting and I like to complete all side quests.
Ah yeah, interesting point. The old “everyone can move freely because it’s evidently trivially cheap to do so” imaginary tale they like to weave.

Hadn’t considered how that’d change the discourse for abortion but I can see it now.
When you do code review, you are approving a patch: the difference between the old code and the new code.

With GitHub / Gitlab you push a branch and tell the tool to generate the diff by comparing two branches.

With Phabricator you make the patch locally and push the patch directly for review. There is fooling to help you do this, as well as to pull and apply patches.

This decouples Phabricator from your VCS tool and is partly a legacy of a time when Facebook had some engineers (and the central repo) using Subversion, and others using git. Even when everyone is using git, there are still 1001 different workflows which people use, so Phabricator ignores all that and zeroes in on the relevant bit: the code change you are proposing.

It is more precise, imho. At its heart, code review is a human process for discussing the merits of a document that happens to be structured in the form of @@, + and - symbols. You can bolt other tools onto the side of it for CI/CD, linting, etc., but the human readable code change and social interaction parts are still front and centre.
J40: Independent, self-contained JPEG XL decoder
Feedback:

1. It was good enough that I finished. This is success! Good job!

2. It took me too long to realize characters could occupy the same space, and the game doesn't draw characters occupying the same space very well.

3. The flashing lights at the end are too fast, slow them way down and it will still look good. You'll probably only have to change a number in your code.
Doesn’t sound like the worst code really; sounds like the average older php codebase I run into. I maintain (inherited) products that are over 15 years old and I find it enjoyable. I would be able to slowly move this thing to modern standards without rewriting or breaking anything; been doing that on very large php projects for a decade. Probably doesn’t need a rewrite, just see it as a bonsai tree.
I downvoted this because I think you are wrong about some crucial details. Woodstoves have in fact improved considerably since the late 70's: higher efficiency, longer reload times, and lower emissions. Modern woodstoves do not need to be refilled every 4-6 hours.

I'm in a good position to assert this, since we live in Vermont (a place with cold winters) and heat almost exclusively with wood. We recently upgraded from what was a state-of-the-art 1980's stove to a start-of-the-art 2020's stove. Doing so reduced our fuel consumption by about 30%, and improved our reload time from the 4-6 hours you mention to 8-10 hours.

After upgrading, I no longer have to get up in the night to feed the fire. And this is in a 100 year old house with overnight outside temperatures frequently in the -20C to -10C range (-5F to 15F). I do agree with you though on the necessity of properly drying wood and on the carbon cycle.
I always run small mutations like that in a transaction.

BEGIN;
DELETE FROM product WHERE id=123;
ROLLBACK;
--COMMIT;

And then I remove/comment the ROLLBACK and enable the COMMIT when I'm confident it's correct. This way I also get the number of affected rows for the statement.

I do this even on the command line but it's handier in an Emacs buffer and for busy databases you then don't need to worry about other transactions and locking while you type.
Really? I find the difference between the Stable Diffusion code and the code you find in a typical Python package to be night and day.

Why is there precisely one test (that has nothing to do with the core functionality)? Why is the Git history full of things like “finish”, “correct merg”, “fix more”, “add code”? Where is the linting config? Why are there print statements everywhere? Why does non-UI code have UI code embedded in it? Why is there random code commented out? Why is there no consistency across the codebase? Why is everything written as if they’ve never seen a Python project before (comments that should be docstrings, docstrings that should be comments, print("WARNING: ") instead of using logging or warnings, underscores in CLI flags, no shebangs in scripts intended to be run from the command line…)

Not all Python software gets all of this right, but it’s incredibly rare to have so many misses, even for hobbyist developers. Unless it’s code released by researchers, etc. It’s pretty typical in that context.

> This is not a project made by people without dev skills.

No, but it is a project made by people lacking software engineering skills, which is a distinction I drew in my earlier comment. Like I said, they can write clever code, but there’s a difference between bashing on code until it works and building it properly. This is the kind of codebase you get when you have people who have been writing code for a long time, but never in the context of a software engineering project alongside experienced software engineers they can learn from. Put them on a team like that and they’ll be forced to unlearn most of these bad habits fast because they’d never get their pull requests approved otherwise.

I’m trying not to be harsh – I understand that this code is more of a code dump from researchers than a real software project, and they’ve done some incredibly clever things here – but if somebody is suggesting that Python projects in general are like this, it really should be pointed out that this is not in this slightest bit representative of a typical Python project.
I think they meant it literally, to further reinforce the fact that they were colluding to extract profit out of their students via yearly textbook revisions.
I have a 5.0 system, and the dynamic range mumble voice + super loud explosion is still very present, even when I artificially boost the center channel. I think voices are actually better on a typical tv speaker 2.0 setup.
So the simple fact remains, how much of your country's wood burnt pellets are actual cast off "junk" and how much of it comes from forests getting mowed down to feed the system? Not just your house.
That’s not the definition of free speech in the US. The reason you should care is that your definition is likely to produce a free speech absolutist counter-movement.
I think this is really cool and a smart way to approach this problem. That being said, the physical isolation of the YubiKey is what makes it useful. Having to physically press a button is the real isolating factor, the interaction is physical and not determined by a piece of software.
I think the parent comment was complaining specifically about the misspelling "centrifical" rather than the fictitious force issue ("-fical" means "making", while "-fugal" means "fleeing" or "escaping").
Check this out: https://youtu.be/puIAG8ienB8
Economics of Money and Banking | Coursera
I think it as basic and as deep as it gets and a great teacher Perry Mehrling
Check if you're breaking the law. Those junior programmers may well have not thought to worry about privacy laws or industry regulations.

Then check for the most basic security issues like the database being accessible from the outside, SQL injection, etc.

Then set up monitoring. It's quite possible the thing is falling over from time to time without people knowing.
So, you are going to draw a very arbitrary line where you define a human life to be worth it.

Do fast food workers qualify? Garbage collectors? Store clerks? Mailmen? Taxi drivers?

There are millions of jobs that you routinely depend on in your life. But sure. "We as society don't owe them anything".
I've found the Yubikey to be an incredibly easy way to do 2FA. I use a usb-c nano version and it pretty much never leaves my mac (and the mac never leaves me). I've found it faster to do 2FA on a large number of tech websites. Just touch the key and you're done.

I know 1Password can fill TOTP for you, but I like having my security spread across 1Password and Yubikey. In the unlikely event 1Password gets compromised they still need physical access to my computer.

I don't log onto the mac with Yubikey and it has full-disk encryption turned on, so I'm pretty happy with the attack surface.
How Co-Founders are picked these days (Humor)
Maybe pessimistic: leave and find a place to work on something you enjoy. If you stay you will be left fighting everyone and doing all the grunt work by yourself whilst others keep pushing more code in for you to cleanup.
>In May, the 11th Circuit, based in Atlanta, found that most of a similar Florida law violates the companies' free speech rights and cannot be enforced

Why should a _company_ have free speech guaranteed by the constitution? It's a company - not a person.
I don't get the hostility, nor why you keep trying to shove words in my mouth.

I never said anything about new customers, nor even old customers.

I've also been very explicit that I'm just talking about seeing a plausible possibility, and not made any claims about it's probability. Nor said I think any person or entity - WotC included - should actually do anything or not.

And I've absolutely not made any particular judgements on the intrinsic value of NFTs.

I get you don't like the whole crypto thing, but this reaction is way beyond the point of reason.

I'm really not much of a fan either, honestly. That doesn't mean we should demonize our own thoughts if they point towards a hypothetical possibility that some other people might find value in it.
std::function is literally an object that can be invoked like a function. As an object, it can contain multiple values.

Move-only values are very used for common situations of unique resources that should not be duplicated.

But, what if you want to enclose a move-only value in a std::function? Are you simply out of luck and must give up on your dreams? A move-only function lets you get that work done.
I'm always hungry, however eating one nectarine every 3 hours starting at 2pm reduces my hunger dramatically.
I uss that trick as part of a diet to lose weight really fast.

I noticed a big difference in hunger by drinking a lot of water (3L per day), with the big downside of needing the washroom more often
You misunderstood my point. Whether a system is "socialist" or "market" says nothing about whether a system is good or whether it is better than another. The only way to measure whether a healthcare system is good is by looking at the outcomes of that system. The comparison to programming would be if people declared a program written in rust to be better than a similar program written in python simply because of the language. That makes no sense. It is certainly possible to produce programs written in rush that are worse than ones written in python.

The point is that the measure of the quality of healthcare systems shouldn't be whether they are socialist or something it's looking at life expectancy, efficacy, cost, etc. Those are the things that actually matter. Hence "but they don't think that American health care is good" is missing the point. A common talking point in the US is that American healthcare is better because it's not socialist (or some essentially equivalent argument). It's total nonsense. An introspective American with a little humility might wonder "I've been led to believe my system is better because it is not socialist, but outcomes in other systems I consider socialist seem better". An introspective American might wonder if this belief "the solution is for the government to be less involved in healthcare, or at least make it more competitive" is truly worth holding given that so many supposedly less competitive systems have better results.

Maybe in summary, think in terms of actionable information about systems and not nebulous undefined dogmas such as "socialist" or "market".
A company is just a group of people.
Not refunding a customer for selling a broken product is against the consumer law in plenty of jurisdictions.

People still don't do it because they have been taught that software is special, they have to put up with broken products, that is just how things are with computers.
How big is this code base and how advanced are the features? With only 3 juniors behind the wheel is it really that big? Was it always this small or is this the leftover maintenance team?

Is there documentation, requirements or user stories available for the existing features? Is it B2B or B2C? If it's B2B it becomes a lot easier to do customer survey of what is actually used and could help you remove half of the 12 year legacy.

Apart from the lack of source control, the rest of the issues, while being far from best practices, honestly don't sound extremely bad. Lack of framework or DI is not an antipattern in itself, even if it of course can be. Productivity of 3 juniors, split across one stack each, doing both operations and feature development on such a big application is going to be small even if using better practices. If revenue really is 20M and this code is critical, it sounds like you are understaffed.

Skipping the scm, deployment and process improvements, as others already gave good suggestions. Assuming you need to keep the existing code. One thing that has not been mentioned in static analysis. If the majority of the rats nest is in PHP, one thing you should do to add static type checking. This has zero effect on production and makes the code infinitely easier to navigate. This will expose how much of the code that is dead, how much is shared, what depends on what, etc. From here, refactoring will be a lot easier and safer. As others suggested you obviously need tests around it as well.
For how popular this is, streaming providers and major video websites like youtube sure phone it in with subtitle placement. They could do basic shit, like force the subtitles to be within the black bars as much as possible with some basic algorithmic programming, or just spend one person day laying out the subtitles better or just approach an iota of the effort that most fansub groups do.
Not a sound guy, and have struggled for a while w/ this for my plex setup @ home, so grain of salt.

If there's not a separate track for e.g 2.0, then the mixing down from 5.1 -> 2.0 will not have a human who validates the output. An automatic conversion can't accurately confirm that "this is legible for human ears at the right levels"
People do not generally lose rights by coming together to do something.
Lambda Calculus is computationally foundational. Lisp carries a lot of non-foundational baggage, some of which (like number primitives) makes it far more efficient for running on actual hardware.

> As such, Lisp's identification of CONS/CAR/CDR/COND as a sufficient set of primitives for a universal Turing machine

You don't need any of those for universality. They are trivially expressible in Lambda Calculus. LAMBDA is really the only necessary primitive.
I think I remember reading a Cobain interview where he stated this sentence was something he often said when he was invited by friends for dinner or the like. I can't seem to find the reference so I may have dreamt it.
The UX is right but the business logic is strange. It's obvious it's entirely possible to casually walk out with goods you didn't pay for. I've done it a few times by accident and returned to pay.

How many people don't return to pay? If you have say, 70,000 unique customers in a year the loss could add up quickly. The only way I could imagine this working is having some flex in the budget for theft that is being used up by these systems. In that case, it might be that "encouraging" people to steal smaller, cheaper items may save you on theft of big ticket items. So much so it's worth it.
That sucks. You’re the one maintaining the code base so you’ll be the one who suffer when something like that explodes. Do you think boss will take responsibility for making bad architecture decisions?

My approach is to explain first, and do it my way anyway in case of hard disagreement. If boss disagrees with that what’s he gonna do? Do the job himself? Maybe he’s the boss but I’m in charge of the code base and architecture.
> "The loud parts (including explosions and music) are too loud for her, so we have to turn the volume down during those parts, but the dialog is too quiet [..]"

On YouTube the ads are the explosions. Ads are so loud compared to the regular videos that I often just turn the volume down and the captions on.
Great rewrites are alomst always a bad idea. I took part in flushing 2 man-years early in my career and more recently 4 man-years. Both were rewrites that couldn't get to shore. Painful both times, moreso the 2nd time since I was one of the implementors.

It's almost always better to do small replacements. Peel the onion so-to-speak. Refactor from within first to make a migration plan away from the crufty tech possible.

First and foremost: make a plan and sell it to the devs. If you don't get buy-in from them, nothing will change.

Good luck.
Seems like it's a bit buggy. Got a bunny stuck on a flower, unable to move it. Moved the second bunny to the same place and that made it unstuck.
But limited liability companies are definitely more than just a group of people.
What would you call walking and chewing gum?
Golden age was Silicon i.e. Intel, Silver age was Internet i.e. Google, Bronze age was Social Media / Mobile Apps / SaaS.

We're now into some kind of 'common age' which I think will be different than before because we're likely going to be more distributed.

Tech is the new 'Banking' where all the kids to go to get guaranteed payouts so you'll see the culture change. It already has. No place for hippies and surfers anymore.
Dark scenes tend to look better on bad TVs because they tend to brighten everything too much with LCD bloom. I feel like it's an opposite problem with OLEDs, they're the one with scenes that are too dark.
It's a distributed system. You can almost always scan faster than a cashier and you know exactly what quantity and item you intended to buy. Moreover, a cursory (rather than colonoscopy level) scan of "big ticket" items that are commonly stolen is probably more than sufficient to deter most thieves.
These all seem fine to me in northern California. Might raise some eyebrows in some other parts of the country.
There is significant danger that management will use these metrics to micromanage your efforts. They will refuse changes that temporarily drive that number up, and force you to drive it down just to satisfy the tool.

For example, it is easy to see that low code coverage is a problem. The correct takeaway from that is to identify spots where coverage is weakest, rank them by business impact and actual risk (judged by code quality and expected or past changes) and add tests there. Iterate until satisfied.

The wrong approach would be to set something above 80% coverage as a strict goal, and force inconsequential and laborious test suites on to old code.
Worked fine for me on FF on Android. With third-party disabled uBO even.
This is the great thing of having a nerdy side: You know that literally everything will get interesting if you just dive into it deep enough.

Sometimes I feel sad for people who cannot experience that joy.
>what about some dangerous stuff like radicalisation which then will produce terrorists or extremist?

Is this the millennial version of boomers' "3d shooter games create school shooters"? "Tweets with bad words create terrorists"?

I thought this BS (both versions) has been disproved countless times. But here we are and the nu-conservatives (who call themselves liberals) are at it again.
I'm the same age as the students in the article, and I'm surprised that reading cursive is such an issue for them. Almost all of the letters closely resemble block letters except for R, S, Z and a few of the capitals. I mean, I don't use cursive at all in my daily life, but I still have no trouble reading things like https://commons.wikimedia.org/wiki/File:Letter.posted.in.189... using context clues.
Dune sounds great on my 2.0 system at home (low mid-range receiver and ~$200 yamaha floorstanders). Sicario too, from the same director, I generally think he does a fantastic job with audio mixes.

Strange that article doesn’t talk about the tripod noise from the ‘05 War of the Worlds.

https://m.youtube.com/watch?v=jzY099ihULs