vicda

The Feynman book, while being quite good, is not a good fit for this list.

> I'm also curious how one builds up strong manufacturing skills safely?

While getting mentored at jobs that takes OSHA violations seriously? Most youtube maker channels are full of comments complaining about how lacking the hosts are in their safety.

You say that like they have heard of the acronym CRDT before.

Don't let the curse of knowledge be an excuse to be rude to people.

There's always the sweet spot, but like almost everything involved with predicting the future you rarely know what that is. So you take an educated guess and do what feels right, and the people you know and the media you consume paint that normal for you. Hopefully you don't have a warped perception, because you won't know under after the damage is done.

Maybe it's a reference to the compiler or the plethora of internal and paid tools out there in the enterprise world.

With no preexisting trust? Ask them to give their honest feedback as a favor. Make it into a cooperative discussion so they don't feel like they're the only one criticizing the subject. You need to prove to them that it is safe to discuss those thing with you first, you being by default direct can give some people the opposite impression.

The book The Culture Map goes through that and lot of other "Culture X is more Y than Z" in a readable level of detail.

When there's only one way to do it, everyone is or soon will be accustomed to it.

I'm not a fan, but it fits with google's goal when creating the language.

Imagine using python without pip or conda. That's what using excel vba feels like.

Lightweight sandboxed applications in the browser. No admin password needed since there's nothing to install.

Sure it may be bloated overkill for something that could have just been a plain text file, but it is nice to have real time and interactive visualizations.

Plus it is nice to have the choice to use mobile websites instead of using the access hungry native apps.

We don't read documentation to entertained, but to solve problems. How searchable your text is extremely important.

It was a known limitation before the purchase. But, It was consistent. All the keystrokes went in in order and you get used to the new framerate really quickly.

Your issue (which I agree is mildly annoying) is about inconsistency.

I did this. Latency sucks but that didn't matter for text editing.

But the drivers sucked and the screen was too small and you want to have a white background text editor just for the eink screen. Switch that to the wrong screen and you're suddenly blinded.

Was fun, but I wouldn't recommend it. Making everything dark mode is easier, or keeping screen brightness super low is the easier option.

Ok boss. We'll keep a cache of the best known route for the most common queries or fallback onto the existing algo.

10. When the donation gives you favors in return.

This is what instantly came to mind for me. Making a station faster generally only matters when it's a bottleneck.

It doesn't matter how optimized your computations are if you're spending the whole time waiting in IO. And don't forget that the program is generally just a piece of a larger process.

"If you want anything done, ask a busy man to do it." They don't have the time to fuss about perfection. They have to do the most with the least or not do it at all.

I've always approached this thought from the perspective of "how much time can I spend" instead of energy levels. Thinking about it, it's likely a mixture of the two. Thanks for widening my perspective.

Yeah, it shocked me the first time I memorized a deck of cards with a memory palace. Plus, imagine how well trained muscle memories became since methods would have hardly changed from generations before.

That's why there are many products with a test client at inception. You localize the initial issues (which would cause those bad first impressions) to a single client who you can spend the extra time to build up good faith with. Once you've built up steam you can expand to more clientele with bolstered confidence.

Though, one problem is that you risk over prioritizing client-specific edge cases.

In any case, an idea without action is worthless.

Yes, but you write a short function/lambda for connecting them. Just like how you have sed/awk, or the many required flags to make any non-trivial operation "just work".

You're not free from the need to specify how to parse the strings just because your whole human readable system is stringly typed.

Coming from Visual Studio, my impression is that a proper IDE should do all those things you mentioned. (minus annotations, but that's what comments are for)

I am curious as to why you would want a read-only IDE though. I'd like to see what would be different if the IDE's focus was for reading a large code base rather than writing one.

This was the hardest thing to figure out. I have a program just to ensure I'm sending the arguments that I think I am.

Yeah, it's a mixture of Perl and Bash with sudden C# calls interspersed.

Also, I'd imagine it's a way for them to fight back against providers capping download speeds to Netflix's content.

I work with one of the 60% keyboards. The biggest plus for me is having the navigation keys within the home row, but the biggest negative is having to press fn to use the function keys. I don't know if I'd go so far to call it idiocy though.

But when that pitch is being interpreted by another program wouldn't that make the most sense?

I would imagine this gets harder as you age, get more set in your ways, the higher on the career ladder you've climbed, and/or as your required salary increases.

Searching on mobile is tedious in compared to using a keyboard. I'd be more inclined to use the voice search if it wasn't socially awkward.

Google has other avenues to work. This problem is more so a service designed for desktop web experience isn't as easily usable on mobile.