In a decent engineering environment, regardless of it being "agile" or not, I would hope that the decision was made to formally release to customers, and a branch was created for that release. After a short period of stabilisation (removal of critical bugs, but no more features) the most recent build from that branch can be released, while feature development has continued on master/trunk. All of those bug fixes can be merged back into master for mainline development.
Sure, you might provide canary/integration/every-stable-build-of-master-from-the-CI-system releases to stakeholders so they can track development and give feedback, but your releases need to be managed. How else are you ever going to support that release after your customers have got hold of it - ie supply bugfixes for it without forcing them to upgrade to a newer release that might contain masses of new features, bugs, and incompatible changes?
Except, in true American film style, it takes extreme liberties with the facts. It wasn't even filmed at Bletchley Park either - which was criminal IMO (supposedly Bletchley Park didn't look enough like Bletchley Park so they used Chicheley Hall instead).
If you don't know what the comma is for, then it is usually better to leave it out altogether.
But (to continue this digression), I wish some people would get over this fallacy that it is perfectly OK to mangle the language in any way they please, then speciously attempt to justify this by calling it "evolution according to common usage". Obviously, the language can only evolve according to customary usages that change over time, but to use the phrases "couldn't care less" and "could care less" to mean the same thing is plainly nonsensical, and reflects poorly on the writer's cognitive skills.
Is that why you abused the comma at least twice in your reply?
Fortunately, while punctuational pedantry is alive and well, the English language is fairly robust against the incorrect use of punctuation. However, I agree that interchanging "couldn't care less" and "could care less", a grammar mistake that completely changes the meaning of the phrase, is a horrible abuse of the language.
There is nothing to require you to release the source of a BSD derived binary you ship. Apple do it purely out of respect, not obligation. The GPL, however, forces you to release your source (as far as it can be enforced anyway).
Other than the africanized honey bee fiasco, bees tend not to sting. Most species of bee die soon after stinging and they are reluctant to do so. This doesn't apply to wasps, hornets and most other stinging insects. By breeding out the stinger we might totally change the behaviour and properties of the insect.
Yes, it is more like 70-80% of crops (http://www.sciencedaily.com/videos/2007/0703-honeybee_decline.htm). The World is still fucked without them.
Oh, you meant in the USA, where most of the food (as here in the UK) eaten is manufactured crap - so yeah, optimistically 30% of the food the USA consumes (http://news.nationalgeographic.com/news/2004/10/1005_041005_honeybees.html).
get your own website and put your photos there...jeebus cristo, you people are TECHIES. act like it...lazy. do your own site and html.
Yep. I spend all day writing software and battling with annoying issues in app servers and application frameworks. Damned right I'm going to be lazy and take the easy and, generally, more flexible, robust and accessible options when I'm using my own time to do it.
The code review process we use is pretty lightweight yet thorough (it is built around gerrit and hudson), and we've caught lots of issues before they made their way into the codebase. I'm sure we've stopped more bugs going into the repository than we could have fixed if we hadn't been doing reviews. We also generally have cleaner code going into the repository, because now everything is being reviewed the team are striving for clarity.
Admittedly this is a small project - 500k semicons, around 8 developers (typically around 5 very experienced, 3 junior) at any one time - but I don't see how overall productivity could do anything other than go up. We also have poor test coverage (but better than the majority of projects I've seen) - about 35% overall, but close to 75% on the critical core parts. The GUI is currently lacking any significant tests, but thats partly a byproduct of having rapidly changing customer requirements for the GUI - it is also where the majority of our regressions have historically been.
The conservative party is for the rich though - and have the interests of the rich at heart. Not the wannabe 'middle classes' (working class really, but think they aren't) that seem to always vote for them.
In other words, I'm not surprised. If you can't play the games with the wealth, you aren't rich enough to take part.
It's not corporation websites that are badly coded, it is internal business applications in most cases. Typically, these were developed under contract, or by a development team that has long since moved on. In some cases source isn't available. In almost all cases no resources (financial or bodies) are available to apply any fixes.
I've seen a couple of applications break (buttons stop working, JavaScript breaks, security is tightened so XSS that used to work no longer does, etc) between Firefox releases but, as you say, it is nothing as bad as with IE as you say.
The places I've worked have traditionally refrained from anything other than IE because there are no decent corporate configuration or lockdown tools as there are with IE. Firefox or Chrome on the Internet would be a dream come true - as it is, I'm stuck with IE7 in a Citrix session until issues with some internal apps are resolved (and there is no timeframe for that at the moment). Sigh.
Except it is far too easy to write bad code in them. A language that encourages good practices is better starting point - Python springs to mind (even though I'm not a fan)
It's just a release. Releases are deprecated almost immediately with security updates, new features / API changes etc. The only difference here is the version numbering is insane which makes it harder to see what has broken.
To me this reads like it is meant as a move against Apple over the reader feature that is built into the upcoming iOS5 (which works surprisingly well).
They aren't clean though. I live in the UK with a VW using the same engine, and here it is considered a luxury higher performance engine. If you care more about "clean" you go for the blue motion - that isn't clean either though.
Which requires Exchange and only runs on certain versions of Windows, and has a slew of other restrictions.
If you run another ActiveSync capable server on a non-Windows platform you are screwed. And yes, some small-medium sized companies are looking to quality Exchange alternatives, such as Kerio (which requires far less resources to serve more people).
Slashdot Mirror
In a decent engineering environment, regardless of it being "agile" or not, I would hope that the decision was made to formally release to customers, and a branch was created for that release. After a short period of stabilisation (removal of critical bugs, but no more features) the most recent build from that branch can be released, while feature development has continued on master/trunk. All of those bug fixes can be merged back into master for mainline development.
Sure, you might provide canary/integration/every-stable-build-of-master-from-the-CI-system releases to stakeholders so they can track development and give feedback, but your releases need to be managed. How else are you ever going to support that release after your customers have got hold of it - ie supply bugfixes for it without forcing them to upgrade to a newer release that might contain masses of new features, bugs, and incompatible changes?
Same monarchy (though basically puppets now), but definitely not the same Government.
Except, in true American film style, it takes extreme liberties with the facts. It wasn't even filmed at Bletchley Park either - which was criminal IMO (supposedly Bletchley Park didn't look enough like Bletchley Park so they used Chicheley Hall instead).
If you don't know what the comma is for, then it is usually better to leave it out altogether.
But (to continue this digression), I wish some people would get over this fallacy that it is perfectly OK to mangle the language in any way they please, then speciously attempt to justify this by calling it "evolution according to common usage". Obviously, the language can only evolve according to customary usages that change over time, but to use the phrases "couldn't care less" and "could care less" to mean the same thing is plainly nonsensical, and reflects poorly on the writer's cognitive skills.
Is that why you abused the comma at least twice in your reply?
Fortunately, while punctuational pedantry is alive and well, the English language is fairly robust against the incorrect use of punctuation. However, I agree that interchanging "couldn't care less" and "could care less", a grammar mistake that completely changes the meaning of the phrase, is a horrible abuse of the language.
There is nothing to require you to release the source of a BSD derived binary you ship. Apple do it purely out of respect, not obligation. The GPL, however, forces you to release your source (as far as it can be enforced anyway).
My iPad2 and iPhone4, like pretty much every colour LCD screen, are practically unusable outdoors in sunlight.
WINE
I'm running iOS 5 betas, and yes, it is true. Wire free activation and cloud backups.
Other than the africanized honey bee fiasco, bees tend not to sting. Most species of bee die soon after stinging and they are reluctant to do so. This doesn't apply to wasps, hornets and most other stinging insects. By breeding out the stinger we might totally change the behaviour and properties of the insect.
Yes, it is more like 70-80% of crops (http://www.sciencedaily.com/videos/2007/0703-honeybee_decline.htm). The World is still fucked without them.
Oh, you meant in the USA, where most of the food (as here in the UK) eaten is manufactured crap - so yeah, optimistically 30% of the food the USA consumes (http://news.nationalgeographic.com/news/2004/10/1005_041005_honeybees.html).
Clearly this isn't a problem at all.
If this is true, the parent should be modded up (there are plenty of articles suggesting it needs more research - eg http://www.fastcompany.com/1710746/bayer-our-bee-toxic-pesticide-is-actually-safe-for-bees)
get your own website and put your photos there...jeebus cristo, you people are TECHIES. act like it...lazy. do your own site and html.
Yep. I spend all day writing software and battling with annoying issues in app servers and application frameworks. Damned right I'm going to be lazy and take the easy and, generally, more flexible, robust and accessible options when I'm using my own time to do it.
If that is the case you are doing it wrong.
The code review process we use is pretty lightweight yet thorough (it is built around gerrit and hudson), and we've caught lots of issues before they made their way into the codebase. I'm sure we've stopped more bugs going into the repository than we could have fixed if we hadn't been doing reviews. We also generally have cleaner code going into the repository, because now everything is being reviewed the team are striving for clarity.
Admittedly this is a small project - 500k semicons, around 8 developers (typically around 5 very experienced, 3 junior) at any one time - but I don't see how overall productivity could do anything other than go up. We also have poor test coverage (but better than the majority of projects I've seen) - about 35% overall, but close to 75% on the critical core parts. The GUI is currently lacking any significant tests, but thats partly a byproduct of having rapidly changing customer requirements for the GUI - it is also where the majority of our regressions have historically been.
The conservative party is for the rich though - and have the interests of the rich at heart. Not the wannabe 'middle classes' (working class really, but think they aren't) that seem to always vote for them.
In other words, I'm not surprised. If you can't play the games with the wealth, you aren't rich enough to take part.
The UK isn't really part of Europe though, thankfully. However, the thought of an unpaid intern is somewhat repugnant here in the uk.
I carrier unlocked my iPhone too. I bought one from the Apple Store, brand new, sim-free, with no carrier lock.
It's not corporation websites that are badly coded, it is internal business applications in most cases. Typically, these were developed under contract, or by a development team that has long since moved on. In some cases source isn't available. In almost all cases no resources (financial or bodies) are available to apply any fixes.
I've seen a couple of applications break (buttons stop working, JavaScript breaks, security is tightened so XSS that used to work no longer does, etc) between Firefox releases but, as you say, it is nothing as bad as with IE as you say.
The places I've worked have traditionally refrained from anything other than IE because there are no decent corporate configuration or lockdown tools as there are with IE. Firefox or Chrome on the Internet would be a dream come true - as it is, I'm stuck with IE7 in a Citrix session until issues with some internal apps are resolved (and there is no timeframe for that at the moment). Sigh.
Eh?
Except it is far too easy to write bad code in them. A language that encourages good practices is better starting point - Python springs to mind (even though I'm not a fan)
Mod Parent Up.
A more sensible solution would be to declare which APIs the add-on requires, and for the browser to say whether they are available or not.
It's just a release. Releases are deprecated almost immediately with security updates, new features / API changes etc. The only difference here is the version numbering is insane which makes it harder to see what has broken.
To me this reads like it is meant as a move against Apple over the reader feature that is built into the upcoming iOS5 (which works surprisingly well).
They aren't clean though. I live in the UK with a VW using the same engine, and here it is considered a luxury higher performance engine. If you care more about "clean" you go for the blue motion - that isn't clean either though.
Which requires Exchange and only runs on certain versions of Windows, and has a slew of other restrictions.
If you run another ActiveSync capable server on a non-Windows platform you are screwed. And yes, some small-medium sized companies are looking to quality Exchange alternatives, such as Kerio (which requires far less resources to serve more people).