> I have worked in languages and technologies that are near unusable without an IDE.
I had a colleague once who was considered a "Perl expert".
His work pattern was pretty consistent:
When assigned a new task, he'll
- Fire up Komodo IDE
- As a start: rename an older, similar but incomplete script from the same problem group
- Google for a missing part with "Perl" included in the query
- Paste new chunks and wait if Komodo complains by underlining some line
( something like "fly-make perl -c " is activated by default here)
- Make some adjustments, always waiting if lines are underlined
- Repeat the googling process with other missing functionality
- Occasionally run it from the editor
- If it fails add a break point by clicking the line, it now runs under the debugger and stops there
- If inspecting the variables which are shown in a extra pane don't reveal problems stop at the next break-point
- In 80+x % cases he's "successful" with this strategy
- In the other 20-x % cases he came ranting into my office saying that Perl is totally inappropriate for the job ...
... and that obviously Python, Ruby, * (fill it in) is FAR better
OK you might say this is not a real "expert" ...
... he doesn't even know how
- to read documentation
- to use perl -c
- to start the debugger and use it's commands
- and other things
But management - which is non IT and has no clue about programming and the long term costs of boiler plating and cargo cult - will say
- that our group has a cheap company license for Komodo
- he gets most his jobs "done"
- that the investment was obviously justified.
- and he can't be blamed for Perl's complexity
Needles to say this "expert" will tell the world that:
Perl is near unusable without an IDE like Komodo.
Punchline? Already one week after I started in this project I knew Komodo (V6 back then) better than the rest of the team together. To be fair ... with all my Emacs experience I knew what to look for.
For instance I tried to help them to switch the internal REPL from Python to Perl - for vain.
That much about bundles with useful defaults.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
