skysight-inc/HackerNews huggingface dataset:
USB Power Delivery spec basically requires sane cables to handle 3A safely, which isn't much of a stretch, because final non-PD charging spec requires safety up to 2.4A.

Given that, even if you allow 2.4A or 3A, this is not a consistent load, and the fastest I've seen pre-fast charging (strictly, not including >5V PD, or PD-esque incompatible (and 'illegal') QC 3.0, and also not including OnePlus's Dash micro-pulsed 5V 4A/6A) is 1.8-2A (tested using many devices, on Anker PowerIQ 1.0 and 2.0 chargers, on modern Anker cables), and it does not even remotely spend most of its time at that peak.

As in, you will never see >2.0 amps in actual practice on a sane but high performance charger, even if it negotiates PD 3A; and if you happen to, it most certainly will not stay there very long.

Also, in the interest of completeness, the highest I've seen my 6T's 4A Dash charger is a smidgen over 3, and it has a thinner (but still thicker and heavier than your average Samsung/Apple grade) stock cable than any given Anker cable still in my collection. At peak speed, it never felt anything but room temp.

TL;DR Don't worry. If your cables or connectors are dangerously heating up at 3A, then they should be deemed faulty and replaced.
I wonder if a compromise could be caching things only if they are widely used across public sites. A browser vendor could use telemetry or crawling to aggregate information about commonly used resources across the web. The browser could cache these resources, even proactively. It's certainly more complex than the shared cache, but it could achieve an end that is broadly similar. Then again, maybe the vendors' telemetry it telling them that first site load is not that common and that the shared cache doesn't move the needle that much. This wouldn't be surprising to find out.
> You're meant to do the actual cleaning indoors in a place with relatively dust-free air.

Well that's a disappointment. I was picturing a friend of mine who goes to burning man to take photos. Poof camera full of dust!
Bugs do get to prod, that’s just reality. If you keep changes small and release often you won’t see many big bugs in production. We typically keep master in an “always deployable” state. If a bug gets found in prod, we either fix it or create a new commit that reverts the commit that caused the problem. If it’s a faulty migration, reverting the commit usually won’t work and we have to fix the bug. For QA we use a mix of automated tests and manual tests.
Isn't the bigger problem that the developer then choses for the user whether to leak information or not?
Yep, that's a fair point. In scenarios where you have made non-backwards compatible database changes, this approach cannot be used. Typically the dark cluster is accessible for pre-flight testing, so you can run tests there to determine if the service is still operating as expected despite the database being one migration step ahead. In your response runbook, you should have a contingency for the scenarios where that happens. (For many projects, the % of changes that have this characteristic are small enough that it doesn't move the needle on the risk profile, but Murphy's law can mess with you :))
Tech is one sector in which some eastern EU people strike it rich without connections to the oligarchs.

One example from Latvia: MicroTik CTO Arnis Riekstiņš [0].

[0] https://en.wikipedia.org/wiki/MikroTik
Just FYI in case you weren't aware - Ableton Live and several other DAWs have this capability built in. It's far from perfect, but great for humming a melody and then quickly turning it into MIDI.
In the US they can forcibly draw blood with a warrant. I don’t think they can without a warrant, but I’m not 100% sure.
Kai Lab Laser Microphone: A Microscope for Sound
>There is a great opportunity at this moment

I wouldn't advice to invest in the company of this guy, but is their money, not mine, so... do as you please. Honestly, I would love to hear that he became billionaire.
It's about 50k employers versus 5k employers, not 500 versus 5.

The real effective argument/consideration IMO is the question of whether the technology MARKET is more prosperous /because/ of the centralization, and therefore leading to higher demand/wages, or vice versa.
>> ... which together own around $2 billion of Apple stock, have published an open letter urging Apple to think differently about ...

Lol, there is a small difference between few shares and few $billion worth of shares. Latter' voice is easier to be heard.
That's not something new, that's how it is for decades and has nothing to do with agriculture production itself.

It has mostly been a way (among others) to raise, at least virtually, the purchasing power of smaller european countries and make this closed system work.

There is an 80s greek short film in form of documentary that shows how they used to discard all that production, subsidized by the EU, because there was simply no demand for it.

Sadly it's all greek and no subtitles around but pictures will tell the story: https://youtu.be/o25DPfZeFxI
This is a false choice and a different one than I suggested. You would have to consider this scenario also:

A released tax records
B released tax records
C didn't release any records

FWIW, I've talked to an accountant about the idea of Trump revealing his tax records and the bottom line is that they would be sufficiently complicated that there is no possibility that the average person would be able to interpret them accurately, so you'll be left with the spin from the various media organizations, hardly a source of objective truth.

So I would assert that requiring candidates to release their tax records doesn't actually provide any useful information for a voter.

Remember that Trump's tax records, are already examined by the IRS and I believe have been audited. So there shouldn't be any question of illegal activity being hidden, unless you want to assert that the IRS can't be trusted either.

There are also other concerns about tax records revealing information about 3rd parties. And finally tax records aren't really a useful way to understand the intricacies of a business. If you are really interested in that you would want the audit report for the underlying business and not just tax records.
AnandTech makes the worst list, with 469 to 71 requests and 4.5 MB to 0.45 MB page size: https://webtest.app/?url=https://anandtech.com
Well, highly unlikely that such an error will arise. If it does and you know that you actually need to roll back then most likely something else is wrong.

But again, I also saw the other comment about how "Dogmatic" my approach is. I wouldn't say it's dogmatic, idealistic - yes. But not dogmatic. There is a place and time for anything and roll back can STILL be useful when you don't trust the system nor the code base (as I pointed in my other comment, rollbacks are useful with legacy systems and systems that you have to maintain that were build by outsourced teams).

Well also roll backs is the first thing you think of when you join a large company as a director of engineering to support systems you never touched before.
Don't throw the baby out with he bathwater. Hardware is hardware and their wireless APs are good, their switches suck, 2 minutes of downtime with any settings change?! Their controller software is a marketing gimmick trying to silo you in. Still, its an easier battle if you're armed with the right tools, and their APs are a dream compared to most others.
I would need to find data to back this up, but my sense is that much of the political difference can be accounted for with demographics.

Tech workers as a group are younger than the population at large. Tautologically, the group excludes retirees, and as the industry has expanded over the past decades, it's growth has been fueled by hiring recent college graduates. Lower ages and higher levels of education are correlated with left-wing views in polling results.

If you controlled for age and education, I don't think you would see any ideological distinctions between tech workers and the rest of the population.
I'm having difficulty determining how this impacts subdomains.

From what I can tell a.example.com, b.example.com, and example.com would all have their own caches, correct?

We have multiple (sub)domains a|b|c.xxx.example.com that share a template, and therefore resources (we're a .edu). If we're now looking at an initial load hit for all of them, that may impact how we've been setting up landing pages for campaigns.

I can't see us completely moving away from a CDN because of the other benefits they provide.
More like used to code for anti-business, whereas presently codes for nativist.
Hearing that people are pressured to buy it, to ensure its success, further diminishes my confidence in it. I agree that 5% is pretty minimal.
I think that it's not actually possible to know anything, and your only real options after recognising that are to reject the pursuit of truth entirely or fall back onto probabilistic models instead of binary beliefs. Not knowing whether or not Snowden is a CIA asset leads me to the question, "how likely is it that Snowden is a CIA asset?" As to why we should care, here's another question: "if Snowden were a CIA asset, how would that change my future behavior?" If it wouldn't change your future behavior, carry on not caring. If it would, then ask yourself "given that I may be wrong about Snowden being a CIA asset, which way would I rather err for an optimal risk/reward ratio?" Then you consider all three answers, and decide how to act in the future despite never actually coming to a conclusion about whether Snowden is a CIA asset. Maybe you think the risk of him being an asset is so low that you don't mind risking the chance that he isn't, or maybe you think it's reasonably likely that he could be an asset while not believing that your personal risk from being wrong is worth worrying about. Or, maybe you change your behavior.
What part of the business model do people not like?
Some jobs do require people that can solve “hard problems”(tm) at scale and can’t use off the shelf frameworks. But I’ve heard (but never experienced) companies looking for a developer for a bog standard yet another software as a service CRUD app or some bespoke internal app who still think they need to do an interview process like a FAANG. That was where my dismissive attitude toward that style of interview originally came from.

Over the last few years I have kind of seen the light of day. When you’re hiring at scale, you do need a standardized process. On the other hand, while I haven’t spent a day studying any really complicated algorithms[1], I’ve spent just as much time knowing how to talk the talk of a “cloud native enterprise architect”, and it took me awhile to realize how much of a hypocrite I was being for saying that I would never jump through the seemingly artificial hoops of studying algorithms.

[1] that’s not entirely true. I spent a year or two maintaining a bespoke compiler/IDE/VM for Windows Mobile.
You are asking a very generic question without really stating what environment you are using. The ability to "rollback" is really a statement of how you have defined your deployments. A good environment really should have a few things:

* A version control system (ie. git) that has a methodology for controlling what is tested and then released (ie. feature releases). If you want the ability to revert a feature, you need to use your version control to group (ie. squish) code into features they can can be easily reverted. Look up the GIT Branching Model [1]. It's a good place to start when thinking about organizing your versioning to control releases.

* You should be able to deploy from any point in your version control. Make sure your deployment system is able to deploy from a hash, tag or branch. This gives you the option of "reverting" by deploying from a previously known good position. I would highly suggest automating deployment to generate timestamp tags into the repo for deployment so you can see the history of deployments.

* Try to make your deployments idempotent and/or separate your state changes so they can be independently controlled. If you have migrations, make sure they can withstand being deployed again, ie. "DROP TABLE IF EXISTS" then "CREATE TABLE", so redeploying doesn't blow up. If you need to roll back, you can rollback as much as you need to the point you want to deploy. A trait of a well designed system is it needs few state changes to add new features and/or those state changes can be easily controlled.

* Have a staging system(s). You should be able to deploy to a staging system to verify the behavior of a deployment. It should be able replicate the production every way except in data content. Ideally, should also build this from scratch every time so that you can guarantee if production dies hard death you can completely reproduce it. A great system will also do this for production, bring it up for final testing, and then you can switch over to it once tested.

Notice the trend here is to breakup the dependences between how, what, and where code is deployed so that have many ways to respond to issues. Maybe the solution is small enough to just make fix in the future. Maybe it is create an emergency patch, test it on a new production deployment and then switch over. Maybe it is so bad you want to immediately deploy a previous version and get things running again. All of these abilities depend on building your system such that you have these choices.

[1] https://nvie.com/posts/a-successful-git-branching-model/
“I really like systems that do one essential thing and do it well. Good examples are Dropbox and Twitter. Dropbox just works. Twitter has a no fuss 140 character tweet box. Simple, easy to understand and minimalist.”

They used to... Maybe even when this was published in 2014.
My mum ran the computing department in the Education Faculty at a university in Australia from 1976. I was 6 years old then and would 'help' her at work during school holidays and sometimes when I was ill.

My fond memories included:

- Discovering the paper tape machine.

- Writing stories on the card punch machine, one line per card.

- Pressing buttons on the massive card sorting machine when noone was looking.

- Walking to the Computer Centre to pick up the output of my mum's previous day's coding. If she was lucky, there was a thick stack of fanfold paper in her pigeonhole. If not, just a couple of pages with the error message.

- Around 1978, playing with her HP RPN calculator. It had an inbuilt reader for programs on small magnetic strips. I typed in the example Moon Lander program from the manual and spent a few hours figuring out how much thrust was needed to land without crashing.

- Some time around 1979 they got a computer with a video display and a lightpen. And a 300 baud acoustic coupler.
Even if the browser could read your mind and pay the perfect amount for content automatically I'm betting the model would have lower overall margins than the current model.
Bullshit Generator
BullshitGenerator
How does it sent back data without revealing the source IP address? :)
Libertarianism started on the far left - The "original libertarian", the anarcho-communist Joseph Dejacque, attacked Proudhon, the "original anarchist" for being a "moderate anarchist, liberal, but not libertarian" for his regressive views on women.

Right-libertarianism was an attempt to unite the libertarian parts of the left with socially liberal elements on the right against authoritarian ideologies; their main distinction are views on property rights and on whether or not de jure vs. de facto rights matter most.

As such it is often hard to place people with libertarian views firmly on a traditional left-right axis. You'll find a variety ranging from the far left seeing private property as illegitimate restrictions on liberty (Dejacque applauded Proudhon's famous "property is theft"), to right wing libertarians who see private property as fundamental to liberty (often invoking e.g. Ayn Rand, Hayek and von Mises), to people in between who want various trade-offs (e.g. mostly protecting property rights but seeing a need for some level of welfare provisions)

My experience is that engineering in general tends to have a lot of socially liberal people, many of whom could probably be described as libertarian, but that the left/right position of their views is often a lot more ambiguous.
I work at one of the companies often cited as having very left-wing employees, and my impression is that the media heavily overplays this.

I would instead say there is a small but very active group of employees that push a left-leaning political agenda, and most of these people tend to have non-STEM backgrounds (I don’t know why this is the case, but it is what I have observed). Most of the software engineers and data scientists that I work with do not really enjoy discussing politics (at least at work) and have views that lean more libertarian. Four of the people I work with are closet conservatives, and there are some issues I would say I am conservative on as well, but no one ever really brings these topics up at work.
This is a useful concept. I also thought these lines were insightful:

New features mean new sales opportunities, good for the company but not good for the user.

The problem with adding features to MVP is that when we ship more complex products like complete operating systems that are packed with programs, the complexity of the individual programs contributes to the complexity of the whole.

Not sure how to solve that particular problem though.

This made me think of a blogpost linked on Hacker News when Joe passed away: https://github.com/lukego/blog/issues/32. This part seems relevant here:

Joe wrote amazingly simple programs and he did so in a peculiar way. First he wrote down the program any old way just to get it out of his head. Then once it worked he would then immediately create a new directory program2 and write it again. He would repeat this process five or six times (program5, program6, ...) and each time he would understand the problem a little better and sense which parts of the program were essential enough to re-type. He thought this was the most natural thing in the world: of course you throw away the first few implementations, you didn't understand the problem when you wrote those!
> the left wing tends to be more science based

Sorry, but the left wing is not "science based" at all when it comes to the social sciences - their attitude to social issues is very much religious in nature (see any mention of "socialism" and "wealth taxes" as perhaps the clearest and least controversial example) and "the antithesis of the enlightenment". Both sides are playing this game.
How do you reference locations in buildings then? "Over next to Accounting" only works if the person already has knowledge of the office layout and only for one floor.

Facilities generally refers to areas of buildings by floor and cardinal direction.
Meanwhile, at my company, our HR has decided to cut sick leave to the CA state mandated 3 days minimum.

So now we have people coughing their heads off at work and spreading flu everywhere. How efficient can you be I wonder when you are sick? Yet people seem to take pride in the fact that they are still working while battling an illness.

I'm honestly surprised they tried this in Japan which has a super rigid work structure.
"Seventy-seven percent of the Medicare decedents' total healthcare expenditures occur in their last year of life, a staggering 52% in the last 2 months, and 40% in the last month."

That's a lot worse than I thought.

The inverted pyramid age distribution mentioned in his article is already happening in some countries
In general the ability for HTML to reference resources outside of the current domain seems to be a privacy and security nightmare. xss attacks, privacy leaks, adtech tracking cookies, etc.
There are many reasons, IMO.

1. The US has almost 330 million people; Europe has 740 million - but we're spread over so many different countries / policies / cultures etc. Hell, eastern Europe was locked out up until 30 years ago, and didn't stat to see industrial prosperity until 20 years ago.

2. USA had a massive advantage after WW2, while Europe was still in shambles. The rebuilding of Europe wasn't really completed until the 50s and 60s, at a time when the US experienced its golden age of industrial development.

3. More rich people and more investors compared to Europe, from earlier on, coupled with excellent schools that could produce and feed talent into the industry.

Sure, we here in Europe have had excellent schools, but nowhere near the financial backings. In many countries, financial backing of tech and companies have been a gov / state affair, which in turn can be extremely limited compared to private investors.

etc.
I deploy to Kubernetes with Helm, so I just do an Helm rollback.
The internet itself was in large part created by the us government.
I'd love to get a bunch of the UI engineers out into the rural areas where their gear is used, to remote work from there for a while, so they can see how badly it caters to the needs of those who need it most, and that they can go back with some easy to implement and much needed improvements.
If we split up google what would likely happen is that youtube and gmail would simply die

Or compete on a level playing field with Vimeo, Fastmail and so on. Everyone wins if Google is split up. Even Google shareholders, who will finally get some nice dividends when the ad business money isn't being diverted to prop up the rest of it.
I think there are two categories of developers who would use that. One is smart, experienced people who have correctly evaluated both security and performance concerns and decided to turn this on for a specific narrow case where it's truly valuable to speed up first-time page loads.

The other is people who want things to go faster and flip a lot of switches that sound fast without really understanding what they do, and then not turning off the useless ones because they're not doing any real benchmarking or real-world performance profiling. This group will get little or no benefit but open up security holes.

Given the declining usefulness of shared caching (faster connections, cheaper storage, explosion of libraries and versions), I expect the second group to be one or two orders of magnitude larger than the first.
I guess that's the point I was making about sense of direction. I have never had the experience but two of my kids get confused very easily, the third is like me and seems to always know location and direction.
> Start talking loudly at your job about starting a side business, being frugal and retiring early

Where I work, we have a Slack channel dedicated to this kind of talk, and most managers are in it. It’s been just fine.
>Driving 40 miles/hour anywhere with pedestrians/cyclists is incredibly dangerous. If hit at that speed, a pedestrian/cyclist will almost certainly die.

The former doesn't follow from the latter. I mean, by leaving your house, you might slip and fall and die; that does not mean leaving your house is incredibly dangerous, because we have to account for both the severity of the outcome and the probability of it.