If automated tests/linters are a part of your build system, then they basically are breaking at compile time. (Having to write tests to mimic functionality of a compiler seems wasteful to me though)
I'm very social in person, it's just the "cold email" part of it that is off putting for me. There's no observable social norm around this from my perspective. You can be a wallfly at an event and pick up norms, but you can't do that will chat/email. Maybe it's a generational gap thing, but the only times I get that type of interaction is from vendors who want something, group emails, or it's from someone I already know quite well.
Thanks for the response! Kneejerkingly that feels weird, but that's surely because I've never been apart of cold emails/messages like that. I guess I just have to make that part of my new normal.
All of the pivotal points in my career came from serendipitous moments that happened with coworkers outside of my core team at the office/at lunch/at holiday parties. That kind of natural cross pollination is near dead when working
fully remote.
They sometimes go deep, but that is more at the discretion of the interviewee than Lex. Lex is usually asking questions about topics he has only tangencial knowledge in but is the expertise of the interviewee.
The Chris Lattner episodes are great, and James Gosling had some fun stories in there, and Kernighan had a good interview as well.
I greatly prefer dark mode for my normal monitors. I greatly prefer light mode for the eink monitor. My multi-monitor setup went exactly as well as you might imagine.
Also the eink monitor I bought for $1k is quite small by today's standards, so I couldn't utilize as effectively as a vertical monitor which keeps more continuous text visible at a time.
The tech on its own? 7/10. I love it and it only lost points because the driver documentation and accompanying tool interface wasn't fully translated from the original Chinese. Ghosting issues and a relatively slow refresh rate were known tradeoffs at purchase time. so can't fault it for that.
(Despite the comment clearly being flamewar bait...)
Most of the other comments are correctly suggesting to just not exit emacs. Something opening slowly once at the beginning of a long workflow is hardly an issue. If you must open something quickly over and over again, being proficient in a secondary lightweight editor like vim wouldn't be a bad suggestion.
I bought an eink monitor. Overall great except I had to switch to light mode for everything since ghosting was an issue. It had a high enough refresh rate to be workable.
(there were warnings though that using the higher refresh rate settings would greatly affect longevity of the screen though.)
I used copilot to learn the crufty parts of bash and to pick up swift from zero. The smaller the problem you're trying to solve the easier it is for copilot to generate it perfectly for you.
Think of it like a snippet engine on steroids. It's a huge value add.
Many understand the concepts perfectly well, but will still not always remember the arbitrary difference in naming. If memorization of arbitrary words is so effortless with repeated context then no one would mix up common words like effect and affect.
This means people will mostly give their money to the loudest charities that spend the most on marketing, not on their actual effectiveness. Boring yet important projects will get almost nothing with this model. Don't make the economist mistake of assuming that people are perfectly rational actors.
This is so painfully bullshit. Imagine the scientists and engineers at bell labs thinking that the operators of their machines are akin to drug addicts.