afdssfda

Many were expecting more and may hold off for the 5. Sari is good for the first elitists that want to show it off, but people want to use their devices quietly- not talk to them. Although many don't want to admit it, it was a bad idea. When you have Gizmodo post a link to a Hitler video making fun of it immediately, you know it is bad. Not to be callous, but Jobs death probably spurred a lot of buying. That probably won't sustain.

Shameless iOS promotion.

Today (October 17, 2011), it went down. And, of course many will see Jobs gone as a problem, as well as iPhone 4S being somewhat of a bust. Whenever they release iPhone 5 and their killer settop media/gaming box, their stock may go up. But, for the most part the market is currently volatile and people are less in the mood to spend on higher cost products, so I would bet on a downward trend. Who knows though. I would not buy now.

The danger in the president learning to code is that no one wants to tell him his code sucks, then he releases/deploys it and fucks shit up. All I can say is "good luck".

It seems as though they still are weighed for sorting. Isn't that enough? I think it looks fine without the points, and hopefully it will reduce the number of people that say something a certain way just to get points. I just say whatever the hell I want to most of the time, though.

None.

I read a number of blogs when I search, but there are none that I go to daily just to read them.

delete from hacker_new where title = '%Occupy%';

...

Darn. Didn't work.

I think saying that Agile development is broken because it is too developer-centric is BS. It is all about implementation.

XP for example is meant to be customer-centric. The point of it is to complete working functionality for the customer, and the customer should drive the development and what features are needed.

Scrum is similar in that the customer can define a bunch of requirements and prioritize them and the team works on those priorities.

The problem with any development being about development and not about the customer's needs has to do with management. I've seen and heard of many mismanaged Agile teams, but none where the problem was Agile. Agile might have been the excuse for lack of organization and direction, but good management that focuses on the customer needs as well as the developers' needs is what is needed- that can be done with Agile (e.g. XP, Scrum), Kanban, and other methods focused on quick incremental delivery usually much more easily than other methodologies (e.g. Waterfall).

With regard to:

"As Igal pointed out in this summer’s webinar, what is a unit that is tested in a unit test? Business logic."

Strictly speaking, yes, but generally if you describe what a unit test is doing to a user, assuming it is really a unit test, most of the time they would not agree that it is business logic. Business logic is usually considered a lot more high-level. Human-language-based customer readable test definitions can potentially be created in Cucumber and similar BDD frameworks. There are also products that use UI-based behavior driven test definitions. But, in my experience, even these haven't really defined solely the business logic; there is always some level of implementation detail that creeps in. But, you do what you can. From what I've seen and heard, sometimes having the developer or analyst work with the customer to define tests is a good idea, and other times it is a wash or is a time sink. Do whatever it takes is basically the rule of thumb- i.e. there are no hard and fast rules to these things.

Good luck to the guy that ditches Agile because it is "broken".