[olug] need some quick help with sed

[DYNATRON tech]

craig,
i completely agree with you when you say "*tends* to stay bad code", as you
also understand that this isn't always the case. little effort often means
questionable utility, i would guess this may be a reason that crappy things
stay crappy. in my case, it never was crap, but there was a matter of seeing
how helpful the code was going to be before putting a ton of effort into it.
my bf script was a good example. it's only useful in a rare circumstance, so
it was functional at v1.0 and never revised. however, i did feel it was
important for the manufacturers to close the security hole, so i posted the
code on one of my websites. unfortunately the hole still exists in the
newish equipment i've pointed it at.
as far as you not enjoying the writing of code, i can't relate. if it were
socially acceptable, i would do nothing else but tech (especially writing
code). it's a good thing i have non-tech friends who pry my fingers from the
keyboard.
my advice...pick up that book, as long as you have an exit strategy.

aric,
don't feed the animals. especially yoghurt.
i appreciate the link (my second post).


obi,
what's this all about?
you don't even know me, dude.
i don't know what your deal is, but you should take a pill.
follow the path of a jedi, not a spoiled child.

*"What kind of tiny toy projects do you write?  Perhaps the fact
that it's a shell script should answer that..."*
a friend, former employer, and fellow OLUGger (TC - much respect) taught me
xslt a year ago while working on a different project equally massive in
scale. in my spare time i flow-charted a personal project for when i earned
the skills to code it. i've improved my skills, and now i'm coding it. the
bash scripts just run the back-end on the server. i'm not the kind who
measures software by the byte, however, the whole project now is 1.3MB of
hand-written code, 2MB of generated code, and so far just 500KB of xml data.
once the back-end is fully autonomous, it writes it's own code. at that
point, the sky isn't even the limit.
bash, xslt, python, xml data sets, a handful of css skins, + xslt generated
ajax-js/html and rss to make it universal.
yeah, dude. tiny toy project.....FU2, i guess.

*"I haven't flowcharted anything since 8th grade computer class."*
i can't believe i just got flamed for good project prep.
another baseless insult for no apparent reason....FU2, again.

*"Code that's initially ugly, poorly written, and hard to maintain will
forever remain ugly, poorly written, and hard to maintain.*"
you saw the two lines of code and publicly insinuated that the whole project
was forever doomed to look like your
<http://godnet.org/rich/mullins2.gif>face (i've never seen your
face...get the
point <http://godnet.org/rich/mullins2.gif>?). those that know me, and those
that have written code with me, know that your accusations are the opposite
of my faults.

*"This isn't just a theory.*"
no, it's not. it's you passing judgement on someone you've never even met.
yes, i revise my code once it is functional if it proves useful enough to
warrant a new version.
that's how writing software works. anyone with the intelligence to use sed
should know that by now.
as far as this project....it's a keeper, and i've gone through it with the
sweeper eight times already.

i posted on olug for help with one line of code, not for some infantile
flame war. you are doing a disservice to the mailing list when you make
unfounded personal attacks. what's the real beef anyway? politics? religion?
repressed?
it would be Q-BASIC to verbally demolish you, but i'm gonna take the high
road....with an exception.

i decided to pay a little tribute.
there are two well-commented lines of code that i decided not change so you
can be fully satisfied in knowing that you're always right.
it's my little christmas gift to you.
happy holidays, mf.

i'll see you at the next OLUG meeting.



On Tue, Dec 22, 2009 at 8:20 AM, Craig Wolf <CJWolf at mpsomaha.org> wrote:

> I will agree that bad code tends to stay bad code, even when I, er, the
> author just had to get this "one thing working" and then another fire puts
> it off, and another and the original code is forgotten until something has
> to change or the interface to another piece of code is changed.  I have been
> on both sides of this coding fun and don't like either one, writing
> something "temporarily" or editing code from someone else what just threw it
> together until get back to it.  These days, I am primarily sysadmin but
> vividly remember my coding days.  I am struggling to even pickup this
> scripting book because it starts to pull me back in that direction and I
> don't want to live there again.  8(
>
> Craig Wolf
> Linux Server Support
> Backups Administrator
> Desktop/Network Specialist
> Desk: (402)715-6283
> Cell: (402)510-0301
>
>
> >>> "Aric Aasgaard" <aric at omahax.com> 12/21/2009 >>>
> You guys should whip out your schwartz and duel!!!!!
>
> I know I have sed this before but this is a good resource.
> http://www.grymoire.com/Unix/Sed.html
>
>
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://lists.olug.org/mailman/listinfo/olug
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://lists.olug.org/mailman/listinfo/olug
>



-- 
dynatron digital services
box 191 - 68037
www.dynatron.org
dynatron at gmail.com