This is very good.
There’s no free lunch after all. Go’s quick compilation also means the language is very simple, which means all the complexity shifts to the program’s code.
This kind of thing can be easily automated nowadays. It’s not really a problem.
And at that point you’ll also have a better idea of the problem and solution.
If I was gonna make a suggestion, it would be to use some formatting tool such as black to make sure your code is styled in a standard way.
It helps to look up certain concepts in the Wiki (Arch Wiki is probably the most complete and well explained) as you come across them. The idea is to increase knowledge little by little, but over time it compounds.
First thing I install in each platform is fish
So many websites out there are built on Django, Flask, etc. (YouTube must have spent a decade using Python, Instagram, Threads etc. all use Python and optimize as they need).
Just as an example, I worked as a contractor with the biggest bank in Latin America before and basically all their server code is Java (with new code in Kotlin nowadays).
That seems like it’s trying to be everything.
I might be wrong — who knows — but from that text I don’t think that is being made by passionate individuals trying to create a good product for the software community because they believe in it. It feels like some VC money grab that throws LLMs at the problem and already expects to be the next Facebook.
And I work at a company who switched to “trunk-based development” but because of bureaucracy, nothing can be merged early. Big feature branches still sit waiting for months, then need a big document describing the changes and their impact, some QA team to test the new feature branch build etc. The “release management” team simply renamed the develop branch to trunk and called it trunk-based development.
It’s a good concept, I just have to look it up and understand exactly what it is doing before I start using it.