UIBuzz - Software and game development

We all love to try new things, those you see all over the tech news and discussions. But exercise caution when doing so. They might make life far more complicated than it needs to be regarding shipping. Some thoughts and suggestions in this episode.

Show Notes

★ Support this podcast ★

What is UIBuzz - Software and game development?

I love making software. I also love sharing that experience with others. I explore it all in this Podcast, from apps to games and in between. From developers just getting started to professionals. We all have something to learn and share with others on our journey.

In this episode, we'll be discussing cutting-edge tools and the pros and cons of staying on the cutting edge.

We all love using the latest and greatest tools, whether it's a new framework or library, especially in the world of JavaScript.

But there are some downsides to always being on the cutting edge.

You might encounter problems that no one else has solved yet, or you might be using something that's not fully functional.

That being said, I'm not saying you shouldn't explore new tools.

I personally have two approaches that I follow, and I'd love to hear your thoughts on them.

First, when I'm working on something that I need to ship and support within a reasonable timeframe, I stick to tried and tested stable versions of tools.

I avoid jumping on new frameworks and rebuilding everything from scratch, as it's not a reliable way to deliver a product and provide timely updates and fixes.

Second, I believe in constant learning and experimentation.

I explore new tools and technologies to understand their capabilities and limitations.

I don't necessarily plan to use them right away, but I keep an eye on their progress and maturity.

For example, when Swift was released for iOS development, I jumped on it for my side projects to learn and understand it, while still using Objective-C for production versions.

So, my suggestion is to approach new tools as a learning experience rather than immediately integrating them into your projects.

Unless it's for tutorial purposes or you're certain it's stable, it's best to avoid shipping products with cutting-edge tools.

Remember, not all new tools stand the test of time, and you don't want to waste time fixing issues unrelated to your project.

If you do encounter problems, make sure to contribute back to the open-source community.

And if you come across an abandoned tool that you really like, consider forking it and continuing its development.

These are just my thoughts on the matter, and I'd love to hear your opinions.