generally agree, probably most devs nowadays do. otherwise there wouldn’t be stuff like @data in lombok.

i think the word ‘dogma’ is pretty good: it takes a good idea (encapsulation) too far. i am not old enough to have been coding when OOP was the new and hot stuff. but i imagine it comes from the idea that it is a good idea to protect private members where needed.

public class Account {
  private Integer balance;
  public Integer getBalance() {
    return new Integer(balance);
  }
}

that is not such a bad idea to protect balance from stupid sideeffects.

  public String getName() {
    return name;
  }

is a nothing burger, as it returns the same reference and does not protect from accidental sideeffects.

lots of people already pointed out tools to (kind of) dry run locally. they are great to figure out cryptic error messages.

however, if you have issues with the complexity of the whole pipeline, it is usually easier to just execute the whole pipeline. for that we have the branch prefix cicd/ and treat these exactly as main/master and develop (except the very last deployment step). that way we can see where a whole pipeline will go. and when it is finally doing what it should, we can squash it before merge -> have a nice history.

Some say Alduin is Akatosh. Some say M’aiq is a Liar. Don’t you believe either of those things.

which one of you took a picture of my jellyfin server?