7 Replies - 646 Views - Last Post: 24 April 2013 - 02:29 PM

#1 Michael26  Icon User is offline

  • Radar love
  • member icon

Reputation: 332
  • View blog
  • Posts: 1,419
  • Joined: 08-April 09

10 Pieces of Really Bad Advice (for Computer Scientists)

Posted 22 April 2013 - 12:41 PM

If i could put this into my signature i would :bigsmile:

"Don't worry about the complexity of the algorithm we will never have enough data for it to make too much difference."
"It does not need to be secure, who would be interested in hacking it?"
"It does not matter if you don't understand it, it works OK."
"It is just one awkward user complaining."
"Do not bother about updating the documentation, nobody will read it."
"You can tart up the user interface post-release."
"This is an ideal problem for [insert name of obscure programming language]."
"It would be easier to write it ourselves rather than work out what they have done."
"We could just change the standard protocol slightly."
"Of course he can program, he has a Linux t-shirt."
Honorable Mention: "Leave the back-up until tomorrow."

Is This A Good Question/Topic? 2
  • +

Replies To: 10 Pieces of Really Bad Advice (for Computer Scientists)

#2 WolfCoder  Icon User is offline

  • Isn't a volcano just an angry hill?
  • member icon


Reputation: 781
  • View blog
  • Posts: 7,604
  • Joined: 05-May 05

Re: 10 Pieces of Really Bad Advice (for Computer Scientists)

Posted 22 April 2013 - 01:59 PM

Quote

"It would be easier to write it ourselves rather than work out what they have done."


This one isn't always bad advice, I write my own version of things if the existing libraries are so hard to understand or terrible enough that it is indeed actually faster. The exception to this is anything dealing with security- never write your own security libraries (you would have to do extensive security testing which takes years for something to be somewhat secure).

Examples of things I don't write myself include ZLIB, ODE, SDL, etc.


But then again some of the software engineers out there make a living off fixing and cleaning broken code because someone wanted to edit an existing thing for a new problem, so by all means, borrow libraries and source code from like, everywhere.

This post has been edited by WolfCoder: 22 April 2013 - 02:02 PM

Was This Post Helpful? 0
  • +
  • -

#3 Michael26  Icon User is offline

  • Radar love
  • member icon

Reputation: 332
  • View blog
  • Posts: 1,419
  • Joined: 08-April 09

Re: 10 Pieces of Really Bad Advice (for Computer Scientists)

Posted 22 April 2013 - 02:05 PM

Quote

"Do not bother about updating the documentation, nobody will read it."

this one irks me to much if i have to deal with anything older than 6 months.
Was This Post Helpful? 0
  • +
  • -

#4 Cheribasa  Icon User is offline

  • D.I.C Head

Reputation: -2
  • View blog
  • Posts: 212
  • Joined: 11-December 12

Re: 10 Pieces of Really Bad Advice (for Computer Scientists)

Posted 23 April 2013 - 05:10 AM

View PostMichael26, on 22 April 2013 - 12:41 PM, said:

"Don't worry about the complexity of the algorithm we will never have enough data for it to make too much difference."


This one is like, the story of my life.
Was This Post Helpful? 0
  • +
  • -

#5 AdamSpeight2008  Icon User is offline

  • MrCupOfT
  • member icon


Reputation: 2216
  • View blog
  • Posts: 9,352
  • Joined: 29-May 08

Re: 10 Pieces of Really Bad Advice (for Computer Scientists)

Posted 23 April 2013 - 05:17 AM

Quote

Don't bother with commenting your code, nobody will read them.


Quote

Repeat Google, Copy, Paste and Delete Until you get desired output.


Quote

I don't know what we want but it has look like this.


Quote

I'll post my 3 line program on a forum, rather run it to find out for myself.

Was This Post Helpful? 1
  • +
  • -

#6 Michael26  Icon User is offline

  • Radar love
  • member icon

Reputation: 332
  • View blog
  • Posts: 1,419
  • Joined: 08-April 09

Re: 10 Pieces of Really Bad Advice (for Computer Scientists)

Posted 23 April 2013 - 05:20 AM

Nice one Adam :)/>
it reflects some of the posts here on DIC

This post has been edited by Michael26: 23 April 2013 - 05:21 AM

Was This Post Helpful? 0
  • +
  • -

#7 WolfCoder  Icon User is offline

  • Isn't a volcano just an angry hill?
  • member icon


Reputation: 781
  • View blog
  • Posts: 7,604
  • Joined: 05-May 05

Re: 10 Pieces of Really Bad Advice (for Computer Scientists)

Posted 24 April 2013 - 06:00 AM

Quote

Perpetual Beta

Was This Post Helpful? 0
  • +
  • -

#8 AdamSpeight2008  Icon User is offline

  • MrCupOfT
  • member icon


Reputation: 2216
  • View blog
  • Posts: 9,352
  • Joined: 29-May 08

Re: 10 Pieces of Really Bad Advice (for Computer Scientists)

Posted 24 April 2013 - 02:29 PM

Quote

Show the client a work in progress, they'll understand it's not finished.

Was This Post Helpful? 0
  • +
  • -

Page 1 of 1