After a few years of helping developers review code, I came up with 10 code smells and how to fix them while building my project Axolo. - Source: dev.to / 4 months ago

Between the PR creation until it’s merged, the majority of the time, nothing will happen. We wait for the next step to happen. Unfortunately, that idle time hurts the delivery time (the lead time for changes). While they wait for a review, developers will be tempted to start another task, leading to context-switching. Practicing mob programming can prevent such latencies. Also, a solution like Axolo offers a Slack... - Source: dev.to / about 1 year ago

Comments: We are launching a free side project to create awareness for our main service (https://axolo.co). Source: about 1 year ago

Looks really nice! Also I love the level of personality on the marketing page, it's nice to see a product not taking itself too seriously. Just curious, this seems to have a lot of overlap with Axolo (https://axolo.co/) and I always love chatting to new people in this space. Email in my bio if you want to say hi! - Source: Hacker News / about 1 year ago

Disclaimer: I built one of the tool with a friend (https://axolo.co), but even if it is not for you I hope the two others possibilites might help your team! Source: over 1 year ago

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