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...
One question: Your basic package says 1GB of RAM. Is that 1GB available to me or is the OS using some of that to. The reason I am asking is I have been considering something like this to run a Minecraft server for my kids and their friends. Ever since I changed providers their port forwarding is broken and I can't serve it from home. However to run efficiently a Minecraft server needs 1GB to itself so if the OS is using some of that RAM getting the basic service is out and so are the other options since they are not affordable for me.
Not really. Trying to explain your code to someone else helps you understand better as much as it helps someone else to understand it. You only explain it at a high level unless there is a complicated part that you might then go through line by line.
No it is not. Just because you have a one bad experience, doesn't mean that is how the enterprise works. There are hundreds of thousands of enterprise shops out there. We don't do anything like the craziness you guys are talking about. We make it work with the easiest code possible. If necessary we refactor when we need to make a solution more generic.
For this to work they have to have the correct key in the first place. If I encrypt something with my key and send it down the wire and they intercept it and try it on a machine they own they wouldn't be able to decrypt it. This requires them to be hooked to my machine while I am decrypting to get at the key.