765 karma · joined November 12, 2010
The lab component of such coursework did start with TTL chips but the timing of the coursework was such that you'd have most of the asynchronous logic theory taught by the time the chips came out.
Looks similar to my own project. I think we even used the same case for the display.
https://www.reuters.com/article/us-qualcomm-m-a-broadcom-tim...
Supporting EINK on mine could potentially help make it more visually compelling like yours, but I've done other EINK display projects in the past (see https://github.com/Mrjohns42/DoggieClock) and screen burn-in was definitely an issue.
Every company all hands for the past year wouldn't be complete without an exec making comments about our eventual "return to work" policy, which has been delayed over and over again by surges and variants.
Asses in chairs is not a "company culture". I'm 10x more efficient in my home office than my open floor-plan desk next to the bathroom (with no sound-proofing) in a high traffic area. The 45-minute commute (each way) that I save largely ends up translating into more hours worked from me. With communications primarily happening over email and chat, we now have written records of decision making processes and we lose a lot less information along the way.
We're not a purely software company, so I understand some roles simply don't work remote, but I don't agree with a company-wide policy preventing regular remote work. I'm not looking forward to the struggle that is on the horizon.
Makes me wonder if an ideal service ever does come along, would we even be able to give it enough of a chance for it to stick? Or have we just been burned so badly, we'll never trust again?
> If you think a message you've received in a secret conversation goes against our Community Standards, you can report it. Learn more about what a secret conversation is. When you report a secret conversation, recent messages from that conversation will be decrypted and sent securely from your device to our Help Team for review. We won't tell the person you're talking to that you reported it.
Since Facebook's software is managing the keys, they have the ability to decrypt Secret Conversations. You have to trust Facebook not to snoop. Whereas w/ ZuccNet, the public keys can be exchanged via a separate channel from Facebook, thus rendering Facebook unable to snoop.