It sounds like an interesting experimental feature.
The environment is more important than we tend to think.
Building a healthy and safe environment where people can prosper and grow together is crucial for an organization to last, but more importantly, for its employees to feel proud of what they do and how they do it. An atmosphere of continuous learning and sharing knowledge makes a difference.
Software is fun
As a software developer, when you write software, you are the main responsible for the quality of whatever you're writing.
I would recommend the fundamentals of Java, and after getting the basics them transition to kotlin.
TDD is not just about "red-green-refactor" but "THINK first what you want to test, and then red-green-refactor." And that's precisely the most challenging step when practicing test-driven, especially for beginners.
Great talk: https://www.youtube.com/watch?v=TzkuDJ6ef44
When your unit tests are poorly written... 😆
When doing TDD, make sure the test fails for the right reason. That's more important than we tend to think. Seeing the test red (for the right reason!) is crucial to make sure what you are doing (make it pass) is the right thing to do. And then you can refactor with confidence 🏗️
I might join for a coffee-chat if you are still there in an hour, I just arrive from a plain, and now I need to get home 😆
You need to follow yourself to see the notes you publish in your timeline"
#[0]
A great way to learn (and improve!) a programing language is by practicing it with others. And for this, Open-Source Software is one of the best opportunities we all have out there.
You can start fixing some typos, translating something to your mother-tongue language (if applicable), writing some docs, or applying simple refactoring opportunities... until you get comfortable and you can start applying bigger refactorings or even contributing to adding entirely new features.
For sure! Check this out: https://github.com/vitorpamplona/amethyst/pull/218#issuecomment-1458482144
For Servian, you might want to use the directory name `res/values-sr/` (instead `res/values-hu/` from the example)
Amethyst 0.24.2: You are you.
NIP-39 Identity Binding Support by #[0]
Add Taiwanese translations by #[1]
BugFix: Scrollable Select screen by #[2]
Adds missing ES translations by #[3]
Adds missing portuguese translationsby @greenart7c3
Shows private message notifications by #[4]
Upgrades encrypted storage by #[5]
Moves MarkAsRead write and read to IO context by #[6]
Moves Zap amount Calculations in cache and into an IO context by #[7]
BugFix: Delays in updating UserProfile feeds by #[8]
Adds Reporting menu option to badge notifications by #[9]
Uses full banner image sizes on User Profile pages and Drawer by #[10]
Download: https://github.com/vitorpamplona/amethyst/releases/download/v0.24.2/app-release-v0.24.2.apk
And again a new release! The development speed on this project is crazy exciting 🥳🍻
#[0]
You don't want to test "private methods" but "public behavior". Private scope is about implementation details.
If happens that you feel the need to test a private method, it will luckily be that your class is responsible for multiple things.
TIP: Consider extracting that private method to another class, and create an interface to invert the dependencies between them. This way you will make your behavior testable.