skysight-inc/HackerNews huggingface dataset:
Most the time the only thing devs are allowed to interact with on the business side is a product/feature proposal with all assumptions already made.

If devs do not know the customers/users nor interact with them then they can't really argue about the proposal's assumptions, it defacto becomes a demand.

With experience devs see such proposals with skepticism. A significant amount of our output ends up being useless, no matter how fast or well it was built.

If you want devs to focus on value creation you have to make it their job, they have to take ownership of the whole thing. When a dev can help a user or a customer they tend to feel fantastic about it.

But truth is business people think devs are inept at doing that so most companies are structured in a way where the only agency devs have is how much time they have to do something.
It could be a me problem because lately I'm stretched too thin but it seems to end up being a crutch too often when programming in unfamiliar languages and then I don't have the time to go on and understand what's going on before I move to the next step. This has obvious compounding issues.
Context switching will happen regardless of where your thread implementation lives. Reimplementing scheduling in a bespoke fashion in usermode will not give you the gains that you hope for.

Basically, learn how an OS works first before trying to reimplement it badly.
Thanks for indulging me. I know I am yelling at the clouds.

I also know people usually misunderstand me because I am a “programmer” and all I see is “code”. I guess that’s fair enough, but I fully understand legal being of a completely different nature from Rust.

What I also understand is that no matter how long everyone argues about it, the only thing that matters about legal is the text. The font, the styling, etc is all secondary. It might be important, but it’ll never be primary. Unless courts start judging differently based on page margins I guess.

The same goes for science. Publishing “attention is all you need” in an 8bit NES font might not be fashionable, but it does not and cannot detract from the discovery within it. LaTex produces the exact same documents (I know it is configurable but we are going for a certain style) and that’s what this is about. Not how the tools work but that we fundamentally even care about it instead of focusing on the primary issues like correctness, openness, accessibility. I’d like academic papers to be APIs actually.

Again I see the importance of styling and appearance in general. It’s just that we start with that and I think that’s problematic and actively harms our progress.

Also, to conclude, I am nitwit. This is just my take.

Edit: A man can dream, right? If a paper was plaintext I could typeset it last minute in 8bit NES fonts if I’d be so inclined. I hate ya’ll deciding how everything looks and works. I know that’s technically challenging, but to me that’s where the progress is. An academic paper like, say, a jupyter notebook would be awesome, not? Would you give up your fancy type setting? I would!
Some reductions via Conway's method give non-trivial Collatz problems even though other simple techniques show the halting question for those machines to be trivial; the Conway reduction sometimes reduces trivial Turing machines to non-trivial Collatz problems.
I don't know what jabber.ru's policy is, it's running a very old version of ejabberd. But you would be hard-pressed to find an XMPP server that would allow authentication without TLS. Starttls makes no difference.
> The viewing experience on YouTube is so much better if your Internet is not uber fast.

The viewing experience, if you don't include the chat experience, is better regardless of your connection's speed. YouTube seems to have access to better distribution (you'd think Twitch being an Amazon company they'd be more or less on par), the software works better, the ad policy works better.
Should people here really just accept any nations blatantly stealing and "infiltrating"?
Why does zero new tools (X) add time?

Alternatively, why does one new tool add so little time?
Superlensing without a superlens: microscopes boosted beyond limits
New technique could be used in medical imaging and advanced manufacturing
Physicists at the University of Sydney have shown a new pathway to achieve superlensing with minimal losses, breaking through the diffraction limit by a factor of nearly four times. Their trick? Remove the superlens altogether
> What kind of latency did that approach manage to achieve?

Generally 10-20s depending on the size of the video segments. For streams we controlled entirely, we could even go as low as 5s (at the expense of short video segments).

> From your description elsewhere was it using the WebRTC data channels to deliver DASH/HLS style segments or actually using the MediaStream stuff?

The former, but we'd split the segments in much smaller chunks for delivery purpose.

> I think the magic info we're missing here is what the Twitch viewers are watching on, and my hunch is it's a lot of mobile for which the P2P idea will not work (and/or provoke angry messages from mobile operators).

Yeah mobile is more complex than desktop because you must not incur spendings on the viewer side and because battery use is paramount. But you can still get good result by setting the mobile users as leaf node (receiver-only).

> In the case of smart TV then I can see the P2P idea saving a lot of money

Yeah, smart-TV and set top boxes were a very important segment for us. But as you said it's probably not Twitch's market.
Performant Terminals with Encrypted Buffers – This Week in Gnome
There is no process that can prevent unknown failure modes.

Legacy software is almost always going to have issues, and some use complex frameworks knowing full well they have heavy maintenance burdens.

Saboteurs come from all skill levels and backgrounds. Integrating accountability in the development and deployment process is wise.

Most modern "Hackers" are just the sane old cons repurposing common auditing tools to check for known CVEs. Most others simply don't care about some obscure website.

When you catch unknown people poking hardware in COLO data centers... the real problems start to become apparent.

With enough coffee and doughnuts anything is possible. =)
Using Eggshells as Electrodes for Batteries
Then you’re just empirically wrong. I’ve never had managers who didn’t want me to have professional communication skills in the ten years I’ve been in our industry.
No, the CEO needs to know how to clone the repo, read and write E2E test code (basically usage examples), and run the “make test” or whatever to check their (the managers’) E2E tests are running and which properties pass or fail. Otherwise, the “non technical” manager is unwilling (not incapable…just too lazy) to understand the definition of “done” so they’ll be clueless about if the thing is working or not, they’ll be forced to play telephone to add a simple test expectation and then they need to have a meeting to beg someone else to write a function. That’s a leech, not a leader!
> I can not see anyway which anything is becoming better by this immature and ridiculous regulation.

Have you read the link I provided? What exactly do you see as immature or ridiculous?

> What it certainly does is put burdens on small companies, independent developers and open source projects.

Of course it doesn't. That's why the major AI industries are so up in arms about it: because they have to document and describe their foundational models, and make sure their data is sound: something that they definitely don't want to do.

Independent devs and open source will be fine: they already (mostly) do that.

It's GDPR all over again: the industry fights it tooth and nail because they couldn't be arsed to play nice. This time the FUD has been launched preemptively in hopes to stifle this.
And nobody here knows how to raise a cow, milk it, and slaughter it. Neither can anyone make a fire in the rain, and god help us if the internet stops working. We’re so far from basic humaning that every generation needs to relearn how to change a baby.

Bleak stuff indeed.
You'd get into latency and consistency issues. It seems a poor choice if your main design constraint is real-time or near real-time interactive content delivery.
> For them, spending a decade working with a low level programming language before you jump into high level programming language is simply not an option

As a counterpoint, I'd say that it's also chance to build on top of these abstractions without having your brain cluttered with how they're implemented. That's also how science grows.

And don't underestimate the new players. They're perfectly capable to understand the low level details if they have to, and they have much more resource available to learn too.
audio hardware
Thanks! That one frequently trips me up. If I think about it for a moment I know "his affect" is different than "the effect something has", but, as is sadly and normally the case, I power thru writing w/o thinking as much as I should.
That echoes the book Waltzing With Bears, if I'm remembering it right.
You could spend 15 years cutting every corner imaginable as a self-professed genius 1-man engineering team until everything becomes unsustainable, feature work is impossible due to frequent fires, the business is faltering, and you can't even understand your own code any longer. Then, quit as soon as a new hire comes in so you can't be held accountable for your quagmire by other engineers. I don't really understand why someone would do this, but I recently got to see it first hand. ;)
Nuclei v3
It's not that LN owns the venues, but that the venues have an exclusive ticket agreement with TM. So if you want to perform at this venue, you must sell via TM. When my startup was trying to compete, we found that basically every single outdoor amphitheater had exclusive ticket rights. This makes stuff like crowdfunding a concert impossible
How a subscription-based Windows 12 upgrade would change the platform
Now seriously, my comment is a call for people to acquire professional communication skills, because they are extremely useful when negotiating work in far too many areas to count. Such advice getting down voted indicates how little value quality communications has within the software developer community - to the industry's demise. Communications are everything, and if you don't have good communication skills you get overlooked, abused, and misunderstood... leading to career frustration, stagnation, and burnout.
Very cool! Have you already taken the time to cross-examine the output to ensure it's hallucination-free?
Okta asks for a HAR file of your okta session. By default this includes okta session tokens. The attacker who compromised oktas support systems (again) then used this session token to access customer's okta accounts as the first step in trying to gain access to the customer's systems.
As a developer I hate "precise" and "complete" requirements. Usually these extremely detailed roadmaps are just fairy tales. They indicate a management and product mindset that thinks you can pre-chew a developer's food for them and make things more predictable.

In fact, what you are doing is tying the developer's hands and making it less possible for them to nimbly work around unforeseen obstacles or repurpose existing solutions without raising a "process exception" to reopen the spec or sizing of a work item.

Be clear about the goals but let the developer(s) who have their hands in the code make the decisions about how to implement it. That means you can't really roadmap a big project down to the minute, but those roadmaps were always lies so there is literally nothing lost except for some fantasy Gantt charts.
I've always taken comments like this to explain why [whoever you are] are so obsessed by 'dont tred on me' freedom -- they have so little of it where its actually experienced: at the daily, local, level
> the money isn't printed. It's debt, which is different. The debt is expected to be repaid, with interest

One person's debt is another person's money. Our economic system is built on an expectation of contistent growth, deflation is not an option and those in charge will do everything they can to avoid it.

When the government creates new money it's technically debt, but debt they will never get back and clear off the books. Doing so would reduce the money supply and either cause deflation or reduce GDP, neither are acceptable for the system. They tried quantitative tightening policies to remove some of the debt/money created after the housing crisis, even a small amount of QT hit hard and they very quickly abandoned the idea of allowing those debts to be paid back (or ought back and removed).
Gets value ? Or extracts value?
I have met such managers you talk about but from my personal experience they are not a majority. Maybe I have been lucky or you have been unlucky.
> OP made a claim that being a bigger country means less corruption and less misinformation without giving any evidence.

As opposed to your evidence for your claim, because you feel yours is intuitively correct?

How about providing evidence (!) for your own thing first? :)

Meanwhile, there are tonnes of examples of smaller nations that have been corrupted. Look at Africa for several examples, Sri Lanka in the news about a year ago, Myanmar (ongoing), etc. :(
Have written software for a pig tracking company for the past few years. I'm always surprised at the amalgamation of low and high tech. On the one hand, some pigs can detect leaks in the line and map the pipe's dimensions. On the other hand, the industry often takes speed measurements via listening for a pig to pass a weld joint (which you can hear from far away) with a stopwatch.

The pig does often get stuck, so much so that there's a "Pig Stopped" button which influences ETAs. Every blue moon a pig really gets stuck for days or breaks in the pipe. Techs might have to use estimated locations and dig in someone's back yard.

Years into our contract, my girl friend was reporting on something farming related and said "hey can I pick your brain on raising pigs, I know you've been working with those farmers". Different type of pig tracking
Standards are up for technical/video quality which is amazing. Quality of content - sorry we must be watching totally different things. While there are obvious gems from either time period the ratio of good to bad is decreasing (this is of course my personal judgement which is as good as yours)
The problem is not only the level of abstractions but the cross dependencies and assumptions across abstractions. For example, in higher level frameworks (e.g. React) you should firmly follow the rules in a way that makes assembler a toy language comparing to the stuff you need to know ahead.

The security issues expand beyond what is described in the article: you assume the security is solved by a stack of layers where is not. A single issue impacts everything doesn't matter where in the stack it is.
I don't think this argument really works, because you can also classically simulate superposed states as long as they are stabilizer states, or fermionic gaussian states, or log-space states or whatever else. Similarly you can also classically simulate states with arbitrarily large amounts of stabilzer magic if they happen to be fermionic gaussian states or whatever.

I think you can sort-make the argument you want to make, because all computational basis states are also product states, just like all computational basis states are also stabilizer states and also (if they have the right parity) fermionic gaussian states. Where it goes wrong is when you start thinking about gates/circuits instead of states, because (e.g.) CX or CCC..CX gates with arbitrary numbers of controls are (in general) highly entangling gates, but they map computational basis states to other computational basis states.

Does this make sense?
Any county's legislation is huge and most people don't pay attention to it, news at 11.

News don't pay attention to major pieces of legislation unless it can be farmed for clickbait and outrage, news at 11:05.

Give any country (including the one you live in), and I can bet you I can find a major legislation you are not aware of, and news aren't talking about. Why is EU singled out again?
Wow, the frame is very nice and sleek, also the graphics are nice, I only don't like the guy dressed icon, yeah it's nice but I would have used the space to display some more useful informations like pressure, humidity, change of rain, etcc... by the way very nice work!
I'd like to point out that this has a disclaimer[0] by SSB in the Norwegian version (but not the english one) translated here:
"A Discussion Paper is a preliminary version of a research work that the authors want discussion around and input on, before possibly revising and trying to get a final version published in a scientific journal. Discussion papers are commented on by other researchers at Statistics Norway before publication, but both conclusions and choice of method are the author's own responsibility."

And here are two reviews/rebutalls by the Norwegian University of Science and Technology, Industrial Ecology Programme:

https://blog.indecol.no/climate-sceptic-talking-point-publis...

https://blog.indecol.no/dagsvik-silent-on-the-sensitivity-of...

[0] https://www.ssb.no/natur-og-miljo/forurensning-og-klima/arti...
> Whenever this estimation question comes up, developers rarely put themselves in the shoes of the business side

A big issue is that "business side", including UX, mostly have zero scrutiny of what they spent their time on or when important work will be completed. Whereas engineers get scrutinized about tasks by non-engineers who can't and won't understand.

And frankly, many times this hand-wringing about estimates is because product and UX took way too long to "plan" the work to begin with. So there's some natural resentment from engineers about this.
Government spending both increases the government's debt and causes inflation. Maybe that's the link they are looking for.

Plus, I don't know much about monetary policy, but wouldn't the Fed feel obliged to start quantitative easing if the government's debt put it in difficulty?
Is it any different in your opinion when $1T is created and deposited into bank accounts rather than minted and released as coins?
Noah smith's thoughtful and enthusiastic techno-optimism
So how my compiler reasons about multiple threads?
Back when I was an IT leader running all our internal appdev, I had a "pet" business system that my team used exclusively to write, optimize and rewrite as a testbed and learning environment for new frameworks. It was probably not the most efficient way for me to run the org, but I honestly believe it saved lots of longer term headaches by containing a few potentially terrible decisions to the scope of a single, not-mission-critical app.
Sorry, neither me nor my friends are into fast food business and it is not something I would read about in my free time.
Have you played around with what region you're downloading from? You can change it manually and it may be worth checking out whether or not Sydney/Melbourne offer better download speeds than Brisbane.
This comment makes no sense to me.

How is Clojure a layer of abstraction that had to be removed and replaced with Java? What do you think that Clojure was abstracting exactly?

Same question for Typescript. In fact, Typescript is a layer on top of Javascript so I could say that you actually added one more here.
If you're doing Scrum, then you might have noticed that the Scrum Guide considers the contents of a sprint to be a "commitment" on the part of the team. That "commitment" is usually built by taking the number of story points delivered last sprint, and bin-packing the same number of story points from the backlog into the next sprint.

If you don't think toxic managers and scrum masters are going to use that "commitment" to death-march the team if it looks like the sprint goal is going to be missed then you have a far more optimistic view of humanity than I do.
> but what has been done recently?

Specifically about Ticketmaster or what has FTC done more broadly?

Proposed a rule against hidden fees (10 days ago). It's also supposed to give FTC enforcement mechanism so that it'd be more effective than state laws that were passed and basically ignored.

Also filed an antitrust lawsuit against Amazon (less than a month ago) for how they're treating third-party sellers. And if I remember correctly a lawsuit against Facebook is supposed to proceed in December, in which the FTC is asking the court to force Facebook to sell Instagram and WhatsApp (I wouldn't get my hopes up on this one).

FTC definitely has some teeth now, but they can't wish monopolies out of existence, they have to go through a years-long court process against an army of lawyers employed by tech companies with a budget that's orders of magnitude higher than FTC's.
Show HN: GPT Gifts – Because humans suck at gifts
Everyone understands that why the business needs to an estimate and that shorter is better than longer. There is no ambiguity there at all. The complaint is the phrasing like the developer can know when it'll be finished. Someone's ability to deliver value quickly is unrelated to their ability to estimate how long it will take. They can get their estimate completely wrong and deliver huge value. And we all know if there was some way of estimating how long software tasks would take, software companies would hire a professional estimators for the same reason that software companies often develop product teams to negotiate what features a product should support. There is no point asking devs to do it. Oh course, no-one else can either and the devs will at least get the lower bound right so people bother them but the process is transparently stupid.

To know how long something will take it is necessary to list all the steps taken to do the thing. That just isn't possible in software development. Developers can come up with a lower bound for a given set of requirements. And I think everyone agrees that they could do an accurate estimate assuming nothing unexpected happens. Then, in 95-98% of projects, the estimate turns out to be under-calling how long a project will take. The "developer estimates" becomes a measure of how much fat the developer feels like putting in the system this project.

Asking for estimates completely misframes the conversation. The question is what problems does the business have now, what problems are likely to develop in 6 months, and some input from the developer on the cost-benefit of trying to solve those problems. Then people make some qualitative decisions with an eye on minimising risk. The best outcome after giving software estimates is that everyone ignores and forgets them - anything else destroys business value.
I mean, I use it for my family finances (two of us) and it works well.

Most of the limitations I run into relate to the types of goals you can set.
Definitely not the land of the free, that's for sure.

Zoning and the use of police powers generally seem to have almost no limits.
I guess the idea is that an async/await context switch would always be cheaper than an OS thread context switch.

Whether that is actually true probably depends a lot on the specific operating system and async/await runtime (I think there's a lot of mysticism involved seeing async/await as some sort of silver bullet instead of relying on cold hard performance numbers alone).
You manager wants you to agree to the work they ask you to perform, and they want to load you up with work to maximize your efficiency. How one negotiates when you're reaching capacity is professional communications. If one is unable to attain work/life balance that is due to a lack of communication skills, the lack of the ability to explain you're past ordinary capacity, burning your health. Our industry is over run with members over working - that's due to their inability to communicate the are over capacity.