skysight-inc/HackerNews huggingface dataset:
> Buying a 100 megapixel digital camera would cost me ten thousand dollars minimum.

Hasselblad makes some nice ones.

https://www.hasselblad.com/h-system/
I thought that's what solutions like Calcite[1] were for: running queries across disparate data sources. Yes, you still need to have adapters for each source to normalize access semantics. No, not all sources will have the same schema. But if you're trying to combine Postgres and DynamoDB into a single query, you would narrow your view to something that exists in both places, e.g. customer keys, meta data, etc.

Maybe I'm wrong.

[1] https://calcite.apache.org/
So many problems arise from the idea that "we are going to do this thing to the maximum extreme and exclusion of other possibilities."

Just look at the US legislature right now. Anyway, it doesn't have to be Monoliths vs. Microservices. It can be a compromise. Perhaps the microservices are a bit less segmented than we have been imagining. It might be OK for a microservice to do more than one job. As the highlight shows, the fundamental ingredient is Engineering Discipline. If we strive for that it might work out in a Monolith, Microservice, or somewhere in between.
> I don't recall anything nefarious

If an SSL backdoor installed by the OEM doesn't strike you as nefarious, I have beachfront property in Arizona to sell you.
Because most of the time you don't get hired at FB for a specific team, you might end up working on PHP sure, but the interview process for SWE is general and they test you on algorithms regardless.
Dhall[1] is a similar concept, though instead of augmenting a particular format, it is an implementation of a simple pure functional programming language (with a very expressive type system which guarantees termination). Dhall programs can then be evaluated to several different formats (currently JSON, YAML and XML).

[1]: https://dhall-lang.org/
I am very aware of driving's safety statistics. And I'm not saying people shouldn't be able to design their spaces the way they see fit. It's on San Fransiscans to decide what is best for the city, and everyone outside can just deal. Buy neither is "GM blackmailed people" and excuse to treat drivers like murderers in these conversations.
> I would tell them that I could look at myself in the mirror and have a full blown telepathic conversation with myself without opening my mouth and they responded as if I had schizophrenia. One person even mentioned that when they do voice overs in movies of people’s thoughts, they “wished that it was real.”

I think this author has an inaccurate understanding of people who do not have an "auditory" inner monologue.

Think of it this way: a lot of people don't vocalize text as they read it. I do not. I am still able to read, and I still "understand" what is being read, but I don't need to turn it into voices and sound it out, to gain that understanding. Tbh, I find it slows me down.

Inner monologues are the same way. People still have rich inner "conversations" even if they aren't vocal ones. Which is what I do -- I'm not really sure the best way to describe it, but I'm able to have a "debate" between inner arguments without mocking it out as two people talking to each other (I mean, I can if I want to -- but I find it unnecessary and slow, personally). I'm sure a lot of people are the same way.

I think the author is getting a bit high on the idea that he has a richer inner life than the people around him, and needs to think about alternate interpretations.
What is old is new again.

I've been a software engineer for over 30 years and have dealt with companies always trying to jump on the next bandwagon. One company I worked with tried to move our entire monolith application, which was well architected and worked fine, over to a microservices-based architecture and the result was an unstable, complex mess.

Sometimes, if it's not broke, don't try to "fix" it.

I can say the same regarding a lot of what is going on in the JavaScript ecosystem, where people are trying to replicate stuff that works fine in other languages in JavaScript. Mostly because they are only familiar with JavaScript and don't realize this stuff already exists and doesn't need to be in JavaScript.
When small practices get bought or acquired by hospitals they typically switch to epic.
Similarly, not everyone can visualize things in their mind. Pixar's founder Ed Catmull did a survey of Pixar employees and, interestingly, there wasn't that big of a skew of artists who are able to mentally visualize.

https://www.bbc.com/news/health-47830256

I wonder if there's an intersection of people who do not have an internal monologue nor a "mind's eye?"
> They installed spyware. That is more than enough reason to lose trust.

I agree on principle, but Lenovo is no less trustworthy than any Smart TV manufacturer, such as Samsung, Sony, or LG.

It has become a common industry practice to subsidize consumer hardware with pre-installed spyware. The only solution here is to replace the pre-installed OS with an open-source alternative.

I would still pick Lenovo ThinkPad running Fedora Workstation over any iMac or Macbook product.
Or they see this problem and that's why the policy is sanely phrased as follows:

Going forward we’ll primarily use PyTorch as our
deep learning framework but sometimes use other
ones when there’s a specific technical reason
to do so.
Fast, Parallel Applications with WebAssembly SIMD
This reminds me of some other recent articles about topics like aphantasia (no visual imagination) and severely deficient autobiographical memory (SDAM). People who have these conditions do not realize how different other people think.
everything pales in comparison to Vanguard and its innovative ownership and strategy.
Have you heard of the email startup Superhuman (http://superhuman.co/)?

To use Superhuman, you need to join the waiting list and have one of their team members go through a 30 minute onboarding call with you.

Superhuman CEO Rahul Vohra has said many times that he's modeled the user experience for Superhuman after video game design. Note that this isn't the same as gamification.

He views the onboarding for Superhuman as a "tutorial" level in a game, while getting to Inbox Zero is a reward and referring other people is the equivalent of playing with other people.

Controversially, he says that he doesn't care what people want or need, but obsesses over how they feel. People don't need video games after all; they operate as entertainment.

I'd highly recommend watching a talk or two of his on YouTube if you're interested in his thoughts on the relationship between video game and product design.
Pretty much microservices happened because of managers. Managers are promoted to high level jobs such as Director or VP based on number of direct reports. This won't happen with a small team of devs. So they need an infrastructure team, a devops team, a SRE team, a QA team, a microservices core team, an access management team, network engineering team, AWS integration team, and the list goes on. What was once a four person team is now a 50 person team costing 10 million per year, but, hey, the guy/girl gets his VP promotion for setting all this up.
To me Mongo is like Redis: it has its place in the pipeline but is not a proper tool to replace a rdb nor should anyone pretend it is.
Anecdotally (on my own example) this might be true, with verbal skills anyway.
Email-hawk.com the solutions to send large quantities of email for less
Can you not "sound out" words in your head while reading? Is that the same thing or something else entirely?
This is interesting, because this is close to how I'd describe my thoughts. Occasionally I can go fully abstract with good focus, but most of the time I'm monologuing. Do you ever find yourself struggling to switch over to abstract thought because the monologue is just a duplication of effort?
These exact words apply reflexively to the left, you know. It absolutely stuns me that the left is able to correctly identify the things that empirically matter most to middle America based on their voting behavior, then campaigns on the opposite of that and still has the nerve to say they're "voting against their own interest".

The dehumanizing arrogance this kind of rhetoric betrays is profoundly disturbing and everyone who finds themselves thinking this way needs to stop immediately and do some soul searching. Half the country is not too stupid to discover their own values and preferences, and you are not the enlightened shepherd they need to guide them against their own will.
The way that technical learning works... if they aren't stubborn (and probably fired because of it) then they've likely adapted. Developers grow in knowledge over time as they hone their craft and every senior dev can easily call up some terrible crap they wrote when just getting started.

It's also likely that even at the time the devs working on this wanted to start refactoring more - it's one thing to recognize bad code, having the muscle within a company to allocate resources to fixing that code is a different matter.
But again, if you're not the domain admin you are pretty much SOL. It's not a friendly technology for the hobbyist.
I decided to switch to digital for anything where I want to go over 400 ISO. My personal feelings are that the image quality of 800 ISO film is just terrible. YMMV based on personal preference, I know people who really like the look of fast film.
Russian regulators bring case to court calling for mailbox.org ban in Russia
Me too. Sometimes I notice my internal monologue is slowing me down, so I turn it off and let the thoughts flow without converting them into words. Other times, I feel like the abstract thoughts are coming too quickly, so I'm like "woah, slow down there!" and work my way through the same thought process again in words, to assure myself that I'm not skipping steps and jumping to conclusions.
I’ve been a freelance in Finland for some time and was surprised by how easy setting everything up electronically was and how little I had to pay if my income was low in the beginning. I was also very surprised to see how helpful the tax office (Vero in finnish) is, even for questions that could be answered with “hire an accountant” but thanks to their help, I was able to do it on my own. I even made a mistake once and they let me know and fix it without consequences.

Compare this to my home country (Spain) where you have to pay a rather high fixed fee every month despite having no income (a typical situation at the beginning of any business), the amount of paperwork and unreadable legalese together with the unwillingness of the tax office to help you out with most of the stuff.

On a side note this guide looks great and wish I had such thing when I started out!
How would this work for something like Photoshop? Or is that an edge case?
> It is also why you really don't see any actual innovation come out of Europe.

There's actually quite a lot of incremental innovation happening in Europe, but they're in non-consumer spaces so they're less visible.

But you're right, a lot of European innovation is in the area of refining and improving proven ideas. The pool of technical expertise in Europe is vast and strong so it makes sense to leverage the competitive advantage there.

The U.S. on the other hand is much stronger at defying norms and inventing completely new categories.

U.S. companies know this, so the joke in industry is: invent in the U.S., perfect in Europe (setup R&D labs etc.), and manufacture in China.
At work, we switched over from TensorFlow to PyTorch when 1.0 was released, both for R&D and production... and our productivity and happiness with PyTorch noticeably, significantly improved.

Back when we were using TensorFlow, whenever we wanted to try something new that wasn't already provided out-of-the-box by existing APIs, sooner or later we would find ourselves wrestling with its machinery, especially for models with more complex control flow.

TensorFlow feels like it was built from the ground up to scale up to billions of users and all kinds of devices, with developer productivity and happiness a secondary priority. PyTorch feels like it was built the other way around, prioritizing developer productivity and happiness; other considerations were secondary.

That said, we are keeping an eye on Swift + MLIR + TensorFlow. We think it could unseat PyTorch for R&D and eventually, production, due to (a) the promise of automatic creation of high-performance GPU/TPU kernels without hassle, (b) Swift's easy learning curve, and (c) Swift's fast performance and type safety. Jeremy Howard has a good post about this: https://www.fast.ai/2019/03/06/fastai-swift/
I did this. I built a big service microservice first, with the single caveat that I wrote a local Python version that did everything with fake data in memory first, just to test it out.

I'm very happy with this approach.

> Splitting up your application in many services requires a lot of thinking and designing.

In my experience, you spend a bit of time asking "What does my project do, and how do I decompose it?" and that's about it. The same thing you'd do with a single binary that you decompose into modules.

> Challenges with syncing, communication etc are not always easy to deal with.

Depends on what you're doing certainly. For me, I'm basically doing an ETL and analytics pipeline, so I have no issues there.

I have found it much easier to reason about code and boundaries. I did a ton of experimentation with code and services (I didn't know how to build it when I started, so there was tons of iterationt) and the ability to just rewrite any service fairly trivially helped a ton.

I haven't had to do any "splitting". Merging services is trivial, splitting is not. I'd much rather say "Ah, the synchronization here is too hard, I'll shove it into one process" than "How the hell am I going to scale these two modules separately with all of this shared memory between them?".

I've gone through a "We have to start splitting things for reliability/performance/conway's law" and it's years of very difficult, dangerous work.

It's really a "to each their own" but I don't think I overengineered things at all. Microservices just make sense for my use case.
Isn't this the whole point of a data lake?
Sometimes they’re one and the same.

https://twitter.com/CaughtCctv/status/1212381004591255553
> Note that I consider the bulk of that utility to be in communicating to upper management.

A massive amount of software, tools, and techniques exist entirely for that purpose.

Best advice I heard was something like "treat them like children: bright colors, short slides, easy to grasp charts".
At GitLab a couple of years ago we had to fight the temptation to split the application up in hundreds of micro-services.

I'm glad we did and today GitLab has a big monolith but also a ton of services working together https://docs.gitlab.com/ee/development/architecture.html#com...

I did an interview about this yesterday https://www.youtube.com/watch?v=WDqGaPGBZ9Y
The Certbot team would like to see an official nginx integration at some point because it would be easier and more reliable. Certbot's integration relies on parsing nginx configuration files but the nginx configuration file grammar isn't formally specified and there are surely divergences between nginx's interpretation and Certbot's interpretation. (The last one I worked on, which I don't think we resolved, is that nginx allows you to use arbitrary character encodings in configuration files, e.g. many Russian users may have comments in KOI8-R rather than UTF-8. I believe this is because nginx doesn't make a consistent attempt to explicitly interpret multibyte characters in all contexts. Certbot, as a Python application, generally does nowadays.)

The most sustainable and reliable long-term approach would be to have Certbot's integrations gradually superseded by supported official Let's Encrypt integrations in applications that terminate TLS.

P.S. Thanks for your enthusiasm for Certbot!
It's not really bad for the time it was written, but today you wouldn't want to write PHP code like this.

Lots of global variables that can clobber each other (if one bit of code, even in one of the includes, redefines $user, everything explodes), no classes, no code autoloader...
As someone in the middle of destroying a monolith I hope the title is not true. Of course distributed-yet-still-deeply-coupled systems are possible they are at least harder to create.

For me though the most important thing is grokability. Our monolith is to a point literally no one on earth can understand the whole thing.

Even if the system is complex, the individual deployables being fully understood by some number of engineers is extremely valuable and drastically reduces search space for the cases where things don’t go as planned
I've been fascinated by this concept ever since I studied American Sign Language in university. When I spent enough time signing, I stopped thinking in words.

My thoughts became more abstract, quieter. It was actually kind of nice, peaceful. I don't know that I was any smarter or able, but it was a notably different experience in a minor way.

But then I graduated, moved, and stopped spending 1-2 nights per week at the campus pub signing with other students. And it all slowly went back to a loud internal monologue instead.
Community based crypto-product related reviewing web-platform
Here's a video about Maharaji, including Ram Dass talking about that exact case

https://www.youtube.com/watch?v=vXrDrxkOFX0
> Teams can still deploy their services and change their database schemas

No, because as soon as you change your schema, you have to plan ahead with the reporting team for starters. The reports still have to be able to work the same way, which means the data needs to be in the same format, or else the reports need to be rewritten to handle the changes in tables/structures.
The problem is that you get into wash sale rules [0]. Most people are not aware of this, but wash sales can be impacted by securities owned in retirement accounts [1].

Worse, the aspect of options and "substantially similar" securities starts to get arcane fast. Meaning, you really want a tax lawyer involved on a complex transaction like that. Otherwise, you may find that you've apparently made a ton of money, and then a few years later the IRS knocks on your door and asks for all your profits in a nice check paid to US Treasury.

(I'm not saying you can or cannot do this, only that the tax law gets complicated fast.)

[0] - (page 56) - https://www.irs.gov/pub/irs-pdf/p550.pdf

[1] - https://www.irs.gov/pub/irs-drop/rr-08-05.pdf

=======

EDIT - meant to add that "sale or other disposition" includes the expiration of an option. So you don't actually have to sell to incur the wash sale situation.
Huh, it's almost as if Ajit Pai is corrupt. Whadya know.
In a boolean sense sure, but the world is more complex that true or false, and some are more public than others.
Spot on. The metaphor I typically use here is cleaning up a mess vs spreading it around. If you have a really big mess and spend a year or two rearranging it into dozens or hundreds of smaller messes, yes the big obvious mess is gone, but the overall amount of mess has likely gone up and by segregating everything you’ve probably made it much harder to someday get to a clean state.

If you’re moving to microservices because the number of people working on a project is growing too large to manage and you need independent teams, great. If you’re refactoring to microservices because “we’re going to do everything right this time,” this is just big-rewrite-in-disguise.

Whatever engineering quality improvements you’re trying to make—tech stack modernization, test automation, extracting common components, improved reliability, better encapsulation—you’re probably a lot better off picking one problem at a time and tackling it directly, measuring progress and adjusting course, rather than expecting a microservices rewrite to magically solve a bunch of these problems all at once.
It never works out this way in practice. You need corporate clout to go against corporate policy. That's the point of having a corporate policy.

Of course they added that caveat. That's probably how this idea got through in the first place. Just point at the caveat and say "But we're not really throwing all the other frameworks under the bus. If everyone decides it's a good idea to use something else, we'll use something else."

Except that likely won't happen, because now as a junior engineer you need to convince N other people that using Jax was a decent choice. And it's against your company's culture to use anything but Pytorch.

This battle of Tensorflow vs Pytorch is bad for everybody involved. OpenAI released a lot of cool and important code related to Tensorflow. They did GPT-2 (tensorflow 1.x), blocksparse (also tensorflow), memory saving gradients (tensorflow 1.x), and now they're announcing they'll likely never be releasing such tooling again. Memory saving gradients have been hugely helpful to us for scaling our models beyond the normal limits.
Yeah, they're marvelous. But the digital back by itself is $26,000. A full camera is around $35k.
The hashtag #shootfilmstaybroke exists for a reason.

Film's initial cost may be cheaper than digital, but after 10-20 rolls of film, digital comes out to be cheaper when accounting for film + development costs.

A used Canon 5D MkII kit can be had for under $800 these days.
My interpretation is that the author isn't referring to people who suppress vocalization by choice but rather to people who can't enable vocalization in the first place.
Why do we need to choose one of monolith and microservices? What about simply "services"? Monolith doesn't have to be split into 50 microservices, it can be split to 3 services
Ever since the Widevine fiasco Netflix and Amazon have just worked out of the box on Linux.
Do you have any tricks on suppressing verbalization? I've found that it feels really wasteful when I realize that half my thoughts are just acting as a translator for the abstract side, instead of keeping it abstract until I get to something I need to verbalize.
Frequency illusion or Baader–Meinhof phenomenon

https://en.wikipedia.org/wiki/List_of_cognitive_biases#Frequ...
I wonder if this is related to (forgive the term) grammar-nazi-ism. I'm pretty sure I don't have any inner-monologue, at least the concept of it sounds weird to me. I'm also super picky about grammar: if someone writes "its cold out today" I have to re-read the sentence to try to understand it. I don't "hear" "it's cold" in my head, I parse "its (posessive) cold" which doesn't make any sense, and I have to go back and re-read it to fix the writer's error.
Once you get into 70mm film or 70mm IMAX, you're better off just leaving it alone and projecting it directly. I think 70mm could be scanned to 8K, and I'm not sure there's even a equivalent for 70mm IMAX yet.

That's why Nolan still screens his films with 70mm IMAX projectors. He might use digital for effects, but I believe he preserves the analog film in the final prints instead of using a digital intermediate.
Calcite is only a SQL parser and planner. It doesn't execute anything and is meant to be a component in a larger database system.

You need to use something like Spark, Presto or Drill if you want to run queries across different data sources.
> It's hard to imagine a programmer without medical training could be blamed.

Sure, but I would have expected that there would have been some perplexities by the actual doctors when they were presented these popups at each patient data access.
> Ten verifiers are automatically selected based on the mined block hash (as a random seed).

Congrats you've reinvented proof-of-work in an obfuscated form.

This paper repeats the errors of all previous proof of "useful work" papers from the past. I'd recommend that people actually take a look at discussions on bitcointalk, IRC channels like #bitcoin-wizards, and Bitcoin mailing lists to learn about what has already been figured out for all these things.