Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
04/13/10 13:23
Read: times


 
#175021 - Really important to protect company names
Responding to: ???'s previous message
So "leading developer and manufacturer of sophisticated test and measurement equipment" is making fools of themselves by showing a total lack of competence.

That was one of the worst (quite possibly the worst!) attempt I have ever seen at trying to selectively describe their interests in a new developer.

Just as funny as when I have received mails on mailing list from senior softwared developers, heads of R&D etc of reasonably well known companies, where the person are totaly absolutely unable to program, understand the difference between asynchronous or synchronous data transfers or similar.

It really is important that a company name is not closely associated with really stupid questions, requests, claims, ... Why buy TV cards from a manufacturer who have developers who don't know the difference between logical and bit-wise logic operations?

List of 16 messages in thread
TopicAuthorDate
Do employers know what they are asking for?            01/01/70 00:00      
   Of course, they don't            01/01/70 00:00      
      often enough, they don't know what the acronyms mean            01/01/70 00:00      
         HR shouldn't try to evaluate competence            01/01/70 00:00      
            Well at my new job            01/01/70 00:00      
      I stumbled over this laughable example            01/01/70 00:00      
         Really important to protect company names            01/01/70 00:00      
   Agency != Employer            01/01/70 00:00      
      Not always the case            01/01/70 00:00      
         Better to just ask for any additional skills            01/01/70 00:00      
   what I have found is ...            01/01/70 00:00      
   non-technical MBAs in technical management positions            01/01/70 00:00      
      Maybe not ...            01/01/70 00:00      
         The other issue..            01/01/70 00:00      
         Maybe ...            01/01/70 00:00      
            Well ... I don't know the answer ...            01/01/70 00:00      

Back to Subject List