skysight-inc/HackerNews huggingface dataset:
> what does the term "woke" mean in this comment?

In brief, “woke” means having awakened to having a particular type of “critical consciousness,” as these are understood within Critical Social Justice. To first approximation, being woke means viewing society through various critical lenses, as defined by various critical theories bent in service of an ideology most people currently call “Social Justice.” That is, being woke means having taken on the worldview of Critical Social Justice, which sees the world only in terms of unjust power dynamics and the need to dismantle problematic systems. That is, it means having adopted Theory and the worldview it conceptualizes.

Under “wokeness,” this awakened consciousness is set particularly with regard to issues of identity, like race, sex, gender, sexuality, and others. The terminology derives from the idea of having been awakened (or, “woke up”) to an awareness of the allegedly systemic nature of racism, sexism, and other oppressive power dynamics and the true nature of privilege, domination, and marginalization in society and understanding the role in dominant discourses in producing and maintaining these structural forces.

Furthermore, being woke carries the imperative to become a social activist with regard to these issues and problems, again, on the terms set by Critical Social Justice. This—especially for white people—is to include a lifelong commitment to an ongoing process of self-reflection, self-criticism, and (progressive) social activism in the name of Theory and Social Justice (see also, antiracism).
No, the first sentence does not imply that mailers use the same underlying "render a view" mechanism. I would argue it implies the exact opposite, in the mailers are just another way to render the view. The two sentences mean the same thing.
Oh man, but try using “this Friday” on a Saturday. Now you’ve entered into a possible third case!
> Its strange American English created this ambiguity in usage. There's a perfectly good english language noun which means "2 weeks". The word is "Fortnight".

...the ambiguity exists whether or not you use fortnight!

Fortnight combined with semi- will do pretty well, assuming people don't screw up semi-. But you still need an unambiguous term for "every other month" before the problem is solved.

Maybe if you can change the schedule to quarterly?
“Adjusted for economic growth” is doing a lot of work here. Economic growth is happening for reasons like the growing addressable market for smartphones and the development of clever algorithms that make cheap sensors take good photos. The line cooks at my favorite roadside diner in Des Moines may well feel that this means they deserve a raise, but nothing has happened to the passing motorists’ willingness to pay for the cheeseburgers they can make each hour. Unless one of the few thousand people involved in those projects happens to be among them.

Especially after adjusting to life without restaurants, bars, hotels etc. I don’t see consumers suddenly paying the prices that would support significantly nicer lifestyles for all the workers involved in these things.
I have never heard "depress" used that way (native speaker, AU).
The Indonesian navy does it to Chinese fishing vessels. They do this with primitive resources and without "help" from the US military.

Why does Argentina need the US navy? Why not Brazil?
Mmm, no? You can be on the dole or maternity leave, be a kid, elderly, disabled and everybody gets exactly the same quality of healthcare (in most countries including dental and glasses)

It means that I with good salary pay a shit ton of money for health insurance to subsidize other people. I don't mind, I still think it's a great system (and I probably still pay less than US people because our system isn't rigged and hospitals don't charge $20 for a single Ibuprofen pill).

AFAIK healthcare isn't tied to employment in Canada or Australia either.
> Why is it in your interest

Because a society where we can have less partisan opinions and more fruitful discussions is a better one.

But I'm not attacking you, and I don't think most of the other commenters are, either. You expressed a disagreement with its thesis and explained how identity has been useful to you. I just pointed out that perhaps there is a way to achieve the same goals without expanding your identity. I was trying to have a discussion about the essay. But it appears I misunderstood, and you did not actually wish to engage in a discussion, so I will stop here :)
A week from Friday is something very different, isnt it?
1.) We are industry in which you often become senior engineer after 2 years of experience, because basically you are confident a lot and can code.

2.) We are also industry that writes about senior engineers as if we were perfect zen masters, with no ego but great confidence and security, with infinite patience combined with effective asertivity, knew exactly what to say when socially and politically. And yet also willing to sacrifice self whenever self interest and project interest are in opposition.

And also having perfect technical skills, both abstract thinking and attention to detail, and know all algorithms and also all optimizations and all technologies and generally being perfects perfections.

3.) Although the previous two points sounds to be contradictory, maybe it goes back to confidence and absurd expectations.
It's really more like the staff of an anti AIDs org trying to organize to give as many people AIDs as possible
Alright. I'll bite. Please elaborate, which one?
“This Friday” or “not this Friday but the next” is the way to go.
Fantasy 6MiB DNS Stub on Windows
Free healthcare at the point of delivery perhaps?
Not GP, but I think they meant big fraction and mistakenly wrote small fraction. At least that’s the only way their comment makes sense to me.
OfficeJS Add-In or the old one?
If it's Saturday, and you're sending an email or text to confirm Monday's plans, you'd more likely to say "this Monday" than you would say "next Monday," though?

I agree with you, "this <weekday>" means the upcoming day this week, and generally changes to "last" if referring to the past, and "next" if referring to next week. "Next week Monday" or "a week from Monday" could both refer to "Monday, a week from now" though the first one might be confused if sent on a Friday...

Really, the answer is to skip English entirely and use calendar events and hope time zones don't change between when you plan the event and when it occurs. ;-)
It's always the lower class' fault. Because the wealthy own the media and write the narrative. Blame their lack of virtue or work ethic while being dishonest and greedy.
Google Dataplex – Datamesh/hub as a service?
It's a common phrase in East Anglia in my experience.
> I think if we can get through this year without going crazy with wage increases we can keep inflation at bay and COVID will go away

When cost of everything is going up, you can't keep inflation at bay.
That does not sound right at all, its a very common a word in the UK.

Fortnight derives from Old English "fēowertyne niht", meaning "fourteen nights"

Are you sure that was not the case for non native speaking folks in living in the UK.
In the past, for me, the word should was the blocker to improving on some of these. e.g. Senior manager X should know how this works. Programmer Y should be promoted. Technical debt Z should be paid down. I used to get stuck on this dismissive stance. It was the idealist in me saying we shouldn't have to waste energy on this stuff because it should be common sense. I was seriously lacking compassion for some situations. I think learning to synergise my empathetic side and my logical side has allowed me to step away from what 'should' be and what 'can' be.
Previous threads:

Keep your Identity Small (2009) - https://news.ycombinator.com/item?id=16454591 - Feb 2018 (110 comments)

Keep your identity small (2009) - https://news.ycombinator.com/item?id=11732970 - May 2016 (153 comments)

Keep Your Identity Small (2009) - https://news.ycombinator.com/item?id=6171790 - Aug 2013 (90 comments)

Keep Your Identity Small - https://news.ycombinator.com/item?id=471660 - Feb 2009 (253 comments)
>Make it simple enough that a brand new completely green junior member of the team immediately understands it on first reading.

But what if the junior member can't understand OOP, functional programming, has no idea of abstraction and can only produce duplication and duplication of code,should we also try to adjust to that level?

I do see the need to keep code simple, but sometimes an additional layer of abstraction and complexity is needed because code maintenance task requires it, junior people most likely can't appreciate it until they are no longer junior.
How+to+Find+Duplicate+Values+in+a+SQL+Table
Somalia shows nicely why we, as the West, has a hard time combating illegal fishing. We ignore large scale illegal fishing in Somali waters, ruining the local economy. We also ignore that our fishing fleets aren't that innocent.

When the locals, for lack of a standing Navy, defend their waters, we call them pirates and send our Navy to fight them. No surprise, that these pirates went after bigger ships, realizing that being more profitable than fishing.
Now imagine a world, in which our Navies would defend Somali waters against these intrusions. While at the same time, we did some real, like non-military, backes nation building through the UN. I guess that would have been a much better way to combat piracy there. But who gives a shit about some poor bastards in a failed state somewhere in Africa?
A Case For Week Numbers.

Friday Week 26 is certainly less convenient to say or parse, but it’s completely unambiguous. Yes, everybody uses ISO week numbering, it’s what’s on the calendar, it does not matter that you don’t like it. Week ordinal = iso, cope.
Thanks for providing some factual real-world insight to the topic of US healthcare where most information that bounces around Europeans is along the lines of "yeah, well Americans have higher salaries because healthcare costs are so extreme so everyone without a tech job is living paycheck to paycheck and can easily be bankrupted by illnesses".
Terminology has stabilized, since. Cpre parsed and analyzed C-with-classes code, and synthesized C code just like any of the later compilers, and Cfront.
Not to mention all the other places crew is recruited from. Including crew on first world merchant marine ships.
As descriptivists, they observe that the "semi-" prefix is unambiguous, and the problem doesn't arise.
Replace "amortized" with "on average" and you'll have the basic concept.

A constant time operation has bounded runtime for every input, but an amortized constant time operation can allow for much longer runtimes so long as they happen sufficiently rarely. Concretely, doing an amortized constant time operation N times should be O(N).
I mean at first it sounded like fraud, but then you explained it, and then it really sounded like fraud.
Interesting point. Lets do the numbers. Supposedly desalination is 86.55 million m3/day (https://iwa-network.org/desalination-past-present-future/). 1m^3 is 10^3 kg. So 8610^9 kg desalinated water, I dont know the conversion rate, but lets say rougly 110^11kg water from sea pumped. Divided by 5e6 we have 2*10^4 kg/ day. 20 tons of lithum per day. Sounds a lot. That's roughly 8000 tons of lithium per year. Worldproduction is 80000 tons per year. https://www.statista.com/statistics/606684/world-production-...
So while not insignificant it doesnt seem a game-changer. (I might have miscalculated a factor of 10 somewhere, probably..)
Sorry, but I find your language inappropriate.

> what you mean is simply side-effect freeness

This really makes it sound like an assumption. And:

> So just exchanging ref. transparency with “not having side effects” in your otherwise perfectly fine and interesting reply will make it correct

You implying my answer is incorrect here but you are not giving an example of what is wrong even though I asked for it.

That being said, I believe that the definition of referential transparency (and therefore FP) is not useful at all without making "semantics" a part of it. And this is the point where discussion can happen. For example, is the performance characteristics of a function part of the program semantics? I would say no. Even though it matters in practice. Same goes for logging: one can argue that logging (that can not blow up due to e.g. lack of disk space) can be considered irrelevant for program semantics and hence a function that logs something with a "print" can still be pure.

If you remove semantics from the definition then the definition becomes rather useless imho. In that case I would rather change its meaning or switch to a different definition alltogether.
Only one way to find out!
Jokes aside, this would be awesome for Portugal, there's a lot of protests when lithium mines open in here.

Have an option to start extracting lithium from the ocean (which Portugal has LOTS of) would be really cool, but I doubt anyone would put a finger on it without have proper studies on the environmental impact.
Personally I am surprised that the idea of pure capitalism is still preached at all. I don’t understand why.

No one is in a capitalist system. Democracies ensure that - politicians will act to ensure the interest of their supporters.

As a result there will always be tariffs, subsidies or tax breaks to support different types of commercial work.

Is it just a rhetorical tool? Some times it reads as if people are actually arguing based on a pure capitalist model and it’s confusing.
She is free to continue doing activism and even continue her indoctrination efforts, she just can't expect to subvert university resources under tenure to achieve her activist goals. Note however that she was still offered an untenured position.

The importance of the point that her 1619 Project is not a serious attempt at historical understanding but a project within critical race Theory is beyond calculability. This is because the standard approach to challenging the 1619 Project’s bogus claims and attempts to roll itself out into our society and educational system is to challenge its historical legitimacy, and this is unfortunately a necessary part of engaging with it. The trouble is, because the 1619 Project neither is history nor claims to be history, this necessary activity is ultimately severely limited in its purposed utility.

Letting political activism like this into the universities therefore makes it harder to continue the Universitys original mission of continuing the liberal project of real knowledge seeking and research. Not everyone is fit for research and teaching, and you do have to protect the liberal system from efforts such as this for them to remain centers of knowledge production and truth seeking.
Yes but this can be harder than writing good documentation along side the code. For example I work with software that automates CAD manufacturing. Knowing what side of the part is side A is hard to communicate. But we have drawings that help explain it all. I've yet to find a way to have this embedded into the code. Asci art comments are as good as I've gotten.
One of my favorite podcasts, Hello Internet (hosted by CGP Grey and Brady Haran, though currently on hiatus) had this section called the "biweekly weigh-in" where every sometimes the hosts would talk about their health gains.

Using an ambiguous word like "biweekly" was very much intentional.
Or “next week’s Friday”
Some parts of FFmpeg are LGPL, and some codecs are GPL (e.g., if you have x264 libs in there).

How does one comply with the GPL and LGPL with Wasm, other than a complete source dump?
Anyone else reading Bier score?
GP is likely referring to the use of electron tubes [1] perhaps juxtaposing (hypothetical Taiwanese) tubes in 1958 with TSMC today(?). A decade earlier, however, the transistor was invented and would replace the use of tubes, at least for computers.

Tubes, aka valves, are still popular in professional and consumer audio equipment, vintage and contemporary microphones, amplifiers and compressors.

[1] https://en.wikipedia.org/wiki/Vacuum_tube
my favourite: "intuitive" for "I'm unable to explain but you better feel stupid if not knowing upfront."
In German it is "dieser Freitag" (this Friday) and "nächster Freitag" (next Friday).

But still "nächster Freitag" isn't totally clear for everyone.
It's because the vast, vast majority of code is not and need not be groundbreaking computer science, it's boring business logic and glue code, and it's built in teams of regular people. We aren't trying to save the world with efficiency and cleverness, we are trying to be robust and understood.

There is a time and a place for innovation of course, but you will be in a unique position when it happens. Perhaps you have a very interesting problem to solve, an opportunity to automate some part of the building, maybe you are architecting the system, or you are writing code for fun and not in a team. But you will know it when you see it, and if you can't tell then "write simply" is actually fantastic advice for you because you might be over-engineering some really boring stuff.

It is genuinely good, pragmatic advice to execute most code as simply as possible because that is all it needs to be, and your code will probably be worked on by others in the team at some point and you are wasting their time if they have to pontificate about the meaning of life before understanding your code.
Sure, but to saw timber, irrigate and grind seeds to not starve is also worth something.

Wind and solar have net negative energy output, meaning the cost of manufacturing the cells/turbine + the electronics, cables and batteries cost more energy than the hardware will generate in it's lifetime.

The tree is the best solar panel + battery and nature invented it, it made all the coal, oil and gas!

Beyond that only hydro and nuclear can help, and you cannot build, maintain or rescue a nuclear plant without dead trees.

So that leaves hydro, even with flooding and drought; it's the only stable "source of progress".
I think OP is saying a lot of 'cars' in China wouldn't fall under that definition of a car, so aren't in the stats...
If tomorrow someone burns a red light and smashes into you and you can’t drive anymore, are doordash going to keep paying you?

Yes, these “jobs” are fine as long as everything goes to plan, but is it really that much to ask to not have to live under the sword of Damocles?
What is this ‘revolution’ revolting against? All I see is a violent astroturfed corporate-funded government-supported mob demanding more wealth and freedom to be taken from the average individual, and given to the already most powerful. It doesn’t look like a revolution to me; it looks like the same old parasitism moving from host equilibrium to final harvest.
MailTrackerBlocker 0.4.1 – The biggest feature update yet
Yeah, what a hilariously click-baity title; worth a LOL ;-).
For me, this is the critical bit here:

> One of the problems of patching code using ast package of Python is that it loses all the formatting and comments of the original source code. This can be solved by making the patch script a little smarter. Instead of having it unparse the entire patched AST and write that to disk, we can make it unparse only the nodes it modified and insert the modified code at the corresponding line number in the file. The ast nodes have lineno attribute that can be used to retrieve the line number of the file to be injected the patched code with.

Parsing & Patching the AST is relatively easy, with the provided tooling.
I always struggled to write the modifications out in a minimal way.
Looks like line-number information does get you over this hump.

EDIT: Looks like the python community has already a package for this: https://github.com/PyCQA/redbaron
I think we may be thinking about this differently.

I value reading the documentation of libraries that I'm using. I don't memorize it, but casually read over it to understand what's possible.

I do not do this for everything, but if it's a piece of technology that I value, then it's probably a good idea to read the docs so that I'm not faced with "I did not know that it could do that" situation.

The amount of times I've seen developers painfully code around something that was already supported in the library they're using is suprizing.
Technical writer here. I avoid saying something is "simple," because whether it's simple is subjective and is relative to the reader's background knowledge. So at best it's unhelpful, and at worst it can be insulting.

If you're stuck on a task, the last thing you want to hear is that it's really simple.

On the other hand, I would write that X is a simpler approach than Y, if I was comparing two possible approaches.
If given a binary choice, I think you're right. I'd use "this Monday." But really I'd just say "Monday" or "on Monday" in that case. As in, "Just confirming that we're going to update the confabulator settings on Monday."

After writing my previous comment, I keep coming up with exceptions and variances to those exceptions. Like—as I write this—I would refer to June 9 as "this Wednesday", but June 11 as "next Friday". So I suppose I "glue" Fridays to the weekend? And right now it's still the weekend so June 4 retains the "this" title until tomorrow?

Starting to feel like I have epicycles of rules similar to the adjective ordering we all know, but never explicitly learned ("big red bouncy rubber ball" is okay; "bouncy red rubber big ball" is NOT OK)
Hey, give Gemini (https://gemini.circumlunar.space/) a chance. Things like https://cosmic.voyage/ make me happy to just browse stuff, read some stuff, have fun, not just consuming random posts on reddit.
Wow, what a coincidence. I did some maintenance on my NAS yesterday and finally removed one of my oldest hard drives, which I had unplugged a while ago because it was too noisy (it still worked when I unplugged it). I thought the name was familiar, I checked and yes, it is the very same model. I guess I was lucky not to lose any data on it, I wasn't very good with backups back when I first bought it.
I have lost access to my old account, but this comment has so much FUD (and seems to describe the state of Linux as it was about ten years ago) that I had to make a new one to respond.

>- package management (pkg & ports)

It's a matter of taste, I much prefer the power of dnf (the rewritten and modernized yum with full backwards compatibility) with its support for transactions (and transaction rollback, like reverting the state of packages as they were at a particular point in time) and many similar features.

>- file system (native ZFS)

Ubuntu has ZFS built in. You just have to install userland tools (run a single command to add a half-megabyte package and wait a few seconds).

>- instrumentation (systat & dtrace)

dtrace was ported to Linux long ago. We also have bpftrace: https://lwn.net/Articles/793749/

- documentation (handbook & examples in most man pages)

Back in the day it was way easier for me (as a *nix newbie) to find the answer to any of my questions for my Linux systems. I am not a native English speaker and I couldn't read English documentation at all. The various Linux docs, blog posts and community support absolutely dwarfed anything that was available for FreeBSD.

- event notification interface (kqueue vs broken by design epoll & inotify)

No mention of io_uring? https://lwn.net/Articles/776703/

- license (BSD, no GPLv3 at all)

Similarly, it's a matter of taste. The GPL family is a clear win for me.

- quality control (no shellshock, no dataloss on fsync)

The recent WireGuard fiasco proved that one wrong. Most code that's going into your system gets /absolutely/ no review besides its original developer. IIRC I heard that from Allan Jude (I think you should know of him) in one of the recent episodes of 2.5admins.com. He was obviously very uncomfortable describing the QA situation throughout the entire discussion.
Add Korea and Japan to that list. They are very careful about managing their own fishing grounds, but, sadly, much less so for international waters.