Chapter 1. Don't Put Your Resume Ahead of the Requirements
Nitin Borwankar worked at Ingres and Sybase in the early 1990s. He was involved with some of the earliest web-database applications using SybPerl and OraPerl, and soon after with early Enterprise Java. He was also an active participant in New-EDI, an IETF standards process for EDI on the Internet. He has been an independent consultant and researcher since 1994 and has focused on enterprise data and integration along with messaging. His current interests include database schemas for tagging (folksonomy) applications in the enterprise and database issues underlying social networks with applications in the enterprise. He is a member of the Policy Group in the Data Portability effort, where he is tasked with creating the first drafts for EULA templates that respect user data rights. He has written about database issues for GigaOm.com and blogs at http://tagschema.com. He holds a patent in messaging for collaboration across trust boundaries.

AS ENGINEERS WE SOMETIMES RECOMMEND technologies, methodologies, and approaches for solving problems because deep down we want to have these on our resume, not because they are the best solution for the problem. Such decisions very rarely result in happy outcomes.
The best thing for your career is a long string of happy customers eager to recommend you because you did the right ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access