楕円曲線暗号(Elliptic Curve Cryptography)の話なんかもでてきて、大学のころにやったことも含まれて良い感じだった。主にはセキュリティ関係のところを想像しながら聞いていた。
I bought the book of Practical Network Automation when the book was discount.
The main topic is Ansible and Python code for network engineers who have few experience for Python/PowerShell. I expected more programming related stories, but it is a bit fundamental stuff.
BTW, when I saw some word such as “Software Defined Network”, “Open Flow”, etc, and it made me nostalgic… (My previous company and sort of my university age.)
So long ago, I tried to monitor iOS performances using instrument commands. But I gave up once because of host machine’s load.
But https://github.com/appium/appium-xcuitest-driver/pull/637 is created and that is awesome…
I just remember seeing the PR and I’ve published this article in my memory…
I know of Kubernetes, but I have few experience for that.
But the kubernetes community has interesting tutorials.
I can imagine the architecture and how to work.
I guess I’ll use them and Istio though.
One day, I encountered Mastering Blockchain. When the book was available with some discount, I purchased it and I finished reading it lately.
I was able to enjoy reading the book since I have some knowledge of distributed system especially the Byzantine General Problem in theoretical aspect and cryptography.
We can lean not only the Blockchain and its implementations but also the more fundamental knowledge such as what distributed system is and cryptography. It’s essential thing than concrete implementations. If the implementation is disrupted, you can implement other way or new way because you know the fundamental stuff.
I strongly feel again. Lately, academical/scientific stuff and industrial stuff become closer. For me, it’s very exciting things though.
I left my thought for the book which I’ve posted on Twitter.
I touch [Flutter]some thoughts for the Flutter (v0.1.0) before. And this time, I tried to run the app with Appium.
We can run UI test with Appium as well as native apps. But Flutter apps have no accessibility identifier and customised resource id. So, it’s quite difficult to implement robust test automation scenario so far.
Probably, Appium is easy to kind of automation than Espresso/XCUITest so far.
Lately, ML related technologies step into industry section and many engineers challenge to integrate them into their services.
The movement also comes into test/quality industry. I also have some ideas to use them though.
A few weeks ago, I found a service which named mabl which provides ML-driven test automation service. The service run tests using ML technologies, not test ML technologies itself. I try the service recently and put some results and thought here.
The target URL is simple, https://www.google.co.jp
I don’t do anything except for input the URL into a particular area. Then the journey started and I just wait for a while.
The site looks crawling the target site and checking all links. The followings are the results. I can see some error message which may be broken links.
In test section, we can see some test cases and its results. Their test cases are generated automatically. According to the titles and some logs, the test aims to collect available transitions, it means available links and some data.
We also can see train section. I guess the section is a teacher in ML world. So, we running test iteratively, then the ML logic learns the test target and they will be able to conduct automated test efficiently.
I believe if we run test iteratively and collect test data, cases and results, the ML will be more inteligent and they can run test automatically effective.
Anyway, it looks promising and I’d love to try my thought using ML technologises.
I was interested in the book for a long time. The O’Reilly has published a part of the book and I also read it to know the book.
Just I read only one section. I couldn’t more monitoring stuff in this book, but I got some antipatterns.
- Anti-Pattern #1: Tool Obsession
- Anti-Pattern #2: Monitoring-as-a-Job
- Anti-Pattern #3: Checkbox Monitoring
- Anti-Pattern #4: Using Monitoring as a Crutch
- Anti-Pattern #5: Manual Configuration
When I read the above sections, I can imagine why they are the antipatterns. Some of them have similar issues creating the autonomous team.
In short, to scale the system, we must make the system automate. And the book should have many practices of the monitoring.
Anyway, we should take care monitoring stuff as well.