The 3 Biggest Realisations I’ve Had About Data Engineering
<p>If you work in data engineering, I think you can agree that you can easily apply that wisdom to a data engineer’s journey: when you think you’ve grasped one thing or solved one problem, something else turns up to flip it all on its head.</p>
<p>Mountains, mountains, mountains — everywhere!</p>
<p>Data issues, endless courses, errors, tools upon tools, boot camps — like I said, mountains everywhere!</p>
<p><strong>Simply put, data engineering is not for the faint-hearted, nor is it boring.</strong></p>
<p>This is true for every project, from the simplest to the most complex. As your experience grows, the more you learn, and the better you get at wrangling data — bending it to your will.</p>
<p>The work you do and the ideas you have will grow more ambitious.</p>
<p>After a few years of trying to figure out this data engineering thing, I’ve realized that data engineering is a balancing act. These are the three realizations I’ve come up with.</p>
<p><a href="https://medium.com/art-of-data-engineering/the-3-biggest-realisations-ive-had-about-data-engineering-5338cde2bfeb">Website</a></p>