jennstrater

I haven’t talked about this for various reasons. From the comments I’ve received in the last week, it seems like continuing to hint at what happened rather than talking about it, and embarrassing people(myself included) has actually made the situation worse so here’s a collection of everything that happened from my point of view. The First Blog Post (Early March) So let’s begin with a blog post I published back in March.  The version there right now is not the original.  Originally, I had included a case study based on a conversation from Twitter about the low number of women who were applying at Gradle, Inc. I thought I was helping by showing that it wasn’t just a problem with Gradle, but in the entire community and trying to think of reasons why the numbers might be so low. Within 45 minutes of posting it, I had three different people harassing me via various communication methods about how it might be viewed as an attack on Gradle, Inc.  I had a lot of respect for the members o

Note: I'm publishing this now, even though I wrote most of it over a year ago when I was working on the Diversity 101 series. At the time, I was really burned out. I was struggling with issues at work and in the community, and the feedback I got from some of my readers was that they felt there was nothing they could do to help improve the conditions since they weren't doing anything wrong and every time I brought up the numbers, it was just depressing. The sentiment is still true today, but perhaps we can revive the effort and work together to change it. Introduction In short, it shouldn't be. The purpose of diversity organizations isn't to create an unfair advantage but rather for equality. In fact, I get rather annoyed when individuals or articles claim "Girls are better at .. X". I fall outside many of the generalizations about my gender and find that most stereotypes have little to do with that and more to do with personality traits or confounding v

After many recent announcements about the abuse of women at different companies in our industry, I saw a thread on Twitter about encouraging and supporting women in tech.  There was one aspect of a tweet though that got me thinking about the percentage of women applicants at several companies who use Groovy and related technologies.  My first thought was that maybe it was a lack of applications in general or perhaps even an HR screening problem so I started to look for how many women might apply for a job based on prior knowledge and contributions to open source projects. For each project, I looked through the list of top contributors on Github. As I searched through the list, I saw a depressing pattern.  My prior work with company data shows that only about 5% of Groovy developers are women. That number is consistent with conference attendance at Groovy conferences. I also know that when we look at other programming language communities, we typically see an even smaller number

During my talks last year about Spring REST docs, I was frequently asked if I could use Spring REST docs to document other APIs. I always thought it was possible, but now I have a working example.  I was able to configure RestAssured to poll a public demo API,  JSON Placeholder, and use those snippets to form API docs. The demo repository is available at  https://github.com/jlstrater/spring-boot-restdocs-public-api-example , and the docs are published at  https://jlstrater.github.io/spring-restdocs-public-api-example The rest of the example is similar to any other Spring REST Docs example, but the configuration is slightly different: Figure 1: RestAssured Configuration In figure 1, the third line specifies the URL to run against.  This will also affect the generated snippets as seen in Figure 2. This shows how it will use the real address instead of localhost like it would for a local example. Figure 2: Example Snippet with JSON Placeholder Address Conclusion This co