David Martinez

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 @david_martinez/4-reasons-to-ditch-static-methods-in-your-java-code-8339fa5f5e96" target="_blank" rel="nofollow noopener">medium.com/@david_martine…

@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_software @simas_ch @archtests @structure101 Honestly, I'm not convinced of this. A first class citizen like JPMS, yes. But I'm not convinced to couple build tool and architecture. I've worked in a project for quite a while that followed this approach and had over 700 Maven modules. Just building the reactor took over a min

I hate multi-module Maven projects

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

@david_software @StooCrock @davefarley77 Long term and speed are incompatible.

What's something you've realised about your work recently that you should've known a long time ago? 🤨

@alexbunardzic @StooCrock @davefarley77 Not in the long term

@StooCrock @davefarley77 Speed is almost always achieved by sacrificing quality.

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

@housecor Although I appreciate that code reviews can be a good way to start conversations. What about ship/show/ask?

@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".

Some things that can’t be fully tested via automation. ✅ Is the code readable? ✅ Are there reuse opportunities? ✅ How’s the user experience? ✅ Is the app accessible? ✅ Does the design match the requirements? ✅ Are automated tests readable and comprehensive? ✅ Is the code needlessly complex? This is why we do code reviews, manual QA, and user acceptance testing.

@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.

What is your stance on testing a class's private method or making it visible for testing purposes?

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

Just reviewed a web page making 55 fetch calls totaling 570k of JSON. This one page is 1.6 MB. Why 55 calls? Because each database table is exposed as an endpoint. The UI joins all the JSON together via the provided foreign keys. To be clear: Don't do this.

@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_software @bootify_io 100% functional coverage does NOT make your application error-free. Unless you test your application with all possible inputs and combination, which you can't even if your application is just a trivial "int add (int x, int y);"

Unpopular opinion: a 100% test coverage does not make your application error free.

@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.

A programming technique I find very helpful is using pseudo-code: write your dream high level code first as pseudo-code, then implement missing objects methods etc. #GodotEngine example of a thing you could write when setting up a turn based game architecture:

Having processes on a team by default is premature optimization.

@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.

@fosseng Design your system well, and it will tell you. Most developers listen to what their ego is telling them, not what their software is telling them.

Wide use of micro-services isn't for productivity gains, system design, other good. It enables hiring n times as many devs to get the same amount of work done. Micro-services are great when applied where they're useful, but most orgs can't manage the overhead well, so net loss.

@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_software While being error free by definition, in reality most often they are not.

@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_software I use @archtests or @structure101 for that purpose. Much leaner

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

@TheKartikBansal Java ☕️

You are doing backend development using which language?

@IamAbhiDev Understanding what you are trying to solve.

Hey Developers 👋, What's the most crucial part of programming? 👀

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

So DRY is the root of all bad code?