- This topic has 165 replies, 13 voices, and was last updated 14 years, 4 months ago by UCGal.
-
AuthorPosts
-
July 11, 2010 at 3:24 PM #577878July 11, 2010 at 4:04 PM #576870svelteParticipant
[quote=larrylujack]
no offense, dude, but software engineers are a dime a dozen…literally[/quote]Sounds like they are more like $120K for one.
And if that what the market bears, the market must think that’s a reasonable value vs India, China, et al.
July 11, 2010 at 4:04 PM #576966svelteParticipant[quote=larrylujack]
no offense, dude, but software engineers are a dime a dozen…literally[/quote]Sounds like they are more like $120K for one.
And if that what the market bears, the market must think that’s a reasonable value vs India, China, et al.
July 11, 2010 at 4:04 PM #577492svelteParticipant[quote=larrylujack]
no offense, dude, but software engineers are a dime a dozen…literally[/quote]Sounds like they are more like $120K for one.
And if that what the market bears, the market must think that’s a reasonable value vs India, China, et al.
July 11, 2010 at 4:04 PM #577598svelteParticipant[quote=larrylujack]
no offense, dude, but software engineers are a dime a dozen…literally[/quote]Sounds like they are more like $120K for one.
And if that what the market bears, the market must think that’s a reasonable value vs India, China, et al.
July 11, 2010 at 4:04 PM #577899svelteParticipant[quote=larrylujack]
no offense, dude, but software engineers are a dime a dozen…literally[/quote]Sounds like they are more like $120K for one.
And if that what the market bears, the market must think that’s a reasonable value vs India, China, et al.
July 11, 2010 at 7:20 PM #576910CoronitaParticipant[quote=ucodegen]
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.
[/quote]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 π
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)…
July 11, 2010 at 7:20 PM #577006CoronitaParticipant[quote=ucodegen]
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.
[/quote]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 π
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)…
July 11, 2010 at 7:20 PM #577532CoronitaParticipant[quote=ucodegen]
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.
[/quote]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 π
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)…
July 11, 2010 at 7:20 PM #577638CoronitaParticipant[quote=ucodegen]
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.
[/quote]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 π
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)…
July 11, 2010 at 7:20 PM #577938CoronitaParticipant[quote=ucodegen]
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.
[/quote]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 π
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)…
July 11, 2010 at 8:32 PM #576925AnonymousGuest>> 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
20 yrs ago it wasnt like that. i took and ta’ed an real time systems/concurrency class at ucsd. that class had hw, where you had to use sw to control trains that shared an intersection. if you didnt understand semaphores by then, you were hopeless lost.
granted this was an upper division elective and not required. the switch over to java started about 10 yrs ago, and actually a sad state of affairs. 10 yrs ago the assembly stuff would weed everyone out. here comes the fuddy dud…what amazes me now about the kids in the last 10 yrs is how disconnected there are to HOW things work: hw, stacks, linkers, compilers, build systems, etc. tools do everything for them(even write code for them!). when they get if if those tools dont exist, they’re useless. for embedded stuff their done. stick a fork in them. unfortunately the learning curve is too steep once they’re employed (a few bright ones can get by).
July 11, 2010 at 8:32 PM #577021AnonymousGuest>> 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
20 yrs ago it wasnt like that. i took and ta’ed an real time systems/concurrency class at ucsd. that class had hw, where you had to use sw to control trains that shared an intersection. if you didnt understand semaphores by then, you were hopeless lost.
granted this was an upper division elective and not required. the switch over to java started about 10 yrs ago, and actually a sad state of affairs. 10 yrs ago the assembly stuff would weed everyone out. here comes the fuddy dud…what amazes me now about the kids in the last 10 yrs is how disconnected there are to HOW things work: hw, stacks, linkers, compilers, build systems, etc. tools do everything for them(even write code for them!). when they get if if those tools dont exist, they’re useless. for embedded stuff their done. stick a fork in them. unfortunately the learning curve is too steep once they’re employed (a few bright ones can get by).
July 11, 2010 at 8:32 PM #577547AnonymousGuest>> 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
20 yrs ago it wasnt like that. i took and ta’ed an real time systems/concurrency class at ucsd. that class had hw, where you had to use sw to control trains that shared an intersection. if you didnt understand semaphores by then, you were hopeless lost.
granted this was an upper division elective and not required. the switch over to java started about 10 yrs ago, and actually a sad state of affairs. 10 yrs ago the assembly stuff would weed everyone out. here comes the fuddy dud…what amazes me now about the kids in the last 10 yrs is how disconnected there are to HOW things work: hw, stacks, linkers, compilers, build systems, etc. tools do everything for them(even write code for them!). when they get if if those tools dont exist, they’re useless. for embedded stuff their done. stick a fork in them. unfortunately the learning curve is too steep once they’re employed (a few bright ones can get by).
July 11, 2010 at 8:32 PM #577653AnonymousGuest>> 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
20 yrs ago it wasnt like that. i took and ta’ed an real time systems/concurrency class at ucsd. that class had hw, where you had to use sw to control trains that shared an intersection. if you didnt understand semaphores by then, you were hopeless lost.
granted this was an upper division elective and not required. the switch over to java started about 10 yrs ago, and actually a sad state of affairs. 10 yrs ago the assembly stuff would weed everyone out. here comes the fuddy dud…what amazes me now about the kids in the last 10 yrs is how disconnected there are to HOW things work: hw, stacks, linkers, compilers, build systems, etc. tools do everything for them(even write code for them!). when they get if if those tools dont exist, they’re useless. for embedded stuff their done. stick a fork in them. unfortunately the learning curve is too steep once they’re employed (a few bright ones can get by).
-
AuthorPosts
- You must be logged in to reply to this topic.