<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering Mindset on x00/</title><link>https://fleax.codeberg.page/series/engineering-mindset/</link><description>Recent content in Engineering Mindset on x00/</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 22 Feb 2026 19:34:34 +0100</lastBuildDate><atom:link href="https://fleax.codeberg.page/series/engineering-mindset/index.xml" rel="self" type="application/rss+xml"/><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>