I work at Honeywell, Inc. at a Web-Dev type internship. It's pretty good -- the work is manageable and the atmosphere is worthwhile. The pay is pretty good, too.
I *almost* sprang for a Dot-Com a while back, but thankfully I didn't (they 'hired' me, but the employment agreement was terrible) -- I was going to get paid in worthless, worthless stock. I passed it up and stayed at places that pay me actual money.
So, back to the story at hand -- there are internships out there but it helps to know the right people and make a name for yourself first.
I work for a Fourtune 500 company (intern) working with a software & hardware development model. The model that we use constantly goes through changes and is very sucessful in terms of delivering software and hardware on time, and defect free. I have no clue about budget, but I'd guess that it is not over budget either. Working here has given me a favorable view of software engineering. Every process is laid out and explained, and there are many tools at our disposal, including a requirements tool, a UML tool, code generation tools, code testing tools, etc.
Now for the rant. I also go to a large University 20 miles down the road, and I am taking their software engineering course (<- yay for relevance). Among CS majors there is a bad reputation for the SE class, that it is never organized well and leaves students with a bad taste for SE. In my class, we are currently in the 'Design' phase for our semester-long project, we will be done tomorrow. The Implementation phase is a week long. That's right, a week. We spent months on the requirement and ooa phases, but they are still unclear (because the document that calls for them is unclear), and now we have a week to iron everything out. This class leaves me with an unfavorable view of software engineering.
I think that more colleges should teach software engineering not as just one class but as an approach along with code classes. It makes sense when teaching people how to code that one should also teach them the likely environment in which they will code, otherwise students will get the impression that they can opt-out of having to deal with software engineering.
Has software engineering become better? Probably. Would you be able to tell when taking the class that I am? Hell no.
Slow - yes, but don't blame the CPU
on
Is Mac OS X Slow?
·
· Score: 1
Overall, I don't think that given machine running OS X is slow, but on some things it seems to be absolutely DEAD.
I must preface this by the computers I've used: Mac OS X: G4 Cube @ 400 MHz Brand-new-iMac @ something
OS 9: Macintosh 512k - up
Linux: Pentium 133 and up
DOS/Win: 386DX-20 and up
by 'up', I mean all the way to the New Hotness machines.
I think that OS X has _serious_ filesystem problems, HFS+ is a little faster, but for my use, worthless. Yesterday I installed xfree86 from a tgz package (our system) on the new iMac, and it took over 10 minutes. On linux, that only takes a minute or two. Application launches like XDarwin take forever. I have been happy, though, with image rendering and web rendering, and Quartz Extreme is pretty nice, although nothing can compare to linux (icewm & 4.2.1) for response.
I have been running the CPU monitor app and it is hardly ever at 100%, so disk I/O is probably to blame.
Side note: anyone notice that fsck dies with a 'Bus Error' sometimes, and then, ironically, your installation is f*cked.
I work for a large university, and I've been working to integrate Mac OS X with flat BSD files (for both the GUI and other environments). I have some tips for anyone intent on doing the same - dave (at) math.umn.edu. Apple support (the people to complain about when you've already bought the product) didn't help me at all.
Back to the business: Gordon Shukwit (who I talked to last week) is writing white papers on integration with Active Directory, and said that "[he'd] have them done soon" (<- perfect for slashback). I won't publish his e-mail address because having a slashdot story about it is already enough pressure:)
It's wayyyyy too long for here, so I shamelessly plug the website. I tried to keep it at least a little bit funny. As a Sys Adm, either you havve to take a proactive stance on cruft, or just let everything sit and collect.
To have a proactive stance, but concede that you cannot fix everything and reinstall thusly (better if it's automated, and where I work, is it ever) in my opinion is the best. The cruft (xcept users' crap, but that's what quota is for) is gone, and most (usually all) people don't notice when the reinstall happens. In case anyone cares, we use slack packages.
The U of M's OIT (office of information tech.), outlawed kazaa and rate limited it, so you'd think they'd hate it enough not to study it... (hey, it was a big deal while I was in The Dorms)
They must have done it at HP to get around Packeteer.
This is not easy, Coward. You'd need a giant voltage regulator setup. However, if you want to build a circuit to change 12V to 5V that _doesn't_ suck, you would need to convert it to AC first because AC is the only type of current that can be transformed by coils. So, inverting the power is less complicated than scrweing with the DC.
The power supply already does the job of regulating power, why get rid of it?
As long as we're talking about ghetto UPSes
on
Do-it-yourself UPS
·
· Score: 1
When I was shopping in my local store I found dead power backup units for $5 each and fixed them up to create several UPSes. I used a car battery (type 24) for power storage. I haven't used it much; It's really bulky with the car battery. The supplies are rated at about 500W (and they can power a lot) and work great.
When I was building one of them I accidentally hooked the battery up backwards and a few transistors popped. The part that was damaged was the charger and line in; i turned it into an inverter for my car (with much success), and have powered TVs off of it and such.
One time I dropped a fan across the car battery and the 24-gauge wire burnt up like crazy. The advice I'd have is to seal up the battery as soon as possible so stupid crap like that doesn't happen. Oh, also use the proper gauge (a/l 10 gauge, 12 if you're not going to put much load on it), if you put 24 gauge on it it will burn, oh yes...
Re:He was my disscussion TA for honors physics
on
Comic Book Physics
·
· Score: 1
holy crap you must have been in my class. Too bad you're an anonymous coward...
I work at Honeywell, Inc. at a Web-Dev type internship. It's pretty good -- the work is manageable and the atmosphere is worthwhile. The pay is pretty good, too.
I *almost* sprang for a Dot-Com a while back, but thankfully I didn't (they 'hired' me, but the employment agreement was terrible) -- I was going to get paid in worthless, worthless stock. I passed it up and stayed at places that pay me actual money.
So, back to the story at hand -- there are internships out there but it helps to know the right people and make a name for yourself first.
I work for a Fourtune 500 company (intern) working with a software & hardware development model. The model that we use constantly goes through changes and is very sucessful in terms of delivering software and hardware on time, and defect free. I have no clue about budget, but I'd guess that it is not over budget either. Working here has given me a favorable view of software engineering. Every process is laid out and explained, and there are many tools at our disposal, including a requirements tool, a UML tool, code generation tools, code testing tools, etc.
Now for the rant. I also go to a large University 20 miles down the road, and I am taking their software engineering course (<- yay for relevance). Among CS majors there is a bad reputation for the SE class, that it is never organized well and leaves students with a bad taste for SE. In my class, we are currently in the 'Design' phase for our semester-long project, we will be done tomorrow. The Implementation phase is a week long. That's right, a week. We spent months on the requirement and ooa phases, but they are still unclear (because the document that calls for them is unclear), and now we have a week to iron everything out. This class leaves me with an unfavorable view of software engineering.
I think that more colleges should teach software engineering not as just one class but as an approach along with code classes. It makes sense when teaching people how to code that one should also teach them the likely environment in which they will code, otherwise students will get the impression that they can opt-out of having to deal with software engineering.
Has software engineering become better? Probably. Would you be able to tell when taking the class that I am? Hell no.
Overall, I don't think that given machine running OS X is slow, but on some things it seems to be absolutely DEAD.
I must preface this by the computers I've used:
Mac OS X:
G4 Cube @ 400 MHz
Brand-new-iMac @ something
OS 9:
Macintosh 512k - up
Linux:
Pentium 133 and up
DOS/Win:
386DX-20 and up
by 'up', I mean all the way to the New Hotness machines.
I think that OS X has _serious_ filesystem problems, HFS+ is a little faster, but for my use, worthless. Yesterday I installed xfree86 from a tgz package (our system) on the new iMac, and it took over 10 minutes. On linux, that only takes a minute or two. Application launches like XDarwin take forever. I have been happy, though, with image rendering and web rendering, and Quartz Extreme is pretty nice, although nothing can compare to linux (icewm & 4.2.1) for response.
I have been running the CPU monitor app and it is hardly ever at 100%, so disk I/O is probably to blame.
Side note: anyone notice that fsck dies with a 'Bus Error' sometimes, and then, ironically, your installation is f*cked.
I work for a large university, and I've been working to integrate Mac OS X with flat BSD files (for both the GUI and other environments). I have some tips for anyone intent on doing the same - dave (at) math.umn.edu. Apple support (the people to complain about when you've already bought the product) didn't help me at all.
:)
Back to the business: Gordon Shukwit (who I talked to last week) is writing white papers on integration with Active Directory, and said that "[he'd] have them done soon" (<- perfect for slashback). I won't publish his e-mail address because having a slashdot story about it is already enough pressure
It's wayyyyy too long for here, so I shamelessly plug the website. I tried to keep it at least a little bit funny. As a Sys Adm, either you havve to take a proactive stance on cruft, or just let everything sit and collect.
To have a proactive stance, but concede that you cannot fix everything and reinstall thusly (better if it's automated, and where I work, is it ever) in my opinion is the best. The cruft (xcept users' crap, but that's what quota is for) is gone, and most (usually all) people don't notice when the reinstall happens. In case anyone cares, we use slack packages.
NO SHAME:
http://www.thecubic.net
The U of M's OIT (office of information tech.), outlawed kazaa and rate limited it, so you'd think they'd hate it enough not to study it... (hey, it was a big deal while I was in The Dorms)
They must have done it at HP to get around Packeteer.
This is not easy, Coward. You'd need a giant voltage regulator setup. However, if you want to build a circuit to change 12V to 5V that _doesn't_ suck, you would need to convert it to AC first because AC is the only type of current that can be transformed by coils. So, inverting the power is less complicated than scrweing with the DC.
The power supply already does the job of regulating power, why get rid of it?
When I was shopping in my local store I found dead power backup units for $5 each and fixed them up to create several UPSes. I used a car battery (type 24) for power storage. I haven't used it much; It's really bulky with the car battery. The supplies are rated at about 500W (and they can power a lot) and work great.
When I was building one of them I accidentally hooked the battery up backwards and a few transistors popped. The part that was damaged was the charger and line in; i turned it into an inverter for my car (with much success), and have powered TVs off of it and such.
One time I dropped a fan across the car battery and the 24-gauge wire burnt up like crazy. The advice I'd have is to seal up the battery as soon as possible so stupid crap like that doesn't happen. Oh, also use the proper gauge (a/l 10 gauge, 12 if you're not going to put much load on it), if you put 24 gauge on it it will burn, oh yes...
holy crap you must have been in my class. Too bad you're an anonymous coward...
Kakalios was my freshman physics (non-comic) TA.
:)
We did do the gwen stacy problem and several other comic-book problems.
Interesting guy, always gave us donuts to reward us for showing up to his 8AM class
http://www.kmfms.com... that's all I have to say.