I began learning C++ at university, but I never quite got comfortable with it before losing interest.

That’s a solid point. Software development really benefits when engineering principles come first, not just quick delivery. Planning, system design, and reliability still matter a lot, especially when building products that scale. It’s similar in service businesses too—Sawtransfer works better because the process is planned like an engineering system, not just random transport booking. Strong systems always create better user experiences.

Got basic knowledge how to protect and maintain confidentiality

This explains one of the biggest misconceptions around AI-assisted development right now: people think faster code generation automatically means faster software engineering. But the real bottleneck was never typing code — it was understanding systems, constraints, tradeoffs, scaling behavior, and long-term maintainability. The “vibe fixing” part especially feels real. A lot of teams are accidentally replacing deliberate engineering with endless prompt-repair cycles that only look productive on the surface. Feels like the companies that survive this shift won’t necessarily be the ones gener

This is an interesting framing of the context problem — I especially agree that a lot of failures in software projects come from unclear requirements rather than execution. Even in simple tools like [IPPT Caculator] https://sgipptcalculator.com/ if the problem isn’t defined properly, you end up rebuilding things multiple times. That’s why I try to keep my own projects very focused and minimal from the start.

Good explanation. A real challenge appears in production environments when access tokens expire during long-running sessions, especially in microservice architectures. For example, in Kubernetes-based applications behind API gateways, improper refresh token handling can lead to repeated authentication failures, spike traffic on auth services, and even cause cascading failures during peak load. That’s why token rotation, secure storage, and proper retry mechanisms are just as important as the JWT implementation itself.