Day 1 of learning Go after office hours.
Built a simple HTTP server (with routes) & learnt basic semantics with pointers, interfaces & structs
This project will finally turn into implementation for Raft from the official paper (link in comments)
Go is pretty nifty & cool :)
What title do you actually identify with when someone asks 'What do you do?'"
A. Tech Enthusiast (The hobbyist)
B. Software Engineer (The architect)
C. Programmer (The logic solver)
D. Software Developer (The builder)
E. Coder (The syntax writer)
Where is the Jumia you guys said you'd rebuild in 2 weeks???? π€‘ This is the last day.
I need a written apology not less than 500 words from all of you who insulted me for saying it's impossible. π
Letβs talk about webhooks (the simplest way to understand them).
Most apps still waste time asking:
βDid anything change yet?β
βNow?β
βNow?β
Webhooks work the opposite way.
Instead of polling every few seconds, services notify your app instantly when something happens:
β payment succeeded
β user signed up
β repo updated
β order shipped
β AI job finished
They let apps react instantly instead of constantly checking for updates.
If APIs let you request data,
webhooks let systems react.
Go + Gin β REST APIs
Go + Fiber β High-Performance APIs
Go + Echo β Web Framework
Go + net/http β Core Backend
Go + gRPC β Microservices
Go + PostgreSQL β Relational DB
Go + GORM β ORM / DB Access
Go + Redis β Caching
Go + Kafka β Event Streaming
Go + NATS β Messaging Systems
Go + Docker β Containers
Go + Kubernetes β Cloud Native
Go + Terraform β Infrastructure as Code
Go + Prometheus β Monitoring
Go + CLI β Dev Tools
Go + WebSockets β Real-Time Systems
one language
backend
cloud
devops
systems
and people still say
βgo is too basicβ π