skysight-inc/HackerNews huggingface dataset:
We operate 300ish IT systems of various size, from handling vacation time between leaders/employees to full fledged SAP solutions. We have 10,000 employees but only 5 developers of which 2 are also operations engineers developers. If an employee needs a little bit to automate some small workflow, to save them a few hours a week, that’s way below the scope of where we would get involved to do an RPA process. But that doesn’t mean we don’t want people to automate those tasks. In the ideal world we wouldn’t need RPA, because much of what it does is things that should work smarter in our current systems. But the enterprise world is far from ideal.

We didn’t use one of the big consultant houses like EY. We didn’t because we have plenty of business process people, project managers and so on ourselves. And that’s typically what the big consultants mainly offer, they offer it along with tech consultants that are often from some partner. We started by gathering info on what was available, as well as what we thought we needed and we drew on experiences from other cities. Many places had gone with the big consultant agencies and gotten this big package on the business end, and one or two processes build with the tech consultant, and then their project stranded because the business part doesn’t actually build RPA processes.

We decided to go with a small local startup, where we bought hours and “open” consulting. We did brainstorms with them, but then we build things ourselves and had them review it, and we put a much larger focus on learning the technical parts - and well - we are now the leading city on this area if you compare the 96 cities that aren’t our two largest cities. So from my anecdotal view, that is far better than using the big consultant agencies.

I named EY, and that may give them bad publicity here, but EY was actually the best of the big package offers that we didn’t decide to go with. Which is why their name stuck with me, so it’s a little unfair if this makes them look bad.
Live orbit visualisation of Starlink constellation
Can I go from my house to my friends house using only rails? My house to the supermarket?

Not all pairwise points are connected by rails, while they generally are by roads.
Maybe this will motivate product owners, developers, marketers, to start thinking before implementing a dozen of SDKs in a mobile app (or website). It's understandable when you need some analytics/crash reporting, but it becomes a privacy and ethics question when a lot of data is wandering around, and even better, crashes your app. And the users will blame you, they don't even know how many SDKs are there and what they are doing.
Applies even more so to CSS and JS.

All the above are quick hacks that never really did the job properly in the first place. So they're propped up by a creaking pile of frameworks and other support systems that try to mitigate their awfulness, but mostly just add extra awfulness of their own.

Meanwhile backend systems - core server and db infrastructure, user authentication, computing resource allocation, payments, media and content management, privacy, and project build systems - are even more byzantine and non-standardised and more or less have to be retooled from scratch for every project - a huge job which duplicates an incredible amount of work across the entire industry.
Never said they wouldn't, just you can fork/clone/mirror without auto-cascading delete.
Missing Sony and Nintendo (Switch main API is NVN) there.
Thanks for this! I was just gonna say "wait, this looks exactly like Visual Studio Online".
If you only need login, then you can have the same functionality without the Facebook SDK or Google SDK by using OAuth.
As an example, 9 million people die each year due to hunger or hunger-related issues, many of them children. 135 million face food insecurity. Due to lockdowns and recession, the World Food Program estimates the toll will double this year. And hunger is just one cause of death that a recession can lead to (suicides, substance abuse, etc).

Lockdowns might save lives, and I can't blame public health officials for protecting their community, but I personally fear more lives will be lost due to economic costs. They just might be poorer, quieter lives. And while death is, of course, final, suffering in life should count for something too.

https://www.wfp.org/news/covid-19-will-double-number-people-...
You just need the right motherboard. ASRock Rack X470D4U
His wife worked together with people from China.
My original comment misses some nuance.

Django's documentation is great for developers who know their way around documentation like that as it is very comprehensive. It drills down nicely and is quick and easy to understand if you otherwise know what else is going on.

What it misses is mapping that documentation to the specific problem a person wants to solve or the feature they want to build. When I was learning Django a couple years ago I found the examples and best practices sparse.
So because the webapp is exposed to the public over the internet and there's a risk of hacking the the developer story can be poor? That doesn't sound right. The developer story is just poor because the frameworks and developer Tools are poor, badly documented and don't work well together holistically. Part of this is just due to the continuous churn in web development that creates insane amount of busywork and makes sure that almost all of your available documentaton is always put of date. i find that most of this "complexity" that the author mentions is just man made.
I had a similar idea, probably less user friendly than yours.

The secret is a user defined function. When the user attempt to login. Some random inputs will be given, the user can use a calculator to produce and type in the output.

Since the calculator can be a physical one or just by brain, key logger and screen logger will not be able to steal the secret.
The article is partisan, and yet it DOES make some valid points.
React - as a library, but especially as a UI paradigm - has clearly won the frontend war for now, taking the mantle from JQuery. I don't even use React directly, just its DOM renderer through a ClojureScript wrapper (reagent) and the high-level concepts are still basically the same.

Still, when I glance at the JS frontend world people are still looking for the next hot frontend framework all the time, even if many are doing something similar to React. Going by github stars, Vue is the biggest one now. There's also Angular, Svelte, Ember, and Aurelia.
I'm European and was surprised to hear that legal issues are indeed a part of the decision, not just technical details.

AFAIK data that passes through the US may be legally intercepted by the US authorities.
That is a common Khronos approach to learning, one should learn everything from ground up, including hunting for libraries that handle math, images, fonts, shader loading,...

I agree with you, this is not the way to bring people up to speed with graphics programming.
[Looks like you've read 0.1% of this page! Enter your email into this popup to receive emails you don't want about things you're not interested in. Also turn off your ad blocker, because we're not a charity, you freeloader.]
Years ago I discovered that there are many poems you don't have to wilfully memorize, but which you "learn" like you learn melodies, very quickly and totally unconscious. For me, this includes for example Poe's "Raven" [0]. I once had a teacher who had memorized large parts of Goethe's "Faust" by accident, just by reading it every year she taught it in class.

[0] https://www.poetryfoundation.org/poems/48860/the-raven
My understanding is some COVID-19 patients (as in, the fraction of people who experience symptoms much more severe than a regular flu but do not die as a result) suffer severe permanent reduction to their aerobic capability (lung damage caused by pulmonary edema).

I am certainly not suggesting that ALL servicefolk who contract COVID-19 should be medically discharged, but statistically a portion of them will have severe enough cases that medical discharge is the only sensible option, as they may be endangered if left in place. It is not their fault, but if an existing servicemember is no longer physically fit to serve then it seems fair to medically discharge them. And similarly to reject an applicant on medical grounds.

I do not think it is fair to blanket reject all COVID-19 patients, as most will make a full recovery and would be perfectly able to serve, but if you had sufficient applicants that you could be choosy about it you would understandbly want to choose the ones with less doubts about their medical history. I am not from the USA so I do not know how picky they are with recruiting at the moment, but if it is a trough in the cycle then I would expect to see recovered coronavirus patients turned away.
Wow, as a fan of your web persona, I find your stance on this intriguingly Stallman-ish. All the more because you omit making the utilitarian fungibility-talent margin argument, which I'd expect you to be aware of.

I find refusing to "build the tools of oppression" more defensible on utilitarian grounds than denying to even use such tools (apart from practical considerations, that is e.g. vendor lockdown, privacy issues etc).

And yet you already claim to be boycotting evil corporations, which in my eyes amounts to pretty much that.

I suppose I can buy the "we shouldn't normalize morally wrong behaviour" as long as it remains defensible on utilitarian grounds i.e. working for megacorps. But I have a hard time seeing my use of e.g. google translate as morally wrong.
> such quality of work would not be accepted in the private sector.

To be fair, if such code would be used for a paper and the flaws came out, I think it would warrant a retraction.

I think I saw not too long ago a story right here where a software error caused completely wrong results.
Resolves issues of low quality image originals in one click by Let's Enhance
This could be rolled out as a service for companies to integrate into their pages to provide support to their users.
lovense (Actually 'lovesense') - It's a vaginal/anal wireless vibrating egg that can be controlled via bluetooth. A lot of Webcam models use them and the viewers can trigger the vibrations via payment tip.
I like that a lot. Thanks.
Because it's artificially made hard by people who enjoy complexity for its own sake. The article is about implementing a shopping cart, as far as I can make out. Well people used to write those kinds of websites, that perfectly well enabled users to browse products, fill a basket, place the order and make a payment using nothing more than notepad.exe.

Some software is legitimately hard to write, even some websites. But this isn't an example of that. The author has been sent on a wild goose chase.
But that has nothing to do with "cookies" at all. You could in principle implement purchasing using client-side javascript without any cookies, as long as you don't care that the customer's shopping cart disappears if they close their tab, and when the customer sends their purchase information you'd still have all their personal info even if you didn't use any cookies.

Meanwhile the actual problem with (third party) cookies is that they're used to correlate users across multiple sites for tracking purposes, which goes away when browsers stop accepting third party cookies by default.

> But consider if you buy some books or sex toys or whatever from an online store. Do you want the store to sell information about your purchases to third parties?

This is really a different problem, because how are you supposed to know if they're doing this anyway? How is the government? Once they have your information there is no real way to tell what they're doing with it if they're willing to lie to you.

So the answer is to make it so they never actually have your personal information. But for this we need some kind of anonymous digital payment system for small transactions, so that the vendor doesn't have to know who you are. If all they have is a transaction ID from a bank that lets them get paid and a virtual one-time-use PO box number you had the item shipped to which forwards to your real address for a week and then is deleted forever, they can do whatever they want with that information and you don't have to worry about it.
You can do all kinds of stupid animations with pure CSS.
+1 that's one of the reason for us too.

GPU machines are clearly too expensive in most cloud providers compared to on-prem.
A company is not just one thing.

https://www.linkedin.com/pulse/response-tim-brays-departure-...
Sony and Nintendo definitely make hardware.

Microsoft not only does not support Vulkan, ICD drivers aren't allowed in Win32 and UWP sandbox models.

NVidia designs their hardware in collaboration with Microsoft, giving first class support to DirectX, and only afterwards they port the features as extensions to Vulkan/OpenGL.

Latest two examples, Ray Tracing and MeshShaders.
> Lockdowns might save lives, and I can't blame public health officials for protecting their community, but I personally fear more lives will be lost due to economic costs. They just might be poorer, quieter lives.

That's a real issue in the developing world; in the developed world the resources exist to buffer the temporary additional low-end economic impact; not doing so effectively is a policy choice (and, in practice, a deliberate active one made when the alternative of providing the aid is presented), not an inherent corollary of lockdowns.
The number could have been factored by hand.
Tackling bioinformatics as a webdev: why is it so hard?

"I am a professional in Field X but I am doing work in Field Y despite having minimal skills or experience and I ran into loads of problems and issues that I don't know how to fix! Field Y is total bullshit and people need to make it easier so people with no skills or experience can do it! Wah wah!"

... or to be less facetious, modern web/frontend development is a genuine skill set that benefits from experience and knowledge.

Should we expect anyone to just jump in cold with minimal experience and not find it difficult? E.g. in the same way would we expect people to start bioinformatics cold and be productive immediately?

I'd doubt it.

On the past web dev has been looked down upon as somehow "lesser" than "real" engineering, with sneering criticism from people more used to traditional development approaches (particularly criticism of JavaScript). It is just some web pages right? HTML and CSS? How hard can it be?

Well guess what: it is a genuine skillset and people should not expect to just be able to jump into something without knowledge training or experience and be proficient at it, just like we'd not for brain surgery, car mechanics, concert piano, structural engineering, or indeed bioinformatics.

</rant>
cached: https://webcache.googleusercontent.com/search?q=cache:Wxi-Iu...
If this were Reddit, I would comment that: IE.. it only took it nearly two months to display that message /s :)
Must have been a blip on my end then.
every user is a bot except you
Subdomain hijacking is only possible if you’ve allowed subdomains to be used for such other things, which I strongly assert is rare.

Older browsers: all browser releases from the last couple of years support it (including IE11); browsers from before then should not be being used on the public internet under any circumstances. It should be a negligible fraction of your user base that uses such browsers, and so long as you’re also happy to break IE11, a safe path (from a security perspective) is to actively break the site for old browsers by blacklisting them or checking for support of a comparatively recent feature. (Just don’t do a whitelist by user agent string, that approach is unmitigatably bad.)

You’re correct about some auth systems not playing nicely with strict same-site cookies, because they’ve been designed with certain assumptions in mind. I’m not particularly conversant with that space, never having had to interact with such a system.
I am currently reading this and I can't help but think every single page is a puff piece on how many stocks he owns and which opportunities he did and didn't see.

It doesn't feel like learning about investing for a beginner but rather an autobiography on his portfolio. What did you like about it?
“Everything in moderation, including moderation.”
-- Oscar Wilde

I've found it to be an excellent philosophy to live by.
> And the users will blame you

Rightfully so. If you add an SDK to you app, it's your fault if the SDK causes your app to crash.
So it's just like trackbacks we used to have in the late 2000s?
Well, it's sad that he could not remember you ; but maybe his mind was already full caring about his current students - whose life he's going to change too - that would be cool, he ?

Great that you could "pinpoint" someone that had a such a profound effect on you. Do you think there's anything in his behavior that can be "stolen", to try and have the same effect on other people down the line ?
There is a nifty Firefox extension (maybe it exists for chrome too, haven’t checked) called “I don’t care about cookies”

It discards most of these popups. Coupled with unlock origin and decentraleyes, I think you’re pretty well covered against tracking without too much hassle.

Of course temporary containers is the cherry on top (although amazon seems to have a way to recognize you anyway because it almost always only asks me for my email before logging me in)
I like seeing all 3 core motivations for taking a11y into account: ethical, legal and business (as recommended by WebAIM[1]).

[1] https://webaim.org/articles/training/motivate#types
> Why’s there so much data in the url? A common refrain I’ll use for the remainder of the post is, “I don’t know”. One of my biggest gripes with web programming is the number of rabbit holes to fall down. There’s just not enough time.

I mean, bioinformatics is _notorious_ for spending just enough time working on software to publish a result and no more. If we want to talk about rabbitholes I nominate BioPerl.

> here are a list of terms that you’d never come across as a bioinformatician: ["X-Forwarded-Proto", "proxying", "requests", "TLS connection", "HTTP", "loopback/localhost", "whitelisted proxy servers", "gunicorn", "nginx", "Apache/httpd", "HAProxy", "Django", "SECURE_SSL_REDIRECT", "SecurityMiddleware", "adapter", "URI"]

This list is more than a little disingenuous:

Django: This is like, the framework OP built their software on top of. I don't know how one gets the point of filing this bug without knowing the term Django

requests: literally, a user's web request.

HTTP/URI: this is the web developer equivalent of a biologist not knowing the term DNA. Or DOI for that matter.

whitelist: the opposite of a blacklist

Much of rest comes down to the simple fact that job of web developers is to build a network service. This is primarily done with layers; each layer only needs to know how to interface with the adjoining layers above and below, like a lego brick. This is actually a _solution_ to the complexity, allowing us to constrain the design of each layer to interact only with those above and below it. This layer abstraction lets us reason about each layer locally, independently of the system as a whole.

nginx, Apache/httpd, HAProxy: in this context, mentioned as possible proxies forming the outermost layer. in this context, accepts HTTP/HTTPS connections and makes HTTP connections to gunicorn

gunicorn: the thing that runs the Django app. Accepts HTTP connections, makes WSGI calls to the Django app

Django: Accepts WSGI function calls, routes them through middleware, then to the app as you define in urlpatterns

SecurityMiddleware: a class that potentially modifies inbound requests and outbound responses

Finally, OP is in the unhappy situation of bridging two network protocols: HTTP and email. The normal trick of using a protocol relative URI will not work here because you've gone outside the browser request-response loop. This puts them in the unhappy state of the lowest layer needing to know the details of the highest layer, hence the discussion of absolute uris. This is a direct violation of the local reasoning constraint, and what makes all of this hard.

X-Forwarded-Proto: An HTTP header, added to incoming HTTP requests designed to indicate to layers below which URI scheme was originally used, HTTP or HTTPS.

SECURE_SSL_REDIRECT: a setting for SecurityMiddleware that will stop processing the request and send a response to the browser telling it to resend the query over https (an HTTP 302 redirect), if the incoming connection is seen as coming over not http.

tl;dr: email is the thing that sucks.
I don't think that this is what makes it hard.

Setting up https, or online payments, etc. is actually quite simple. People with engineering or scientific background have most likely faced much more complex tasks. Security and safety aspects can be more stringent in many other industries, including in software development.

The difficulty of the web, I think, is the proliferation of standards (or not so standards) and technologies: networking, https and friends, APIs (payments, etc), html, css, javascript, php, ruby, java, aws, react, vue, redis, SQL, etc. And they are all evolving independently all the time. This is a right mess and can be overwhelming.
Probably the wrong place for the discussion. Do a search and you'll find all sorts of people with this issue. I had the problem after I first built the computer. Then I was able to boot by lowering the speed of the memory in the BIOS, now I have the problem again after a reboot. I don't know what changed. There's hundreds of threads which cover a lot of ground on this issue. I'm just going to make this a long term project to understand the issue until I finally cave and buy something which has already been built.

Edit: Also 3600 with B450 board. Kingston DDR4-2666 Ram (8x4) which is all the computer store here in smallish city in the Philippines had in stock.
> Blocking cookies should be done by users via software.

That’s what is done.

The government doesn’t block cookies for you, they set the rules with user data, and the actors (service providers and users) act accordingly.

That’s how things should be.

I don’t want the governments to build or design software, I want them to set the rules and let browser developers and other actors react accordingly. If the reaction isn’t judged well intended or good enough, they are sanctioned accordingly.
Execution matters more than an idea.
Maybe browsers should have a mode where they don’t display images that are larger than X bytes if you don’t click on them
If one could come up with an estimate of how many hours per year it would cost to maintain (plus initially setup cost), and multiple that by $75/hr (a reasonable rate for a good engineer), then you could estimate how much it all costs.

I'd wager a guess that a properly-configured server won't actually cost that much to maintain. Unless you're frequently updating the OS and other stuff - but that's a software issue. I don't expect the hardware will fail that frequently at all. If there's a HDD failure, a good RAID system (with tolerance for 3 or 4 disks failing simultaneously) will alert you to it, and you'd grab the spare HDD (you should have a few spares), and pop it in, and the RAID would recover from the failure. What other hardware components frequently fail? RAM? CPU? Not really.

The engineer who sets up the server should be someone who is a generalist, and a full-time employee who when not tending to the server, works on other stuff (like the product). Then you have someone on staff who is familiar with the system, and can fix something that goes wrong, without needing to ramp up on it first. I know a lot of programmers would love to set up a server. Any who enjoys buildings PCs (which many generalist programmers do) would probably love to have a one-month project where they pick parts and set up a powerful server.
I had no idea why my app was suddenly crashing multiple times all of a sudden. God fucking damnit.