skysight-inc/HackerNews huggingface dataset:
Could be, but that is a separate problem. For example places I've been in Europe have multiple competing services, even when Uber is present. But that's because the typical Uber business model where drivers are not professional drivers is banned most everywhere.
If any dev is here, I'm on IPFS and can't seem to search, getting console error:

> Uncaught ReferenceError: passQueryToResultpage is not defined
I agree with the both of you, so here is my simple version:

Companies rely on the fact that you stay a couple of years at least. So if you want to make good deal, you need to switch jobs more often.
Can someone confirm that apple here are trying to get other companies to pay them if that other company offers its customers a subscription service?

What is apple offering the other companies for the pleasure of paying apple?

I feel like I'm missing something.
I recorded a podcast with Tudor Gîrba on Moldable Development as well if you prefer to consume things that way.
https://www.infoq.com/podcasts/tudor-girba-moldable-developm...

The broad thesis, that we spend way too little time thinking about how we understand our systems, is one I'm in strong agreement with.
A lot of (most?) already super rich people monetize everything they can to the max. So I don't believe it's out of a desire to simply quit working. I think it's more about making money for the sake of making money, also known as greed.
If you follow Nintendo steps, what happens is that anybody will hit your Switch directly if they connect to any port on your public IP. If some services on the Switch are running and listening on the Switch public interface, they will answer. If one of the those service has a security vulnerability, you are in trouble. You just don't want to expose your entertainment devices to the whole world like this.

This setup could make some sense for a DMZ but not a gaming console connected to your local lan.
I am vastly more scared by surveillance and data acquisition, regardless if that would be domestic services or US ones. Still true that you should think about your preferred solution to tunnel out of the EU, preferable with a service outside of your legislation.
RE: intelligence agencies - https://twitter.com/wingarscarlett/status/148160261830488883...

One of the replies to Ben’s tweet includes a diagram and references to the NSA’s RJ-45+Ethernet capturing device within the RJ-45 jack itself.
> unless your business model is to abuse your customers' personal data. Then it might be hard.

It's not only your business model, but also the business model of all third-party services you are using on your site.

Also, part of the reason why it's not that hard is that the GDPR is pretty much one of a kind. Imagine the US and maybe some countries in Asia having similar but different implementations of privacy laws, and you having to work with them simultaneously. Or even different laws in each US state (CCPA?). Imagine every country requiring you to store user data only the user's country of origin, thus managing a separate database for each country.
AngularJS is a different framework. They are not the same and i think that was very clear from the start.

( I've written webapps in both AngularJS and Angular)
Reliability requires some fact checking. Rather impossible in this case
Totally agree. That's kind of what I was going for when I described the hypothetical "true-strict" mode: don't allow the code I'm writing to do bad/unsafe stuff.

And yes, I really wish that TypeScript's non-null assertions actually included a runtime check. Type casts can't really do anything at runtime without a definition of what "being type Foo" actually means, since the types are erased, but you can definitely check if something is null or undefined and throw an error.

I think it would be fair to have the non-null assertion do a runtime check, and if you want the non-null assertion with no runtime code, just use a type cast.
Because the same author wrote a review of that ran on the same day, and seems to have written this as a companion piece to the review. https://www.vox.com/culture/2022/1/10/22872347/station-eleve...
That's possible, but if Amsterdam has big name tech companies, Booking and Adyen are definitely it, so perhaps it makes sense that they pay more. Sadly I'm not that interested in working for them; Booking uses way too many dark patterns for my taste, and I've been to Adyen's office, and they had dozens of programmers working in a single noisy room. That didn't appeal to me at all.
Sounds like you are describing “institutional knowledge”. In addition to good documentation, an org needs to maintain employee retention, so you have people that know the what and why’s of all the automated processes you’re seeing.
You can also use a USB Ethernet dongle with the Wii (that’s exactly my set up in fact).

This obviously doesn’t help DS users though.
In the article he describes the device as "terrifying" and "cursed". I think he gets it.
Of course, there are very cold places where much of the population happily bikes. See here for example: https://www.youtube.com/watch?v=Uhx-26GfCBU&t=800s
(Author of post)

They advertise this as a network appliance, so it makes sense that they use Debian since being able to install packages via things like apt makes the whole experience much easier. A lot of career network engineers are not that savvy with sysadmin type roles, so something like buildroot would alienate their market a little
> If I were to refactor it at this point, it's really only to pander to my own ego, which probably isn't a sensible business goal.

But it could be fun! You are aware of the risks, so if you'd really love to do it, knock yourself out! :D

Another perspective: It has occupied your mind for such a long time, why not get rid of it?
What do I think of it?

Literally nothing.

He made a thing. People enjoy it.
Until quite recently cities were organized such that the things people need are close by. Then the car was invented and someone had the idea that we should separate living, recreation, and working spatially and connect those locations with highways. In hindsight it turns out that this idea wasn't very good. Replacing highways with subways improves the situation a bit because subways are more efficient than highways, but real solution is to re-mix cities so that you don't have to travel 10km in five different directions each to get through your day.
Correct - there is no standard for AC bidirectional charging. But someone could write one, and lots of existing cars could support it with a firmware update. Cars onboard chargers tend to use synchronous rectification[1], which means the power can flow the other way if software wants it to.

Most DC rapid chargers could likewise support it, although again it would require new firmware to be written for the car (to not abort when it sees current flowing outwards), and new firmware for the charger.

If you disassemble a car or charger, the thickest traces are the power path. If there are no diodes in the power path, then its likely the charger uses synchronous rectification and could support vehicle to grid with just firmware changes.

[1]: https://en.wikipedia.org/wiki/Active_rectification
I hate everything about this article. From the video thumbnail to the misleading claims.
> Workers are 3.8 times more likely to leave Tesla than Ford

I wonder how much of this is culture and how much is that Tesla employees are more likely to have gotten rich off their stock compensation in the past 2 years.
Never. In 2008 I switched to Mac (OS X Leopard on Core2Duo iMac) and I have done in-place upgrades and when buying new hardware migrated that install to new machines. Currently running Monterey on an M1 MacBook Air.
This is not at all a risky play, because GP was willing to walk.

It’s a true negotiation only if you’re willing to walk out. So to negotiate, realistically assess the availability of other options, and whether you’d accept them.

If you’re not willing to walk, it’s just a game of chicken. That can indeed be risky, as then you might lose what you have with no fallback and no alternative.
Whatever I would have written, people would always nitpick one way or the other, so I simplified it anyway.
> hard to describe succinctly.

Maybe "Institutional Complexity"?

Some degree of complexity is intrinsic to the problem domain, but it's the incidental complexity that emerges as a thoughtless side-effects of other efforts that is the most annoying, especially when it compounds.

To flip your comment on it's head... Some of my most satisfying projects have been the ones that eliminated this type of complexity where I work, because they improved the quality of life of everyone I work with and gradually remove all but the necessary work. However because these things are usually difficult to isolate and deeply engrained, this is only usually possible once you've gained enough trust and autonomy, which I suppose makes it a hard sell for a new job.
Uh, yeah. Especially in large companies, this is common practice, even without that transition you describe.

It is often much easier to hire internally than externally. And that's good. It keeps people happy within the company vs forcing folks to move on. Onboarding new employees is expensive. If you can shift 1 and keep them happy vs having them leave and having to externally hire 2 it's a win.

For my team (I have no hiring decision, just input), I frequently look for smart people dissatisfied with their work somewhere else. Things I look for: people wanting to work on something more interesting, work with a higher performing team, having greater "impact" with their work, wanting a new skillset, stuck without upward mobility, wanting opportunities for more visibility, etc.

It also avoids the gamble of a resume and behavioral interview. You know the person and can take a reasonable guess on their "fit" with the team. You know their actual skillset ("hard" and "soft" skills) vs claimed.

We've lost a few to job hopping, but for the most part, it's a much better predictor of someone who will stick around, be happy, and be a valuable contributor.

You do have to followup with being an advocate for those high performing people. That can just be recognizing their work publicly or pay/promotion opportunities.

Also, if someone is frustrated with the job on my team, I try to use my internal connections to find a place that they will be happy. I really do care about them as humans and see happiness and job satisfaction as more important than hoarding them.

From the other side, every job I've taken (internally or externally) based on people I know has worked out great. Every one I took by just applying to a posting, notsomuch. No it doesn't sound fair or like a meritocracy, but it's human. Walking in with trust and understanding is a real advantage.
Ages ago, probably the first time Mozilla added telemetry to the browser.

Go interview people Mozilla. Less analytical data but you'll end up knowing your users.
Audible and Netflix have exceptions given they are “reader” apps. For something like Roblox, they must have in app payments if they accept payment via the web, so the publisher would have to opt out of the platform completely to avoid the 30% surcharge for one of these types of apps.
In other news, king orders tide out.
Ossification doesn't have to happen though. Continuing education and some time to "practice" and try new things on a smaller scale can do wonders.
With ue4 that's not really the problem, it mostly falls under category b). The problem is that a bunch of stuff has unneeded module dependencies that hide the real dependency tree. Say a.h includes b.h but doesn't use anything from module B, but b.h includes SomeFundamentalHeader.h which a does need. The choice here is leave it alone or fix the dependency but break any user code that relies on the same behaviour. I did just that in a few modules that were new and off by default but good luck making a change like that in any commonly used modules.
> its a weird fact to leave out of public discourse

It surely is. Thanks for getting back to me, appreciate it.
I thought it was more because of green screen or blue screen dominating production now a days. They had to turn one color off. The side effect.

I was wondering why no one was noticing the lack of color and details in post 2010 films. Watch any 80 or 90s film and see how sharp and details those looked.
Perhaps you should go with an HTTPS one instead then.
Lithuania’s foreign minister calls on EU to stand up to China
Meh, not convinced. Sure you can craft a shitty built bike with cheap parts so to learn more quickly about how the bike fails, and sure you can probably make some money selling these shitty bikes.

But I’m in it for the craft. I want to build and sell super high quality bicycles that ride and look beautiful and will ride for a lifetime.

And for that, every little detail of the bike has to be crafted in a high quality manner.
Thanks for the app, i wanted to start learning web development this week so the timing is ideal :)

Only took a quick look at it, but I like the format with short snippets per page
No worries. I have solved the problem:

https://github.com/timonoko/Context-Aware-Auto-Brightness
But then he’d have to spend the time creating and maintaining an iPhone and Android app. That takes time. As it is now the game is done. It’s an HTML page accessible by anyone with a browser. It requires nothing of him.
it's impossible (i.e. illegal) in Germany to be uninsured. you may have to pay yourself depending on the situation (I had to do it once between jobs), but the amount you have to pay is not crazy, and there are no people who have no health insurance because they can't afford it. For example, if you are eligible for ALG II (aka Hartz IV, i.e. long-term unemployment benefits), your health insurance is automatically paid for.
I find it interesting that many companies focus on hireing experienced developers and the problems surrounding that. I think the smarter and more long term play is to massively improve the experience of university graduates (or anyone really) starting at a company. Have a very clear track and get them to be useful ASAP and make it enjoyable for them and possibly have them stay forever. Developing your own developers seems like a better strategy than trying to hire for fit (in a vacuum).
If you dont want privacy, you are 100% free to make that choice. However, the default should be that things are private unless that privilege is waived.
America is an individualist country and individualism is rewarded. We don’t care about average people. We care about our own ethnicity, our own identity, our own family, our own self. We are just playing the game here. Don’t blame the player. Blame the game.
As my grandfather used to tell me when I was a child, "An idle mind is the Devil's workshop."
What company would associate itself with blocking advertising? Worse it could end up like AdBlock plus.
> I guess my point was more about the reasons behind these weird rules. AFAIK interop with existing JavaScript was not the primary reason for doing them this way, if that's any consolation.

Are you sure? Because there was an essay written by the TypeScript devs when they released whatever version that introduced the strict-function-variance flag explaining why they "couldn't" make it also apply to class methods, and it boiled down to breaking too much existing JavaScript code.

That's not proof that the original variance choice was also due to JavaScript compatibility, but I feel like it's a very strong suggestion that it was probably a big motivator.

I'm glad that it wouldn't work in Flow. I'm sure it wouldn't work in most/all of the other statically typed compile-to-JavaScript languages. I just hate that none of them won out over TypeScript, so they're basically all irrelevant- Flow included.
This is what Amazon does with Kindle sales already.
Tbh, only stripe is surprising. The rest (Ga, FB, twtr) you can easily not include and be safe from the US transfers. They make money from the visitors data, of course they'll be problematic.

The stripe part is the one that will be interesting to watch, because "The EDPS confirmed that the website actually transferred data to the US without ensuring an adequate level of protection for the data". Anyone can easily point out that Stripe claims compliance: https://stripe.com/en-au/guides/general-data-protection-regu... So I hope that that part will die soon.

You can however implement stripe server-side where they can't see more than explicitly provided by the user for the purpose of the checkout. I believe that would have a different result in court. (We'd need to see that tested though)

But! If you're actually worked even able the stripe part, there are EU-based payment processors. More expensive, but they exist.
The Case Against Token-Based Authorization
The GDPR's objective is exactly to give you that choice.
This is exactly why I say that NAT gives a false sense of security.

The point is that even without manual port forwarding your Switch is _already_ exposed to the public internet. You can't assume that NAT is going to forever hide your device from the public internet because the role of NAT is to pass traffic, not prevent it. The example I mentioned is to show that NAT's heuristics may end up exposing your device anyway, manual port forwarding or not. So if you really run a device with vulnerable services, you either add a real firewall or disable NAT.

If the Switch had any vulnerable ports, they were exposed already long ago. Not to mention: IPv6 networks, public Wi-Fi hotspots, etc.
The problem is that you cannot evolve that part of the code.

All is fine as long as you don't need to.

When somebody change that library without approval, it will be a pandora box.

So it's a ticking time bomb.
In Toronto, Canada, freelancing or contracting is a way to pay senior engineers more than the company's standard fixed pay bands. The FTE pay brackets aren't great and we have a great public health care system so there's not much advantage to benefits packages.

Contractors are paid from the project budget (capex) and often don't have to go through the central HR department which allows projects to pay what they need to in order to attract the right people. We typically work alongside FTEs but we get "rolled off" projects as they ramp down at the end whereas the FTEs either stay on or get reassigned within the company.

For me, contracts typically last 1-3 years.

- I find my clients through my network of people I've worked with in the past

- My clients are usually based in Toronto like me

- I've been 100% remote since March 2020.

With respect to remote, my current client is trying to get people back to the office in a hybrid model. If they force it then I'll probably look elsewhere.
Out of curiosity, how do you suggest that be done? Should I live in a mud hut and eat bugs? Forego interaction with society in a cave somewhere?

If you think I should protest, I do. And, I've pointed out exactly how protestors are dealt with: minimized, attacked, infiltrated, smeared, ignored, and so on.

Every year, hundreds of environmental protectors are murdered. So what exactly is your suggested course of action here?
Is this why Mafia 3 is so dark? I mean game is unplayable on Stadia because you can’t see anything.

/endrant
FAANG employees, particularly on the West Coast, are an anomaly, even within the US. People also often include stock grants in listed comp, so be sure your comparing apples to apples.

DC/Mid-Atlantic salaries at an established (non-FAANG) company are more like $85-$100k for a recent grad, $130-$170 for senior developer positions. Most of those jobs are in the suburbs, where a nice house is in the $500-$1million range.
That's at least 3x - 5x my experience, and I'm typically running 3-4 environments (dev, qat, prd) at full utilization (24 x 7); stg enviro as needed. Normally I host using a mix of AWS and CloudFlare; costs with Google Cloud are similar. Your db expenses seem high for so few users, I've seen (and rewritten) those kinds of rates when apps were built using mlab DBaaS / mongo on K8s a few times. If your app is very write heavy using a RDBMS those kinds of fees aren't too unusual. For HIPAA/SOX/isolated apps I normally estimate around 10x a non-isolated environment.
Well, that's humblebragging for ya^^ - your code isn't shitty, au contraire mon ami, if it ain't broke don't fix it.
At a certain size, though, workplaces become unavoidably bad places to work.

Imagine you have ambition and you work in a team of 100 people. How do you get promotion if you don't want to leave? Headline-grabbing stuff, not good, solid, written down, maintainable stuff. It is said many times but it is true.

The only other way you might choose the good over the noticeable (assuming you want promotion) is when you get genuine recognition from someone you look up to. Imagine getting called out at a department meeting for sorting out the documentation or automating a load of rubbish stuff.

I guess either way you want to be noticed/make a difference right? This is easy in small companies because everyone makes it better or worse. Once you reach 50+, I think it all starts going downhill. Maybe some of these companies just need to organise as microbusinesses - something that microservices promised, so that everyone can make a difference.
The component heirarchy tool in React Devtools (https://chrome.google.com/webstore/detail/react-developer-to...) lets you select something in the page and then click a button to go to it's component definition in the code (if your sourcemaps are working properly). It's the angled brackets in the right hand side panel - https://imgur.com/a/ufCPsMo It's very useful.
Oh whoops, my previous response was about which collation I (want to) use. Were you asking which DB I use?

The answer is Postgres. I have some previous experience with MySQL and there are advantages and disadvantages. The biggest advantage so far is partial indexes.

But since I don't have as much experience with Postgres, there's still the occasional surprise, e.g. index names not being scoped to the table, this collation thing. And from what I've read online, I should probably set up some monitoring for vacuuming issues.

The article about Postgres operational footguns recommends outsourcing those issues by using a managed Postgres service (e.g. AWS RDS or Google Cloud SQL), and that's what I do.
Let's build a building over them and put the solar panels on the building's roof.
I am currently using Adsense settings that allow Google to choose the placements. It seems it makes the sites too crowded with ads - I agree.
We are planning on a new design and when that is done we will have specific spots for ads and not allow Google to choose how many or where to place them.
I have a small business that operates a website. To be absolutely clear, we don't rent or sell personal data in any form and our business model has nothing to do with tracking or profiling anyone.

We retain certain access records that can potentially be used to identify individuals indefinitely. These records have demonstrably helped us to defend against attacks on our infrastructure and to prevent attempted fraud on multiple occasions, sometimes years after the records used were first collected. We include these general purposes for processing but do not disclose exactly how we use these records for these purposes in our privacy policy.

So, are we compliant because there is a demonstrable legitimate interest in keeping these records? Is holding that personal data indefinitely, knowing that it mostly won't be needed, disproportionate and a GDPR violation? I'd love the people who think the GDPR is simple to show me verifiable, authoritative answers to these types of questions, because so far we haven't found any lawyer who can, nor found any information from any relevant regulator that we could point to as a clear indication either way.
It’s a firewall thing not a batting thing. You need a stateful firewall to do that kind of smart port forwarding. Which, to be fair, all consumer routers should have.

Stateless firewalls, however, need to have explicit rules for UDP traffic. So that’s what Nintendo are addressing here.