令状/Edit for Hentzenwerke
|
About HWP
Our 使節団 is to produce 広大な／多数の／重要な 調書をとる／予約するs for
serious ソフトウェア developers. Not 簡単に 調書をとる／予約するs that are 満足な,
or 承認する, or good enough. We want the reader to 停止する every
選び出す／独身 調書をとる／予約する of ours and say, “This is a GREAT 調書をとる／予約する!”
For a 類似の 視野, look at the automobile 産業.
There are the 集まり market 生産者s ? GM and Ford and Toyota.
They produce 抱擁する numbers of 普通の／平均（する） cars. Some are pretty
good (like the Corvette), while some really shouldn’t have
ever been 許すd on the road (like, 井戸／弁護士席, you know which
ones.) Most publishers are like GM, Ford and Toyota, building
cars in large numbers for the guy next door who 運動s to
work each day.
There are also the 高級な automobile 製造業者s ? Mercedes,
BMW, Jaguar. They produce cars for the 集まり market, but are
always at the high end of the market, and everyone would love
to have one of those machines in their driveway. There are
a few publishers that fit this mold ? O’Reilly come to mind
すぐに - and readers are rarely disappointed by their
調書をとる／予約するs.
And then there are the exotics ? Ferrari, Maserati, Lamborghini.
These automobiles are high 業績／成果, finely （手先の）技術d automobiles.
They are truly the 広大な／多数の／重要な cars of the world. But they’re built
for niche markets, and for serious drivers who 需要・要求する 広大な／多数の／重要な
cars. We, too, produce high 業績／成果, finely （手先の）技術d 調書をとる／予約するs
for niche markets - for serious developers who 需要・要求する 広大な／多数の／重要な
調書をとる／予約するs. If you're not up to working on a 調書をとる／予約する with the passion
and zeal 要求するd to produce a GREAT 調書をとる／予約する, then you'll want
to move on along to another publisher.
Types of 調書をとる／予約するs we produce
The first thing you have to understand, before you
can 令状 or edit for HWP, is what type of 調書をとる／予約するs we publish. Our 使節団
is to produce truly 広大な／多数の／重要な 調書をとる／予約するs for serious ソフトウェア developers.
If you 港／避難所't done so already, wander through our catalog at www.hentzenwerke.com.
You should also spend a few minutes at www.amazon.com,
and read the reviews of our 調書をとる／予約するs to get a feel of how our 顧客s feel
about what they buy. (Search for "Visual FoxPro" and then 追跡（する） for 関係のある
肩書を与えるs, or look for a 明確な／細部 肩書を与える from the 名簿（に載せる）／表（にあげる） in our catalog.) We
also welcome you to visit the さまざまな online 会議s that are 関係のある to
the 支配するs covered by our 調書をとる／予約するs and ask around there.
Our 肩書を与えるs cover a 明確な／細部 topic in depth, and are written
by individuals who have 重要な day-to-day, on the 職業
experience with the language or 道具 in question. We 一般に
don't 令状 for end-使用者s, nor do we produce 'day and date'
調書をとる／予約するs - tomes that are 解放（する）d 同時に with the 解放（する）
of a 製品 and thus can't cover the 構成要素 in-depth or
with 論証するd experience. If you page through a 調書をとる／予約する of
ours, you'll see that each page is packed - the text is dense,
we don't pad the page count with 二塁打-spaced paragraphs,
extra large fonts, fancy doo-dads in the 利ざやs, gratuitous
or redundant 審査する 発射s, or a layout that is more style
than 実体.
Many authors wonder how many pages a 調書をとる／予約する should be, or what it should
cover. Most publishers 始める，決める page counts for a 調書をとる／予約する ーするために 会合，会う a predetermined
法人組織の／企業の 基準 - 関わりなく the 支配する or 構成要素 to be covered.
Our authors have one guiding 原則 - to 令状 until they have covered
the 支配する 完全に, and then to stop. It's as simple as that.
類似して, tech editors wonder how far they should go ーに関して／ーの点でs of making
changes and 是正s to the manuscript of the author they're working
with. Again, it's simple ? the tech editor should edit until he/she is
happy with the manuscript - is it a 調書をとる／予約する that they’d want to buy and read
themselves?
As a result, you’ll find that each HWP 調書をとる／予約する is written only with the reader
in mind, not to fill out a catalog or match with other 調書をとる／予約するs in a 法人組織の／企業の
series.
What a HWP 調書をとる／予約する looks like
HWP 調書をとる／予約するs all 一般に follow the same 判型, so
that a reader of one 調書をとる／予約する knows what to 推定する／予想する from another 調書をとる／予約する. In 新規加入,
there are 確かな elements that I think belong in each 調書をとる／予約する, so by using
the same 判型, we make sure each 調書をとる／予約する has them. Here's what you'll find,
page by page, in a HWP 調書をとる／予約する:
肩書を与える page: 含む／封じ込めるs the 指名する of the 調書をとる／予約する and the 指名する(s) of the
author(s).
合法的な page: All the 正規の／正選手 合法的な stuff that belongs in the 前線
of the 調書をとる／予約する, 同様に as 接触する （警察などへの）密告，告訴（状） and identifying （警察などへの）密告，告訴（状）
about the 調書をとる／予約する.
Dedication: Each author can dedicate the 調書をとる／予約する as they wish.
Our 契約 with the Reader: Where we 述べる what the reader
can 推定する／予想する from the 調書をとる／予約する and from HWP.
承認s: This is where the author(s) gets to thank (or
非難する!) their family, friends, and others who helped them out before,
during and after the 令状ing of the 調書をとる／予約する.
About the Author(s): Biographies of each author and tech editor.
How to Download とじ込み／提出するs: A description of how to download the とじ込み／提出するs
that …を伴って the 調書をとる／予約する.
名簿（に載せる）／表（にあげる） of 一時期／支部s: A one page synopsis of the 一時期／支部s in the 調書をとる／予約する.
（米）棚上げする／（英）提議する of Contents: A 詳細（に述べる）d 輪郭（を描く） of each 一時期／支部, 負かす／撃墜する to
the first (and usually deeper) section 長，率いる.
Introduction: Some authors like to 令状 an introduction for their
調書をとる／予約する. Others prefer to use 一時期／支部 One as the introduction. This is where
the Introduction goes if there is one.
団体／死体: Depending on the content of the 調書をとる／予約する, an author may just
令状 a 一連の 一時期／支部s, which are numbering sequentially, like so:
一時期／支部 1
一時期／支部 2
一時期／支部 3
一時期／支部 4
etc.
In other 事例／患者s, the content of the 調書をとる／予約する lends itself to a more granular
始める，決める of 分割s. This is also true if there are a lot of 一時期／支部s ? seeing
a 名簿（に載せる）／表（にあげる） of 30 or 40 一時期／支部s is difficult for the reader to grok, and thus
dividing the 一時期／支部s into sections is helpful, like so:
Section I
一時期／支部 1
一時期／支部 2
一時期／支部 3
一時期／支部 4
一時期／支部 5
Section II
一時期／支部 6
一時期／支部 7
一時期／支部 8
etc.
In yet other 事例／患者s, the author may want to divide the 調書をとる／予約する into その上の
pieces, and uses “Parts” to collect sections. This organization would
look like this:
Part One
Section I
一時期／支部 1
一時期／支部 2
一時期／支部 3
一時期／支部 4
一時期／支部 5
Section II
一時期／支部 6
一時期／支部 7
一時期／支部 8
Part Two
Section III
一時期／支部 9
一時期／支部 10
一時期／支部 11
etc.
虫垂 (one or more): Some authors 含む 付加 構成要素
that doesn't fit inside a 一時期／支部. An example would be a 言及／関連 （米）棚上げする／（英）提議する
of 命令（する）s and 機能（する）／行事s; another would be a 名簿（に載せる）／表（にあげる） of URLs or 示唆するd
readings.
索引: Keywords and the page number(s) that they're 設立する on. 公式文書，認める
that each 調書をとる／予約する 含むs an ebook in CHM and/or PDF 判型, and thus, the
reader can do a 十分な text search across the entire contents.
HWP ebooks
The contents of each of our printed 調書をとる／予約するs
are also 利用できる in electronic とじ込み／提出するs. These とじ込み／提出するs were 最初
in HTML Help (.CHM とじ込み／提出する) 判型, but in 2002 we’ve switched
to the Adobe Acrobat (.PDF とじ込み／提出する) 判型 予定 to a combination
of 安全 穴を開けるs in the HTML Help Engine and 限られた／立憲的な （軍隊などの）展開，配備
適切な時期s compared to PDFs (which are usable on a variety
of operating systems. These ebook とじ込み／提出するs are 利用できる for
download from our website either through a email/password
or username/password combination (if 購入（する）d 直接／まっすぐに from
us) or 経由で a keyword from the 調書をとる／予約する (if 購入（する）d どこかよそで.)
These ebooks 許す the 使用者 to bring the 調書をとる／予約する ‘on the road’
with them, to a 顧客’s 場所／位置, home, or vacation, without
having to lug 激しい 調書をとる／予約するs with them.
顧客s can also order just the ebook 見解／翻訳／版 of a 調書をとる／予約する; this is 特に
attractive to overseas 顧客s who don’t wish to 支払う／賃金 large shipping
告発（する），告訴（する）／料金s and wait for weeks for the printed 調書をとる／予約する to arrive.
The company
承認する, now that you have an idea about our 製品s,
a word from our sponsor.
I run Hentzenwerke InterGalactic (the 法人組織の／企業の parent of HWP) from my
home office in Milwaukee, WI with the help of over 50 (to date) part-time
staff, 独立した・無所属 請負業者s and third-party vendors. Part-time staff
helps me run the company, 実行する orders, answer email, and 成し遂げる other
行政の chores. I 契約 with authors, technical editors, copy
editors, layout and graphic artists and indexers from all over the world
to produce a final manuscript for a 調書をとる／予約する.
At the 完成 of this 過程, I send the manuscript to my printing
company, who produces the printed copies, and 蓄える／店s the 調書をとる／予約するs in their
倉庫／問屋. Orders arrive 経由で snail mail, fax, 運送／保菌者 pigeon, email, and
our online 蓄える／店 at our website from individuals, groups, resellers and
distributors all over the world. Once 過程d, orders are sent to the
fulfillment 中心 at the 倉庫／問屋 and 調書をとる／予約するs are shipped out to 顧客s.
承認する, just kidding about the pigeons. The PETA people wouldn’t 許す it.
At the same time, we ship a sizable 量
to our distributor, 独立した・無所属 Publishers Group in Chicago,
who takes care of sales to online 場所／位置s and 蓄える／店s all over
the world.
The history of HWP - how we got here
I’m a mechanical engineer by training (BSME, Rose-Hulman 学校／設ける of 科学（工学）技術 in Terre Haute, if you’re 利益／興味d) and a ソフトウェア developer by 貿易（する）, having written dBASE, FoxPro and Visual FoxPro 使用／適用s as an 独立した・無所属 developer since the 早期に ‘80’s. I’d done a fair 量 of 令状ing during high school and college, sports for the 地元の newspaper, school yearbook, that sort of thing, and frequently 与える／捧げるd to a variety of 出版（物）s after 卒業. In the 早期に-90’s, I started 令状ing a column for Pinnacle Publishing’s FoxTalk technical newsletter, and すぐに thereafter wrote 早い 使用／適用 開発 with FoxPro 2.6, a 125 page 調書をとる／予約する published and marketed by Pinnacle.
A year later I wrote the introductory 容積／容量 for Microsoft Visual FoxPro 3.0, Programming Visual FoxPro 3.0, for Ziff-Davis, the folks who at the time published PC Magazine. This 900 page behemoth became the 基準 text for anyone learning Visual FoxPro, and still sells an 時折の copy
nearly a １０年間 later. A year after the 解放（する） of the 3.0 調書をとる／予約する, I started looking for a publisher for a general 目的, language-独立した・無所属 guide to ソフトウェア 開発 practices. Each of the publishers I talked to felt that there wasn’t enough sales 可能性のある in a 調書をとる／予約する that didn’t talk about a 明確な／細部 道具 or language. I ended up putting together my 公式文書，認めるs in 調書をとる／予約する 判型, finding a printer, and publishing the 調書をとる／予約する, the 1997 Developer’s Guide, myself. We sold direct ? through advertising, 貿易（する） shows and word of mouth, and
moved several thousand copies around the world.
Because of my experience with the RAD 調書をとる／予約する and the
Ziff 3.0 調書をとる／予約する, Pinnacle asked me to edit their next 一連の FoxPro 調書をとる／予約するs,
The プロの／賛成のs Talk Visual FoxPro. I pulled together four 産業 専門家s to
令状 this series and four more folks to edit the 作品. Pinnacle took
care of the marketing and publishing. The series was 結局 連合させるd
into a 選び出す／独身 Microsoft 圧力（をかける） 容積／容量.
すぐに thereafter, I approached Ziff about an update of the Visual FoxPro
3.0 調書をとる／予約する for the 近づいている 5.0 解放（する） of Visual FoxPro; unfortunately,
Microsoft’s marketing of the 3.0 製品 left something to be 願望（する）d,
and Ziff didn’t want to do a 5.0 調書をとる／予約する 予定 to a 予報するd 減産／沈滞 in sales.
A few 5.0 調書をとる／予約するs were 結局 解放（する）d, but to lukewarm 返答.
The 状況／情勢 with publishers didn’t seem to be 改善するing as Visual FoxPro
6.0 entered alpha 実験（する）ing; seeing reader 失望／欲求不満 with the 試みる／企てるs
made at 5.0 調書をとる／予約するs, and wanting to 令状 a follow up for 6.0, I decided
that I could self-publish a 6.0 update of my 3.0 調書をとる／予約する, and pulled together
several other authors who had experienced the same 不本意 of major
publishers to commit to some sort of a 6.0 調書をとる／予約する.
I was able to get seven authors together to produce a collection of five
調書をとる／予約するs on Visual FoxPro 6.0; each 調書をとる／予約する would cover a very 明確な／細部 area
of VFP 開発. In 新規加入, I would be updating my ’97 DevGuide for
1999. I formed a new company that would be 責任がある the 生産／産物,
marketing, and order 過程ing for all these 肩書を与えるs. At the time (早期に
1998), Internet e-商業 was just starting to become mainstream; this
meant we could market and sell our 調書をとる／予約するs both through our own website
同様に as though other online booksellers. アマゾン, through whom we had
sold a number of ’97 DevGuides, quickly became our biggest 顧客, as
thousands of programmers すぐに flocked to them as their number one
資源 for computer programming 調書をとる／予約するs.
Since that 初期の group of six, I’ve continued to 追加する 肩書を与えるs to our offerings,
both on more Visual FoxPro 肩書を与えるs 同様に as new topics, such as Microsoft
Office Automation and Visual SourceSafe. Here’s our history and 現在の
ーするつもりであるd schedule of 出版（物）:
| 1996 |
10 |
DevGuide ‘97 (Hentzen) |
| 1998 |
11 |
効果的な Techniques for 使用／適用
開発 with VFP (Booth/Sawyer) |
| |
12 |
Hacker's Guide to VFP 6 (Granor/Roche) |
| 1999 |
2 |
DevGuide '99 (Hentzen) |
| |
4 |
前進するd 反対する Oriented Programming
with VFP (Egger) |
| |
5 |
Internet 使用／適用s with VFP 6
(Strahl) |
| |
12 |
根底となるs of VFP 6 (Hentzen) |
| 2000 |
6 |
Microsoft Office Automation (Granor/ツバメ) |
| |
7 |
1001 Things You 手配中の，お尋ね者 To Know about
VFP (Akins/Kramek/Schummer) |
| |
9 |
（弁護士の）依頼人/Server Programming with VFP
and SQL Server (Urwiler/DeWitt/徴収する/Koorhan) |
| |
12 |
Creating VFP Apps with Visual FoxExpress
(Archer/Jurden) |
| 2001 |
3 |
VFP Certification Exam 熟考する／考慮する Guide
(Winegarden/延期する) |
| |
6 |
必須の SourceSafe (Roche) |
| |
7 |
What's New in Visual FoxPro 7.0
(Granor/Hennig/McNeish) |
| 2002 |
2 |
Debugging Visual FoxPro 使用／適用s
(Folsom) |
| |
4 |
Hacker’s Guide to VFP 7.0 (Granor/Roche/Hennig/ツバメ) |
| |
4 |
The Visual FoxPro 報告（する）／憶測 Writer:
押し進めるing It To The 限界s & Beyond (Pountney) |
| |
5 |
Prechazime na Visual
FoxPro 7.0 (What's New in Visual FoxPro 7.0 - translation
localized for Czech 共和国) (Granor/Hennig/McNeish) |
| |
6 |
WebRAD: Building Database Websites
with VFP/Web 関係 (Chattaway/Pearson) |
| |
8 |
DevGuide 3 (Hentzen) |
| |
9 |
.NET for VFP Developers (McNeish) |
| |
11 |
MegaFox: 1002 Things You 手配中の，お尋ね者
to Know About 延長するing Visual FoxPro (Akins/Kramek/Schummer) |
| 2003 |
3 |
What's New in Visual FoxPro 8.0 (Granor, Hennig) |
| |
4 |
CrysDev: A Developer's
Guide to 統合するing 水晶 報告（する）／憶測s (Berntson) |
|
5 |
Das Visual FoxPro 8.0
Update Buch (What's New in Visual FoxPro 8.0 - translation
localized for Germany) (Granor/Hennig) |
| |
8 |
OOoSwitch: 501 Things
You 手配中の，お尋ね者 to Know About Moving to OpenOffice.org from
Microsoft Office (Granor) |
| |
10 |
FoxTales: Behind the Scenes at Fox ソフトウェア (Nietz) |
| |
10 |
Painless 遺産／遺物 FoxPro 使用／適用s on Modern 網状組織s (Bourke) |
| |
12 |
Linux 移転 for 網状組織 行政官／管理者s (Jang) |
| 2004 |
3 |
Building Your Own Visual FoxPro 枠組み (Chazotte) |
| |
4 |
Linux 移転 for 力／強力にする 使用者s (Hentzen) |
| |
6 |
（軍隊を）展開する，配備するing Visual FoxPro 解答s (Schummer) |
In the 早期に days, we sold 調書をとる／予約するs to the
Visual FoxPro community. It wasn't difficult because I had
a lot of visibility in the community - through online 会議s,
令状ing, speaking, and other activities. In 新規加入, my authors
were all 井戸／弁護士席-known in the community 同様に so pretty much
everyone knew we were the folks with the best FoxPro 調書をとる／予約するs
around. Over the years, that 評判 has grown to the point
where we became the 単独の source for Visual FoxPro 調書をとる／予約するs.
People bought from us either 直接／まっすぐに through
our website, or through アマゾン, with whom we started selling
through in our 早期に days. We also took special orders from
bookstores until we developed a 関係 with a 卸売業者
who 扱うd that part of the 貿易（する） for us.
However, ーするために grow, we 拡大するd
our marketing past direct 簡単に taking orders. Here's what
we did.
Marketing, selling and 分配するing our 調書をとる／予約するs
顧客s can 購入（する） our 調書をとる／予約するs 直接／まっすぐに
through our website, through online booksellers like アマゾン.com,
at their 地元の bookstore, through resellers in other countries,
and at 貿易（する） shows where we have a booth.
As you 診察する the 肩書を与えるs we have produced, you’ll see that
we don’t produce “me-too” 肩書を与えるs ? each of our 調書をとる／予約するs covers
a unique topic, often in a very 狭くする niche, and thus, often
doesn’t really have a direct competitor. For example, there
were over 20 調書をとる／予約するs on Visual FoxPro 3.0, but most 試みる／企てるd
to cover the entire 製品, and usually didn’t do 司法（官）
to any area. There was one 1000 page 調書をとる／予約する that 演説（する）／住所d 反対する
orientation in VFP 3 (arguably the most important feature
in 3.0) with just two 宣告，判決s! By contrast, we published
a 400+ page 調書をとる／予約する that only covered 反対する Orientation in VFP.
As a result, 顧客s who are 利益／興味d in a particular
topic usually are looking for a 明確な／細部 調書をとる／予約する from us, not
just ‘any old 調書をとる／予約する on’ a topic. This means that they
often come looking for us on the Web, and either find us through
an online 蓄える／店 like アマゾン, or find us 直接／まっすぐに.
I 最初 make the 顧客 aware of a 肩書を与える through several
means. First, I often select authors with high visibility
in their 支配する area. This visibility 含むs 正規の／正選手 参加
in online 会議s, columns and 正規の／正選手 出資／貢献s to 産業
出版（物）s, and speaking 約束／交戦s at 産業 events.
Their visibility attracts attention to their work, 含むing
the 調書をとる／予約する. Next, I advertise 定期的に in the appropriate 貿易（する）
magazines and websites, which to date have been まず第一に／本来
oriented toward Visual FoxPro, but are starting to 含む
other 発生地s. We …に出席する 貿易（する） shows at the appropriate 会議／協議会s,
and 持つ／拘留する 昇進／宣伝s to 生成する 利益／興味 and buzz.
I 供給する a 広大な／多数の／重要な 取引，協定 of （警察などへの）密告，告訴（状） about our 調書をとる／予約するs on our
website, in the form of 一時期／支部 listings, very 詳細（に述べる）d （米）棚上げする／（英）提議する
of contents, and a 一連の 見本 一時期／支部s from each 調書をとる／予約する.
In 新規加入, we continually request happy readers to 地位，任命する
comments on アマゾン.com for 可能性のある 顧客s to review.
Authors are 推定する／予想するd to 供給する updates and errata as appropriate
to the 調書をとる／予約する; that 構成要素 is 地位，任命するd on our website and encourage
readers to visit for updates. By doing so, 顧客s learn
of new 調書をとる／予約するs that we have produced since their last 購入（する）,
同様に as of 調書をとる／予約するs that they may not have been aware of if
their 購入（する） was not made 直接／まっすぐに from us.
I also do 時折の email 告示s to 警報 存在するing
顧客s of new 調書をとる／予約するs and special 昇進／宣伝s. We've 蓄積するd
a sizable mailing 名簿（に載せる）／表（にあげる）, both because many of our 顧客s
buy 直接／まっすぐに from us, 同様に as the fact that many 顧客s
who do not buy 直接／まっすぐに from us still come to our website
to download 付加 構成要素s (and need to 登録（する） to
do so.) As a result, our emails are 一般に やめる 生産力のある.
We have resellers in England, Germany and Australia. We entered
into a 配当 協定 with 独立した・無所属 Publisher's
Group in late 2002 - they 扱う all North America bookstore
accounts and some special reseller accounts overseas. We continue
to 拡大する our 配当 網状組織 世界的な. We had a booth
at the nation's 最初の／主要な 調書をとる／予約する fair, 調書をとる／予約する Expo America in Los
Angeles in May, 2003.
The sharp-注目する，もくろむd の中で you may wonder about our 計画（する）s for 配当
past the VFP world. Up to this point, most of our 調書をとる／予約するs have
been 焦点（を合わせる）d まず第一に／本来 on Visual FoxPro, a market 基本的に
ignored by other publishers. Thus, we’ve had a lot of success
because (1) VFP developers were 餓死するd for 調書をとる／予約するs, and (2)
we’ve been 事実上 the only game in town. As we broaden
our horizons to 含む 非，不，無-VFP 肩書を与えるs, there will be 意味ありげに
more 競争. What are our 計画（する）s for 取引，協定ing with this?
It’s a fair question, but one that we’ve considered ourselves.
First of all, our cost structure is such that we don’t have
to sell 10,000 or 20,000 調書をとる／予約するs ーするために make a 利益（をあげる） or
for our authors to make reasonable 収入s. We as a company,
and my authors 個々に, can be successful by selling
just a few thousand 調書をとる／予約するs. (詳細（に述べる）s on how my authors do can
be 設立する in “the money” section under “The Publishing 過程
at HWP”.) Thus, given that our 最小限 goal is to sell in
the ‘thousands’ of 調書をとる／予約するs, not the tens or hundreds of thousands,
we have some latitude.
Second, we are still 焦点（を合わせる）d on very 的d
調書をとる／予約するs - 肩書を与えるs that have a unique propostion for the reader,
in new or 専攻するd markets. However, the size of the new
markets we’re getting into are 意味ありげに larger than the
FoxPro market, and so we just need a small piece of those
markets.
Third, the new markets we're entering (水晶
報告（する）／憶測s and OpenOffice.org, for example) have 十分な general
利益／興味 that bookstores are 利益／興味d in 在庫／株ing our 肩書を与えるs.
ーするために support that 利益／興味, we're 極端に 積極的な
with 昇進／宣伝s - tabletop placements, advertising in 調書をとる／予約する
出版（物）s, email （選挙などの）運動をする through online retailers, and
so on.
Together with our 存在するing direct marketing,
advertising in the appropriate places, and continued word
of mouth 能力s, we think our marketing will be enough
to move our 非，不，無-VFP 調書をとる／予約するs in 十分な 量s to 満足させる
everyone 伴う／関わるd.
Finally, don't forget that we’ve got a couple of 競争の激しい
advantages that should be 維持できる for the foreseeable
未来. I believe these are 維持できる because of the 堅固に守るd
態度s at the major publishers.
-
First, we sell direct, which results in higher 利ざやs, and a direct
関係 with the 顧客.
-
Next, because of our personal
関与 in each and every 調書をとる／予約する, we're able to produce 終始一貫して
high 質 調書をとる／予約するs.
-
Third, because of our cost structure, we can go after ‘small’ markets
that are さもなければ ignored. We 定期的に update our website with source
code, errata and FAQs; an attractive feature to many readers but one
that is often ignored by big publishers.
-
And finally, we 含む an
ebook とじ込み／提出する with every 購入（する）; another attractive feature to most
readers but a major 構造上の 決定／判定勝ち（する） that a big publisher is not
likely to 可決する・採択する easily.
These factors make a HWP 調書をとる／予約する a 説得力のある
購入（する）, and 価値（がある） going the extra mile to 得る for enough
people so that we can 会合，会う our sales goals.
And it’s just possible that a 肩書を与える of ours will 生成する
十分な 脚s so that it will move in even larger 量s.
In short, the upside is there, but without the corresponding
downside.
Author 必要物／必要条件s
I 推定する／予想する that an author use the 製品,
道具 or 科学（工学）技術 that they are 令状ing about in a 十分な-time,
professional basis, and that they have 論証するd 専門的知識
and mastery with the topic. Because our 調書をとる／予約するs cover 高度に
technical 構成要素 for 前進するd 使用者s, programmers and developers
in an in-depth manner, I do not work with “professional authors”
? individuals who use a 道具 or 科学（工学）技術 for the 目的
of 令状ing a 調書をとる／予約する, and then put that 道具 aside. While that
approach can work 極端に 井戸／弁護士席 with some topics, 特に
end-使用者 ソフトウェア, doing so with 高度に technical topics results
in shallow, superficial, incomplete 調書をとる／予約するs. A professional
writer who doesn't use the 道具 定期的に 簡単に can't be
knowledgeable enough to produce the in-depth 構成要素 that
展示（する）s real-world experience that I 要求する.
I would 推定する／予想する an author to have, at the 最小限, many hundreds
of hours of day-to-day experience with the 支配する they're
令状ing about. And, interestingly enough, this 期待
doesn't change much with beta 製品s - if you 港／避難所't lived
with the beta day-in and day-out and done some 重要な
work with it, then you're not ready to 令状 for me.
Finally, I 推定する／予想する an author to support their 調書をとる／予約する after having
written it by 参加するing in the appropriate online 会議s,
供給するing errata and FAQs in 返答 to reader requests,
and 一般に 促進するing it when possible, such as 経由で speaking
約束／交戦s at 使用者 group 会合s and 会議／協議会s, and 令状ing
関係のある articles in other 発生地s.
You could click here for the
scoop on becoming an author. But why don't you 展示（する） some
patience and read the 残り／休憩（する） of this... you'll get there soon
enough.
Editor 必要物／必要条件s
A tech editor’s 責任／義務 is two 倍の ? to 確実にする that the 構成要素 現在のd in the 調書をとる／予約する is 訂正する and 完全にする, and to 確実にする that the source code 供給するd with the 調書をとる／予約する runs 適切に and matches what is 現在のd in the 調書をとる／予約する.
Most tech editors also 供給する feedback about the approach
and general content of the 調書をとる／予約する 同様に, indeed, いつかs to what may
appear as nearly an unhealthy degree! A tech editor for a 選び出す／独身 author
調書をとる／予約する should have 論証するd competence with the 構成要素 covered in
the 調書をとる／予約する; for a 多重の author 調書をとる／予約する, this 必要物／必要条件 may be 修正するd
as each author will in essence 供給する a tech edit for the 構成要素 of
other’s authors.
Again, click here for the
scoop on becoming a tech editor if you can't wait - but be
sure to read this entire thing at some point.
What’s in it for you?
井戸／弁護士席, there’s a 月毎の 王族 check,
for one thing. (Yes, we 支払う／賃金 月毎の, unlike some publishing
houses that 支払う／賃金 twice a year.) But an author should not be
in it 厳密に for the money. Any individual who has the technical
know-how to 令状 a 広大な／多数の／重要な 調書をとる／予約する can make more money plying
their 貿易（する） rather than 令状ing about it ? period. A 調書をとる／予約する
will take hundreds of hours of direct 令状ing time, 加える more
time 伴う／関わるd in 研究, and even more time spent acquiring
background. That same 量 of time could invariably be better
spent 法案ing out at a 顧問’s 率.
That said, there are 重要な advantages to 令状ing (or editing) a
調書をとる／予約する beyond money and the scratching of the natural “I want to 令状 a
調書をとる／予約する” itch. First, many authors feel a need to give 支援する to the community
from which they learned so much, and a 調書をとる／予約する is a 広大な／多数の／重要な medium to do that.
Second, a 調書をとる／予約する is a 広大な／多数の／重要な way to develop visibility and 付加 technical
信任状. Most of my authors and tech editors have 獲得するd 協議するing
事業／計画（する）s (either as a 十分な-time developer or on the 味方する) as a result
of readers 接触するing them. In 新規加入, the 信用性 that comes from
having written a 広大な／多数の／重要な 調書をとる／予約する 許すs the author or editor to 増加する their
法案ing 率s.
And there are two more things. Once an author has submitted their final
manuscript, they (and the tech editor and 地位，任命する-print editor) can also
get complimentary copies of every 調書をとる／予約する we produce until the end of time.
And 令状ing a 調書をとる／予約する is just plain fun. Hard work, sure,
but so is climbing a mountain, and that's why people ひもで縛る on the boots.
What about tech editors? They, too, get a check every
once in a while, a lifetime 供給（する） of 調書をとる／予約するs, and their 指名する on the cover
of the 調書をとる／予約する. Anything else? I've 設立する 一般に that tech editors often
use the chance to tech a 調書をとる／予約する ーするために 確実にする they read every word
of a 調書をとる／予約する whose content they're 利益／興味d in. And others like to be 伴う／関わるd
in the 調書をとる／予約する publishing 商売／仕事 - just not as an author. Editing, while
十分な of its own special challenges, is definitely not as difficult as
doing the 初めの authoring. And some use technical editing as a way
to break into the authoring 商売／仕事.
|
