Looking for an intern to play with a Linux-powered robot fleet

[Bruce Dawson]

Amen!

On 08/10/2015 01:00 PM, Joshua Judson Rosen wrote:
> On 2015-07-31 18:04, Bill Freeman wrote:
> ...

> While I'm often amazed that candidates for engineering jobs will show 
> up with _no portfolio_ (especially when we're talking about software 
> jobs: mechanical engineers, for example, may have a legitimate case 
> that it's hard to get personal access to the tools they'd need to 
> build a personal portfolio; but the tools required to develop 
> software?); I'm even more amazed that people on the other side of the 
> interview-process often have no idea what to do when a candidate does 
> have a portfolio of work available for review.
>> Before that, unless you're in a field where you can publish while doing
>> graduate work (it's own form of internship), you have to take low paying,
>> crummy jobs.  In some fields they're called interships.
>> It's the non-paying ones that are real scams.
> That was one of the things that soured me on college: not only was the experience
> non-paying, they were actually _charging me_; and the `experience' part of the
> experience wasn't all that great, either. And I had to buy my own books.
> And I had to buy my own equipment. And the amount of _time_ that it seemed
> to require if I actually wanted to be good at `being a student' was crazy.
>
> ...
>
> (I retrospect, the last time I was talking to a recruiter
>   who said I'd have to move to CA even if I was going to  end up
>   in the company's Boston office, I guess I should tried proposing:
>   "how about I just stay in NH, I do CA software work on the CA schedule,
>   and you get to pay me like I work in MA?").
And just to show you how ego-centric the field was/is, most recruiters 
will actually ding you for "taking that attitude"!

--Bruce