I'm working on this template for some time. This is what I use to quickly start a game prototype and explore an idea. After this is ready I can polish this better and make it the next step in this. Right now I'm discussing the Logger class that I use across my prototypes.

Keep in mind, all code is AGPL, so if you copy this code your codebase will be AGPL.

All feedback is welcomed.

I've started this template some time ago, and I think this is solid enough to talk about it and show this code. I'll discuss the template ins and outs along the way, this is the starting point and the reasoning for some decisions.

The first entry is the Logger class.

Keep in mind, all code is AGPL, so if you copy this code your codebase will be AGPL.

All feedback is welcomed.

Not sure if this is fully part of this community. But maybe could be a good read for the folks here since this is focused in the GameDev in he Unix systems.

This is how I organize my Godot Template for development. And a fair bunch of code. All code is AGPL so if you use this code, your codebase is also AGPL.

If this is too far from the community, I can delete this post, sorry for streching the community definition.

All feedback is welcomed.

For the last 2 years I've working in prototypes for my games. And I started to make this small template to use it. Now it's solid enough to talk about. This my start of this conversation. Today I'm explaining why and how I've my logger.

Keep in mind, all code is AGPL, so if you copy this code your codebase will be AGPL.

All feedback is welcome.

This isn't a framework, this is just a bunch of glue code that I used over the last few years. But now feels like I've a more solid parts that I can share some of the details with other folks. And with that I can discuss about it.

So this the first part, I've more in the oven cooking. But this is is about what makes a good logger (at least for me) to have in the Godot projects.

Keep in mind, all code is AGPL, so if you copy this code your codebase will be AGPL.

All feedback is welcomed.

In my view, all software is political in one way or another. Also, when software makes an attempt to be "politically neutral", in doing so it is making a political point.

So let's pick the Linus questionable part regarding the not a Social Warrior place, and I feel that it is time to either think about it or talk about it.

All feedback is welcomed.

I think that all software has a certain amount of politics in it and to say that software is non political.. is in itself a political statement.

With the mailchain of Linus... (with lack of better word) questionable quote in the Linux kernel, I think it would be good for us to discuss this issue. What are the politics behind this?

All feedback is welcomed.

I think that every software is political to an extent. And even when software tries to make its "not political" is in itself this act is political in itself.

With Linus recent suspicious statement regarding the Linux kernel, I believe we should at least try to think on it or debate on it. What is the political intention behind this?

All feedback are welcome.

From my view, all software is political in some sense. And if a software claims that isn't political is a political statement in itself. And with the recent dubious statement from Linus in the Kernel of Linux. I think we should either think about it or discuss about it.

What is the political intention that is happening in this.

All feedback is welcomed.

I think we are looking on the wrong angle. We are so focused on the AI usage that we completely ignored part that can bite us hard in the back in the future. This is me trying to untangle this point.

All feedback is welcomed.

It's hard to imagine the future, specially on our current world divide... But I think we can make a good metaphor by looking into someone from 1900s, and make a bridge for the 2100.

I hope you enjoy this reading.

All feedback is welcome.

I wanted to explore how a person from 2100s would see us. What would they think about us? What they would say. And I use the lens of us looking at someone from 1900s.

Maybe this is a good starting point for a conversation.
I hope you enjoy this read.

Feedback is always welcome.

As we continue developing our software, we accumulate a growing amount of technical debt just to keep the system running. But I believe we are on the brink of an even larger issue. Cognitive debt.

Hope you enjoy this reading, all feedback is welcome.

The more we work on the software the more debts we take to make a system. And I think we are on the verge of a greater problem, that I don't see a lot of people talking about, the cognitive debt.

Hope you like this reading, all feedback is welcome.

I think that the push of AI on the software development this will be a huge hurdle to solve, even if we manage to solve. This is my view on the cognitive debt with AI tooling. And how shit it is to help on this.

This isn't so strong on the coding part, but touch in some degree on this regard. The focus is on the data storage and access of data. I hope you like this post.

All feedback is welcome.

This is a post about how can we store and access data. What can we do, and solutions for the age verification. All feedback in welcome.

This is a deeper discussion on the concept of intelligence, and what can we infer from it. And this leads to what we can define as artificial from the concept of intelligence that we have. Maybe this is something that you may want to read about it, I hope you enjoy the read.

All the feedback is welcome.

I've wrote this post to discuss if we can infer intelligence from the inside of the machine. I've my own view on the topic, maybe this is something that you folks could enjoy the read.

All feedback is welcome.

The old-ones of us already have reached some agreement on the "what" is intelligent or not. I wanted to pick this old paper and add some more modern view on it. Hope you like this read.