I don't think you examined the code in full. main spawns 10 go routines that are constantly sending player scores to the game. That means 10 different players are sending their scores concurrently until someone reaches score of 100.
I had time to spare so I toyed with the example exercise.
Now I am not sure if I misunderstood something because solution is fairly simple using only channels: https://go.dev/play/p/tD8cWdKfkKW
Pretty much this. Get hold of your ego and be humble enough to take lessons from experienced people who have track record of delivering successful projects. It is imperative to get the basics right before being able to take on more responsibility later.
"We don't rise to the level of our expectations, we fall to the level of our training."
Make sure you get as much training as possible before raising your expectations. It will be easier for you later when business expects senior output from you but you are under constant pressure on both personal and professional fields.
Can anyone recommend a book that you would use as the guide for building a new software project from scratch? Like something that would provide good overall structural approach and best practices. The goal would be to end with as least amount of tech debt and codebase flexible enough to stand the test of time?
An interesting read but this kind of predictions don't work "in advance". Usually it's needed for some market player that is still unknown to show up first. That player will then serve as an example and solidify the argument. To know/feel what SaaS 2.0 is, in advance, would mean that you are the one driving it. SaaS 2.0 is not here yet.
Well I live in a country with non-elected attorneys and they become marionettes of the politicians quickly. As long as they do as the regime is saying they will be there and they don't care.
Topic is Desktop computers. Not Development computers. Users of Desktop computers have specific requirements not necessary related to the development. Ignoring their requirements would definitely not allow you to take over the desktop.
> this place should not be named "hacker News"
Well couldn't you be a "hacker" in terms of UX, product design and other things as well?
It's not just developers. My friend works in the sales department and he hates it. Every functional request that he make has to go through the usual "agile" process and it's just blocked by the weeks of sprints that are trying to keep up with the increasing backlog.
Some of those requests are very important and will benefit with actual real monetary results, but he has to personally escalate it through hierarchy and force dev team to break their sprint rules and force them to work on it.
In other words he has to make them be agile by force.
It's very playable. There is only one ruining problem, as the game progress and number of objects on the map increases, game becomes ultra slow. Like one frame in 10 seconds.