One of the comments I received said that I kept giving bad
examples for conditions I disliked from previous workplaces,
instead of positive elements I would have liked to see. Another
- commentor told me in private, that he felt that the
+ commentor told me in private, that he felt that the
"End of IT Slavery" and other essays of mine reflected the
- fact that I had a "primadona attitude" instead of a more
+ fact that I had a "primadona attitude" instead of a more
positive "team-player" attitude.
them a serious thought, you can make such potential employees want
to work for you, love to work for you, want to stay, and be
happy as long as they are working for you. Furthermore, you will
- know better than to irrationaly fire perfectly good employees.
+ know better than to irrationaly fire perfectly good employees.
<ulink url="http://www.catb.org/esr/">Eric S.
Raymond's Homepage</ulink> and especially
- his <ulink url="http://www.catb.org/esr/writings/cathedral-bazaar/">the "Cathedral and the Baz
zar" series</ulink> and his
+ his <ulink url="http://www.catb.org/esr/writings/cathedral-bazaar/">the "Cathedral and the Bazar" series</ulink> and his
to become a Hacker"</ulink> document.
comparison to star programmers. (And according to
Law</ulink>, you can't effectively replace one good
- programer with many worse ones.)
+ programer with many worse ones.)
As I noted <ulink url="http://discuss.joelonsoftware.com/default.asp?joel.3.197867.7">there
but rather not being overly secretive. )
ly, you should avoid vendor lock-in: use standard
+ Finally, you should avoid vendor lock-in: use standard
or documented protocols and specifications,
- <section id="conditions--pa
+ <section id="conditions--pad-vacation">
<title>A Lot of Paid Vacation</title>
- Work on open-soure software or their own personal
+ Work on open-soure software or their own personal
A similar fallacy is the <emphasis role="bold">"Mountains
- of documentation fallacy"</emphasis> of having superflous
+ of documentation fallacy"</emphasis> of having superflous
commenting, Literate programming, etc. The problem with
this approach is that the extra documentation is often
redundant if the code is well written and factored out
Ayn Rand' Objectivism, Neo-Tech is the best idea-system
I've encountered yet. Note that it is easy to both
dismiss Neo-Tech as a stupid cult, or to hugely
- mis-understand it at first. So when reading Neo-Tech
+ misunderstand it at first. So when reading Neo-Tech
go over the material (preferably without skipping, but
possibly while taking breaks), and then let it sink
- Nevertheless, a workplace enou
crage its employees to note
+ Nevertheless, a workplace enourage its employees to note
down every useful knowledge and procedure. My friend once
told me that in his previous workplace they kept a
knowledge-base as a group of Microsoft Word documents stored
Raymond's "Tale of J. Random Newbie"</ulink> is
illustrative of the many problems programmers encounter
- in highly-prorietary environments. Generally however,
+ in highly-prorietary environments. Generally however,
even if you're using proven, mature,
well-documented and functional technology, you are
likely to encounter bugs.
I was instructed to write a mail-processing framework
in PHP. Now since I know and love Perl, I know there
are many fine modules for doing that on <ulink url="http://sial.org/howto/perl/life-with-cpan/">CPAN (= The
- Comprensive Perl Archive Network)</ulink>, but there
+ Comprensive Perl Archive Network)</ulink>, but there
was little of substantial quality for PHP. At a certain
time I needed to register at a site, to download the
latest version of a PHP library, that was free software,
With my PHP code barely working and prune to many errors,
I decided to quit after about a month, out of being
- appaled by the bad code craftmanship I could do there.
+ appaled by the bad code craftmanship I could do there.
Make sure you don't repeat such a mistake.