MSWord   1128

« earlier    

How can I include only part of an image caption in a table of figures in Microsoft Word? - Super User
How can I include only part of an image caption in a table of figures in Microsoft Word?

msword  word  captions  images  tableofcontents  magic 
6 weeks ago by sspela
Word Document Batch Processes
can this batch change headers footers in EntreArchitect templates?
MSword  Word  batch  productivity 
8 weeks ago by Dexxx
MS Word macro to accept all "format" changes
Sub AcceptFormatChanges()
Dim rev As Revision
For Each rev In ActiveDocument.Revisions
If Left(rev.FormatDescription, 10) = "Formatted:" Then
End If
Next rev
End Sub
vba  msword 
march 2017 by whkoh
Complexity and Strategy
“This perspective does cause one to turn a somewhat jaundiced eye towards claims of amazing breakthroughs with new technologies. Managed code was one that we argued about for a long time during this period. Leveraging open source also has some of the same dynamics. What I found is that advocates for these new technologies tended to confuse the productivity benefits of working on a small code base (small N essential complexity due to fewer feature interactions and small N cost for features that scale with size of codebase) with the benefits of the new technology itself — efforts using a new technology inherently start small so the benefits get conflated. Additionally, these new technologies (Java, C#, NodeJS is the latest one) start out with a much more functional initial set of base libraries and rich frameworks, certainly compared to what we saw in C and C++ and in the early days of either Mac or Windows application development.
In terms of our Functionality/Cost curves, this means that you push that curve significantly up the functionality axis at the start. This can create confusion for technical managers about whether you have simply translated a curve that still has the same fundamental shape or whether you have changed something significant about the shape or slope of the curve itself. This is especially true in an environment where every disciple of a new technology is singing its praises to the heavens. In actual practice, if the product stays small, you can essentially “book” that initial productivity gain — a clear win. If the product starts to grow complex — and you can predict that fairly directly by looking at the size of the development team — then costs will come to be dominated by that increasing feature interaction and essential complexity. Project after project has demonstrated there is nothing about language or underlying technical infrastructure that changes that fundamental curve.
The dynamic you see with especially long-lived code bases like Office is that the amount of framework code becomes dominated over time by the amount of application code and in fact frameworks over time get absorbed into the overall code base. The framework typically fails to evolve along the path required by the product — which leads to the general advice “you ship it, you own it”. This means that you eventually pay for all that code that lifted your initial productivity. So “free code” tends to be “free as in puppy” rather than “free as in beer”.
None of this argues against “lean startups” or “minimal viable products” or any of the other approaches that focus on accelerating the process of finding the right product/market fit or feature viability. Continuous agile delivery is a fundamental change in development process because it removes the horrendous friction and delay between feature development and feature use. (There are other benefits as well but again worth a separate post.) But continuous delivery does not change anything about the essential complexity I am discussing here except so far as it helps prevent the team from building features that increase complexity but do not add user value. The highest cost feature you can build is the one that is not used or valued — your cost / benefit ratio is infinite. You continue paying to integrate with that useless feature as you build every additional feature from that point forward.”
code  business  strategy  microsoft  google  googledocs  msword  complexity 
march 2017 by migurski

« earlier    

related tags

214  accessibility  accessible_presentations  addin  adobe  appellate_briefs  apple  automation  backward-compatibility  batch  bisexual  business  captions  clean  cleaner  code  coding  com  complexity  content  conversion  converter  dissertation  doc  edd703  emacs  eng1111  eng1112  epub  file-formats  file  footer  gay  git  google  googledocs  header  howto  html  html_editor  images  it  jira  layout  legal  legal_tech  letterhead  mac  macro  macros  magic  mailmerge  markdown  markup  mediawiki  merge  microsoft  microsoftword  msexcel  msoffice  msword  msword_macros  mysql  ooxml  osx  pandoc  pdf  php  poetry  powershell  productivity  programming  reference  resources  rstats  section  settings  stats  strategy  style  styles  survivalanalysis  swdev  tableofcontents  text  tips  tools  training  troubleshooting  tutoral  tutorial  twiki  ulysses  useful  vba  versioncontrol  webapp  wiki  windows  wishlist  word  wordpress  work  writing  wysiwyg  zotero 

Copy this bookmark: