60 karma · joined July 11, 2018
Opinions are my own and not the views of my employer.
With software, it's probably a matter of prioritization, why invest into explaining errors when you can work on preventing them? Not that this error prevention always works out, but still.
> But because neither audio server is interested in implementing functions for embedded displays, neither power supply daemon is interested in implementing audio routing, encoding, decoding and playing functionality, neither input layer software is going to process battery and power relayed functionality and also it is not up to the modem software to register input devices into kernel and process button press events, the only reasonable solution for this problem is to provide another software which would own HSP/HFP AT modem connection for remote Bluetooth devices and would forward commands, signals and requests to appropriate application.
> The email client strips out the text/x-amp-html part of the MIME tree when a user replies to or forwards an AMP email message. This is why it is important that an email provide alternative content in the HTML part.
Open in what sense? For example, there's no open standard (to the best of my knowledge) for the HTML used in emails right now and different email clients render HTML in emails differently.
On the other hand, the protocol itself is standardized, but AMP is not working on protocol level.
What makes you think input won't be heard?
I'm aware it's a security risk, but I also keep nothing of value on that machine nowadays.
IIRC, she's been there since 2012. Her role in Google [Cloud] came much after.
Have you considered adding it to the FAQ? I feel this is a thing many are curious about.
They gave a very thorough overview of the (many, many) challenges involved with "kickstarting" a hardware product - and how they overcame them (from issues with banks to FFC and CE certification). It's a great source of knowledge for anyone who considers doing the same.
Laci also did an AMA on Reddit: https://www.reddit.com/r/IAmA/comments/3tkyme/iama_l%C3%A1sz...
That said, after learning to touch type, I found some layout decisions surprisingly intuitive.
Most notably, it turned out that having arrow keys on my home row is a great idea. Only after I got used to that did I realize how annoying it is to leave the home row on a normal keyboard.
Still not sold on escape and fn keys. I believe that it would've been better if had an extra row for those, but I might learn to appreciate that too in the future.
There are minimal frameworks, containing e.g. just a grid. People often use one of these and then build their own components.
There are also component libraries. While they ideally aren't as opinionated as you describe (forcing you to use a specific color scheme), they still impose on you a certain philosophy and require you to use the whole library, not just individual components. Unlike e.g. Node.js where you can easily stitch together different things, UI requires consistency, both in terms of how it looks and how it's coded. Mixing different sets of components would not just be a nightmare in terms of appearance, but maintenance as well.
---
All that said, you might like [Basscss](http://basscss.com). It's one of the least opinionated CSS frameworks, giving you just the "tools" part, not getting into appearance of your website at all.
How so? I see nothing in my day-to-day life that's different because of Bitcoin.
So, it sounds like it only works if nobody uses it.
Sure, you can say we now have <insert name here> which is like Bitcoin, but solves this problem. This, however, is similar to pointing out there are credit cards with lower fees than what you mentioned (e.g. national ones), it's just the major ones that are expensive.
This sounds like it seriously underestimates just how much influence a government can have.
First and foremost, they can make it illegal. This would immediately make the fact it can't be devalued moot, as people who'd use it become criminals by default.
Also, I don't see much of a difference between "classic" performance reviews and the "360-degree reviews" that the article mentions, other than the latter having better branding.
Well, I've come across companies that have policies against using unlicensed or public domain code.
This sadly makes whether it's a founded concern irrelevant, as the licensing choice suddenly prevents me from using the code in any shape or form if I work there.