It's a game where you use their API to buy/sell ships, food, goods, structures for profit. You write code to plan trade routes, send out scouts, or whatever strategy you think will make the most money.
They reset the game every week and you can see how you're doing on a leaderboard. Good stuff!
I think this is a fantastic article in many ways. It clearly describes the issues of callback hell and gives simple examples on how to clean it up.
Modern JavaScript has gotten very complicated lately because it's so flexible. Many people are developing interesting frameworks to solve niche problems; however, it feels like many of these solutions are overly complicated outside the niche. Yet, developers are adopting these frameworks due to it being trendy instead of choosing the correct tool for the job.
Many times, the correct "tool" for the job can be a mixture of an effective standard library, small specific libraries, and good conventions like the author describes.
I've been a programmer for 18 years now, and I am convinced that simple proven solutions are the way to go.
It's a game where you use their API to buy/sell ships, food, goods, structures for profit. You write code to plan trade routes, send out scouts, or whatever strategy you think will make the most money.
They reset the game every week and you can see how you're doing on a leaderboard. Good stuff!