|
|
|
|
|
by albumdropped
1979 days ago
|
|
I feel you. I left $BIGCO a few years ago. Here's what we're doing. For databases, we seriously considered cockroach, but went with postgres. For source control, we use self-hosted gitlab. For CI/CD, we use Go and bash exclusively. Our entire back-end/api is Go and we use Go templates on the front-end. Front-end is almost entirely straight html and css. There are handful of front-end javascript http calls if the customer has js enabled, but js is never required. Auth uses jwt. The Go standard library makes it pretty easy. At $BIGCO, I did use Auth0, but it got very expensive. We dont really need GraphQL, so that one's a no for us. For service metrics, we capture KPI data server-side and have an admin section/views for the business managers. Our team is distributed - mostly US, but a few overseas. Slack for comms. Business managers and CTO prioritize support-tickets/feature-requests and they get assigned to developers. No formal sprints; just bundle features together into a release and test it. |
|