I mean, I barely see the website, and I think it is great for looking for jobs and such – I think for searching people is an amazing tool. But it fails in some basic features very badly when you are not looking for job and don’t have the time to keep several profiles being updated. Main reasons below:

The default/main profile written in stone, meaning it is a pain to switch your default profile. You need to go there, delete it and re-create from scratch <– and that’s because they enable this now, for years you just couldn’t. If you moved from one country to the other, just give up on writing your profile in a new language and not being able to set as primary.

The languages integration is none. I have to literally write 5 profiles if I want to keep portuguese, english, french, german, and italian as profile languages. Any minimal change in anything at your current work, it is a pain to go there, change everything back again. I gave up and keep only 3 main profiles.

No language verification. You can add a new spanish profile, write everything in another language. No validation will be made. This is good and bad, because at least you can re-write your main profile in another language, like I did.

Jobs are dynamics like life not static. This is a more general problem, also correlated to writing a CV. You start doing one thing, focus on another, then do another thing, the role you are assign has the duties you are suppose to do, but from time to time the focus changes. Keeping updating all this, every time, from time to time is painful. Creating a more interactive experience would be more useful instead of a few lines for description. Maybe a better timeline, I mean, you start doing that, now you do this, your were someone mentee, now you are a mentor. And so on, sometimes by product. Or even maybe show by project/product.

Sometimes I even think about deleting it there and keeping just my personal blog. But then I cannot see my friends work, or their promotions, or even job changes. Maybe they should try to do less of a Facebook/Meta journal updates/network and more on professional graph network. You can select the other people you interact, see their projects, how they are being displayed.

I’m sure if you are into Kubernetes/OCP you already played with those bundles of Go automation scripts called operators. If you haven’t that’s pretty cool stuff in the sense of automating the deployment, some operators cover the whole deployment life and as usual, if a pod or a resource is different than the spec, on the status, it will self adjust – for instance it will pop up another pod if the number of pods is different than the operator settings.

What is interesting about this, I would say for DevOps teams is the facility to deploy applications/start EAP/DG/SSO with the operators. As soon as you download one from OperatorHub in OCP for instance, and install in your respective project (given you have storage setup) the deployment is complete seamlessly, only the namespace is will need to be known before hand.

Depending on the operator you can have more or less features, like seemly upgrade up to complete autopilot.

I think it is amazing how powerful it is, with a few oc apply using some templates one can spawn a complete cluster very easily: oc apply rhdg-setup.yaml -f –, where the template defines a namespace for the operator, a namespace for the pods, the operator itself (subscription and OperatorGroup) and the cluster itself:

- apiVersion: operators.coreos.com/v1 <--- api version
  kind: OperatorGroup          <----- OperatorGroup
  metadata:
    name: datagrid
    namespace: ${OPERATOR_NAMESPACE}
  spec:
    targetNamespaces:
      - ${CLUSTER_NAMESPACE}
      # - ${GRAFANA_NAMESPACE}
- apiVersion: operators.coreos.com/v1alpha1
  kind: Subscription            <----- Subscription
  metadata:
    name: datagrid-operator
    namespace: ${OPERATOR_NAMESPACE} <---- the namespace
  spec:
    channel: 8.2.x  <--- channel to fetch the operator, on this case channel 8.2.x instead of 8.1.x or 8.3.x
    installPlanApproval: Manual  <----- manual approval
    name: datagrid
    source: redhat-operators     <----- source
    sourceNamespace: openshift-marketplace <---- source namespace
    startingCSV: datagrid-operator.v8.2.8 <----- starting version

Above the fields are complete for subscription and operator group – as described here. Also the api version and so on defined here. It is very easy to add jvm flags or add routes, just do it in the custom resource, for instance infinispan or cache cr, and that’s all.