skysight-inc/HackerNews huggingface dataset:
Metrics-driven organization (aka KPIs or what the author calls Spreadsheet mentality) is what I do for a living: I’ve seen companies die by it, and companies succeed thanks to it. It’s meant to do one thing: clarify everyone’s role in a large, confusing, often political organization where success wouldn't otherwise be clear. If that’s not a large, systemic issue that even the best would-be cult leader among your CxOs can’t address, you need to have KPIs for things to be clear (on top of the best would-be cult leader among your CxOs to sell the idea, the hard choices in there and the vision unpinning it).

Imagine you work for the customers' support team: you unblock the client, the client is happy, and you also fix the public doc to unblock anyone after you… That’s all great. But at large organizations (namely: Google, Facebook, and LinkedIn) people ask: should we have a CS team at all? Isn’t that objective unscalable and trying to satisfy people a feature we shouldn’t have because every solution should be a product, not a process?

Unless you are working at companies where that question is legitimate, you don’t need KPIs formalized into a tree structure: you need objectives, clear goals, praises for unexpected great work, and support to make sure that people who are asked to do things can. The MECE tree is useful if you don’t want to miss something. For smaller structures, the gaps are a feature: you can’t do it all.
How to be a good web application developer
I guess Ohh1 is the same as Unruly. But 0hn0 is not the exact same as Range in the collection. Range includes the extra rules that the blockers cannot touch, and the remaining must be continuous.
It would be a significant amount of work. The MiSTer project is specifically targeted at the DE10-Nano so it's designed for that FPGA and that peripheral set. In particular MiSTer relies on the onboard arm to run support software, you'd need to replace that on this (perhaps with a RISC-V softcore you could build the MiSTer software for but lots of software work to do to make that work).

It may also simply not be possible. The DE10-Nano has DDR memory for example but most MiSTer cores need extra add-on SDRAM. The reason being the latency on the DDR is just too high for the accurate emulate most cores are aiming for. So SDRAM is required. On this board you don't have that option. Though perhaps you can build your own DDR controller, with the DE10-Nano you have to use the hard controller built into the FPGA. Perhaps another controller specifically optimised for the latency needs of MiSTer cores could work. Each core would need potentially significant porting work to use this new setup as they get direct access to the SDRAM pins in MiSTer. You'd need to trace back to where they're actually generating memory accesses and then plug that into whatever new DDR controller you had.
You don't really need DX10 and lower on Windows anymore either, dgVoodoo2[1] is routinely used (along DXVK) on Windows itself because of how better supported DX11/DX12 and Vulkan are by modern drivers.

I hope someone will benchmark a game with DX9+dgVoodoo2 vs native DX9.

[1]: http://dege.freeweb.hu/dgVoodoo2/
As a German person, this and so many other stories about customer - business relations gone awry or lost in miscommunication, I sometimes want to scream at the monitor, "why the hell wouldn't you get that in writing???"

The same goes for many work situations where the boss suddenly lowers the pay or fires someone for not filling in last minute for another employee calling in sick on a weekend. How is that possible? Don't you Americans value written contracts?

I am often annoyed by the amount of paperwork needed to make my life go smoothly, from work to private matters to whatever - but the times I was glad I could just point to a written and signed, extremely detailed contract which is the only thing that matters should things ever get in front of a judge, easily make up for the tedious writing and reading of contracts beforehand.
Nobody needs a gun to commit suicide. In countries where guns are less available, they use hanging or poison.

Putting that aside, it’s not our role to forcibly limit the choices of healthy, responsible people just because some unhealthy, unresponsible people might make the wrong choices when given the freedom to do so.

It’s not a societal-level tragedy if someone chooses to eliminate themselves. While it’s abhorrent to even consider, the fact is, there’s very likely a net economic/social gain.

We don’t need to be protected from our own choices. We need to be protected from the authoritarian impulses of people who don’t think we’re equipped to make choices in the first place.
Zero. I guess I'm an outliner.
I have honestly no idea what you're trying to convey. I didn't move any goalpost, I tried to restate my point since you missed it completely. Don't argue in bad faith, please.
Did you consider Purism Librem 14?
I absolutely don’t see anything in Go resembling C from a technical perspective, other than (before generics) being similarly unexpressive. It is much closer to JS than C in any way and shape.
It's a pet peeve and a common problem in software development, where developers don't want to do the work that is asked of them because it's not challenging enough (yay another REST API in front of a database), so they add complexity themselves - new, more difficult languages like Rust or Scala (not as much of an issue anymore I think), excessively complex architectures like microservices, DIY infrastructure configuration like k8s, etc.

See also magpie developers. It's not that the new technologies are not great, it's just that in most cases it's not what a client needs, but what the developers want to do. They will have a solution and look for a problem to match.

I mean I'm not innocent of that, I'm looking left and right for problems where I could use Go to solve them with because I enjoy it. But I am aware of the risks.

Anyway the comparison is apt because it happens with developers; I've seen it happen firsthand at multiple projects, and in almost ALL of those, after the consultants left, the company moved back to their own technology, picked something off-the-shelf, or did yet another rebuild.
Do Nothing- a message of motivation from Self-help Singh
Journals still play the role of quality filters/QA, which is very important. While your typical Internet-only journal is going to be like Alibaba, a top journal like Nature is more like Harrods - you're not going to waste money by browsing through trash there.
KSP (the original) use the Unity engine. When the original devs quit, the game got more and more buggy, to the point it was unplayable, kept crashing every other hour or so... I played without quicksaving for a more tense experience - and the crashes ruined that.
worked most recently with these guys:

https://www.fiverr.com/mamanok

https://www.fiverr.com/ddt_arnulfo
The problem as I see it is that projects often start without a vision, or even clear goals; even if there is a vision, it ends up getting lost and forgotten in a sea of feature requests.

Not only should we be asking if a project has achieved its original goals once it’s finished, we should be continually assessing progress against those goals throughout the life of the project - yet few projects I’ve worked on actually do this, even when I’ve explicitly requested it.
The problem is email is a plain text format end to end, so all those emails are just text files on disk. In various situations admins might end up seeing mail headers and contents even if they don’t want to just by investigating various issues. Acting on that content is a different question though.
Cuckoo is terrible from constant const point of view, linear probe is where is it at, indeed.

>"mov" is the biggest cycle-eater of them all.

The R part in 'RAM' is so wrong nowadays.
Nutrition and regular movement. Don't worry, you'll be fine, had a similar thing a few years ago, all gone. Be careful about surgeries, last time I checked the consensus seemed to be converging on that in this case they're largely placebos.
The killer feature of Zig is polish - not yet in implementation(teething issues still abound if one tries to take it into production) but definitely in design. It goes down the list of every language wart or make-do tooling situation in C and addresses it with a reasonably specified and generalized feature, without making the language much bigger(if it is at all - it's not a big language spec). It actively works on some really grody systems-level problems with building binaries that most languages will address with "compiles to C" and C itself addresses with "fight the build system" - Zig aims to be a one-stop shop that clarifies this process. And it integrates C code compilation into its build system, so existing projects can be migrated.
I think the comment was fair; Too often have I witnessed clueless and/or conniving salespeople recommend businesses to move onto Azure or other cloud services when there was very little to gain from it, yet it meant that the cost compared to hosting their very simple ERP software on metal would bankrupt them in the first bad month.
I have seen a company spin up and after 2 years spin out a seperate innovation unit, and when it was a proper seperate entity outsource their core IT to the unit... Which was then branded a big success! It was liberating to see such systemic incompetence; The people were all highly educated but as a group just can't seem to organize effectively.
https://www.foo.be/docs/tpj/issues/vol5_3/tpj0503-0013.html

A CSS (DVD encryption scheme) decryption program converted from C to English.

https://en.wikipedia.org/wiki/DeCSS#Legal_response
Any specific reason? Do you think it's a waste of time, do not feel like you have the time, or do you not know what to read?
Kind of similar for me but my cars tend to get hit now and again a lot whilst parked. One time almost written off because it was hit at high speed and the offender kept on going despite leaving several piece of his own car at the scene. The police couldn't do anything because, well, I was insured so 'they can deal with it'.
Hot take here but I think crypto should be as unregulated as possible. We already have plenty of highly regulated assets. People that want those qualities already have many things to choose from.

Having different options is what makes life fun. If you want safe, regulated, buy your bonds, etf and so on. If you want extremely risky investments where you have no one to blame but yourself, there's crypto.

The focus should be on informing people how risky these assets are and that there is a very good chance they will go to 0. If you are fully informed of the risks then you're free to gamble your money.
it is speculated that having many vaccinations actually increase your chance of a bad reaction to the virus (and other infections/diseases).
Now this was a good story. I wish more people would write about stuff like this... and then I realize that most people can't because of NDAs and such.

What I like about the story is that it makes my own experiences seem normal. At some point in life, we all run around trying to fix things we don't fully understand.
Ask HN: What tools do you use at work to keep your images up to date?
I'm tired of manually updating each screenshot in our documentation whenever there is a new UI change.

What do you use at work and what are the pros and cons?
I've had a situation where I needed to stream blocks of data from a remote computer in soft-realtime, but still needed to share the same data with many different consumers.

The code was simple, but effective (Go):

import "sync"

type Muxer[T any] struct {
ret T
mut sync.RWMutex
}

func (c *Muxer[T]) Multiplex(fn func() T) (ret T) {
if c.mut.TryLock() {
defer c.mut.Unlock()
ret = fn()
c.ret = ret
} else {
c.mut.RLock()
defer c.mut.RUnlock()
ret = c.ret
}
return ret
}

The way to use it is to write a non-concurrent nullary get() function, then pass it to the Multiplex() function in as many goroutines as needed:

get := func() DataType { ... }
muxer := Muxer[DataType]{}

// in other goroutines
value := muxer.Multiplex(get)

The value will be shared across all goroutines, so we get minimum latency with minimum copying.
"The point" was to find a large project to test import performance, and it sounds like they hit that point dead center.
Depending on how far off the deep-end you want to go, you can look into: peptides (BPC-157, TB-500), Human Growth Hormone and Platelet-Rich Plasma injections (PRP). There might be more stuff out there now, it's been a few years since I looked into it for a SLAP tear in my shoulder.

If you are in the USA, look into "anti aging" or "longevity" clinics. It's basically gymbro MD's that will prescribe you that stuff for money. Then at least you can be fairly certain that you know what you're injecting. Otherwise, you're at the mercy of the dodgy websites/alibaba for acquiring the stuff.

Obviously there is no definitive proof that the stuff works or if it's safe, otherwise it would be significantly more common. You can google, there are many small scale studies done on those compounds of varying degrees of quality. It all depends on your risk-tolerances etc. Ideally you'd be somewhere in the US near one of those clinics and could speak to a real doctor about your options, and not a random idiot from hackernews :D.
I understand. Good point. This indeed creates a bit of a problem. I might have not needed any work above Upwork level. However I still would avoid scenarios where agencies don’t have enough skin in the game, you said something along those lines in your article anyway.

Good Look with tinypilot.
I think that at the time, the agency upsold the author and they went along with it; after that, sunk cost became a factor. I do believe this is what most agencies will try, upselling I mean.

That said, clients can also be problematic; I recall one where the client paid a fixed amount per two-week sprint, but then really started to stretch out how much work was done within that sprint by basically not signing off on tasks and reporting new features to be added as bugs. It's another case I think of a party not being firm enough about scope.
Mostly accurate TL;DR; for tax payers

Your money is not going to research. Instead, it is going to bureaucracy and "extrinsic motivations" (researchers status games)
AIUI, Epictetus also discusses the matter quite directly and is under no illusion about his relative "downtrodden" status, so the contrary remark found in the textbook looks like naïve, groundless speculation. Slaves may have been personally "lively" and had complex stories - Epictetus certainly did - but this is a different matter altogether.
> most clients when starting out with a project can't really say exactly what they want, so the scope creep is not only driven by the agency, but also (sometimes mostly) by the client.

Most clients know exactly what their goal is ("To increase market recognition", "to increase conversion rate", etc). The scope creep can only happen in a requirements phase[1]. Once a client has signed off on exactly what will be delivered, and what the payments milestones are there's no wiggle room for the agency to continue experimenting.

If you're skipping the requirements phase because "agile"[1], then the work will be over budget, over time and under the scope.

There's very few projects that actually require the exploratory-driven process that agile uses. If you have one of those projects then farming the management of it out to an agency is exactly the wrong thing to do.

[1] There may be multiple requirements phases. For example a large "need to revamp our website" project can be split into multiple serial projects, each with their own requirements phase.

[2] I.e. We'll figure out what is acceptable to the client with constant feedback.
If the volume of data fits on a mobile phone for it to be offline, perhaps you don't need deep learning?
kB. 1000 bytes is 1 kB
Is "must be an agreement for future performance" a fair first test of whether something is a securities contract?

1) If there is no contractual agreement for future performance, it cannot be a securities contract (a "security").

That we can test before applying 2) the Howey Test, and then 3) assessing whether it's a Payment, Utility, Asset, or Hybrid coin/token

From https://en.wikipedia.org/wiki/SEC_v._W._J._Howey_Co. :

> "In other words, an investment contract for purposes of the Securities Act means a contract, transaction or scheme whereby a person invests his money in a common enterprise and is led to expect profits solely from the efforts of the promoter or a third party, it being immaterial whether the shares in the enterprise are evidenced by formal certificates or by nominal interests in the physical assets employed in the enterprise."[1]

> "The test is whether the scheme involves an investment of money in a common enterprise with profits to come solely from the efforts of others. If that test be satisfied, it is immaterial whether the enterprise is speculative or non-speculative or whether there is a sale of property with or without intrinsic value."[1]

Collectible coins, trading cards, beanie babies, real estate, and rare earth commodities, for example, are not securities per US securities law. Do these things fail a hypothetical and hopefully helpful "must be an agreement for future performance" litmus test for whether a thing is a security per US case law precedent?

What must be fed into the FTC CAT is a different set of policies.

From "Guidelines for enquiries regarding the regulatory framework for ICOs [pdf]" (2018) https://news.ycombinator.com/item?id=16406967 https://westurner.github.io/hnlog/#comment-16407277 :

> This is a helpful table indicating whether a Payment, Utility, Asset, or Hybrid coin/token: is a security, qualifies under Swiss AML payment law.

> The "Minimum information requirements for ICO enquiries" appendix seems like a good set of questions for evaluating ICOs. Are there other good questions to ask when considering whether to invest in a Payment, Utility, Asset, or Hybrid ICO?

> Are US regulations different from these clear and helpful regulatory guidelines for ICOs in Switzerland?
That's ok ;)
The term for the typical lay flat style of this type of photography is ‘knolling’ (could not find a decent source)
In practice Cuckoo sucks, b/c the reading from an unknown index in an array is not a const cost operation. It has an upper bound of course, but its average cost is quite different, depending if you are to hit L1, or L2... or just go for the a cache miss.

"Cache misses" is what dominates performance nowadays.
Sounds like if you want a version of this that doesn't leak memory you need a garbage collected language?
I had a similar experience with a trainer. Did squats, said my form was mostly good but wanted to test some things out. Did a quick ankle mobility check, saw that it was a problem. Slipped some 5lb weights under my heels, told me to squat again and it was an incredible difference. The balancing was so much easier and it felt much better when going lower. Really showed the value a trainer could bring. That was day 1.
I liked the article, and as an outsider to the discussion (I do embedded C for a living, and C++ as in "C with classes") I might add:

What I've seen so far is that Rust tries to lure C developers with a sort-of "memory-management shaming". I've even been called "old curmudgeon" here in HN for not showing interest in Rust, and not using it right now. I think if hear one more time that "70% of bugs are memory bugs; here is the link" I'm going to explode. For which I answer: "My applications have a button and a display, what exploits are you talking about?".

Spoiler alert: "memory-management shaming" doesn't stick with us. C is vast and has tens of millions of applications. Not every project is wired to Ethernet, BT or WiFi. If there is a bug, it might be hard to find, but that's it. Hey, there is people that even pays you to solve problems you've generated yourself. What's better than that?

Luring C developers is about something else and Rust doesn't get it yet. At the same time Rust tries also to lure millions of high-level languages developers with features like async-await, super clever one-liners, package management, etc., which personally as a C developer, I don't really care.

You can't make everybody happy. Make happy either C developers or JS developers. Pick one.

Another note: even if the language it's been there for a while, I often see "hey! I've built a build-essentials replacement! It only works like the 20% of it". You go to see the repo and it's been idling for the last 6 months.

So even the Rust's momentum is already starting to decay, there are really just a few of top "99% complete" reference projects. What does it means?

Zig on the other side, shows itself as a more humble language, with simpler syntax. I don't really like the syntax but it's not a big deal. Zig has, or at least, it users don't show bigger expectations. It's taking a careful and slow road and I like that very much.

That said I'm following both languages very closely. I only hope Zig doesn't become as bloated as C++ and Rust today, to be really in that sweet spot I'd like for embedded.
What exactly are you aiming to build? DP/HDMI output and Ethernet aren't exactly beginner topics in FPGA (though you may be able to cobble something together using pre-existing components).

The Nexsys Video would give you what you need: https://digilent.com/shop/nexys-video-artix-7-fpga-trainer-b... (though out of stock)

The DE10-Nano gives you both HDMI (though not 2.0) and Ethernet: https://www.terasic.com.tw/cgi-bin/page/archive.pl?Language=.... There's some availability, apparently buying direct from Terasic is the best option (though often more expensive as shipping is pricey and you pay import duties). It's also what the MiSTer project uses https://github.com/MiSTer-devel/Main_MiSTer/wiki so is what you need if you want to play with console emulation.

FPGA toolchains are indeed a nightmare but both Xilinx and Intel have freely available versions. They tend to be limited in the devices they support but the free versions of Vivado (Xilinx) and Quartus (Intel) both support the FPGAs in the boards I mentioned above.
Hate to be pedantic, but goods and services.
Isn't this slow because of pointer chasing in the trie?
The Hubble Palette
you may end up in Guantanamo
https://www.theguardian.com./world/2011/apr/25/guantanamo-fi...

:(
Keeping reading. The author explains the implications of this not being true.
Which is innately more fragile, a communication system you rely on for data that runs dozens to hundreds of miles through some communication medium that you don't control, to disks.

Or a disk (or five) in your own chassis.

It's not quite that simple, but still...
It doesn’t even work that poorly. DALLE2 came up with better designs for my mobile app than anything mid tier designers on upwork have.
Most of those historical benefits have been effectively precluded to anyone born in the '70s, the movement to close that gap has been steady over the last three decades of reforms and is supported by pretty much the entire political class. They even started cutting already-granted pensions, with retroactive moves that are on the border of legality. What I'm saying is that this particular element has already been normalized, and we'll seeit reflected in stats in less than a decade (when the '70s generations will be stopped from retiring in their mid-50s like their parents did).
I don't need to control for race or income. The point made was that the traffic fatalities in the US is only 0.012% of the population. My point was simply that while it's not a huge percentage in absolute terms, it could be lower.

While I'm not entirely convinced our more restrictive traffic laws aren't part of the equation, I'll agree that socioeconomic factors are probably important.

Thankfully, both countries have a vision for zero traffic fatalities by 2050. Lets hope they make it.
It also made lack of 64bit version a very thorny problem for a long time