I’m a big fan of anything which makes my life easier, and when it comes to web development and styling things, SASS ticks just about every box I need. I’m not going to go into what SASS is, but you can see what it’s all about over at sass-lang.com. (PRO TIP, don’t go searching “get sass” with safe filters turned off, especially on an office network).
Having just released version 5.1.4 of my website which brought in the ability to contact me, I thought about all the other features I want to build into this site. I debated not putting that sort of detail on here as it might indicate how feature lacking this actually is, but then I realised that I’ve got nothing to hide. This is a personal site, and the whole build is an education for me. The code is never intended to be released for general use (it’s very bespoke and not even close to a CMS). Putting them on here also means I have things to look forward to.
Not too long ago I looked at working with HTML5 Canvas. It’s a great little thing, and I am working on some posts to explore it more and what it can do. However I have just ran into a problem with it which others have found, and something which is going to trip people up at some stage. It’s not responsive. This means that when you put your canvas work onto the web and view it on different devices, it’s not going to scale with the viewport. Nightmare.
I spend quite a lot of time on StackOverflow, both in terms of finding answers for something I need, and also for helping people out with their issues. One question I see quite a lot is around security permissions for creating files on the server. Usually these questions are for PHP, and as such I’m going to address this post as if PHP developers are sensible and deploy on a LAMP stack.
More often than not, I see the posts and they have something along the lines of the following:
I’ve set the permissions to 777 but it’s still not working
It makes me want to turn into the Hulk and smash things.
Following the news this week that South Wales Police have been hit with a fine of £160,000 for not reporting missing data for two years, I got thinking about the importance of keeping data secure.
The case itself is an extreme example of why you should keep data secure. You really don’t want evidence in a very serious case just going walk about. Beyond that, looking more towards home personal data, there are many good reasons of why you want data to be secure, and many ways of doing it.
I’ve always found version numbering interesting, and wondered how they are thought up by companies. With Mozilla jumping Firefox from 3 to 30+ in a very short space of time (about 3 years, Google getting Chrome from 1 to 41 faster than you can say “Is this the latest version”, and Microsoft going from IE4 to IE11 in around 20 years, it doesn’t lead to a simple answer. I did a bit of research, and found that there isn’t a hard and fast rule on how to do it. Jeff Atwood over at Coding Horror covers this better than I ever could in his post “What’s in a Version Number, Anyway?”
In a nutshell, people don’t care about version numbers.
‘Tis the season for change, it seems. And after a lot of chanes with the site and jobs, I’ve had to make yet another change. Namely to my web-hosts.
I orders a VPS with 1 and 1, configured it and set this domain to be transferred to them so everything could be working nicely, just as I want it (and so I could play around with server management). After a week of waiting for the domain to be transferred I thought I would get in touch with them to see whether I had made a mistake, or when the domain was going to be transferred. I got the following response from them: