I wrote a bash script, I can share it if needed, that takes a screenshot of my computer every minute. After approximately a day (2700 pictures to be exact as that works out to 3 minutes of video at a 10fps rate) it automatically compiles said screenshots into a video.
I am in the process of writing an IT security plan specifically for my employer as it relates to web applications and storage of some very sensitive PII (personally identifiable information). I cannot post the entire plan here, nor will I post specific security measures. I did want to start a post on the overall, basic concepts of an IT security plan as it relates to web applications. Naturally these concepts apply to all the code I write and I think it should also be taken into consideration by mobile app developers and others writing code without security.
I'm currently writing a completely benign app that is related to discovering sales on a users favourite products. I should be clear up front that I am not a malicious user and will never write viruses or malicious apps. The information provided below is for prediction, curiosity, and information purposes only.
I was very fortunate, today, to be invited to attend a seminar where IBM Canada’s Chief Security Architect summarized their X-force Threat Landscape report. This report is put out bi-annually by IBM with the intent of summarizing the threats their unified security division is seeing and the trends the IT industry is facing. The X-Force Threat Landscape Report can be found here.
My girlfriend is taking a Code Academy course and was given the exercise of writing a Rock/Paper/Scissors game. I was pondering it (last night at 1am) and thought you could do something really quick & easy with variable function names in PHP. I wrote the following code:
I have a philosophical/technical comp. sci. dilemma. I’m writing a mobile app that is going to require NoSQL (Mongo) as its going to be dependant on large numbers and be highly transactional. Response time and agile DB development are key. I’m mostly writing this to “think out loud” as they say.
I watched this presentation on big data and fraud prevention in the insurance industry.
I’ve got a data problem. Well, we [Guardian Risk Managers] do. As with most insurance companies, a lot of reporting is done in Excel spreadsheets. We are generating a rolling earthquake aggregate report based on a bordereaux of policies. We were also generating a contract-year report based on those same spreadsheets but realized it was collecting incorrect data as the contracts renewed/changed. I am now in the process of building a full database solution to collect the data, never loose it, and provide automated reporting/analysis.
These are notes from:
Nitesh Dhanjani, Billy Rios, Brett Hardin (2009) ~ Hacking:The Next Generation ~ O'Rielly Media
For obvious reasons server/web security has become crucially important to me recently.
This is the blog of Simon Le Pine. I write about a number of varied topics including my technology startup, the insurance company I work for, my running/climbing/skiing, and the MBA I'm working towards. I organize posts into the following categories to make browsing by topic easy: