skysight-inc/HackerNews huggingface dataset:
Can we just have a chuckle about a humorous event for once, without someone introducing fear?
tldr: Boring Hit piece...
Bill Gates family office supported vaccination efforts that respected IP, so he's responsible for all the inequity in the world and the vaccination rollout.
I wonder if Amtrak is the antipattern here for just that reason. Or even the state. How about county to county? Rail just can't cost this much in actuality. It's gotta be the systematics
What does Swift have to do with Tensorflow. It's like comparing apples and oranges.
Sainsbury's ex-boss buys into grocery app market
>Anyways, did you get the FB job?

Yup
The dangers of travel when your country declares war on the country/territory you are in:

King George III lamented the French ruler’s “restless disposition,” and on May 18—a little more than one year after the armistice—Britain declared war on France.

In retribution, Bonaparte issued a decree that all British citizens in French territory over the age of 18 be held as prisoners of war—including those living in Geneva, an independent city-state that Napoleon had annexed. Roget was stunned. “The measure was so unprecedented and so atrocious as to appear destitute of all foundation,” he wrote.

——-

Unfortunately this is type of travel misfortune has occurred to so many.
Exactly this. You never know your problem domain as well as you think you do.

I always try to start a new project assuming everything could change. Paradoxically, this approach tends to produce the same net result as assuming nothing will change. If you have no idea how requirements will evolve over time, there's no point guessing. Just write the code needed for the first batch of requirements, and nothing else.

It is orders of magnitude easier to add a layer of abstraction to a simple system when new requirements demand it vs. remove a layer of abstraction later when you finally realize you don't need it. The latter is often impossible.
People need to stop with this idiotic idea that Shotwell is some firefighter constantly holding Musk back. This is a meme at this point.

Shotwell and Musk are working together very closely and have for 10+ years. Shotwell is often just as aggressive as Musk. On Starship specifically Shotwell has been just as agressive as Musk.

And Elon is not a 'hype man' he is the Chief Engineer no matter how much people want to ignore that and call him a marketing guy or business guy or a hype man.

NASA was clearly impressed with what SpaceX is doing with Starship and that was during the time when 'hype man' was running it (according to you). Accept of course we know that Shotwell is very much involved.

Starship is developed the way it is because it is the most of how ambitious it both for operations and production. And those criticizing have clearly never developed a fully reusable rocket the size of a sky scraper so their criticism is mostly worthless.
(in neutral use) large size or scale.
"I began to get a sense of the enormity of the task"
I'll add one more thing to my sibling comment. This person is clearly unaware of whether there is ongoing R&D in the realm of hobby astrophotography mounts. They mentioned they're just considering getting into it. They're talking about mass manufactured goods. They were not aware that this is a field of active innovation.

We could have given someone a warm welcome to the hobby by clarifying that politely.

I know when I was getting started, I didn't know what made some things more expensive than others. I didn't know about doublet or triplet refractors, Strehl ratios, Chroma vs ZWO filters, why a MACH2 is such a grail mount over a Optron CEM120. Luckily I had nice, friendly, helpful people to talk to, instead of a wall of arrogance.
I'd not like to see this response go unanswered; I'm the first to attack these organisations for the damage they do and I've long abandoned reading them, having written them off for the damage they've already done.

But I can respect honest acknowledgement of the bad while arguing the good side is worth staying. You'll (obvs) have a better perspective as a subscriber and given you can approach the thing with nuance I'm willing to go with your take on it.
Do you have similar problem?
What will you do if go abroad is your only solution? Especially if corona and you don't have legal reason to go to other country.

So, my brother let say do crime. Using your identity to get loan or bad talking about you and you get bad rumour. Then in your country, you need to pay fine because in the family card, you are the only family he had.

Your exboss who had artist and blue blood family know then trapped you since he also doesn't like you have a career. Furthermore, he has a friend who works at google hq. And plan to involve in your life since 5years ago.

If i can reborn, i wish don't live like this.
It's a tiny, dying mining town over 50 miles away from the closest community. Having fibre is amazing as it is.
Two options spring to mind:

1. Don't worry about that failure mode. There will always be ways for collusion among employees to gain salary information.

2. Publish the methodology by which compensation is calculated. That is, it is presumably some combination of algorithm based on location and role, performance, and discretion. Make the calculation methodology transparent (internally). This will also set a range you can publish externally.

This allows people to ask informed questions ("why is my perceived performance not being rewarded") instead of being completely baffled by numberwang. Transparency about the process and forces the company to do better, which is a good thing.
I always recommend the nlnog IRRexplorer for this stuff.

Much better to see what the situation is for IRR/RPKI for a prefix/AS:

Cloudflare:
http://irrexplorer.nlnog.net/search/1.1.1.0/24

One of the prefixes this thread is about:
http://irrexplorer.nlnog.net/search/7.0.0.0/24
Well it's unlikely that person was the only one on your team that could run a two-line scp script. Choose any two engineers and their expertise in, and understanding of Docker is going to differ, but they should equally and completely understand basic file copy tools.

I would guess you are more likely to be in the situation where only one developer really knows your complicated build tools and how exactly they are put together. That's your actual "hit by a bus" vulnerability.
Crypto really has nothing to do with trust.

It provides a mechanism that enables distant parties to be confident that they hold copies of the same document.

That’s all.
You're forgetting the performance license. With a (consumer grade) CD you get the rights for private performance of a non-commercial nature.

You don't usually get the rights to play the music for large audiences or for commercial use - those cost extra.

If you didn't get those rights then you couldn't even play the CD in the privacy of your own home, as that constitutes a performance of the work.

(Of course I kind of think there's something fundamentally strange with the idea of having to get "performance rights" for a recording that you supposedly own, but that doesn't change the law right now.)
Think Raku
We often talk about the auto industry as a whole screwing up but I wonder if there's an automaker out there that didn't follow this trend and is doing fine.
> It was developed during a time when there was a push to make Software Engineering a licensed profession

Regardless of the merits (or lack thereof) of the original push, I do want to see greater accountability and oversight of safety-critical systems and related, such as IoT systems - the idea of having a licensed/chartered engineer having to sign-off on a project (and so putting their personal professional reputation at stake) is something I support in the aftermath of things like Boeing's MCAS snafus - or the problems with Fujitsu's "Horizon" system - and so on.

I don't want occupational gatekeeping like we see with the AMA and the trope of licensed nail parlours, but we need to learn from how other engineering professions, like civil-engineering and aviation engineering, have all instituted a formal and legally-recognized sign-off process which I feel is sorely lacking in the entire software engineering industry.
Ricardo Reis
You can commit the deployment script in the app repo. I'm not recommending not using ci/cd, but not using it doesn't mean you run every step manually from memory.
I fully understand this point of view, and I think it's invaluable to have said checklists and DDx lists. Having tools like UpToDate and DynaMed is awesome. Especially for emergency medicine, being able to DDx complex situations quickly and provide immediate life-saving care is very important.

But — and I don't say this to provoke — I think this view is myopic. It somehow misses the humanity at the core of the doctor/patient interaction. What is the ultimate purpose of medical care, really? Is it not to treat the patient, and not simply cure the disease?

A lot of times the checklist-style of medicine forces patients into a loop of patchwork solutions which don't address the root cause. To an extent, this is even true in emergency medicine. If someone comes in with their third heart attack, and they're clearly obese and in bad health and spirits, the problem that needs to be fixed goes beyond the immediate danger of the heart attack. There's something much more systemic, much more basic, which lies at the core of this person's suffering.

And I think the same is true for many chronic diseases and ailments, which are hard and time-intensive to solve in a holistic way, but which are easy to treat with patchwork solutions.

Take also the recent advent in hospice care, which I find wonderful. Hospice kind of rethinks the concept of "curative" medicine and treats the patient as a human being. How many people spend their last days in a miserable state, burdening themselves and their families by forcing themselves to stay alive? The "treatments" justified in the name of life-saving care can be incredibly diabolical and torturous. Doctors know this, and they often spare themselves that gruesome fate: https://www.rd.com/article/how-doctors-choose-to-die/.

Point being — treating the patient is not as simple as it sounds. The proper treatment is not only to fix the immediate disease.

But again, I am not against checklists. Doctors who use checklists and can care for the patient at the deeper level of soul and psyche are golden.
There was a port in the works at one point.
The reason to use build and deployment tools has nothing to do with _how_ the tools actually work. Deployment issues are mostly issues of consistency and access. Who runs the build/deploy, from where, with what arguments, when? Using a CI/CD pipeline isn't just wrapping an scp call in a bash script, they provide tools for managing the when, the where, the why.

Do you think using only scp will prevent you from deploying the wrong artifact? Or deploying to all-but-one production node? Or scping but forgetting to run the nohup?

Honestly setting up a github action to do this takes very little time, doesn't depend on containers, doesn't really add complexity to your stack. CircleCI exists and is equally easy. To suggest that your above-posted script is just as good is, to me, mostly just NIH + developer bikeshedding. YAGNI is great for being honest about the needs of an org and ignoring tools or frameworks that aren't appropriate, but there really are tools that exist that add consistency in ways that don't really increase complexity all that much.
> Docker containers is [...] a universally-understood encapsulation of an app or service amongst technical and non-technical people alike

On what planet does a non-technical person even know what a Docker container is?
Docker in itself, apart from everything else, is not that hard to setup. But you have to look at the bigger picture here.

Maybe the deployment is on "pet servers" and not on-demand, which means if you are a responsible admin and have a nftables config you need to analyze how docker will mess up your rules (or why it is not working).

Maybe you don’t want to lose time setting up an artifactory, and a docker registry with proper access controls.

Maybe you don’t want to have to focus on the ops side of things until you actually need it. Yes that may mean losing time later when you need it fast, but at the same time this can be done iteratively when things are ramping up.

From experience at a previous workplace, using docker as part of your local development process can be a huge PITA, and getting developers to adopt it without grumbling and complaining about it every day is also a hurdle. Given enough computers, you will get weird network errors, some borked modules due to an upgrade, some containers refusing to die, etc…

I am not saying it cannot be done, and in the general case docker mostly works without (too many) glitches, but it is always another layer that hinders your productive work.

(also, "docker" in production nowadays is mostly a shortcut for k8s, and that is a whole new amount of investment required)
They use a lot of Java and Scala. But I'm sure it's inevitable some teams are dogfooding Swift on the server as well. Swift is a very nice language.
You can also build a fat jar, which is basically a zip file containing everything but that the JVM knows how to load. All the static assets can go in there, too. It saves you the build.sh.
It makes me think of the recent "Nature is healing" memes (sometimes "Nature is healing, we are the virus"), i.e. Nature is taking back what humans assumed was theirs to keep.

https://www.buzzfeednews.com/article/emmanuelfelton/coronavi...

I agree that the "cute/relentless" combo of beavers is quite comical..! See:

https://www.irishtimes.com/news/beavers-continue-relentless-...
To be fair, scp was officially deprecated: it is effectively "legacy knowledge" now, and so soon it will be difficult to find anyone who can use it effectively. https://lwn.net/Articles/835962/ In contrast, we all know that knowledge of the Docker container format is both universal and likely to "stand the test of time". That anyone would believe that merely downloading a binary and then running it directly could ever be easier than first downloading and installing Docker so that you can then run docker on yet another file clearly has never worked as a systems administrator.
In different terms, we’ve all heard If I have seen far, it is only because I stood on the shoulders of giants.

Those who came before give you a leg up so you can work on the next problem. There aren’t enough years in a life to develop particle physics by yourself, completely from scratch.
Kivy as a touch based UI library is very nice and the cross capability is awesome.

Actually building production artifacts with buildozer is painful. Last time (admittedly 2 years ago) I did it I had to trick it into using a newer NDK because the play store required it but buildozer wasn't up to date enough to recognize the new NDK. Getting it to sign an apk was undocumented and required finding the right magical mailing list response.

But I can't put all the blame on buildozer. They seem like they're actually trying to abstract away all the pain of building native apps for android.
If you've ever built a PC from 90s era cases, you'll know it is quite easy to get a slight scratch/cut from some edge in that case. If you've ever done enough electrical wiring, you'll have felt the tickle at some point. If you've ever worked with near a stove or anything hot, you'll have touched something you shouldn't have at some point. There are a lot of oops that happen that are not life threatening OSHA violations.

If you've never shed a tear over something so close but ultimately not working, then you must be a robot or souless. It's human nature. You could just as easily add and/or swap tears for curses. Personally, I lean toward the cursing as it's more satisfying.

Also: argue: intransitive verb: To put forth reasons for or against; debate.

The fact that this word immediately sets forth a hostile emotion for you does not mean I am being hostile.
A lot of people that invest simply lack better alternatives. On the other hand the people that could invest reasonably like homeowners in energy efficiency do not have the money to do so, with the current monetary policy. Even if they had, they would gain more from investing in overvalued assets that have a growth in value detached from reality, driven by loose money supply for investors.
I have had the weird experience of dispersing a dead whale, stuck in an urban shore. No explosives allowed, no toeing, no T. rex, no light saber ... and a ticking gas bomb indeed.
I mean that it promotes a style of operating where a sudden change, for whatever reason, can cause all kinds of problems.
What's the argument for building in debug mode vs specifying -g to the compiler to build with debug symbols?

I've previously encountered bugs that stubbornly refused to reproduce in a non-optimized build.

One thing that comes to mind is `#ifdef DEBUG`-style macros, although I'm curious if there's anything else I'm missing. Omitted stack frames, e.g. from inlining, perhaps?
That assumes that you don't need to drive?

10 hours of active driving is something completely different than 20 hours being a passenger/sightseer (of which I would spend significant part asleep or reading) In fact I don't think it's safe to drive for 10 hours, you probably need to add several hours of rest, and will still be half zombie after that.

At some point the train becomes attractive. It's certainly a much less stressful option.

That said I must agree American trains are in poor shape compared to other places.
Agile killed off UML. Pre-agile, people were either doing really slow iterations (spiral development, rational unified, etc.) or just trying to do waterfall because that what people learned in school. Either way that meant obsessing over requirements for a while and then doing an actual design phase before you actually did any coding. And of course that required lots of diagrams and documentation; if only to give management some sense of progress (which to be fair was often the main point). UML merely tried to standardize that practice. And then IBM bought Rational around the same time the Agile Manifesto was signed.

IBM buying Rational emphasized how corporate things had gotten and drove the point home that the Agile Manifesto signees were trying to make that basically was about eliminating inefficiencies and bad decision making from software development.

Extreme programming introduced the notion of a sprint measured in weeks and the notion of having working code at the end of each sprint. Later scrum, kanban and other agile methodologies copied at least those parts of the process.

Whichever your flavor of Agile is, two weeks does not leave a lot of room for maintaining artifacts that don't evolve along with code. Like UML diagrams. You draw a nice diagram, then you code for a week or so, and then your diagram is out of date. You could fix it by dedicating time to that. But you'd need to do so every two weeks. Or you just skip the part where you obsess about having diagrams and just move on straight to just worry about how to best run sprints.

Extreme Programming was extreme because it intentionally skipped both requirements specifications and design documents as things because they realized that requirements were a combination of wrong and out of date because of things you learned during the project. And consequently, the designs were wrong as well. You do a little bit of requirements and design each sprint. That's called a planning and estimation meeting. Requirements are called user stories now. And since there is only so much you can do to a software system in two weeks, you don't need a lot of UML documents to describe the changes you are going to make.

Along with Extreme Programming came tools like white boards, camera phones, and wikis. You use them to do a little white board session with typically some simple diagrams, you snap a photo of the whiteboard, and then put it on a wiki where no-one ever looks at it again. Good enough if you are doing two week sprints. The second you wipe the board, it fulfilled its purpose: sharing and communicating ideas and getting some consensus.

So, that's why UML died. It's no longer needed. Too expensive to create, more expensive to update, limited value once you have it, very limited shelf life once you stop maintaining it.
I've been working on enterprisey Java software for nearly two decades, and I've never come across anything that's full of "factory non sense" in the wild. Sure, I'm just one person, but I've worked on more projects than I can count. With good teams and bad teams alike.

I'm sure there are shitty programmers in every language community, who will write things using concepts they understand only marginally, and I'm sure it has lead to a couple of FactoryFactoryFactories here and there. But the ecosystem is not "full" of this at all.

Java isn't the same as it was 20 years ago. It grew up.
Comparing UML and No-code is apples to oranges. UML is about generic abstraction without actual implementation. No-code is about domain-specific implementation done using simplified high-level visual constructs instead of general-purpose programming languages. In other words, No-code is programming (just not text-based), while UML is modelling.
I just finished implementing a small service that talks to the stamps.com API and I have to say that its been really easy to implement. Deployment via Docker is really easy, for small services Vapor is just great. The Vapor Discord community is absolutely fenomenal.
Is it described in the page? A technical description may get more traction here.
Why wouldn't I be?

Fractional reserve lending is one of the ways in which the money supply is actively managed. Adjusting the reserve rates adjusts how much banks can loan, which adjusts the circulating supply. It's not in and of itself intrinsically harmful.

Remember, that nobody has lost a single dollar to a bank failure since the backstop (the FDIC) was introduced in 1933 - following the Great Depression. Even in the Washington Mutual failure in 2008. The FDIC by the way is a funded through premiums paid into it by the member banks. They have an emergency credit facility with the Fed, of course.

This is completely different than issuing company scrip and buying up assets with it to enrich yourself with it.
The author clearly states he prefers a statically typed programming language for large, long-lived programs.
Inflation is a tax on money (so yes, savers). It's not a tax on labor, nor is it a tax on productive assets. Normally speaking, compensation changes with inflation
I hope that beaver can chew through all fiber cables in the world and people go outside and live more and communicate in person again. Good job beaver.
A society that takes climate change seriously will replace international air travel with passenger ships featuring high-speed satellite internet and spacious work areas. Little-known fact, ocean travel is 3x more energy-efficient than even rail.
I was excited for this to come to CA but at a public company it is only a weak signal because your salary is not your total compensation. My RSU are about 50% of my TC, which isn’t uncommon but can still vary wildly up and down the % of TC. So weather my salary is above or below Jill or Steve’s doesn’t mater much when their TC takes into consideration things this gives no visibility into.
Yes, sorry "autocorrect"
Not sure if this is a nit or not, but NFTs rarely represent ownership of anything other than the NFT. You're not really buying the art, you're buying association with the art. At least if I buy a Jackson Pollock, but the world realizes he's a one-gimmick artist, I can still enjoy the painting. If the world stops caring about NFTs, you're left with "cool story, bro."
Heaven or High Water: Selling Miami's last 50 years