Peter Moyle


Biography has not been added


's contributions
    • While I have worked with many that did have install scripts, many of those scripts would crash out of the box (many times due to permissions - that sudo wouldn't fix) that required you to have to deal with anal IT dept's or debug/modify the scripts or both. But, on the other hand windows is just such an abomination that it's the lesser of 2 evils.

    • You can't run Linux on a 16K Flash/16K SRAM uC. Period. End of discussion. That said you can't run an RTOS on a 4K Flash/4K SRAM uC (well maybe a small bare bones one, but not FREE RTOS). So There is also a niche still for the good old super loop. But just like the discussions of the 8051 those opportunities are becoming much more niche to the extremely cost sensitive application. To make such a broad statement is like carrying a a single wrench to every job site whether it be a 1/2" pipe to turn or a 3". No similarities in those 2 jobs.

    • Have to 2nd the motion for Greg504. But I think if he's only a newly wed and getting that kind of flak, then it's time to book, sooner rather than later. If your wife is dictating constraints that will have a serious impact on your career path (and money, especially in these times, is one of the most serious), then that will lead you to a job where (if you're lucky enough to find it) the salary was inflated and you probably gain no hard skills. When that happens, watch out. If you are laid off, your chances of finding another job are virtually nil. For 2 reasons: A) when they look at your salary history, they will conclude that you couldn't possibly be happy there, no how you try to convince them otherwise. B)You will have no hard skills to sell, so all you have at that point is what you graduated with a GPA and a degree designator, and that worth becomes water down quickly with passage of time. So, bottom line, go where there is big demand and you can get a lot of hard skills. And don't let salary be a dictator. Don't stay at one company for more than 3 yr. As for job sector, Verification is a great place to be right now.

    • "(there's a reason the aerospace industry uses Ada)"..... Yes, and tell me what that is??? never mind I'll tell you what the Colonel told me: "Officially we use ADA, unofficially we do everything in C" the reason they use ADA is because it was invented by gov't bureaucrats and so they must, but won't any time they can get away with it or justify it

    • A bunch of years ago, I was talking to a defense contractor about doing some development for them. Then, I thought and said, "Oh, but you you use Ada, don't you". And they said, "Officially we use Ada, unofficially everything we do is C". I said, "Oh, ok, then we're good."

    • "The Ada language was designed to restrict not so good programmers so they cannot make the same mess if they were using C/C++." Right on!! Garbage in, garbage out. It reminds me of laywers trying to regulate stupidity.

    • There is some truth to that but there are the enablers and the politically incorrect.

    • I am also a hardware engineer. The problem that I find is that software engineers are mentally lazy and don't take the time to thoroughly plan the relationships between functions, variables and loops. A tool to do that isn't going to do much to change that. Garbage in, garbage out. I got into software, having to clean up messes made by software guru's that only had excuses for. I did then return to school however to take a bunch of classes in CS. For a good while I actually got stuck in software after having the title of software engineer for about 9 yrs. After that, none thought I could design hardware any more. Thankfully, I did manage to escape it and I'm in a job where I do both, although I'm doing a lot more FW than I'd like to because I have been rescuing 3 large projects done a genius no longer here, a left a huge overly complicated mess. I find HW people are generally much more mentally disciplined than SW people because HW blows up when your careless. BTW, my programming languages are: 1) Assembly 2) C 3) Verilog 4) Perl I can also work in a bunch of others such as C# or C++ or VHDL but prefer not to.