3 ms·

API First: The New Way of Developing Software

• mytailorisrich 4y ago
  Nothing new here. This goes back to at least as far as the ideas behind OOP. Maybe I'm becoming a grumpy old man, but it seems that most of the new shiny things are just reinventing the wheel every year.
  • carlmr 4y ago
    >Maybe I'm becoming a grumpy old man This is the never ending cycle of grumpy old people (women can be grumpy, too). When you get to ~35 you realise that the next generation repeats the mistakes of your generation. When you get to 65 you see it a second time. If you get to 95 you see it a third time, but you've probably extrapolated by then. If you manage not to stay bitter, instead you will see that even though 95% of the human experience is on a generational repeating pattern. There are some changes that stick and lead to actual innovation. It's slow, but it's there.
    • euroderf 4y ago
      > If you manage not to stay bitter, instead you will see that even though 95% of the human experience is on a generational repeating pattern. I've seen data that the cycle of war & peace tends to 50 years. This makes sense if the horrors of war make the next generation skip war, but then the generation after that has no direct memory of the horrors and repeats the error of war.
    • mytailorisrich 4y ago
      Sure. I guess the deeper point here, though, is that software/tech seems particularly prone to hyping things that are just a re-hash of what has already been done, and should be part of education/known best practices.
• wg0 4y ago
  Even better, I think is to put the API first without putting a communication layer on top (REST via HTTP, gRPC or graphql) in form of plain old functions/methods/types and include that in whatever communication layer is to be built on top such as a REST API.