Microsoft recently announced they are developing a new programming language designed for Quantum Computing. This (still unnamed) language will come with full Visual Studio integration as well as a Quantum Computing Simulator and will be available before the end of 2017.
Microsoft is also going to release *two* versions of the Quantum Computing Simulator. One version will run locally, the other version will be powered by Azure. The local version of the stimulator will offer up to 32 qubits and will need 32GB of RAM. Each additional qubit doubles the amount of memory required. The Azure version will scale up to 40 qubits.
This is fantastic news for anyone interested in Programming or Technology in general. I’ve been very impressed with Microsoft over the last few years, their Visual Studio development tools, their SQL Server database product, Azure etc. I’ve signed up to the Quantum Computing preview program and am looking forward to playing with their offering in due course.
I’ve long been a fan of Tim Ferriss and his incredible ‘Four Hour Work Week‘ (4HWW) and whilst re-reading it recently I came across a flowchart diagram that neatly captures his approach to ‘activities’. The image was originally created by a reader Jed Wood.
I’ve recreated the flowchart and supplied it below as an image. I assume Tim and Jed will be ok with this, if not it can be easily removed 🙂
The reason I have done this is that the 4HWW is an incredible work, yet its not the easiest to get into in the first place. If the image below interests you in any way you will do well to check out the book and the associated website.
Looking for an App creating for your Windows or Mac Computer? What about an App for your iOS or Android Tablet or Phone, or A Web App? Bespoke, Custom, High Quality Applications.Contact Me
Since the dawn of time I have been using one of the more traditional types of version numbering systems for all my software developments. Recently however I have ‘enhanced’ my methodology and now use something slightly different.
To the outside world not a lot will appear to have changed, the N.N.N methodology will still be used, albeit with a slightly different interpretation. Internally however I will be using the full version numbering system shown below:
Aside from building the release date and time into the version number and swapping out Revision Number for Restricted Release Number, the main benefits to me are building an ascending Feature Number and Fix Number into the version number.
These numbers will only ever increase, regardless of the program status changing from (for example) Version 1 to Version 2. This means that at a glance I can see how features and fixes have been applied to this particular program since day one, without having to go to Version Control for this information.
Looking for an App creating for your Windows or Mac Computer? What about an App for your iOS or Android Tablet or Phone, or A Web App? Bespoke, Custom, High Quality Applications.Contact Us