> Or maybe a piece of good advice on how to deal with that personally. I also considered if I was the problem - by somehow misjudging the situation or something - but i think like myself, so don't spare the criticism.
Before anything else, I really like and respect your attitude. As a developer, I would like to work with more people like you.
Further, as a developer, seeing an application take 20 seconds to render makes me physically ill. I would feel exactly the same way you do, and ask the same questions.
The 20 second rendering time needs to be fixed. But, in a situation like this, there are always two options. It should be the first priority, or other things are higher priority.
Sometimes, I think it's good for developers to look at a business as a predator. It doesn't particularly care about anything other than staying alive. It has to take in as many or more calories than it expends or it will die. And, in order to catch that many calories, it has to be ruthless.
Businesses are like that. If a business consistently spends more than it makes, it will eventually die. It has to maintain positive cash flow over a certain period, no matter what. (That isn't completely true all the time as tax planning can come into it, but just accept this as a helpful half truth.) This means that when it comes to fixing problems, it's not about fixing the bullshit, it's about fixing the most expensive bullshit first.
A 20 second render time is fucking atrocious, but maybe, at worst that will cost $5,000 a month. Whereas, maybe there is a feature that will bring in $8,000 a month. In that case, the new feature wins, technical debt be damned.
All isn't lost though because again, you have a good attitude and I'd bet that other people notice that too. If you are prepared to lose graciously, you can bring up your concerns to management.
However, it's important to speak their language. They likely can grasp that a site will fail under load, but they might not care. They might not care because either something else is more valuable to work on, or because they don't know how costly your problem is. If you want to win this argument, put together some numbers and go at it. But, always remember that a starving lion isn't going to pass up a sick gazelle because gazelle meat gives it gas...:)
Before anything else, I really like and respect your attitude. As a developer, I would like to work with more people like you.
Further, as a developer, seeing an application take 20 seconds to render makes me physically ill. I would feel exactly the same way you do, and ask the same questions.
The 20 second rendering time needs to be fixed. But, in a situation like this, there are always two options. It should be the first priority, or other things are higher priority.
Sometimes, I think it's good for developers to look at a business as a predator. It doesn't particularly care about anything other than staying alive. It has to take in as many or more calories than it expends or it will die. And, in order to catch that many calories, it has to be ruthless.
Businesses are like that. If a business consistently spends more than it makes, it will eventually die. It has to maintain positive cash flow over a certain period, no matter what. (That isn't completely true all the time as tax planning can come into it, but just accept this as a helpful half truth.) This means that when it comes to fixing problems, it's not about fixing the bullshit, it's about fixing the most expensive bullshit first.
A 20 second render time is fucking atrocious, but maybe, at worst that will cost $5,000 a month. Whereas, maybe there is a feature that will bring in $8,000 a month. In that case, the new feature wins, technical debt be damned.
All isn't lost though because again, you have a good attitude and I'd bet that other people notice that too. If you are prepared to lose graciously, you can bring up your concerns to management.
However, it's important to speak their language. They likely can grasp that a site will fail under load, but they might not care. They might not care because either something else is more valuable to work on, or because they don't know how costly your problem is. If you want to win this argument, put together some numbers and go at it. But, always remember that a starving lion isn't going to pass up a sick gazelle because gazelle meat gives it gas...:)