David Martinez

Crafting code and chasing Agile dreams - because life's too short to waterfail! 💻🚀

[David Martinez @david_software]

Just published an article on why static methods in Java code can be a hindrance and how to avoid them. Check it out and learn how to improve your code! #Java #staticmethods #coding #codeimprovement

https://t.co/BMiCuoLzna

[David Martinez @david_software]

@codecholeric @simas_ch @archtests @structure101 Having 700 modules feels like the wrong thing to do no matter what you use.

There's no way this is maintainable.

[David Martinez @david_software]

@alexbunardzic @StooCrock @davefarley77 What I mean is that not delivering quality today slows you in the future.

[David Martinez @david_software]

@alexbunardzic @StooCrock @davefarley77 Not in the long term

[David Martinez @david_software]

The contemporary testing approach simplifies the pyramid:

Base level: Focus on Business Functionality Tests to ensure core features work as expected. Mock the external.

Top level: Implement Integration Testing for smooth connections with external systems.
#SoftwareTesting

[David Martinez @david_software]

@housecor Although I appreciate that code reviews can be a good way to start conversations.

What about ship/show/ask?

[David Martinez @david_software]

@housecor I think there are better ways to collaborate than code reviews.

User acceptance tests should be changed by "iterate and listen to your users' feedback".

[David Martinez @david_software]

@bazlur_rahman Needing to test a class's private methods signals that there's a problem with your design.

It usually means that the Single Responsibility Principle (SRP) has been compromised.

[David Martinez @david_software]

@housecor This is a symptom of the Smart UI anti-pattern that Eric Evans talks about in the DDD blue book.

[David Martinez @david_software]

@S_Dietrich @bootify_io That's a good point. With boundary testing you can pragmatically achieve that.

It's true tough that there's no 100% theorical assurance that you won't have any error.

What I meant is that the focus should not be in code line coverage.

[David Martinez @david_software]

@PLyczkowski I do kind of the same. I specify the signature of the methods that I need in the "high level" algorithm and I implement the details later.

[David Martinez @david_software]

Having processes on a team by default is premature optimization.

[David Martinez @david_software]

@srbaker @fosseng Exactly. Do not plan for it in advance, separate your things in bounded contexts. When the time to split it comes, you and the team will know. Let changes come naturally.

[David Martinez @david_software]

@bootify_io You'll have external dependencies that could fail as well, but there's not too much you can do about it.

I care about my software, and what I'm responsible of, working.

It's also beneficial to have 100% integration test coverage to ensure error-free code.

[David Martinez @david_software]

@simas_ch @archtests @structure101 Multi-module Maven projects offer faster feedback for structural issues, especially when using an IDE with POM validation but also because it's the first thing checked when running the build.

I like the high cohesion of having a dependency manager who also checks the issues.

[David Martinez @david_software]

Remember, #DTOs are essential for efficient data exchange, but they should NEVER be mixed with your domain entities! Keep your data clean and separate for a maintainable and scalable codebase. 🚀🧹 #Programming #BestPractices

[David Martinez @david_software]

@TheKartikBansal Java ☕️

[David Martinez @david_software]

@IamAbhiDev Understanding what you are trying to solve.

[David Martinez @david_software]

@DevWig DRY means "do not repeat knowledge", different to "do not repeat code". Not all duplicated code is duplicated knowledge.