10 August, 2018

Ubiquiti UniFi

Recently acquired a Ubiquiti UniFi UAP-AC-PRO wireless access-point.

PoE+ required, the USB-interface is misleading, it does not power the unit at all.

20 July, 2018


1987 ZipStick® joystick. This yellow buttoned joystick uses micro-switches and has a triple fire action, and is THE best joystick I have ever used / abused. It can withstand practically ANYTHING!

Got hold of a near-mint copy (a few scratches on the housing and dirt beneath the screws), which tested OK and working on an Amiga A600 + Amiga A1200. SCORE!

Amiga-gaming will be a pleasure with this accessory! ;) :D

18 May, 2018


I was reading this article a couple of weeks ago, and sure was tempted in getting one...

Yes, I am a weak individual to g33k-marketing, I know this... 😅

So... I ended up shelling out the wet stinky, and it is on its way in the post 😋

Ubuntu on Nintendo Switch
Yes. Indeed. It will be used to do what its supposed main function is... But, I will also tinker and experiment with this gadget to my hearts content 😅 😎

Update Monday, May 28th:

Nintendo Switch Red/Blue JoyCons

Nintendo Switch + 8Bitdo NES30 Pro Bluetooth gamepad

02 May, 2018

Continuous Integration and Deployment

Continuous Integration is the practice of constantly merging development work with a Master/Trunk/Mainline branch so that you can test changes and test that those changes work with other changes. The idea here is to test your code as often as possible so you can catch issues early on. In the continuous integration process, most of the work is done by an automated tests technique which requires a unit test framework. It is best practice to have a build server designed specifically for performing these tests so your development team can continue merging requests even while tests are being performed...
Yes, automation here is key.
...Continuous Delivery is the continual delivery of code to an environment once the developer feels the code is ready to ship - this could be UAT (User Acceptance Testing), staging or production. The idea behind continuous delivery is that you’re constantly delivering code to a user base, whether it be QA or directly to customers for continual review and inspection. Although similar to continuous integration, continuous delivery differs because it can feed business logic tests where unit tests are unable to catch all business logic, particularly design issues.

...Continuous Deployment is the deployment or release of code to production as soon as it’s ready. There is no large batching in staging nor a long UAT (User Acceptance Testing) process before production. Any testing is done prior to merging to the Mainline branch and is performed on production-like environments. The production branch is always stable and ready to be deployed by an automated process. The automated process is key because it should be able to be performed by anyone in a matter of minutes (preferably by the press of a button).
And after all that, log-auditing after deployment; checking key metrics if they are influenced negatively or positively by change(s).

In the ideal workflow, the entire process could be automated from start to finish:

  • Step 1: Developer checks in code to development branch.
  • Step 2: Continuous integration server picks up the change, merges it with Master/Trunk/Mainline, performs unit tests and votes on the merge to staging environment based on test results.
  • Step 3. If Step 2 is successful, developer deploys it to the staging environment and QA tests the environment.
  • Step 4. If Step 3 passed, you vote to move to production and the continuous integration server picks this up again and determines if it’s ok to merge into production.
  • Step 5. If Step 4 is successful, it will deploy to production environment. 

This process varies slightly based on needs, requirements and approaches.

24 April, 2018

Need for security-professionals in Norway

Yes, it's been an often-discussed topic in Norwegian media in later years:

"Lack of security-professionals."

Well, as commented in this (Norwegian) article, BY a security-professional; there seems to be a lack of security-oriented IT professionals, but, not because they aren't there at all. They are. What is seriously lacking in this scenario, is competence in recruiting firms looking for this kind of competence. Always has been.

Computer-security is not a fixed-set field, AT ALL. Even though a lot of so-called "professionals" seem to be stuck on the idea that it is.

Serious professionals wanting to work in this field on the other hand, are (often) painfully aware of what it actually entails to do so:

  • constant refreshing on networking- / computing- / vulnerability-security in IT
  • vulnerability-monitoring of often-used software in the company
  • a simple awareness of the fact that: nobody is ever 100% secure
Computer-security is a weight-battle; does the securing of something vulnerable affect normal operations? Or, is the fix / security-measure absolutely needed for normal operations? These are everyday obstacles a security-professional has to deal with on a regular basis, so they have to be quite flexible on expanding their knowledge-base, and often.

These points are often completely missed by recruiters. They don't look for ability / knowledge / flexibility, they often tend to only look at academic degrees (preferably multiple(!)), gender, published articles / blog-posts and other non-related (and often quite unrealistic) demands for the position(s) in question.

Then, they complain about not finding any candidates for their outrageous requirements.

Seriously, re-define your demands / requirements to a more realistic degree, maybe you'll find a competent person to do the job. But you most certainly will NOT find the dream-candidate with the kind of demands currently set as standard.

17 April, 2018

when PIGS FLY!!

"After 43 years, this is the first day that we are announcing, and will be distributing, a custom Linux kernel," Microsoft President Brad Smith said

Yeah, well, OSS / Linux won...