<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering on x00/</title><link>https://fleax.codeberg.page/categories/engineering/</link><description>Recent content in Engineering on x00/</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 26 Apr 2026 07:52:44 +0200</lastBuildDate><atom:link href="https://fleax.codeberg.page/categories/engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>openQA Scheduler Design</title><link>https://fleax.codeberg.page/2026/04/openqa-scheduler-design/</link><pubDate>Sun, 26 Apr 2026 07:52:44 +0200</pubDate><guid>https://fleax.codeberg.page/2026/04/openqa-scheduler-design/</guid><description>&lt;p&gt;When we say scheduling in openQA we are talking about the trigger which runs one or more tests in the framework.&#10;Usually we use &lt;code&gt;isos post&lt;/code&gt; to refer to the this - when we call them by terminal. the &lt;code&gt;isos post&lt;/code&gt; in fact, is the API&#10;which calls the endpoint which says to the according controller to perform the action. And it looks like this&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;❯ openqa-cli api --host http://localhost --apikey &amp;lt;apik&amp;gt; --apisecret &amp;lt;apis&amp;gt; -X POST isos&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#ae81ff"&gt;400&lt;/span&gt; Bad Request&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Error: missing parameters: DISTRI VERSION FLAVOR ARCH&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This is one way, and as it is shown above any job requires some particular&#10;variables, DISTRI VERSION FLAVOR ARCH but it will also need ISO at the minimum&#10;or/and BUILD GROUP even.&lt;/p&gt;</description></item><item><title>Every career path needs clarity</title><link>https://fleax.codeberg.page/2026/02/every-career-path-needs-clarity/</link><pubDate>Sun, 22 Feb 2026 19:34:34 +0100</pubDate><guid>https://fleax.codeberg.page/2026/02/every-career-path-needs-clarity/</guid><description>&lt;h2 id="reasons-which-blocks-productivity-and-good-engineering"&gt;Reasons which blocks productivity and good engineering&lt;/h2&gt;&#10;&lt;p&gt;Engineers tries constantly to solve problem. Their value depends in the&#10;productivity measures and good engineering. I believe, most of us spend a big&#10;amount of time thinking about all the ways to improve and what blocks them.&lt;/p&gt;&#10;&lt;p&gt;Somehow, the toll is expensive and the mental energy required is significant&#10;burden of being a software engineer. I see part of the problem at the&#10;processes of the daily interactions required to deliver a task or a project.&#10;The way of communication and the unknown unknown is one perspective. And&#10;another the philoshophy which the working environment embrace. There might be&#10;a lack of proper engineering approach — something so common when a team is&#10;trained to just do things rather than think and prepare the project.&lt;/p&gt;</description></item><item><title>Every career path needs clarity</title><link>https://fleax.codeberg.page/2026/02/every-career-path-needs-clarity/</link><pubDate>Sun, 22 Feb 2026 19:34:34 +0100</pubDate><guid>https://fleax.codeberg.page/2026/02/every-career-path-needs-clarity/</guid><description>&lt;h2 id="reasons-which-blocks-productivity-and-good-engineering"&gt;Reasons which blocks productivity and good engineering&lt;/h2&gt;&#10;&lt;p&gt;Engineers tries constantly to solve problem. Their value depends in the&#10;productivity measures and good engineering. I believe, most of us spend a big&#10;amount of time thinking about all the ways to improve and what blocks them.&lt;/p&gt;&#10;&lt;p&gt;Somehow, the toll is expensive and the mental energy required is significant&#10;burden of being a software engineer. I see part of the problem at the&#10;processes of the daily interactions required to deliver a task or a project.&#10;The way of communication and the unknown unknown is one perspective. And&#10;another the philoshophy which the working environment embrace. There might be&#10;a lack of proper engineering approach — something so common when a team is&#10;trained to just do things rather than think and prepare the project.&lt;/p&gt;</description></item></channel></rss>