I enjoy digging deep into complex systems, doing intensive researches, in order to solve business problems with optimal concepts and reliable technologies.
I’m building a set of Go katas for experienced engineers.
Not algorithms.
Not "learn Go"
Just real production patterns:
context, errgroup, goroutine leaks, HTTP hygiene, error semantics, allocation control.
#golang#php#concurrency#java#JavaScript
https://t.co/i7qZek3K6O
I will write a series of blog posts to share my learning throughout the journey of transitioning to #Go
In this first post, I explain why you'd rather stay away from the builder pattern once inside the Go land
#golang#php#java#javascript#symfony
https://t.co/vlwU22LF0b
A thread-safe, generic LRU cache implementation for Go, designed for high-throughput systems (GC pauses in mind). It achieves O(1) time complexity for all operations and zero heap allocations during standard R/W cycles
https://t.co/RQEQLH5pWM
#go#golang#softwareengineering
@jwage please define fail: fpm logs, app logs, the upstream's region / reacheability, OS, how often, a simultanous curl to the sipstream or even netcat, etc.. many things can help..
If you've ever worked with C, you've likely encountered the rite of passage that is the Makefile.
Cherry on the cake: Github project with end-to-end build, test & release pipeline.
https://t.co/tbNgF9r87c
#C#Makefile#DevOps#Tutorial#GitHubActions
We just moved
from: "Automate the #boring stuff with python"
to: "Automate the #boring (Automate the #boring stuff with #LLM) with python"
It is the instinct of continuously targeting the #boring segment and automating it.
Here we go again:
I have just finished creating (and using) a tiny CLI tool, written in Go for cloning elastic search indexes.
Supports bulk and long running, as well as index document start/stop
#go#golang#elastic#elk#elasticsearch#DevOps