Avelino

Igor P. Leroy

Cássio Botaro

Adimir Colen

Diego Leite

Herson Leite

Ivan Rocha

Ellison

Brandon Bennett

itchyny

Diego Garcia

Eduardo Elias

Henrique Leal

Magnun Leno

Cézar Augusto

Felipe

Pedro Henrique

Afranio Martins

Francisco Omar

Guilherme de S. Vieira Beira

Stoo Johnston

Rodolfo

Carlos Coelho

Adam Kaliński

Alexandre Medeiros

Amim Knabben

Andrew Widdersheim

André Dalcin

Andy

Archie Hilton

Bruno Agutoli

Caio Vitor

Chinmay Hebbar

Cirelli

DIEGO DOS SANTOS

Dilan Nery Lopes

Eduardo Cuducos

Eduardo Pinto

Elton Souza

Erik Tetland

Actionless Loveless

FatMinMin

Felipe Finhane de Paula

Gabriel Gutierrez

Gurjeet Singh

Henrique Santos Fernandes

Hélio Meira Lins

Ihor Dvoretskyi

Jake Worth

Jean Rodrigues

Jessica Temporal

John Deng

José Augusto

João Batista Neto

LATA SHARMA

Layton Nelson

Leonardo Rezende

Marcus Hrvatin

Mateus Esdras

Prasetiyo Hadi Purwoko

Pratham Sharma

README Bot

Rael Max

Rakan Alhneiti

Raymond Barbiero

Robson Roberto Souza Peixoto

Rogerio Fonseca Gonçalves

Sayz Lim

Tarsis Azevedo

The Gitter Badger

Victor Stein

Vishwa.R

Wellington Moraes

Adriano Vieira Petrich

raimon

Vim Bootstrap is a generator that provides a simple method of generating a configuration for vim / neovim.

co-founder

Developing the *"onboarding"* process for a new person in an engineering team takes a lot of dedication, and keeping this process fluid takes even more work (with as little friction as possible).

This issue is challenging for any team working full time, it is even worse for Open Source projects where contributors usually work in their spare time. We should make this process as fluid as possible so that people don't get discouraged by the complexity of getting up there and testing, until they make their first pull request.

## Configure development environment

Every developer has a different way of setting up a development environment, even if it is in a popular technology (programming language) with lots of documentation, text editor extensions (emacs, vim, vscode, ...), etc.

We developers are used to “*our way”* of doing things, it is common for us to create resistance when someone presents a different way and I do it another way.

In the vast majority of applications they depend on external resources such as databases, APIs, tokens, etc., if we force the developer (user) to read all the project documentation before having the first contact with the project it is very likely that we will lose his engagement, and some frustrations in him, such as:

- I just wanted to test
- I have to read all this to see it working
- What a complicated project
- I have to install X, Y and Z services/software on my machine
- I don't know the programming language used in the project, which plugins should I install in my editor?
- ... and much more.

There are some tools to assist project maintainers (open source or private) to generate an onboarding process with as little friction as possible.

Configuring editor (with all the necessary plugins and parameters), all the services the project needs to run, environment variables configured, database running with initial data load, data viewer configured (software to manage data from the database), etc.

To the point where the developer “**clicks a button”** and magically has the development environment ready to test the software.

In the last few months we at *prestd* have been working on improving our documentation (it is far from being good documentation) and removing as much friction as possible in the process of getting a new development environment up, some issues we have implemented until we got to what we have today:

- [Improve local tests execution](https://github.com/prest/prest/issues/510) — it is frustrating that someone wants to contribute and cannot run the local tests (we use e2e tests, making requests to *prestd*'s own API), a way was implemented where the tests run inside docker using `docker-compose`;
- [Documentation: new content architecture](https://github.com/prest/prest/issues/542) — thinking of a person who has never had contact with *prestd* and wants to test or use it in a production environment, both people should get into the documentation and be able to do what they want to do (bring up the environment);
- [Onboarding of new contributor: using devcontainer](https://github.com/prest/prest/issues/665) — prepare the development environment with *"1 click"* using [devcontainers](https://code.visualstudio.com/docs/remote/containers) ([GitHub Codespaces](https://github.com/features/codespaces) support).

See *prestd*'s development guide page [**here**](https://docs.prestd.com/prestd/setup/development-guide/#dev-container).

> It is not nice to have the engineering team working in a bad environment, we need to think more about our team and make the team experience fluid.
> **people > technology**
> 

## Focus on the developer (user)

The *prestd* exists open source since 2016, I particularly like the project very much and believe it is a great solution to accelerate the development of a RESTful API for existing database and especially development of a new API (project starting from scratch).

But for many years we turned to developing the software didn't look at documentation with the dedication we should, causing the contributor base to shrink (existing and new) — people going through open source project, hardly stayed for many years, so we always have to have the most rounded onboarding process possible.

Given this problem I started to look at the documentation with more dedication and every decision in *prestd* from now on will be thinking about the developer (user) experience, answering the following questions:

- Will this improve the developer experience using the project?
- Will this make the project easier to use?
- Will this make it easier to maintain the development of the project?

When all 3 questions are “**yes”**, we will proceed with the implementation, regardless of what it is: feature, improvement, fix, etc.

Developing the *"onboarding"* process for a new person in an engineering team takes a lot of dedication, and keeping this process fluid takes even more work (with as little friction as possible).

This issue is challenging for any team working full time, it is even worse for Open Source projects where contributors usually work in their spare time. We should make this process as fluid as possible so that people don't get discouraged by the complexity of getting up there and testing, until they ma

Matt Holt

Kirill Danshin

Dmitri Shuralyov

Dobrosław Żybort

Marin

Duke

Ceriath

Dean Karn

Patrick D.

Bo-Yi Wu

Phani Rithvij

Jerry Zhao

Andy Pan

Felipe Oliveira

Peter Benjamin

Linh Tran Tuan

Carles Cerezo Guzmán

Mehrdad Arshad Rad

mattn

Alessandro Leite

Renato Suero

Vishal Rana

Chris Lu

Bob Glickstein

Dave Brophy

Eyal Posener

Hugo Leonardo Costa e Silva

John Arundel

John Dyer

Kamil Samigullin

Olivier Poitrey

Peter Thaleikis

Rafael Jesus

Ralph Caraveo

Sasha Melentyev

Travis Harmon

siddontang

徐佳军

Surya Asriadie

Viet Hung Nguyen

Osamu TONOMORI

Adam Hanna

Aliaksandr Valialkin

Andrey Yurchenkov

Anthony HAMON

Carlos Alexandro Becker

Daved

Eduard

Eduard Urbach

Francois

Henry

Inhere

Lunny Xiao

Pieter Claerhout

Qiang Xue

Romano de Souza

Saddam H

Walter Schulze

Philip O'Toole

Patricio Whittingslow

Alex Archer

Konstantin

Max Chechel

Sadlil Rhythom

Alexander F. Rødseth

Andrey

Andrey Nering

Andy Grunwald

Asdine El Hrychy

Claudemiro

Enrico Bianchi

Erik Unger

Gleb Sinyavskiy

Guillaume Simonneau

Hajime Hoshi

Igor Novgorodov

James Polera

Julien Feltesse

Marco Muratori

Matt Joiner

Max Halford

Miles Croxford

Navid

Nikolay Dubina

Paolo Ibarra

Pascal Dennerly

Prashant Gupta

Raed Shomali

Rafał Lorenz

Raul Ascencio

Rijul Gulati

Roman Atachiants

Nan Lin

A curated list of awesome Go frameworks, libraries and software

[![awesome-go](https://github.com/avelino/awesome-go/raw/main/tmpl/assets/logo.png)](https://awesome-go.com/)

[![Build Status](https://github.com/avelino/awesome-go/actions/workflows/tests.yaml/badge.svg?branch=main)](https://github.com/avelino/awesome-go/actions/workflows/tests.yaml?query=branch%3Amain)
[![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg)](https://github.com/sindresorhus/awesome)
[![Slack Widget](https://img.shields.io/badge/join-us%20on%20slack-gray.svg?longCache=true&logo=slack&colorB=red)](https://gophers.slack.com/messages/awesome)
[![Netlify Status](https://api.netlify.com/api/v1/badges/83a6dcbe-0da6-433e-b586-f68109286bd5/deploy-status)](https://app.netlify.com/sites/awesome-go/deploys)
[![Track Awesome List](https://www.trackawesomelist.com/badge.svg)](https://www.trackawesomelist.com/avelino/awesome-go/)

[![awesome-go producthunt](https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=291535&theme=light")](https://www.producthunt.com/posts/awesome-go?utm_source=badge-featured&utm_medium=badge&utm_souce=badge-awesome-go)

> A curated list of awesome Go frameworks, libraries and software. Inspired by awesome-python


### Contributing

Please take a quick gander at the [contribution guidelines](https://github.com/avelino/awesome-go/blob/master/CONTRIBUTING.md) first. Thanks to all [contributors](https://github.com/avelino/awesome-go/graphs/contributors); you rock!

A curated list of awesome Go frameworks, libraries and software

[![awesome-go](https://github.com/avelino/awesome-go/raw/main/tmpl/assets/logo.png)](https://awesome-go.com/)

[![Build Status](https://github.com/avelino/awesome-go/actions/workflows/tests.yaml/badge.svg?branch=main)](https://github.com/avelino/awesome-go/actions/workflows/tests.yaml?query=branch%3Amain)
[![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg)](https://githu

Cesar Gimenes

Henrique Chehad

Mario Idival

Tiago Temporin

Arthur Silva

Joel M. de Souza

Andrews Medina

Fabrízio de Royes Mello

Ivan Voronchihin

Matheus Francisco

Sebastian Webber

Cezary Tarnowski

Christophe Camel

Imgbot

Kemel Zaidan

Louis Brauer

Georgy

Eugen Biegler

Hsieh Chin Fan

Kaique da Silva

Naren

Norris Oduro

SSMK

Weverton do Couto Timoteo

julien brunet

Rafael Marques

Azzuwan Aziz

PostgreSQL ➕ REST, low-code, simplify and accelerate development, ⚡ instant, realtime, high-performance on any Postgres application, existing or new.

## 1-Click Deploy

### Heroku

Deploy to Heroku and instantly get a realtime RESTFul API backed by Heroku Postgres:

[![Deploy to Heroku](https://www.herokucdn.com/deploy/button.svg)](https://heroku.com/deploy?template=https://github.com/prest/prest-heroku)

## Documentation

<https://docs.prestd.com/> ([content source](https://github.com/prest/prest/tree/main/docs) and [template source](https://github.com/prest/doc-template))

PostgreSQL ➕ REST, low-code, simplify and accelerate development, ⚡ instant, realtime, high-performance on any Postgres application, existing or new.

## 1-Click Deploy

### Heroku

Deploy to Heroku and instantly get a realtime RESTFul API backed by Heroku Postgres:

[![Deploy to Heroku](https://www.herokucdn.com/deploy/button.svg)](https://heroku.com/deploy?template=https://github.com/prest/prest-heroku)

## Documentation

<https://docs.prestd.com/> ([content source](https://github.com/prest/pr

Avelino

vim-bootstrap

Constant work to onboarding new members into engineering team

awesome-go

prestd

Saying hello! 👋

Avelino

vim-bootstrap

Constant work to onboarding new members into engineering team

awesome-go

prestd

Saying hello! 👋