When writing integration tests for be careful with how many and how big application contexts you are starting.

If you are not careful, you can start a lot of full contexts and that can make the execution of your tests very slow.

@deshipu so silos within the team? Gatekeeping about who can do what? Makes no sense to me.

If you are my teammate I really don’t care about how “senior” you are! We are all equals and have equal rights to work on tasks, propose solutions, and voice our opinions.

Titles like team lead, tech lead, ultra senior ninja rooster, suck!! They do more harm than good!

Following “best practices” in the development process of most software products makes no sense. Best practices have no place in complex domains.

What you need instead are emerging practices that are constantly revisited, reviewed and improved.

Igorski boosted

@nielsa @igorski yeah, the admins are responsible for writing the code of conduct for their own server, and that's part of the reason it's important pick a good server with a good admin.

In the larger ecosystem, there's no widely agreed code of conduct, but those who take the safety of their users seriously are often good at blocking misbehaving or under-moderated servers.

@zatnosk @nielsa how do moderators operate? Is it a subjective decision or there is a code of conduct i.e. a rule book they follow?

Igorski boosted

I've made a deliberate choice against a quoting feature because it inevitably adds toxicity to people's behaviours. You are tempted to quote when you should be replying, and so you speak at your audience instead of with the person you are talking to. It becomes performative. Even when doing it for "good" like ridiculing awful comments, you are giving awful comments more eyeballs that way. No quote toots. Thank's

@deshipu it can work the same but have a completely different design. The fact that "it works" tells you nothing about the design.

Btw, there is a huge difference between stepping a minor and a major version. You can just say "stepping is stepping".

semver.org

@deshipu I would recommend a good book on object-oriented design in that case.

From what I've gathered in my career, proper usage of access modifiers has NOTHING to do with style and everything to do with design. Which needs to be intentional.

On another note, when you add new functionality in a backwards-compatible way (make a method public) you bump the minor, not the major version.

@deshipu if you ship libraries, each time you change the signature of a public method or remove it completely you introduce a breaking change.

That means you need to step a major version each time.

And that makes no sense if the end-user was never even supposed to use that method in the first place.

has four different access modifiers: public, private, protected and default.

When choosing which to use always start from the most restrictive and move to the most permissive.

Don't just make everything public. Especially if you are creating libraries.

Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!