I have used https://takehome.io/. The timer starts when they check out the repo containing the project and instructions. - Source: Hacker News / almost 2 years ago

I run https://takehome.io and https://clubman.app on the same stack. Backend in Go with a simple MVC pattern, no framework. All data in Postgres. Front end is server rendered HTML using MaterializeCSS for components, migrating to TailwindUI. Hosted on GCP using Cloud Run, deployed using the gcloud cli orchestrated in a makefile. Database is a Cloud SQL instance. Google Cloud Tasks for the message queue. Amazon SES... - Source: Hacker News / almost 3 years ago

The person who mentored me the most when I was getting started with Terraform used VIM with pathogen but honestly this isn't a great idea unless you're really invested in a VIM workflow. Source: almost 1 year ago

I am a bit confused. What has this anything to do with your original question? vim-pathogen is for Vim editor itself, not for PyCharm. I don't know much about MacOS, so not sure how to help. Did you try the installation steps at https://github.com/tpope/vim-pathogen ? Source: over 1 year ago

Back in the old(ish) days of Vim, usage of tpope/vim-pathogen to manipulate runtimepath was a popular way to install plugins. As it got update 9 days ago, it might be still used by some. Source: almost 2 years ago

To install any plugin using Pathogen plugin manager, you need to configure PAthogen in your vimrc if you have not done it already. You can find the installation docs on Pathogen.vim. After Pathogen has been configured in your vimrc, you can clone the git repository of that plugin into your local machine and then activate it using Pathogen. - Source: dev.to / almost 3 years ago

Bundles, Plugins, and Packages. Oh my! - Vim plugin management have gone through many "best practices". vim-pathogen, Vundle, vim-plug, and Vim 8's :packadd. At any given time I am certain the community would say one of these is "modern" or at the least some sort of standard. Source: about 3 years ago