I liked it ... I think. But I completely understand your criticism.
I do see his point "you’re not here to write code; you’re here to ship products.”
I think too many developers think it's the company's obligation to pay them to write "elegant" and sophisticated code when the company needs you to write robust and functional code and get it out the door, or in my case, out on the floor to test shipping products. I think his point is that too many developers try to make things complicated (for job security? bragging rights?) that you eventually have something so complicated that unforeseen bugs creep into the code weeks or months down the road. I've inherited such projects, and probably wrote one or two myself.
IMO, if you want to methodically improve your coding skills you need to do that on your own time - not on the company's dime. Don't get me wrong. I learn something new every day on the job, but if I wanted to tackle a project using something totally new like OO or scripting techniques I would do that on my own time. And I would only put it into a work project when I was absolutely sure I knew what I was doing.
My $0.02
I think that distinction now belongs to Detroit. But I don't think it has anything to do with the smell. I would love to see the G20 bring their little circus here.
Michigan is wooing the movie industry here with tax breaks and incentives. Just a few weeks ago a couple of film crewmen were mugged outside one of the studios.
Naming conventions are up to you and your team - and as you will see here you will get just as many suggestions as folks who respond. Good luck with that.
One thing I have learned, however, and it could be useful for you: don't keep a seperate folder for typedefs and custom controls. Put these in the code directories. It will make things a lot easier if you ever want to reuse your code somewhere else.
Dude! My first real job after the military was working for a medical imaging company. Optics, imaging, image processing, lasers, etc. I managed to work my way into engineering very quickly. I loved that line of work. Some of the best years of my life, career-wise. LV wasn't quite around then and I didn't get into LV until a few years later. But your are definitely in the right spot now.
What kind of work are you in? Medical? Space imaging? Machine?
Welcome to LAVA. I'm sure you will find many here who can be very helpful.
Colour, color, favour, favor. I like the good, old fashioned Noah Webster American English. The Queen's English wastes too many good letters that could be better used somewhere else.
I once knew an attorney, last name "Arp". We were not exatly on the same side and in my correspondence to him I would feel some smug satisfaction when my spellchecker would hit his name and list:
...
Carp
Rap
Crap
...
That is a great question, and probably the most difficult I have had to answer on numerous occasions in my career.
I'm no expert but I have gotten a lot better coming up with reasonable estimates on how long it will take me to write some code. And I'm not intimidated any more when my boss(es) and planners and account managers in the meeting room let out a collective "GASP!" when I say "oh, about 3 months."
What always ends up biting me in the @ss is something hardware related.
Every. Single. Time.
Whether it's drivers or compatibility or mechanical, or availability or cleaning up someone else's mess it's always hardware related. Trying to fit a square pin into a round hole accounts for 90% of my wasted time.
Indeed. I find that term as offensive as some are by the "F" word.
And he didn't look at my avatar ... I have a cat with frickin' laser beams coming out of her eyeballs ...
I understand your frustration. I felt it, too when I was preparing for my CLAD exam. But I kept studying the material before I took the test. And because of that I see no ambiguity at all in either question. To me the answers to both questions are no-brainers. (D and 120,30). But I KNOW THE MATERIAL. I know how arrays and coercion works. I knew the material and I passed my CLAD years ago. That was my point. It's not so much the "right" answer as it is knowing the answer NI wants to here. And that answer is not necessarily "wrong".