zeptonaut22

Very helpful! May not save a ton of time, but as someone who performs this action 100 times per day, every little bit helps.

My personal plug for my Github WYSIWYG wishlist item: create an easy way to make images smaller (not full width). Everyone on our team gripes about the fact that, when posting screenshots (common in code review threads), they immediately bump up to full width, making portrait images look massive.

The only way to get around this is to paste the image, wait until it uploads, then replace the Markdown image tag ([text](url)) with <img src="url" width="400" />, which is incredibly annoying to do 15 times per day.

I have a close family member with sensorineural hearing loss to the extent that, at 60, he's unable to participate in conversation. It's dramatically impacted both his mental and physical health.

I'm not sure that less regulation around hearing aids would help him in the short term, but the options for people with severe hearing loss are remarkably bad and I'm willing to try just about anything to stimulate innovation in the space. I hope the FDA gets its act together and releases some draft guidelines for this new category of hearing aid.

I lived in Detroit next to a major corridor (Cass Ave) that got protected bike lanes going both ways and can confirm, it was _awesome_. The biggest differentiator I noticed is that the bar for how "hard core" of a biker you had to be to use the infrastructure went way down. You started to see many more families and women bike than you saw before.

The problem I repeatedly see with public opinion on both bike infrastructure and public transit is that both benefit and suffer from network effects.

When the network is already large, adding a new connection is amazing: the whole network gets access to that new node, and the new node gets access to the whole network.

When the network is tiny - as it is in most American cities - adding a new connection looks pitiful: the connection often looks like a "road to nowhere" that does nothing to solve the broader problem.

I think that one thing that can help this is communicating any improvements within the context of a broader plan, e.g. "This bike lane connects an additional 3,000 residents to the downtown business district. More importantly, it will serve as a central artery in connecting an additional 20,000 residents over the next 5 years."

God I am so dumb.

I've found a lot of lessons can be drawn from competitive games with tight feedback loops and applied outside of those domains. There's something to be learned from these areas where there are a whole bunch of people trying very hard to get good at something (e.g. chess, Rocket League), especially with regards to how to build a mindset around failure and how to review your mistakes.

The hard part in all of these is finding the right "hooks" in these pursuits that tend to be more obvious in competitive games. How do you "record your performance" when programming or holding meetings about business strategy? How do you review that recording after the fact? What criteria do you use to evaluate success and failure?

It's certainly not as easy to do this with "games" that lack a clear scope like startups, but I've found regularly reviewing your performance ("Did this meeting have a clear agenda before starting?") and building checklists for what practices lead to success is immensely helpful.

I mean... surely they can't be making money on this, right?!

A lot of offers I've seen like this (e.g. Wendy's free Frosty keychain fob) require buying something else with the free item, just to make this vaguely cost effective.

Bold move on Krispy Kreme's part.

Ironically, the founder of my company and I spent over an hour breaking apart this exact page yesterday talking about its UI. There are a lot of really good things that this page does right (shows tradeoffs between different tiers in a way that's not confusing at every tier), but... yikes. Sorry to hear about this.

As an early-stage CTO, I really appreciated this insight-from-the-future about how my role might change over time if we're ultimately successful.

One interesting difference with our company is that I hit the bottleneck of "I need to be doing more spec work and less engineering work" more quickly - possibly because we were relying on contractors who couldn't (or wouldn't) take on as much of that spec work themselves. I started to really feel this pain point at 3-4 other full-time engineers, where I was sort of trying to stay ahead of them and make sure that upcoming features were fully specc'ed and met the business needs as opposed to chipping in and coding myself.

I'm definitely tinted by my own experience, but it seems like 8-10 other engineers is a really late point to hit this bottleneck - did you have a PM that was also working to help plan the features to reduce this burden on you?

I'd love to hear an Airpods Max mic test here. This is the only meaningful info I could find on its microphone:

> With AirPods Max, voice calls and Siri commands are crisp and clear due to beam-forming microphones that block out ambient noise and focus on the user’s voice.

Mic quality has become a much higher priority for me and I think others since starting to work from home. In my opinion, high-quality voice audio helps greatly improve the quality of conversations over VC.