skysight-inc/HackerNews huggingface dataset:
Sure. I'm talking about the bulk of the CS PL field as a whole, and I don't think I'm disagreeing with the author of the post. (Do note, however, that the author left academia and is now in the field...)
Noted; basically I'm just saying that Musk won't care about treaties, and given the US' silence so far on his 'terms and conditions', I'm willing to bet they'd go along with it; in fact, wouldn't be surprised if the US 'suddenly' took things over and started staking claims.
When Covid hit, I stopped doing regular sports, because everything shut down, even tabletennis, which is an individual sport and safe. So I gained 10 kilo, and it's not getting better because now I have to do my own cooking, which tastes so much better than the previous food I just got somewhere. It changed my life, and my table tennis is getting worse and worse. I won't be able to go pro for sure.
I agree with your assessment. Using the language "tech debt" makes it appear that there is a correct way to design something and that if you're not doing it that way, you will need to pay a debt on it, now or later.

The reality is it's all trade-offs and sometimes those debts never need to be paid at all. "Bad code" that is reliable within the constraints it is exercised and that is isolated may appear to have to tech debt, as in "if we changed the design, we could support XYZ feature" but if XYZ feature never materializes, it's a waste of time to touch it.

Maybe we can come up with more appropriate language for this? Something akin to "inflexible" code. Calling something "debt" assigns too much subjective value to it while making it seem objective.
> According to the article, it was one Canadian employee told by one Canadian supervisor that this was a no-go. There was no "Poppies is bad!" memo from Austin or Seattle. It was how a single Canadian manager chose to interpret the dress code.

This is egregious cherry-picking from the article. While one sentence says "An employee of the Whole Foods in Ottawa says", the previous paragraph says "U.S.-based Whole Foods Market says poppies aren't allowed [...] which affects employees at its 14 locations across Canada", and the one before that (the first in the article) says "a national grocery store chain has banned its employees from wearing the symbol of remembrance". Later, the article says "A poppy does not comply with that policy, the company confirmed", referring to Whole Foods, not any specific location. The sentence that you're quoting, read with any context whatsoever, is clearly anecdotal evidence provided to support the claim that Whole Foods both has a policy against wearing poppies, and is enforcing that policy in at least one store.

> Further along in the article it shows the problem is provincial law

I don't know what the hell you're going on about here. "would not be protected" is vastly different from "is not permitted". This sentence merely clarifies that Whole Foods' action is not explicitly illegal, not that it is required under any law.
It was misleading because it was leading the reader to conclude that it was intentional when in fact it was A) an accident that B) was quickly rectified.

That's what misleading means, to lead amiss.
Many of the core examples of rogue-likes have the concept of bones files, where you can encounter the level a previous character died on. So in those cases some runs affect some future runs.

I assume that what's being talked about in DCSS and Hades is a stronger effect, though?
Good advice. This is not CA, but my understanding of state law here is that I will not be eligible for unemployment if I resign or if I'm terminated for gross misconduct. Unlikely that they can claim gross misconduct given the circumstances.

I definitely won't resign until I get a signed document from them.
At this point I feel like some crazy person talking to themselves when I say this, but "AI" is a research field that includes many more sub-fields than machine learning, let alone deep learning, and it's impossible for someone to be an "AI Expert" while ignoring this, even if they think they are because they ignore it. I appreciate that synecdoche is a thing, but to recommend a "roadmap" to becoming an "AI Expert in 2020" while ignoring most of AI is...

... well I don't know what it is, anymore. Sign of the times? Perhaps the field (AI that is) should abandon its name just to be sure that if a backlash ever comes against deep learning it won't take everyone else's reseach with it?

On the other hand, I feel a bit like the horses and the cows in Animal Farm, when the pigs took over the Revolution. Not that there was any revolution, not really, but the way that the research trends have shifted lately, from what would make good science to what will make you hired by Google, is a little bit of a shock to me. And I stared my PhD just three years ago. It's come to the point where I don't want to associate my research with "machine learning" and I don't want to use the term in my thesis, for fear of the negative connotations (of sleazy practices and shoddy research) that I am concerned might be attached to it in the time to come.

And it's such a shame because the people who really advanced the field, people like Joshua Bengio, Jurgen Schmidhuber, Geoff Hinton, Yan Le Cunn etc are formidable scientists, dedicated to their preferred approaches and with the patience to nurture their ideas against all opposition. The field they helped progress so much deserved better.
Mipmaps aside -

I remember texture pop-in being a common complaint for the original RAGE (and being one of the complainers). But i replayed it recently on a regular SSD and the effect was barely noticeable at all. So i'm confident that an NVMe disk with direct GPU DMA will really make this a non-issue.
It is beautifully efficient from a top-down perspective, but it turns out employees like the consistency of a known work location each day

I worked somewhere once that tried this open-plan hot-desking nonsense. The HR dept kept their nice private office with fixed desks however. They said it was because they had to deal with confidentiality. Whereas us dumb engineers developing the IP of the firm presumably didn’t...
That's why you need good engineering managers. If you can convince people that something is important then all of a sudden the business finds a way to make it happen.

What would happen if you said you need another developer to hit that delivery goal. Good chance you'd get it, right? A good EM should be able to articulate the value from non-functional work and refactoring.
Here's another interesting one, from Detroit [0]. A software glitch resulted in recording incorrect vote tallies, with a +6000 swing in one county for Biden's favor. The same software is used in 47 other counties.

> results on electronic tapes and a computer card were accurate but it appeared that some of the results were somehow scrambled after the cards were transported in sealed bags from township precincts to county offices and downloaded onto a computer

[0] https://www.freep.com/story/news/politics/elections/2020/11/...
"Classical roguelike" or "traditional roguelike" works fine.
> Several of the engineers I worked with a few years ago left Intel (for the company I work at) after they switched to hotdesking to save money on facilities.

Throwaway account as I work there, but I'd like to make some minor corrections to this: I don't think most of Intel ever switched to hotdesking. It was a trial program. In my building it was on one or two floors. I can't speak for all the locations, but most of the other buildings at our site did not have this at all. Unfortunately I was on that floor and hotdesked for 2 years.

I'm pretty sure none of the process/fab folks were hotdesked (I used to work in that area and stayed in touch with those folks). Nor did any of the circuit designers/architecture folks get hotdesked. After a few years, the trial was over and everyone reverted back to having their own permanent desk.

It's incredibly unlikely that this is a reason for Intel's decline.
Suricata can do 40Gb/s on a single server using AF_XDP and eBPF for bypassing traffic that will not be inspected. (Think TLS after the handshake)

https://suricon.net/wp-content/uploads/2019/11/SURICON2019_P...
Why risk my career, my bridges and (who knows?) my law license?
But it's not even relative anonymity. It's psudeonimity. It's a completely different thing we are not used to dealing with.

Unless you actively try to hide your tracks, every single transaction you make is related. You may pay your friend at work $5 back for coffee using Bitcoin -- and at that second -- since he knows your wallet id -- he can check the blockchain for every transaction your wallet has ever participated in - every website you paid for (as a captcha, as a registration fee for that totally-legal-but-morally-questionable site, the money you contributed to support/oppose a political cause, etc.)

This is NOT paranoia. People who aren't the NSA are constantly analyzing and making public identities related to wallets and transactions they made. Psudonimity is not anonymity - it's one step away from being an identity; and the fact that the blockchain is public makes all history public for an identity once that step was taken.

Take cash from ATM. Put in wallet. Use cash in wallet to pay for drugs. Use cash from same ATM from same wallet to donate to church. Only NSA/FBI has the means to track this, and they have to work for it.

Put money in bitcoin wallet. Use wallet to pay for drugs. Use same wallet to donate to church. Now church knows you paid for drugs, and your dealer knows which church you contribute to.

Brandan Eich was forced to resign because of his political beliefs, as evidenced by his monetary contribution to some political cause[0]. If pseudonymous blockchain payments become mainstream, such events are going to become an everyday occurrence. For some things, that's a net positive for society (you want to know who the hypocrite politicians are). For some things, it's a net negative (losing privacy for individua).

[0] I'm tryting to word this as neutrally as possible.
If enough people file individual actions with the binding arbitration company, they'll _wish_ it was a class action instead.
> Cubes and open office are bad enough but hotdesking is the next step.

It's not that simple. I worked with hotdesking at Intel. Those workstations, although still small, were bigger than the (assigned) ones I saw at Google and Facebook when I interviewed there, and Intel's one offered more privacy. Visiting those companies for an interview was depressing - finding out your crappy cube at Intel was still better than the ones at FAANG. Surreal.
Is there any advantage in using this method over HMAC with the key stored in the HSM, without pepper or salt? It seems overly complex to me but I'm not a cryptographer.
I'm not surprised it's missing from here, but Dream Quest was an important link connecting Dominion-style deckbuilding with additional roguelike elements. It was a key inspiration for Slay the Spire and everything that followed from it.
Thank you!

In this case it's a similar checklist, and I'm sufficiently junior that the company doesn't want to fight it.

Glad to hear that getting fired doesn't have the negative connotations. It is certainly tempting to enter a downward emotional spiral.
Alan Kay on Dijkstra, (1997 OOPSLA keynote): 'I don't know how many of you have ever met Dijkstra, but you probably know that arrogance in computer science is measured in nano-Dijkstras.'

Was this article written by Dijkstra himself?
Great idea! I was not aware if that!
Major League Hacking 2021
>Further along in the article it shows the problem is provincial law, not the policy of an American company:

That is, as I read it, merely saying that the provincial law allows them to ban wearing it not that it requires them to ban it. So the issue is very much with the company and not with the law unless you're saying that we're only allowed to complain about things that are illegal?
They’re not useless. They stop passive adversaries, like the Australian government. They just don’t stop active adversaries.

Browser security warnings imply https > http > self signed https. The correct order of should be https > self signed https > http.
Yes, that was my conclusion as well.

A general pattern I see in software is that it scales up much better than it scales down, and Kubernetes is definitely like that. I had hopes it would be useful and educational to run for personal projects, but it's just too heavy.
I've seen a situation where old IDs were re-used for new users, like we were about to run out of numbers or something… XD

And with former users coming back, of course expecting to have their IDs back too !

This being on a paper-first (often paper-only) database, with no locking process, where we also had the issue of new users being added at the same time, for the same ID.

If only I already had been through a database course at the time…
From the spec:

Servers MUST use TLS version 1.2 or higher and SHOULD use TLS version 1.3 or higher. TLS 1.2 is reluctantly permitted for now to avoid drastically reducing the range of available implementation libraries. Hopefully TLS 1.3 or higher can be specced in the near future. Clients who wish to be "ahead of the curve MAY refuse to connect to servers using TLS version 1.2 or lower.
Yeah. And there exists a very scummy form of meta-gaming exploit known as bones stuffing where you deliberately create well-stocked bones levels for future characters to find.
Last time I encountered mentions of [1] was in "Humankind" by Bregman, and there he says it was not really "scientific" experiment, stretched some facts.

https://www.ft.com/content/63803e14-95d9-11ea-af4b-499244625...
> One of the biggest challenges security engineers face is getting software engineers to fix their bugs.

Oh my, don't get me started on that. Usually it's not worth talking to maintainers who don't understand security implications. Either walk away and choose something else or maintain a fork with your fixes. This is usually the easiest. And trivial with git to automate.

But hiring penetration testers just to convince some moron that this bug is exploitable? Come on!
Is there any indication that Intel will move to this chiplet design? It seems like it's a no brainer and it's been proven to work by AMD.

What's keeping Intel from adopting this same practice? is it IP?
No, try .aq!
That type of mechanic is often referred to as rogue-lite
This is a game of energy. The energy necessary to deflect an asteroid from earth is undoubtedly lower than to put it on that course to begin with. It's really not MAD.

Also, sending a nuke could be done much faster than an asteroid intercept mission. It could get there in as little as a week.
I'm actually working on a library like that for Common Lisp, but it's still very much a work in progress.

My goal is to have a framework where I can experiment with different parts of OpenGL by sub-classing something and then override a method or two, and have it "just work" with everything else in the framework (shaders, viewers, animation, user interaction, etc.)

https://github.com/jl2/newgl/tree/buffer-refactor
Yikes! This doesn't really come across as a nice comment (bent minds???). There are good concrete reasons to pursue a PhD (ignoring soft reasons like pure interest): wanting a research career is one - it's pretty difficult to get hired as a scientist without a PhD. Also, historical evidence doesn't really support your claim that R&D is orthogonal to business value. Sure, pure science is often independent from $$$ (despite plenty of examples of producing real value), but applied R&D is oftentimes parallel to value generation. if R&D in general is useless, why do top tech companies spend big money on research groups?

Getting a PhD is a fine deal if you have good reasons.
ImGUI has backends for every graphics API in regular use, and some that might be considered deprecated (DX9). Including game engine abstraction layers in Unreal and Unity and console properietrary APIs (not public, of course). Here's a full list of public graphics APIs and windowing systems part of the official release (https://github.com/ocornut/imgui/tree/master/backends). Maybe with the exception of stb_image, it's only of the most integrated open source libraries in games and graphics
Dream Quest is great! I have it on my phone and enjoy the odd run every now and then. It has a ton of stuff to unlock!
unified2 is not a great format and does not sound very flexible for further development. The JSON marshaling is expensive but is not the first of my worries when doing line rate inspection on traffic at those rates.

I think most shops have a million integrations that they want to set up for their IDS alerts and JSON is pretty close to a lingua franca.
I more and more think we should challenge that difference. IMO software engineering is bad in many ways because we lack experience. And we do lack experience because we do not repeat what we do. Most developers work on legacy code that is older than their own stint at the company. Yet, the constantly ship new features. That means they are constantly working as maintainers and producers in parallel.

My suggestion would be to have dedicated producers and dedicated maintainers. And software should have a planned shelf life. You should buy a piece of software the way you buy a house. Huge up front investment followed by a long period of negligence interrupted by frantic maintenance efforts.
Maybe it's not about minimizing time spent, but doing something you enjoy.
I started with just YouTube screencasts. After I had a couple hundred subs, I made a video asking if people were interested in additional premium content and shared a link to a survey. About 70 people saw the video, 22 filled out the survey with their emails and seven paid when I offered an earlybird discount.

After that, I built a "real" but very minimal site and created a subscription business. I've put very little effort into marketing other than the fact that most my videos are free.

I probably picked too small of a niche but it's what I was into. It may be hitting its growth limits, but it's in the 4 figures / month MRR range.

My main advice is to focus on being helpful over UI, business models, growth hacks, etc. The first step is to provide value. After you can do that, then start worrying about how to capture it.
Hades is typically called a roguelite, and the progression elements are rather strong for the genre. You get significantly more powerful with some permanent upgrades. This does make a lot of sense for the game, especially with the strong focus on the story. You want most players to be able to complete the game after a certain amount of tries, but not too early to shortcut the story. And the real difficulty slider is in the endgame anyway.
This what I was wondering too. 20k steps might take around 2.5 hours every day which is a lot.
> I assume that what's being talked about in DCSS and Hades is a stronger effect, though?

Very much so. In some games, past runs only unlock additional content (more possible items, monsters, etc.). In Hades, for example, you actually get stronger with each run.
It is not? I an not saying he was grooming him necessary, but overnight trips are not normal behavior of teacher trying to help poor gifted student.
>One of its founding pillars is a teleological universe which, thanks to advances in science, we now know to be false.

No, we don't. We know that if a teleological universe is true that it is a lot more complex than previously thought, e.g. that evolution would have to be a part of it. That isn't a disproof of a teleological universe though.
A quad core A17 is less than that at quantities under 1K pieces so why bother? When I looked at RISC-V I was hoping I would be able to get something similar to ARM SoCs but without the large number of peripherals I don't care about, like video decoders, jpeg decoders and what not. All I wanted was just a lot of ARM cores in an SoC, and if possible multiple I2S ports or at least a bus I can attach an FPGA to which can handle multiple I2S ports for me. Or perhaps an ARM SoC with onboard FPGA. That already exists but again too many useless peripherals and not enough CPU cores.
"...debt repaid quickly afterwards"

If you're telling them it was a test and providing feedback, then I could see that eliminating my concern. I think I wrongly assumed (based on my past experiences) that it was done in secrecy without telling them it was a test or how they did.

Even though my organization requires interview feedback for internal candidates, it's rarely helpful or insightful.
I think you are absolutely right when it comes to anxiety. I think it paralyzes me on certain days but then I have a framework similar to what you are alluding to in dealing with it.

In a weird way, it's a good feeling to know that other people go through similar ups-and-downs. Thank you for your comment.
Neat. Glad to see this heading to release. I represented Google at a few of the ISO meetings years back before another team took over.
But isn't the term "Technical Debt" meant to help business-people understand an issue that, while real, and though inherently grasped by people who write software, not necessarily by others in positions to make resource allocation decisions? By calling it "debt" it is put into financial terms everyone understands.
If it is a red flag, it is in the sense that people are making decisions about software, who don't understand how it is built and maintained. That is the case in a lot of environments.
I believe with the latest versions of the APIs, the fixed function pipeline stuff is now emulated in the programmable pipeline, but the two don't mesh well, so you end up with particularly bad performance. I've had to find and install the old DX9 runtime to get some older games to run at reasonable frame rate.
People landed rockets vertically in real life for decades beforethen.

What SpaceX did was to put a second stage on top of that, scale it up, and make it automatically guided. You're going to have a very, very hard time arguing that this is anywhere even near the level of innovation that NASA or the Soviet space program achieved in a third of the company's lifetime.

As for the stagnation in space, sure. That's the issue with government programs in our current paradigm, they are heavy and the best course of action is seldom taken. Also, for some reason the US has an aversion for SoEs, so NASA, for ideological reasons, wouldn't have been allowed to make their own reusable launch vehicle and make a profit out of it.
I genuinely don't think that's a fair characterization. People watch those guys like hawks. I still remember the endless lies about the fish food with Abe, completely distorting reality. And this time it's a huge deal. At the time the things you listed were not known. And the words used were were tame for the magnitude of that event. I can't see any wrongdoing. If sides were switched, people would not frame it like this.
I have not played Hades, but I think referring to these types of games on a spectrum is more apt.

In The Binding of Isaac, each run starts the same. The difference is playthroughs allow new items to be found, but the main character is not enhanced. FTL unlocks different starting ships, but there are no "upgrades" as far as I'm aware, just different ships with pros and cons.

In Rogue Legacy and Crypt of the NecroDancer, successful playthroughs enhance aspects of the main character. This to me is a hallmark of roguelites. The Binding of Isaac technically has iterations but since only the random item pool is modified, I would keep it in the roguelike camp.
Exactly. The “easy choice” is to drop support for those users. I suspect most web developers won’t even notice.

It’s a pity - there’s no essential reason why old phones with new batteries should get worse over time. But software kills them in so many ways.
I was confused about that too; roguelite seems to have caught on pretty well these days, especially in the PC Gaming community.