#popgrammers

[photoskunk]

Part 2 of the #80sfunkopop challenge, tagged by @funkoken. I ❤ the 80s! #funko #funkopop #popvinyl #popphotography #popphotos #popgrammers #popgram #popfunko #toyphotography #toys #sixteencandles #samanthabaker #jakeryan #tedthegeek #thebreakfastclub #mollyringwald #anthonymichaelhall #starwars #returnofthejedi #ewok #wicket #80s #1980s

[aggressive2-blog]

Usability / Stability, you can only have one!

Somewhat sick of the situation that I'm in at the moment. Working in a fairly small team where two of us are open-minded, where the others are fairly closed and are terrified of change.

From where I sit, I can see the whole picture, where things are failing, and why. The simple fact is that we are growing faster and the current system just can't keep up. I've spoken of some of the tools that I use in my area and how it would be beneficial for them to use along-side the systems, but that is another thing that needs to be managed and they don't know how.

I think it's more a power issue they have. Remove their ability to manage something and they feel useless. See I personally think that if you can use something that will increase stability, and reduce strain, do it. Our jobs are to make ourselves redundant. If we made the perfect system we wouldn't be needed, but because you can't write the perfect system, so you'll always be needed. They just keep creating work-arounds to temporarily keep the system up, and them around.

The current event that sparked this entry was a DB issue. We've been advised to look into a High Availability solution to an issue that we're having, but we've been told that it has to be Windows based. Why? Personally I think it's because they don't want to learn how to manage something from a terminal console is my guess. Is the concept of terminal access really that hard to grasp?

I'm not saying this from a Linux fanboy's opinion, hell if the best solution meant running the DB's off a modified Playstation VITA, I'd still suggest it having no knowledge about the thing. You have to keep the companies best interests in mind, and this I think is something that they are not doing. Their demands will result in a bandaid solution due to the limitations enforced on us.

I've already had it happen to me with the current setup that I was forced to run with. I had created an ideal setup for what I needed for a DB solution, but at the last moment the plan was changed and I was forced to implement another method, which has been catastrophically flawed (and I had said that from the start that it would be). Why the change, someone's ego got in the way, and they decided that they knew best and they saw a fault in the logic. They freaking created the biggest fault that could have been made in the setup and forced us to run with it.

Forget "Brogrammers", the new (or should I say old) enemy to company growth in the IT sector are "popgrammers", those developers that have been around for years, and refuse to change their ways and logic to accommodate for advances in technology while still using out of date programming languages.