skysight-inc/HackerNews huggingface dataset:
Non-Swiss students have known to stay away from this university for awhile now. See: https://gmatclub.com/forum/university-of-st-gallen-hsg-mbf-2...

This is a really good overview of one of the Financial Times' top rated business school programs in the world, where this PhD student was expelled from, in Switzerland, with an extremely damning report of the program and how they cook the books to make it look like you would have a chance of making it in a place like Switzerland post-graduation.

What is really damning about it: You have zero chance of integrating unless you have an EU passport from about 8 or so countries, unless you are Swiss. It is very insightful, actually.
Definitely worked at similar places in the UK straight after graduating. Thankfully not for long and thankfully nowhere near as bad as this.

Same sort of vibe though, same sort of deal though where the founder had some successful company in something else then we were the smaller side business doing web design and 3D animation at the time but clearly knew nothing about how to make that work and same sort of deal as this where the other businesses subject would start to leak in presumably because that's what the founder understands.
Many open roles at ConsenSys [Remote | Hybrid]:

ConsenSys is a blockchain software technology company focused on building infrastructure, tools, and products for Institutions, Enterprises, developers, crypto and DeFi investors and users. If you are someone that thrives in a fast-paced environment where being self-directed, determined, and resilient are a requirement, we would love for you to join us.

All job postings: https://grnh.se/27ba08321us

- Security Auditor / White Hat Hacker - Account Executive (Diligence)

Analysts (Business, Data, Senior Business, Security)

Engineers (Fullstack, DevOps, QA Automation, Site Reliability, Technical Support, Backend (Golang, Node.js), Test, JavaScript, Senior Mobile Software, React Native, Web3, Blockchain, Cloud DevOps, Java Software, Rust)

- Technical Lead - Internal Tools and Automation - Senior Systems Administrator

Research: - Applied Researcher - UX Researcher - Distributed Systems Applied Researcher (Protocols R&D)

And Many other roles (Solution Architect, Marketing, Economists, Scrum, etc). https://grnh.se/27ba08321us
Do you have evidence for this from a reputable source?
>However, you seem to have missed the point. My problem is not AppleID, my problem is that Apple forced it on my app and threatened to shut me down if I didn't include it

My understanding is that Apple only force you to include this if you provide other third-party login options.

This is a consumer-friendly feature that Apple is forcing you to implement so that your users on Apple platforms can choose to use your app's one-click third party login functionality whist still retaining control about what personal data they share with you.

Apple's platforms require a variety of consumer- and privacy-friendly features from developers who choose to release apps on them, and you could make your same argument against any of them (e.g. not tracking the user without their permission)

That Apple does this and holds third-party developers to standards for privacy and consumer-friendliness is why I (and many others) use their platforms.
+1 The Brother printers are awesome and just work as printers should do.
Anyone taking part in the design of one of these machines should be required to stop, prior to starting design, and build a wall of bricks by hand. In a grassy field. From scratch.

The problem with all of those (less the exoskeleton) seem to be a poor grasp of the challenges involved in doing the job. They all seem to assume a perfect environment; something rare (impossible?) for most on-site work.
That's a really fair point, sorry for misunderstanding you. I agree: government incompetence can enable people with strange ideas.
You might want to ask yourself, or your readers, what it is people are trying to access on your site that they cannot by other means.

The interfaces for many sites actively and with brutal effectiveness deny ready access to any content not currently featured on the homepage or stream feed. Search features are frequently nonexistent, crippled, or dysfunctional.

Last week I found myself stumbling across a now-archived radio programme on a website which afforded exceedingly poor access to the content. The show ran weekly for over a decade, with 531 episodes. Those are visible ... ten at a time ... through either the Archive or Search features.

Scraping the site gives me the full archive listing, all 11 years, in a single webpage, that loads in under a second. I can search that by date, title, or guest to find episodes of interest.

The utility of this (a few hours work on my part) is much higher than that of the site itself.

Often current web sites / apps are little more than wrappers around a JSON delivery-and-parsing engine. Dumping the raw JSON can be much more useful for a technical user. (Reddit, Diaspora, Mastodon, and Ello are several sites in which this is at least somewhat possible.)

Much of the suck is imposed by monetisation schemes. One project of mine, decrufting the Washington Post's website, resulted in article pages with two percent the weight of the originally-delivered payload. The de-cruftified version strips not only extraneous JS and CSS, but nags and teasers which are really nothing but distraction to me. Again, that's typical.

I'm aware that many scrapers are not benign. More than you might think are, and the fact that casual scraping is a problem for your delivery system reflects more poorly on it than them.
There's always room for improvement on all of this stuff, but I'm generally in agreement, I thought the SameSite=Lax rollout went a lot more smoothly, and I saw people outside of Chrome mailing lists talking about it and sounding alarms that sites might break.

I try to pay attention to upcoming potentially breaking changes, but I didn't know about the iframe changes (luckily they didn't affect any of my projects). I did hear about the SameSite changes from multiple sources, it felt like there was a real effort there to try and break the news into the mainstream.

I also think a big part of what made SameSite=Lax better was that it wasn't just Chrome notifying people about the changes, it was other developers in the community helping to spread the word. I saw multiple blog posts and Twitter threads warning about it.

I don't think the model of "Chrome announces something then wipes its hands and steps away" works in the real world. Developers need to be included in efforts to spread awareness, because there are communities that the Chrome team doesn't have access to, and not everyone pays attention to what the Chrome team posts. It's better if multiple stakeholders both inside and outside of Chrome are invested in getting the word out.

It sounds to me like a big part of the complaint about the removal is that there isn't currently a good replacement for `alert` in intro tutorials, or a clear process for sites that depend on `alert` to quickly move to something else. I don't expect the Chrome team to understand that in advance, the web is enormous and they are going to miss use-cases, no single team can predict the full impact of every browser change. But early awareness of changes and early interaction with communities outside of the main mailing lists will make it more likely that developers and communities raise these issues so they can be addressed before there's a PR fallout.
It taught me a whole lot of other things, but definitely not what you propose.
> If I had a euro any time I heard a sysadmin tell me 'they can't code', only for me to see them write perfectly good Python... A euro for every time a sysadmin tell me they really want to program more, but they think they're underqualified to even start learning, even though they write higher quality, more maintainable and better designed code than most fresh CS grads I've met

And if i had an euro for every sysadmin who told me "i'm not a developer, you do it", i'd be rich. "Sysadmin" includes Windows-only, GUI-only, ClickOps style admins, which still exist. Do you think they can or want to code? Heck, there are even networking admins that prefer to use GUIs over CLIs!

Not everyone can or wants to write code, even if some people underestimate their skills, some people are afraid.
> Bigger question is how they found the accounts to ban - did they just get the social graph of this outspoken researcher or is the extension itself distinguishable based on its activity?

It sounds like they may have just banned the researchers associated with the, but not the app itself. She's still asking people to install it: https://twitter.com/LauraEdelson2/status/1422742671957843971.
I was looking for a nice coffee table recently. I decided to try the unfinished wood furniture store, most of it made by the Amish or Menonites. I'm handy enough to stain but not equiped to build a table myself so I figured I'd save a few bucks doing the finish. Most the tables weren't our style but finally found one that looked great and was some real quality oak. Asked for the price and just about crapped my pants. We stopped by Ikea on the way home and bought probably the nicest table they had for a quarter of the price. The nicer Ikea table will be able to make it through any moving we do in the future but it most certainly won't be an heirloom like my parent's old oak stuff.

I want try my hand at some furniture building in the future but just don't have the space or some of the standard tools for it now.
O.C. Tanner | Senior Cloud Engineer | Full-Time | REMOTE (~36 States) US | VISA

Hello. We’re O.C. Tanner, a technology and services company focused on employee recognition and workplace culture. We've been named one of the 2021 Fortune 100 Best Companies to Work For:
https://fortune.com/best-companies/2021/

We run a modern platform stack including Docker, Kubernetes, Grafana, NodeJS, & Go. I'm looking for a Senior Cloud Engineer that has DevOps experience. You'd also get to work on our Open source PaaS called Akkeris (running k8s under the hood): https://beta.akkeris.io/ and https://github.com/akkeris

Senior Cloud Engineer: https://recruiting.adp.com/srccar/public/nghome.guid?c=11161...

Other teams are also hiring for multiple engineering positions, see a full list here:
https://www.octanner.com/company/careers.html
Android (from v10 I think?) does that - deferring the request for permission X until it's actually used.

No more giving Camera permission to an app just because it supports sharing photos, which you know you never want to do, or whatever.

(Yes, this was possible beforehand by manually refusing specific permissions after granting all, or vice versa. But it could be unpredictable and cause app crashes etc.)
https://gez.la - Open Source Virtual Tour Database

https://github.com/stfurkan/gez
These are well written. Looking forward to parts three and four
Yeah, that seems like the best plan. It might not improve the speed of bricklaying, but it would certainly be an improvement on the bricklayers' quality of life.
Don Syme teaches Guido van Rossum F#
https://archive.is/u4D8H
This is the pettiness I'd feel embarrassed about if I'd ever let it come to fruition.

Restricting Apple ID to the mobile app seems more than enough, the snarky popup goes too far. As a user, I don't care about your personal beef with Apple. Simply explaining that the button was added because of Apple's restrictions in the first place and that you never wished to support it in the first place should suffice.

I appreciate your willingness to lose customers to make a point against Apple. A little more... nuance would probably make it a lot easier to gather support from others.
Honestly the whole app could probably use a UI overhaul. The button looking different than other social logins isn’t the problem; the app looking completely alien to any version of iOS released in the last 10 years is the problem.
I haven't been at Latacora for a while now.
> The privacy leak that Facebook is so concerned about is actually the identity of advertisers on their platform.

Yeah? That also seems like a completely legitimate concern.
I have learned a lot as a self-taught developer. At first, the experience is quite something new. I am always looking forward to contributing changes to the projects assigned to me.
For websites without an RSS feed, you can try to generate one using self-hosting RSS Bridge[1]. There are some instances with open access, though supposedly some may work more reliably than others.

[1]: https://github.com/RSS-Bridge/rss-bridge
Bloomberg LP NY Is Hiring Sr Engrs for FI Real Time Pricing Platform Team
In Sweden, Norway, Finland, the government leaks this info for like 30 Euro. You can know anyone's taxable income.
The very presence of their agency implies that we're not exactly in new territory here.
I hate to be the one to say it - but if it was first tested on IE5, that's over two decades old. I really wish it were just the one!
The peer review process is a joke. I trust preprints just as much as peer-reviewed studies.

Which is to say:

1) I read carefully, evaluate the methodology, assume authors are spinning for "high-impact" research, and believe results only once they've been replicated a few times by independent researchers using different methodologies.

2) I use results I haven't vetted like this in a probabilistic way -- they're often good for best practices, or identifying risks, but not as sources of ground truth.
Obama _far_ preferred focusing on domestic, societal issues over foreign policy and long-term strategy.
Bloomberg LP NY Is Hiring Sr Engrs for ESG Team (Environmental Social&Governance
Yeah when I see anything .NET related, it's always backend or fullstack oriented positions.
German ruling party CDU reports security researcher to the police then rows back
There are several localized Swiss dialects and there are some Swiss German formal written publications in these local Swiss dialects that other Alemannic German readers have trouble understanding.
> You've got very low expectations if you count those as "good" services

A fair point. "Workable" is probably better.

> trying to travel with one small child would be challenging, two is likely to be stressful

Sure but I know a lot of people who manage that regularly on similar routes without having to resort to cars.

> Maybe not ideal, but in the real-world, that's sometimes the way it is.

Sure but if you're a top-level government climate spokesperson, using an old diesel car because "you don't want to stop to charge" in an EV and you seemingly haven't even considered trains is a very bad look.
> There's a bit of a difference between getting data for public interest purposes and getting it for making profits.

I'd say what Cambridge Analytica did was worse than that: they weren't transparent about their purposes, which was to manipulate people. AdObserver seems like they're being transparent, not trying to manipulate anyone, and working for the public interest.
>For someone like me, who doesn't just want to help the rich get richer

When it comes down to it, doesn't that describe the majority of well paying jobs?
(I say that as someone who bailed on my well paying tech career to work in the non-profit space for that very reason)
I work on a lot of web scraping and we have business agreements with every site that we scrape explicitly allowing us to do so and with pre-approval for the scraping rate (which we carefully control).

None of this gets around over-eager Cloudflare or Akamai rules set up years ago by some contractor that the businesses have no real ability to change.
> With the vast number of laws and opinions, it seems it's just as much about making the judge like you because they can pick and choose what laws apply (just look at stuff like split opinions).

I tend to view this as analyzing the same problem under different rule sets. Like, making an argument to a “living constitution” judge can be different than making none to an origins list judge, but there’s an internal logic to each argument. It’s just different axioms and rules.
Mostly anecdotal, since there's no real definitive way to tell.

There's two spaces I see.

- Caching within the webserver, as the caching there has improved over time. The caches in Nginx, Apache, LiteSpeed, etc, perform much better than they did in the past.

- Caching at a load balancer tier. Nginx again (though in a LB context), Haproxy, etc.

Both spaces seem to have less talk about Varnish than they used to, and more about other platforms.

You can see a plateau, then decline (though slight) that starts for Varnish around mid-2018, here:

https://trends.builtwith.com/Web-Server/Varnish

Compare to:

LiteSpeed: https://trends.builtwith.com/Web-Server/LiteSpeed

Nginx: https://trends.builtwith.com/Web-Server/nginx

(Though these kinds of surveys are tricky, as they depend on outward facing headers that don't always exist, or don't always tell you enough...like Nginx doesn't always imply the cache is in use)

I also wonder what percentage hit Varnish might take if Fastly moves away. I'm sure they regret not varnish specifically, but exposing the varnish vcl directly to end users.

Edit: Yes, I agree that sites like "builtwith" are flawed, and mentioned some of the reasons above. And, I didn't mean for this comment to sound like a criticism...just an observation. I noticed builtwith's chart has a similar plateau + slight decline for Apache, starting also near mid-2018.
Database Connection Deserves a Name
No need for `* *`; just `*` would do fine.
Someone who needed a job?
There is the generic and the specific.

Generically an e2e test requires you replicate all aspects of the system. Even if everything goes right that is a lot of work to set up and a lot of time to wait. Many parts means many opportunities for something to break, and you'll be really resentful of how long the happy path takes when you have to redo it because of the one part that isn't happy.

Also specifying a good outcome in a robust way is hard. You might build into your specification a certain kind of UI element is blue and then you decide to make it red. On one level the corporate people think the branding is important and might take forever to decide on the right color, on an another level it is superficial to what the application does. Robust tests capture what is generic/important and aren't bothered by what is specific/unimportant.

Contrast that to unit tests where you can be sketchy.

I was writing a unit test the other day that involved an object had 20 fields. Only 2 of those fields were used by the system under test so I left the other 18 null. If one of those fields being null is a problem later I can give it a value. If I had to make up values for the other 18 fields it is a lot of effort and probably one of those values will be problematic in the future and have to be changed. An E2E test though would require that all the fields are specified because that object could exercise the whole system.

Specifically E2E testing of some systems is less fragile than other systems.

Unit tests are that way too. In some cases writing unit tests can be a joy, in other cases it is a constant fight and you end up with "test induced design dysfunction".

If you make peace with the process and address all the sorts of fragility you might think your automated E2E tests are less bad than what they cure; if you don't find peace you went from the frying pan to the fire.
Yup. I think the problem in the current truthiness and messaging is that the CDC -- and more broadly the scientific establishment -- have undermined their own credibility. It's really hard to roll that back.
Asking an honest question: if Apple didn’t force this, would you really add this voluntarily?

Because this response tells me you’re willing to compromise your user’s experience because of your personal issues with Apple.

As a user, this does not give me confidence in your decision making.

It’s somewhat understandable to be annoyed, even angry at Apple. But the moment you decide to pass that on to your users is the moment you’ve forgotten the most important humans in this story.

Of course, it’s your right to do what you want, and if that means taking a stance against Apple ranks higher than your user base, I suppose that’s your prerogative.

But that definitely would make me hesitate to use the app.
And in most cases are in fact legally immune from any personal liability.
Right. The other thing is that in the parent, "static type checking" got shortened to "types", which in turn got confused with "modelling".

The problem with stringly-typing is the model, which is SQL as strings. Statically type-checking that all your strings are, in fact, strings does not buy you anything whatsoever in this scenario.

On the other hand, if you have an actual model of the SQL, then it also doesn't matter whether that model is checked at runtime (dynamic typing) or at compile-time (static typing). In either case it will not allow injection attacks, if implemented correctly.

And of course the actual place where nastiness happens is the user input, and I haven't yet seen a place that can statically typecheck users. ;-). So, as you point out, you will need to do dynamic checking and sanitising of input.
https://en.wikipedia.org/wiki/Profession

Law, medicine, etc.

There's no professional body for corporate design is there?