skysight-inc/HackerNews huggingface dataset:
The notion that the node.js ecosystem moves way too fast is a time-traveling statement from, like, 2012. When it really was, in a lot of ways, true. But today it really has congregated on a relatively small set of best practices and the tools you see today are mostly the tools you would have seen two years ago. They're also mostly the same tools you would have seen five years ago, and plenty of people use "old" tools completely and perfectly acceptably. You don't have to throw out Grunt if you like it, you don't have to rush onto Parcel if Webpack works for you. Because other people still use them and other people still maintain them.

Node is no less stable, today, than Ruby or PHP, and is only arguably less stable than Python because Python has largely ossified.

SQL database usage is still an ongoing bummer, though.
There's actually no reason you can't architect microservices like this. You can put RabbitMQ or some AMQP service as a comm layer between services. But then you have to architect your system to be event-driven. It's not a bad approach.
>Ah sorry, "A con of a con stands indirectly of support of the original pro" — better? :-)

From a logical standpoint, not at all.

From a social standpoint, it often does persuade people towards the pro. However, that is a known fallacy. It is a standard tactic in persuasion.

From the movie "Thank You For Smoking":

Joey Naylor: ...but you didn't prove that vanilla was the best...

Nick Naylor: I didn't have to. I proved that you're wrong, and if you're wrong I'm right.
Could you provide some examples of times when being arrogant improved the quality of the product you delivered?

I've certainly run into arrogant engineers in the past. I spent the 2-3 weeks after the worst of them left cleaning up his bug-ridden, brittle code. If he had worked more collaboratively, it wouldn't have had to be that way.
> if it sounds like a digital it's not so fun anymore

There's a DSP for that. Or ten.
Yeah, I think this is actually calling out a major weakness in the original comment's hype cycle model. Sometimes step #5 ("Five years pass...") doesn't happen in that way. Sometimes what happens is that the new technology has been found to be generally useful, though imperfect, as everything is. People may be evolving it in different directions, perhaps incorporating elements of the old technology the new one replaced, but it isn't being fundamentally abandoned. The tough part is that you don't know which version of step #5 will happen when you're surveying the world at step #4.

If it was easy to figure this stuff out, they wouldn't pay us to try :)
How to Deploy Canonical Hostname and HTTPS Redirects to Edge Servers Using Fly
"With everything running in a monolith, if a bug is introduced in one destination that causes the service to crash, the service will crash for all destinations."

The real reason people should investigate Erlang/Elixir.
We should bring Categorical concepts into microservices. Maintain compose-ability between entities rather than forming a graph of intercommunicating objects similar to OOP.

I don't know if adhering to these principles will make microservices better.
Clever! I'm thinking a similar design with a range of hole sizes and wider borders could be a handy generic tool - might have to design and order one next time I'm making boards with QFNs.

Does anyone here know what the smallest practical hole size is in acrylic?
Hilarious code:

>>`"so your first mistake was using my code, but since you are clearly reading this
let it be known that mutuals.py lets you create a mutuals list on the hell
site known as "twitter dot com".`

It would be cool to make the list private.
So it's their inability to be replaced that's the issue - some other mechanism is failing us. I suppose in the short term removing the cells "manually" would help.
Hey, if you can go without, or have fuck you money, or have other options, then you aren't truly in need. That is a want scenario.
They might help the platform for consumers, but I'm talking about for the owners of Twitter. Third parties don't help by a measurable amount, or if they did, it is less than the cost of maintaining a good API.
From the same wiki article:
"The wine trade in Italy consisted of Rome's sale of wine abroad to settlements and provinces around the Mediterranean Sea, yet by the end of the 1st century AD, its exports had competition from the provinces, themselves exporters to Rome. The Roman market economy encouraged the provinces’ exports, enhancing supply and demand. An elevated supply of wine meant lower prices for consumers."

If that's true, then it worked out well for Romans wine consumers, likely freeing them from local wine-making monopolies, and also for the development of regionally unique varieties of wine.

Also, what is the relationship between Roman wine making technology and Teslas? It's not like China doesn't know how to make electric vehicles - they already produce many more that the US does.
It's a timing question. If the dead person gave away a diamond ring before death then it's not part of the estate and the new owner can keep it without issue.

If the dead person owned a ring when they died then it's an asset that can't be passed on until after debts where paid. However, the estate can sell the ring which they still own for what it's currently worth without issue. They just can't give anyone assets until debts are paid.

This opens up something of a loophole where family can purchase items of a sentimental nature which are not actually worth much on the open market.
Yes! Attack everything around it, and any mistakes using it.
My name is Ivan and I keep making the best photo editor in the world
Who would want to use a rolling release distribution for a (production) server? Sounds like a pretty terrible choice, to be quite honest.
Keto + intermittent fasting is a great combo. You just feel better and less bloated day to day.
Its amazing. Thanks for sharing.

Regards,
Mohammed Ovesh
https://www.sherekhudahazratali.com
While china is ruled by a nominally communist party, its party is definitely undergoing deliberative market reforms that are inspired by western capitalism.
Been using JS for years and still loving it. The only thing I would move towards from here is some kind of ML like Elm, Reason, Haskell, etc. Certainly wouldn't go back to Java.
But that's pretty much what the parent asks about in this context: the existing debt is part of the estate, and relevant to the heirs. I think you misunderstood the intent of their question by focusing on the "inherited" too much.
I think things like computer vision would be more accurately labeled as "drawing conclusions" rather than "making predictions". And if you can get your prediction success rate close to 100% that seems more like drawing a conclusion as well.
didn't really see an answer from him.
> What's needed is a fast-living animal, that ages, and gets cancer, in the same way humans do. Then you can just experiment without understanding.

A simulated human?
"Since I published this piece Microsoft have made significant improvements to HTTP scaling on Azure Functions and the below is out of date. Please see this post for a revised comparison. https://www.azurefromthetrenches.com/azure-functions-signifi...
Separating by schema would work, too. At least, they would be separated from each other but still on the same database.
unfortunately, matomo is harder than necessary to automatically deploy to containerized environments like heroku because they don't support the 12 factor principles [1]. a cynic might assume that this is because it would undermine their own hosted solution.

[1] https://github.com/matomo-org/matomo/issues/6223

(i would use matomo if they fixed this issue)
This essay felt sparse on the detail. Every tech person on HN knows their product and problem domain quite well - how to market it is a genuinely different problem.

Mentioning "listening" is a great point - but this is not particularly novel (any book on sales & marketing would suggest this first step as well).

Some points I was expecting:

- Story telling, vision setting and narrative building (I would recommend "CopyHour" for anyone interested)

- Visual imagery (design, photos, icons)

- Content marketing (informing your customer, aka. "thought leadership")

- Sampling across various marketing channels, then scaling on those which perform well ("Scientific Advertising" is a very quick read here)
It's UI is outright ugly.
Same here, DirtyPCBs is great! I particularly like that you can update orders right up until they have started in production.

The SLA printing service is a real game changer too.
The Big Bang Theory is an insulting characture. While some developers may like it - it's not really best way to endear yourself to a group of people.
That's encouraging. Given the usability (or absence of such) of iTunes etc. I would hate to have to look for replacement for 1passwd.
>China’s energy companies will make up nearly half of the new coal generation expected to go online in the next decade.

https://www.nytimes.com/2017/07/01/climate/china-energy-comp...
> Can you imagine if one of the cures to aging is safely removing senescent cells from the body?

Very rarely are things in biology so simple. Everytime we thought something was useless in the past (junk DNA, appendix, tonsils, ...) it turned out that removing it causes damage somewhere else.
The first point is 100% wrong in my experience. I know multiple great marketing people who climbed the ladder and do the job quite well. In my experience, the people who only market their own products do succeed for the reasons the article mentions, but they have minimal capability to break down why they succeed and translate it into success on future projects.
But you can then twiddle with these photons after exchange right?
Use them to communicate after?
Otherwise what's the point?
My bad. I'm so used to the cognitive dissonance around here.
Google Risks New Antitrust Fines in the EU. The U.S. Lags Behind Again
We have RIPE and other IANA organizations that have routing objects in their databases with information about through which ASN certain classes are announced, there are also LOAs. GTT and Cogent are huge Tier-1 providers, why they do not check which classes their clients are announcing? Am I missing something here?
I'm not sure I've ever read a clumsier, more tone-deaf introduction to a blog post.
I can kinda understand that using docker makes Java programs "run" the same way as other languages. But from my perspective, if you run a pure Java stack, using docker instead of the Java technologies for packaging, deployment seems like a step backwards.

You can probably use for defining and spinning up new servers (with JRE, database, servlet container and so on) though but that's a different story.
> I've always said if the Linux kernel can be a giant monolith, in C no less, than there's maybe 100 web applications in the world that need to be split into multiple services.

This is apples and oranges. The production profile of operating system kernels and web applications are so dissimilar that the analogy is not useful. It may be true that most web applications don't need to be split into multiple services, but the Linux kernel provides no evidence either way.
Agreed, but a millennial can be over 30 years old. This sounds like they're emulating a 10 year old trying to be edgy.
I don’t know, but if I did, I’d get a CS degree and skip grad school, probably ending up with 1/3 the student loans.
It sounds like he read a good book, but that article really doesn't say anything about actually "Rehabilitating the Arrogant Engineer", just that he read about it, kinda.
I know these aren't your arguments but I can't help but respond to them.

> Saying “I was respectful!” often doesn’t fly.

I think there's a big difference between works that are mockeries versus work that seeks to make something beautiful & useful that's obvious to most people.

> It seems unfair when an impoverished people creates something beautiful but gets little economic benefit from it, while someone from a richer country/ethnicity comes along, reproduces it, and then makes a lot of money.

I can understand this sentiment if the derivative work is nothing more than a copy. However this is an argument that's similar to the ones that proponents of extending copyright forever make. It's just another form of gate keeping and monopoly. Ideas should be shared and used. It helps promote and continue innovation, and in this case share culture.
Ugh. I know a lot of people who went to electrical or mechanical engineering and wound up doing software, and the pay's better.

I might focus on embedded work, or math maybe, because this web dev world full of bright-eyed, bushy-tailed youngsters repeating the mistakes I made in 2002 is getting pretty old.
Gravwell Community Edition: A Splunk Alternative Built with Go
Best vector web based tool
Script to download full sized images: https://gist.github.com/RyanEager/a747215c259ffecb9beb1dfec0...
Correctly identified that a product would be a GDPR problem. Said product's main feature was deanonymizing non-consenting visitors.

Insisted that certain metrics should be recorded, ended up identifying massive gaps in SLA, improved overall QoS.

Was asked to give SRE and Devops advice to a team. Told them to document their "regular tasks"; that is, to write down a doc "How to Upgrade Frob Databases" so that they would have a way to do all the "Upgrade Frob Database for Customer #xxx" tickets on their kanban board. Got pushback. Wrote the docs for them anyway. Their kanban board drained over the next two sprints.

Edit: In all cases, got massive pushback from management and never from devs nor engineers. Was called "arrogant", "troublemaker", "enabler", reprimanded, etc. You asked for examples, you get examples.
Reminds me of the opening lines of the SICP lectures[0]:

"I'd like to welcome you to this course on Computer Science. Actually that's a terrible way to start. Computer science is a terrible name for this business. First of all, it's not a science. It might be engineering or it might be art. We'll actually see that computer so-called science actually has a lot in common with magic. We will see that in this course. So it's not a science. It's also not really very much about computers. And it's not about computers in the same sense that physics is not really about particle accelerators. And biology is not really about microscopes and petri dishes. And it's not about computers in the same sense that geometry is not really about using a surveying instruments."

[0]: https://www.youtube.com/watch?v=2Op3QLzMgSY
I don't know if I'd call a lot of the things described in this article camping. If I paid $200 a night to stay in a cabana in the Caribbean, eat three meals a day and have access to a bar, I'd say that I spent my vacation at a Caribbean resort and wouldn't dare to call it camping. Likewise, I don't think it counts as camping if you do the same thing in a forest in North America. I think it would be more accurate to call these places "Outdoor resorts" or something similar.

I don't think you have to hike 20 miles into the forest to camp, but I think the level of service and amenities provided at some of these places shift it away from being camping.
I'm not shy about calling people out on self-serving narratives. If that article pointed at "startups should be more pliant to VC narratives", I'd be throwing down the rhetorical penalty flag, calling Projection on the offense, and telling them to try again.

That all being said... it appears that you're assuming facts not in evidence.
Linux is the kernel.
Editorial and Marketing Calendar for Small Business
What annoys me most about that show is that 3 physicists and a mechanical engineer are often shown writing working software. That's rarely the case.
New, easy-to-use marketing & editorial calendar for small business. Just launched the beta and am offering free accounts until we do our commercial launch. I would love your feedback! I'm offering lifetime discount for anyone who signs up for beta. Go get it! And thank you.
I was thinking the same thing. I don't think you'd score points in the office relating to engineers with a "Hey I watch Big Bang Theory!".

blank stares

I once had an HR team give a talk to a bunch of engineers. They opened up with "Who watched Judging Amy last night?"

It did not go well after that, in fact it was a horrific couple days of "training" where everything went wrong communication wise, for a lot of reasons ... one dude effectively ended his time at the company on one of the first days when he got into an argument with HR. (Granted that wasn't Judging Amy's fault).
The hypothesis I have heard is that fasting and keto both result in ketone bodies and ketone bodies result in the cellular optimization (culling old cells so not spent precious energy resources on less efficient older cells).

IF this is correct, it means keto and fasting both accomplish the same thing in terms of life extension, only with keto you get to eat bacon, steak and cabbage, spinach, brussel sprouts, etc rather than starve and be miserable. :D
I hear so much of this fasting hype lately. People seem to conveniently forget that you:

1. Lose all your muscle mass.

2. Suffer malnutrition.

3. Destroy your stomach lining due to too much acid building up.

All for zero proven benefit.

But hey, people like TDD too, so I don't hold it against you.
The electric scooter wars enter a new phase with Uber and Lime
Many big ISPs are quite diligent about what blocks their downstream customers announce. If you're an NTT ip transit customer every new block you announce to them is vetted. They have a high degree of automation with IRR integration but also humans in the loop.

Any asshole can theoretically make a fraudulent LOA, but by producing one to an upstream a hijack factory opens itself up to criminal charges of fraud and forgery.
There's a lot of hatred for ORMs that floats around but most of the ire seems to revolve around the cases where the ORM's flexibility doesn't allow it to expose the power of the underlying database properly. But people often fail to note how few and far between these examples are and how the vast majority of an app's queries tend to be dumb & boring and handled extremely competently by the ORM. Contrast this with the number of dumb typos & sql mistakes through verbosity that the ORM has saved. Don't get distracted by the 1 or 2 cases per app.
badlanguage/ is too long
I tried several different queue systems best version I got is using Erlang Queue, Elixir & Kafka on top for doing high concurrent crawler, the project was to develop a realtime Amazon product ASIN price monitoring system for our company as a challenger prototype. Our main problem was basically proxies, we stopped buying them as managing thousands of proxies is a huge effort that we did not want to take, also lack of data means our Hadoop clusters gets thirsty and machines stops learning properly. Currently we are using a third party https://proxycrawl.com on very high tiers > 10B with a great discount and we are happy to get that part solved. Other lessons learnt are like sometimes things fail and logs help a lot so you will need a highly available Logging and monitoring system.
You should read the PKGBUILD, even on upgrades. In this case the bad guy took over an orphaned package (with 853 votes) and updated it. You could have looked at the upvotes 5 years ago and blindly upgraded to his new version last week.
As someone that works in a high energy particle physics lab, I have a slightly different perspective on this. There does increasingly seem to be a sort of anti-not-invented-here bias to externally buying off-the-shelf solutions, this has resulted in lots of equipment in storage that simply does not do what it was specified for, essentially expensive paper weights. It is also causing a lack of knowledge and skills development for new scientists and engineers. Big problems are looming as lots of our scientists and engineers with their 30+ years of knowledge are retiring soon, the new generation need to be allowed to develop knowledge and expertise though their own designs, not just buy stuff in. Imagine if we had said to the authors of Art of Electronics in their early days, hey guys don't bother designing all this instrumentation, we'll just buy it in from National Instruments, what a loss that would have been.
I'd love to be able to do all this, but it sounds like a little bit too much work. Aren't the gains of all that process (e.g. code reviews, etc) the fact that it helps multiple minds get on the same page? With one person isn't it more trouble than it's worth?
Pure anecdote so I know it is meaningless but I have rewritten/refactored old services with new code, or even new languages twice with little problem because the interface was well defined. We had hundreds of devs working in other areas and we were all on different release cycles because changes were easy and decoupled. We let any team submit bug reports when we either weren't complying with our interface or we had a bug somewhere.

The only teams I had to spend time on were the ones which were on a common DB before we moved off of it.
>it makes sense from a legal perspective

No it doesn't.

This is the work of a second rate player on paypal's legal team. You do not address letters to dead people. You address letters to their estate or if you know who the individual is, the executor of the estate in respect of their estate.

You do not say someone breached a contract when in fact you're exercising a right to wind up the account triggered by death.

Either one of these errors is an annoying mistake. Both of them together is a fairly large fuck-up. Lawyers put a LOT of work into drafting the right tone into their correspondence.

Estates law isn't particularly esoteric, either, but most in-house counsel practice corporate law, primarily, so it's probably just a case of a few corporate guys going "It looks okay, I guess" when proofing the template and not firing off a quick call to their pal that works in estates to review the deceased creditor notice.
I wonder who the target audience here is. It is a short article composed of quotes from Randy Pausch, some generalizations about engineers, and sports metaphors.

> I’ve had the privilege of spending my entire career in technology surrounded by wicked smart engineers. I’ve always been drawn to their raw intelligence, Spock-like rationality, sincere honesty, dry humor and quirkiness. With the immense popularity of the sitcom, “The Big Bang Theory”, I suppose I’m not alone in my appreciation of them.

Almost none of the characters on Big Bang Theory were engineers, they were physicists. This article seems to conflate 'nerd' with 'engineer' on an incredibly surface level exploration.

... and before anything is actually stated, it moves over to use sports metaphors to accent how important teamwork is.

The awful truth is that arrogance, inability to delegate, poor communication, poor ability to react to feedback are traits that are rampant in pretty much every industry, including VC. Picking out engineers are some type of specific 'archetype' especially bad at these skills is buying into awful stereotypes about engineers as if we have no social skills.
Interesting. My PI in undergrad had several R01s and we were swimming in funds but their spending categories were restricted. $50000 to us on labor may have been worth it for $25000 in equipment, for instance. He did, however, refuse to tap the large startup fund, which could have been spent however he wanted and instead saved it for a rainy day. On the other hand, we had a very strong "core/shared" support and could basically rent equipment. With the amount of money he was spending on the core, we had a huge influence on the equipment purchased. Also, we collaborated with other groups helping their projects, gaining access to their equipment for our projects. Basically, trading our labor for their equipment.
Elon again making promises he cant keep. Tesla cannot even make 5000 / week.