skysight-inc/HackerNews huggingface dataset:
I read your post before it was flagged. Have you ever played Civ: Beyond Earth?

You're like the Purity faction, who bends all new technology around human whims and limitations (dome cities, big anthropomorphic mechs), solving the issue by segregating genders into silos where their whims and limitations are directly catered to.

There's two other factions in the game, Supremacy and Harmony, both of which are transhuman, who transcend their human whims and limitations and exploit and adapt to new technologies on the technologies' novel terms.

Purity is comfier and easier, but I think it's a net retardation of growth and development. (It's certainly a regression in terms of liberal egalitarianism.) That future is stagnation. Transcendence is the key. We should all become third gender. (Just kidding. I had nothing else to end with. By the way, your emphasis on "third gender" is pretty unusual to me. Do you mean non-binary people? Or are you using it as some TERFy catch-all for trans people? :p)
Usually something with good short-term stability, e.g. a hydrogen maser, generates a steady signal that can then be measured against a frequency reference such as a caesium fountain, and the output can be adjusted to correct for frequency drift.
Let's talk again about this after the next postmortem?
Author of the paper here, in case someone wants to ask a question :)

I originally didn't think it would get much attention, provided it's a bit technical...
Not endorsing this point blank but.. One positive side effect of this is that it becomes much easier to rally folks into improving the fidelity of the dev environment, which has compound positive impact on productivity (and mental health of your engineers).

In my experience at Big Tech Corp, dev environments were reduced to low unit test fidelity over years, then as a result you need to iterate (ie develop) in a staging environment that is orders of magnitude slower (and more expensive if you're paying for it). It isn't unusual that waiting for integration tests is the majority of your day.

Now, you might say that it's too complex so there's no other way, and yes sometimes that's the case, but there's nuance! Engineers have no incentive to fix dev if staging/integration works at all (even if super slow) so it's impossible to tell. If you think slow is a mild annoyance, I will tell you that I had senior engineers on my team that committed around 2-3 (often small) PRs per month.
Very, very nice, but to be more clear: it's not just Chrome.

The modern web is the surveillance web because the modern web is "an endpoint" for users (witch means a new mainframe dumb terminal, at a far higher price and complexity than the old ones) and someone else service, typically run on giants cloud datacenters.

To avoid that, and still have the modern level of life PLUS MANY MORE, we already have had a solution: the desktop computing. The first one on record the modern way AFAIK was the Xerox Star Office System, but even the older NLS (1968!!!) have networking, videoconferencing and screen sharing. YES, you read correctly. Dates are not wrong.

So what? So it's a real mess because since Xerox except for LispM and Plan 9 we do not have developed desktop computing anymore, so the old model might still be rediscovered, at least it still exists, but on actual iron, very badly designed even if far more powerful in mere horsepower terms, and with essentially no modern software. The last living vestige is Emacs, witch is VERY good but not enough evolved for actual end-users, so we need:

- public universities, paid enough by the government and government only, with a very effective separation from the private sector, to create a new old classic research not for short term business but for the society;

- enough years to write a modern desktop, which means around a decade because it's not just a matter of code, it's a matter to learn how classic systems works and design a new one, a thing most today devs do not know and have issue imaging, than time to develop it, to spread it etc.

The other option? Well... A small Canadian TV series (Continuum) recently gives a nice idea, perhaps mixed with a small French movie (Virtual Revolution) to see a more realistic one. Be prepared to a future where you will have to eat only if some IT giants gives food to you. Be prepared to live to work instead of working to live because yes, I'm not joking nor exaggerating, it's just a matter of observing the world today.
Static site generators often require prerendering and dynamic content so, no won't work without ssr.
limit eating out, cook your own food, don't have a car
It's perfectly natural to not want to have an account even if it's trivial to make, and even if you already have one, it's a basic privacy desire to refuse to link your computer to this account.

It's also a reasonable desire to have your computer local authentication be completely separate any from Microsoft service, ensuring that the events are private and don't even get communicated to Microsoft, much less being able to circumvent local authentication by anyone who is in control of that cloud account.
Anything that can't have a gc probaly can't use a regular memory allocator either (since they aren't necessarily easy to predict). So you would be left with static allocation and stack variables.
This article has some very weird trade-offs.

They can't spin up test environments quickly, so they have windows when they cannot merge code due to release timing. They can't maintain parity of their staging environments with prod, so they forswear staging environments. These seem like infrastructure problems that aren't addressing the same problem as the staging environment eo ipso.

They're not arguing that testing or staging environments are bad, they're just saying their organization couldn't manage to get them working. If they didn't hit those roadblocks in managing their staging environments, presumably they would be using them.
Did nobody say "fix the process" or "make 'cutting a build' automated with tests so that a human can't 'fuck it up'" or "have Mike drive that automation?" Because that would be a blameless approach.
SEEKING WORK | Europe | Remote only

Front-end developer with over 5 years of freelance experience, mostly on greenfield projects but also occasionally with established codebases. Used to working alone with minimal supervision or in small teams. Have a good eye for design, a strong focus on code quality, good communication skills and some experience in technical management.

Technologies: React, GraphQL, Typescript, CSS3/HTML5, Git, styled-components, Formik, Jest, Storybook, TailwindCSS, NextJS, SASS, TailWindCSS

Blog: www.slavenbacic.dev

Github: www.github.com/sbacic

LinkedIn: https://www.linkedin.com/in/slaven-bacic

Email: bacic dot slaven at gmail.com

CV: available on request
Crunchbang was based on openbox and not xfce.
I made a point not to single out one poster. Like most online conflicts, it was a co-creation.

Your original comment was great! And it got mostly positive responses, IIRC.

The problem is that negative responses hit harder than positive responses. If three people give you flowers and one explodes a bomb, the bomb makes the impact [1]. Unfortunately, the dynamics of internet discussion guarantee "bombs" on any divisive topic.

If you're not used to it, this has a dysregulating effect [2]. One gets sucked into a feedback loop where one can't help but respond to the outrage of being treated unfairly, but that just fuels the feedback loop. From my perspective, this is what happened here.

The important thing to understand is why your comment attracted negative responses in the first place. It had nothing to do with you, or your comment, or the community. It was just a mechanical consequence of it being the top-voted comment in a thread on a divisive topic—that's how the mechanics work. And it was the top-voted comment because it was interesting and thoughtful discussion (up to the point where it got derailed). Good things lead to bad things, so here's a cap on how good things can ever get [3], and all we can do is try to encourage the good and mitigate the bad.

[1] Lots of past explanation on that: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

[2] And getting used to it sucks—it's like being bitten by mosquitoes and wasps all over your body until you finally develop some sort of partial immunity to them, partial immunity being the best one can hope for. Most sane people wish to avoid that experience.

[3] https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
Yes! The project leader posted a pic of progress on the Regolith Slack a few days ago. No ETA that I know of but swing by the Slack to stay up to date. [1]

[1] https://regolith-linux.herokuapp.com/
Isn’t the concept of a single staging environment becoming a bit dated? Every recent project I’ve worked on uses preview branches or deploy previews, eg what Netlify offers https://docs.netlify.com/site-deploys/deploy-previews/

Or am I missing something?
Obviously Sam from accounting did this before Excel was t
urning complete.

https://www.felienne.com/archives/2974

https://www.microsoft.com/en-us/research/blog/lambda-the-ult...

No metion of a cell-u-lite version.
I think Ancestry does. I believe there is a lot of innovation happening there, but that is just a feeling.

However, it can be a tough problem. Census takers' handwriting can be pretty bad.

(I often say doing genealogy will cure people's love of cursive. Terrible, quickly-written printing is usually still fairly legible, while cursive can be a series of hopeless squiggles)
Fun! Playing on a 16 hour flight, a fine time killer
The units stop displaying after a certain point. Fonts or glyphs issue?
> We only merge code that is ready to go live.

In their perception, is the rest of tech industry gambling in every pull request that some untested code would work in production?

I work at a large company. We extensively test code on local machines. Then dev test environments. Then small roll out to just a few data centers in prod bed. Run small scale online flight experiments. Then roll out to the rest of prod bed.

And I've seen code fail in each of the stages, no matter how extensively we tested and robustly code ran in prior stages.
More likely it was autogenerated from the API specs, if it hasn't been edited too much you might be the hero who made regenerating it part of the build.
Around here, a training and education plan is required. Some institutions have a requirement on ECTS or another form of "study points" a PhD student must have gathered before defence.

The fact that you are paid doesn't preclude it being a traineeship.
> It's as if Jeff Bezos was walking around with his weiner hanging out but somehow only got asked questions about Amazon's fourth quarter numbers.

Like Lyndon B. Johnson?
That's me when I use languages that don't support circular imports. Can't have circular imports if everything is in the same file. Taps head.
Huh. Another SV darling of the past 5 years ends up being a massive fraud. Sad there’s no real media in this country to cover these stories.
Two other languages I speak refer to noun "child" in neutral gender, so maybe English is the outlier here.
> It might not be zero-sum but someone still has to raise the kids.

In generations past, that was done by women who were counted as not having a job (despite working longer hours than their husbands, 7 days a week). That doesn't need to be the case -- and in fact, dual-income households can create jobs: cleaners, cooks (delivery drivers etc), and childcare. In my grandma's generation, a woman's household duties also included gardening and preserving foods, and making/repairing clothes -- but those jobs have been outsourced so completely that they're now seen as quirky hobbies.
The point about communitarianism in many societies is overall reasonable but generalizing about "indigenous people" is not sound. "Indigenous" is a wastebasket taxon, defining people by what they are not rather than what they are.
I assumed his post must’ve been genuinely awful, based on how dramatic your response is, but it’s been flagged so I can’t see it. I did see a quote below from it which makes it seem pretty harmless and now my gut is that your post is probably more “shocking” than his was…

What’s with the current trend amongst certain members of society of using such extremely dramatic words to describe things that… aren’t actually that bad? It feels like a tabloid or something. “Shocking. Horrific. Abhorrent. Reprehensible.” (Like, unless you’ve been on the internet for a day, you really actually thought it was “shocking”?)

I’m seeing this everywhere now and it’s kind of annoying. It’s like you don’t have much of an argument, and you realize they probably have a point, but you want to silence the opposition, so you downvote, flag, and then write something super melodramatic as an attempt to scare others away from daring to have a similar opinion.

Pro-tip: you are likely reinforcing and bringing more people to the cause you so histrionically oppose.
Reading VALIS trilogy & latter Radio Free Albemuth was a lifechanging experience, about a core lifechanging PKD encounter. The idea of the BIP is a super strong idea among tbis, an atemproal archin dogging us. Very gnostic to me.

There's some Discordianism tie in too I think but Im forgetting exactly where.

Anyhow, highly recommend. Wish this had gotten more votes & traction, oddball as it is for this place.
At amazon your interviewer is supposed to be >= the job level you're applying for.
No. Most languages evolved from earlier languages through gradual linguistic drift. Some languages emerged by putting fluent speakers of two or more existing languages into a shared environment and having them form a common language.

Nicaraguan Sign Language is the closest example we have of putting a bunch of humans who don't know any language into a shared environment, and watching them develop a new language, with minimal influence of existing languages.

Of course, this was not actually a linguistically isolated community. But, for obvious ethical reasons, it is probably about as close to one as we will get.
They mention database as a factor not to have a staging env due to different size, but they don’t mention how they test schema migrations and any feature which touches the data which usually produce multiple issues, or even data loss.
I think a more appropriate analogy is you have a Ford car, and you tell the GPS system to navigate you to a Toyota dealership. Instead of doing that, it prompts you multiple times if you really want to go to a Ford dealership instead.
Suppose I join the workforce at 26, and earn an average of 65k per year while in the <30 cohort, while my friend joins at 19 and earns an average of 55k per year, in this statistic I'll seem better off even though my friend earned 345k more.
> Although Räsänen has triumphantly said she will continue to quote the Bible and hopes the ruling will set precedent for traditional Christians to confidently share their beliefs without fear of mob prosecution, this seems unlikely unless we undergo a cultural shift.

This is peak persecution fetish, given that 70% of Finns declare themselves as Lutherans.
Basically, the code is all there for you to read, and if you can’t, you can’t.
This was covered by CNBC and WSJ. What media sources did you check?
Or, on the flip side, how much do you lose by deploying an 'oops', resulting in customers having a bad experience and posting "This thing sux!" on social media?

I can sympathize with the costs in both time and money to maintain a staging environment, but you're going to pay for those bugs somehow - either in staging or in customer satisfaction.
The tax code isn’t enforced at the cash / low income level.

Thus you can vote for increased taxes to fund increased social spending and not actually take part in the taxation. In fact, you’ll likely even get additional money back filing taxes when there’s no record of your cash income.

Convenient, eh?
Developing legislation like this one on fast-fashion has little to do with management of current events. It’s a very slow and long process done in the background and doesn’t take away focus from energy and economical issues.
This used to be pretty common until applications like Napster took the usecase for p2p to mainstream for copyright music filesharing. Then p2p got a lot more scrutiny. Also, since it is hard to create a search index for wireless devices that may be offline, the mesh network becomes a bit of a darknet.
And front loaders at least spin out more water so drying is more efficient. I suspect there’s less of a difference with dryers.
Co founder of deleteme here. Ama. Fyi to the thread posters, Deleteme removes customer data by default after 6 months. Happy to hear views on what we could do better and examples of companies operating to high standards as well. Thx!
> It's written "the pay check"

Thanks! I updated my comment
nit-pick: They don't block 3rd party browsers, they just don't allow 3rd party browsers to have full access to the device, so they are less performant than Safari, which does have full access.
My logic is that you cannot copyright a fact. It is a fact you released an album, and it is a fact you titled it such. I'm free to reproduce that information, say in a catalog, without violating copyright.
That was my first thought too, but if there's a generator for this it has been lost to time and retirements.
I feel you should instead look for paying jobs contributing to existing blogs that have high readership. Baeldung.com for one example.
I found several members of my family. Though the last names had 4 different spellings.
Nah. Does Android complain if you switch the default browser away from Chrome?

I wouldn't complain about favoring Edge by just having it pre-set as the default when you install Windows. That's fine and reasonable to me, you want some kind of default browser anyway, if nothing else, to install other browsers.

But the OS complaining about it when you switch is stupid. Whereas you can argue that having some kind of browser built into the OS is a reasonable necessity for user convenience -- and you could argue this for other app types too, like image viewers and video players -- having the OS try to convince users to not switch is explicitly anti-competitive.
People who don’t know data, handing it off to someone who doesn’t know data.
This can be part of it (same with other factors that people are discussing) but none of these (even combined) fully explain that 7% difference. I do highly recommend The Pay Check podcast as it goes in depth into all of this and it is far more nuanced than most people believe the problem actually is.
is it easier to type? I can give an objective reason why kebab-case may be easier to type: you don't have to press shift at any point.
Prescient comments from 3 years ago.

https://news.ycombinator.com/item?id=18041106

“The grapevine says this place is a dog and pony show.”

https://news.ycombinator.com/item?id=18042433

“Grapevine is true. What they are doing is extremely questionable. They are billing insurance thousands of dollars for tests that are rudimentary and only look at absence or presence of microbes.”
All of that shows systemic discrimination against men.
At least in tech, I think we're mostly there already, particularly if the applicant has some explanation for it (and even then it's getting rarer to ask about it). With the large amount of no-child/one-child families and waiting until mid 30s to start having kids, it's very common for people to have enough income/savings that they can take a few months or even a couple years off to travel the world or try a startup, or something else.
no you're right, "staging" is gradually being replaced with per-commit "preview". but at enterprise scale when you have distributed services and data, and strict financial controls, and uncompromising compliance standards, it can often be unrealistic to transition to that until a new program group manager comes in with permission to blow everything up
>How does that matter?

Because C is a low level language. It is not a mistake, it by design exposes hardware characteristics. If you don't care about that you probably shouldn't be using C.

I am the first to agree that undefined behavior in C is pretty bad. But this is trivially understood and one of the most basic examples. Can it still bite you in the ass? Sure.

I would prefer it to be implementation defined, but relying on that blindly isn't much better anyway.
This makes sense. With a high-enough release velocity to trunk, a super safe release pipeline with lots of automated checks, a well-tested rolling update/rollback process in production, and aggressive observability, it is totally possible to remove staging in many environments. This is one of the popular talking points touted by advocates of trunk-based development.

(Note that you can do a lot of exploratory testing in disposable environments that get spun up during CI. Since the code in prod is the same as the code in main, there's no reason to keep them around. That's probably how they get around what's traditionally called UAT.)

The problem for larger companies that tend to have lots of staging environments is that the risk of testing in production vastly exceeds the benefits gained from this approach. Between the learning curve required to make this happen, the investment required to get people off of dev, the significantly larger amounts of money at stake, and, in many cases, stockholder responsibilities, it is an uphill battle to get companies to this point.

Also, many (MANY) development teams at BigCo's don't even "own" their code once it leaves staging.

I've found it easier to employ a more grassroots approach towards moving people towards laptop-to-production. Every dev wants to work like Squeaky does (many hate dev/staging environments for the reasons they've outlined); they just don't feel empowered to do so. Work with a single team that ships something important but won't blow up the company if they push a bad build into prod. Let them be advocates internally to promote (hopefully) pseudo-viral spread.
Someone please tell me this is transpiled from a separate project.
Better one good organized file than 100s of folders and subfolders and files and symlinks. I have worked on projects where even after 2 years I didn't grasp the folder structure and just used search to locate files.
The Open University of the Netherlands is, generally speaking, open to the idea of part-time mature PhD students who have a regular job and pursue the PhD 1-2 days a week. We also have regular full-time positions (when the funding deities have smiled upon us); the latter are funded, the former typically not.
Have you watched the cycle of a modern front loader versus an old top loader?

The old top loader basically filled up a big tub with hot water and sloshed it around a bit.

Modern front loaders just incrementally add the amount of water needed as determined by weight. Presumably wouldn’t have worked nearly as well with the available detergents of 50 years ago.
No doubt dozens of devs will throw in their own 10k LOC story here, and yes it's painful to watch so many people having professional cramps over it.

But don't forget society itself if governed by OOM larger bits of text with no referential integrity, no machine to tell you if it's inconsistent, and no way to test anything, other than making humans write more text to each other and occasionally show up in court. The law itself, even parts of it like the tax code, and regulations on various areas, are a melange of text and cultural understandings between lawyers, judges and government. We collect the data for this machine in the form of contracts and receipts, and it piles up in mountains.

As with code, it's not just legal professionals who have to deal with law. It spills into everyone's life, and there's nothing to do about it other than either guess what to do or pay a pro to tell you what to do.