I’m not talking about the coding, though. I’m talking about everything else.

Coding is much easier now, sure. We can get roughly 35k-line PRs in one day like it’s nothing. But work is much more than just writing code and I think the AI-brained folks are just making everything much more difficult because of how AI-focused they are in their coding work.

Emails are AI-written and use a ton of words to say literally nothing. Docs are worthless now because they’re so verbose and never get to the point. And sometimes even the Slack messages I get are clearly from a bot that some shmuck rigged up, which makes me have to wade through a couple of additional barriers before getting to chat with the person with the answer I’m looking for, like I'm some kinda Xfinity customer.

AI has been a huge help for the coding process, sure. But work is more than that even for software engineers, and aside from the actual writing of code, I feel like everything has gotten much more time-consuming.

Hi, I'm not an experienced software developer at all, but I'm still asking this out of curiosity.

What's the best approach for software portability in many different machines, NOT just desktop computers? Whether I'm finalizing a video game, or just any software that has a GUI.

Should I use something like C/C++ or Rust, or will other compiled languages like Go or Nim also work well? And for VM languages like Java and C#, the machine would require the VM system to be installed so I assume VM languages would not be viable for portability.

Also, should I not use any third-party APIs, like SDL? Or will embedding APIs still work for a lot of machines?

For example, Doom was easily portable since it purely used C, and separated the core game code from the machine-specific implementations, right?

SuperTux also had a lot of ports, though it at least used SDL as another API. I wonder if it still was easily directly portable with barely any changes?

To sum it up, how much will third-party APIs matter when it comes to portability?

Aside from that, what other things should I consider in order to make programs easy to port?

Hey everyone,
I’ve been working on a project called BugCapsule, and I’m finally opening it up for beta testing.
One problem I’ve faced countless times as a developer is getting a bug report that explains what went wrong but gives you no reliable way to reproduce it.
That’s exactly why I started building BugCapsule.
The idea is simple: instead of just reporting a bug, BugCapsule captures the app state, user actions, and network responses around a failure, allowing you to replay the scenario locally.
You can reproduce the issue, debug it, apply a fix, and replay the same scenario to verify that it’s actually resolved.
A few things worth mentioning:
Supports Flutter, native Android, iOS, and Web/React.
Integrates with Sentry for web apps.
Works alongside your existing error tracking tools.
Lets you reuse captured scenarios for regression testing.
It’s still in beta, and I’m sure there are things that need improvement.
I’m particularly interested in hearing from developers who deal with hard-to-reproduce bugs.
I’d genuinely appreciate your feedback, especially around the setup experience, replay reliability, and whether this would be useful in your workflow.
You can try it here: https://bugcapsule.com/
There’s also a guided demo if you want to explore it before installing an SDK.
Thanks for checking it out!