Unfortunately, one of the previous pieces of software in this area followed the poster's "self documenting code" style (very nice, clean, well written code with no comments), and even I find it difficult to piece together what's going on in places --- not because all of the code is crypto-specific, but because the author has thrown so much effort into writing "clean, pretty" code that it's actually hard to know where the crucial pieces are. I can't quite explain why I find this so irritating, but perhaps some of you will know what I mean.
I can kind of understand this, often in the quest to make things more understandable things are refactered into methods/functions that arent modular operations in themselves which can lead to more confusion since they masquerade as pieces of modularly reusable code when they in fact rely on assumptions which happen to be satisfied by their caller.
Its also worth noting that you do get a performance and memory usage penalty for pushing additional frames onto the stack. In certain cases that can be a factor. (As an aside why is it in Uni that recursive code is held in such high regard as being elegant whereas in day to day like its almost always a bad idea. I made that mistake a few times early on in my professional life).
I also find the best thing to do is treat them like a corporation so in order to get support they need to have first signed off on the Enterprise wide computer usage and security guidelines and then logon to the issue tracking database and create a problem along with a risk assesment and business impact. If they are unable to access the issue tracking database they need to get one of their coworkers to create the ticket on their behalf. The requests are then sorted according to impact where those causing more than $10,000 revenue loss are given an SLA of 5 hours. Other problems are assigned response times based on impact to the user and support team workload.
Post resolution if the problem was caused by failure to adhere to the Enterprise wide computer usage and security guidelines then appropriate disciplinary action is instigated with their direct report-to.
In Total Anhilation and to a lesser extent Supreme COmmander rushing doesnt really work. Best tactic is economic superiority (and thus winning through attrition) through skirmishing.
So look for work for a software company then? Some people have a narrow view of "IT". There are other roles than general system support you know. Some of us work in profit centres.
[quote]
I still the the acronym "MMO" sucks; shouldn't it be either "MMOG" or "MMORPG"? MMO would just stand for "Massively Multiplayer Online", which is somewhat lacking in the noun department.
[/quote]
Maybe player is the noun?
Wubi is bookmarked for checking out when i get home. While I doubt im going to ditch windows for my stuff as Im quite entrenched it might well be a cool thing to have a play with.
Once I can take my VSTs with me then it becomes a sersious contender.
Yeah but its not like if I recompile my binary then that 6/8 middle section is going to flow into the verse better is it?
The mixdown step is more to do with the traditional process where mastering would be done by a separate engineer so its a workflow embedded in a lot of musicians subconscious already but theres nothing to stop you strapping your master fx over your master bus and working that way.
With a modern DAW I dont see why you would ever want to route audio to another application (MIDI is another story mostly due to one particular app [reason]) but see rewire) since all your audio apps will be running inside your DAW via VST or rtas anyway.
As for value for money. These days Reaper (unlimited free trial, 50 bucks license) is available on windows and Mac and is pretty much as fully featured as cubase, its missing some audio editing facilities but you can hook in audactiy as a helper app so going linux doesnt save you any money at all, except the OS license I suppose but quite frankly a windows OEM license is what a hundred bucks or so so by the time Ive wasted 2 or 3 hours trying to setup linux the windows license has paid for itself. Hardware of course you are fairly limited on what you can even use on linux so I doubt you get the most band for buck when your buying your interface either.
Basically if you dig linux and like toying around with this stuff I can see the attraction but as usual for people who arent interested in the technology aspect the workflow isnt optimal with a far to high barrier to entry in terms of initial configuration. This is the same problem linux has in other creative spaces.
Their data is inherently low value though, and data corruption is largely unimportant. I bet you'd end up with the exact opposite view if you looked at banks and financial institutions.
I dont think you've had much experience in the enterprise world. Ive only used toy SAP systems to test some interfacing but typical implementations are gignormous this is the kind of stuff that replaces departments of hundreds of people.
Right now, I can install Linux on any number of systems I have as well as systems at work, including all sorts of software, without any legal worries about licensing
Except that what alot of people are now realising is that you cant because it impairs your ability to write your own non-GPL'ed code.
Im unconvinced your any less locked in to be honest. Any non-trivial product in the OSS world is maintained by a specific team of people, usually funded by a corporate sponser. Realistically the time it takes to build the skills required to provide support makes it cost prohibitive for anyone but core developers to maintain most software. So if the core developers quite, like say because their corporate sponser quits footing the bills then your in almost exactly the same situation as with proprietary software. Possibly worse since most will be under no obligation to provide migrations paths.
What the hell do you do with yours? I have a 2yo work laptop that gets taken home every night and is absolutely fine and a 5 year old personal laptop that also gets lugged to band practice once a week (and associated exposure to beer, sweat, dropping, and risk of crushing by 4x12) and it doesnt show any signs of failure either.
I think you might be doing something wrong if you only a get a year out of yours.
Actually java datatypes are machine independant so they can be serialised and unserialised across architectures. Altering the size of the primitive types simply because your happening to be running on a different wordwidth cpu is a bad idea for portability.
Yeah, but none of those are very important. If a transaction fails when you're updating your Facebook profile, nobody gives a shit. I mean look at what happened to Slashdot when it got 24 million posts.
I would bet money that none of those companies use MySQL for their paycheck processing software.
I don't dislike MySQL, but I wouldn't consider it an "enterprise RDBMS"
And how often does MySQL participate in transactions involving multiple dbs?
I wouldn't really have said many of these are enterprise apps either, theres no messaging, app serving, transaction management. Theyre all just web apps really. I mean i'd have expected stuff like JBoss, ActiveMQ, Tomcat and such to be mentioned rather than vBulletin and OpenOffice.
Much like when to use each paradigm answer is in the focus of the degree course as a whole. For an AI course functional programming cant be beat since it abstracts away depth first search into the language and many have higher order logic constructs built in. For software engineering OO is king as it facilitates reuse. For systems and embedding programming focus procedural is the way forward.
Further I fail to see how the point and click method of configuration is better than editing a text file than can be searched, backed up and version controlled.
Because it requires documentation and a user who can be bothered reading the documentaiton and understands the documentation. Further text is a free form interface. For example in/etc/spiffyapp/pathSetup I *could* write "SPIFFYPATH=/path/to/spiffyapp" but theres nothing to stop me writing "hello im a happy cloud, giblledideedeee" and to someone who isnt pretty technically literate theres no reason why one should instantly consider one more intuitive than the other. Whereas in a gui they would have a gui file chooser widget that only allows them to select paths.
The answer of course is to have both with the gui widgit a view onto the internal txt file / registry settings / xml docs / whatever.
Slashdot Mirror
He meant 2100 in hex. :)
I can kind of understand this, often in the quest to make things more understandable things are refactered into methods/functions that arent modular operations in themselves which can lead to more confusion since they masquerade as pieces of modularly reusable code when they in fact rely on assumptions which happen to be satisfied by their caller.
Its also worth noting that you do get a performance and memory usage penalty for pushing additional frames onto the stack. In certain cases that can be a factor. (As an aside why is it in Uni that recursive code is held in such high regard as being elegant whereas in day to day like its almost always a bad idea. I made that mistake a few times early on in my professional life).
I also find the best thing to do is treat them like a corporation so in order to get support they need to have first signed off on the Enterprise wide computer usage and security guidelines and then logon to the issue tracking database and create a problem along with a risk assesment and business impact. If they are unable to access the issue tracking database they need to get one of their coworkers to create the ticket on their behalf. The requests are then sorted according to impact where those causing more than $10,000 revenue loss are given an SLA of 5 hours. Other problems are assigned response times based on impact to the user and support team workload.
Post resolution if the problem was caused by failure to adhere to the Enterprise wide computer usage and security guidelines then appropriate disciplinary action is instigated with their direct report-to.
In Total Anhilation and to a lesser extent Supreme COmmander rushing doesnt really work. Best tactic is economic superiority (and thus winning through attrition) through skirmishing.
It makes sense too because otherwise it would be perfectly legal to run 400 simultaneous copied of something off of a shared disk.
So look for work for a software company then? Some people have a narrow view of "IT". There are other roles than general system support you know. Some of us work in profit centres.
You should post that to thedailywtf.com its pure genius!
[quote] I still the the acronym "MMO" sucks; shouldn't it be either "MMOG" or "MMORPG"? MMO would just stand for "Massively Multiplayer Online", which is somewhat lacking in the noun department. [/quote] Maybe player is the noun?
Yeah footnote arithmetic is a pretty bad idea.
Wubi is bookmarked for checking out when i get home. While I doubt im going to ditch windows for my stuff as Im quite entrenched it might well be a cool thing to have a play with.
Once I can take my VSTs with me then it becomes a sersious contender.
Yeah but its not like if I recompile my binary then that 6/8 middle section is going to flow into the verse better is it?
The mixdown step is more to do with the traditional process where mastering would be done by a separate engineer so its a workflow embedded in a lot of musicians subconscious already but theres nothing to stop you strapping your master fx over your master bus and working that way.
With a modern DAW I dont see why you would ever want to route audio to another application (MIDI is another story mostly due to one particular app [reason]) but see rewire) since all your audio apps will be running inside your DAW via VST or rtas anyway.
As for value for money. These days Reaper (unlimited free trial, 50 bucks license) is available on windows and Mac and is pretty much as fully featured as cubase, its missing some audio editing facilities but you can hook in audactiy as a helper app so going linux doesnt save you any money at all, except the OS license I suppose but quite frankly a windows OEM license is what a hundred bucks or so so by the time Ive wasted 2 or 3 hours trying to setup linux the windows license has paid for itself. Hardware of course you are fairly limited on what you can even use on linux so I doubt you get the most band for buck when your buying your interface either.
Basically if you dig linux and like toying around with this stuff I can see the attraction but as usual for people who arent interested in the technology aspect the workflow isnt optimal with a far to high barrier to entry in terms of initial configuration. This is the same problem linux has in other creative spaces.
You apparently have failed to discover the master bus in most audio software.
Their data is inherently low value though, and data corruption is largely unimportant. I bet you'd end up with the exact opposite view if you looked at banks and financial institutions.
I dont think you've had much experience in the enterprise world. Ive only used toy SAP systems to test some interfacing but typical implementations are gignormous this is the kind of stuff that replaces departments of hundreds of people.
I thought you had to write robots.txt on your roof in foot high letters.
Except that what alot of people are now realising is that you cant because it impairs your ability to write your own non-GPL'ed code.
Im unconvinced your any less locked in to be honest. Any non-trivial product in the OSS world is maintained by a specific team of people, usually funded by a corporate sponser. Realistically the time it takes to build the skills required to provide support makes it cost prohibitive for anyone but core developers to maintain most software. So if the core developers quite, like say because their corporate sponser quits footing the bills then your in almost exactly the same situation as with proprietary software. Possibly worse since most will be under no obligation to provide migrations paths.
Oh yes the linker elves.
What the hell do you do with yours? I have a 2yo work laptop that gets taken home every night and is absolutely fine and a 5 year old personal laptop that also gets lugged to band practice once a week (and associated exposure to beer, sweat, dropping, and risk of crushing by 4x12) and it doesnt show any signs of failure either.
I think you might be doing something wrong if you only a get a year out of yours.
Actually java datatypes are machine independant so they can be serialised and unserialised across architectures. Altering the size of the primitive types simply because your happening to be running on a different wordwidth cpu is a bad idea for portability.
And how often does MySQL participate in transactions involving multiple dbs?
I wouldn't really have said many of these are enterprise apps either, theres no messaging, app serving, transaction management. Theyre all just web apps really. I mean i'd have expected stuff like JBoss, ActiveMQ, Tomcat and such to be mentioned rather than vBulletin and OpenOffice.
Much like when to use each paradigm answer is in the focus of the degree course as a whole. For an AI course functional programming cant be beat since it abstracts away depth first search into the language and many have higher order logic constructs built in. For software engineering OO is king as it facilitates reuse. For systems and embedding programming focus procedural is the way forward.
Because it requires documentation and a user who can be bothered reading the documentaiton and understands the documentation. Further text is a free form interface. For example in /etc/spiffyapp/pathSetup I *could* write "SPIFFYPATH=/path/to/spiffyapp" but theres nothing to stop me writing "hello im a happy cloud, giblledideedeee" and to someone who isnt pretty technically literate theres no reason why one should instantly consider one more intuitive than the other. Whereas in a gui they would have a gui file chooser widget that only allows them to select paths.
The answer of course is to have both with the gui widgit a view onto the internal txt file / registry settings / xml docs / whatever.