skysight-inc/HackerNews huggingface dataset:
I don’t think an organized group like Antifa promoting “by any means necessary” and getting tacit approval from the main stream left is comparable to one (universally condemned) deranged lunatic, a bunch of keyboard warriors, and something stupid Trump said once.

There aren’t right leaning groups out there organizing violent protests at college campuses trying to prevent left leaning speakers from being heard.
They're both tools used to build interactive websites.

The parent didn't understand why developers would be happy that React got the greenlight. My response was that React (and Vue) really is a much better tool for building interactive websites than many older tools like jQuery.
I’ve wasted $250 a month in SaaS costs in the last 5 months! This is how I fixed it.

Hey guys, I’m King an undergrad from Stanford. Over the last couple of years, I’ve been running multiple startups and an outsourcing dev shop based in the Philippines. I’ve been repeatedly fucked by bloating SaaS expenses — especially when it comes to old projects (with server and domain allocation) or old employees who have transitioned out (but are still on Adobe / Sketch / etc ). With multiple personal credit cards of co-founders used on different line items, it gets hard to reimburse each other. It gets worse when handling multiple projects! So… Fuck SaaS!

Not that we hate SaaS products, we actually love them a lot! That’s why we use them all the time. Over the weekend, me and my buddy, Jig, who was a PM for Growth at a Y-Combinator Start up, hacked together an enterprise subscription manager to identify unused subscriptions, organize expenditure, and save your runway!

We’re running the beta right now and if you’d like to save money now, comment “Fuck SaaS! with your e-mail and country!”
You may be filtering your pipeline according to the wrong criteria, and rejecting candidates strong in algorithms but weak(er) in JS specific or framework-specific stuff at a stage that's too early. Or those candidates may be unicorns -- usually the early-career people who like thinking about recursion don't jump into applying to frontend roles, which they see (wrongly IMO) as a lower tech, design-oriented kind of role.

If it's an entry-level role and you don't have good signals for the steps prior to the interview, maybe consider a pre-interview assignment that includes some asynchronous concepts, and administer it much earlier in the pipeline. That's a slightly lesser investment but should be as good a signal.

If it's a senior role, then your questions are way too easy, but also you should go on Linkedin and ask individual people with good experience to apply, that's what everyone else is doing.

Edited to add: Well, I saw in your other answers that you are filtering candidates based on "really wanting" the job very early in the process... I work in a region that is not the hottest job market wise and even here no one could afford to do this. Software devs are just too in demand... you're going to get pretty mercenary candidates unless you go with personal referrals. If the non-technical aspects of the candidates are more important, which with your ordering of the hiring pipeline it sounds like they are, then you need to consider hiring fewer people and growing less fast, pr hiring for fit first and training the recursion skills later.
I want to say no, because I don't especially enjoy or excel at it. But I don't have a strong sense of better alternatives, either.
It's refreshing to read an article which challenges common wisdom.

I've endured a lot of suffering at the hands of the microservices fan club. It's good to see reason finally prevail over rhetoric.

It would have been nice if people had written articles like this 2 years ago but unfortunately, people with such good reasoning abilities would probably not have been able to find work back then.

Software development rhetoric is like religion. If you're not on board you will be burned at the stake.

So many times during technical discussions, I had to keep my mouth shut in the name of self-preservation.
My view is that microservives is more of a workaround to company culctures and silos than a software solution. At least in most cases.
When you use the cloud, you're immediately at the mercy of three entities:

The provider, who can ban you on their whim with no practical recourse.

The ISPs between yourself and your provider, which is a real problem when ISPs have such lax requirements about "what is broadband"; when they have huge ambitions for making money off your traffic.

The browser vendors, who break backwards compatibility like it's going out of style. This goes back to the provider too, who like to dictate which browser you must use to access their services.

That's a lot of links in a fragile chain just to have access to basic computer functionality.
> along with not following the basic rule of services "put together first, split later".

Agreed. I treat services like an amoeba. Let your monolith grow until you see the obvious split points. The first one I typically see is authentication, but YMMV.

Notice I also do not say 'microservices'. I don't care about micro as much as functional grouping.
> I don't know anyone who perceives those two products as comparable for daily usage.

Allow me to introduce you to me :-) I presumably have different usage patterns that you do.

I've got both an iPad Pro 10.5 and a Surface Pro and keyboards and styli for both of them. With the exception of software that is available for one and not the other, they are pretty much interchangeable as a daily driver with two caveats.

1) If I am using my Surface on the road I have to tether it through my phone for internet connectivity.

2) If I am using the iPad have to SSH into a Linux machine to get a Linux userland prompt.

I use Dropbox on both of them to access shared files.

The big differentiator for me, is that on Surface when I plug in the dock connector it lights up my dual 2K monitor/keyboard/mouse setup and it is just like being on a desktop machine. Not something I can do with the iPad.

The other aspect that probably makes my setup unique is that I'm not developing code for either the iPad or the Surface, just using them as essentially terminals to get to the systems where I am writing the code.
All of my analogies are intended to be similar situations, not identical situations. It's inaccurate to say that they don't apply because they aren't identical.

Yes, there are regulations and consequences for mishandling food and patient data but I still have no personal way to ensure that these practices are followed. In the end, you have to trust the entity that you are doing business with. The same applies to 1Password.
It's also worth pointing out that if your Lambda is in a VPC its cold start time can be over 10s.
Vulnerability scans on Kubernetes
>A Type IV "metal" tape with Dolby S and recorded using HX-Pro can sound seriously good

We had one of those 3 head tape decks growing up. The one we had a yamaha with dolby hx-pro,b,c and dbx. We used to tape cds and try to a/b compare them.

The 3 heads were erase, record and play, which meant you could monitor the recording as it was happening and adjust levels and such. (and results in the weird behavior of the "tape monitor" button on amplifiers).

With Cr2 tapes (not as good as metal, better than normal) and dbx noise reduction it was really hard to tell the difference between cds and tapes.

The quiet parts on tape clearly had hiss without the noise reduction and the dbx noise reduction made the tape sound like crap in your walkman, so we just used dolby C most of the time. The walkman was always the weak link, without cleaning those rubber rollers you could get some weird speed ups and slow downs on playback ("tilt a whirl effect").
It‘s concerned with publishing, because that‘s where it originally comes from, centuries ago. People distributing newspapers, and earlier, flyers and pamphlets needed and still need to name a responsible person.

This person sometimes gets called ironically „Sitzredakteur“. „Sitting editor“. Not because he is currently the editor, as in „sitting president“, but because he‘s the one who is going to sit in prison.
It's not quite that straightforward. Lambda is more expensive per cycle if you are capable of keeping an instance fully utilized and getting every cycle out of that machine. After all if your Node.js or Go code takes say 20ms per request and can handle many concurrent requests you can squeeze a LOT of requests per second from a single instance.

But many workloads don't have that high of a request volume and can't actually make full use of an instance. If you have a small API or service that gets one or two requests every few seconds then paying for a 100ms chunk of Lambda execution time every couple seconds is going to be much cheaper than reserving an entire instance and then not being able to get good utilization out of it.

The tipping point is whether or not you have enough workload volume to keep an instance busy at all times. So for example password hashing in the article above. Because password hashing is deliberately CPU intensive it is very easy to keep an EC2 instance busy with even a low request volume. For a good hashing algorithm with lots of rounds its not uncommon to only get 10 authentications per second per core, because the algorithm is deliberately designed to be CPU heavy. So if you process more than 10 auths/sec then its probably cheaper to put the workload in a container that runs on an instance because you can keep that instance busy.

But if the same service is only handling one or two password hashes every minute, then you can save money by only paying for 100ms increments when an auth request arrives, and stop paying when there is nothing to do.
I'll be the guy who ruins it by asking a clarifying question. If I can do it all over, does that mean, that I keep the wide mental aperture I have forced open over the past 20 years, by learning how people work, learning how general process works, folding probable outcomes and recognizing corner cases, into my personal toolkit? And forget the software engineering? I'd have to go with a hell no. I'd be someone else.

If I lost everything except the notion that I kinda love this stuff? Yeah, I'm sure I would.

Do I go back to 1998 or do I start over now? It's becoming more obvious to me that the closer you can warp back to about 1950 for these start-over fantasies, the better a time you're going to have. I would be in a full panic if I had to start over right now, a fresh 22 year old undergrad with a 2018 degree in software. Yikes. Maybe that's just a me-getting-old thing peeking through. I sure hope it is. And am worried it's not, for younger folks on here.
I thought this part below was interesting. We know that the most selective schools weigh non-academic factors, and many well-off parents are not willing to pay $75/K for a "name" school, so it's reasonable to replace a school filter with a cognitive test.

"Most of the people Vista hires score highly on the cognitive test. Often they are young employees with less-impressive credentials or experience. These HPELs, as they are known, may have gone to state universities and be willing to do a job for $75,000 that an Ivy League graduate in a high-cost market would demand twice as much for."
Ask HN: What do you work harder at than most people?
What do you work harder at than most people? That people either do or don't know about?

What is it, and what do you do to work harder than anyone else? Why?
Doesn't this defeat the whole point of an interview, to find out what the person knows/can do/can understand instead of reading some website that tells them what to say?
True. When I was starting out, I was tasked with editing the Wikipedia page of one of our clients to add more information. Wasn't anything sinister; the company just wanted to ensure the page had up to date information.

When I ventured to the 'Talk' page, I was surprised to see so many edits and comments from editors.

This was for a little known company in a niche field with little traffic or chance to profit. Yet the editors were as diligent as ever.
I believe some banks have 2FA. My bank's app will require me to setup SMS verification by October. A little late, but better than never I guess
> Segment's service is roughly the size of one microservice on our end.

This gave me a good chuckle. Dunning–Kruger in full effect.
Not really. For example, it's easier to mock a microservice, than a module, for testing purposes. Let's say you have component A and component B, A depends on B (dependency implemented via runtime sync or async call), B is computationally intensive or has certain requirements on resources that make it harder or impossible to test on developer's machine. You may want to test only A: with monolithic architecture you'll have to produce another build of the application, that contains mock of B (or you need something like OSGi for runtime module discovery). When both components are implemented as microservices, you can start a container with mock of B instead of real B.
React/Vue + Hot Reload is a game changer. It's very productive and enjoyable to develop and iterate with these tools.

Granted, it's absolutely true they're often used in places they probably shouldn't be and can easily result in JS bloat. When working on the frontend it's tempting to use them for everything because of how comparatively fast/easy development is. Ultimately the tradeoffs should be considered on a case by case basis.
>and if Trump keeps snuggling up to Putin, it wouldn't surprise me at all if Germany, Italy and Spain started seeing the same thing.

Can't they just snuggle up to their close neighbor and EU/NATO partner France? France is a nuclear power too, don't forget. UK is one too, and still part of NATO.
I know, but now, what controls credentials and instance bootstraping for that?

it will always be the "not invented here" type of deal. you can always add something else to bootstrap it further. I can't think of a use case where lemur/athenz/other x509 brokers adds real value (or convenience) versus a well defined process and bare bones things like etcd and such.

Thinking you can bypass the well defined process step is just an illusion. what most CTOs do is offload that to the few devops handling their abstraction. when that team grows too much, add another layer on top with a smaller team.
Right, but the thing that makes Linux actually useful isn't really the kernel is it? I would say what makes it useful is all the various small, targeted programs (some might call them microservices) it lets you interact with to solve real world problems.

If Linux tried to be an entire computing system all in one code base, (sed, vim, grep, top, etc., etc.) what do you think that would look like code base/maintainability wise? Sounds like a nightmare to me.
Agreed. "Micro" is a terribly defined term, and it sounds like this team went absolutely nuts in one direction. (And then in response to their problems, went as far back as possible to a single monolith.) This suggests a bit of a lack of nuance in their decision making process to me.

I'm not interested in figuring out exactly what the right marketing term for it is, but I've had good experiences with teams of 6-10 engineers owning something like 2-5 services with a larger ecosystem of dozens to hundreds of services. Of course, I've been working at very large companies with extremely high traffic for several years now, so my experience is skewed in that direction.

If I had three engineers on my team I'd be unlikely to end up with more than a small handful of services. Half the benefit of splitting up your services has to do with keeping your independent teams actually independent -- if it's just one team then that isn't a problem in the first place.
A. Using a quote by a writer who has been dead for 50 years to inform your view on people's attitudes is probably not going to serve you well.

B. Also, I noticed that you spell check as 'cheque'. Thank you for condescending to us poor American rubes, we always appreciate it!
It's not just the life sciences. Time is generally undervalued in physics, too.

The most-successful scientists, though, have an excellent perception of the value of time. They may not perceive it that way explicitly, but their choices of what is and is not worth working on amount to valuing time.
The upside is that we can still edit them all anytime :)
I'm a laser physicist, so I think exclusively in terms of lasers and mirrors, but I get your point.
How does that compare to the cost of cloudflare workers?
I have both Safari and Chrome on the iPad Pro. For what I'm doing both work well, fewer web sites have issues with Chrome than they do with Safari. Where they differ greatly is in their ability to integrate with other applications on the iPad. For example a very common workflow for me is to gather PDF datasheets/docs and feed them into iBooks.
Microservices aren't some magic bullet for scaling. If anything, they conform to Conway's Law [1]. I'd agree, though, if a single engineer is singularly responsible for 2+ microservices that are only supporting a single product...you're doing it wrong.

[1] https://en.wikipedia.org/wiki/Conway%27s_law
I am sorry but you are very wrong.

the description for the only one on fdroid even says so.
Or buy a semi-autonomous truck that can be used in convoy mode - one driver in the lead, two trucks behind following. Once it gets to a city they all get drivers to navigate to the depot. This is already a feature of the Tesla Semi.
Or, you know, you could just admit that the wording was poorly chosen and caused a lot misunderstandings, and that Musk wasn't officially asked for help, but that a random stranger on Twitter asked him to do something.
Jekyll has gotten pretty fast too, especially if you enable incremental building.
Microservices are an organizational and design choice that is intended to mirror the structure of the teams or engineers, the actual human beings doing this stuff.

It seems like Segment didn’t really understand this at all, and instead decided to have seemingly arbitrary and rediculous service boundaries that had no relationship to the real world.

See also people who create poor abstractions in their code and other sources of technical debt.

This isn’t an article about how microservices architecture is somehow bad, it’s an article about how bad Segment’s engineering team is. You can make the same argument for anything. At the end of the day some architecture or process or programming language or tech can’t replace real thinking about your problem and correct application.
How light, how cheap, and how strong, though? Seems like an incomplete theorem.
ohv has 3€ a month vps that will be largely enough for small communities, and probably average ones.
Interesting perspective. I don't see much difference between building websites, physics models, game dev, and data science.

Computers certainly have wide ranging applications but at the end of the day, programming all of those tasks is pretty similar.
Yeah, and you can't rotate your fingerprints or retinal scans.
put a date on this old article title! [2016]
I believe the most common reason some people don't see the utility of cryptocurrency is that they have a real or perceived vested interest in the status quo around money not being disturbed.

It is often the case that:

Securities lawyers and traditional venture capitalists don't want a world where regulatory agencies and traditional venture capital can be routed around.

Those in financial law enforcement don't want the trend toward total financial surveillence, euphemistically called instituting anti-money-laundering controls, reversed.

More generally, those with a major economic or ideological investment in government-funded programs don't want people to have financial privacy that makes enforcement of the income tax more difficult, or to see an alternative to central bank issued currency, which gives governments the power of seignoriage, gain traction.

The utility of cryptocurrency is clear: sending value from point A to point B electronically without depending on an intermediary that can extract rent or surveil/censor the transaction.
I’ve been running some on my side projects just using a docker containers on digital ocean and t1.micros and apparently that was the most cost-effective way to run it ?
The decline of practical enforceability in some patent areas has created adverse incentives with respect to how you use the patent system, leading to much of the mess you see today. As a practical consequence, less R&D is being patented since disclosure is not adequately protected, and patents are instead used strategically to increase the cost of reverse engineering a trade secret. This leads to the large number of patents designed with enough specificity to deny competitors access to technology without enough critical implementation detail to replicate the technology from said patent.

Even trade secrets often only buy you a small amount of time these days before a competitor reverse engineers your technology, so increasingly elaborate (and often futile) measures are being taken to extract an advantage from R&D that justifies the investment in the first place before your competitors use it against you.

Especially in computer science, as much as many people complain about algorithm patents, an enormous amount of state-of-the-art research is being solely done as trade secrets now and will never be patented or published. I suspect many people that strongly favor banning computer science patents would not be happy with the reality that this drives advanced computer science research to never be published at all. There is no longer a viable path for recovering investment in computer science research that involves publishing it, which should be cause for concern. (People that want to monitor the advancement of AI tech should find this reality particularly distressing, as it severely hampers their efforts.)
As an Eastern European I would definitely entertain the idea that totalitarianism is not entirely wrong. IMO the world needs politicians with stronger will who are less obsessed by next elections and are religiously persecuting criminals and opportunists... however the politicians are parts of these criminals so yeah, welcome to 21st century.

In any case, regulations have proven time and again to mean absolutely nothing unless enforced very strictly and with a very heavy hand (flat percents of the offender's gross income, and I mean from 20% and up, not some petty 1-2%). But that won't happen -- lobbies, rings of companies, "anonymous" donations, things like that... the status quo is too deeply entrenched. But we can dream, right?
Building the Google Photos Web UI