skysight-inc/HackerNews huggingface dataset:
I'm very sorry if you can't see how this is getting out of proportion and more and more irrational, it just means you're lacking basic sense of observation and I recommend you to work on that.

And regarding the word "master", do you think a black guy will get offended to get called a masterchief ? a chess master ? no way... It doesn't make any sense. There were hundreds of millions of white slave in history, and still white people don't seem to get concerned by that, because it's not used for "political" matter.

I'm always surprise on HN to see the smartest people falling for the dumbest propaganda.
Regularly asked question. The reasons are many and on the top of my head:

prove of work protocols are an energy sink, no matter what crypto proponents bs about it.

most use cases of a ledger could be done with a proper centralized service with a good database.

crypto money do not scale and lots of the regulations they don't apply have actual sense.

lots of crypto marketed stuff is actually pseudo distributed, pseudo crypto, and often just a scam.
Hello from the Cloudflare team - thanks for the nudge. We're in the process of migrating away from the proprietary license to an Apache license. We'll update the GitHub issue too; should be wrapped up in the next couple of weeks but likely sooner.
He probably thinks of frontend as

„my static blog and I cant get the text centered, damn css!“

instead of

„basically a full blown native application but written using browser APIs, with live collaboration features, GPU-using code where performance matters, oh and did i mention it must also work and look good on a mobile screen?“
Its copyright law that is being broken here that makes it illegal, not breaking the license/contract.
Yeah, this feeling is ubiquitous among programmers (or 'developers' perhaps), and I suspect it's a large reason why businesspeople are suspicious of "we need to invest time paying down tech debt".

There's a big difference between "this code is horrific and can't be built upon" vs "ugh, this framework is so old, we need to rewrite it in Foo.js".
I like the term because it is like financial debt, and is a good way of communicating the problem to a business person. The debt will need to be paid off at some point, the longer you leave it the more that is going to cost, and it costs you even if you just keep paying the interest. Framed this way, it also helps us explain why many business people don't care. Many will only care about the projects they are currently responsible for and not about next weeks or the ongoing health of the company. With luck, paying the debt will be somebody else's problem. If you called it 'cutting corners', you get a pat on the back for keeping costs down and expected to do it more often. You might even get a bonus if your boss doesn't take the credit.
Same here. Not fan of Apple or Facebook as a company, but would definitely take their offer over anything that is plaintext and carrier-controlled.

At least with iMessage or Messenger we have a way of sending encrypted messages of almost any format. (Clarification: not necessarily E2EE but at least encrypted to a non-carrier company)
Reminds me of when every US newspaper basically plainly copied what the gov said about the strikes against Kata'ib Hezbollah being in response to a hit and run toyota-rocket attack of theirs on a US base.

Not a soul that took note of the fact that Kata'ib had denied any involvement or that this happened very far away from where they held power and deep in territory with an enemy local group that had instantly claimed the attack.
Eliciting latent knowledge: How to tell if your eyes deceive you
I did not say that I'm slow due to this or not agile.

But I will not build a sync feature and not having alerting if it fails.

I will not write nee Features and will not think about a proper index.

If you do it right and actually learn those things from an early point those things become obvious.

And yes there is also that believe that a bug in production costs 10x what it would cost to find while developing.

Yes I'm aware of the fallacy that a manager might praise you if you are fast and accepts bug as a common normal thing.
For D-T fusion, the output is 80% neutrons, so the only option is to let them heat something to run a turbine. You also need the neutrons for breeding the tritium, so you let your breeding blanket heat up and run coolant pipes through that. Commonwealth plans to use molten FLiBe salt as the breeding blanket and first loop of coolant.

Aneutronic fusion produces fast-moving charged particles instead of neutrons, so if anyone gets that working, we could extract electricity without a thermal cycle.
It is not the same. Financial debt has to be on the balance sheet; technical debt is not. My point is the a finance/business guy will think in the totally wrong direction with what you actually mean. Also to whom do you repay technical debt?
Techincal debt is a typicall long term problem without a short term solution. Product managers are biased towards delivering short term value incrementally, and don't like anything that slows down the value delivery pipeline.
> Technical debt is something that 'business users' don't need to or want to care about.

Sometimes it's hard to tell your manager: Yes I know you want to track every single coding task in Jira, and you don't see any immediate value to this one, and I'm not going to dispute that, but I am going to do it and you "don't need to or want to care about it".

Sucks not to have that autonomy but it's real. That's when you have to justify the refactor, and not with potentially offensive statements like above.
Guess it depends on your management.

I've often told my boss the feature would be easy, but I would also like to take the time to clean up the code in the affected area since it's making it harder than it should be to implement changes. And I've gotten some time extra to do just that.

Other times I say doing it fast and cheap is possible, but I see an opportunity here to do something more clever and involved which will very likely open up further possibilities down the line. For example, I might predict other clients will need a similar feature, so by making my code a bit more general it should be easier to implement if they come asking for their variant.

Sometimes I get a green light on that, sometimes I do not.

I guess it helps that the owners are playing the long game, so my boss can afford to see beyond the next quarter.
Yeah, but they dock your pay 30-35% for living outside a few select tech hubs. While I understand how such a thing made sense in the past, and could even understand a small difference, I think we're past the point where a 35% difference is fair.
Yes, I want HD Radio. In Los Angeles, KROQ's secondary HD channel plays KROQ as it existed in the 1980's, including some old jingles and such. I think it's such a cool idea.
In civil law countries it is. Also you can be sued for it.
Well, I certainly don’t know your friends but I can say that in my experience the guys who _said_ that tended to have, shall we say, gaps in their self-assessment or were unable to accept that there was nothing you could do to make one specific person feel differently.
From what I gather, TCAS is tricky at an airport environment as there are "close calls" somewhat routinely. Resolution advisories are definitely inhibited. Some more info here:

https://skybrary.aero/articles/tcas-ii-activation
I got the same feeling. I was immediately overwhelmed with cringe and disgust when I landed on the page.
A lot of Peloton in the news lately. Is there anyone that owns a Peloton machine that can comment on what they like and dislike about Peloton? Have you guys noticed a decline in the product, software, classes?
4c group might be able to help you - https://www.4cgroup.co.za
Excellent, thanks for the update. Apache isn't what I would have chosen but is reasonable enough.
So to get into his home we just need to clone the MAC address that he constantly broadcasts everywhere?
No, pull requests are not illegal, at least when done on Github, because by posting code on Github (that you are allowed to post) you grant Github and its users certain rights:

https://docs.github.com/en/github/site-policy/github-terms-o...

> By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).
> One other question that might have an obvious answer: how did the pilots become aware of the other plane?

I assume they saw it.
It's the best performing PC in that form factor and has actually good enough battery life. It's not GBA battery life but it's on par with the V1 Switch, the Vita and the PSP and considerably better than It's PC competition which are more like 1-2 hrs vs. 3-5. It's also the fastest and costs considerably less. Performance seems good for a PC half the price of even a cheap gaming laptop that's also considerably smaller. The only difference between tiers is storage with the base model having eMMC and the upper ones having NVME.

And we haven't even talked about software like resume feature yet. If that works it will fix my biggest pain point about PC gaming.
Anytime is possible for the data that returns to be interpolated by the client, you could have xss or related attack.

Client side rendering does help but mistakes are still regularly made. Sometimes by the app dev, sometimes by the framework dev.

You could probably go to an extreme and return all of your application data as sprites.
Also, the supposedly free crypto markets often have a few whales who can manipulate the price and can rob smaller investors from their money.
Missing from that article is how much energy was used to get that output.
Thank you! Sometimes the HN comments really pay off.
Well, if too many corners are cut, people understand it as well 'for this feature we have to fix the architecture, we have been cutting too many corners, so otherwise the whole thing will crumble' makes it pretty clear. Also it term makes it clear why the state is as it is (since cutting corners also 'solves' problems). How do you explain why engineers would have been allowed to take on debt on the company?
How the modern world arose from imaginary numbers
That makes sense. In the UK you can buy induction hobs that plug into sockets, but they are limited to a measly 3.7kW or there abouts. A nicer 32A induction hob needs hardwired (single phase).

You can have upgrade your domestic supply to three phrase, but AFAICT it's uncommon. Perhaps with electric cars and induction hobs replacing natural gas and petrol, it will become more common.
I think the concept here is similar to the behaviour a lot of people exhibit when trying to say 'no' to something. Generally the 'no' is non-negotiable, but a layer of reasoning is added on top that invites the other person to negotiate.

Person A: "Sorry, I can't do this because of X, Y and Z."

Person B: "Well, can't you do X, Y and Z another time instead? This is important."

You never really wanted X, Y and Z to be part of the conversation, but now they're in it and you've been placed on the defensive. If X, Y and Z were never mentioned in the first place, they wouldn't be on the table and you wouldn't have to justify them.

Same as it is with stuff like tech debt and non-functional requirements. You want to do them, you most likely have to do them, so bake them in. Keep the tech debt and NFRs off the table but leave the features open to negotiation.

Obviously has to be within reason if you want to maintain credibility, so you've got to figure out how to prioritise your tech debt too. And sometimes that means you don't do any of this and you accept a bit of interest on that debt.

Tradeoffs all the way down.
> Good writer

I would posit that when you write hit pieces (either for your own convictions or money), you are not a good writer.
That license doesn't allow modifications, which is what pull requests are. The forking thing is only about making copies, not modifications.
I love Tailscale, but it’s not really designed for public tunnels. You can do it, but you typically need to provision some kind of proxy with a static IP (most likely cloud based) to handle your public stuff.
That would work really well if it were possible & straightforward to consistently estimate complexity story points, independently of time. Even better if you could (ditch Fibonacci, necessarily, and) objectively match each complexity value in linear scale relative to the others.

In order that you could say 'it's now taking us twice as long per complexity point as it was last year', and know that that was meaningful.
There are no slow desktop computers in 2022. There is a lot of slow software running on fast computers.
One of the three analyzed files has a last modified timestamp of Jan, 14 2020:

https://twitter.com/dmoulding/status/1491593763466088448?s=2...

That could be the time of sequencing.
wasn't that the idea of ssh to begin with?
Microsoft starts a charm offensive to push through its Activision deal
Lots of people have fought with technical debt for a long time, and if it was as easy as just being like, 'oh hey, we just do it next sprint' it wouldn't be a thing.

...it's not that easy. It's not easy.

I'm not saying it's easy.

I'm saying: If you do the easy thing, which is always choosing to leave technical debt behind, and waiting for someone to come and tell you its ok to deal with it... you're going to have bad long term outcomes in your project.

Part of your job, as an engineer / developer / whatever to spend a portion of your time not just doing work, but ensuring you can continue to deliver value in the future.

Here's a metaphor for you:

Some people like 'release based' branching; because you can push all your changes into develop (however messed up they are), and then some poor soul has to someone pull out a release candidate and then slave away over it to make sure it works...

You release seldom... but, most developers don't have to worry about it (just the release manager), and its fine.

Some people prefer trunk based development; it's harder.

Every merge to master you have to make sure your code actually works, because hey, it might go live in the next 2 hours.

A lot of people really hate this, because it means they have to do a lot of work and they cannot push the hard work onto someone else.

...do you see the metaphor?

I think it's pretty relevant.

Address technical debt slowly and continuously, not rarely and massively, and you will, in my opinion and experience, have better outcomes.
There are now locks for your front door that can be opened using a numeric code or a fingerprint or even an nfc fob.

Likely any of those would be more robust.
.NET Rocks: Twenty Years of C# with Anders Hejlsberg
Walks at lunch. Standing desk. Exercise bike under the desk. Weight machine in the basement. Swimming during the summer when it is warm enough. Running in place when streaming instead of sitting.

I do all of those a little bit. I'm no athlete, and am still overweight, but having a large number of things you do less often than you should is still better than just sitting.
"but those can't both be true"

They can. I think you're missing one of my key parts - without assistance. It's highly likely single mothers are getting child support. It's possible they are getting assistance too.

Just look at the stats on how much people have saved in emergency funds and for retirement. That should show you the dire need for two incomes.
Steam Deck: Hardware Review
I used to read physorg and other publications and would get really excited by all the new discoveries. But then decades go by and you sadly never see most of them realize.
No one is saying you have to needlessly screw things up. If you're writing things in an equally laborious but worse way, that's just being a bad programmer – nothing to do with tech debt.

Tech debt is more, say, "let's build this new bookmarking functionality by saving bookmarks locally" and then, later on, "let's make it more extensible by syncing them with the server, so we can build on it by e.g. using this information in our new recommendation algorithm".

It's about implementing things in a less complex but less extensible way, and perhaps a less feature-rich way, so as to more quickly validate user demand and thus iterate more quickly.

And yes, it's trivially true that you'll be slower than you could be otherwise by not doing this. You might think you're still faster than other people will be. I wouldn't bet my own money on that, but it's your prerogative to bet yours.
Revisiting: Empire II: Interstellar Sharks (1983)
At a tech company? Definitely the CTO and CEO should be talking every week.

Months is VERY weird.
You're right, but I think parent was joking
I've never witnessed that kind of hardware problem precisely, but now just think about it: what would happen if the same situation happened on an AWS instance? How would you go about debugging anything and/or fixing it? It's not even sure you could diagnose the problem in the first place, let alone deploy a workaround. You'd have to send dozens of email to tech support who of course would say there is no problem because their machines have 999999999999999999% uptime and nothing could be wrong on their side, but hey they can sell you advanced support/engineering if you've got way too much money to help you find the problem in your code.

Some commenter mentioned the dark days of Oracle/Microsoft/SAP ruling over the server market. But at least these companies had the most basic decency to let you house/access your own hardware and diagnose things yourself if you had the skills. Now in the "cloud" you can just go to hell and suffer all the problems/inconsistencies, or rather your users can suffer since you as a sysadmin have zero control/monitoring over what's happening. Oh and bonus point: if users report some problems, they will be reproducible 0% of the time since there are great chances your users are connected to a different availability zone: yeah it's easy to reach more than 5 9's when "ping works from a specific location" counts as uptime for a global service.

So in the end, is it better to have a silly answer to "Why was the database upgrade delayed this time?"? Or is it better for the answer to be "i don't know, but upgrading the database cost us 37k€ in compute, 31k€ for storage and 125k€ for egress for backup of the previous db" ? I much prefer silly answers, but maybe that's because i don't have dozens of thousands of euros to be shorted of even if i wanted to :-)
No I meant it exactly as I wrote it, without any judgement. Aspirin is just used as a generic term for painkiller by a lot of people, and until like 10-20y ago it was also the most common thing. I'd say most people are migrating to Ibuprofen these days for stuff like "I have a headache that's not killing me" but people still say Aspirin, usually followed up by a question if whatever is available is ok...
BBC cryptocurrency documentary pulled from air at last minute
One and only one data point: the handle allowing the chair to move forward and back broke 2 months ago, about 6 months out of warranty. (Great for my partner, who now has exclusive use of the bike in her position… not so good for me.)

Support originally wanted to charge me $250 for replacement and service. A few YouTubes and a second call, the service person admitted that a $5 part would probably do the trick.

It’s taken two full months from that support call to get the shipping notification on that part.

Other than that, though - my experience with the bike and classes has been positive.
The Open University. It’s reputable (although by no means in anyone’s top 10 rankings), let’s you go your own pace and the tuition isn’t too bad.
For sure! And most of the time I would say spending 20x the time on a thing that you have no flipping idea is going to land is worse than technical debt, its called closing your doors.

I just wanted to call out the posters who blame individual eng for the product quality, they've either never worked in a toxic org or are helping be the source!
One of my earliest memories is of a TRS-80. I was 4 years old when I saw my first computer program. My brother (10) showed me a program he wrote a that would print a pattern of Xs on the screen.

It blew my mind that he was able to tell the computer what to do.

I can't remember anything about the computer before that memory, but I must have assumed the software was just magically there, not that humans had put it there. Not that a regular person like me could write my own programs.

That event made a big impression on me. When I was 7 I started teaching myself BASIC coding on our Atari 800 using a book I found on the family book shelf.
It is quite obvious that Laravel is written by an American, they all do understand marketing better than us Europeans, Artisans creates works of art and it is eloquent even if it isn't.

What is great about Laravel is all the addons you can apply seamlessly.

But I can't say I like the overall design, too much magic for my taste and all the non-strict typing. Put things in the correct directory and things happen is generally a bad design. Use magic name on class object either as a property or a function and different things happen.

I do understand that it is easier for the framework developer to have loose typing, easier to swap implementations between major versions, but it makes it harder for the framework user. I have to, at least in older Laravel versions, apply a lot of annotations to get a pleasant developer experience.

In every Laravel project I haven been involved in I have needed to read the Laravel framework source code with all its layers to get grip what is actually going on and how it is related to my specific problem. However this have been true for every framework project I have been involved in, Laravel or not.
I like the suggestion at the bottom of side bar, when I just tried Nukemap[0]:

> Fallout: Your choice of burst height is too high to produce significant local fallout. The minimum burst height to produce appreciable fallout for a yield of 100 megaton is 5.49 km.

Its really helpful. Guess, I should retry it with recommended value.

[0] https://twitter.com/app4soft/status/1491747174178336774
This is a naive article with no critical thought from the author. It feels like the author is just rephrasing quotes from people like Elon Musk (who claims to use first principles thinking).

Progress in real life are mostly made by trial and error, and then the underlying theory or first principles are solidified later (eg jet engines, cooking recipes, penicillin).

The cases where things start from theory to some final outcome are incredibly rare and mostly concentrate in the field of theoretical physics.

People who think otherwise are usually people who never had to get their hands dirty in the nitty gritty of science and research (or cooking for that matter).
actually I think using javascript to steer cars could be very productive in making them kill
The distinction between persistent and ephemeral state may be too coarse-grained. In many applications like preference systems and object persistence more fine-grained distinctions are needed. As a typical example, miscellaneous data like window positions, sizes, and settings can and should be reset under certain conditions in desktop applications, but they still need to be persistent. There is a need for systems of default values & conditions that regulate when resets from corrupted states are allowed and when resets are executed for certain types of data (but not for others).

I've never seen a framework or OS-support such fine-grained persistence and failure management. It's strange because almost every application needs something like this, and if it's just to reset a faulty preferences file. I've always thought that these kind of features should be provided by the OS, together with indexing and better guarantees for file integrity (e.g. ACID-compliant atomic file operations).