skysight-inc/HackerNews huggingface dataset:
I was in a jet taxiing and headed for a runway crossing. I could see out the window a plane on coming in to land on the runway we were about to taxi across. It was clear from our speed that the pilots had no intention of stopping before crossing the runway. I could see it all unfolding and was actually considering taking off my seat belt and running to the cockpit. At that moment the pilot suddenly applied massive braking and we came to a stop just before crossing the runway as the landing plane sped down the runway right in front of us. Frightening.
The other problem with “tech debt” time (and same with “devops”) is it becomes a bucket for all kinds of stuff that isn’t tech debt at all. For example upgrading framework versions, fixing bugs, and so on. Not necessarily wrong to do these instead but it is kind of the team fooling itself.

Instead I think you need the
unicorn of someone who understands product and engineering and can decide at any given time whether to pay down tech debt or add a new feature.
oh wow! ChatGPT is bad because we (humans) can use it to do bad things? is that what the author is trying to say, or did i completely miss the point here?

and if i didn't... seriously?
My team took this approach when we open-sourced our web app. Apache licensed and anyone is free to do with our code as they please, but GitHub issues and PRs are set to employees only.

But whether this approach makes sense really depends on what you're hoping to accomplish by making your code available. For us, the goals were mostly around transparency and assuring customers that if we went out of business, it'd be possible for someone else to operate our service. As a side effect, it's also nice for hiring since candidates can see exactly what our code base looks like, what kind of feedback we give each other in code reviews, etc.
I looked up the Silk icons and they appear to be about half the dimensions (1/4 area) and high color. I was thinking that there were upscalers that targeted and worked well with 16-color/more pixelated images.
Amazon clawed back 401k contributions if you left before 2 years..I can't remember the exact timeframe.
What is bland is universal, what is universal is bland.
Some input: The organism's environment.

Outcome should be: The organism successfully produces offspring

Natural selection is doing exactly what you describe.
The only thing worse than not having any users for your open source project...
what useful purpose have you found for ChatGPT given the “it can return inaccurate results posed as accurate” problem?
Isn't it? I probably just changed it and forgot about it then. Either way, it takes a couple of seconds to switch.
What's hard to follow? Too many people exist vs old ideas need to die which often requires death...is not remotely the same argument. One says we need to cull the herd out of an imaginary number that is viewed as "too many people;" the other says you can have tons more people and have no problems, but old ideas can hold back social and scientific progress which is a problem death of older generations helps to alleviate.
Though small sites might derive a limited income from ads, big areas like google and facebook would certainly push pack if most people adopted an adblocker. Users would soon find themselves locked into a system that proves they loaded the ads.

Money would be better spent creating a virtual screen sandboxed extension for browsers where ads were navigated to the e screen ... where most people could opt not to ever view and ultimately deleted.
I'd be curious about latency for frequent access and the 1MB quota. I think that may make it a similar solution on the surface, but fairly limited in usage.

I was powering a fairly large amount of state, to the point we had to diff state changes due to browser message costs. It was difficult to write, but was incredibly powerful.
Yes, sorry I assumed it would be understood that it did the training and maintained quality.

The irony of pointing out missing context and providing insufficient context myself.
Between Christian states sure, but tell it to the French Cathars or the Baltic pagans. Or heck, the Byzantines during the Fourth Crusade.
FriendFeed lives again!!
Just ignoring someone, IRL or online can have its consequences. The homeless guy can attack you physically. The online troll can try to cancel you digitally.

If the last few years have taught us anything, it is that no one is safe from abusive behavior by people who feel entitled to something you have (money, time, etc.) and seem to have nothing better to do than go after you for the slightest thing.

Online they can badmouth you and your project to everyone they contact. They can leave nasty comments on your blog or in open forums like HN. They can give your product bad reviews. They can issue takedown notices to social media sites.
I think some of us are already doing pay as you go approach. It's roughly equivalent to this 10% but spread out in every few commits.
People die at intersections with stop signs every day, but we don’t do it on our roads for the exact same reason.
Leaning on a code of conduct to fix a cultural problem seems like a losing battle. In the sense that it establishes a framework for moderation, a CoC has some value, although if I'm being honest I think the CoC concept is more about signalling than anything else. But this article already hits on the core problem:

We're living in a culture where a large amount of people think that it's OK to be rude to service workers because it's their job. People who don't return the shopping cart because there's no incentive.

I think that engaging a beurocratic process every time you get a toxic comment will in fact not make your job as a maintainer less stressful. I also suspect that it won't reduce the volume of abuse anymore than just blocking/muting abusive folks. If anything, for most first time offenders, they're probably just tilted and telling them to stop is the most productive thing to do. But abusive asshats don't care about your rulebook very much other than to use it against you, so I really think it's not as valuable as it's being made out to be.

I don't know if we can improve the cultural problem. It really did feel, at least from what I can recall, that "netiquette" was stronger at some point. Exactly what was "toxic" was tuned very differently, but that's not the point. The point is that there were SOME baseline tenets that most people expected out of eachother in a lot of situations. These days, it feels like everyone has completely different standards and really long, complex justifications for their standards on what conduct is OK and when. I dunno if that's good or not. All I know is, "don't be an asshole" is deprecated, but its replacement doesn't appear to be ready yet, whatever it is.

So what do we do? Frankly, my recommendation is to detach harder. I know the "just grow a thick skin" bit has gotten stale, but that's not really the point. The point is to try to not be vulnerable. Detach. Block and mute as you need if politely asking people to stop acting like an ass doesn't work. Try not to take it personally; recognize that most people don't actually mean what they're saying. Etc, etc. Changing the world is hard and slow. Changing your own behavior is also hard, but at least you have more personal control over it.

I feel bad for open source maintainers getting burnt out over this. It's a shame. But, it'd be impossible to have all of the amazing upsides of the internet and open source without some coinciding downsides. You have to be realistic to some degree.
Out of curiosity, how far could this blow?

Silt formerly of the Sahara blows to the Amazon. The Aral Sea's former seabed blows across the province. Will Colorado, Wyoming, etc be affected?
Did the developer have any special agreement or contract with Twitter that the API would always be available? If not it sounds like an unacceptable professional risk to base your livelihood on the whims of another entity.
The basic strategy I use now in writing new code is this:

1. Write out requirements in a form following RFC guidelines: the keywords like MUST, CANNOT, etc. are very, very important because they can be broken out into a spec for a single codepath or function: when your spec says "it always has to do this, and it can never do that", you can make simplifying assumptions.

2. Skeleton code: Your first run at the problem should be to attempt to return answers statically: if "a", return 1, if "b", return 2, and so forth. Many practical engineering problems are effectively "lookup table code" with routine answers and do not need a solution more complex than this. This can help even if your spec implies that a non-linear solution with some kind of algorithm is called for, because it immediately gets you to a point where you are filling out enough of the spec to see if you need to revise requirements, and you can build tests in tandem with this process. Often a run at the problem fails not because you can't keep going, but because you realize that you can define it in a more simple way. You want to iterate towards the simple because the alternative is to heap up requirements that are more incidental in nature(e.g. a feature that exists because of two other features that produce edge cases when used together - a very, very common outcome in complex systems).

3. Algorithmic strategies. OK, you've filled out enough to know that you need an algorithm. What class of algorithm will it be? In the majority of cases it'll be one of these:

"I have an analytic problem using a standard math formula" (therefore you implement the formula)

"I have a sequence of symbols that needs to be mapped into a different sequence of symbols" (this describes most parsing problems)

"I have a data collection or an answer set resulting from a prior event that needs to be searched, ranked or ordered" (list processing, constraint solving, AI; if the data needs persistence, serialization formats, databases etc may come into play.)

Master application of just those strategies, and you've covered many domains of programming entirely. A lot of the literal aspects of coding appear in setting up and tearing down the environment needed to apply that core algorithm, and then in providing enough of a user interface to configure the environment(whether it's an application user or another developer interacting with the code later).

At scale, code is building on other code, but in the sense of "communicating with a ghost". You don't get to dictate how older systems and APIs that you're building on behave. Often you can abstract them, but that only means you're talking with your abstraction, which in due course turns into another ghost if it actually gets put into production.
Thanks for the response! I'm definitely no expert but I think I understand the basics.

Other commenters made a similar point about reserve requirements, I definitely overstated their importance. Interesting to hear about the A&L limits and kind of terrifying to know the limits are self-imposed.
Well, back in my day we didn't have the ability to "block anyone", we just smiled knowing we were the man.
> If you can't ignore negative comments and move on without getting worked up

Expecting everyone to have your opinion is literally entitlement.

Perhaps consider empathizing and addressing the complexities root cause rather than just shrugging it off as, "boys will be boys."
I think the selling point for JWTs are that they're a mostly-standardized way to do auth tokens such that you only need to do one very simple and cheap database query (is this a token that has been invalidated but hasn't yet expired) rather than a larger number of database round-trips to implement various authorization checks.
Look at history. When Europeans arrived on the shores of the "New World", the Natives' culture was effectively over.
Planning to use an iPad that lost two hundred dollars in trade in value between Christmas 2021 and Christmas 2022 as a wall mounted dash board for home assistant.

I'll be sure to add an automation to control the plug so I don't run into this issue
Indeed. The submission headline doesn't apply in 2023. All of the money has been allocated. https://bondaccountability.resources.ca.gov/P1Program.aspx?P...
Exactly. I recall one place where an exec pushed for something to be completed in a too-short timeframe. It launched on the schedule he announced to his higher-ups, so he was promoted and moved elsewhere. Woe be to the exec who inherited the project, though, as the code was basically a mound of turds wrapped in Christmas paper. And the team, of course, was fractured and burnt out. The cherry on top was watching the ladder-climber throw a lunch to thank the team; their reward for hundreds of hours of grueling overtime was lukewarm Chinese food dished out of large aluminum bins in a conference room. Plus $50 gift cards!

This was a long time ago, but I still think about it as a moment when I learned what POSIWID really meant.
> JWTs are vulnerable to brute force attacks once intercepted.

On the linked PDF it says:

> Shorter keys can be brute forced.

Yeah... don't use short keys.

And then also misquotes:

> JWT token cannot be invalidated by itself

JWT _can_ be invalidated, you just need to somehow store the invalidated tokens, depending on the use case this can make sense, since the number of invalidated tokens is going to be way smaller.

> But if we need to send this on every request, we need to persist these credentials somewhere. In a native mobile environments, there are secure options, but on browsers we only have localStorage or sessionStorage, both of which are 100% insecure.

The mobile version is not secure either... You need access to the raw payload, so if the app has a remote code execution vulnerability, the attacker is going to be able to read the token.
Thanks for the heads up that chronological timeline is getting disabled. I've disabled auto-updates for the Android app in the hopes that I can keep it for just a little bit longer. We'll see whether that works in the face of Musk's determination to make Twitter profitable.
Cloud Security Managed Services
Managed cloud security services help protect your business from data breaches, cyber-attacks, and other security threats.
As long as users are running the game on their own computers, preventing that type of read-only cheating is not possible. "Solutions" to this problem come in the form of invasive spyware, such as Warden (Blizzard), Easy Anti-Cheat (Epic), Vanguard (Riot), etc. These are programs that run with the highest possible priviledge, inspect all memory/storage/devices/input, and report what they find to a server.
They renamed it because they decided being a pun on "Kama Sutra" was just weird and unprofessional.

(Same for the NIPS conference. But oddly not for the science journal PNAS.)
Ameristar Charters 9363 is one example of this happening:

> Captain Mark Radloff was thus faced with an almost unprecedented situation: having already accelerated well past V1, he suddenly realized that his airplane would not become airborne. At that point he faced a choice — keep trying to force it into the air and risk failing, running off the runway at well beyond takeoff speed, or try to stop, and guarantee a lower-speed overrun?

https://admiralcloudberg.medium.com/lesser-of-two-evils-the-...
The two hurdles the Fediverse must cross to rule the internet
> California's infrastructure was built to serve a population of 20m but it is currently at 40m and rising with no efforts despite funding in place to increase water storage and service, just bleating about 'droughts'.... The climate anxiety crowd would like you to think water is 'running out' but the reality is just spectacular mismanagement incompetence.

And the climate change deniers would like you to think that money that wasn't appropriated in 2018 still isn't appropriated in 2023. https://bondaccountability.resources.ca.gov/P1Program.aspx?P...
Why upper respiratory infections are more common in colder temperatures
Murphy's Law in action. With this many flights per day, you need tons of safety measures to ensure that mistakes like this are extremely unlikely. Like "defense in depth", you can't rely on just a few layers of countermeasures, the more the better. So yes, red lights at every intersection are good, but retrofitting planes with a gps-style map that shows exactly where to go and when to turn is even better (and of course probably insanely expensive).
> True; but you're going to get much better testing if your team collectively cares about it than if it feels externally mandated by that one annoying guy who set up your commit rules.

Some of the worst tests I've ever seen were in places where managers measured test coverage. Reams and reams of absolutely useless tests that may not have checked anything that mattered, but that did bump the coverage metric up.
I remember reading someone (Steve Albini?) who said, paraphrased, "Your musical tastes as an adult were defined when you were 14."
> It matches my criteria for my own colocated 1U Raspberry Pi server. Mine has additional criteria: I have another Pi for OOB serial and remote reset, an ethernet switch so I don't have to pay extra for a separate drop, and USB-3 to SATA adapters with UASP because the Pi 4 supports USB-3 (> 200MB/sec per drive, simultaneously).

That doesn't seem worth it compared to just buying some old used server, especially if you going to get separate pi just for oob.

Hell, currently on ovh/kimsufi $6/mo gives you 2c/4t atom with 1TB of disk and 4GB of RAM

I pay ~10 eur for colocated 2c/4t atom with 2TB
I personally feel so validated after reading this post. The past 3 weeks have been me personally, painfully re-deriving this information independently.

JS FE culture is so fucking obsessed with “modern” instead of what works best.

I am using a very similar stack to the author, but I couldn’t find anything as useful as this post.

I feel like an insane person sifting for information for React. So much SEO spam clogging google over useful content like this article.
Chrome Extensions could be written in Java using a transpiler like this one to transpile to JavaScript: https://www.jsweet.org/
Should they have said 1994-level? :P
I don't see any evidence they're going to do that, including in the HIG quote the OP posted before. It said nothing about removing options, so any suggestion they are seems like scare-mongering to me.
A colleague of mine was blocked in NY overnight on a flight from Rome in early Jan, as the incoming flight clipped the tail of another airplane right after landing.

https://www.reuters.com/business/aerospace-defense/ita-airwa...

This stuff is happening a bit too often in JFK as of lately...

From the article:
> The Italian airline, noting it fully respects all safety regulations, said in Thursday's statement that "collisions during taxiing manoeuvres are an increasing phenomenon ... especially in highly congested airports like JFK."
Kotlin alone won't implement these features for you. You'd end up with something like this:

val order = loadOrder()

val approved =
order.copy(
approval = order.approval.copy(
confirmation = order.approval.confirmation.copy(updatedOn = Instant.now()),
status = ApprovalStatus.Approved
)

I think I prefer this explicit deep cloning over the automagically generated lenses in standard code, but I can see the appeal. The problem is that mutated copies of immultable objects with deeply nested properties that need to be updated just requiresa lot of code.

On the other hand, if I were to design the application in Kotlin, I wouldn't use such a deeply nested object graph if I was going to constantly duplicate theses objects. I also think constantly creating and destroying immutable objects is a sign of immutability being used in the wrong place; I don't know why you wouldn't simply mutate state if the goal is to mutate the state. With Kotlin, but also Java, you could then very easily achieve these changes.

Lenses are available as a package for both Java and Kotlin so the concept is hardly language specific. People find a use for them in both languages, even if I don't see the point, and that means just switching to a better language isn't the solution here.
At that point just get normal MiniITX board and case
Those two categories are both random af. Are local police "Big Government" according to even half of the people who use the phrase "Big Government"? Are banks that utilize AI "big tech"? What about government intelligence agencies that have venture wings and invest in these companies? How quick a revolving door between the two blurs your distinction? Are you imagining pitched legal battles between the two based on public court filings? How likely are the filings themselves falsely suggesting some schism between the two that doesn't exist?
I agree this sounds like a reasonable solution, though I can imagine projects with this policy may hear about fewer security issues.
The End for Third-Party Twitter Clients
You get that with cheap PCIe SATA ones too, gotta watch out. I eventually traced my NAS problems to that, shitty controller (I had 4 ports off mobo + 2 extra off controller)
Never interact online with your real name. The internet is not a real place. Block the people who are annoying and get on with doing what you enjoy. They can try to cancel your online name all they want. It doesn't matter.
I’m reluctant to use Mastodon because I don’t see it gaining much traction outside of tech. It’s incredibly annoying to use, and the entire concept of how different servers work is far too complicated for any non-tech user. It really needs a frontend to take off that regular people can join without having to worry about getting anything setup.
(Safari has adblockers.)
The Great Salt Lake sits in a big bowl, so it normally wouldn't get very far, geologically speaking. It would affect millions of people though.
Ask HN: Does functional programming increase dev productivity?
Hi HN,

Curious to know whether any of you have noticed significant improvements in developer productivity due to adapting a functional style of system building?

On the surface, it looks like FP will lead to a more modular and decomposed system, and hence would lead to greater re-usability and maintainability.

Moreover, if you have any thoughts/experiences on how adapting FP impacts a software dev team (or just individuals) currently operating in imperative style, please share your views.
It will. There’s no ambiguity about it. The only ambiguity is whether the effect is responsible for all aging symptoms or just most of them.
I wish Awk had capture groups. It would fit in so well with typical Awk one-liners to be able to say:

awk '/foo=([0-9]+)/ { print $1 }'

although I suppose the syntax would have to be different since $1 has a meaning already.

Yes, gawk has a function that returns capture groups, but it's a bit verbose for one-liners. Instead I switch to Perl:

perl -nE 'if (/foo=([0-9]+)/) { say $1 }'

But I wish I could just use Awk.
Can they cover it over? Like with a tarp weighed down with rocks? I welcome the reasons why this is a stupid idea.
Breaking the law does not solve all the issues I listed so easily. It does easily solve the issue of killing somebody who had taken military action in a country that the US military is already in.
> lack of elevator control

This was the case with Ameristar Charters 9363, which aborted after V1:

> [T]he jammed elevator could only be detected once aerodynamic forces came into play — something which would only happen once the plane was already speeding down the runway. The NTSB was forced to come to an incredible conclusion: that there was no way for the pilots to have detected the problem until they attempted to rotate for takeoff.

https://admiralcloudberg.medium.com/lesser-of-two-evils-the-...
PITA

With normal install you can just configure unattended-upgrades (on Debian at least) and mostly forget about security updates, they will just happen (can even set a schedule for reboots for kernel updates IIRC).

But IIRC boot on card + root FS on SATA or USB-SATA works just fine and you only get some writes off occasional kernel update
Libre Computer (SBC's)