Over a million developers have joined DZone.

The Best of the Week (Mar. 22-29): DevOps Zone

DZone's Guide to

The Best of the Week (Mar. 22-29): DevOps Zone

· DevOps Zone ·
Free Resource

Open source vulnerabilities are on the rise. Read here how to tackle them effectively.

In case you missed them, here are the top posts from the DevOps Zone this week--as chosen by yours truly. This week: Preserving type safety in functional programming, why Johnny can't do TDD (remember the book "Why Johnny Can't Read"?), reporting custom JVM metric sets, polishing your feature branch commits, and a Git pre-hook that fails in Jest and Jasmine.

1. Functional Programming: Preserving Type Safety

Functional programming is a very important and powerful way of programming. Experts in the field have realized that applications written in a functional style tend to be more expressive, readable, and correct. Referentially transparent functions can have their result values substituted inline in place of the actual function call. Finally, using Optional can enhance your code in many ways by making it shorter to write as well as fluent.

2. Why Johnny Can't Do Test Driven Development

The code we generate shouldn’t assume that people will take the code and adapt it into testable code, but that we should write testable code as our sample code. Maybe colleges should teach basic software architecture and TDD as part of the curriculum. Maybe those of us who know better should just start testing and figure this all out well enough to explain it to others.

3. Using jstat to Report Custom JVM Metric Sets

I've always been missing possibility to configure custom headers in JStat. Of course there are a lot of predefined data sets, but it'll be nicer if we could create our own data set.

4. Polishing Your Feature Branch Commits

When you create your own, personal feature branch you're allowed to do as much commits as you want, even allowing kinda dirty commit messages.

5. Git Pre-Commit Hook That Fails if "it.only" Used (Jest/Jasmine)

One of the annoying things with Jest is that while it enables you to run only a single test by using it.only, it does not report this in any noticeable way. Thus you can end up in the same situation as we did, not running many tests without knowing it. (Oh yeah, if we only did review the code properly …).

Learn about the ins and outs of open source security and management.


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}