dsuurlant

a simple dev blog

This article was first published on dev.to on December 22nd, 2023.

In 2013 I attended my first developer conference, the Dutch PHP Conference. I had never been to any event like it and found it invigorating. I made connections with devs that I still have to this day, I went home feeling inspired and motivated to do more, do new things. And more importantly, I had now in-person seen just how few women showed up at such events. Whether that was an accurate representation of women in tech, or if it simply meant that women didn't have enough of a personal or professional budget to attend, I don't know. What I did know was I felt very strongly about increasing the visibility of and enfranchising women in tech.

Read more...

I founded a DEI team for our company. About a year and a half ago, I felt so proud of this accomplishment — after campaigning for it and working together with my dev team lead, and making a case to the whole management team, we were approved for starting a DEI team with its own budget. I thought this was a great step for a relatively small company — a way to make diversity, equity & inclusion a part of our DNA, a part of our ‘normal’ rather than an afterthought. It would allow us to tackle diversity from the get-go, making sure that our employee demographics would match up with our worldwide clients and ambition. Diverse companies boost employee happiness, cooperation, and overall profitability. The statistics are pretty clear on that. Or, they were.

But in recent months, I became aware that ‘DEI’ is used as a slur in conservative circles, something to fear and hate, going the same route of appropriating progressive language to corrupt it into a symbol to bash and mock, like ‘woke’. Tale as old as time, but accelerated by social media. For a certain chunk of the population, DEI is now synonymous with something bad. And now a report has come out that ties DEI with negative outcomes for company culture, too.

I made a DEI team… but was it a mistake? Can I hold on to this accomplishment, or should I change course?

Read more...

This article was originally posted on Medium.com on May 27th, 2020.

A friend of mine recently asked me to review a job posting for the company he works for; they are trying to attract a more diverse workforce. As a woman who works in technology, I’ve read my share of red-flag-raising job openings, and I’ve had to deal with plenty of situations that would send anyone who doesn’t fit the white straight cisgender middle-class dude stereotype of a developer running.

It wasn’t until I started to review this particular text I realised I had a lot of opinions about this. And what better to do with those but compile a list of what (not) to do?

Read more...

Searching for a distraction-free, simple, yet effective blog editor/hosting platform I landed with write.as.

I have started, and abandoned, more Wordpress blogs than I can remember, so this time around I knew that wasn't the right choice. I always get overwhelmed by all the options and each time I want to write the perfect article with all the images and links and comments and categories and tags and taxonomies and...

So, it wasn't going to be WP.

Then when searching for “simple blog site software” I found a lot of suggestions for static site generators, such as Grav and Hugo. The thing is when I'm writing I don't want to think about Markdown, or committing code, or builds, I certainly don't want to set up any GitHub Actions or Docker containers.

I just want to write!

Write.as is based on WriteFreely which is Open Source, so if I'm ever inclined, I could set up my own instance — or join another one (though Wordsmith isn’t open to new accounts at the moment). It’s got RSS, Email updates, a custom domain, even a connection to the Fediverse.

This is the free trial, so if I like it I do have to pay for it eventually — but compared to the cost of hosting it myself and the investment in time for setup and maintenance, I think it kinda levels out. It’s not that I can’t set up my own server, deployment, pipeline, and all that. It’s just that I really don’t want to. Writing comes from another part of my brain, I guess. Not that DevOps isn’t creative in its own way.

That’s all to say — this is my new dev blog. Will I keep this one updated? Stick around and we’ll find out together!

Enter your email to subscribe to updates.