LÖVE

My tip would be: Take your time. Pace yourself.

Fast coding results in errors, bad mood, nervousness and headache.

Earlier I wanted to make all fast and quick.

Now I say: one little feature per week is enough. Or nothing, too.

You tell them that if you want to learn an easy programming language, you learn the one that's right for you.

I started with QBASIC in the early 90's. And if not for Löve I would probably either be still be coding in QuickBASIC ironically or using one of the many JavaScript HTML5 gaming libraries. Actually, before I discovered Löve on that fateful February 2008 day, I was porting my current (at the time) Adventure engine project from QBASIC to JavaScript.

Jasoco wrote:I started with QBASIC in the early 90's. And if not for Löve I would probably either be still be coding in QuickBASIC ironically or using one of the many JavaScript HTML5 gaming libraries. Actually, before I discovered Löve on that fateful February 2008 day, I was porting my current (at the time) Adventure engine project from QBASIC to JavaScript.

Sounds like the start of a new and great thread there

The best tip I could give to a game programmer, is something my science teacher told me a long time ago. 'If something doesn't work forward, than think of it backwards, just a silly example.."Maybe you aren't moving over the floor, the floor is moving under you".'

Roland_Yonaba wrote:Hmm...If I had to believe this, I'll rather say :
If one wants to code better, work late..!

That's hilarious!