What I'm Up to Now
martinfowler.com
What I'm Up to Now
1–10 of 142 posts
Re: What I'm Up to Now
#2Martin Fowler has been a big advocate of micro services. I think micro services has been one of the biggest mistakes ever promulgated on software development and is responsible for developer misery, un-productivity, failed projects, and unintelligible rats nests that have set back a generation of engineers who have to now unlearn all of this nonsense. I can’t take him seriously and he is forever tainted in my mind. However it is a big boon for consultants like him and those that like to spend a lot of time gluing unmaintainable services together.
Re: What I'm Up to Now
#3Martin Fowler has been a big advocate of micro services. I think micro services has been one of the biggest mistakes ever promulgated on software development and is responsible for developer misery, un-productivity, failed projects, and unintelligible rats nests that have set back a generation of engineers who have to now unlearn all of this nonsense. I can’t take him seriously and he is forever tainted in my mind. H…
Maybe it's the right pattern for some problems, and got overused when it was high on the hype curve? I don't have a horse in the race, but have seen many other technologies/patterns go that route
Re: What I'm Up to Now
#4Near the end of his post, he writes:
> I’ve always been nagged by my conviction that I’m not working as diligently or effectively as I ought to be. Sadly I’m not getting any better at not letting that bug me.
Maybe this has been discussed in depth elsewhere, but my question in response to this is: how does one/how do we end up feeling like this? And how can you work toward not feeling this way?
Re: What I'm Up to Now
#5Martin Fowler has been a big advocate of micro services. I think micro services has been one of the biggest mistakes ever promulgated on software development and is responsible for developer misery, un-productivity, failed projects, and unintelligible rats nests that have set back a generation of engineers who have to now unlearn all of this nonsense. I can’t take him seriously and he is forever tainted in my mind. H…
Maybe it's the right pattern for some problems, and got overused when it was high on the hype curve? I don't have a horse in the race, but have seen many other technologies/patterns go that route
That statement describes basically every fad in development, every design pattern, and most if not all tools.
Re: What I'm Up to Now
#6Martin Fowler has been a big advocate of micro services. I think micro services has been one of the biggest mistakes ever promulgated on software development and is responsible for developer misery, un-productivity, failed projects, and unintelligible rats nests that have set back a generation of engineers who have to now unlearn all of this nonsense. I can’t take him seriously and he is forever tainted in my mind. H…
Maybe it's the right pattern for some problems, and got overused when it was high on the hype curve? I don't have a horse in the race, but have seen many other technologies/patterns go that route
I find it particularly stupid compared to most other hyped technologies, as the pattern pervades the entire engineering superstructure and has to be entirely burned down in order to fix the core rot. The foundation of any microservice-based system is inherently shoddy in a way other poorly designed systems aren’t.
Re: What I'm Up to Now
#7Martin Fowler has been a big advocate of micro services. I think micro services has been one of the biggest mistakes ever promulgated on software development and is responsible for developer misery, un-productivity, failed projects, and unintelligible rats nests that have set back a generation of engineers who have to now unlearn all of this nonsense. I can’t take him seriously and he is forever tainted in my mind. H…
Fowler also wrote about "cookie-cutter" scaling of monolithic applications. Seems to me that the fault lies with the people who cargo cult approaches rather than reflecting on them and adopting them if and when they make sense.
Re: What I'm Up to Now
#8Martin Fowler has been a big advocate of micro services. I think micro services has been one of the biggest mistakes ever promulgated on software development and is responsible for developer misery, un-productivity, failed projects, and unintelligible rats nests that have set back a generation of engineers who have to now unlearn all of this nonsense. I can’t take him seriously and he is forever tainted in my mind. H…
Maybe you and them just did not understand that it’s an pattern that, as all pattern, makes only sense for certain applications.
Maybe you could also present some references that back up your claims?
It’s always easy to judge on people that tried to solve problems of the past. Mistakes will always be made but this way we do learn and make progress.
So what I try to say is maybe appreciate that he at least tried to solve problems. All this shitposts here at hn against ppl like him or uncle bob or so unreflected and immature… like really what the heck is going on with you people.
Edit: grammar. Non nativ here…
Re: What I'm Up to Now
#9Earlier quoted context omitted.
Maybe it's the right pattern for some problems, and got overused when it was high on the hype curve? I don't have a horse in the race, but have seen many other technologies/patterns go that route
I find it particularly stupid compared to most other hyped technologies, as the pattern pervades the entire engineering superstructure and has to be entirely burned down in order to fix the core rot. The foundation of any microservice-based system is inherently shoddy in a way other poorly designed systems aren’t.
The Problem With Microservices:
Re: What I'm Up to Now
#10Martin Fowler has been a big advocate of micro services. I think micro services has been one of the biggest mistakes ever promulgated on software development and is responsible for developer misery, un-productivity, failed projects, and unintelligible rats nests that have set back a generation of engineers who have to now unlearn all of this nonsense. I can’t take him seriously and he is forever tainted in my mind. H…
Maybe you and them just did not understand that it’s an pattern that, as all pattern, makes only sense for certain applications. Maybe you could also present some references that back up your claims? It’s always easy to judge on people that tried to solve problems of the past. Mistakes will always be made but this way we do learn and make progress. So what I try to say is maybe appreciate that he at least tried to so…
If you build your whole life around didactic speaking gigs where you tell everyone how to do it despite apparently not writing any software yourself, you need to be prepared to be open to some criticism when it turns out your ideas are shit.