[ucodegen]

[quote grepper]
ucodegen, you cant be the original grep writer(written 40 yrs ago), k.t., can you? what did your tool grepper/greper do?
[/quote]
I worked on a later version than the (nearly 40 year old) version you are referencing. It was a fast recursive directory search version using memory mapped IO. It was done before the ‘recursive directory search’ option was added to grep/fgrep/egrep. I was getting annoyed when I needed to search for variable declarations in large source trees.. called it grepper because it was a ‘recursive grep’.. (yes, I’m older than 40… )

There have been many authors for ‘grep’ or versions thereof, though most have settled now on the GNU grep set. No, I am not k.t…

[quote grepper]
i’m a user of grep and wanted a reference to some tool that i find useful. thought it was better than devnull or devzero 🙂
[/quote]
devnull is not such a bad ‘handle’.. there is also devy and devn on some systems (always replies ‘yesn’ or ‘non’ on some systems, not all flavors had it)

‘yacc’ could also be a good handle.. 😉
.. it predates bison..

[quote grepper]
“compiler class @ UCSD” — that class(2 parter) also thinned the ranks out too. along w/ data structures 2 parter, where you learned c++ on the fly, they didnt have a c warm up class either.
[/quote]
I took mine in two parts, over two different years. This did create a problem. I had two different languages to deal with and two different languages to write in. I had to do construction work to pay for my tuition.. so I took a year+ off.

The ‘C’ warm up class was EECS 173 if I remember correctly. Not much of a warm up.. but you got exposure to multiple languages like Lisp, C, SNOBOL.. This was in the days when EECS 61 was Pascal based. I don’t remember what they did after Pascal went by the wayside. Did they replace Pascal w/ C or C++ in EECS 61? Or did they keep teaching EECS 61 in Pascal until Java came along?

I finished my EECS 163 before C++ came along. First quarter was a pain (because of teammates), second quarter was fun but timeconsuming(partially because of teammates). I was working as an admin at the same time as that class, so I could use their Unix machine after hours for the assignment, as well as some Sun2’s @ UCSD. EECS 161A/B and ECS163A/B would really tie up UCSDs machines.

[ucodegen]

[quote grepper]
ucodegen, you cant be the original grep writer(written 40 yrs ago), k.t., can you? what did your tool grepper/greper do?
[/quote]
I worked on a later version than the (nearly 40 year old) version you are referencing. It was a fast recursive directory search version using memory mapped IO. It was done before the ‘recursive directory search’ option was added to grep/fgrep/egrep. I was getting annoyed when I needed to search for variable declarations in large source trees.. called it grepper because it was a ‘recursive grep’.. (yes, I’m older than 40… )

There have been many authors for ‘grep’ or versions thereof, though most have settled now on the GNU grep set. No, I am not k.t…

[quote grepper]
i’m a user of grep and wanted a reference to some tool that i find useful. thought it was better than devnull or devzero 🙂
[/quote]
devnull is not such a bad ‘handle’.. there is also devy and devn on some systems (always replies ‘yesn’ or ‘non’ on some systems, not all flavors had it)

‘yacc’ could also be a good handle.. 😉
.. it predates bison..

[quote grepper]
“compiler class @ UCSD” — that class(2 parter) also thinned the ranks out too. along w/ data structures 2 parter, where you learned c++ on the fly, they didnt have a c warm up class either.
[/quote]
I took mine in two parts, over two different years. This did create a problem. I had two different languages to deal with and two different languages to write in. I had to do construction work to pay for my tuition.. so I took a year+ off.

The ‘C’ warm up class was EECS 173 if I remember correctly. Not much of a warm up.. but you got exposure to multiple languages like Lisp, C, SNOBOL.. This was in the days when EECS 61 was Pascal based. I don’t remember what they did after Pascal went by the wayside. Did they replace Pascal w/ C or C++ in EECS 61? Or did they keep teaching EECS 61 in Pascal until Java came along?

I finished my EECS 163 before C++ came along. First quarter was a pain (because of teammates), second quarter was fun but timeconsuming(partially because of teammates). I was working as an admin at the same time as that class, so I could use their Unix machine after hours for the assignment, as well as some Sun2’s @ UCSD. EECS 161A/B and ECS163A/B would really tie up UCSDs machines.

[ucodegen]

[quote grepper]
ucodegen, you cant be the original grep writer(written 40 yrs ago), k.t., can you? what did your tool grepper/greper do?
[/quote]
I worked on a later version than the (nearly 40 year old) version you are referencing. It was a fast recursive directory search version using memory mapped IO. It was done before the ‘recursive directory search’ option was added to grep/fgrep/egrep. I was getting annoyed when I needed to search for variable declarations in large source trees.. called it grepper because it was a ‘recursive grep’.. (yes, I’m older than 40… )

There have been many authors for ‘grep’ or versions thereof, though most have settled now on the GNU grep set. No, I am not k.t…

[quote grepper]
i’m a user of grep and wanted a reference to some tool that i find useful. thought it was better than devnull or devzero 🙂
[/quote]
devnull is not such a bad ‘handle’.. there is also devy and devn on some systems (always replies ‘yesn’ or ‘non’ on some systems, not all flavors had it)

‘yacc’ could also be a good handle.. 😉
.. it predates bison..

[quote grepper]
“compiler class @ UCSD” — that class(2 parter) also thinned the ranks out too. along w/ data structures 2 parter, where you learned c++ on the fly, they didnt have a c warm up class either.
[/quote]
I took mine in two parts, over two different years. This did create a problem. I had two different languages to deal with and two different languages to write in. I had to do construction work to pay for my tuition.. so I took a year+ off.

The ‘C’ warm up class was EECS 173 if I remember correctly. Not much of a warm up.. but you got exposure to multiple languages like Lisp, C, SNOBOL.. This was in the days when EECS 61 was Pascal based. I don’t remember what they did after Pascal went by the wayside. Did they replace Pascal w/ C or C++ in EECS 61? Or did they keep teaching EECS 61 in Pascal until Java came along?

I finished my EECS 163 before C++ came along. First quarter was a pain (because of teammates), second quarter was fun but timeconsuming(partially because of teammates). I was working as an admin at the same time as that class, so I could use their Unix machine after hours for the assignment, as well as some Sun2’s @ UCSD. EECS 161A/B and ECS163A/B would really tie up UCSDs machines.

[ucodegen]

[quote 5yearwaiter]
It was dig outside of the entire bottom and there was some iron wiring rounded through entire foundation. Didn’t see nor watch what they might have done inside and perhaps (sure) they didn’t do inside at all.
[/quote]

Sounds like the foundation was not deep enough in its original construction, so they dug a second foundation immediately outside and tied them together through rebar (epoxying the bars into the original foundation).

From the pictures, it doesn’t look like the interiors were touched.

-this is only surmising, since I don’t have pictures of the work.

[ucodegen]

[quote 5yearwaiter]
It was dig outside of the entire bottom and there was some iron wiring rounded through entire foundation. Didn’t see nor watch what they might have done inside and perhaps (sure) they didn’t do inside at all.
[/quote]

Sounds like the foundation was not deep enough in its original construction, so they dug a second foundation immediately outside and tied them together through rebar (epoxying the bars into the original foundation).

From the pictures, it doesn’t look like the interiors were touched.

-this is only surmising, since I don’t have pictures of the work.

[ucodegen]

[quote 5yearwaiter]
It was dig outside of the entire bottom and there was some iron wiring rounded through entire foundation. Didn’t see nor watch what they might have done inside and perhaps (sure) they didn’t do inside at all.
[/quote]

Sounds like the foundation was not deep enough in its original construction, so they dug a second foundation immediately outside and tied them together through rebar (epoxying the bars into the original foundation).

From the pictures, it doesn’t look like the interiors were touched.

-this is only surmising, since I don’t have pictures of the work.

[ucodegen]

[quote 5yearwaiter]
It was dig outside of the entire bottom and there was some iron wiring rounded through entire foundation. Didn’t see nor watch what they might have done inside and perhaps (sure) they didn’t do inside at all.
[/quote]

Sounds like the foundation was not deep enough in its original construction, so they dug a second foundation immediately outside and tied them together through rebar (epoxying the bars into the original foundation).

From the pictures, it doesn’t look like the interiors were touched.

-this is only surmising, since I don’t have pictures of the work.

[ucodegen]

[quote 5yearwaiter]
It was dig outside of the entire bottom and there was some iron wiring rounded through entire foundation. Didn’t see nor watch what they might have done inside and perhaps (sure) they didn’t do inside at all.
[/quote]

Sounds like the foundation was not deep enough in its original construction, so they dug a second foundation immediately outside and tied them together through rebar (epoxying the bars into the original foundation).

From the pictures, it doesn’t look like the interiors were touched.

-this is only surmising, since I don’t have pictures of the work.

[ucodegen]

[quote flu]
Sounds a lot like ABE systems. (defense company with their letters purposely scrambled)…and their death spiral… Yeah, good lucky winning those government contracts and being able to execute…Oh wait…Never mind…Oops, I didn’t say that 🙂
[/quote]
Close.. and it is a defense company, though not ‘ABE’ systems. I did work for ‘ABE’ systems prevously, before they became ‘ABE’ and were of their original name.

[quote flu]
BTW: I was totally totally shocked to learn UCSD teaches very little embedded and real-time O.S and very little practical use on concurrency and multi-threading…Everything is Java. Totally unfrickinunbelievable…I remember taking O/S at USC and we had to write a stupid toy O/S (nachos, or something like that)…
[/quote]
I’ve noticed the same thing. A loss of the fundamentals. Too many students were having problems with it, and the powers that be wanted to be ‘relevant’ to the ‘new technology’. Oddly, they were doing this as the EE & CS departments were ‘impacted’ because of the number of students. They should have kept the fundamentals in as a way to weed out candidates.

I remember doing the compiler class @ UCSD without any additional ‘libraries’ that are given to you. In fact, I have heard that many of the projects are just ‘incorporating’ existing libraries to accomplish the projects vs writing the solution ‘cold’.

grepper:
How did you come up with your handle. It is an odd one, which happens to be the name of a simple utility I wrote a long-long time ago.

[ucodegen]

[quote flu]
Sounds a lot like ABE systems. (defense company with their letters purposely scrambled)…and their death spiral… Yeah, good lucky winning those government contracts and being able to execute…Oh wait…Never mind…Oops, I didn’t say that 🙂
[/quote]
Close.. and it is a defense company, though not ‘ABE’ systems. I did work for ‘ABE’ systems prevously, before they became ‘ABE’ and were of their original name.

[quote flu]
BTW: I was totally totally shocked to learn UCSD teaches very little embedded and real-time O.S and very little practical use on concurrency and multi-threading…Everything is Java. Totally unfrickinunbelievable…I remember taking O/S at USC and we had to write a stupid toy O/S (nachos, or something like that)…
[/quote]
I’ve noticed the same thing. A loss of the fundamentals. Too many students were having problems with it, and the powers that be wanted to be ‘relevant’ to the ‘new technology’. Oddly, they were doing this as the EE & CS departments were ‘impacted’ because of the number of students. They should have kept the fundamentals in as a way to weed out candidates.

I remember doing the compiler class @ UCSD without any additional ‘libraries’ that are given to you. In fact, I have heard that many of the projects are just ‘incorporating’ existing libraries to accomplish the projects vs writing the solution ‘cold’.

grepper:
How did you come up with your handle. It is an odd one, which happens to be the name of a simple utility I wrote a long-long time ago.

[ucodegen]

[quote flu]
Sounds a lot like ABE systems. (defense company with their letters purposely scrambled)…and their death spiral… Yeah, good lucky winning those government contracts and being able to execute…Oh wait…Never mind…Oops, I didn’t say that 🙂
[/quote]
Close.. and it is a defense company, though not ‘ABE’ systems. I did work for ‘ABE’ systems prevously, before they became ‘ABE’ and were of their original name.

[quote flu]
BTW: I was totally totally shocked to learn UCSD teaches very little embedded and real-time O.S and very little practical use on concurrency and multi-threading…Everything is Java. Totally unfrickinunbelievable…I remember taking O/S at USC and we had to write a stupid toy O/S (nachos, or something like that)…
[/quote]
I’ve noticed the same thing. A loss of the fundamentals. Too many students were having problems with it, and the powers that be wanted to be ‘relevant’ to the ‘new technology’. Oddly, they were doing this as the EE & CS departments were ‘impacted’ because of the number of students. They should have kept the fundamentals in as a way to weed out candidates.

I remember doing the compiler class @ UCSD without any additional ‘libraries’ that are given to you. In fact, I have heard that many of the projects are just ‘incorporating’ existing libraries to accomplish the projects vs writing the solution ‘cold’.

grepper:
How did you come up with your handle. It is an odd one, which happens to be the name of a simple utility I wrote a long-long time ago.

[ucodegen]

[quote flu]
Sounds a lot like ABE systems. (defense company with their letters purposely scrambled)…and their death spiral… Yeah, good lucky winning those government contracts and being able to execute…Oh wait…Never mind…Oops, I didn’t say that 🙂
[/quote]
Close.. and it is a defense company, though not ‘ABE’ systems. I did work for ‘ABE’ systems prevously, before they became ‘ABE’ and were of their original name.

[quote flu]
BTW: I was totally totally shocked to learn UCSD teaches very little embedded and real-time O.S and very little practical use on concurrency and multi-threading…Everything is Java. Totally unfrickinunbelievable…I remember taking O/S at USC and we had to write a stupid toy O/S (nachos, or something like that)…
[/quote]
I’ve noticed the same thing. A loss of the fundamentals. Too many students were having problems with it, and the powers that be wanted to be ‘relevant’ to the ‘new technology’. Oddly, they were doing this as the EE & CS departments were ‘impacted’ because of the number of students. They should have kept the fundamentals in as a way to weed out candidates.

I remember doing the compiler class @ UCSD without any additional ‘libraries’ that are given to you. In fact, I have heard that many of the projects are just ‘incorporating’ existing libraries to accomplish the projects vs writing the solution ‘cold’.

grepper:
How did you come up with your handle. It is an odd one, which happens to be the name of a simple utility I wrote a long-long time ago.

[ucodegen]

[quote flu]
Sounds a lot like ABE systems. (defense company with their letters purposely scrambled)…and their death spiral… Yeah, good lucky winning those government contracts and being able to execute…Oh wait…Never mind…Oops, I didn’t say that 🙂
[/quote]
Close.. and it is a defense company, though not ‘ABE’ systems. I did work for ‘ABE’ systems prevously, before they became ‘ABE’ and were of their original name.

[quote flu]
BTW: I was totally totally shocked to learn UCSD teaches very little embedded and real-time O.S and very little practical use on concurrency and multi-threading…Everything is Java. Totally unfrickinunbelievable…I remember taking O/S at USC and we had to write a stupid toy O/S (nachos, or something like that)…
[/quote]
I’ve noticed the same thing. A loss of the fundamentals. Too many students were having problems with it, and the powers that be wanted to be ‘relevant’ to the ‘new technology’. Oddly, they were doing this as the EE & CS departments were ‘impacted’ because of the number of students. They should have kept the fundamentals in as a way to weed out candidates.

I remember doing the compiler class @ UCSD without any additional ‘libraries’ that are given to you. In fact, I have heard that many of the projects are just ‘incorporating’ existing libraries to accomplish the projects vs writing the solution ‘cold’.

grepper:
How did you come up with your handle. It is an odd one, which happens to be the name of a simple utility I wrote a long-long time ago.

[ucodegen]

[quote larrylujack]
no offense, dude, but software engineers are a dime a dozen…literally, so don’t take yerself so seriously….
[/quote]
Sounds like typical MBA think. Completely ignores skill levels, experience, and ‘rate of production’. Rate of production is hard to quantify, though the most ‘popular’ and overused is SLOC/hr. The reason why SLOC/hr is not that good is that some software engineers can write the same function in software with far fewer SLOC than another.

Kind of reminds me of my experience where I was laid off. A new VP of the division came in and chopped the ‘highly compensated’ software engineers and other ‘highly compensated’ employees, except ironically; management layers. He completely ignored the capability of the people he laid off and didn’t allow projects to ‘bid’ on people being laid off on the condition that they release a certain number of their own.

The result was a lot of bad feeling, since the “laid off” were long-timers that were responsible for a lot of what the company had come up and were the ‘go-to’ people for technical questions.. what is the use of company loyalty? Now the company has re-hired several of these people, including myself, as ‘consultants’ or ‘part time’ to get the work complete. Some of them refused to come back to work for the company.

The whole purpose of the layoff was to reduce the cost structure so that the burden rate was less.. after the layoff, the burden rate actually went up — oops.

[quote flu]
even with some of the easiest/stupid shit totally fvcked up like method names completely misspelled (getRecievedPakcetTipe()) in a public API you give to customers, after supposedly it was code/design reviewed, blocking/synchronous calls across networks with high latency ???
[/quote]
The last one, is one I have seen too much of.. as well as very poorly structured code. Code that almost looked like.. “well, lets try this.. no that didn’t work.. lets try this.. no that didn’t work either” style of software engineering. I have also run across several multiprocessor race conditions in code, not protected by a semaphore/guard.

When I was going through College, I used to TA software engineering courses. Through experience, I found that some people had an innate ability, some people were more ‘mechanical’ about it and others just could not ‘get it’.

[ucodegen]

[quote larrylujack]
no offense, dude, but software engineers are a dime a dozen…literally, so don’t take yerself so seriously….
[/quote]
Sounds like typical MBA think. Completely ignores skill levels, experience, and ‘rate of production’. Rate of production is hard to quantify, though the most ‘popular’ and overused is SLOC/hr. The reason why SLOC/hr is not that good is that some software engineers can write the same function in software with far fewer SLOC than another.

Kind of reminds me of my experience where I was laid off. A new VP of the division came in and chopped the ‘highly compensated’ software engineers and other ‘highly compensated’ employees, except ironically; management layers. He completely ignored the capability of the people he laid off and didn’t allow projects to ‘bid’ on people being laid off on the condition that they release a certain number of their own.

The result was a lot of bad feeling, since the “laid off” were long-timers that were responsible for a lot of what the company had come up and were the ‘go-to’ people for technical questions.. what is the use of company loyalty? Now the company has re-hired several of these people, including myself, as ‘consultants’ or ‘part time’ to get the work complete. Some of them refused to come back to work for the company.

The whole purpose of the layoff was to reduce the cost structure so that the burden rate was less.. after the layoff, the burden rate actually went up — oops.

[quote flu]
even with some of the easiest/stupid shit totally fvcked up like method names completely misspelled (getRecievedPakcetTipe()) in a public API you give to customers, after supposedly it was code/design reviewed, blocking/synchronous calls across networks with high latency ???
[/quote]
The last one, is one I have seen too much of.. as well as very poorly structured code. Code that almost looked like.. “well, lets try this.. no that didn’t work.. lets try this.. no that didn’t work either” style of software engineering. I have also run across several multiprocessor race conditions in code, not protected by a semaphore/guard.

When I was going through College, I used to TA software engineering courses. Through experience, I found that some people had an innate ability, some people were more ‘mechanical’ about it and others just could not ‘get it’.

[Author]

Posts