Forgot your password?

typodupeerror

Comment: Re:Computer Scientist Programmer Software Engineer (Score 1) 446

by pnewhook (#38914193) Attached to: Ask Slashdot: Transitioning From 'Hacker' To 'Engineer'?
Completely agree. The first run through is to get it working with simple, very easy to understand code. Absolutely nothing fancy. Once it works, THEN you check the performance and optimize only those modules that need it. Simple code is far more likely to be bug free than come convoluted pile of packed code that no one but the writer understands. For some reason coders take pride in the fact that they can write code that works but no one else can read (even though the simple version would have taken an hour and they took a week). Baffling.

Comment: Re:Computer Scientist Programmer Software Engineer (Score 1) 446

by pnewhook (#38914153) Attached to: Ask Slashdot: Transitioning From 'Hacker' To 'Engineer'?
No I'm not talking about sloppy bad code with bugs that allow exploits. I'm talking functioning *working* code that's been *tested* to be correct, but don't happen to match the aesthetics standards, or 'wow that's a cool way of doing it' standard of a developer that thinks hes top shit. Problems have to be fixed, but changing code to make it more elegant or efficient when there is no performance reason to, or making it run in 3 lines of convoluted code instead of 10 or 20 of very clear easy to understand code is just moronic.

Comment: Re:Computer Scientist Programmer Software Engineer (Score 1) 446

by pnewhook (#38901911) Attached to: Ask Slashdot: Transitioning From 'Hacker' To 'Engineer'?
The problem comes down to you get a developer who believes the beauty of the code is the only thing worth looking at. He then gets assigned to add some features to existing code, looks at *other* parts of the code that don't need to be changed, are completed and are fully tested, reacts with horror saying 'what idiot wrote this piece of crap?!?' and then proceeds to spend a month rewriting it, breaking multiple other things in the process cause he doesn't understand the code. THATS the problem and it happens ALL the time.

Comment: Re:Computer Scientist Programmer Software Engineer (Score 1) 446

by pnewhook (#38893049) Attached to: Ask Slashdot: Transitioning From 'Hacker' To 'Engineer'?

A computer scientist who's also a programmer not only does the same thing but with the added goals in mind of making his code the most efficient running code possible on the target platform while understanding why a particular collection of code is the most efficient it can be upon the target platform.

Which is EXACTLY why software development programs tend to be massively over budget and often don't work properly at the end of the day. Like who gives a rats ass if the matrix multiply is the most efficient it can possibly be if the overall system still meets the requirements with an inefficient matrix multiply?? You people spend so much time optimizing the academic worthless shit that there is no time left to actually finish the project, and then you blame management for unrealistic deadlines. Just get it working, make sure the code is clean and easy to understand, and move on to the next task!

There is nothing more silly than a silly laugh. -- Gaius Valerius Catullus

Working...