21–30 of 230 posts
One of my main thoughts was documenting things I have found I had to do to with certain projects to get it the way I want, like homebrew packages I need to install and what to setup for if and when I wipe my computer and start fresh or get a new computer and want to set it up like I am used to.
I have had many times I forget little things I had to do and end up going through the whole spiel of getting it to work correctly.
> The Game Engine Trap. What is that? I have a few theories. One is that the developer doesn't really want to ultimately write a game. Creating the assets needed for a game, as an example, can be daunting. Implementing high scores, audio, saving game state.... There is a lot of work to create a game beyond the rendering part. Or the developer is intimidated by the more qualitative nature of the "game part" of the gam…
I have a different theory. Making your own engine is a way to turn the enthusiasm I have now into something productive now . If I want to make a character jump in Unity I need to familiarize myself with Assets, GameObjects, Cameras (don't forget the CamRotate component!), C#, Rigidbody and Colliders. My hunger for programming has turned into homework. But if I make my own engine I have more control between where I am…
I miss myself and my urge to write when I was thrilled by the concept in 2002. My original blog would be old enough to commit cr-- drive now.
I have taken great care to preserve all of the posts on my personal website, but unfortunately I don’t write new posts very often lately. I wonder if that’ll change.
Earlier quoted context omitted.
First time I heard someone asking for that. But I do indeed have that for my own blog and love it: https://www.splitbrain.org/ And if you're into random blog post, be sure to check out my project https://indieblog.page/
Thanks for making and sharing that project. A feature request, if I may: please consider adding support for https://www.jsonfeed.org/ . Thank you.
Things I love about your blog:
- The fact that every post has links to the sourcecode!
- Open source
- No ads, no trackers, no popups
- I can tell you use this all the time. So I know you strive to make your content as good as possible _for you_. Which is a strong signal that it will also be good _for me_.
- I love the timeline (but wish they were done in a way that reflects scale, see user test video for more)
Here's my user test: https://news.pub/?try=https://www.youtube.com/embed/UF7fjvE_...
> The Game Engine Trap. What is that? I have a few theories. One is that the developer doesn't really want to ultimately write a game. Creating the assets needed for a game, as an example, can be daunting. Implementing high scores, audio, saving game state.... There is a lot of work to create a game beyond the rendering part. Or the developer is intimidated by the more qualitative nature of the "game part" of the gam…
Your game needs sprites, so you could write code that loads the one graphics format you need at the 2 or 3 sizes you need. While doing that you decide it looks hacky so you add support for more formats, better scaling, ... suddenly you have gone from doing that one thing your game needs to something that supports everything every game on the planet might need but usually doesn't. By the time you have done that for every system in the game, you now have an "engine" but are burnt out on the project.
If I ever finally find the motivation to start a blog, I think this is a key point. Vanity metrics would be demotivating.
Nice presentation and nice recap! A couple of observations from the text that resonate with me: * "Blogging helps me become a better writer, which in turns helps me become a better developer." Yes. Writing is super-important as a developer, particularly in a corporate setting, because communicating ideas clearly is critical in convincing others and in showing your contributions. And to be a better writer, well, one h…
> Other platforms like Twitter have captured the space of short form writing Does this ever feel like a waste? Are there good thoughts, ideas, and quips you've written and shared, that were then essentially lost to time? Since those thoughts are not archived on your website, when (if ever) do you (or anyone else) ever get to see them again?
This reduces the friction in sharing things, since building a whole new page takes a few minutes.
> The Game Engine Trap. What is that? I have a few theories. One is that the developer doesn't really want to ultimately write a game. Creating the assets needed for a game, as an example, can be daunting. Implementing high scores, audio, saving game state.... There is a lot of work to create a game beyond the rendering part. Or the developer is intimidated by the more qualitative nature of the "game part" of the gam…
I just make tech demos and libraries for odd stuff like loading 3D models