comlonq

I not able to come up with politer wording yet I'm downvoted. Total discrimination.

Terrible analogy.. Your wife complains about you being away so you tell her to shut up becuase military families have it worse? Yeah... when my kids are hungry, I'll tell them to quit complaining because some kid in Africa is worse off....

Jesus christ man - all of this sacrifice for a time sheet application? Is it really worth it?

Can't believe all the down votes for this!

Don't make me think... I should be able to copy and paste without any browser tricks or viewing the source.

So I have to click a mailto link rather than letting me copy and paste the email address? I don't have a mail client set up on this machine. Good one....

I read the Oracle complaint in full (unlike you). Some of the staff at Oregon were modifying software config on production servers which totally circumvented Oracle release procedures... Oregon would not lock down solid requirements... Stakeholders and requirements would change frequently and existing work would be rendered obsolete.

I've worked with those kind of badly managed clients before. They likely ignored Oracle's advice, came up with nonsense strategies and requirements then kept being vague about the details.

Go and keep turning you bakers over off or requesting crazy ingredients that should never go into mixture (against the bakers advice) and see what kind of bread you get.

Change "rich white tech workers" to "Mulsim" or "Indian". People move, things change, if you've got a problem with white techy folk driving house prices up then I'm sure you also have a problem with various amounts of South Asian immigration driving house prices down.

Anti-immigration / anti-change is stupid. Nobody would be where they are today if change never happened. Get off my lawn.

I used to work for Accenture as a technical consultant.

Having read both complaints, I'm on Oracles side more than the Oregons.

On so many big IT projects I would see the client constantly change requirements, be very vague, change stakeholders who then completely move the goal posts and effectively hold the project back for large periods of time.

It's not surprise that large projects fail when you see the state of most large clients.

This highlights a much larger problem. Our processes for delivering large IT projects need a radical change in order to stop toxic stakeholders tanking whole projects.

However, Some of Oracle's products are shit and do fuck all out of the box despite what the sales people say.

For some reason, this was worth a downvote even though it has some validilaty.

If you find yourself regularly having to force that kind of behaviour out of a language that doesn't support it, you're using the wrong language or you have a bad design.

Yes, that is exactly what Apple did with the iPhone. They wrote the interface then tested it over and over again and made optimisations on every iteration.. This was before it was released to the general public.

The article is talking about optimising before you can prove where the problems are... Apple had excellent testing which showed where a lot of issues were. Some issues may well have not been discovered until a wider audience had access though.

Testing can happen before you release a product you know? You new fangled startup MVP types only think good testing happens on paying customers. Fuck you guys.

Interestingly, Grainger are using an off the shelf ecommerce platform called hybris. I imagine they made (or got someone to make) many modifications to its extended functionality though.

I don't see how this is in any way related to my comment?

Not everyone is you.

I enjoy a wonderful and varied diet since I moved near the coast in Australia... some days I would just rather not have to eat though (various reasons). For these days, why not use Soylent?