DEV Community: Andy The Web Dev Queen

3 reasons why I love Doctrine

Andy The Web Dev Queen — Fri, 21 Jun 2024 14:33:04 +0000

Doctrine is a powerful Object-Relational Mapper (ORM) for PHP, widely used in the Symfony framework but versatile enough to integrate with various other PHP applications. Personally, I use it with the PHP framework Nette which is widely used in Czechia where I'm based. Here are three reasons why I love Doctrine:

1. Handling Database Entities as Objects

One of the most compelling reasons I use Doctrine is its ability to handle database entities as objects. This object-oriented approach to database interaction offers several advantages:

Simplified Code: With Doctrine, I can work with database records as if they were regular PHP objects. This eliminates the need for complex SQL queries and instead, I define entities as classes and map them to database tables. This not only makes my code more readable but also reduces the likelihood of SQL injection attacks.

Seamless Data Manipulation: Doctrine allows for seamless data manipulation through methods on entity objects. For example, instead of writing an SQL query to update a record, I can simply modify the properties of an entity and persist the changes. This abstraction layer makes my code cleaner and more maintainable.

Relationships Management: Handling relationships between entities (like one-to-many, many-to-many, one-to-one, etc.) becomes really straightforward with Doctrine. By defining relationships in my entity classes, I can effortlessly navigate between related records, making my data model more intuitive and reflective of the actual business logic.

2. Events

Doctrine's event system is another feature that significantly enhances its flexibility and power. Events in Doctrine allow me to hook into the lifecycle of an entity and perform operations at specific points in time.

Doctrine provides a set of predefined events such as prePersist, postPersist, preUpdate, and postUpdate. These events give me hooks to execute custom logic before or after an entity is persisted, updated, or removed. This is particularly useful for tasks like logging changes, sending notifications, or validating data before database operations. For example, I use events for createdAt and updatedAt parameters. This way I can keep the business logic decoupled from the entity operations. This separation of concerns leads to a more modular and maintainable codebase, as my entities remain focused on data representation while the event listeners handle additional logic.

3. Command Line Interface (CLI)

Doctrine's CLI is a powerful tool that streamlines database management tasks and provides numerous commands that simplify the development process. Creating, updating, or removing entities has never been easier and it saves me a lot of time.

Conclusion

Doctrine’s ability to handle database entities as objects, its powerful event system, and its comprehensive CLI tools make it an exceptional ORM for PHP developers. I cannot imagine a development without Doctrine anymore. Its features not only enhance my productivity but also contribute to writing clean, maintainable, and efficient code. Whether I am building a small application or a large enterprise system, Doctrine provides the tools and flexibility needed to manage my database interactions effectively.

Do you use Doctrine in your projects? And why?

But you don't look like a web developer

Andy The Web Dev Queen — Wed, 19 Jun 2024 16:23:02 +0000

When you think of a web developer, what comes to your mind? Most people from my private life outside technology would describe such human as a man, often wearing glasses, hunched over a laptop in a dimly lit room, surrounded by empty coffee cups and energy drink cans. Maybe he’s an introvert, someone who’s more comfortable with code than with people, lacking in social skills and physical fitness. This stereotype is so ingrained in our collective consciousness that anyone who doesn’t fit this mold might be met with surprise, or even skepticism.

“But you don’t look like a web developer.”

This phrase is something I hear almost every time I introduce myself as a web developer (sometimes even in the STEM environment, but mostly in private life). You see, I am a web developer, but I don’t fit the outdated stereotype. I’m a woman, nearly 30 years old, in good shape, and I like sports. I take pride in my appearance, use make up, get my nails done, and care for myself because I want to be attractive. Yet, my abilities and passion for web development are no less than anyone else’s.

The image of the "ideal" web developer is not just a harmless stereotype; it’s a narrow definition that excludes the vast diversity within the tech community. The reality is that web developers come from all walks of life. They are men and women, young and old, extroverts and introverts, athletes and artists. Our skills and passions shouldn't be measured by our appearance or lifestyle choices, yet they still do.

In fact, diversity in web development brings about a richer and more creative environment. Different perspectives lead to innovative solutions and more user-friendly products. When we cling to outdated stereotypes, we not only limit our view but also discourage many talented individuals who might feel they don’t belong.

For me, being a web developer is about problem-solving, creativity, and continuous learning. It’s about staying curious and pushing the boundaries of what technology can do. It doesn’t require me to sacrifice my social life, neglect my physical health, or conform to an image that doesn’t represent who I am.

I want to challenge the notion of what a web developer should look like. Next time you meet someone in tech, resist the urge to judge their capabilities based on their appearance. Instead, focus on their skills, passion, and the unique perspective they bring to the table.

In a world where technology is constantly evolving, so too should our understanding of those who create it. Let’s embrace the diversity within our community and move beyond the stereotypes. After all, it’s not about how we look, but what we can build together.

What it's like to be a woman developer

Andy The Web Dev Queen — Fri, 14 Jun 2024 15:46:24 +0000

As a woman developer, my journey in the tech industry has been a blend of unique challenges and rewarding experiences. Despite numerous initiatives promoting gender diversity, women, especially those in backend development roles, remain underrepresented. Here’s a glimpse into my personal experience navigating this male-dominated field.

The landscape of women in tech

Before I even entered the tech world, I was already aware of the gender imbalance there. Breaking into this field was surrounded by societal stereotypes and a historical bias against women in STEM. Even my parents questioned my decision to study IT at the university when I told them for the first time. Even when I was A student in high school and there was a 99 % probability I would attend some university, they thought I would choose a different field, some "more feminine" field, such as medicine, law, or economics. They were kind of "shocked" by my choice of IT being the field of my future career. It's important to say that this was in 2014, 10 years ago.

I would like to believe our society has evolved in the last 10 years but the data claim the opposite. Over the past decade, the ratio of women in tech positions has improved from around 20% to nearly 30%. While progress has been made, significant disparities remain, especially in specialized technical roles and leadership positions.

The team dynamic

Thanks to the low ratio of women in tech, joining only male tech teams has been a common experience for me. I usually was the only woman on the team. Interestingly, I’ve found that my presence often brings a positive shift in team dynamics. I don't think it was personal since I am not special in comparison to any other woman in the world. I think that they were cheered up just by having 'some' feminine energy around them. Many of my male colleagues express genuine happiness and enthusiasm about having a woman on the team. This isn’t just about gender diversity on paper; it’s about the fresh perspectives and diverse approaches I bring to problem-solving and project management. Our team environment becomes more collaborative and inclusive, which benefits everyone involved.

Intellectual attraction

One of the more intriguing aspects of my career is the intellectual curiosity I often spark among my male colleagues. Many men in the tech industry seem genuinely interested in women who can engage in technical discussions and share their expertise. This mutual respect for knowledge and skills has led to stronger professional relationships and a deeper appreciation for diverse viewpoints within the team.

Challenges and biases

However, being a woman in tech isn’t without its challenges. I’ve faced implicit biases and stereotypes that have sometimes created obstacles in my career. There have been moments where I felt the need to prove my technical skills and knowledge repeatedly, more so than my male counterparts.

Conclusion

Being a woman developer in a male-dominated industry has its unique set of challenges and rewards. My journey has taught me the importance of resilience, support, and the power of diverse perspectives. Despite the difficulties, the impact that women like me have on tech teams and the industry as a whole is undeniable. By continuing to support and promote gender diversity in tech, we can create a more inclusive and innovative future. And personally, I think that men like working with tech-based women. As more women enter the tech workforce, our contributions not only enrich the industry but also pave the way for future generations of women developers.