That's how I got started. My dad left his Borland Delphi III disk lying on his desk with a copy of "Teach yourself Delphi III in 28 days", so I took it and installed it on my computer. Eventually I got bored just drawing pretty windows, so I ask my dad how to "do stuff", and he introduced me to pointers, linked lists, stacks, and all sorts of wonderful data structures. The rest, as they say, is history.
We do the same thing: functions and varibles that are local to a specfic file (i.e. helper functuions) are declared "static", and are not required (or allowed) to have the module prefix.
I write code for embedded systems where there are many hundreds of C files that all need to compile together to form a single executable (everything shares a single address space). Since there are alot of modules working together, the most useful thing is the usage of prefixes for modules components. For example, all of the database public methods, defines, etc. are prefixed with a DB_ and all the private ones are prefixed with a db_. Granted, it is up to the programmer to enforce these restrictions, but it is nice to be able to tell exactly where a function comes from when reading through some else's code.
On the strange side is the omission of vowels on functions and varible names to save text space (it's not required, but should be consistent for similarily names objects). It sounds weird, but is still quite readable.
My Software Engineering Professor always told us that "Extreme Programming" was having one programmer doing the actual programming, and another looking over their shoulder correcting their mistakes as a they go.
Whether that is more efficent than having both work on seperate parts and fixing their own bugs, I'm not sure, but it always helped the teams I've worked on produce good code.
Although, I'm not sure that that lines up with the definition of "Extreme Programming" that everyone else has:)
This reminds me of the Robo-Dozers on the old Outpost http://www.outpostuniverse.net/ computer games. Good games, they taught me a lot about resource managment for Real Time Strategy.
I work in Academia tech support, and I've come to find that a most of the time, it is the hardware, not the software that requires the legacy support. For example, we have several gas spectrograph (or something like that) in our building. The hardware works just as well as it did when they bought it, but the manufacturer hasn't bothered to keep updating the software to run on anything newer than Windows NT 4. Thus, we are required to keep these old machines around and support them since the department doesn't want to drop however many tens of thousands of dollars on new equipment when the old stuff works just fine (which I comletely understand). Also, in cases like this a VM would likely be far more hassle than it is worth, due to propritary interface cards used to connect the computer to the spectrograph.
Not necessarly to say that this problem is unique to Windows or even non open-source software, it just tends to be more pronounced and occur sooner.
The point is, you can't always just port the application to the newest version of the OS and continue with life.
I don't like IE, but he almost have to use it in at the place I work.
why?
Because it automatically gets patched by the M$ patch server, where as we would have to manually go around and patch Firefox. Theres only two of us, and it would take a while to update firefox on 150+ systems. (the users are locked out of doing most things, so that can't do it themselves, not that i would really trust them to do anyway)
Re:If/When Valve goes out of business...
on
Review: Half-Life 2
·
· Score: 1
I seriously doubt that they would spontaneously decide to disbanded the cult following that has made Half-Life 1 & 2 so popular. These people are committed to their fans.
Mayeb a bit off topic, but maybe we should ask a little help from the Russians. They seem to have been using charged gas engines for quite a while.
Maybe a hall effect thruster? They use more power, but seem to generate more thrust as well.
I for one, am glad that there are plenty of lusers out there who open E-mail virus.
It gives me a job that I get paid for
More importantly, as long as the lusers keep getting the viruses, the people that write them will feel no need to make them more advanced, and thus the people that do know what they are doing are less likely to be suprised by an unknow virus. Make sense?
Slashdot Mirror
The HP Oscilloscopes used in my EE Circuits lab had a hidden Tetris game. It was a great way to have the Lab TA give you a funny look.
http://www.eeggs.com/items/28801.html
That's how I got started. My dad left his Borland Delphi III disk lying on his desk with a copy of "Teach yourself Delphi III in 28 days", so I took it and installed it on my computer. Eventually I got bored just drawing pretty windows, so I ask my dad how to "do stuff", and he introduced me to pointers, linked lists, stacks, and all sorts of wonderful data structures. The rest, as they say, is history.
We're allowed to use goto to break from a double loop instead of using a boolean flag.
...
...
i.e.
for(i = 0; i < N; i++)
{
for(j = 0; j < M; j++)
{
if( foo )
{
goto end;
}
}
}
end:
...
We do the same thing: functions and varibles that are local to a specfic file (i.e. helper functuions) are declared "static", and are not required (or allowed) to have the module prefix.
On the strange side is the omission of vowels on functions and varible names to save text space (it's not required, but should be consistent for similarily names objects). It sounds weird, but is still quite readable.
This was cover a while ago, except they were testing in Huston. Cool to see more footage though.
My Software Engineering Professor always told us that "Extreme Programming" was having one programmer doing the actual programming, and another looking over their shoulder correcting their mistakes as a they go. Whether that is more efficent than having both work on seperate parts and fixing their own bugs, I'm not sure, but it always helped the teams I've worked on produce good code. Although, I'm not sure that that lines up with the definition of "Extreme Programming" that everyone else has :)
This reminds me of the Robo-Dozers on the old Outpost http://www.outpostuniverse.net/ computer games. Good games, they taught me a lot about resource managment for Real Time Strategy.
I work in Academia tech support, and I've come to find that a most of the time, it is the hardware, not the software that requires the legacy support. For example, we have several gas spectrograph (or something like that) in our building. The hardware works just as well as it did when they bought it, but the manufacturer hasn't bothered to keep updating the software to run on anything newer than Windows NT 4. Thus, we are required to keep these old machines around and support them since the department doesn't want to drop however many tens of thousands of dollars on new equipment when the old stuff works just fine (which I comletely understand). Also, in cases like this a VM would likely be far more hassle than it is worth, due to propritary interface cards used to connect the computer to the spectrograph. Not necessarly to say that this problem is unique to Windows or even non open-source software, it just tends to be more pronounced and occur sooner. The point is, you can't always just port the application to the newest version of the OS and continue with life.
The 128 GB Drive in the XPS M1730 is a 2x64 GB Raid, so it is not really more advanced technology.
I don't like IE, but he almost have to use it in at the place I work.
why?
Because it automatically gets patched by the M$ patch server, where as we would have to manually go around and patch Firefox. Theres only two of us, and it would take a while to update firefox on 150+ systems. (the users are locked out of doing most things, so that can't do it themselves, not that i would really trust them to do anyway)
I seriously doubt that they would spontaneously decide to disbanded the cult following that has made Half-Life 1 & 2 so popular. These people are committed to their fans.
Mayeb a bit off topic, but maybe we should ask a little help from the Russians. They seem to have been using charged gas engines for quite a while. Maybe a hall effect thruster? They use more power, but seem to generate more thrust as well.
- It gives me a job that I get paid for
- More importantly, as long as the lusers keep getting the viruses, the people that write them will feel no need to make them more advanced, and thus the people that do know what they are doing are less likely to be suprised by an unknow virus. Make sense?
maybe kinda selfish... but it works.