jesseg17

While I understand the motivation to move away from Slack, Basecamp, to me, seems like a worse alternative.

Most of my Basecamp interactions come from the emails that are sent on every thread change. It almost seems to be a proxy between conversation and email, which is counterproductive to its goal.

The key issue in this article is about the lacking of separation of concerns in Slack. I may be missing something, but it seems to be diametrically opposed to Slack's "always-on" structure. I would argue that Basecamp tends to devalue workplace communication through impersonal Basecamp-templated emails which often hide the original sender and thus any sense of urgency that would otherwise be generated. We have so many fantastic tools, but often email seems to be the unsung, yet essential, hopper for all of our notifications. For workplace communication and general project discussion, just email (under the right direction and guidelines - along with supplemental direct chat) strikes the perfect balance between urgency (or lack thereof), the ability to compartmentalize, and personal touch, without interfering directly with work by breaking concentration.

I agree, fixed headers are terrible on mobile devices, But I think it's a little far to say that they have "ruined web design".

Emacs Org-mode is fantastic at doing everything you mentioned.

The manual goes very in depth into all the features you need: http://orgmode.org/org.html

Yeah, but I still love org-mode. I keep my org files backed up to Dropbox so I can view them if I have to when I'm away from my computer.

I'm not a big fan of Basecamp. I find lack of support for code snippets and specific issue tracking make it inferior to GH Issues and Trello.

As a high schooler who loves coding, I'm torn between these two fields. The problem is that I can code as much as I'd like now, but real medical experience is hard to come by.