61–70 of 299 posts
Martin deserves every penny of his hard-work on Designing Data Intensive Applications. Experienced engineers can easily use the book as a reference and you can give the book to smart junior engineers to give them a great foundation. Honestly, the best technical book I’ve ever owned.
Second-best, second only to Aurélien Géron’s machine learning book. ;)
Miracles happen and sometimes a book, like this one, takes off. For the most part, it's not worth your time and energy. I've made far more money as an author of articles and as an expert witness than I ever did from my books, even though one did with quite well and was translated into Greek and German. I'll also add that he must have one heck of a deal with ORA to get those kind of royalties because the standard ORA…
The 25/10 structure has been O’Reilly’s standard split for at least a few years, no negotiation needed.
My favorite line in the post, and one that inspires my own efforts lately: > How to be a 10x engineer: help ten other engineers be twice as good. Producing high-quality educational materials enables you to be a 300x engineer.
That sentiment (though I didn't think of it in quite this fashion) is why I set up a bi-weekly project management meeting at my last office, and tried to set up something similar for technical people. The PM meeting was not a status reporting meeting. It had no management beyond the PMs (that is, no supervisors proper). The entire purpose was to facilitate sharing information across project boundaries (technical, pro…
At my last office, I set up something very similar for our org with similar success. Your PM procedural problem case is a perfect example down to the complaining about having to attend a meeting they weren't required to attend.
Enter new management. After 8 weeks of ice-breaking meetings in triplicate and taking cues from all the wrong people, the first concrete thing they did that touched me was cancel that meeting. I found new employment shortly thereafter.
It's now an essential part of my repertoire. For technical people? Well that's mostly my team. We have a Trello board where anyone on team can drop RFC cards. Members of my team meet every couple weeks to review and discuss. It's visible to the whole org if anyone else is interested. (Generally, they aren't.)
Earlier quoted context omitted.
The 25/10 structure has been O’Reilly’s standard split for at least a few years, no negotiation needed.
What does 25/10 mean in this context?
"that I get 25% of publisher revenue from ebooks, online access, and licensing, 10% of revenue from print sales..."
Miracles happen and sometimes a book, like this one, takes off. For the most part, it's not worth your time and energy. I've made far more money as an author of articles and as an expert witness than I ever did from my books, even though one did with quite well and was translated into Greek and German. I'll also add that he must have one heck of a deal with ORA to get those kind of royalties because the standard ORA…
I'd revise that, and say it's not worth your time and energy if the goal is to make money from it. There may be other goals (e.g. to evangelize and popularize some piece of technology, or maybe to make certain tech more accessible).
He kind of touches upon it, but there is a lot of value in being able to go into an interview and literally being able to say about a topic "I wrote the book on it." It's a tremendous signal to have overcome the hurdles of getting a publisher to accept you and print your book with your name on it. I used to have several guys on my team that had published books- and they were great, and were constantly getting contact…
He kind of touches upon it, but there is a lot of value in being able to go into an interview and literally being able to say about a topic "I wrote the book on it." It's a tremendous signal to have overcome the hurdles of getting a publisher to accept you and print your book with your name on it. I used to have several guys on my team that had published books- and they were great, and were constantly getting contact…
And I'd add that this is the real value IMO of going with a name publisher--which is otherwise a bit of a mixed bag. Fairly or not a lot of people mentally make at least a bit of mental deduction for a book published independently.
He kind of touches upon it, but there is a lot of value in being able to go into an interview and literally being able to say about a topic "I wrote the book on it." It's a tremendous signal to have overcome the hurdles of getting a publisher to accept you and print your book with your name on it. I used to have several guys on my team that had published books- and they were great, and were constantly getting contact…
>It's a tremendous signal to have overcome the hurdles of getting a publisher to accept you and print your book with your name on it. And I'd add that this is the real value IMO of going with a name publisher--which is otherwise a bit of a mixed bag. Fairly or not a lot of people mentally make at least a bit of mental deduction for a book published independently.
I love writing (and I’m working on another book), but other than maybe getting you in the door, you’ll still have to deal with typical tech interview nonsense.