couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filippo Fadda <>
Subject Re: Seeking for professional training help with CouchDB
Date Wed, 13 Nov 2013 17:32:04 GMT
When the company you work for needs to use a new technology no one knows. If you have experts
inside you use them to train the others, when you haven't, you pay someone to train your programmers.
When do you need a new technology? When you have a project can't be done with the technologies
you know, because they don't scale or they are not an option anymore. Or when these new technologies
let you reach the goal faster and with a better result. Think for example at the adoption
of a framework when you never used one: if you decide to adopt Symfony or Ruby on Rails and
you don't have expertise, you call an expert to teach, not only you, but all your team.
Same reason you go to university: teachers are there to teach you faster things you can learn
alone, because, presumably, their experience drive you in the right direction, focusing your
attention on the useful things. This not always happen, because there are bad teachers and
bad trainers, like there are bad programmers, but I think I made a point here. :-)


On Nov 13, 2013, at 6:04 PM, Giovanni P wrote:

> ok, reading it again my question may have been a little disrespectful. Now
> it is clear for me when someone would need an expert:
> - when you have a team of developers that need to learn CouchDB;
> - when you need very complex data migrations from various relational
> databases;
> - things related.
> To do these things an expert (or a team of them) to do the training or data
> modelling is probably a very valuable asset.
> The question that stays unanswered (although now I know there is an
> answer), for me, is when someone would need these services?
> On Wed, Nov 13, 2013 at 2:39 PM, Andy Wenk <> wrote:
>> I don't want to start a discussion here. Just wanna drop a side note:
>> Please don't forget when this book was written and where CouchDB was at
>> this time. At least the original version was one of the first written
>> documentation available. To understand the basics about CouchDB, I think it
>> is definitely a good choice.
>> Writing a good book is extremely hard and very time consuming (I
>> experienced it twice). So even when it sound harsh what Jens said, I can
>> imagine, that a lot of people think like that. But also don't forget for
>> whom these books are written. Newbies or intermediate users - not "expert"
>> users or core developers ;-)
>> To come back to the original post, yeah the question was not about a book
>> ;-)
>> Cheers
>> On 13 November 2013 16:54, Filippo Fadda <
>>> wrote:
>>> +1
>>> On Nov 13, 2013, at 4:41 PM, Jens Alfke wrote:
>>>> (Also, I have to say I’m unsatisfied with that book. It skips around a
>>> lot, is often unclear, and spends a lot of time on examples as opposed to
>>> principles. That said, I haven’t seen any really good books about
>> CouchDB.)
>>>> —Jens
>> --
>> Andy Wenk
>> Hamburg - Germany
>> RockIt!
>> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588

View raw message