Although I played with various coding projects since I was in the 5th grade, for a long time I thought I didn’t have what it takes to be part of the IT world. In college, I didn’t like Math classes because I was put through the ordeal of absorbing superfluous theory. Because of this, many times I thought I just couldn’t pursue a career in IT .
I was never a good fit for regular education, as I’m a more practical person. I like to find and understand patterns and enjoy thinking outside the box. I tried college, but the practical aspects were more appealing to me. Over time, I realized that school does give you a lot of useful tools, but my interests laid elsewhere.
So, my life journey led me to different fields before finally settling for a Front-End development career: I studied Communications, Public Relations, Public Administration, and Computer Sciences. With a bit of luck, I ended up being able to do what I loved. I started work as a freelancer, with jobs ranging from fixing people’s blogs or creating online stores, to developing small websites and small scale applications.
Becoming a Code Master
It all changed for me two years ago when my friend, Előd, convinced me to attend an interview for a Pentalog position. I got the job and since then I couldn’t be happier.
From creating an online shop from scratch, back in the 2010s, to taking the API of a popular game to create several interesting and filterable statistics for me and my friends, and finally reaching to the complex projects of today, I found that my journey towards becoming a professional Front-End developer doesn’t relate anymore to just writing clean code, but also embracing the team spirit attitude.
Supported by my colleagues and managers, I started offering technical assistance, improving developer experience, and sharing knowledge through regular meetings.
Lone Rider versus Team Player
Like many of you, a big part of my professional life I worked as a freelancer. I gained experience in PHP and, of course, the general Front-End environment – HTML, CSS, and JS.
I wasn’t interested in a desk job because I considered myself a lone wolf. I enjoyed the freedom that freelancing offered me, but the work was a bit inconsistent at times, both in quality and quantity. On the other hand, being part of the pack brings unexpected perks.
“People in Pentalog are nice”, said my friend, Előd. “Yeah, really?”, I thought. Well, it’s been two years since I started working here and I’m still surprised by how close-knit we are. My colleagues quickly became great friends.
In the meantime, I learned how to work in a team, and that helped me to provide more reliable code and to solve issues.
What Really Matters as a Front-End Developer
In spite of my background at the time, the position I was offered was that of a Front-End developer, so I swapped my focus, a decision which was very fortuitous!
My regular day starts with a few code reviews, not too many meetings, and the ones I have aren’t generally draining. Then, I just pick up tasks and work on them. The Practices Manager in Cluj office had a large influence on the way I view meetings and gave me a lot of tips on how to handle and moderate them. The part I love the most is when my colleagues require my help or just need to bounce some ideas around.
I am currently working on developing an application that handles coaching sessions. We use Agile methodologies with a few team-specific tweaks. The tech stack is a PHP Back-End with Angular as the Front-End framework of choice. The local management stresses on collaboration which makes most teams a breeze to work with.
From the Local IT Community…
Tech is changing, a lot of developers have fallen prey to developer churn and burnout. It’s hard to keep up with a field like web development where people tend to chase trends far too much. This puts more of a strain on us, as developers, to try to steer our conversations towards a more reliable and more stable tech.
How to Master Front-End Development – Tips from an Experienced Code Advisor:
Methodologies, patterns, and other higher-level concepts are learned far more easily once the foundation is solid.
A more “out-of-the-box” package can save you a lot of time. Don’t fall prey to Not-Invented-Here Syndrome.
Consider things like progressive enhancement, compatibility, and accessibility more.
With a slew of new APIs being added every year, you should take a minute and have fun with Intersection Observer or Ambient Light Events.
Ensure that your tools help you. Ensure that your workflow aids and doesn’t hinder your team’s work.
I think that Web Components will be game-changing by making things more framework-agnostic. I’ve been dreaming of these ever since I read my first.
I don’t really like to chase trends, I choose my tools by their function rather than form.
Hype isn’t a good metric by which to pick your frameworks, but rather their usefulness and their applicability in a given team/project.
Read more career stories: