The time of year for reflection and looking back over the last 12 months, to supposedly learn, is fast approaching. Now, I wouldn't be one for too much introspection, but as I spend a large chunk of my day staring at a screen I do think about how to make that habit somewhat useful. Improving your workflow is always important.
Nothing is perfect. It is an impossible word to realize, and like foresight it simply does not exist. Forethought on the other hand does exist, but unfortunately few people put enough effort into thinking ahead.
DevOps, as discussed in last weeks blog, brings a number of benefits to software firms that need to quickly get their coded goose to market, so to speak. Most of these are tangible benefits, while some are unquantifiable advantages that certainly help deliver the goods. I’m going to run through 5 benefits here today; two technical, two business, and one unmeasurable.
DevOps is a word that has been creeping into the Software Development Life Cycle (SDLC) lingo of late, and it's not one readily understood. Much like some new meme you missed when making coffee and upon your return are left wondering if everyone around you is speaking the same language, or fully compos mentis, it provokes sideways glances and fake nods of agreement. So, for arguments sake I am going to define the term today, and let this forever be the dictionary definition.
Last week I covered the general idea behind Cross-site Scripting (XSS), and this week I am going to get a little deeper into how you can prevent it happening to your web app or site. There are a number of tactics you can use to make your project a less attractive target, and even though it’s probably impossible to have a complex user app and be totally immune to XSS, you can at least be more difficult than the next guy. This gives you the added advantage of sending wannabe hackers towards easier pickings.
