At the beginning of 2014, I purchased my first-ever MacBook Pro. It was a Late-2013 model with Intel Core i5, 8GB of RAM and 256GB SSD. A superb machine that worked with me for years (till 2020). It could work with me a bit longer but I feel that I need an upgrade.
I never classed myself as a creator despite I have learned to use new things to create something new.
I am more of a person who can use certain skills and available tools to achieve my goal.
Most of us have certainly heard about the requirements for Windows 11, when it comes to hardware. A large number of users were disappointed, checking whether they will be able to update their hardware to the latest system from Microsoft. But… how it is not possible, if it is!
Even though Windows 10 has settled in on our computers, Microsoft has prepared a real surprise for us — Windows 11. In addition, it announced that the update will be free — well, almost.
There are a couple of things that I cannot imagine doing when surfing around the internet. One is RSS/Atom to stay on top of new things on websites that I am watching (I wrote about it in a post: Why RSS still matters in 2021?). The other important thing is a virtual place where I can save a website to come back to it or to read it later.
If you are a person who is just starting to be tech-wise, or you are an experienced user, who on daily basis monitoring various websites to be always up-to-date, you know that social media is not the place where you will look, it’s RSS.
When I started working for my employer, they were using an on-site server and file storage with overnight backups to external drives. Everything was limited by the broadband (internet connection) speed, which in England is quite crazy — business parks rarely have access to inexpensive fibre connections, whereas at home you can get cheap Full Fibre. When things changed (or rather, the company needed to invest in change), we moved everything into the cloud.
We chose Microsoft 365 as our provider.
Once the migration was completed and people had got used to accessing their files in the new way (which hadn’t changed much thanks to the integration of the OneDrive app with Windows, apart from the use of file links), I needed to find a method to back up all files in case of an emergency (or the accidental removal of important files by an employee).
Although Microsoft provides an option to restore files for a short period (typically 30 days), sometimes that may be too short — by the time you notice files are missing, it could be too late. It’s better to have a backup (even an old version of the file) than to have no copy at all.
Without going into costly online backup solutions, or even investing in Microsoft 365 Backup (with its pay-as-you-go billing model), I decided to build an inexpensive and relatively cheap long-term backup system — and I did.
Looking across various internet forums, from time to time I see people asking a support question, and straight away they add their apology for their poor English.
Most of the time, the question, issue or general query is formed correctly. English and not native English speakers can read and understand what the author got on his mind. The addition to showing the author’s weakness in the language (where he is not an English speaker) is unnecessary.
The current price of storage devices fall drastically. Currently, you can buy 128 GB memory stick for as low as £8.99 on Amazon, however I will highly advise you against doing that, and here is why.
When I moved to Hugo with my website, I looked to optimise everything and implement new techniques. Once Safari gain native WebP support back in 2020, I implement WebP following PawelGrzybek.com - WebP and AVIF images on a Hugo website. The post introduced not only how to implement WebP (at the time when Hugo <0.83 haven’t support it), but also shown how to go step further by implementing AVIF.
This method require you to have WebP/AVIF files stored along with PNG/JPG and not relay on rendering them when the site is build.
I was interested in implementing this as well, but after some tests in my environment I decided not to, and here I will explain why (and it is not about browser compatibility — Safari incompatibility).
My site use cookies 🍪. Read more about it on: Cookies Policy.
