I actually laughed out loud at how different this is to the usual "be yourself and to hell with what people think" advice. Can you elaborate on why it's so important to care if people like you?
Hopefully stupid question but were you replacing the pen nibs? My screen has been solidly responsive for several years of heavy usage, but the fiber nibs do get worn down and need replacing every few weeks/months (by design) or the pen starts exhibiting this behaviour.
I have to admit I have also switched back to real paper for a lot of tasks but I still like the remarkable as an e-reader, and enjoy writing on it occasionally, so I wouldn't say it's a big regret.
It's a case of convergent evolution - I don't know where I heard it first, but I asked GPT if it minded and it said "Of course, you can call me Gippity!", so I do, because it's more fun.
There's undoubtedly a setting but if you don't want it on all the time you can always add \c at the end of the search term, like /foo\c to denote case insensitivity
100% agree. I'm currently preparing several 10s of GBs of HTML in nested directories for static hosting via S3 and was floundering until Gippity recommended find + exec sed to me. I'm now batch fixing issues (think 'not enough "../" in 60000 relative hrefs in nested directories') with a single command rather than writing scripts and feel like a wizard.
These tools are things I've used before but always found painful and confusing. Being able to ask Gippity for detailed explanations of what is happening, in particular being able to paste a failing command and have it explain what the problem is, has been a game changer.
In general, for those of us who never had a command line wizard colleague or mentor to show what is possible, LLMs are an absolute game changer both in terms of recommending tools and showing how to use them.
Curious if you have any examples of these pains? I'm not familiar with the late Python 2 era but I've been writing Ruby for a long time and wonder if I'm doing some of these as well.
"Nice" is a very subjective concept and can be used to describe people in both complimentary and derogatory ways. In my experience niceness and competence are in no way correlated – I have known nice people who were good at their jobs and assholes who were good at their jobs, as well as some of both who were terrible at their jobs. It is perfectly possible to be both competent and nice.
Given the choice between two persons of equal competence, where one is nice and one is not, I would be surprised if anybody chose the less nice one, all other things being equal.
I suggest continuing to be genuine, rather than focusing on "niceness", and not allowing a single comment on the internet to make you feel self-conscious about your character.
The m3u link is broken but the recording of the "corn chip sermon" Waits was referring to is on the same site: http://www.tomwaitslibrary.info/audio/fritolay.mp3. I can see why he was upset, I'd fall for it.
I not infrequently find myself prefixing my own code review comments with some variant of "I'm mostly asking this to make myself sound smart, but..." and then usually (not always) I delete the comment. But it's not a high proportion of my total review output, assuming I'm impartial enough to tell the difference.
My point is, it definitely happens, but if it applies to _most_ PR comments I think the code review practices of your project may need improving. My experience has been that most code review comments are either seeking to impart or gain knowledge that the commenter genuinely finds useful.
My advice would be never to purchase anything from Haier, IoT or not. We had a washer drier that had to be repaired three times because of an enormous design flaw causing it to overheat to a dangerous extent. I did eventually somehow manage to persuade them to collect it, after more than a year of back and forth with their nice, hardworking and entirely powerless customer service team. After the device was collected it then took more than six months for me to get my money back. Never again.
I feel like there's a misunderstanding here of there being a choice for victims of complex trauma to make between "suffering" and "coping". It is not as binary as this and I know people to whom this advice would be not only unhelpful but actively destructive.
Even if every single technological hurdle is removed the human aspect is the largest likely source of catastrophic failure IMO. A company town with ultra-limited resources and no escape? It will be a cold day in hell before I voluntarily imprison myself in such a high stakes social experiment.
This sounds like an absolute nightmare and I see stories like this very frequently. Is this the "normal" experience of working at FAANG in 2023, and how long has it been like that? I have never worked for (or been tempted to apply to) any business remotely approaching that scale (currently in largest ever company, 3-400 employees total, only because my previous much smaller company was acquired) and I can't really understand why anybody would ever want to.
Surely the delta in terms of earnings at FAANG vs literally anywhere else is not worth this kind of horror – can anybody explain? Or do people just not find out until it's too late?