skysight-inc/HackerNews huggingface dataset:
Have a solid, standardized base/framework layer for your services, and a way to roll out changes to it that doesn’t involve manual work for each service. Migrations are the devil. You will have an extraordinarily difficult time evolving cross—cutting concerns like auth, tracing, metrics, profiling, health checking, RPC encoding, discovery and routing, secrets, etc. without it.

And definitely don’t start migrating stuff that matters until you have mature implementations and operations around all those things, and probably many others too.
Ask HN: Is Micro-Optimizing Your Resume Worth It?
Hello HN,

I've been wondering what the benefits (if any) of micro-optimizing your resume are, e.g. things like changing wording, adding strong action verbs, etc. etc.

Is it worth paying for some sort of professional service that does this, if friends/colleagues have already looked over it?

I imagine these things work better if an actual human reads it, but I've also heard that a lot of hiring these days uses automated services to screen resumes. Can anyone who works in recruiting share anything about that?

Is it all about keywords + gaming the system now? Should I be worried about these small things?
What's really going on here is that a remote procedure call (RPC) to a microservice or REST API is conceptually equivalent to calling a function in a library specified by an interface in a header file. There is an incredible amount of handwaving that obfuscates minutia around synchronous blocking vs asynchronous callbacks/promises/async-await but there is no reason why we can't convert from the distributed to local paradigm losslessly.

What I'm not seeing is any attempt to go in the opposite direction. A compiler should be able to look at ordinary code and slice it up into microservices automagically, converting the header interfaces to API specifications like OpenAPI/Swagger. We should literally be able to write a monolithic program in any functional or C-style imperative language and get a conversion to a bunch of lambda functions. If that doesn't work, then something is seriously wrong (probably having to do with determinism, like inadequate exception handling for timeouts, etc).

So frankly, the first day I saw lambdas, I was skeptical. I don't understand the point of writing all of the glue code by hand. Incidentally, I reached this same conclusion after manually building a large REST API around the JSON API standard just before GraphQL went mainstream and made a mockery of my efforts.

I think that the HTTP spec and things like separation of concerns serve a purpose for human readability. But we're well past the point where the gains made by the early internet are providing dividends in today's highly-interoperating stuff like Rust, Go and Node.js. Basically 90% of the work done today would be considered a waste of time (bike shedding and cargo culting) in the 1980s and 1990s. Just my two cents.
The hobbyist is the domain admin. What situation are you thinking of where they're not?

It's not a friendly technology for enterprises where it might take weeks to add a DNS record, maybe. But nor is much else.
This is so true. Also, I see tremendous value in not being reliant on any of the three major cloud providers. They all kinda seem untrustworthy in their own, unique way.

And also:

That JOIN really tied the tables together.
The coronavirus outbreak is now a global health emergency, WHO says
Jail for a year??? How about the rest of his pathetic life, human beings with this level of depravity do not belong in our society, period.
Web Development Trend Predictions for 2020 – Coding Infinite
Maybe try reading using a speed reading app. I use Comfort Reader [0]. When the words fly by really fast you have to stop sounding the words in your head or won't be able to read the full sentence. For me thinking is like writing and reading to myself so it helps.

[0] https://f-droid.org/en/packages/com.mschlauch.comfortreader/
> Quite the self-fulfilling prophecy there.

Microservices require your organization to have an engineering culture. I would be afraid of introducing them at, say, Home Depot where (I've heard) your average programmer doesn't even write tests.

If you have engineering talent within a small multiplicative factor of Google (say 0.5), then you can pull off Microservices at your org.

Edit: I'm being downvoted, but I don't think it's a dangerous assumption or point to make that it takes a certain amount of discipline and experience to implement microservices correctly. When you have that technical capacity and the project calls for it, the benefit is tremendous.
In general, it's often a good idea to munge pure probabilities to improve user experience. A very well known example is shuffle play. If you use pure probabilities you'll reliably play tracks back to back occasionally, frustrating users. A paradoxical quirk of true randomness is that it reliably throws out improbable events.
Yes, I'm sorry for the confusion. You use Clojure, I use Clojure, we're both commenting in a Clojure related post. I know that I'm "preaching for the choir", and stating the obvious. But to many other people scrolling through the comments, all that may not be obvious.
*if you're near colleges
Yoto audio player that kids control
Pair Programming Patterns
Debezium uses neither triggers nor NOTIFY. For Postgres, it uses one of several supported logical decoding plug-ins (pgoutput, decoderbufs, wal2json), which doesn't have any size limit and also allow to capture changes occuring while it isn't running by catching up with changes from the WAL from the point where it left off before.

Disclaimer: Debezium lead here
Same here, in fact at least 90% of my new music comes from online radio. 90% of that comes from dandelionradio.com. What other streaming radio stations would you recommend?
Interestingly, a friend of mine in a writing group recommended these to me as a way of organizing ideas for the plot of a novel, specifically the reasons that things happen in the story. They're not at all specific to business or any other field in their essentials.
Ask HN: Those who went from FAANG to working for a startup did you have regrets?
Hi all,

I had been working at a FAANG for a few years. I decided to leave that company and instead join a startup, I accepted the offer of a startup and am going to start there in March.

As my start date gets closer and closer, I am feeling a bit of anxiety and some kind of FOMO about leaving a big company for a startup.... mainly around money. The startup is offering me a good base salary which is about par with what I was making but obviously they can't offer me those RSUs that make the FAANG compensation skyrocket. (Yes I have been offered stock options but I am basically treating them as lottery tickets that may never pan out). I really love this startup and what they are doing but a part of me at the back of my head occasionally pops up saying "What are you doing idiot? Many people would have killed to be where you were and you left all that?".

Ofcourse many people esp on HN have made a similar move in the past. I would like to hear what your experiences were and if you ever regretted the decision. And more importantly how to stop the FOMO.
Would this same logic apply to other jobs? For example, do people who brew beer make the choice to kill others? If the drunk drivers add a level of indirection that prevent blame, then why doesn't the same happen with the doctors in this case?

Gun manufacturers? People who build cars that have a known higher fatality rate? People who build swimming pools (look up how many kids die to swimming pools a year)? People who sell unhealthy food? People who make tech/video games that result in less physical activity?
It's like a museum of problems. Waves of solutions that became problems after.

The culture of code generation before the culture of XML configuration.
>However, the same skilled operator should be able to calibrate her minilab in order to obtain decent looking b&w prints on color-based paper (RA4 process - used by Noritsu & Fuji).

It's actually a fairly good way to test if your lab sucks ass. B/W is not forgiving to poorly calibrated equipment or chain stores that are cheaping out on replenishment.

small nitpick: RA-4 is a Kodak process. The Noritsu minilab I ran used Kodak chemicals. Fujitsu labs typically use a 'compatible' version of their own that can't be called RA-4. While the two systems work, we always found C-41 Fujifilm looked inferior printed on the Kodak processes and vice-versa.
Agree here; Given the insane hours that people spend in FB, the feed becomes part of their reality and better nudges affect their outlook on the world, their spending decisions and their political directions.
If you already can't serve your requests from one DB, and you already want to factor out the analytics stuff, the long running background queries, modularize the spaghetti, scale the maintenance load, CI build + testing time, etc...

That's what SOA and microservices is supposed to solve.

At that scale you do reporting from a purpose-built service.

Allegedly.
As a Finn, this is great. I would just like to downgrade "strong support from Nazi Germany" just to support, and later a nuisance.

Initially Germany and Soviets made the Molotov–Ribbentrop Pact to divide the Europe. Nazis would get Poland and Soviets would get Finland etc. They were agreement at first, so Nazis stayed away for the Winter War (1939-1940) and Finland had to block attack on their own since most of the Europe was allied with Soviets or Nazis.

Later in the following Continuation War (1941-1944), Finland asked for Germany's support when they tried to reclaim some of the areas Soviets had previously taken, including the city of Vyborg. German sent some arsenal and troops from Norway. I think the number was 40,000 compared to 500,000 Finnish troops.

So I think it wasn't that much of a "strong support". Also the German troops didn't have the tactical skills or right equipment for long lasting forest/winter warfare, so they weren't that effective either. They were used to Blitzkrieging everything.

Most of the German troops were stationed in the Northern Finland and once the peace was found with Soviets, Finland had to fight the Germans to get them out of the country. Along the way, the German troops scorched everything they came across on their retreat to Norway.
> despite sending an email being an utterly trivial, long solved problem.

It is absolutely not. Even if you are not considering the whole spam thing.

Sending an email with the multitude of clients, MIME which is very complex in itself, network issues, message queuing, retries, unsubscription, bounces, providers feedback loops, rate limiting and what not is very hard.

If you add the whole spam folder + blacklists situation into consideration, sending emails becomes a more than painful thing you don't want to deal with.
An important part of the reward is American citizenship, which Americans already have, so for them, it's a high risk low reward field.

As America makes it harder to immigrate, and other countries are catching up in opportunity and quality of life, there should be fewer foreigners spend many years and sacrifices in pursuit of the green card.
I just go to Android settings and enable tethering over usb. Unfortunately, this creates another step every time I turn on the laptop, but I'm actually used to do it already. This "smartphone antenna" is being used for two years now.
Since when are the sciences "high risk, high reward" fields?

They seem like high risk (of not getting one of the few jobs available) for low reward (the jobs that do exist pay extremely poorly compared to writing webapps).
Yep, spending directly into unregulated insurance and healthcare companies who lobby for less regulation.
> but they won't be cooking up the next iPhone anytime soon.

It's funny you say this since Nokia, who are a Finnish company, were the globally dominant mobile phone company for years before the iPhone due to their innovations e.g. doing camera phones well. The 3310 is one of the best selling mobile phones ever. Yes they ultimately fell from that position, but to suggest Europe is some desert of mediocrity seems foolish.
> But you do not simply go and poke your reporting fingers into individual service databases. In a good microservice architecture you should not even be able to do that.

I agree. In a monolith architecture, though, you CAN do that (and many shops do.) That's where their pains come from when they migrate from monolith to microservice: development is easier, but reports are way, way harder.
I mean, I get what you are saying, but just somehow comparing a deep reason for drinking coffee (alertness/greater focus that apparently needs fixing) vs. heavily tripping on an acid trip (when you are experiencing hallucinations) is in bad taste.

When discussing these things, coffee should not even be mentioned in the same group as the heavy hitters, and just the fact that a lot of people posting here mentioned it makes me super suspicious about the whole thing. Just based on that alone. Regardless of whether it fits the actual, technical, dry definition of "mind altering" because it's adenosine-receptor antagonist.

I completely agree about alcohol. All alcoholics are trying to numb or drown the pain. And of those I've seen a lot. There are no exceptions, just like heavy drug users. Everything else is a lie - regardless of how deep the lie goes, or how organized it is, or how eloquent it sounds, or how popular it is at any given time. It's still a lie.

We should fix the reason they need those powerful drugs in the first place. And it seems like the best we can do is "lEgAlIzE" it, e.g. ignore the problem.

Why is nobody asking the question: why do you need alcohol/drugs/whatever in order to live another day and not jump off a building or something? How can we fix that? Is it fixable? How did it come to this? And so on..

What a society!

From "War on drugs", to "heh, fuck it, legalize everything and hope for the best" in less than a few decades. Jesus Christ, no wonder the propaganda is mixed up and lacking logic or consistency.
The NHS Digital Service Manual has been updated. It contains a lot of evidence-based information about building digital services for a large number of people.
I wonder if there's a connection between people with strong internal monologues and people who dislike audiobooks?

I _hate audiobooks_ as it's essentially a constant interruption of my own inner monologue and breaks my ability to visualize the world the author is painting. It also feels lazy to me, like by relenting I'm outsourcing my internal dialogue to a voice on my phone...
"they are convinced the DEM are going to confiscate/ban/etc"

This is a very legitimate and real fear for many. Remember Beto? "Hell yes we're going to take your AR-15's!"

That was met with overwhelming cheer and praise at the debate. Clearly many Democrats are not that vigorous, but you get the point...
Because the user has an easy choice. Monopolies are not a problem in themselves, it’s when that monopoly is leveraged to crush competitors out of the overall market.
I'll definitely put that on my list of arguments against proprietary software (although I'm aware that's not the primary issue).
Are you sure?

https://legalbeagle.com/8608294-difference-between-larceny-t...

> In many states, "theft" is an umbrella term that includes all different kinds of criminal taking. This is the case in New York. Under the New York Codes, theft can be any type of taking, like identity theft, theft of intellectual property, theft of services and theft of personal property
As a non Bay Area resident I can't say that compels me to think the app is any better. Seems like a lot of apps I use these days only work in the Bay Area.
> This means those occupying the "top" jobs have a much, much, much longer tenure than their predecessors.

"Much, much longer tenure" is a bit of a stretch. This is more about scarsity of certain jobs. We require a lot of 'on the ground' workers, e.g. software developers, and orders of magnitude fewer CEOs, CIOs, directors, etc.

It's similar to someone wanting to get into a management position. Once the position is filled, and the person is doing at the very least "slightly above awful" job, you won't hire a manager for that team for quite some time.
This looks amazing, I'm definitely going to use it to discover. If I would've known before writing the blog post, I would've added it :)
Sure, I've done this many times myself. The big caveat is that this only works if your data/update velocity is relatively low. I've seen many operational data models where the data warehouse would never be able to keep up with the operational data flow. Due to the rapidly increasing data intensity of business, there is a clear trend where this latter situation will eventually become the norm. I've already seen instances at multiple companies where Kafka-based data warehouse pipelines are being replaced with monolith architectures because the velocity of the operational system is too high.

For it to work, online OLAP write throughput needs to scale like operational databases. This is not the case in practice, so operational databases can scale to a point where the OLAP system can't keep up. The technical solution is to scale the operational system to absorb the extra workload created by the data warehousing applications, but current database architectures are not really designed for it so it isn't trivial to do.
> Depending on your location, pedestrian traffic, streets, street traffic, etc. It might be best for you to be on the sidewalk. … Maybe a town has a law saying you HAVE to bike on the road.

Depending on location indeed. The majority of US states still make it blanket illegal to bicycle on a sidewalk, codified into early highway laws. (It's also probable the last time those laws were effectively enforced was somewhere in the middle of the 20th Century.) There are states where it is illegal, but individual counties or cities (or strange in-betweens like townships) override their state laws and allow it. I don't know of any examples of the opposite where a state allows it, but individual towns forbid it, but I wouldn't be surprised.
Apple Maps got me lost 3 times in a row, put me at least 1 mile out of the way. Never used it again.
There are two big reasons to go to microservices (note that the exact definition of microservice can vary a lot).

1. Organizational streamlining. If the team working on the monolith becomes to large, then coordinating and pushing out changes quickly can become incredibly difficult. One rule of thumb I've heard is the two pizzas rule. If two pizzas can't feed the team working on a system, it's time to break up the system.

2. Horizontal scaling. If some components of your workflow require much more computing power than others, then it makes sense to break up your system to move computationally intensive tasks to their own services.

While there are lots of other decent reasons to break up a system, if you can't invoke at least one of the two above reasons, you may be shooting yourself in the foot. I think he's dead on when he points out that if you don't have engineering discipline in the monolith, then you won't have it in the microservices.
I can second this recommendation. Zig is really the best language I seen so far at attempting to be a direct replacement to C (Rust is good too, but maybe a bit too advanced.. feels more like a C++ replacement)

The compile time generics is kind of necessary to replace some of the stuff people use C preprocessor macros for. I think Zig is just taking the idea of having compile time evaluation of code to its natural conclusion, and it ends up being a lot cleaner than C with preprocessor magic.

The only thing they've added which isn't necessary for a "better C", is the async stuff they're working on now. But I think it's still a good idea.
The author doesn't mention what seems to me must be an important factor: modern American society is completely geared around safety, and against risk-taking.

Consider all the commercials about how safety is job #1, and so forth.

Or the fact that "drive safely" and "have a safe trip" seem to be pretty much the default conversation closers.

I'd much rather that people wish me a rich, fulfilling experience than curse me with boring safety.
These days I find tons of new music through https://daily.bandcamp.com/ . No blinders, you'll get hip-hop, then doom metal, then Philippines traditional music. I like this much more than recommendation engines that only make little circles around what you know.

And buying music on Bandcamp, musicians get a fairer share than they do on big platforms.
Watching Atomic Bombs Explode Was a Big Tourist Attraction in Las Vegas
I posted the same comment yesterday and for some reason got downvoted to oblivion. SSDs do not rely on bits being correct. Raw bit error rates in multi-level flash are generally over 1%. In other words if you read a 4K page you are guaranteed to get several wrong bits. The only reason a of it works at all is because of sophisticated error-correcting codes.
Well, I made some input to data protection agencies and got some feedback, so I'm rather happy on how things do progress.

That said I assume nearly all companies out there are not in compliance. To the point of the article, privacy policies are mostly not detailed enough and it will take some time before companies come into compliance.

This is the trade off between a strict PCI level compliancy policy with a strict checklist of things to do and the "vague" GDPR compliancy which was created that way to be independent of technology changing over time. The downside is it's not clear how to be really compliant and companies do the very minimum on what they think they get away with.

Also there are so many huge violations, that yes, the data protection agencies can't cover everything, so they start from the top with the companies that get the most complaints (1&1 getting a 10M EUR fine) or have the biggest missteps. I assume the Buchbinder fine will be much larger than the 1&1 fine, and it will for the first time proof to companies that they are still responsible when they hire an IT company to manage their data - which was the point of the parent.

Until the GDPR arrived data leaks were just "Ooopsy" moments to companies. This culture has festered for decades and it will take some time to change.

And my comment was to the parent "and the information they sell to the end user? Is it secretly there deep in some terms of service" where the GDPR requires you to tell people what you do with the data in terms that they understand it without obfuscating the message or hand weaving. I would have wished that companies need to open their process directory to the public though.
Are ideas getting harder to find? (2019) [pdf]
Writing a RISC-V OS in Rust: System Calls
Does it matter? How is a random person on the internet sufficiently qualified to define theft in a complex domain like digital copyright and intellectual property? You don't have to be a lawyer to be skeptical of what someone says online.
This is a terrible guide that ignores the best algorithmic recommendations that spotify provides, the "Related Artist" feature from the artist page. If you are a life long music explorer, why didn't you mention the last.fm Similar Artist feature? Concert reminder services like songkick are great for learning which bands are touring with your favorite artists, too, in addition to suggesting artists based on your current likes. This is low effort.
> 1) what if your data set is larger than you can practically handle in a single DB instance?

I have clients at 10TB-100TB in a single SQL Server. It ain't a fun place to be, but it's doable.
Thanks, that makes more sense. Still, I would be surprised if any continuity between the two requests became a factor.

Even if it did, it would show you as someone looking out for students at a community college, something which would likely elevate the importance of the request. A bunch of potentially snarky students mocking Apple Maps/Apple Inc. on social media seems like a force multiplier that would work in your favor.