Good for you. You don't necessarily have to leave. Once you have some experience you can find another prospect and then deliver an ultimatum. You want dev work full time or you will quit. And mention that you already have another job lined up.
Do not break the user expectations. When I use the scroll wheel on my mouse the page screws up. As soon as I get close to the bottom it automatically flips back to the top. You may want the user to use your scroll buttons but most people won't because scrolling has been around from the beginning and people already do it a certain way. Expecting them to change for your site will make them leave. You can add your own little nuances like you have but always make sure it meshes with the current way of doing things.
Don't know what you are using but Edge sucks for me. It constantly freezes. It''ll freeze starting up or freeze shutting down. And once that happens the process stays stuck and you can't even kill it so you can't even try again. You just have to restart.
Getting the tools to do the job. Can't use Angular cause its not approved. Can't use REST because it is not approved. Supposed to use STRUTS 2(what a joke).
Damn, beat me to it. I've been thinking about this for a while. I just starting doing something for myself a few months ago. I'll have to try yours out.
Are you sure about that? Cache-Control, Expires? If you don't change the URL IE will cache the response whether you like it or not. 2 ways to handle this are to generate a random number to append as a parameter to change the URL. The other way is to have your web service to tell the browser not to cache with response headers. I have had IE do this to me and made all my web services send back "Cache-Control: no-cache" to prevent IE caching.
Not frequently, but yes. Was forced to move from Oracle to Postgres, not that I mind Postgres. Very little software changes were required to get up and running. If everything was in views or stored procedures the change would have taken months instead of weeks.
I do the same. I also keep the configuration centralized so all access goes through one class. I also allow defaults in the config file along with specific values based on what environment you are, such as production or UT, etc...