Earlier quoted context omitted.
Bad engineers are only effective when given tasks that are interesting to them. Good engineers are those who are equally effective when given tasks that aren't so exciting. If you're at the intern level and you're already picking out which tasks are worthy of you and which tasks are beneath you, you may want to think about a different line of work.
While not disagreeing entirely with the core of your argument, an internship should be about learning rather than handing off the work no one else wants to touch. Is is unreasonable to expect, in a position which is reasonably considered a part of your education, that mentorship, controlled exposure to production systems, and legitimate work will be provided? An internship is not some magical excuse to hire someone l…
GDB tricks
31–35 of 35 posts
Re: GDB tricks
#32We apologize for any inconvenience this may have caused."
sounds like a perfect time to whip out that debugger Oracle, or upgrade to faster DB engine?
Re: GDB tricks
#33Earlier quoted context omitted.
Bad engineers are only effective when given tasks that are interesting to them. Good engineers are those who are equally effective when given tasks that aren't so exciting. If you're at the intern level and you're already picking out which tasks are worthy of you and which tasks are beneath you, you may want to think about a different line of work.
While not disagreeing entirely with the core of your argument, an internship should be about learning rather than handing off the work no one else wants to touch. Is is unreasonable to expect, in a position which is reasonably considered a part of your education, that mentorship, controlled exposure to production systems, and legitimate work will be provided? An internship is not some magical excuse to hire someone l…
I certainly was given jobs that were considered semi-important but that the full-time staff had more important things to do.(They aren't going to pay an intern to do useless work) I still learned a lot, even when I wasn't coding because I was required to learn good practice.
Re: GDB tricks
#34Earlier quoted context omitted.
I found constructing small problems and solving them with GDB when not under pressure greatly expanded my working knowledge. Trying to learn GDB while attempting to solve a time critical production bug is not possible for me.
Have you got any of those problems written down or any pointers for creating them? That sounds like fantastic material for a tutorial.
Re: GDB tricks
#35Earlier quoted context omitted.
Bad engineers are only effective when given tasks that are interesting to them. Good engineers are those who are equally effective when given tasks that aren't so exciting. If you're at the intern level and you're already picking out which tasks are worthy of you and which tasks are beneath you, you may want to think about a different line of work.
While not disagreeing entirely with the core of your argument, an internship should be about learning rather than handing off the work no one else wants to touch. Is is unreasonable to expect, in a position which is reasonably considered a part of your education, that mentorship, controlled exposure to production systems, and legitimate work will be provided? An internship is not some magical excuse to hire someone l…
However, somebody had to migrate the blog, might as well've been me.