The Worst Advice You Could Ever Get About we software stagnation
Software stagnation is a common condition that exists when we are stuck in a certain programming stack. It is what keeps us from truly exploring what is possible and solving problems in software development.
Software stagnation is a very real thing to live with. Many software developers and designers struggle to get a game going. Sometimes they’re even afraid to start it because they think it will fail. The point is that developers often want to start a game, but they just aren’t sure how to get the game to work. They are so afraid to try something they don’t know how to.
I know I’m writing a bit of a rant here. I’m going to say that I think it’s important for software developers to learn how to program. Sure, it takes time and it can be frustrating, but it’s the only way to truly see what the limits are of a system.
I agree. I think a lot of developers don’t know how to program, because they are afraid to try. They just want to see the code work. The point is that they dont like to think about the code, so they tend to make things that are very difficult to debug. And that’s why the code isnt good. It’s because nobody knows how to debug the code.
This is one of the main reasons why my first job out of college was a glorified C and C++ programming class. I was a programmer for about six months, and then I realized that I loved writing C programs, but I hated writing C++ programs. The only reason I like C++ is because of the garbage collection and concurrency. But if you think about it, it makes sense.
The reason the code is bad is because nobody can debug it. This is the kind of code that you get when you have a bunch of codebases that are pretty much the same (yet with different names) and nobody knows the differences.
I was a programmer for a few years and then I realized that I also loved writing C programs, but I hated writing C programs. The only reason I like C is because of the garbage collection and concurrency. But if you think about it, it makes sense. The reason the code is bad is because nobody can debug it.
In the same way that the programming industry is stagnant because nobody can debug it, software development is stagnant because nobody can debug it. You can look at a codebase and say “What’s wrong with this?” but there’s no easy way to tell if it’s actually wrong. It’s like we software stagnation because nobody can debug it.
I think that’s why the software stagnation is so prevalent. It’s because the people who create the code can’t figure out how to make it better. So they don’t fix it.
The point of all this is that there is no easy way to tell if something is wrong with your codebase. And theres no easy way to tell if someone is making it better or worse. So developers create software and hope it gets better. But theres no easy way to tell if the code is actually better or worse.
