skysight-inc/HackerNews huggingface dataset:
"To characterize that scale as common is one of the most embarrassing failures of modern software engineering."

This point cannot be stressed enough. Almost all the worst software engineering failures I have seen have been caused by premature scaling - which is way worse than premature optimization because the latter's effects are usually local. But premature scaling causes architectural decisions that affects the whole project and simple cannot be undone.

One example among many are some of the influential engineers insisting on that we needed four application servers with fail-over because they had experienced servers crashing under heavy load. This complicated failover setup took huge amount of time and resources to setup, delaying the project by months. In the end it only attracted a few hundred visitors per day and was cancelled in under a year.
2-Nonenal newly found in human body odor tends to increase with aging (2001)
> very good results

with diminishing returns. Post-Apollo funding was/is but a shadow of NASA's glory days. As soon as the military interest is gone, it's inevitable that a program will lose financial support.
An argument for " is you don't have to escape ' inside string's. In an argument about single vs double quote you can bring up `Template strings` and everyone will hate you ;)
You have to dig deeper to make the right analysis here, your view is very 1st world-centric.

To the poor people living right now, they are already living with their life at stake to them it's not an actual argument. They need access to cheap reliable energy right now and frankly, don't care about climate change.

Talebs minority rule is not a universal rule it's a contextual rule which is important to understand.
I don't see an issue with Ulrich's behavior here. Calling somebody an idiot after being called "a terrorist" seems rather fair. Being a somebody, of course he is going to be the center of attention, not the dozens of nobodies annoying him into reacting like that.

Nobodies like you, who have no name, who have a disposable identity, who get to accuse people of misdemeanor online. You are not a decent person, that's for sure.
How would you enforce a ban on backyard breeders? I personally detest them as they flood the market with unhealthy dogs.
I wonder if Fuchsia will really become a consumer brand though. If I understood it right, the original motivation was a desire to get rid of the Linux/GNU heritage in Android.

If that is the case I could imagine that Fuchsia might not become a separate "product" for consumers at all - instead, Google could replace Android's implementation "under the hood" with it but still present it as just another Android version brand/UI wise.

If they managed to do the same with Chrome OS, the'd actually have archieved consolidation on a technical level without causing consumer confusion. (Well, more than there already is)
The best ever USB bootable app Rufus
I mean, they can. Breeders often focus on a specific breed (or breeds) of dog, and puppy mills will usually claim to do the same, even though many will crossbreed and not tell you. Shelter pups are likely to be more mutt-y than what you'd find at a mill or breeder, often with 5 or 6 different breeds of dog in it.
What hard- and software do I need to be able to stake? In non-technical words preferably :).
Bristol-Myers Squibb to buy Celgene in $74B deal
in my opinion several build systems / package managers have already solved this issue. The answer is that it doesn't matter mono repo vs polyrepo. Look at nixpkgs/nixos/nixpkgs if you are interested
I've done my fair share of Elixir. And this looks like you hit it right on the nail. Elixir is a great language, but I think Python is Python and Elixir is Elixir. We shouldn't me complicating any more than it already is (not that python is complicated, just adding another languages functionality another hurdle to learn).
The left regularly address each other as "comrade", albeit sometimes a little tongue-in-cheek. Solidarity is an important and necessary part of the culture, given the odds are heavily stacked against them.
Which as a user just taking a quick look at it I don't need or want, and the audience for this isn't going to have difficulties with the concept that they'd need to log in to get that.
> Let's be honest, there are no other language counterparts (Java as Javish?! or JS as JSish?!) for such adjective

I've seen it for other languages, including those two, and denying the term wont deny the concept.

I've seen perl, python, and javascript written like C, java written like perl, etc. Its always a bad idea - each language has strengths in the ability to express concepts to other devs, part in syntax and part in conventions, and swimming upstream against those never helps anyone. (Evolution is great, chaos is not)

None of which says that these terms CAN'T be used in an elitist way, but I dont see that as the primary purpose or use (at least in the circles I'm exposed to)
Oddly enough, you could s/mono/multi in your post and that would exactly align with my own experience. I'm not kidding: everything from engendering reliance on weird homegrown tooling, CI & build pipelines to the pain of trying to break out to a different approach, to enforced bad practices, to developers (unknowingly) misleading management, to colossal failures.

I've worked on teams with monorepos and teams with multiple repos, and so far my experience has been that monorepo development has been better — so much so that I feel (but do not believe) that advocating multiple repositories is professional malpractice.

Why don't I believe that? Because I know that the world is a big place, and that I've only worked at a few places out of the many that exist, and my experience only reflects my experience. So I don't really believe that multiple repositories are malpractice: my emotions no doubt mislead me here.

I suspect that what you & I have seen is not actually dependent on number of repositories, but rather due to some other factor, perhaps team leadership.
Not as black and white as that. There are multiple companies running validators and you can choose to run your own. The transactions go to the same shared blockchain. Most of the significant tokens on Stellar have their own preferred validators for transactions. Each validator can configure consensus for their ecosystem as well. IMHO this is a reasonable compromise and not that different from Ethereum proof of stake in combination with a high stakes.

Ethereum is a nice science project so far that may one day result in something usable and when that happens, I will look at it again. However, that is not right now and we are trying to run an actual business right now. Most of the smart contracts I've seen are convoluted and tend to solve things that Stellar can do out of the box with zero programming.

The smart thing seems to be to reuse smart contracts from Github and avoid writing your own and thus avoid taking the risk of introducing exploitable bugs right in the heart of your financial operation.

Not to say that they are useless, but I have no need for them with Stellar. That saved us a lot of time so far.
> And I don't imagine Visual Studio Solutions for C# are used like this.

At my workplace, we've just been cleaning up a whole bunch of instances of exactly that anti-pattern. Except that it's obviously not symlinks (which require specific user rights on Windows), but links to external files in VS.

Same problem, though: They're easy to introduce and a pain to deal with later on.
1. Communicating clearly in 'business language' is essential when the junior developer interfaces directly -- not through an intermediary -- with business people and stakeholders. This tends to happen in heavily siloed BigCos, especially in places where IT is just a business unit among many, much more so than in SV or startups. But it's also a skill that one rarely has an opportunity to use in isolation, away from the pressures of estimation, project management, of implicit requirements-gathering by listening to business units segue to different business problem, and sometimes of fudging and obfuscation and make-believe falsehoods to soften the impact of reality. These are complex dynamics usually played at the senior team lead level. Most team leads know this, and don't subject junior engineers to this game with no help.

2. These sorts of high-level expectations tend to get peddled around a lot, not the least bit because it's both noncontroversial advice and a desirable baseline, but they aren't even always necessary. Often, the systems one will work on already exist, they already don't conform to an idealized model because of a series of fixes and mistakes made under pressure. These points are a stand-in for saying you should design and code in a way that future maintainers can make sense of what was written. Sometimes that's using patterns and strategies that are well known, instead of a contrived variation. Sometimes that's staying true to the existing design of the product and the codebase, because tacked-on parts in a different style will increase complexity of the whole.

3. Interfacing in the design and mechanical sense, and achieving that design consensus using interpersonal relations are really two separate skills, and once again it's reasonable to expect that consensus to be set not solely by junior staff between different business units. After all, interfaces and system boundaries ought to have business significance -- not only because of the implications of Conway's law, but also because interfaces and their outputs are often the only orgwide-visible products of the business unit. They must stand up to, or meet the challenge of future pressures such as planned re-use and enhancements, some of which will conflict with the intentions behind the original design.
Not a neurophysiologist. Can you point me to any controlled studies verifying this microtubule quantum effects? If not, a principle based description of the theory and hypothesized effects would be helpful too. Microtubule physiology characterization would also be good. Completely not up to date on neurophysiology so pretty much any references would help. Thanks in advance!

Edit: Nevermind on microtubule resources. Plenty on the physiology references for those.
Re-align things with Flexbox
> And Coconut code runs the same on any Python version, making the Python 2/3 split a thing of the past.

My understand was that the big issue was the fact that [third party] libraries assume that strings were made of 8bits characters.

How does coconut solve that issue?

Seems a little misleading....

if you import enough things from `six` or `__future__` then you code will run the same on both python 2/3.

some things like fancy tuple expansion aren't available if you work with that subset, but yeah, most things are OK.
http://www.cnsa.gov.cn/english/n6465652/n6465653/c6805049/co...
Correct, but the average person doesn't care. They might have read about it and gone "neat", but they have already forgotten about it.
I think the ICBM utility has been played out. The new concern seems to be defense of space in and of itself. Exhibit A: Fearless Leader pushing through the Space Force creation. New field, new theater of war, new way to line defense contractor's pockets.
A lot of the pain you describe boils down to insufficient tooling and bad code organisation.

Outside of mega-corps, usually only a few people (couple of teams at best) are working on a given section of code at a time. Coordinating changes between maybe 12-15 people is quite feasible. Most of the time it's enough to keep code nicely segregated by paths - something like $team/$XXX or $scope/$team/$YYY should work.

On top of that, you need two things to enable a nice workflow:

* server-side (or otherwise programmatic) merges/rebases only; no human should ever need to push to master directly. That's the job of the [pre-]CI machinery.

* comprehensive pre-merge testing before the server-side merge. Do all your development in branches, and have bot+CI test _all_ unmerged branches against MASTER+YOURBRANCH on every push to YOURBRANCH. Because no human is involved when merging to master, the tip of the master has not moved due to external factors. Also, rerun tests if master has indeed moved thanks to bot having merged another branch ahead of yours. Fix any test breakages in the branch.

To make the second item work, you have to realise that the testing steps need to be rapid enough. Usually it should be enough to test the new-to-be-branch against merge problems, code convention errors and have a run through all the usual unit tests. Most of the time you can leave any larger cross-service or integration/end-to-end tests for code that has landed in master already.[ß]

Once code has landed in master, CI can pick it up and produce the release artifacts. The tooling needs to be good enough to know how to avoid useless work (doing useless checkouts and running tests against dozens of branches will get expensive). It also needs to provide very good and easily actionable feedback. You want clear test results, with quick jumps to failure(s) and robust logging.

To give some context of where the above is coming from... We have a monorepo with more than 130 projects, and about 7% of the codebase changes in any given month. (Except for December. Understandably.) We also clock more than 40k pre-merge test runs a month. Once a merge request has been approved, it is often available for shipping in 20 minutes.

When builds against master never fail due to code conflicts, development velocity is maintained better even with multiple teams working on the same piece of code.

ß: this is a tradeoff between development friction and test coverage. A sufficiently thorough integration test can take anything from a just a few minutes to couple of hours. You want to run them against batches of changes, and in case of introduced failures, incentivise teams to put in new unit tests to cover as much of the uncovered error scope as possible.
I was exactly like that at 19, sans genius. I spent way too much time on the "fun" parts of my work and not terribly much at actually getting work done. I'd also push-back on managers pretty hard. As a result, my first two jobs involved me coding alone on projects of negligible importance.
> more inhumane for Alzheimer's victims themselves

I think you are making the assumption that the unhappy and trapped spouse is going to provide loving care. The Alzheimer patient may be better off with other family or in state care than being dependent on somebody who may be hostile to them.
> If you create high priced housing that no one (including students paying off massive ampunts of debt, where the min payment + rent = a mortgage payment) can afford, your high-priced housing will stay empty.

if too many developers do this, that high-priced housing will have to become low-priced housing if they actually want to clear the market.
> Some customers do not have the option to adopt, particularly if they are looking for a certain type of dog, she said. “That is why we believe they should be given a choice.”

Which they still have by going directly to a breeder instead of relying on a middleman (which is exactly what people who actually care about breed purity and all that jazz actually do).

I think the new law is a bit draconian, but weak counterarguments like this one ain't gonna get it overturned.
> Growth requires work and that requires energy

No it doesn't. "Energy intensity...is calculated as units of energy per unit of GDP" [1]. It fell nearly 1/3 from 1990 to 2015 [2].

Growth is a measure on value. Value is subjective. It is not intrinsically linked to material or energy use. (For example, modern computers use far less energy and material than older computers while delivering far more value. More extremely, consider many purely-digital goods.)

[1] https://en.wikipedia.org/wiki/Energy_intensity

[2] https://www.eia.gov/todayinenergy/detail.php?id=27032
> I don’t know if the tooling has much to do with it, but I suspect it might.

As a development team grows, time to market also grows, in a superlinear fashion. This is known since people shared code on dead-tree pages, so the odds of tooling being the cause are low.
Gratz.
At least on two occasions i have seen configuration as literal code (like in config as java, scala, python code). While config as code could be beneficial, using it as literal code is not optimal.
How different is PoS and PoW in practice (for ASIC eligible blockchains)?

I need to devote X units of currency to get Y hashrate to gain 51%. This is a stake, needed to achieve a certain level of PoW.

One difference is PoS requires stake only from internal currency (you must buy/mine a stake in that currency), vs ASIC PoW you can use a foreign currency to buy your 'stake'. This might mean PoS is less volatile, or resistant to external attacks.
Happy Birthday Bitcoin
The case for anonymity online (2010)
I fear this is just going to create a Cobra Effect

https://en.wikipedia.org/wiki/Cobra_effect
Those are two very different breeds. They have been bred into caricatures of a sort, incapable of doing their original intended job. They can't even breed on their own as they need c-sections to deliver pups.
The American bulldog is a better example of a dog that is still capable of it's original purpose.
There's still a lot of nature vs. nurture to that. A lot more experience = a lot more failures.
Rebuild and deploy everything, what's the actual problem? Like the OP said, that's a scale issue and most projects don't have it.

Also building/testing is far more effective at finding dependencies than just going by repo structure. There are numerous package managers available to solve versioning if you need separate components.
This is common almost everywhere in the world as the 0 and 1 prefix (the plus in the +XXX landcodes) are usually used for international selection but might require an additional 0 or 1 after the first 0. Though in my country and most of Europe the 1 is not a international prefix.
> after it's been solved

I think a quick perusal of this page will show that it's not really "solved" after all. A far higher percentage of developers continue to be affected by large-repo issues than a Python-specific issue (currently #1 story on the front page) or anything to do with Ethereum (currently #7). Are those "horseshit" topics too?
I was really surprised to see an article on HN about China that wasn't full of ignorant hate and racism in both the article and in the comments, but then down and the very bottom is your sole lonely comment. Stay true, freedom fighter.
Here is a language diff that shows when new language features added to Firefox. This might be helpful to get an exhaustive list of the changes:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_...

In practice the only thing you absolutely need to know is the spread syntax for arrays `blist=[...alist]` and objects `objb={...obja}` that will trick you up if you're never seen in before

alist = [1,2,3]
blist = [...alist, 4] // == [ 1, 2, 3, 4 ]

obj = { a: 5, b: 6 }
obj2 = { ...obj, c:7 } // == { a: 5, b: 6, c: 7 }

See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

There is also this weird shortcut for creating objects for which key and value use the same identifier:

d=8
e=9
obj = { d, e } // shorthand for {d:d, e:e}
// == { d: 8, e: 9 }
Texas has enough sun and wind to quit coal, Rice researchers say
SEEKING WORK | REMOTE / Eastern US (GMT -5)

https://kims.al

Experience: 20+ years

Tech/skills
-----------
* server - php (laravel/symfony/zend/wordpress/whatever), groovy/grails
* client - primarily vue, some knockout, some react
* mobile - ionic/nativescript/cordova
* db - mysql/postgresql
* other - twilio, aws/azure, grafana other fun stuff

Background
----------
Have been working with web for around 23 years, started with PHP in 1996(!) - have worked with Perl (2 years), .NET (1 year) and Java/Groovy (7 years) over the years as well.

Enjoy taking an idea and moving from concept to deployment and iterative improvements. Able to work solo, on a team or leading a team (and I have a small team I can bring in to a project if/when need arises).

Happy to talk more via michael@kimsal.com or mgkimsal on skype
This already happend before with Brillo.

It was going to be Android native userspace plus a subset of the Android frameworks redone in C++.

Then suddenly, due to customer feedback as the main official reason, it got rebooted as Android Things, supporting even writing userspace drivers in Java.

Then ChromeOS got to add Android support.

I guess it is kind of clear which group is winning the internal political wars.
If they support desktop correctly (including accessibility, Left to right languages etc) I honestly believe this technology could be a game changer for cross platform development.
The Smell of Age: Perception and Discrimination of Body Odors of Different Ages
I understand where you are coming from. But I don't think that webdev is easier just because it is. Embedded is not the rocket science some people claim it to be.

I believe there is a lot of room where we can improve and lower the barrier for entry.
For example better packaging system, better IDE support (CLion is already very good tbf), modernizing vendor api, improve documentation and testing solutions, compiler that actually throw meaningful errors and of course good learning material...

I know it is a lot to ask and I don't want to sound like a ungrateful child. There are a lot of people working their asses off for free and all that. But i think it is not wrong to point some of the problems we have.
> to reach the center in Houston, orbiting astronauts have to dial 9 for an outside line, followed by 011 for an international line

> His comms slip-up set off a security alert at the Houston center, he explained, with emergency staff to check the room where the space station’s line connected to Earth.

Dialing 9 and "outside lines" implies there's some sort of PBX system, which makes sense. What I don't get though, is if the outside lines are in Houston, why do you have to dial the international access code 011 to call Houston? I thought maybe there was a country code allocated to the ISS, but according to a Reddit thread, they just use Houston numbers [1]. I think the first bit from the article is just a mistake (eg he wasn't calling a Houston number, just through Houston).

Aside, it's amazing how many (new) PBXs still use the "dial 9" requirement. If you dial a 10 digit number (in North America), it's obviously destined for an outside line. If you avoid assigning extensions that conflict with area codes, you can even use early dialing (where the call is placed as soon as a number pattern is recognized), but that's optional as the system will just wait a few seconds to see if you're dialing more digits or not. Already anyone with an extension that starts with the local area code probably already gets lots of misdialed calls since people forget to dial 9 all the time.

[1] https://www.reddit.com/r/todayilearned/comments/56yxnd/til_t...
> why use time solving a problem you don't need to solve?

Unless they're running on the same computer and deploy literally simultaneously, this is already a problem you need to solve.
Doing Data the Right Way – The Ethics of Data Science
I would argue most cities outside of a handful of the largest metropolises. I would argue that outside of the LA, San Francisco, New York, Seattle, DC, Boston, and maybe one or two more cities, affordable housing is well within the 10 minute radius posed by the above commenter is pretty common.

Obviously that list of cities makes up a large group of Americans, but it still isn't really representative of the country as a whole.

That said, at least in my field, the vast majority of jobs are in those cities, and so it becomes problematic when from an employment perspective, it is difficult to avoid those areas, while from a livability perspective, it is financially difficult to get by (at least, without the torturous commutes).
Do you have to write the Padé approximant by hand or has this already been sorted out in a popular library?