At Seamplex we believe that engineers out to solve problems. This can be accomplished a wide variety of ways, from applying complex scientificknowledge up to using common sense and intuition. The main goal is to have a problem solved using the least possible effort (i.e. money). However, we see that there are a lot of
The following two examples will help to illustrate both cases.
Say you have to sign an NDA with a client, or prepare a quotation or work in a technical report with other people. Raise your hand if you would do something like this:
nda1.docto your client attached to an e-mail
nda1.docin your computer and save it.
nda1.docfrom your client.
nda2.docand sent it to the lawyer.
nda2.docyou also notice further misspellings and correct them. You now save as
nda-final.docto your client. 13. Then, you realize that even though it was named as final, that version does not have your misspelling corrections. So you attach to your client
You get the point. Because it has happened to you. And to me. A company I used to work to lost a bid because the document we finally sent did not contain a change I added to comply with the tender requirements. And I am sure something similar has happened to you.
Why do we accept this way of working? Are we dumb enough not to come up with a smarter way of working?
We at Seamplex think that this problem can be solved by thinking straightforward and combining knowledge that other engineers already developed (e.g. DCVS, Mercurial, Markdown, Pandoc, M4, TeX, and LaTeX )
See these two examples of documents generated the Seamplex way (i.e simple, but not simpler):
Let us do the following though experiment: ask an engineer to calculate the period of a simple pendulum of length 60 cm. And of course, tell her that we need a written report.
Raise your hand if you think we will get something like this:
.doc) and not in PDF.
See this example of an engineering document generated the Seamplex way (i.e simple, but not simpler):