Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming > #3636

Re: [OT] engineering

Path csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From Rainer Weikusat <rweikusat@mssgmbh.com>
Newsgroups comp.lang.perl.misc, comp.programming
Subject Re: [OT] engineering
Date Wed, 17 Jul 2013 15:53:57 +0100
Lines 22
Message-ID <8738rdz18a.fsf@sapphire.mobileactivedefense.com> (permalink)
References <krkm21$19jd$1@news.ntua.gr> <87li5dclp5.fsf@sapphire.mobileactivedefense.com> <3q63bax8mr.ln2@goaway.wombat.san-francisco.ca.us> <87k3kxasym.fsf@sapphire.mobileactivedefense.com> <hsi3ba-va22.ln1@anubis.morrow.me.uk> <87li5coi6v.fsf@sapphire.mobileactivedefense.com> <874nc0w72t.fsf_-_@violet.siamics.net> <877ggw2gnk.fsf_-_@sapphire.mobileactivedefense.com> <87mwpouk89.fsf_-_@violet.siamics.net> <8761wai616.fsf@sapphire.mobileactivedefense.com> <87a9llv8n2.fsf@violet.siamics.net>
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
X-Trace individual.net wblDMZjTvlrQuKdLED4YkAr8At5D0HnNsr8KIebeEVB7a+39I=
Cancel-Lock sha1:F9yl8VRv5/q6Tum4xMubRN2VNFw= sha1:vBH36S7BibhFhXeWGCV1Aa8SKQc=
User-Agent Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
Xref csiph.com comp.lang.perl.misc:8739 comp.programming:3636

Cross-posted to 2 groups.

Show key headers only | View raw

Ivan Shmakov <oneingray@gmail.com> writes:

[...]

> 	My point is simple: if the deadline is today, one has to forget
> 	about "science" (be it Wirth's, Borlaug's, or someone's else),
> 	and use whatever "ingredients" available to solve the task at
> 	hand.  Be it a program, or a dinner.

I also wrote a longer reply to this which I shouldn't have posted
(which will continue to be available via servers not processing
cancels) but this is the more interesting part: According to my
experience, writing 'bad' code (for a suitable definition of 'bad')
doesn't take less time than writing 'good' code (for a suitable
definition of 'good') to begin with and 'corners cut in order to be
able to present something superficially suitable to $superior now'
will come back to haunt you, ie, when taking the time necessary for
repairs/ maintenance and the time wasted trying to puzzle out the
meaning of 'the usual thicket' into account, 'bad code' needs a lot
more time overall.

Back to comp.programming | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[OT] engineering Ivan Shmakov <oneingray@gmail.com> - 2013-07-15 11:37 +0000
  Re: [OT] engineering Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-07-16 21:49 +0100
    Re: [OT] engineering Ivan Shmakov <oneingray@gmail.com> - 2013-07-17 09:27 +0000
      Re: [OT] engineering Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-07-17 15:53 +0100
      Re: [OT] engineering Ivan Shmakov <oneingray@gmail.com> - 2013-07-22 10:36 +0000
        Re: [OT] engineering Shmuel (Seymour J.) Metz <spamtrap@library.lspace.org.invalid> - 2013-07-23 06:43 -0400
      Re: [OT] engineering Ivan Shmakov <oneingray@gmail.com> - 2013-07-22 10:38 +0000
  Re: [OT] engineering Rui Maciel <rui.maciel@gmail.com> - 2013-07-26 10:09 +0100

csiph-web