skysight-inc/HackerNews huggingface dataset:
Experts and laypeople (and the press) will go on and on and on about national deficits, but what exactly is it that they are afraid of?

It seems to me that the past decades have convincingly demonstrated that countries really can keep running up debts basically forever, and nothing particularly problematic ever actually happens, except in a few cases where the economy overall is in an extremely bad shape for a variety of unrelated reasons.

Can someone with more knowledge enlighten me what all the fuss is about?
China does not want the yuan to “win.”

The Chinese state views control over capital flows as more important than the prestige of reserve currency. They can, and have, clamped down significantly on foreign outflows when they deem it necessary.
This is not all about payment. It is also about the power-asymmetry.

Corporations expect their employees to be devoted and loyal — at the same time they treat them as expendable and replaceable human resources. That means empirically being loyal to your company will give you nothing in return. There are many such asymmetries, e.g. in the way time is treated or how much slack is given when there are "special circumstances": Be late as the employee and it will get you in trouble, be late as the corporation and everybody is expected to swallow it. Have a special circumstance that would need the employers consideration and you can go fuck yourselfas an employee — but if the corporation is in special circumstances everybody is expected to go the extra mile with it.

Even if the salary was better, this is the opposite of a healthy, respectful relationship. If you treat your employees with respect, don't expect them to act like they respect you.
In comparison, flask is more like express for the javascript ecosystem. You can cover simple scenarios with bottle, its usage is straightforward
1 think my point makes more sense when you consider that I 1. Don't work with production code (more analysis, ad hoc code in an investigatory capacity) and 2. that when 1 mention someone is "new" what 1 mean is someone actively learning and not from a technical background. 1ME, folk like that have a difficult time with that floating 1. So while yes it's a standard that programmers are familiar with, it's not something that someone new will be very comfortable with. Lots of people 1 work with come from a pandas-only background.

Not really conceding because as far as 1 can see, everybody is coming from a position of familiarity.
I think it has its moments but I think they buried the more interesting and (oo scary maybe even thought-provoking) concepts of the book so far down that they're barely there. The plot is very new trek and it's impossible to say if it's beyond redemption because anything is possible, there are no stakes, and why do I care again? New Star Wars made similar mistakes.

Also I had high hopes for Salvor because they were a badass in the first part of the first book. Instead now they are a scowling child who defaults to violence. The writers really screwed up the characters.
One mitigation of the “mastering computers takes 30 years” thesis is that many of the abstractions and technologies that we spent those decades learning are now obsolete, and newly minted grads are blessed with learning materials and environments that make catching up easier than ever.
> nothing particularly problematic ever actually happens, except in a few cases where the economy overall is in an extremely bad shape for a variety of unrelated reasons.

Quite sure you answered your own question here. Survivorship bias isn't a valid argument. Lebanon, Greece, Pakistan, Turkey all come to mind in the last decade, all with unsustainable amounts of debt.

The modern monetary system is a faith based system which hands leeway to governments to create and destroy supply at will. When people lose faith it all collapses very quickly, the failure modes are never slow. The relatively small Silicon Valley Bank is a great example of this and the systemic collapse in confidence of banking.
>but this is the issue addressed with planning poker.

It isn't. Having a team which is both intimately familiar enough with the set of features as a whole, and understands how to use the system to get around the inevitable 'A does it in X while B does it in X*3', are both prerequisites. Suffice to say, with the amount of discussion based around Scrum being done wrong alone, neither of those are even remotely a given. This also doesn't take into account turnover and new features being able to remove a team from meeting those prerequisites at any point.

Too often it just devolves into people raising eyebrows at one another and either it becomes 'X will do it, so X's estimate becomes the value' (why even bother doing poker then) or 'take the average or minimum' which screws over anyone who estimated higher.
Never denied that money and debt are the same. I am denying that printed money is the same as debt money.
And for mechanical power just use the pressure differential?
I'm not allergic to SQL Server. I didn't study the example code; I was just curious about why DISTINCT was a problem. TL;DR: for some query planners, DISTINCT requires a table sort, which requires a full table scan, which can be avoided by using a construct (GROUP BY) that gives the planner hints.

But I assumed that was dependent on the query planner; Oracle SQL, as I recall, has/had specific constructs for giving hints to the query planner.
This is literally free knowledge spread across many MOOCS, YouTube videos and Unix man pages. You can tinker with it with a Raspberry Pi.

Finding time to learn if this is not your day job is another problem, but a solvable one if you're willing to learn.
Who pastes something and executes it without a second look?
I don't think people use Python because it's fast. It gained momentum because it has good libraries for data science and ML. Other languages, including JS, are far faster at this point.

However, the reason to use JS in particular is because when you have a lot of I/O blocking calls (DB calls, web requests) it really is a lot faster. But if you do anything with numbers, JS is the wrong language - it's so limited here that it's almost laughable. Same with dates. That makes it a very bad choice for data science.
Great article. Reminds me of a boss I had early in my career, who would get a bit nervous if you asked any questions about the details of what we were actually doing. I later found out it was because he just copied the procedures used at his previous employer. “We do it this way because we have always done it this way” kind of deal. I wondered why any suggestions of doing things differently fell of deaf ears. Thankfully my next boss was excellent technically and was happy to change our procedures if it would make life easier.
I worked with it quite a bit on my last job, and for me it's really the quality that is not there yet. One example is prefabs: They worked just fine in Lumberyard years ago. The first few releases of O3DE broke them (that was in 2021 I believe), because like almost every other subsystem, Amazon wanted to rewrite it from scratch. Seems like they released the new version in the latest release, but as you can see in this video from Gamesfromscratch, it still doesn't work: https://www.youtube.com/watch?v=5PAuR-pEz1w

Also, they are not great at marketing. For example, in the latest release notes, the main headline talking point is robotics, and not games.

I think the tech is actually good, I prefer both the component system and ScriptCanvas over Unreals component mess and Blueprints. It just needs much more polish. And a big game company trying to actually make a game.
>Today programmers and system administrators no longer exist, instead we have DevOps and even DevSecOps, in which the industry is trying very hard to stuff every single task into the job description of a single individual.

Nice to know I'm not imagining this. Platform Engineers seem to be going extinct, with the Software Engineer taking over the role, and doing it badly.
Still waiting for the Bigger Luke cut.

https://www.theguardian.com/culture/2021/oct/27/the-bigger-l...
Wordpress is an excellent example of vulnerable monoculture though.

And that's not 'on prem' but usually colocated hosting.
I didn't realize that one-thread-per-socket was still something people considered; especially given that many programming languages nowadays have excellent support for async/await which does a great job at managing multiple concurrent connections within a single process/thread and doesn't have the overhead of context-switching.
Personally, I find pithy comebacks like this to sound convincing to but to actually be mostly devoid of utility. They tend operate as a sort of social persuasion tool, but I'd like to Get Things Done, which requires deep domain knowledge.

One thing I've been noticing with my current clients is the vast amount of churn generated by them only having a patchwork understanding of their overall architecture. Some grok the low-level infra, some the deployment levels, others the backend pieces, and others the frontend stuff. However, since there is no story collecting the pieces into a cohesive whole, we see them treadmilling through different tech stacks in an attempt to gain "velocity". They're definitely running fast; it's just they're not getting anywhere very quickly.

It's a pattern I see a lot. On the flipside, when clients have devs who mostly grok the entirety of their system, then we can focus on the questions that really matter: purpose, market fit, empirical evidence from users, _etc._

Questioning things costs time right now, not questioning costs 10 times that in the future.
> Cloudflare exists out of necessity for the most part.

I agree with this, there don't seem to be that much self-hosted software that someone could (easily) setup for the use cases that Cloudflare serves.

> The alternatives to shield from large scale DDoS are all US American too.

Not only that, but the WAF functionality is also pretty useful. To be honest, the same applies to something like wanting to have CAPTCHAs on your own site - not that many options out there.

As far as I can tell as a hobbyist, if you wanted to host everything yourself:

- dealing with load: at best you can probably just run multiple nodes with round robin DNS and something like HAProxy, or even just live with Nginx/Apache/Caddy, though all of those would crumble under attack; probably with some resource limits in place so the software getting overloaded just crashes it (with automatic restarts) and doesn't grind the entire server down to a halt
- WAF: you could get a basic WAF running with something like Apache2 and mod_security, or if you can compile it for Nginx and get it working (a bit annoying to do, also apparently slower than Apache2 version), or something like Coraza (still new), but even then you need sets of rules, OWASP has some, but they're not updated as often as whatever Cloudflare uses, so the effectiveness of it all is debatable; there's also something like fail2ban, but some people really don't like it for some reason
- there's also additional stuff you can use, like LibreCaptcha for CAPTCHAs, something like Keycloak or Authentik for SSO and managing your users on prem (especially with mod_auth_openidc), stuff like Matomo Analytics instead of GA, Uptime Kuma for uptime monitoring, even your own self-hosted mail servers if you feel brave; but all of those take effort and need maintenance

And even then, certain things are not an option - you won't be shrugging off huge DDoS attacks and you probably won't be running your own CDN (easily), unless you have bunches of money to spend and the know-how. So of course people would rely on external orgs for whatever they can.
IANAME (...Mechanical Engineer), but I'll bet "generally no". A pig is propelled by the pressure difference across it, in the pipeline. Having two pigs in the line means they're splitting the available pressure drop - and the line is only rated for so much pressure.

(Yes, in "no other way" situations you might deploy a far more complex, battery- or remotely-powered "snake pig". That'd be really cool & interesting...but also a much more expensive and unpredictable scenario. And pipelines are a big thing because they're cheap and reliable.
Crude estimate based on some self evident truths:

Logarithms for number of people and communication chain come from network theory because network size and network distances slow down information flow.

New technologies bring in unexpected delays and problems that rapidly accumulate in nonlinear ways. If bring in 20 people to work with new programming language, new library stack, etc. everything slows down to crawl.
I wouldn't say I'm someone with knowledge (non-US, non-economist etc). But I understand the interest payments on a large national debt can be a problem. Not sure if that's a significant factor here.

I only just recently learned that national debt is sourced from bonds, purchased by individuals and companies as a safer place than cash, so take what I say with a pinch or two of salt.
"the dollar being reserve is not really "forced" upon other countries - it's a choice they made to use USD as their reserve"

Try selling your oil in anything but usd and see what happens.
It's not a choice if the consequences of making the 'wrong' choice is being invaded, bombed into the stone age and have your country pillaged and its assets handed off to reserve currency alligned corporations.
The stability you describe is relatively recent, the country has catapulted itself to development through deficit spending, and today still has a debt-to-GDP of ~66%. This isn't bad but still is a big subsidy partially financed by poorer countries. Germany, in particular, has been extensively accused by less developed EU partners of unfairly benefitting from the single currency.
Are Wikipedia's "actual" policies the things that Wikipedia says it does, or the things that Wikipedia actually does?
The Apache 2 license is incompatible with GPL2, you cannot have code under those two licenses in the same project. So they dual licenses it under MIT, which is compatible with GPL2.

The Rust project has the same problem, it's also dual-licensed under Apache2 + MIT.

You want Apache 2 because of the explicit patent grant, but at the same time you also want to allow GPL2 projects to use your code.
I assume when they mean that odyssey is going to be fine, they mean that because it's decentralized it can stay on forever?

I've personally always liked Peertube more, coincidentally the creator also got Kauffman as their surname.
I am very, very sensitive to the "cultural fit" in my organization. It has nothing to do with you being gay, straight, black, white, woman, man or other typical trigger words.

It has a lot with you behaving in a way that will be acceptable/enjoyable to the team.

This does not mean that you have to be like them! I have all kind of personalities in several teams and they differ vastly. The thing that binds them is that they like to spend their time at the office together (and for some of them - outside the office too).

Of course this is not measurable and some people are just a "chemical fit", and some others are not. This does not mean that there is something wrong with you (or them, or us) - we are just different in the way we want to be together.
That doesn't really respond to cushpush, who is proposing that resold tickets shouldn't be honored by the venue.
How often does a front-end developer need to know about /proc/pid/mem?

I think it's important to keep things in perspective here - when I took my first programming job the first week was setup. On my team, our onboarding has you branch, review and merge on your first day. Those abstractions allow for people to focus on the areas they're working on, and iterate there. A game developer doesn't need to understand the complexities around js type conversions, any more than a js developer needs to understands rendering thread latency in a browser.

On every team I've ever worked on, that headspace from the team would have been much better served by understanding the product and project, IMO.
Do you know about some way to check whether what I install from Extension Store is exactly the same as on Github?
That was more or less obvious since a while; electricity is solved, time to move on to other kinds of energy.
We need at least 500wh/kg batteries to solve trucking and short-range aviation and at least 1000wh/kg to solve shipping and mid-range aviation (long-range will probably always have to rely on liquid fuels or hydrogen). Where is the progress on them?
thats kind of unfair, when you select something and you are confident what is selected, pasting with middle button and hitting enter can be milliseconds apart

you already decided to hit enter while you are selection something, could be just a bit above your current cursor in the terminal
Sovereign defaults are very rare events outside of banana republics. It's not survivorship bias so much as it simply doesn't normally happen, despite the vast majority of advanced economies having been neck-deep in debt for a long, long time.
It's complicated. It's in their state supreme court because the appeals court decided unreasonable search and seizure laws are excluded from a civil case (as opposed to a criminal one).
When I was in college, I tried to spend my time listening, not speaking.
You can get ahead very far with a 16h free course on kernel development

https://training.linuxfoundation.org/training/a-beginners-gu...

A motivated person can run through it in a couple weeks while working a day job.
How would you mitigate a password reuse?
No but bittorrent scales as the number of user increases.

P2P may be explored again.
> If you actually printed money, which does not have interest to be repaid, then the amount of circulating money would've increased permanently. Therefore, the expectation is that each printed dollar is worth less.

I understand this logic, and I am trying to square it with the following:

When there is instability investors flee to the dollar (like during covid), and the demand for it increases (dollar goes up), also from other countries increasing reserves. So If when the dollar goes up the US prints more dollars, are they really getting into debt? It seems like a different case form other countries.
> Hospitals don't check software quality when making purchasing decisions (much beyond "this button doesn't work")

This! The worst piece of low quality garbage I've seen from the inside is hospital software. Nobody really cares or understands software on the hospital side, so anything goes. The product is inherently complex, so there are only a small number of large companies who don't care either since they can rely on customer lock-in, no matter how crappy their service is.
> Practically every chip company these days is fabless. Intel is the exception, not the rule.

A lot of analog and mixed-signal companies aren't: TI, NXP, ADI (with LT, ON Semi, Maxim, ...), Avago/Broadcom, AMS, Bosch, Infineon, Elmos etc.; also "the Japanese" (Sony, Fujitsu, Oki, Canon, Rohm and probably more)
Fully agree, and it's probably intentional. It's not entirely fair, but I suppose most countries would do the same given the chance. Clearly it's not how you want to get ahead as a country, since all it takes is for the world collectively to decide it no longer wants to bear that cost, and then you can only keep it through force. Inflation becoming a well-understood phenomenon with the general population also threatens it.

If China plays its cards right, the US is going to start having a bad time still this decade. The US should be aggressively trying to reach a more balanced economy. The distribution of not just wealth, but of the ability to generate wealth, leaves the US on very shaky ground.
One little-appreciated fact is that many of the most accomplished and knowledgable engineers were tinkerers from an early age. If you start your computing journey at the age of 18 with a compsci degree, you might already be a decade behind some of your peers.

It’s not too different from pro tennis players, who typically start playing before the age of 8.

For those at the top of the game, computing is a calling as much as a job. They will do substantial learning on their own initiative.
Printing more bitcoin is a tax on everyone and their electricity costs, their environment, and the existence of free tier compute.
The point is that the "unsafe" code is written and checked once, and then everyone can benefit from that. It's the same concept as encapsulation applied to memory/thread safety.
In my important dependencies, there are deep learning frameworks from billion-dollar companies, bindings for C++ libraries that are basically standard in the field, projects from CS labs with millions of users. I don't see any of them getting abandoned. But I guess I can't judge how much work removing the GIL could take. The big projects tend to be well-written and well-maintained, for what it's worth.

Which projects do you have in mind that have a significant user base, are still maintained, and would be too costly to port for someone to do the effort?
No, that privilege is reserved for the private banks. In the US the cunningly named FED. Presidents that actually tried changing that ended up killed.
> Management has to push for lower estimates because developers have an incentive to overestimate to make life easier.

Developers have to push for higher estimates because management has an incentive to underestimate to make life easier.

See what I did there? There's a fallacy in both statements: one side's actions are portrayed as greedy pursuit of "incentives" while the other side's actions are portrayed as a natural and logical counter to those incentives.
There are some things you need to know though. For example most devs today "know" Docker, but very few realize that it opens the exposed ports on the host firewall. Exposing a port for another service to access internally is intuitively safe, until you look at the box and realize that same port was opened to the internet. Convenient thought the docker devs, but touching something so important without feedback is reckless. That's an abstraction that absolutely shouldn't be there, too many devs don't RTFM.
You punish us for being ambitious and failing and give us nothing for being ambitious and succeeding.

As a developer, I endorse doing as little as possible as a result.
> It's an admission that they're not the big dog in streaming any more.

Might have something to do with their quirky UI and terrible search function.
I’ve seen decades old Fortran codebases that everyone is too scared to touch. So instead all the new ‘features’ marketed to clients are just window dressing around the existing Fortran core.
new to the team, I suppose. Everyone on the team has shipped a rails heroku PG app? Then you have a low number of shinies.

Shipping a Vaticle + Haskell on nixOS in your own server farm?

Maybe that's more new tools for the team...
Scalping is something that the artists and ticket sellers specifically enable. If there's a name on each ticket you can't resell it.