Recent submissions

Comment · 1 year ago
As you’ve pointed out High SPL isn’t what breaks ribbons, it’s high SPL at low frequencies (ie wind/air moving frequencies, like those produced from a slamming wooden case lid.

Kick drums and bass guitar amps might not be a good match for a ribbon, but speech (with a pop filter) is fine.

Modern mics like those from Royer Labs can handle high SPL (cranked 100w guitar amp).

There are a few reasons why professionals still like ribbons for certain tasks: unlike condensers and dynamics, the resonant frequency of the ribbon is typically very low (20Hz), so you don’t get any peaks or artifacts when the source audio vibrates at the resonant frequency of the mic. Also, if you like the sound of your expensive mic preamplifier, the low output ribbon mics let you add gain/dirt/harmonic distortion which to some is pleasing to the ear.

Love that the op built his own, that’s really awesome.

Comment · 2 years ago
Comment · 3 years ago
Comment · 6 years ago
This is cool, and I applaud the author’s effort. For certain projects this is likely the right way to go.

However, another way to solve this which is safe to use when testing packages in parallel, and let’s you work against your exact database (driver/protocol/version etc)

Each package under test copies the database schema to a new database with the name “{package}_{uuid}”.

TestMain in each package is responsible for: -cleanup of old databases with the same prefix -create a new test database to work against.

Tests within a package are run sequentially, and are responsible for wiping the package’s test DB at the start of each test.

The pattern of “defer cleanup” is avoided in favor of deleting at the start to avoid the edge cases of crashing in the middle of a test run.

Comment · 6 years ago
It depends what you’re optimizing for.

One of the beautiful things about a static site is it’s ability to be served by object stores like S3 as your origin, and cached by a CDN.

From an operations standpoint, you are not responsible for maintaining much of anything, the performance is super fast, highly available, and relatively cheap (no dedicated servers, just paying for bandwidth and storage costs)

Contrast that with a docker container as your origin... it must be running (and that is your problem to ensure it is).

If you’re optimizing for developer convenience, your traffic is low or not mission critical, or maybe you have a globally distributed highly available k8s cluster and that is “the way” your company does all the things... sure why not

Comment · 7 years ago
Someone wants to lower their cdn bill, so they serve static things on cdn, and dynamic things from origin.
Comment · 7 years ago
Comment · 7 years ago
https://youtu.be/hZGqtmwboHU I defer to an expert.
Comment · 7 years ago
It’s a static site, so perhaps S3 (or any static cloud storage origin) and any CDN are a better comparison. What is the total power consumption of 1/nth of a large pool of cloud resources compared to the power draw of the router they are using in the office that is powered by the grid?

Regardless, I must say I love the “offline is ok”, “slow computing” (ala slow food), “get off my lawn”, “sustainable beats schfnacy” attitude. Nice one!

Comment · 9 years ago
Beme (CNN) | Platform Engineer (Golang) | NYC | ONSITE | https://beme.com

Beme is looking for a software engineer to join us in creating the next generation of apps for newshounds. We're building a new, independent, and wildly ambitious technology+media company bringing a wider range of perspectives to the news. We want to change who informs the world, and how. Our team is small and we are in our earliest stages, so your impact will be massive.

You will be developing product features and infrastructure at scale. If building a better, scalable foundation for the future of video and mobile technology is a challenge you want take on, we’d love to hear from you.

This position is based at Beme’s office in Tribeca, NYC.

What you'll do: - Architect application’s backend, creating scalable services, frameworks, and storage solutions using GoLang. - Have a voice in the entire product, but focus on the performant, server-side implementation of features. - Collaborate with the rest of our small, talented team of designers and engineers on a mobile-first application. Specifically Beme’s API and workers written in Golang, and hosted on AWS.

What we're looking for: - Prior experience with Go and AWS is not a prerequisite for a seasoned coder, but mastery of at least one statically typed language (C++, Java, Golang, etc), understanding of back-end scalability, performance, and/or automation is important. - The ability to comfortably straddle the line between back-end dev and dev/ops. - A practical view towards technology selection, striking the right balance between cutting-edge tools and more stable, rock-solid, traditional choices. - Eagerness to learn as well as teach. Our engineering team come from large scale platforms like Livestream, Google Search, and Tumblr; there are many learning opportunities in this role, but we also expect you can show us a new thing or two!

We have all the perks you might expect: catered lunches, unlimited snacks, relaxed time off and work from home policy, subsidized health, vision, and dental care, 401k program, and fun team outings. We also have a homemade arcade. Interested? Get in touch with us at [email protected].

Comment · 9 years ago
The right to be a customer of cloudflare (edit: cloudfront typo) is not really a "free internet" either. Personally, I value the right to not do business with nazis over the right to have hate speech backed by a CDN. No one is stopping you from starting your conservative YouTube on your own servers.
Comment · 9 years ago
I think it's a common argument for people who think biometrics are a bad idea for security.

IE. You can change your password, you can't change your thumb/face/biometric (easily).

At best, a fingerprint establishes identity, therefore it has more in common with a username, drivers license, social security number, etc. than it has in common with a password.

Comment · 9 years ago
This is a migration problem. A network of only self driving cars is effectively a more complex train without tracks. This does not require an AI, just a very reliable and coordinated state machine. A mixed set of AI and human drivers is much more complex. There is a possible future where towns, countries , certain highways, etc adapt to the needs/demands of humans such that the vehicles and rules of the road combined create the desired environment for autonomous vehicles to thrive. Everyone assumes technology will adapt to us, but history shows that humans do just as much if not more adapting (see: suburbs/highways, industrial revolution, tech addiction, tinder, uber, etc). In many cases this is powerful humans leveraging tech to bend the will and change lives of the masses. Not saying this or good or bad. Just saying... Futurists are generally wrong and overly optimistic (and/or just really good marketers).
Comment · 9 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton