skysight-inc/HackerNews huggingface dataset:
> Ms Wang and Mr Casado have suggested that firms should think about building their own private clouds to keep costs down.

It shouldn't be called a "cloud" in that case. It should be called a "fog".
Data that exists from before? I suppose you could look at fire issues or structural collapses from before there were strong building codes, but these codes were generally developed specifically in response to issues like fires. In the US (colonies, 1600's) building codes emerged for exactly this reason. Later, George Washington & Thomas Jefferson were instrumental in pushing them further. [0]. They continued to evolve in response to things like massive crowding into cities in the early 1900's by new immigrants living in overcrowded and unsafe buildings [1]

They continue to evolve now, with fire deaths dropping significantly over the past 40 years despite population increases as construction methods and building materials get better [2]

I think it's fair to say that there's a legitimate safety concern in allowing structures not built to normal codes for a permanent structure to become permanent without some sort of review. Although I think that simple street dining-- absent these structures that weren't intended to be permanent-- should be much less of an issue. If a restaurant just has tables & chairs out there then I don't see much of an issue as long as they don't obstruct normal pedestrian traffic.

[0] https://www.creia.org/the-development-of-our-building-codes

[1] https://www.tenement.org/blog/lives-gone-in-a-puff-of-smoke/

[2] https://www.nahbclassic.org/generic.aspx?genericContentID=34...
No, I don't think so. I've answered elsewhere in this thread: when making the submission, I thought my comment would stay with the initial post, and yes, I wanted the bump for including a link in the submission. The linked page is a decent page, and a halfway-there example of what I'm looking for.
While I haven't read it, I listened to Will Larson's interview on SEDaily (before the show em... changed). It was quite interesting and it was in my reading list since then.

The interview itself is here: https://softwareengineeringdaily.com/2020/10/29/staff-engine...
> My relationship with my manager was much more of a peer partnership than manager/IC.

To all the managers out there please make note of the above. Do yourself a favour and please give senior engineers enough autonomy and freedom.

At my previous place I managed a senior engineer and made it amply clear to him that we are peers. Between us my job was to handle all the bureaucracy (including scheduling meetings, finding meeting rooms etc.,) and his was to be the team's tech lead.
We actually are setup with a major hardware vendor where they roll out that 10x capacity ahead of time, and we only pay for it when we flick on the switch. Otherwise, it is powered off/Standby just sitting there drawing minimal power resources if any.
What a great idea. We need more of this sort of thing.
Air travel is good and we should want more of it
The problem is social and bureaucratic. Business unit X wants to buy software that solves a certain business problem. Oops you missed this annual budget cycle that is tied to hardware purchasing, better try again next year. Or, great we'll help you buy that hardware, but there is a 3-6 month leadtime. So many organization had an adversarial relationship to their IT group. Even when they didn't want it, the structures prevented solid partnership. On the other hand, SaaS, or self-service cloud (either on-prem openstack stuff, or real cloud aws/gcp/azure) allows groups to manage their own resources while still having a central coordinating function.

Working in enterprise software, I was am always surprised when I find a killer feature may not the functional value of something we've built, but that fact it works around some internal disfunction of operations between internal teams.
Ask HN: Anyone have arthritis in their fingers? How to keep working with it?
The past month I've been dealing with the joints in three of my fingers on one of my hands giving me pain when I bend them, and it kind of feels like maybe the edges of the bones are rubbing against each other (especially painful when I try to pinch or close things, like ziploc bags).

Actually first noticed when I was playing games with the fingers on WASD keys (for movement) and now I've switched to a controller, possibly for good, but now typing for extended periods when programming is bothering them.

I haven't confirmed that it's arthritis yet, maybe it'll still get better on its own, but assuming it isn't, is there a way I can continue to write code (and write comments on HN and whatnot :) and yet protect them and let them heal? Should I look into some ergonomic keyboards? Try typing one-handed for a while?

For those who definitely do have arthritis, how do you manage it as well as work?
I'm surprised nobody's mentioned yet a key (admittedly not only) part in making the US so polarized: first past the post voting system which inevitably leads to a two party system. Good luck having nuance in that system. It literally pits people against each other in two umbrella teams. The internet's echo chamber mechanic has only amplified this.

People need to challenge their own beliefs more often. You vote Democrat? Whatever. Who do you vote for in the primaries? Nobody cares... they should.

It might open the eyes to the foundations of disagreement not being dehumanizing.
What Is Transfer Pricing?
I had that same thought at first, but I think they were trying to do a tie in for enterprise SaaS. They mention Hashicorp as well.
But why is it hard or expensive. These spacecraft can already withstand earth gravity, because we built them here on earth and they didn't collapse during construction. They typically already have lifting points to lift them with a crane too.

Cable is cheap and light.

Getting the whole lot spinning can be done very slowly over many days with the same ion thrusters that are used for stationkeeping. Total delta-V isn't very high. Total fuel used isn't very high either.

The only disadvantage really is that you lose most of the benefits of zero-G. for example, long running experiments requiring zero G. You also start to need walkways and paths. The ceiling of rooms becomes dead unusable space. etc. Docking new spacecraft requires stopping the spinning, which takes many days. Comms antennas and solar arrays get more expensive.
Uh yeah let’s equate that to an armed insurrection that killed 3 people and would have overturned a presidential election if not successfully repelled, and that has been defended or denied by Republicans en masse.

He was condemned by both parties, and was not part of the mainstream liberal movement.
The vast majority of titles in tech confer more prestige than deserved, because there's no downside to a company handing them out like candy. I don't look at it as a portability issue, the incentive isn't to be accurate to begin with. Inflated seniority is just a perk they can offer that doesn't cost them any money, so everyone offers it. Titles across the industry are meaningless unless you're calibrated to that company's levels.
Well above. Witness the rising sea levels caused by the glaciers melting.
Yes, no.

Yes because it's a very nice language, with lot of bells and whistles. Javascript and Java integration are nearly perfect, allowing you to have a access huge ecosystem.
No because even though there's progress regarding the error reporting, it's not always simple to parse them. No because you'll have to understand way more Java than you may be willing to.
No because it's not Lisp per se. It's nearly a different beast.

Would I recommend it? YES. But know that "Here be dragons"
Three above this story on the front page is an article called "The Web Is Fucked", complaining about how there's no character on the web any more, and lamenting the 90s, Geocities etc. etc. I'd say this story refutes that one.
I had the inverse experience: I worked for a startup that gave literally everyone in the engineering department the same title of “Senior Software Engineer” in the HR system because they had one boilerplate offer letter used for everyone.

I was a manager-of-managers, but officially I was a “senior software engineer”. Burned me badly on a couple reference checks, until I specifically started explaining the situation during interviews.
How do we treat Covid before hospitalisation? I just caught it at the weekend and feeling pretty crappy. I'm not aware of any particular treatment I should be taking.
From what I know as not being a professional doctor, I would say that it appears to me that viruses get less dangerous over time, not more dangerous. This appears to be because viruses that are overly dangerous kill off their hosts too quickly, limiting their ability to spread, whereas the milder forms don't kill their hosts as easily and spread more broadly, building immunity against the stronger variants over time.

Edit: The result of this, if you look at previous diseases that have plagued humanity (see Black Death), is a high initial death count when the virus breaks out, but the death rate declines as the milder variants spread and people survive them, building immunity to stronger versions, until eventually the virus mostly disappears.
Right but if anything that's part of the argument. They haven't even started playing financial games to optimize share price yet because they haven't had to.

They have a lot of runway to pump those numbers when they are ready.
PRN was for the printer.

AUX is for "auxiliary" (aka "misc."/"other") device - i.e. any other bit of unspecified random hardware you'd managed to hook up with a custom driver by yourself.
People also seem to be overlooking the benefits of downward optionality - you effectively transform a fixed cost (servers and staff to run them) into a variable one, that you can flex down cheaply (no long-term leases or redundancy payments). It lets you test things out (e.g. entering a new market) and cheaply wind them down if they don't work out.
I also just received this email, and also have no idea what it means
It is relevant and should not be left out.

"He broke tax law not declaring income."
"Oh well where did that income come from?"
"He is Chinese spy, but that's not relevant or important"
"Oh... ok. So then, didn't he also break some other laws by spying for China?" "Yeah maybe, but we don't want to explore that."
I don't, sadly. It was a complete accident. I have MS and take Tizanidine for my muscle spasticity; being able to imagine things is just an odd side effect. I also can't imagine there's enough formerly-blind people with MS to test this on with science. (I'm a statistical oddity!)

One side effect of tizanidine at higher doses is hallucinations, so it would seem to do SOMETHING with your visualization center, but idk what.

For your autistic difficulties, I'm curious if finding resources for people that have gone blind/deaf might help. I know it sounds weird, but as a visually impaired person, we thought I had Asperger's for a while because I literally couldn't see body language well enough to read social cues, and I found it really helpful to look up information on how to 'read' that information elsewhere. Likewise, if somebody goes deaf, I'm sure there are lessons on how to do things like read more into body language. It just might help explain a lot of things that neurotypical people take for granted.

Also biology: I find it really helps me to remember that humans are sacks of hormones and that sometimes when they're silly it's not me being wrong. They might just have gotten a surge of adrenaline and had a knee jerk reaction, or they might be overstimulated. I know I tend to forget humans are embodied and expect more logic out of them than their bodies will allow.
You're right, I didn't define 'relevant', though I appreciate the Congo story. Examples, since you asked:
1. I don't care about Miss Universe (one of the stories in the link).
2. Sports are low value except for championships.
3. I want Covid stories batched where I can look at them if I want to look at that, but where they otherwise don't clutter everything.
4. The Midwest tornadoes are relevant, but human interest stories about one of the deceased candle workers are not.
In my experience the issue experimented technical contributors have with politics is not savviness, it's managing frustration. Unless you enjoy playing politics for politics sake and value the grind of improving your position in the system, the mix of ineffective compromises and letting things rot because the blame will go the right way tends to wear you down in the long run.
There is a small caveat to that as I mentioned app center requires you to enroll the devices into Intune which is the Microsoft MDM which might not be possible to do in all cases.

If that is an option that is agreeable to you and your users then using app center does provide a better experience than Google Play in my opinion.
Don't forget there's also the millions of people dying from fossil fuel-based air pollution every year! https://lrb.co.uk/the-paper/v43/n23/david-wallace-wells/ten-...
Simple Steps to Become a Senior Developer
Health care records seem to be outside this vision as they are inherently connected to the physical world yet invaluable for both epidemiology and marketing.
Others may have other preferences. This is what worked for me. I just find S3 quite cheap for storing a few (tens of) terabytes plus some glacier archives. For data I often want multiple locations redundancy and encryption. That gets more complicated than what I can save.

I guess the equation changes when you have more data or looser requirements. That's actually my point. It's very hard to recreate the whole AWS experience, but it's quite possible to pick any piece and do it much cheaper.
What's nonsense about it? These aren't raccoons digging through people's trash and scavenging, they hunt wildlife for food and are protected from everything that would hunt them in return, even getting food and water and potentially shelter in the worst months.
At faang-level tech companies. Total comp. Base is likely 30% of that. By the time someone reaches principal they've likely been at the company for 5+ years which for many is long enough for equity to snowball such that previous years' grants are vesting at 5x their grant valuation. (Or if they're hired on as principal they're likely leaving similar comp on the table so hiring managers have to make up for it, usually with future-vesting equity of similar current valuations.)
At one of my jobs, all the developers were given the title "Member of Technical Staff" because our boss had worked at a particle accelerator (he had a PhD in physics) and that's what the scientists running experiments had on their badges. He did it for morale, and it probably did make us feel a bit fancier while we were writing Grails and GWT code.
The past few years have made me feel sour on how many organizations run cybersecurity in general. The industry is full of individuals who do not understand the tech they are protecting, and often they barely understand the security tech they use daily. A lot of places are simply doing compliance check-marking and barely have a shred of technical aptitude. They struggle with basic fundamentals like inventory and patch management. It is an industry that is hard to stay upbeat about if you are looking at anything larger than how it benefits your personal paycheck. If you want to get insight into the reality of how the government operates, just look at GAO reports, they are alarming: https://www.gao.gov/highrisk/ensuring-cybersecurity-nation
I'm not an economist either. It just seems the business cycle has been a persistent feature of capitalist economies.
Definitely. It's got great learning resources like Clojure for the Brave and True, and it's very practical. There is good support for using it in server-side work, web apps, both frontend and backend, and now even lightweight scripting.
cue the "it's just the flu!" army.

on this end, I do not want covid at all, straight up. I will keep wearing my N95 to all the dirty looks I keep getting and boost as much as the boosts are there.
Yes, but that's just because a design goal is for modest computers to be able to fully participate in the protocol, and the low number of transactions was the best they could do. They've also been planning to scale since early days. Here are some of Vitalik's blog posts on scaling back in 2014:

https://blog.ethereum.org/2014/09/17/scalability-part-1-buil...

https://blog.ethereum.org/2014/10/21/scalability-part-2-hype...

https://blog.ethereum.org/2014/11/13/scalability-part-3-meta...

And here's one of his 2021 posts, in which he talks about the importance of regular users being able to run a node, but says a million tx/sec should be achievable:

https://vitalik.ca/general/2021/05/23/scaling.html
Umm, just mangle it in the storage layer?
The thing that I just keep coming back to with all this Web 1.0 rose tinted glasses is that "no one" used the web back then. Many people _did not_ have personal web pages. Only a few individuals did, if you were lucky/smart enough.

It's fair bemoan about the state of the web now - there's many faults, but it's considerably more accessible than it was before. There is more information available that's, and more opportunities for people on this new web, and its all (ultimately) easier to access
I’ve heard that it depends on the virus. Some become less severe as they become more contagious, but sometimes their severity stays the same.

Naively, you’d think selection pressure would decrease severity, because severity is not how viruses spread. However, if (some of) the same mechanisms that ar causing the virus to spread better are also responsible for (some of) its severity, then things may not really get better over time —unless our immune systems themselves adapt, but that generally requires a first infection…
That would only work on some. The skeptic I know acknowledges that the world is getting warmer but doesn't believe this is a problem. I do believe it is a problem and find it hard to convince him.
He really glosses over how he uses GPT-3 to correct the text...
> I must work to live

Are you saying that you do not work voluntarily but under duress, e.g. to avoid starvation?

In any case, just to be clear... are you blaming our economic system, capitalism for this? I am asking, because it is a common thing to do; blaming capitalism for everything that is the fault of the Government. After all, capitalism is about working less to earn more. This alone is in conflict with "work to live". Plus the market is a voluntary concept. The Government interferes with the market, and creates all sorts of horrible financial incentives. We have an interventionist economy, and it is not doing too well, I agree with you on that. People should support each other more. Our web of social support is not satisfactory. We have the technology to "retire" many people, but if we do that, they cannot get money, and not getting money is a problem indeed. The Government "creates" all sorts of useless jobs we could do without just so people can earn money. We should be able to work less, and live just as well, if not better; which is what capitalism - our economic system - is about.

That said, existence has externalities. Humans take food, water, produce waste, damage things, require shelter, etc. and someone has to cover that and you could always work to cover it or go join a commune to cover it if your Government has not made it illegal.
Depending on the design of the flash, the storage temperature, and other factors that data can rot.

Please see [1] for one source.

[1] https://www.ibm.com/support/pages/flash-data-retention-0
What skills would you say are nessecary prerequisites for understanding this material?

I'm a writer, and in the past I have had success making poems and shit via messing around with various NLP tools like speech to text software and Google Books ngram viewer, but I've run into situations where I wish I could do something that isn't supported by the application.

Could this course be a good place to start? If not do you have any recommendations? I don't really know how to code but am comfortable using a command line interface.
I can get a dedicated baremetal server up and running in 10 minutes after paying for it (some can get it done in seconds).

Scale does NOT matter for the vast majority of usecases. For example, the parent comment talked about on-prem exchange server.
Skeptics gonna skeptic, no matter what now. Only thing left is to prepare for the crashing and brutal transition, and explain things to skeptics but not for their benefits but in the hope it tips off in the right direction the hesitant people who are silently listening to conversations. Like with covid.
You are right about the trade-off: A more infectious, less deadly virus is the natural evolutionary path for them.

But about the breeding ground, not really: If one day some super deadly variant evolves, it's not popping up in all of the infected hosts at the same time. It'd still need to infect everyone from scratch, and since we all have our guard up right now, it'd definitely have an incredibly hard time doing so.
I mean, I get it, and I agree. But to rail against Social Media and SEO in one breath, and then to have Twitter optimized headers and SEO stuff right at the top of the code seems a wee bit hypocritical.

<meta name="twitter:card" content="summary_large_image" />
<meta property="twitter:image" content="https://thewebisfucked.com/assets/images/feature.webp" />
<meta property="twitter:title" content="The Web Is Fucked" />
<script type="application/ld+json">
{"headline":"The Web Is Fucked","description":"The web is fucked and there’s
nothing we can do about it. This is a manifesto by Kev Quirk looking back
t Web 1.0 and why it was better.","@type":"WebSite","image":"https://thewebisfucked.com/assets/images/feature.webp","url":"https://thewebisfucked.com/","@context":"https://schema.org"}.
</script>
<!-- End Jekyll SEO tag -->
Indeed, small sample size!
It's basically consultingware for IBM/Redhat. It tries to be everything you could ever possibly need, the interactions between the components are brittle, and it has all the complexity of a huge k8s deployment except your ability to affect what's going on underneath is like trying to control an angry beehive with a 20 ft pole.

Think Urbit but for sysadmins and you pretty much get the vibe.
BoA’s scale of operations are probably orders of magnitude larger than most other businesses.
I feel like the overall direction of the software world has been aiming to maximize developer productivity -- at the expense of rock solid reliability -- for quite some time now.

You can think of garbage collection as being an early admittance that it's far simpler to just clean things up in bulk on a periodic basis, than it is to keep track of every resource you're allocating, and making sure that it's freed at the earliest possible time.

Restarting a service after it's been running for hours, because of memory leaks, seems like a broader implementation of a similar notion... despite best efforts, sometimes services just accumulate cruft, and so long as you can properly drain clients to another server before restarting, is it really that bad to have to restart it periodically? I think of it as an extra long GC pause that frees everything up.

There's a sweet spot where "good enough" really is good enough, and I don't lament it all that much.
"I am hoping that it would be some kind of trade off that the virus makes in that it can spread more easily but not be as severe..."

I've definitely seen outlets postulating that the endgame for COVID-19 would be it doing exactly this— becoming way more contagious but way less severe, basically a just a kind of cold. These "final" variants would quickly spread everywhere, choking off the supply of new hosts for the more deadly variants, effectively achieving herd immunity.