Hi Everbody, Am Michael Cengkuru a software developer turned Open Data Specialist. Thanks for this great and informative platform

When you put it in context, you're right. I mean, technical debt will have to be paid once it has been incurred. I've discovered that "shortest and easiest" differs significantly based on one's experience in software development.

lesson learned here

Depends really on the context. But its not bad. Its important not that you would prolly end up writing extra API end points for those tables in the long run though if you want to use that data in your UI.

It really depends on the situations and the stakes involved. Id the project is late, most of the time clients dont give a hoot about how well document the code is if their "paid for" requirements are not done. Most of the time its best to have it working in the best you possibly can and have regular code reviews. that way you dont have angry clients and also you have clean code.

The REST api pattern has really eased how to separate concerns between the front and back end stacks for me

Prolly some orientation of sources and basic intro intro into the standard operating procedure. Only so much can be stuffed into the first day.

Prolly some orientation of sources and basic intro intro into the standard operating procedure. Only so much can be stuffed into the first day.

Airbnb, id love an intimate look at their database structure

you would probably screw up something.... like accidentally put down gmail as we know it!