skysight-inc/HackerNews huggingface dataset:
If it's really abstractable it shouldn't be difficult to refactor. It should literally be a substitution. If it's not, then you have varied cases that you'd have to go back and tinker with the abstraction to support.

It's a similar design and planning principle to building sidewalks. You have buildings but you don't know exactly the best paths between everything and how to correctly path things out. You can come up with your own design but people will end up ignoring them if they don't fit their needs. Ultimately, you put some obvious direct connection side walks and then wait to see the paths people take. You've now established where you need connections and how they need to be formed.

I do a lot of prototyping work and if I had to sit down and think out a clean abstraction everytime I wanted to get for a functional prototype, I'd never have a functional prototype--plus I'd waste a lot of cognitive capacity on an abstraction instead of solving the problem my code is addressing. It's best, from my experience, to save that time and write messy code but tuck in budget to refactor later (the key is you have to actually refactor later not just say you will).

Once you've built your prototype, iterated on it several times had people break designs forcing hacked out solutions, and now have something you don't touch often, you usually know what most the product/service needs to look like. You then abstract that out and get 80-90% of what you need if there's real demand.

The expanded features beyond that can be costly if they require significant redesign but at that point, you hopefully have a stable enough product it can warrant continued investment to refactor. If it doesn't, you saved yourself a lot of time and energy worrying trying to create a good abstract design that tends to fail multiple times at early stages. There's a balance point of knowing when to build technical debt, when to pay it off, and when to nullify it.

Again, the critical trick is you have to actually pay off the tech debt if that time comes. The product investor can't look bright eyed and linearly extrapolate progress so far thinking they saved a boatload of capital, they have to understand shortcuts were taken and the rationale was to fix them if serious money came along or chuck them in the bin if not.
How come you presented this before the other identical post, and yet your post is virtually ignored, whilst the other, half a day later, is noticed? Time of day vs USA West Coast time? Fascinating.
That's cool! Was your experience typical for the region?
Absolutely stunning - I've often wondered myself about why the terminal doesn't behave like this already, it just makes sense.

My only worry would be this is obviously so great it's only a matter of time before Apple/Microsoft see the light and build something similar into their OS - however hopefully this happens via acquisition rather than what happened to Flux, Watson and Duet.
You don't need to scale to zero and can set minimum idle instances on Cloud Run:

https://cloud.google.com/run/docs/configuring/min-instances
That's not what WET means. The GP is saying you shouldn't isolate logic in a function until you've cut-and-pasted the logic in at least two places and plan to do so in a third.
Isn't Quora the anti-stackoverflow? Broad questions, vague answers, too many beginner questions, you name it.

P.S Some images are not loading and the UI is hard to navigate rn. However, I'm assuming that'll be fixed in future iterations.

Something that could help is :

- Forget the question images in the feed. Show them only when the user clicks on that question.

- Make the search bar smaller.

- Add some sort of social proof

- Most of all, remember that a good UI makes or breaks a platform so it IS a main functionality.

Hope you understand what I'm saying. Good luck!
NjRAT v0.7d by Njq8
What do you say to convince someone? It’s tricky to review a large carefully abstracted PR that introduces a bunch of new logic and config with something like: “just copy paste lol”
> In ML languages, you can generally only call functions that were defined previously.

Hum... At least not in Haskell.

Starting with the mostly dependent code makes a large difference in readability. It's much better to open your file and see what are the overall functions. The alternative is browsing to find it, even when it's on the bottom. Since you read functions from the top to the bottom, locating the bottom of the function isn't much of a help to read it.

1 - The dependency order does not imply on any ordering in abstraction. Both can change in opposite directions just as well as on the same.
The parent's comment holds when reformatting, especially in languages with suspect formatting practices like golang, where visibility rules are dictated by the case of the first letter (wat?) or how it attempts to align groups of constants or struct fields depending on the length of the longest field name. Ends up in completely unnecessary changes that divert away from the main diff.
I second the recommendation of Steven W. Smith's dspguide.com, which will get you from (I think) zero to a profound understanding of DSP. I've also learned a lot from Julius O. Smith's Physical Audio Signal Processing, which I see a couple of other people have also recommended: https://ccrma.stanford.edu/~jos/pasp/

But if you're using an existing computer music programming environment like Csound (used in The Audio Programming Book), SuperCollider, or PureData, you can make a mini-synth which takes input from the computer keyboard without any of that stuff! (Stay away from Max/MSP; it's proprietary.)

The most fun I've had with audio programming has been bytebeat, though: http://canonical.org/~kragen/bytebeat. I didn't invent bytebeat but I did write that page about it.

Also, there are a lot of the hassles involved in audio latency on CTSS-derived OSes like MacOS, Linux (especially Android), or Microsoft Windows; it's easy to end up with 100+ ms of latency, and hard to do better than 10 ms, and either of those is a super shitty musician experience. If you do your stuff on an Arduino or similar microcontroller instead, those problems evaporate, and your computer music system will fit into an effects pedal. You need a DAC and, if you're taking audio input, an ADC; the built-in PWM and ADC in a standard AVR may not be sufficient. (And, beware, a 31.25 kHz PWM carrier can go right through a stereo system and burn out your venue's tweeters if it's turned up high enough. Filtering is required.)
Vaccines have gotten so political it’s disgusting. China should be applauded for the role in making vaccines. Not held up to BS political lines about which vaccine is best
> I think the point is that following that book does not really lead to Clean Code.

And that is why I started saying "You can disagree over what exactly is clean code". Different projects have different requirements. Working on some casual website is not the same as working on a pacemaker firmware.
SOLID code is a very misleading name for a technique that seems to shred the code into confetti.

I personally don't feel all that productive spending like half my time just navigating the code rather than actually reading it, but maybe it's just me.
> The study was centered around a Twitter field experiment in which a research team offered polite corrections, complete with links to solid evidence, in replies to flagrantly false tweets about politics.

yeah i don’t really trust or believe these “researchers”. case and point from “fact checkers”:

https://twitter.com/GlennKesslerWP/status/125626793122004992...

https://twitter.com/GlennKesslerWP/status/139716616659076711...

and snopes in particular is very biased. i remember when they labeled a claim by aoc as “factually untrue but morally correct”
Sign in with your work e-mail?
I need this for Linux!
Yeah I'm not saying Netflix never has good stuff, just that it's few and far between in comparison to the others I mentioned.
Yep. Old English word for spear was "gar". One vegetable was related to the leek, but they described the clove as spear-shaped: the gar-leek. https://www.etymonline.com/word/garlic
> it's another to essentially say code is spaghetti garbage because it doesn't precisely align to a very specific dogma

Does it say that though?
> Fuchsia is based on capabilities, ie. handles to access resources, and those include memory regions. So a driver will only be able to access the parts of memory that you delegate to it.

Ah thanks - Fuchsia drivers having capabilities to specific memory regions mostly answers my concerns at that level I think.

Well, I guess I'll continue to be both interested in it from a technical perspective and conflicted about it based on licensing.
It does bring me a sense of despair. Living in Europe, earning six-figures just barely and it's a stretch, significantly higher taxes, significantly higher prices (VAT!!), significantly more red tape. Trying to bootstrap a company, how can one even compete in the global market with people for whom $50k is pocket change?
I'd always assumed that decoding x86 and x64 had a lot in common so not much to be saved there? Happy to be told otherwise.

Agreed that Arm (esp AArch64) must be a lot simpler.
Yoshua Bengio Team’s Recurrent Independent Mechanisms
Gecko ending embedding is almost certainly a major reason why everything built with a browser engine is either a Chromium wrapper (not true embedding, but no browser chrome) and WebKit (true embedded).

It’s a real shame. Gecko is a nice engine but XUL is a much harder sell.
Clearly it is still a hardcoded value! It fails the requirement. Instead there should be a factory that loads a file that reads in the "a" to the variable, nested down under 6 layers of abstraction spread across a dozen files.
I have to wonder - why not put screens on drains?
Sometimes you really just do need a 500 line function.
Bomb one of their airbases. Russia can annex Crimea with no real response, so why should the EU show restraint? (I am not suggesting a bombing campaign, just a targeted strike on the airbase from which the intercepting fighter jet departed.) What’s Russia going to do? They want that Nord Stream pipeline. They aren’t going to militarily respond over some two bit dictator, even one friendly to Russia. The Nord Stream energy revenue is probably going to be much higher than the entire Belorussian economy.
The sales process consists of you transferring ownership to an address the buyer provides you after they pay you; it's not programmatic. The fastest/simplest way to sell is probably to list your star on opensea.io, though there's also a marketplace group on urbit.
This is something we definitely should add as a fallback when a Fig completion spec doesn't exist!

The reason we created our own standard is because traditional shell autocomplete doesn't always provide metadata, like descriptions, priority or icons. Also it is a little tricky to write by hand, unless you're pretty familiar with shell scripting.
You originally said "The phrase 'well regulated' means 'well supplied', as in lots of guns and ammo", but your quote says it means "the imposition of proper discipline and training".

It doesn't seem like they agree with you?

I'd be much more comfortable with gun ownership requiring "proper discipline and training".
I wonder if it will last longer than Stadia did.
In C# and .NET specifically, we find ourselves having a plethora of services when they are "human-readable" and short.

A service has 3 "helper" services it calls, which may, in turn have helper services, or worse, depend on a shared repo project.

The only solution I have found is to move these helpers into their own project, and mark the helpers as internal. This achieves 2 things:

1. The "sub-services" are not confused as stand-alone and only the "main/parent" service can be called.
2. The "module" can now be deployed independently if micro-services ever become a necessity.

I would like feedback on this approach. I do honestly thing files over 100 lines long are unreadable trash, and we have achieved a lot be re-using modular services.

We are 1.5 years into a project and our code re-use is sky-rocketing, which allows us to keep errors low.

Of course, a lot of dependencies also make testing difficult, but allow easier mocks if there are no globals.
Spaghetti code is bad, but lasagna code is just as bad IMO.
Why is this considered a paradox? There is no contradiction, and it seems quite natural that people living in rural areas would be happier. In the timescale of evolution cities are very new and we did not evolve to live in urban environments.
AI Powered Misinformation and Manipulation at Scale #GPT-3
People on the left don't realize that the "fact checkers" are an extension of the propaganda arm of the left.

For anyone who disagrees, take a look at the "fact-checker" Twitter profiles here and tell me with a straight face they aren't literal mouth puppets of the extreme left and/or the communist party: https://www.truthorfiction.com/our-team/
Thanks for the response. I know what the article said, but I also tend to assume that accessibility will be overlooked or treated as not very important.

I'm tempted to buy a first-generation Nest Hub, maybe off eBay, to find out for myself.
Non-aggression and property rights are the only laws that truly matter. Natural rights stem from these principals.

> women's suffrage

If a government doesn't have a monopoly of force, nobody needs to vote or even acknowledge the government.

> banning of the international slave trade

Your body is your possession. Slavery violates that and the non-aggression principle.

> the right to bear arms

Who grants this right? The government doesn't have the right to take any property. It does so via aggression and violates natural rights.
> Despite your opinion, viruses do not penetrate walls.

Despite your research, public transport vehicles don't tend to have walls.
I understand what you're referring to, but was aiming to explain the difference between the US and France in a more approachable way. The US could block a protest from occurring, but the legal basis would be much tougher than that in France (it's more protected in the US).

In the US, a court won't simply forbid a protest ahead of time because the issue was protested several years ago in the same neighborhood and it led to a riot.
Yea... that could probably turn ugly in a lot of cases. I think the flow of object creation and dependency injection would be the important part to handle well in a case with a lot of dependencies. I think the dependencies should be passed down through objects in one direction. So if your object (a) that works on objects (b) that have a lot of dependencies, that first outer object (a) is responsible for injecting dependencies into those 2nd objects (b). So if you have a mocked dependency, you pass that when initializing object a, and object a is responsible for injecting that mocked dependency into object b.

A disclaimer, I'm an sre, so definitely not the most expert proponent of oop.
I don’t really know if it’s a significant finding. My point was that you asked “how you measure a 1 percent decline in news source quality?” and suggested that your personal confusion about such a thing throws the entire paper into question. Instead of having such strong judgments, why not just read the paper?

I am personally not sure how astronomers measure gravitational redshift with such apparent accuracy. But my ignorance does not mean astronomers are a bunch of frauds. It means I haven’t done the required reading.
The EU knows it can’t risk a major energy supply (as evidenced by Gazprom running roughshod over Vestager).
Ask HN: How Does HN Work?
I am always surprised to see some stories in the frontpage with less than 10 votes, as of this moment we even have stories with 3 votes in there. At the same time I've seen some stories go unnoticed with 9 votes in the "new" section.

My assumption is that some users have enough karma to post directly to the front page, but I wonder how many votes does a story need to get promoted. Is the algorithm documented anywhere or is it secret? Is there more to this than just karma?
Overall, I think GDPR is a positive force that protects consumers. It does have one major downside though, and that's that it treats entities of all sizes in the same way.

Placing the same regulatory burdens on start-ups as on big tech is a drag on innovation, and it's frustrating that there is no minimal cap on users before GDPR comes into effect, given how the EU has constant exception for artisanal food and goods manufacturers.

Lawyers and third parties want to get a piece of the pie, so they'll present themselves as indispensable. It's almost as if this is the EU version of TurboTax.
Saw this just the other day. I was at a loss to know what to say. :(
The issue I have is that duplication is a coupling problem, but there’s no evidence in the coupled parts of the code that the coupling exists. It can be ok on a single-developer project or if confined to a single file, but my experience is that it’s a major contributor to unreliability, especially when all the original authors of the code have left.
Los Angeles has slightly higher sales tax[1] than king county (Seattle) Washington[2]

Yet Washington is "regressive" since it doesn't have income tax. Los Angeles would actually be more "regressive" by this metric.

This is why i think its a psyop. Somebody wants the lower and middle classes to fight.

1: https://www.cdtfa.ca.gov/taxes-and-fees/rates.aspx

2: https://kingcounty.gov/independent/forecasting/King%20County...
All codebases are spaghetti garbage, but some are useful.
WET is great until JSON token parsing breaks and a junior dev fixes it in one place and then I am fixing the same exact problem somewhere else and moving it into a shared file. If it's the exact same functionality, move it into a service/helper.
It depends what layer you're considering and what properties you want. At the base layer, the core idea is that the community opts into the protocol and ideally has some say into future protocol changes.

In terms of network consensus, democracy indeed isn't universal in terms of network users, since in PoW the huge mining pools have disproportionate votes, and in PoS the huge staking pools and whales have disproportionate votes. However, the "voting" in this case is just "which blockchain is the valid one". Unless a group of powerful entities collude to 51% attack the network, this doesn't actually confer any direct influence over anything. (Though for PoW, miners do have some influence over what transaction fees people will have to pay.)

In terms of systems built on top of the core network - especially if smart contracts are supported - you can create lots of interesting democratic governance systems. You can basically make whatever you want.

So, is network consensus democratic? Not really. Then it's kind of a question of if it's more or less democratic than, say, money in the United States.

One could make an argument it's way more democratic, since two single organizations control money issuance: the central bank and the treasury. (One partial counter-argument is that the Federal Reserve is - as the name implies - federated regionally through 12 sub-organizations. One could potentially say that it still effectively operates as one entity, though.)

Or that it's way less democratic, since at least everyone in the country can vote for the president, and the president appoints the central bank governors and the treasury secretary.

>Skimming that long comment, I still don't see any evidence for your claim.

The claim:

>My understanding is that most cryptocurrencies intend to be extremely democratic. More democratic than all previously existing currencies, even. (Whether those ideas are feasible or those goals are being achieved is another matter.)

My only claim is that they intend to be democratic. At least Bitcoin did. I don't think that's too hard to support; Satoshi initially intended for everyone to be able to mine. I think he had a pretty democratic vision.

The implied emphasis in that paragraph was on "Whether those ideas are feasible or those goals are being achieved is another matter."
I do cherry picks in magit by:

1. Check out target branch

2. l o (log other) source branch

3. Highlight commits from list you want to cherry pick.

4. A A to apply the pick (I typically throw a -x flag into there too)
> when it's clearly insinuated that the CPU performance on the next-gen ARM cores will not be much of an uplift compared to current gen

Perhaps going to smaller technology nodes will make them faster, still? Or is that already part of the prediction?
Can go both ways. The non-loyal flyers may never book with you again if they don’t get what they want.

A lot of the FFers don’t have much freedom in their booking, and are in too deep in the FF program to switch preferred airlines now.
This is what I'm doing even while creating new code. There's a few instances for example where the "execution" is down to a single argument - one of "activate", "reactivate" and "deactivate". But I've made them into three distinct, separate code paths so that I can work error and feedback messages into everything without adding complexity via arguments.

I mean yes it's more verbose, BUT it's also super clear and obvious what things do, and they do not leak the underlying implementation.
Deepmind Google Independence Negotiations
The thread started where a person used stats to prove his point and someone else pointed out that the stats are prove the reverse... so conclusion in US laws of statistics do not apply.

As a constructive thing, I suggest we figure out why the gun crime stats from 2 different states or from same state but different time are wrong or partially wrong.
I did actually found the SetupTeardownIncluder class author complains about really easier to read and interpret then the original version. I know from the start what the intention was and where I should go if I have issue with some part of the code.

I dont even take issue with name. It makes it easy to find the class just by remembering what it should do. I dont really care all that much about verbs vs nouns. I want to be able to find the right place by having rough idea about what it should do. I want to get hint about class functionality from its name too.
repeat after me:

Document.

Your.

Shit.

everything else can do one. Just fucking write documentation as if you're the poor bastard trying to maintain this code with no context or time.
I think it's the first to allow it with TM.
Protocol-Based Social Networking, Today
I think one should always be careful not to throw out the baby with the bathwater[0].

Do I force myself to follow every single crazy rule in Clean Code? Heck no. Some of them I don't agree with. But do I find myself to be a better coder because of what I learned from Bob Martin? Heck yes. Most of the points he makes are insightful and I apply them daily in my job.

Being a professional means learning from many sources and knowing that there's something to learn from each of them- and some things to ignore from each of them. It means trying the things the book recommends, and judging the results yourself.

So I'm going to keep recommending Clean Code to new developers, in the hopes that they can learn the good bits, and learn to ignore the bad bits. Because so far, I haven't found a book with more good bits (from my perspective) and fewer bad bits (from my perspective).

[0]https://en.wikipedia.org/wiki/Don%27t_throw_the_baby_out_wit...
Please don't use divisive terms like "they" as it turns things into an "us vs them" scenario rather than focusing on the issue itself.
When I switched to emacs, I thought org-mode and repl integration would be the killer features. I was wrong- Magit is best emacs feature by far.

It’s great that parts of the magit experience have been separated into packages. Perhaps now mercurial, perforce etc can get clients similar to magit in quality.