My Employer is their worst enemy

My first computer at work was a real piece.  They had juast purchased a competitor, and had not nerged enough beuracracy to be able to give me a computer.   I had traqnsfered from the purchasing company to the purchased company.

Eventually I started developing software again after I got a bit healthier.  My laptop was so bad, you could not even get the software development tools to run.  The laptop freezed up.

I was told that I could not get a new computer for 4 months.   Th person in charge probably didn't like me because she was the one tasked with getting me my first computer, and probably had to do a lot of work to get it to me.  All she had to do was suggest a different supplier.  The company changes suppliers every 3 months.  But she was not going to do that for me.   I tried to escalate it to my boss, and his response was "A competent engineer would be able to solve that problem".  His idea of competence is really different than mine, and probably most people.

So I got stuck with another computer that was just lying around not being used, just like the first one.  And there was a reason no one wanteds to use it.  It can barely do the job that I am now required to do.

I have been hitting resource limits for months, and have to do a lot of rework to get around them.  This week, the interface to EJB beans just stopped working.  The real-time connection to the bean failed with a very terse error message.  The WWW was no help.   There was just too much obsolete content on the web.  So I struggled for 2 days.

I finally found 2 configuration files, and specialized editors within the software development tool to edit them.  

I did not find a solution.   I stumbled on it.  While looking at the elements and structure of these XML config files, I noticed that there were XML attribute tags that controlled the frequency in which files were checked to see if any changes had been made to them.

Lotsd of web developers are fast and loose.   They like to make changes and see them reflected immediately in a running WebApp.  So the industry caters to them.   But you had to be able to turn these things off, because it just wastes bandwidth in a production deployment.  The code isn't changing hourly in a Production system.

One of the XML attribute tags controlled how often JSP files are scanned to see if any of them had changed.  The default value is ONE SECOND.   Because of the strict constraints put on the WebApp I am making, I was forced to create hundreds of small JSP files that get pieced together dynaically.  I may have over 1000 JSP files.   Checking all those files and comparing the current time to the "updated date" to each file probably used up the entire ONE SECOND.   No wonder my system was taking so long to react to keystrokes & MOUSE-CLICKS.   I turned this off, and the EJB error went away.

I feel like my employer is doing everything possible to make it hard for me to do this job.  Sometimes I click on a word in a code file, and it takes 30 SECONDS for the word to become highlighted.  It is supposed to be an immediate response.