Open that, and create a new aggregate device with just the system microphone. Then set that as the default microphone. And now when applications access the microphone for whatever reason, your bluetooth headphones don't switch profile and keep on using the aggregate microphone device.
It's one of those obscure hacks that should just be default behavior. Why would I want to switch to a low quality audio codec when I have a perfectly good microphone in the laptop? Answer: I don't want to. Never. Loads of people use expensive headsets and they all sound terrible when they take their calls. It's not necessary.
There was a point in the history of front-end dev when they all started calling themselves "rock stars" and became convinced that they are the future of software development. The SPA trend gave frontend devs an excuse to write unmaintainable code, gave designers an excuse to call themselves software developers, and then they all told the world they are doing "full-stack development" when Node appeared. Meanwhile they never bothered to learn pre-SPA UI, UX, or content design principles.
Thing is, working on front end never gives you a chance to work on problems that backend has to deal with. I never let JS guys work on backend code, because they are lost if they cannot find a module online that does what they are asked to do, or is missing half of the features from the spec it promised to implement (always the hard ones). We then have to pick up the mess and rewrite it in Python or Golang, which is wast of time and money. I once quit when when the client showed me the Python code written by a JS dev. My devs refused to touch that shit and we went to work for another client.
It helps decipher JS error stack traces by applying source maps to them. In my previous company, we struggled to configure Sentry to work with source maps, and every error message was cryptic due to minification. First, I created a little command line utility and later made it a web app.
https://github.com/rmuratov/hledger-tools
Just some charts to summarize my monthly finance activity based on hldger journal.
I don't mind the disallowing name shadowing, but I really, really hate (I mean that) websites that are just good ol' text and the odd picture that require Javascript. The excuse of "we used React, it's easy" seems odd given that HTML is much easier.
The idea is to approach content as data-first, with tools on top, and be at ease with plans to Walk-Out when needed.
Besides the article in discussion, here are a few inspirations for plain-text as the defaults.
- The writing of our very own Obsidian’s CEO, Steph Ango at https://stephango.com @kepano on HN.
- A Plain Text Personal Organizer, https://danlucraft.com/blog/2008/04/plain-text-organizer/
- A template to organise life in plain text, https://github.com/jukil/plain-text-life
- Achieve a text-only work-flow, http://donlelek.github.io/2015-03-09-text-only-workflow/
- Note Taking, Writing and Life Organization Using Plain Text Files, http://www.markwk.com/plain-text-life.html
- Plain Text Journaling System, https://georgecoghill.wordpress.com/plain-text/
- Plain Text Project, https://plaintextproject.online/
- PlainText Productivity, http://plaintext-productivity.net/
- The Plain Text Life: Note Taking, Writing and Life Organization Using Plain Text Files, http://www.markwk.com/plain-text-life.html
- Use plain text email, https://useplaintext.email/
- Writing Plain Text by Derek Sivers, https://sive.rs/plaintext