skysight-inc/HackerNews huggingface dataset:
The poor job prospects for history PhDs in particular and humanities PhDs in general for literally years. I know I've read about history tenure prospects 10+ years ago. I know for history PhDs at least it can often take 8+ years to get your degree as well.

So my question is: why do people subject themselves to this? I mean if this is something that's fulfilling to you or you're not that concerned with the poor chances of finding a tenure track position, that's one thing. But we're well beyond the point where people can reasonably be shocked by this.

Is this hubris? As in, "sure the odds are bad but I'll be the exception to the rule".

I honestly don't understand.
Even in a nonauthoritarian country, defecting means you'll never return again to see your friends and family anyways. Given that, defectors probably consider making a political stand more important than their personal connections regardless of what happens after they leave. Not everybody has a loving family and close friends they can't give up.
Record profits, so clearly their problem is the uppity workers.

Sure we want them to be autonomous, we’re not monsters, but why do they have to air their yucky opinions? Why won’t they just shut up?
In my experience physicians are not 95% incompetent. Is there something inherently different about law from medicine? Or is more like how 95% of physicians couldn’t help you with a specific problem because it’s outside their specialty?
Hot Escort Girl for You
Heey babyy
> isn’t generally sustainable outside of a few specific cases.

WordPress can do it. Others also could, if they wanted to.
Rate of Vaccine Opposition
It’s fine if you load each page as an HTTP request, but if your ‘pages’ aren’t real, re-loading everything from an API each time is a bit of a pain.
Since you have a similar certification on both AWS and Azure.

Could you give a comparison according to your observations between the two?
https://calcite.apache.org
can you explain the `git pull origin master` thing one more time here?
The labels are indeed not very useful. It would have been better to use bitrates based on the jxl encoder, which has a perceptual-target based setting (--distance), as opposed to setting it based on absolute HEVC quantization settings (as was done here), which for some images causes 'Big' to be great and for others makes 'Big' still kind of low quality.
tl;dr https://mobile.twitter.com/daiwaka/status/140701138871160832...

Google Execs have an average vote that’s decisively short of “exceeding expectations.” But Google had an additional set of execs go for interviews that gave a more positive vote.
It's generally recommended not to do so. But if it's either that, or dehydration...
That's a very strange line of argument. Many great programs have been written in C. That doesn't mean that there is no way to improve on C. Perhaps to even the playing field, this hypothetical competitor should be given the resources of Microsoft Research as well :)
everyone saying to build on the side probably hasn't built or shipped anything on the side. building on the side:
- hard to think deeply or carve out deep work for side project when work + life keeps interrupting
- hard to make progress if project is ambitious given time constraints
- enthusiasm can fade due to interruptions

if you have a very high conviction and high savings, the best would be to jump into it. the thing with leaving your job is you can always find another one
If only emacs had a sane UI :P
You focus on things people aren’t willing to post on their Facebook feed. Snap and TikTok remain strong despite being copied because it allows people to essentially shitpost without their close friends and family seeing it.
> 3.6T a month?

No.

with P as “person(s)":

300MP × 1k$/P/mo = 300G$/mo

300G$/mo × 12mo/yr = 3.6T$/yr
I am confused…are you implying that history is an STEM degree?
I'd never thought about people doing research in accounting. What do they do? What are the frontiers in the field?
Irrational Modesty
Hiya Doc -- Anybody who had done any programming on mainframes, which both Gates and Allen did before the IBM or Apple computers came out, would only ever say such a thing ironically. Memory has always been the limiting factor on what you could program. An essential base skill for any programmer was minimizing memory use so you would not run out later in the project. So, when the PC came out, 640k was a lot for an 8-bit micro, but the 8088 was nominally 16-bit and equipped to manage a megabyte without any hardware fiddling, and its contemporary, the 68000, could already address more.
Another interesting rabbit hole to explore is the compiler. Back in the day I wrote a toy compiler for a college course and used this text book: "Compilers: Principles, Techniques, and Tools". a.ka. "The Dragon book", but I would look at some of the other books here like "Modern Operating Systems" before this.
I can’t wait to start using this
This is a great idea. There are well-documented ways to undo things on stack overflow, but almost every way:

1. Has three competing ways available to complete the 'undo'

2. Every way has a scary caveat that the user must be aware of

It would be awesome to simplify the process for new users.
The point is, none of the agreements are actually agreements. It's a fiction.
What is your end goal? If it's being hired at a large corporation, you'll find useful advice in lots of other comments here.

If you want to go to FAANG, it can still be useful, but open source contributions and learning data structures might be a better use of time.

If you're aiming at going to a high-growth early to mid stage startup however, be aware that certifications (especially a lot of them) can be an anti-signal. As a startup hiring manager myself, I view certifications at best as a basic aptitude check, at worst as signal of a personality who is fine with wasting lots of time into learning copypasta knowledge.

In that case, you might find a better investment in building presentable side projects.

YMMV.
D-Tron Diaries – A Kubernetes Comic
Hello everyone, I am one of the founders of Devtron. An End-to-End Kubernetes delivery workflow Solution that is completely OpenSource and Contributor led.

So, we are starting a comic series about the basics of Kubernetes. Every week, we'll be following the characters of Noob, Savant, and D-Tron as they learn all about Kubernetes.

Here's the first comic: https://twitter.com/DevtronL/status/1406904512820912129
Do let me know what you think. Suggestions and Feedback would be great!

You can check out our OpenSource Project here: https://github.com/devtron-labs/devtron
Consider contacting your competitors so that you can act together.

Consider contacting organizations like the EFF.
They didnt abolish tips, they force customers to pay untaxed tips. There is a difference.
Is the a rehash of the NeoMedia patent issue? Look up Michaels qr code patent lawsuit ...
….how did you manage to get into this position? Were you a senior principal engineer?
You can also quit the CLI editor, e.g. vim.
The problem is just that collaborative text editing between multiple users simultaneously is hard. It's a human problem and git attempts to be a technical solution but the abstraction fails at the edge cases.

Regardless, what's so bad about deleting the repo and pulling from remote if you can't figure out why you hosed it? It's not like it costs you anything to do `rm ... && git clone ...`. And it's not like this happens daily either.

In the rare case that someone hoses remote, yes you'll have to do some weird git-fu to get everyone working again, but it's really hard to hose remote if you stick to the pull -> commit -> push -> merge pattern, which is what 99% of users are doing anyways. I've used git for 9 years and I've never had to spend longer than an hour troubleshooting git based BS. And if you'll remember, 9 years ago git wasn't the clear winner, it had competition via SVN and Mercurial. Both of them are practically irrelevant at this point so however bad git's UI was, it's clearly better than anything else that existed before.
Especially with CouchDB and Cloudant.
China's Shenzhou 12 spacecraft docks at space station with 3 astronauts
Yeah, it was weird to completely lock out anyone without an iphone.
If you want that as a native app, Corel Painter has that feature of simulating paint bristles and real brushes and their color mixing, and wouldn't be surprised if GIMP and Photoshop also support that by now.
If you are living in the Bay Area, do not quit your job unless you have enough money to keep your own lifestyle in perpetuity.

I have so many friends that have regretted going into startups because they have missed out on literally millions.

If you don’t have a house right now, do not go into a startup because the ones in big companies will earn more money than you and you will effectively take a break in making money for years.

Of course you might work at the next Uber, but chances are 10 to 1 that you will instead work at the next Juicero. The 5 years you dedicate to that job will see no money but the stock market will rise and you won’t see any of that so your peers will get richer and richer.

So if you have a house and enough money to keep your lifestyle no matter what, then sure. Go for it. If you don’t, then wait until you have enough. Or if you don’t care about money and are okay with things like housing being completely out of reach then that’s okay too.
Don't forget `git checkout`!

When I help people get started with git, I tell them several times to commit as often as they can. If they committed it, I can probably save them when they think they lost something.
> And consider that social security is already accounted in the current spending.

Social security is not means-tested welfare.
High fat, or actually ketogenic?

Just curious, really. I'm not aware of any serious downsides to ketogenic diets, except I suppose for the smell, but it doesn't take much glucose or starch at all before ketone bodies are no longer needed.
I've run my company remotely since inception, I hate the idea of making people commute for free.

But one thing I've struggled with since growing to a size where the number of employees is more than I can keep mental track of is measuring individual performance and success.

Can anyone share any resources on how to handle that? What sort of metrics can one use to realistically measure the performance of a developer or designer where work consists of changing requirments & lots of back and forth? How to handle employees who seem to be working low hours or slacking off? How to reward those which have been working efficiently & productively? Any advice or experiences will be appreciated.
Because people generally spend a lower percentage of their income on cars and housing as their income increases. The minimums for shelter and transportation are hard to avoid.

Put another way the percentage of people making say 50k with a 20+k worth of car(s) is greater than the percentage of people making 50 million a year with 20+ million in car(s). Similarly it’s not that rare for retirees to be house rich owning say a 1+ million dollar house while having less than a 50k a year income. On the other hand someone making 50 million is extremely unlikely to have 1+ billion dollars in personal property.

It’s true the rich may own a yacht, but they are also likely to completely avoid paying personal property taxes on it.
Git invokes an editor, for writing commit messages, etc. (it looks in the VISUAL and EDITOR env vars). That could be a GUI text editor, or something running in the CLI (personally, I use emacsclient to open a new buffer in an existing Emacs window)

What they're saying is: if you quit that editor without saving the commit message, git will abort.
Yeah, I remember a midnight trip to the fort towering over Grenoble. You can see the whole town from 1.1km above and a few km away.

Everything was so calm and quiet from up there... until WRRRRRREEEEEEEEEEEEEEEHHHHHHHHHHH!!!!! a scooter cut through the night. :|
This can be difficult depending on the company. Mine has every dev sign a non-compete that boils down to "If you write any code that competes with us is any way, we own it".

They used to let us file requests to confirm whether or not it does compete. They stopped answering and now just say "use your best judgement", which is a nice way of saying "We'll sue you if we need to".
I feel that I only understand git because I’m forced to use it for years, but the experience could have been a lot less painful. I use a GUI for sure. Do people really diff and resolve big conflicts at a command line? I never figured out how.
I think they mean the commit message editor, which git will use to open a temp file to save the message to if you don't specify a message in-line with the "-m" flag when committing, including when a merge commit is initiated by a "pull". This happens on the CLI, it's just usually (though doesn't have to be!) a command line editor that it opens. I think vim's a common default.

AFAIK whatever's opened does need to block the CLI, so you can't use a command that opens a GUI editor then returns immediately or git will interpret that as your having closed the file without saving, but otherwise any editor should work, CLI or GUI, and can be assigned in your git config.
Studying anything at a university is not an apprenticeship for any job, but basically learning and doing science. If one loves History as a scientific subject, just go for it. Often, this is a once in a lifetime opportunity that you could regret later of not having taken.
FWIW, I don't see any paint with my browser: Safari 14.1 (Release 116, WebKit 16611.1.5.3) The rest of the UI seems to work.
In this case, your competitors DO have your best interests in mind. They have to understand that they are next on the list of troll targets, since they are offering a product that likely uses similar technologies.
Kavanaugh hits the nail in the head in his concurring opinion.

> In my view, that argument is circular and unpersuasive. The NCAA couches its arguments for not paying student athletes in innocuous labels. But the labels cannot disguise the reality: The NCAA’s business model would be flatly il- legal in almost any other industry in America. All of the restaurants in a region cannot come together to cut cooks’ wages on the theory that “customers prefer” to eat food from low-paid cooks. Law firms cannot conspire to cabin lawyers’ salaries in the name of providing legal services out of a “love of the law.” Hospitals cannot agree to cap nurses’ income in order to create a “purer” form of helping the sick. News organizations cannot join forces to curtail pay to reporters to preserve a “tradition” of public-minded journalism. Movie studios cannot collude to slash benefits to camera crews to kindle a “spirit of amateurism” in Hollywood.
Price-fixing labor is price-fixing labor. And price-fixing labor is ordinarily a textbook antitrust problem because it extinguishes the free market in which individuals can oth- erwise obtain fair compensation for their work.
Can I ask what country you're in? I'm in the US and my experience suggests the exact opposite of nearly every point in your first paragraph

Programming jobs here are plentiful, you should never work for free, your very first job might be a little harder to get than later ones but it won't be hard. And listing things like "tabs" and "pagination" on your resume feels really desperate, like you're scraping the bottom of the barrel to pad out the list as much as possible. The closest thing I would suggest is to maybe list some specific frameworks like React or Redux (or the equivalent for your area); though even then it's not really for the technical recruiters, it's for the imprecise algorithms that sift through the pile
To others reading this there needs to be a big bold WARNING: Do not drink liters of water as people have died doing just that. Google it and you’ll find horror stories of people in competition to chug tons of water only to make an ER trip and die on the way.

There is a myth on the internet that drinking shitload of water beyond comfort is acceptable and has zero risks because hey it’s just water right?

Here is some literature: https://www.scientificamerican.com/article/strange-but-true-...
Why “validate your idea” is bad advice
It's also possible (if difficult) to recover files which have been git-added and not commited. The only files git can't recover are the ones that it hasn't registered in the first place.
Keep the job until you’ll no longer be asking this question.
This is going to sound childish, but PIK (Google Pik) is literally “dick” in my language. I can’t help to chuckle at the notion of using PIK-images - literally dickpics.
If you are on Windows, Visual Studio's GUI is actually quite good for staging, merging and diffing. I tend to use it for most of those simpler kinds of things while still doing commits, rebase etc. from the command line.

Same for VSCode on non-Windows.

I only mention this because I came to hate Sourcetree in its newer iterations on Windows so much that I tried out Visual Studio's support and was pleasantly surprised.
You're assuming no wars or other inefficiencies...

In practice there is probably plenty of inefficiencies to go around. Maybe less today, but 14 centuries ago.
Some notable features of JPEG XL that don't show up in side-by-sides:

1) Progressive decoding. Like the original .jpg, .jxl can give you a low-quality image when a fraction of the file is loaded, then a decent-quality image, then the final image. This can give JPEG XL the edge in perceived load speed even when the full .avif is smaller than the full .jxl. (Old demo from a JXL contributor at https://www.youtube.com/watch?v=UphN1_7nP8U )

2) Fast conversion: JPEG XL encoding/decoding is fast without dedicated hardware. Facebook found encode/decode speed and progressive decoding to be points in favor of JPEG XL for their use: https://bugzilla.mozilla.org/show_bug.cgi?id=1539075#c18

3) .jpg repacking: JPEG XL can pack a JPEG1 about 20% smaller without any additional loss; the original .jpg file can be recovered bit-for-bit.

4) Lossless mode. JXL's lossless mode is the successor to FLIF/FUIF, is really good, and also has progressive decoding. AVIF has a lossless mode too, but JPEG XL seems ahead here.

(I know the parent comment is from a JXL contributor, I'm saying this for other folks.)

I think those will give JPEG XL a niche on the Web. Meanwhile I suspect e.g. Android phone cameras will save .avif someday, like iPhones save .heic now. Phones want the encode hardware anyway for video, and you can crunch a zillion megapixels down to a smaller file with AVIF before attention-grabbing artifacts crop up--at low bitrates AVIF seems good at preserving sharp lines and mostly blurring low-contrast details (compare Tiny images).

Finally, worth noting the codecs are different due to a bunch of rational choices by their devs. AVIF is the format for AV1 video keyframes. Progressive decoding doesn't help there, and doesn't jibe well with spatial prediction, which helps AV1 and other video codecs preserve sharp lines. And video codecs need hardware support to thrive anyway, so optimizing for fast software encoding probably wasn't an early priority. Otherwise the new formats have a lot of overlap in fundamentals--variable size and shape DCTs, better entropy encoding, chroma-from-luma, anti-ringing postfilters, etc.

Glad to see support for both getting more widespread.
Classic name dropping from a Google employee. This is why the companies products are mediocre, the employees care more about the fact that they work at Google. No mention of product possibilities, innovation, or anything. Just prestige.
Part 1 and 2 define the codestream and file format, respectively. They are both finalized at the technical level (the ISO process is still ongoing, but there is no more opportunity for technical changes, the JPEG committee has approved the final draft). So it is ready for use now: the bitstream has been frozen since January, free and open source reference software is available.

Part 3 will describe conformance testing (how to verify that an alternative decoder implementation is in fact correct), and part 4 will just be just a snapshot of the reference software that gets archived by ISO, but for all practical purposes you should just get the most recent git version. Parts 3 and 4 are not at all needed to start using JPEG XL.
The default editor is usually configurable (of course you'd have to learn all the different contexts you can do this from first to know this is a thing ... discoverability is hard).

For example in ubuntu you can do

sudo update-alternatives --config editor

Some programs will use the environment variable $EDITOR, so you can add this to your shell startup configs

export EDITOR=vi

Or specifically for git cli you can run

git config --global core.editor vi
Let's not forget about the index. Or is it called the staging area?
If I were you, I'd do the following: live frugally and continue your career until you reach a point where you can safely and comfortably retire. Look into FIRE (financial independence, retire early) communities and resources for more info. Once you reach that point, do whatever you want because the money no longer matters. Especially if you are okay with your current job, I personally wouldn't throw such a great position away just to gamble on a personal business. If it's really consuming you that much, just do it on the side. If you can't keep up your current job and get your business started in your free time, I personally don't think you'll have what it takes to power through the business anyway.
EU court rules ISPs can be forced to hand over IP addresses of BitTorrent users
Pruney fingers are a general primate adaptation, and likely have more to do with not slipping from trees when it rains than any serious aquatic phase.
And should not be.
A lot of serious, famous people live in grand, nice houses in older neighborhoods with hopelessly oversubscribed Comcast. The CEO of my Fortune 500 company presented at a remote all-hands at about 0.25 frames/second. Now at that level, maybe you can spend the $10 million it would take to pull fiber to your house. But we’re not taking about buying some prosumer electronics here, we’re talking years of permitting and digging up the street. For mid-tier famous people the only hope they have of getting better upload bandwidth is moving to houses that already have it. That’s a bit more dramatic than going to a clothing store.
still true! but that isn't a great metric necessarily, as #10 is "What is the “-->” operator in C/C++?" https://stackoverflow.com/questions/1642028/what-is-the-oper... which is just a novelty rather than a common question
I don't understand. You can always restore any previous state using git, I used to do it from the command line.

If I use github desktop I can roll back a commit whenever I like with a simple menu command.

What am I missing here. I feel like I don't understand what the tool is doing.
Why are we calling these "patent trolls"? They use the system we all built (or the one we tolerate) and pursue profits as per the "rules of the game". Instead of fighting this one case at a time, shouldn't we be organizing and pushing for the "rules of the game" to be changed and get this over with once and for all?

By the way, I strongly believe that software patents should not exist.
I think the parent commenter says that they do understand the underlying data.

It's just that the command-line interface is very opaque regarding what it does to that data.

For instance, say I want to apply the last three commits I made in one branch to another branch. It's a very simple operation conceptually.

Good luck remembering that the command that does it is rebase, and what the arguments for it are.
Like Nirvana or Pearl Jam?