To be fair, the other 50% of the story is that we collectively listen.
It’s been a long while since I found a Chinese CEO’s post on HN.
312 karma · joined December 10, 2011
It’s been a long while since I found a Chinese CEO’s post on HN.
So if your Gmail is foo.bar@gmail.com you can use foo.bar+servicename@gmail.com and the mail will still end up in your mailbox. Then you can create a rule that sorts incoming mails accordingly.
If the answer is yes then it’s a tragedy - but one that presumably will pass once we collectively discover it. If not, then it’s just nostalgic.
Just right now no one cares enough yet. Give it a year or two.
I could conceive something evolving on a different abstraction layer - say, clean requirements and tests, written to standard, enhanced with “common sense”
Because let’s be honest - all of us know that a lot of data points are being collected about us, countless articles have been written about the insanity of cookie and user-data monetization networks - still it appears to be a privilege to few to tap into that data trove.
I personally haven’t seen an effort to try and make this transparent. Efforts like this page are commendable and informative, much like amiunique or other services - still they lack the tangible information that sharing this information with “the world” reveals about an affected individual.
Why hasn’t this been done yet? Why is this seemingly not trivial?
The system and the fact that he executed it though is genius.
Once I could personally meet or just see people (in person or otherwise) that attempted this kind of rewiring of your synapses I realized how deeply unwell they really are.
And for the untrained eye, your point takes it away: Have a hard look at folks who tried (like Crowley, probably the most documented case) and be wary of following advice on the web that puts your mental health at risk, even on HN.
There’s a spooky coherence in the descriptions and that’s what makes it such a fascinating read. The spin that this work puts on the subject - calling this “technology” and likening it to programming adds to this.
To anyone honestly wanting to take this for a spin, I recommend reading the biography of Aleister Crowley first. It’s an interesting read in itself and it also illustrates the risks/dangers. Pictures speak a thousand words.
Only trusting your gut is probably as bad a piece of advice as saying ”never trust your gut”.
The coworking spaces pitched in the article charge north of $500 a month for a simple chair to sit on. some get more expensive if you only want to stay for a few weeks.
That makes it easy to go for the free option and just squat a spot at a cafe.
I feel bad for the good guys who behave respectfully and know when they’ve overstayed their welcome. But for those that don’t Cafe owners need to disincentivize the behavior.
I’m online >12h/day and I work on all devices available while awake. Still, I personally would prefer a cafe that has a strict “no notebooks” & “phone calls and meetings outside” policy.
This includes the classic “blocker” but besides that opens up for interesting conversations, encourages cooperation and isn’t overly management focused.
For the manager it helps uncover potentially hidden dependencies or team animosities.
Yes, their POC uses SDR
Probably the only digital thing besides my self-hosted mail account that survived the last 20 years unchanged.
The user wants a human to understand their sometimes multi-layered requests. The dev wants these requests to be de-layered and broken into separate issues for tracking and documentation.
There really isn’t a good system today (that I know of) that would facilitate this process with both the user and the dev in mind.
From a perspective of information structuring and prioritization, tickets are perfect (for the dev), yet they lack a “natural” (e.g. email, phone or chat) support exchange where an issue is several issues rolled into one. Or once an issue is resolved there’s the “oh btw while I have your attention” moment where an unrelated issue is discussed but the interaction between the same people is ongoing.
To handle this properly in an email-to-ticket-system the dev would need to ask the user to resend the request in a different mail or themselves open a new issue, which is exactly the overhead the system tries to avoid in the first place. Or either party would need to remember the issue ids to keep a running list, all of which seems undesirable.
In the case of a small team/single dev product it’s that human interaction that’s not paid for so the burden is put on the user, at the cost of a reduced interactive experience.
Is there any better way of solving this? Or are systems being built to support this a bit better than how the Jiras/Redmines of this world are (not) handling it today?