Have you ever heard someone say: I can’t find anything in this documentation? Potential solution = Documentation Quadrants

At work, we recently had a Thoughtworks Tech Radar presentation that was pretty interesting. A colleague introduced us to a way of improving documentation.

This organises documentation into 4 universal categories, along 2 axes.

1. Y axes = nature of the information: is it practical or theoretical?
2. X axes = context of use: are you studying or working?

This is beneficial because:

1. How to calculate CIDR address?

I recently had to whitelist some IP addresses for a client to connect over the public internet. We have a Kubernetes application that had to open up via Public Ingress (incoming firewall rules), secured with an OAuth2 token.

The Ingress rules require CIDR addresses. When I used standard IP addresses the Terraform project failed on the plan step as the addresses were not CIDR addresses.

1. Job focussed
2. What’s the approach?
3. Beginner to Intermediate books
4. Intermediate to Advance books
5. What is the Java Programming Language?

Being a Java software engineer, I’ve often been asked: “What’s a good way of learning Java programming?”
Also, from a career development perspective, I was thinking how I would go about improving my Java and broader programming skills.

What’s the objective?

I think its useful to define some objectives to help target the learning. I think the ultimate goal would be to find a Java programming job. But along the way, it’d be good to develop solid Java skills.