If you’re subscribed to my Twitter feed, you might have noticed that I don’t post as much content as before. It was a good place, once, but I cannot condone the new management and most importantly, their handling of misinformation - or lack thereof. My reasoning is that if I continue posting technical content there, people will continue using it; if nobody posts such content, regular users will leave the site. You might agree or not, but since it’s my content, it’s now how I’ll use Twitter.
To compensate, I’ve created this newsletter, which is more or less provides the same content as I wrote on Twitter. I’l try to publish a weekly summary. Note that I still publish on Mastodon and LinkedIn.
Without further ado, enjoy the first Java Geek weekly!
- BDD - Cucumber, Specflow and Gherkin are not required!
-
The title says it all - in a short easily digestible 5-minutes video.
- Jacoco Agent Measures Code Coverage for Any Test
-
Jacoco is very well integrated into JVM test frameworks. But now, you can check your coverage outside of your tests too!
- Why Your OpenAPI Spec Sucks
-
TLDR:
- You’re still using Swagger. Development has stopped on Swagger but continues on OpenAPI. Hence, by using Swagger, you can’t use the latest and greatest.
- You’re not using components. DRY.
- You’re Not Using Descriptions, Examples, Formats, or Patterns. Help your users use your API
- Bridging Silos and Overcoming Collaboration Antipatterns in Multidisciplinary Organisations
-
Key Takeaways:
- Too many organisations are moving towards more fractured working that focuses on specialisms over collaboration
- Three collaboration antipatterns are: one person across many teams, product vs. engineering wars, and x-led organisations
- Collaboration antipatterns lead to uneven power distribution and decision making
- Unchecked, these antipatterns will increase professional protectionism leading to in-team silos, which makes it difficult to solve wicked problems
- Creating enabling structures, focusing on transdisciplinary teams, and seeking to find where people naturally crossover will enable effective collaboration
The common problem of such posts is that though the describe issues and provide solutions, most shareholders already know the solution. The biggest issue is that organizations carry inertia and change management is hard.
- Upsert in SQL
-
The many (many!) ways to insert new rows in table or update rows if the primary key already exist; from the not working at all, via the dangerous, to the standard
MERGE… that behaves differently depending on the server. - Last but not least, lhe last focus that I wrote was on Rust
-
While it’s not that recent, I believe it’s still good enough if you want to start your 🦀 journey.