What about using the curl command maybe? :)

I also wanted to get into it and took a look into https://phaser.io/ but I only got to simple examples. :-) Maybe you can check this article (from 13 Dec 2018) to have some overview: https://code.tutsplus.com/articles/javascript-game-engines-for-your-next-project--cms-32311 Collection of JS game engines on github: https://github.com/collections/javascript-game-engines

I usually use free tutorials / courses to get my tasks done on the job. However my company also allowed me to get some paid courses (for example: http://egghead.io/). I also take a look almost every day on the PACKT Free Learning because there is a different free book / lesson each day.

My personal best was something like this (I found it in 2012) :D // FIXME (2008.10.11): This code should NOT go to production like this! (Needless to say that it was in production since years.)

I think - as for most question in IT - it depends. Which tech stack do you / your team know better - this already is an advantage. For some kind of applications Node seems to be a better choice. It is also important to understand what you gain with one tech and what you give up For this, I really liked this article which explains why it is important to know what you gave up with choosing a particular technology: https://www.simplethread.com/was-mongodb-ever-the-right-choice/ Many technologies can be reasonably evaluated by asking just two main questions: Question 1: What problems am I trying to solve? Question 2: What am I giving up?

I wrote some parts of a library system - mostly Java Swing desktop applications and a web application for catalog search - which is still in production in big Hungarian libraries (like FSZEK: http://saman.fszek.hu/). I also have a lot of code in a big logistics system written for a big cement company.

I'm working on our administration application to allow customizing logging of our other products. I use TDD, groovy and Java in this project.

Maybe consider dropping the daily meeting completely. In my current project we only have weekly sync meeting [30 min]. Or if it not possible make it max. 15 min. Everyone only tell: what did you worked on which helps the team to achieve the goal what will you do today are you blocked my something? If yes then that can be discussed / solved after the daily.

I did not yet worked with microservices but for me it seems that you exchange some of your problems to other kind of problems. It depends if scaling up and slicing your application worth the big infra and integration overhead. So - as everything in software engineering - it depends.

I use google calendar for todos - simple and for me it is enough. For taking notes i use simplenote which has minimal UI, and syncs between devices.