The word DevScale has been rattling in my head for a while now. With my increasing interest in Raspberry Pi, FreeBSD, and Erlang -- combined with the rise in Internet of Things (IoT) -- the word DevScale has started taking a bit more shape.
West Indies are World T20 Champions yet again. Only this time they won in three different tournaments: Women, Men, and Under-19. This is unprecedented success for any country, let alone a collective of countries that form a single team.
Automated test suites must be packaged for installation and distributed just like your other build artifacts. They are not some special things that live in a code repository (repo) separate from the rest of your code.
My team was writing tests and keeping them all in a git repo. The repo would be cloned and then PyTest would run these tests. All users of tests - from developers to Continuous Integration (CI) and everyone else in between - would run steps akin to:
git clone firstname.lastname@example.org:username/testrepo.git cd testrepo git checkout main pip install -r requirements.txt py.test tests/
This worked for a while but was not a good fit as time progressed for these reasons:
Before going into why FreeBSD is now my preferred OS for learning UNIX let's review why I used Linux for a long time.
I am a Pythonista by trade and passion. It was the first language - after trying C, Java, and Perl - that made me feel productive while loving the (admittedly beginner-crappy) code I wrote. I don't claim to be a Python expert but I have worked with it long enough to be well versed in it for most use cases. And yet I feel like trying my hand at another language.
I have dithered on the decision to pick a language and stick with it. My interest has been pulled in three directions over the past couple years: Go, Erlang, and Rust. I even tried my hand at each language for a couple days before life happened.
I have an ever present restlessness when it comes to figuring out what to learn next. It's a source of agitation and sometimes stress. It's even more unhealthy when I feel that way at times when I can do nothing about it, especially during some much needed downtime.
I have come across various myths about free and open source software or as some call it FOSS. Some of the more prevalent are:
- FOSS is gratis and it is not FOSS if it is not gratis
- It is not FOSS if it has a Cathedral development process
- Creators and maintainers are obligated to include user patches in upstream source tree
- Creators and maintainers are obligated to provide gratis support to all users on the users' schedule
- Copyleft code is free software and permissively licensed code is not
- Free software begins and ends at Linux or GNU (to some extent)
I have read The Rise and Fall of the Operating System by Dr. Antti Kantee as well as Unikernels are unfit for production by Bryan Cantrill. As an outsider I have much to learn about Unikernels. I also don't have a horse in the race yet. For me this is a very academic debate on the pros and cons, today and in the next decade, of Unikernels.