<p>Hello world! This is my first-ever blog post. Cool, right?</p>
<h2>Who's behind the keyboard?</h2>
<p>That would be me, Szymon, a frontend software engineer. Recently, I have joined Microsoft to work on an internal monitoring &#x26; telemetry platform. Sounds familiar? Before that I was developing a large-scale SaaS observability (yep, monitoring) platform at Sumo Logic. It definitely seems like coding interactive dashboards and charts is my thing!</p>
<p>Lately, I've been having many thoughts and no place to share them. That's why I decided to build my personal website.</p>
<p>Interestingly, this isn't its first version. In fact, if you dig into commit history 😁, you will see I had a similar website some time ago. Life got busy, and I moved on, but the source code stayed on GitHub. I thought, why not give it another shot? So, armed with the lessons I've learned over the years, here we are again.</p>
<h2>The old vs the new - Static Side Generation</h2>
<p>I consider Static Site Generation a must for static sites which don't change much over time. It minimizes data transfer between the client and the server. It also paves the way for static hosting - a more cost-effective &#x26; faster way of hosting React apps than using Docker containers.</p>
<p>Old version of my website used <a href="https://www.gatsbyjs.com/">Gatsby</a> for SSG. Now it's all about <a href="https://nextjs.org/">Next.js</a>. Why make the jump?</p>
<p>Well, Next.js is rapidly becoming the go-to React framework. With the release of Next.js 13 and its Server Side Components, it's now the talk of the town in the frontend space. I wanted to dive in, see its benefits first-hand, and perhaps refresh some of the features I might have overlooked.</p>
<p>That said, it's not just about the tech. While I've observed fairly similar build times and other key metrics with both, I must say - and this is purely subjective - the developer experience feels more streamlined on Next.js compared to Gatsby.</p>
<h2>What can you expect?</h2>
<p>I'll mostly post about the technology world. Expect deep dives into frontend topics, handy programming tips &#x26; tricks, and occasional articles on self-development. However, I'm not (currently 😁) aiming to be next <a href="https://blog.pragmaticengineer.com/">The Pragmatic Engineer</a> - my posts will be somewhat shorter!</p>
<p>Every so often, I'll also write about my passions. Right now, that's motorcycles &#x26; cars, sci-fi literature. But hey, these change!</p>
<h3>How often?</h3>
<p>I'm aiming for biweekly posts, but don't be surprised if something pops up sooner (or perhaps a bit later).</p>
<h2>What's next?</h2>
<p>I have plans for a few upcoming posts. I want to create a detailed write-up on coding a blog from scratch (part 0 - preparations, decisions, architecture; part 1 - actual implementation, tips &#x26; tricks; part 2 - transitioning to Server Side Components).</p>
<p>Apart from that, I recently did some job interviews and helped some friends prep &#x26; secure jobs. I have many insights on crafting resumes/CVs and preparing for interviews. I will certainly share these here.</p>
<h2>Other places</h2>
<p>I'll be cross-posting each piece on my <a href="https://dev.to/szymonpulut">dev.to</a> blog. I'll also share updates on my <a href="https://linkedin.com/in/szymonpulut/">LinkedIn</a> with each new post. If you're into the old-school vibe, there's always the <a href="https://szymonpulut.com/feed.xml">RSS feed</a> to keep you in the loop.</p>
<h2>To my Sumo friends</h2>
<p>I want to say a heartfelt thank you to all my colleagues at Sumo Logic. Working in such tech-savvy environment has been an incredible experience and learning opportunity. However, this would've been all nothing if not for all the amazing people at Sumo. Thanks! I'm confident our paths will cross again in future 😉.</p>


Keyword frontend software engineer

Hello World! Welcome to my new site!