Programmers guide to weight loss
I lost 44 pounds in the last 6 months. I did it without a diet or going hungry. I used basic methods that are known to most programmers for optimizing my behavior. Here is a...
Startups & Software – Simple, Open and Pragmatic.
I lost 44 pounds in the last 6 months. I did it without a diet or going hungry. I used basic methods that are known to most programmers for optimizing my behavior. Here is a...
I try to talk about myself as little as possible in this blog, but this is a personal post – so if you are looking for a tech-post, wait for next week. In the...
While this post is being published, I am resting on the beach in a Fiji resort and have probably forgotten about computers, internet, R&D, and anything other than R&R. How do I enjoy a...
Let’s face it- old browsers are a pain in the rear. Browsers like FireFox 2 and Internet Explorer 6 do not behave like modern browsers. They do not render HTML in the same way...
You hear this all the time in software companies – Some business analysts, developer or product manager trying to solve a dilemma in software development by pushing the decision to the end user side. “Let’s make it configurable†seems like a get-out-of-jail free card if you can’t make you mind about colors, screen layout and many other hard choices we have to make many time when designing our software.
The following happens in many software projects –
At start, it seems you only need one environment for your web application, well, at most two:
One development environment (AKA your PC) and one server.
But as time pass, you find you need additional environments:
The clients might want their own testing environment, sometimes you need to have a pre-production environment or a staging environment, so business managers can approve the ongoing content as well as look & feel.
Do you really need these environments? What are these environment good for?
Here is a short description of some of the more popular environments and their purpose.
After a session I gave about Scalability in Wellington NZ, one of developers asked me what are the things software architect should consider. I have gathered and compiled this list:
Application security encompasses measures taken throughout the application’s life-cycle to prevent exceptions in the security policy of an application or the underlying system (vulnerabilities) through flaws in the design, development, deployment, upgradation, or maintenance of the application. [1]