155 karma · joined January 24, 2020
> since psychology is the most vague of sciences
But since you make this claim, we can talk about it. So what's your advice? See religious scholars instead of board certified psychologists?
Any sources that will back this claim? Oh wait, you don't need facts. Do you give this sort of unsolicited religious advice to everyone or do you specifically choose people who are troubled?
I'm a paying customer because I really like the UI and the base git.sr.ht service. However, hosted Git today is much more than Git. And so my overall experience is similar to the parent, I find it opinionated and stubbornly ideological. I'm close to being fed up with the "my way or the highway approach" at every corner.
Some examples off the top of my head:
1. I'm fine with sending patches via email, not every contributor is. So give me the option to accept pull requests. Instead, you'll be directed to tutorials teaching how to send patches. Needlessly increases the friction for a large portion of my peers.
2. I want to love build.sr.ht too. But, there's no Docker support. Instead you end up in discussions like "what did society do before Docker?". Give me the option to build some of my repos using my Dockerfile. Again, an ideological choice creating friction.
3. I want to use pages.sr.ht with Cloudflare. "Connections from CloudFlare’s reverse proxy are dropped." Why? "Do not help one private company expand its control over all internet traffic." OK.
All these small restrictions and gotchas with the finger wagging tone amount up to a very oppressive experience for the user. At least, that's my experience.
Could you point to a source on this? Genuinely curious to see what these items look like, I searched but no relevant results.
Some people are so full of themselves that they don't even realize how crass they might come across.
This is the type of insecurity and paranoia one can expect to find when hanging out in Nim discord.
Contrast this to, say, Zig, their road-maps and community structure is light years ahead.
If you are talking about building in public as to get your "personal brand" out there, I'd say it depends on your personality. Some people thrive when the social noise is minimal and they're focused on doing the important work. Others choose to build in public for many different reasons like motivation and networking.
Once he put the sunglasses on, he was able to see the world for what it is. And then he uttered the words, they live - we sleep.
Response:
From this experience, he said what changed his life was a sense of awareness.
His life, as with many individuals in our community, started with the question of what is the meaning of life, what makes one choose life over the endless sleep of death. Is the choice made on a random decision?
His sense of awareness awakened him to a sense of oneness with all life. One's life has only meaning when their is a sense of connection and awareness of life. They say there is no one more dead than the man who has no curiosity, for he alone who has curiosity has the key to death.
This matches with my (n=1) experience. The only way to cure "yourself" is to get away from organizations that use Slack in the way that OP describes.
Then, I read the comments and saw that every person who came to the same conclusion is downvoted to hell. So I'm just adding this comment in solidarity with people who possess some sort of emotional intuition / "yikes radar". You're not alone.
On a side-note, even though you don't mention having analysis paralysis at your step 3 & 4, something that held me back during pre-development was always trying to decide which language to use and which libraries/frameworks to go for. I've heard this from my peers as well, so I thought I'd mention that as well.
My solution to this problem is to treat the language and tools I'm most familiar with as if they are the only ones that exist in the universe. I learned this from retro game hackathons that apply artificial limits on color palette, sprites, available memory size etc. For some reason, I'm much more creative when a set of these decisions are already made, in this case by my past-self.
When I want to just play, learn, experiment with things I can choose whatever I want. But when it's building a product by myself, then I always apply plenty of artificial limitations from day 0.
There was a series of similar Twitter discussions when a popular JavaScript "influencer" published an article[0] on how they built their website. The amount of complexity that is self-inflicted in the said article was obviously enormous for proponents of MPAs.
However the JS community mostly echoed that the complexity was absolutely within norm. The cultural chasm between JS developers and people who push for simplicity was huge. And the refusal to admit the unnecessary complexity was nothing short of Stockholm Syndrome, imho.
[0] https://kentcdodds.com/blog/how-i-built-a-modern-website-in-...
This was the HN reaction to the article:
At first you're excited about change because the status quo seem clunky to you. You thrive in change as long as you can, and then one day you start questioning if certain changes are necessary or not. And at some point you find yourself rejecting change, holding on to your favorites seem like the sane approach. But what you're holding onto is now clunky and outdated for the new guy and they are really excited to change things. And so the cycle continues.
Even a 30-man search and rescue party would generally have more than 3 dogs.
But given the landscape of privacy issues, I wouldn't vote for an opt-out telemetry in any of the OS projects I'm involved with.