85 karma · joined March 6, 2020
So... basically the entire internet, then?
Oh, you have the gall to mention how depression or anxiety manifests in your life? You better stop flaunting your psychological frailty!
Did you mean "don't need"? I agree with the rest of your post, but this first sentence confuses me
> The web is meant for free speech. Your content shouldn’t be jailed for being controversial.
You mentioned your profile was taken offline after being mistakenly caught in their spam filter. Shouldn't spam blocking be a basic function of a publishing site? Obviously in a perfect world there wouldn't be false positives, but sometimes these things happen. Your content wasn't banned for being "controversial".
I think your general point is right though, it's not terribly practical.
I'm not an Apple hater or a fanboy. I've owned a number of Apple devices in the past. However, they have their issues just like any other tech company, but their devoted following does seem to be more cultish than that of, say, Microsoft or Google.
It's amazing what you're able to accomplish in the browser.
I generally find the axiom "If you want to go fast, go alone. If you want to go far, go together." applicable to this context.
----
Benefits of pair programming (IMHO):
* It eliminates the need for code review (most of the time) since another dev is providing input as you write.
* Pairing senior and junior developers is an excellent way to build the abilities and confidence of the latter.
* Pairing decreases siloing of knowledge and one individual's "ownership" of a particular feature or system. You much less frequently see things like "Oh, you have a question about our Widget Framework? Go ask Sally, she's the only one who touches that part of the code."
* You're less likely to implement hacky solutions just to get something to work because someone else is working alongside you. (At least, I am.)
* It's easier to find and fix bugs (in my personal experience) when you have two sets of eyes on the code.
* You have to slow down and explain your ideas before immediately jumping in and implementing them. I generally find that reaching consensus with my pair about the strategy to solve a problem helps surface edge cases I might not have thought of alone.