> Or just run 20 workers and let the OS handle async. OSes are pretty good at this. Async is pretty hard to reason about.
def slow_sync_view(request):
# these requests won't be executed in parallel;
# async version could eliminate this extra latency
foo = requests.get('https://www.google.com/humans.txt').text
bar = requests.get('https://checkip.amazonaws.com').text
return HttpResponse(f'{foo}\n{bar}')
I think you are being down voted because a straight port of this code to async would still run one request after the other.
You would have to queue one task for each request in the event loop and then await for them both to gain some parallelism in the I/O section of the code.
> As long as The Internet is available to Russians, people will find a way around Roskomnadzor blocks. All it takes is a single 100Mb VPS to provide VPN connection for 10-20 people.
The things is, there is no way to buy a $5 VPS/VPN now in Russia "thanks" to Visa / Mastercard actions.
The part of pg's comments that relates to your comments is this part:
"Saying that an author lacks the authority to write about a topic is a variant of ad hominem—and a particularly useless sort, because good ideas often come from outsiders. The question is whether the author is correct or not. If his lack of authority caused him to make mistakes, point those out. And if it didn't, it's not a problem."
But in general, Paul Graham isn't saying anything that is novel to this site's comment guidelines:
Be kind. Don't be snarky. Have curious conversation; don't cross-examine. Please don't fulminate. Please don't sneer, including at the rest of the community.
Comments should get more thoughtful and substantive, not less, as a topic gets more divisive.
"Don't be a dick, because plenty of people are smarter than you, and even people who are not smarter than you can come up with really good ideas and perspectives."
> Redis Enterprise is a robust in-memory database platform built by the people who develop open source Redis. It maintains the simplicity and high performance of Redis, while adding many enterprise-grade capabilities, such as linear scaling to hundreds of millions of operations per second, Active-Active geo-replication with local latency, Redis on Flash to tier data across dynamic and persistent memory and solid-state disk (SSD) to reduce total cost of ownership, and five-nines (99.999%) uptime based on built-in durability and single-digit-seconds failover. Redis Enterprise supports many data modeling methods with modules such as RediSearch, RedisJSON, RedisGraph, RedisTimeSeries, RedisBloom, and RedisAI, and allows operations to be executed across and between modules and core Redis functionality using RedisGears, a serverless engine that runs across shards and nodes of Redis Enterprise cluster. All this while keeping database latency under one millisecond, so your application can respond instantaneously. Learn how to implement the best in-memory database: Redis Enterprise.
Probably won't be able to refuse it outright. Though It's unlikely that an external contributor would be able to bring these features in easily. Redis Labs has a lot of people working on their enterprise offering.
Redis has sentinel and scaling features, as well as established patterns. Enterprises are likely willing to pay for experience of doing it right, reliably.
I filter based on experience. Previous jobs, roles, projects. Degree is a weak predictor and I consider it mostly for candidates with less than 3 years of experience.
I guess my question transitions over to: If a candidate has less than 3 years experience and no degree, where does that fall on your radar? Genuinely curious as it falls into the "need experience to get experience" job meme many people find initially.
Speaking from my perspective as a prolific FAANG interviewer: Listing whatever experience you can (high-school jobs, sites created for friends, college jobs) alongside interesting personal projects is a huge leg up for getting through recruiting. If you're early in your career, find a few small-time jobs somewhere in tech that'll hire you, and learn as much as you can as fast as you can. MSPs are desperate for people with a little coding background. They'll chew you up and spit you out with long hours and terrible pay, but they're a great place to cut your teeth on getting things done.
Once a candidate gets to me as an interviewer, I'm mostly looking at a resume for what topics I should ask about, both things that you're comfortable in, and things that you're not. If you have personal projects, I'll ask pertinent questions about them, and often I've learned some very interesting insights from the personal projects of candidates.
In my time interviewing, I've hired people without degrees as senior engineers and I've rejected people with doctorates in computer science as junior support engineers. Turns out, degrees are a mediocre predictor at best of ability to do a job, and practical experience is 99% of the time more impactful than a piece of paper.
> Speaking from my perspective as a prolific FAANG interviewer
That's interesting, and somewhat rankling - as both times I interviewed at the G in FAANG, not a single interviewer gave a nickel about any of my experience, or projects I had worked on.
It's such a joke that the keys to a golden line on your resume and a giant salary are gated by the luck of which 7 people get picked to grill you that day, how busy they currently are, and what their pet question is.
If a candidate has less than 3 years of experience AND he has nothing to show AND he has no degree... he will not pass the filter.
Moreover, I'm not really interested in "years of experience". Previous titles don't really matter, too.
What does matter for junior and middle developers: personal projects, specific products or features developed by them or their team, accounts on Upwork, GitHub or StackOverflow, recommendations from other people, a personal website or a blog.
We are talking about the initial screening filter, so _anything_ proving you are a real developer is fine.
