Then you have "implemented" agile incorrectly. FWIW, Agile isn't a methodology - it's just an ethos. You need sensible processes in place to manage it - ie something like Scrum and a framework to support it. Sadly, most people really don't grok scrum or the point of agile and therefore their projects aren't agile and don't deliver.
If you are constantly under pressure to the point you feel you can't work and wont complete tasks, you have far too much in your sprint backlog, or each entry is just far too huge.
You most likely don't have any proper management tools in place either, let alone a rapid continuous integration build process (if it takes more than a few minutes to build the entire product, you are screwed - I know of one "agile" environment where CI builds take over an hour for a relatively small codebase that could be built in less than 10 minutes if done properly, and up to three hours for a full nightly build with test coverage reports etc).
The best I've found so far is Kerio, followed by axigen. Both FULLY integrate with outlook (so the users that refuse to switch/use another client can continue), give a decent web app, and provide full activesync support.
Both are cheaper than Exchange and easier to backup too.
And have to maintain your fork, force everyone else to install another (likely bug ridden, slowly maintained) version of the language if they want to run your tiny number of programs, and increase the likelihood of subtle errors due to the minor inconsistencies between the language programmers know well and your fringe fork. No thanks.
Clearly you code using a text editor, rather than a programmers editor or other environment that fully understands the language you are writing.
Comments in code such as/* end if */ drive me batshit crazy, and they make the code impossible to maintain and refactor, and they just make everything much harder to read.
And yes, you need indenting. Your brain naturally segments things you see - we even read by recognising blocks. Removing the indentation just makes that information harder to understand
I don't see how tabs vs braces makes any difference to properly delimiting blocks of code either. Both force the programmer to do the same thing - it is just the presentation that is slightly different. In any case, if I want to see my code all on one line because it fits my braille reader better, why shouldn't I?
I live in the UK, so I'm not so bothered about the taxation issues in the US - although similar practices go on here. If I lived in the US it would take me years to recover from the shock of how little taxation is applied to fuels anyway though;-)
There are more people in the UK that feel they can't drive an auto than feel they can't drive a manual. I'm assuming the GG...P was talking about the UK, since he used the term "roundabout".
No you don't. In a modern turbo diesel you get the torque from the engine exactly when you need it. And turbo lag is nothing like as bad as your exaggeration suggests. And if you actually like driving and have a manual box, the pulling out on a busy roundabout situation you described should never happen as one is able to have the engine (and turbo) spinning at sufficient speed this is never going to happen.
Put it this way, unless something big changes, I'll never buy another petrol engined car.
So, it has a garbage collector. Whoopie-do. It also has awkward syntax, and suffers from loads of issues around dynamic typing. And it has no concept of namespaces.
The GP was right - it does feel backward - and it's only so popular because Apple essentially mandate its use for the iPhone.
Hardware costs and software licences, as well as soft costs such as network infrastructure costs (bandwidth, pipes etc) and travel. And then you have to add on the costs of hiring people from London, and the extra mark up of getting people through a company such as Capita.
The old "55 everywhere" limit was put in place 40 years ago when that hit the fuel efficiency curve of cars at the time. That is no longer true.
Interesting - do you have any stats to back that up? I live in the UK where most of the roads outside of cities are 60/70mph limits, and I get significantly better fuel economy driving at 50mph than I do at 70mph, let alone 80 or 90mph (I have a fairly fuel efficient modern turbo diesel).
Don't people in Canada have WiFi at home? Surely if the illness was WiFi related they'd be suffering at home, in cities, on planes, or any other populated place?
The banking system used enigma until the 1950's even though the UK could decrypt messages effectively a decade before. (do you believe that collossus was really shut down?)
Collossus wasn't used to crack Enigma - it was used to crack messages from Lorenz machines, which were more complicated than Enigma. The amazing thing is that the cryptologists at Bletchley were able to figure out the way the machine worked having never seen one (indeed, they didn't see one for over 2 years after cracking it) due to an error by a machine operator. But yes, I do believe it was really shut down and evidence destroyed - that's why it took so many years of painstaking reconstruction from photographs and human memory to rebuild one of the things...
The dials on an Engima rotate btw rather than parts inside of them. Each rotation of the wheels causes different pathways through the rotors to be used, thus changing the output - IIRC you can see the wiring inside some of the rotors at both the NSA museum, and the equally amazing Bletchley Park Museum in the UK (http://www.bletchleypark.org.uk/)
Slashdot Mirror
Interesting implications if it turns out to be possible in humans too!
Then you have "implemented" agile incorrectly. FWIW, Agile isn't a methodology - it's just an ethos. You need sensible processes in place to manage it - ie something like Scrum and a framework to support it. Sadly, most people really don't grok scrum or the point of agile and therefore their projects aren't agile and don't deliver.
If you are constantly under pressure to the point you feel you can't work and wont complete tasks, you have far too much in your sprint backlog, or each entry is just far too huge.
You most likely don't have any proper management tools in place either, let alone a rapid continuous integration build process (if it takes more than a few minutes to build the entire product, you are screwed - I know of one "agile" environment where CI builds take over an hour for a relatively small codebase that could be built in less than 10 minutes if done properly, and up to three hours for a full nightly build with test coverage reports etc).
The best I've found so far is Kerio, followed by axigen. Both FULLY integrate with outlook (so the users that refuse to switch/use another client can continue), give a decent web app, and provide full activesync support.
Both are cheaper than Exchange and easier to backup too.
I'll bite - which bits?
And have to maintain your fork, force everyone else to install another (likely bug ridden, slowly maintained) version of the language if they want to run your tiny number of programs, and increase the likelihood of subtle errors due to the minor inconsistencies between the language programmers know well and your fringe fork. No thanks.
Clearly you code using a text editor, rather than a programmers editor or other environment that fully understands the language you are writing.
Comments in code such as /* end if */ drive me batshit crazy, and they make the code impossible to maintain and refactor, and they just make everything much harder to read.
And yes, you need indenting. Your brain naturally segments things you see - we even read by recognising blocks. Removing the indentation just makes that information harder to understand
I don't see how tabs vs braces makes any difference to properly delimiting blocks of code either. Both force the programmer to do the same thing - it is just the presentation that is slightly different. In any case, if I want to see my code all on one line because it fits my braille reader better, why shouldn't I?
I wish I had mod points! That rocks! :-)
+5 funny!
I live in the UK, so I'm not so bothered about the taxation issues in the US - although similar practices go on here. If I lived in the US it would take me years to recover from the shock of how little taxation is applied to fuels anyway though ;-)
There are more people in the UK that feel they can't drive an auto than feel they can't drive a manual. I'm assuming the GG...P was talking about the UK, since he used the term "roundabout".
Yeah, we all drive the nuts off our cars to get from 0-60 as fast as possible.
In real world driving the diesel makes much more sense.
And anyway, the 2.0FSI Golf is pretty much comparable to the 2.0TDI in terms of 0-60 speed (8.6/8.9s vs 9.0/9.2s depending on configuration).
No you don't. In a modern turbo diesel you get the torque from the engine exactly when you need it. And turbo lag is nothing like as bad as your exaggeration suggests. And if you actually like driving and have a manual box, the pulling out on a busy roundabout situation you described should never happen as one is able to have the engine (and turbo) spinning at sufficient speed this is never going to happen.
Put it this way, unless something big changes, I'll never buy another petrol engined car.
Wooooooooooooooooo!
So, it has a garbage collector. Whoopie-do. It also has awkward syntax, and suffers from loads of issues around dynamic typing. And it has no concept of namespaces.
The GP was right - it does feel backward - and it's only so popular because Apple essentially mandate its use for the iPhone.
The units are arbitrary. What does it matter as long as the version number changes (or increases) ?
So fix your broken government department's IT policy.
If your English is that bad, I'm not that confident about your mathematic abilities to bother!
Hardware costs and software licences, as well as soft costs such as network infrastructure costs (bandwidth, pipes etc) and travel. And then you have to add on the costs of hiring people from London, and the extra mark up of getting people through a company such as Capita.
The old "55 everywhere" limit was put in place 40 years ago when that hit the fuel efficiency curve of cars at the time. That is no longer true.
Interesting - do you have any stats to back that up? I live in the UK where most of the roads outside of cities are 60/70mph limits, and I get significantly better fuel economy driving at 50mph than I do at 70mph, let alone 80 or 90mph (I have a fairly fuel efficient modern turbo diesel).
I've never got the whole "death to java" thing - can you explain why you think its demise is way over due?
Yeah, who would want to be second?
* rolls eyes
Don't people in Canada have WiFi at home? Surely if the illness was WiFi related they'd be suffering at home, in cities, on planes, or any other populated place?
Again, please cite something that discusses the distortion, otherwise I'll assume it is because you are suffering from some kind of impedance mismatch
The spy museum is good fun though :-)
The banking system used enigma until the 1950's even though the UK could decrypt messages effectively a decade before. (do you believe that collossus was really shut down?)
Collossus wasn't used to crack Enigma - it was used to crack messages from Lorenz machines, which were more complicated than Enigma. The amazing thing is that the cryptologists at Bletchley were able to figure out the way the machine worked having never seen one (indeed, they didn't see one for over 2 years after cracking it) due to an error by a machine operator. But yes, I do believe it was really shut down and evidence destroyed - that's why it took so many years of painstaking reconstruction from photographs and human memory to rebuild one of the things...
The dials on an Engima rotate btw rather than parts inside of them. Each rotation of the wheels causes different pathways through the rotors to be used, thus changing the output - IIRC you can see the wiring inside some of the rotors at both the NSA museum, and the equally amazing Bletchley Park Museum in the UK (http://www.bletchleypark.org.uk/)
Boom boom?! :(
(citation needed)