Building APIs can be a difficult and painful process. Cross-team collaboration is required and the post development back and forth is almost always expected.
If you care about quality and efficiency, there is a better way to develop APIs that will make your dev life more pleasant. By being more proactive in the initial stages of the development, you can create beautiful documentation, have the incoming requests validated and test your API responses to make sure they follow the correct API contract.
I thought about writing a piece of this nature for a long time but the time has never felt right.
As I am sitting outside my bungalow on the beach of Koh Rong Island in Cambodia, overlooking the most beautiful white sand and crystal clear water paradise combination, I am thinking about my trip, and what I’ve learned so far.
As I said before, now is always the perfect time to do what you always wanted to for a long time.
As I’ve opened Medium and clicked the “Write a story” button, I’ve realized that I have a lot to say. Things that are important to me and have been brewing in my head for a long time. But then many questions have flooded my mind: “What do I write about?”, “Where do I begin?”, “What is the most important thing I can share with the world out of the laundry list I have sitting in my Notes app?”.
At that moment, I realized: That’s it! No, seriously. …
Have technical leadership.
Have a good mentorship program.
Care about code quality & testing.
Promote collaboration among disciplines.
Have language specific style guides.
Dedicate 20% of work time on side projects.
Force pairing upon the developers.
Have architectural decisions solely made by the leadership.
Say “I’ve always done it this way”, “Everyone does it this way” or even “Pivotal does it this way”.
Believe that a ping-pong table, a beer fridge, a company t-shirt or a free lunch is culture.
Are you suffering from bloated views? Do you have trouble sleeping at night not knowing where your views are and how they are behaving? Do you have to squint and make confused faces when looking at your HAML // ERB code? Well then, you must be suffering from a common problem of “The Views Are Too Damn Smart!”.
The usual causes of these problems are:
In theory, your views should be stupid. Very basic. They should just display exactly what they’re…
contemplating existentialism and the mastery of software craft.