|
I like the way it works (for the reasons mentioned by Max and Eddie).
[edit]
But it's nice to have the option. 
[/edit]
/ravi
|
|
|
|
|
|
Jeeze, he's really caught up with technological evolution if he's gone from hunting with a bow to providing cloud services.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
They're lying - it's not Orion!
I looked very carefully, and there are no attack ships burning off the shoulder - it can't be Orion. 
|
|
|
|
|
Batty [^]
I met him once a few years back in a Starbucks, waiting to get coffee. Very nice chap.
|
|
|
|
|
SET RANT ON
I really, really hate that stooooopid little find thingy that pops up when you press CTRL+F.
SET RANT OFF
Have a nice day.
If it's not broken, fix it until it is
modified 16-Mar-15 10:24am.
|
|
|
|
|
Where is that then I can't find it.
|
|
|
|
|
So? Don't press it! 
And don't leave your rant on all day long now... There are third world children who can't rant at all... 
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the time
|
|
|
|
|
Try hitting Ctrl-Shift-F.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
ya, I know... but MS changed they key combos in VS2012 ... CTRL+F USED to open the Find WINDOW, not the Find thingy..
WHY???? WHY???? WHY????
If it's not broken, fix it until it is
|
|
|
|
|
Kevin Marois wrote: SET RANT ON
Kevin Marois wrote: SET RANT ON
That will require TWO "Release Rant" calls! 
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Sorry, I was really annoyed
If it's not broken, fix it until it is
|
|
|
|
|
for(int x = 0; x < 2; x++)
setRant(Rant.OFF);
If it's not broken, fix it until it is
|
|
|
|
|
Ah, you must be the CP automatic debugger.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
The developer has less time for just coding - but doesn't need that time because what is produced works, and suits the customer's needs.
PooperPig - Coming Soon
|
|
|
|
|
_Maxxx_ wrote: because what is produced works
I can see you haven't used any _modern software_ lately.
Now, 'at right 'ere is funny!! 
|
|
|
|
|
Yah, agile isn't about making functional software.
It is about giving visibility to the stake holder so that at the end of the day, they can't say it's wrong. "YOU ASKED FOR IT!"
So in effect, there is an illusion of satisfaction... 
|
|
|
|
|
newton.saber wrote: Developer has not time for development because s/he is too busy being Agile!!
I'm very agile at clicking the "close" button on my browser if I accidentally navigate to such crapware. Keep in mind that Microsoft is, in its ever so non-agile, lethargic way, jumping on the bandwagon as a knee-jerk reaction to the unthinking developer mass.
Agile? 
I just added about 50 user stories to Pivotal Tracker. And guess what? Because they are user stories, none of them directly captures the need for a REST API, and the task of such touches about 30 of those user stories.
User stories are great for capturing, well, user stories, but it does nothing for capturing the behind-the-scenes requirements, unless of course I want to add under those 30 user stories the same task "create a REST API to support this feature."
Blech. The whole concept of Agile was dead on arrival, IMO.
Marc
|
|
|
|
|
Marc Clifton wrote: Keep in mind that Microsoft is, in its ever so non-agile, lethargic way, jumping on the bandwagon as a knee-jerk reaction to the unthinking developer mass.
That is a perfect summary of that advertisement.
It is so obvious -- after viewing the site -- that the agile app that MS is putting out there is indeed just a knee-jerk reaction and some crazy Suit saying, "we need an Agile management solution!! Make it happen!!"
It doesn't even look good.
Well, it probably will in another 123 revisions. For now, this will keep people busy clicking around.
|
|
|
|
|
Marc Clifton wrote: The whole concept of Agile was dead on arrival
My overall tendency is to completely agree. However, the Agile process probably worked for that one high-performance, integrated team that derived it and used it successfully. In fact, whatever regime they decided to apply would probably have succeeded because they were "that sort of team"
IMHO the real problem arises with the bandwagon-jumpers and management who believe one-size-fits-all!
An ex-colleague is becoming increasingly frustrated by being forced to follow "Agile" (the company in question fall into both the bandwagon and one-size categories above), and is convinced that the old team we both worked in would have a working application in production already, that actually did do what the Users wanted.
On the flip side, the "better half" claims to be working with an IT team that are making the Agile process really work ... I have my doubts though, they seem to spend an awful lot of time talking about how long it will take
|
|
|
|
|
|
Marc Clifton wrote: User stories are great for capturing, well, user stories, but it does nothing for capturing the behind-the-scenes requirements
That's not true, because at least one developer who is working on the product has noticed the point you are making, so the issue can be raised at the next planning session, where how to handle the common requirement of a lot of stories can be discussed by a bunch of intelligent people (i.e. developers working on the project, not "other employees of the company")
That's one of the main reasons why agile works: it makes developers talk to each other.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
Damn!
You're right!
CP must be shut down immediately!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
