LOL, now you’re just tailoring the data to match your argument. That’s great if you’re 100% perfect at defining a data spec at implementation time and your business rules never, ever change.
It's totally fine if your business rule changes. If you remove a URL or an element of the page, clients will just work as if that data…
My reason would be that I don’t want to provide any visual data in public API, I just want to provide basic data structures and then it’s up to client to handle this.
You nailed it.
If you don't want to provide any visual data, then this post is not for you. This is valid only when you have a website…
Any request your app sends to the server will get some response back.
Not necessarily, you can have a request that has an empty response.
HTML is just data
Not sure what you mean by “just” data. HTML represents the state of the website stored in the user’s machine. It also…
It’s extremely useful for guidance, but far from replacing the human part. At least to validate TDD.
Automated tools which shows code coverage can’t expose strong evidence you’ve written the code using TDD. To efficiently use TDD, you also need to know Domain Driven Design. Sadly, only humans can do that.
If you’re aware of something else, please let me know 🙂
If junior developers were slower and that was the only problem, everything would be fine. Junior developers might over-engineer the code and make decisions that are irreversible which exponentially slows down even the most senior developer in the future, all without being conscious about it.
Junior developers can’t handle Software Entropy efficiently.
Could you mention maybe some good resource to read beside your blog (books?) which can help me to lay some solid base about “the fundamentals of software engineering, necessary to create robust, stable and maintainable applications” ?
I would recommend to start with (in no specific order):