roflmao! Thats true, I think MySQL is a glorified version of MS Access with a TCP Server on the front... PostgreSQL on the other hand is the open-source oracle...
Agreed, although in a lot of ways, I have always been lucky enough to have had a grace period to prototype things myself:) so my specs are usually accurate!:p
Right as a software developer, I have both written software with specifications (that I have written or been handed) and I have written software blindly with no real path...
Quite frankly I think Linus, is not on the ball there, as both an engineer and architect, I would say that using a spec can result in very well thought out programs.
A specification does not have to reflect on reality at all! It is means to an end to explain how a program *should* work! For example, if I wanted to write an accounting package and knew nothing about accounting, I would fail miserably if I were to write it with no specifications to give me some sort of direction or understanding... The same goes for financial trading systems, if I knew nothing about it, I couldn't write it!
You need some level of documentation saying, the functionality of the program has to work in this way, i.e. we want 1 + 1 to eqaul 2, it doesn't matter how you write it in the end, as long as it still equals 2. That gives a software program some sort of direction...
A spec is only theory to give you direction... That what makes an architect different from an engineer, the architect says, "I want it to do this" its then up to the engineer (which linux is!) to implement it in a real world manner!
Because we are "of higher" intelegence than other animals, it would probably be a lot easier for us to learn how to use our eyes, with the propper training, i.e. focusing on certain objects, etc and learning how to interact with them, it shouldn't be a problem. Don't forget the boy is one year old, he won't have fully developed vision anyway, so in a sense he will be able to see perfectly well (for someone with vision only in one eye), although he will lack something we take for granted, peripheral vision...
The only reason I can think of why they fucked manned space flight was during the cold war. They developed primitive rocketing techs and they never really investigated any other way of space travel.
I could just image.... Viewing the universe billions of years ago... It was a stange place, where beings like GOD knew that we would be looking, so he mooned us!
Waddya mean beer, if you drink too much of it, you will pass out! Forget the SUN screen in the UK we have no sun at the moment... BUT! What we really need is caffine... Lots and Lots and Lots of caffine... mmmmmmmmmmmmmmmmmmmmmmmmmmmmm caffine!!!
I think I will take a week off from the day I get a copy my week will be: doom III, caffine, doom III, caffine... oh and maybe a couple hours sleep inbetween caffine and doom III every 20 hours or so...:P w00t!!!
You make a good point. I mean what's the point of introducing something that doesn't work? Quite frankly I find it a bit stupid. I can understand finger prints and DNA, but eye scanning that doesn't work? GOD!
I have always found that keeping your code as simple as possible (C/C++) its a lot more stable and a hell of a lot faster! Plus abstraction (mention somewhere around here) is your friend. For example, I wrote a database class (C++) for a Point of Sale application. I kept it very simple by creating a simple front end to any kind of database, the abstraction in it is great as all I have to do is add an extra case to switch and then add the corresponding enum and function! But implementing it is a dream!
Also the best piece of advice I can give to a progammer is stick to using integers, enums are great!
Be carefull with new (if you use C++) or find an API that can manage memory allocation for you like QT or GTKMM -> (my favourite!!).
Another performance hint, stay away from too many embeded loop, first of all it makes you code ugly second of all, if you make one mistake say hello to mister reboot because your processor usage hits the roof!
Well, I started this new job six months ago as a developer, I was stunned to see that there was nearly 0 development and two out of probably 10 developers using Version control (excluding myself of course). It has taken me this long to push though a massive whitepaper on how to write software. Software specifications are damned important! Without them you are in the shit, because if you make a cock up or near a dead line things can get really bad, really fast. Probably proves why there is so much crap software out there!
That is a very good point, I know very well that, that is the case. If you have read my other posts you would have seen that I ellaborated on my conclusions in the parent post. I expanded on what I meant to be instant: Instant being that of what we can comprehend of instant, which of course does not mean it is instant.
Slashdot Mirror
roflmao! Thats true, I think MySQL is a glorified version of MS Access with a TCP Server on the front... PostgreSQL on the other hand is the open-source oracle...
That MySQL will sell software with things missing, like ikea sells its funiture with screws missing?
Agreed, although in a lot of ways, I have always been lucky enough to have had a grace period to prototype things myself :) so my specs are usually accurate! :p
Right as a software developer, I have both written software with specifications (that I have written or been handed) and I have written software blindly with no real path...
Quite frankly I think Linus, is not on the ball there, as both an engineer and architect, I would say that using a spec can result in very well thought out programs.
A specification does not have to reflect on reality at all! It is means to an end to explain how a program *should* work! For example, if I wanted to write an accounting package and knew nothing about accounting, I would fail miserably if I were to write it with no specifications to give me some sort of direction or understanding... The same goes for financial trading systems, if I knew nothing about it, I couldn't write it!
You need some level of documentation saying, the functionality of the program has to work in this way, i.e. we want 1 + 1 to eqaul 2, it doesn't matter how you write it in the end, as long as it still equals 2. That gives a software program some sort of direction...
A spec is only theory to give you direction... That what makes an architect different from an engineer, the architect says, "I want it to do this" its then up to the engineer (which linux is!) to implement it in a real world manner!
A person who does ketimine? Do we get free K with this new version of KDE?
2004: Doom 3 released 1 week later, I go broke buying an Athlon64 with a 30Inch display...
Because we are "of higher" intelegence than other animals, it would probably be a lot easier for us to learn how to use our eyes, with the propper training, i.e. focusing on certain objects, etc and learning how to interact with them, it shouldn't be a problem. Don't forget the boy is one year old, he won't have fully developed vision anyway, so in a sense he will be able to see perfectly well (for someone with vision only in one eye), although he will lack something we take for granted, peripheral vision...
and you call a large metal object being rammed into darls behind a flaw???????????
The only reason I can think of why they fucked manned space flight was during the cold war. They developed primitive rocketing techs and they never really investigated any other way of space travel.
May I ask how the parent to this is off topic? Deadrat = redhat! You are supposed to mark it troll!
Isn't that deadrat?
d00d don't give them ideas!!
Plot? But I though a plot was just some cheezy music and kinky toys....
I could just image.... Viewing the universe billions of years ago... It was a stange place, where beings like GOD knew that we would be looking, so he mooned us!
Dude I was trying to be facetious! Ah well... Been working to hard I guess
Thats not bad, its nice to see that ordinary people are getting closer to achieving space flight :P
caffiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiine! :P
Very true... I have been drinking too much caffine, I can already sense my heart not liking me anymore... Been a very busy programmer!
Waddya mean beer, if you drink too much of it, you will pass out! Forget the SUN screen in the UK we have no sun at the moment... BUT! What we really need is caffine... Lots and Lots and Lots of caffine... mmmmmmmmmmmmmmmmmmmmmmmmmmmmm caffine!!! I think I will take a week off from the day I get a copy my week will be: doom III, caffine, doom III, caffine... oh and maybe a couple hours sleep inbetween caffine and doom III every 20 hours or so... :P w00t!!!
You make a good point. I mean what's the point of introducing something that doesn't work? Quite frankly I find it a bit stupid. I can understand finger prints and DNA, but eye scanning that doesn't work? GOD!
OK so its fast! But the question still stands, can I use it with lynx?
eat your braaaaaaaaaaaaaaaaaaaaaaaaaane!!!!
I have always found that keeping your code as simple as possible (C/C++) its a lot more stable and a hell of a lot faster! Plus abstraction (mention somewhere around here) is your friend. For example, I wrote a database class (C++) for a Point of Sale application. I kept it very simple by creating a simple front end to any kind of database, the abstraction in it is great as all I have to do is add an extra case to switch and then add the corresponding enum and function! But implementing it is a dream! Also the best piece of advice I can give to a progammer is stick to using integers, enums are great! Be carefull with new (if you use C++) or find an API that can manage memory allocation for you like QT or GTKMM -> (my favourite!!). Another performance hint, stay away from too many embeded loop, first of all it makes you code ugly second of all, if you make one mistake say hello to mister reboot because your processor usage hits the roof!
And you actually believe an article written by infoworld????? I mean come on dude!
Well, I started this new job six months ago as a developer, I was stunned to see that there was nearly 0 development and two out of probably 10 developers using Version control (excluding myself of course). It has taken me this long to push though a massive whitepaper on how to write software. Software specifications are damned important! Without them you are in the shit, because if you make a cock up or near a dead line things can get really bad, really fast. Probably proves why there is so much crap software out there!
That is a very good point, I know very well that, that is the case. If you have read my other posts you would have seen that I ellaborated on my conclusions in the parent post. I expanded on what I meant to be instant: Instant being that of what we can comprehend of instant, which of course does not mean it is instant.