Forgot your password?

Comment: Re:Want (Score 1) 453

by plopez (#46779459) Attached to: Survey: 56 Percent of US Developers Expect To Become Millionaires

Empirically not very likely. Either the company will implode; which happens to most small businesses I think the statistic is 90% in the first year or two; or you will move on after burning out, or die, or your stock options will never be above water before they get bought out and then you are laid off, or the principles disappear after getting another round of funding, or one of the principles dies or gets very ill, etc. I grew up in a family of small business people. It can be REALLY hard to get a business up off the ground, especially when you are running on borrowed money and promises. The "Startup BIllionares" are few and far between compared to everyone who takes the gamble.

Comment: Re:That's Not DevOps (Score 1) 223

by plopez (#46767533) Attached to: How 'DevOps' Is Killing the Developer

There is what I call "Cargo Cult" management. Some smart people observe things, collect metrics, and develop techniques which improve the way of doing business at least in some circumstances. There are some successes at least initially as early adopters see its value and being often above average use it in their situations. But then it becomes popularized by seminars, books, etc. and it becomes a buzzword. So people buy the books, got to the seminars, take the training etc.

But something happens. Maybe the intelligence level regresses to the mean or the people picking it up are too rigid to change or they are too cynical or lazy. But instead of really understanding the methodology they just buy the books, attend training and seminars, get the certifications etc. They know the buzzwords but they really do not know the meaning behind them. They do not "get it". It becomes a "Cargo Cult" exercise. So it starts to fail and people start to look for the next magic bullet.

It happened with TQM, Six Sigma, CMM, XP Agile, pair programming, and probably a host of others I probably do not know of.

Comment: It makes perfect sense (Score 4, Informative) 322

by plopez (#46736241) Attached to: IRS Misses XP Deadline, Pays Microsoft Millions For Patches

Hypothetical situation. I am an IT director. I track trillions in revenues and hundreds of billions in taxes. Do I 1)
switch to a new system with unknown security risks and associated costs in upgrading in house systems and applications?
2) Do I stick with a true and tried system for a few tens of millions more?

No brainer. Stick with the devil you know. This is not some happy little mobile app like the "Annoyed Nematode" you are dealing with the financial futures of both the US government and each and every person who must file taxes.

Comment: Re:Ooooh shiny (Score 1) 272

by plopez (#46707093) Attached to: Ask Slashdot: Which NoSQL Database For New Project?

" if configured and used correctly"
There's the rub. Configuration takes knowledge and work and most developers think there is a magic way to avoid it. There isn't. If you don't need data consistency or atomic operations but throughput you also have the option of turning off logging. That gives you a mature DB engine that is proven with much faster through put.

"If you've designed a bulletproof database schema, optimized all your queries to the bone, created every possible index on every possible table, partitioned your database files and even thrown hardware at it"
In other words, done everything a good DBA should.

Sacrificing data integrity is ok if it is a happy little mobi game. Go for it. If it has anything to do with human life, e.g. medical records, you had better think long and hard about sacrificing data integrity.

"Look! There! Evil!.. pure and simple, total evil from the Eighth Dimension!" -- Buckaroo Banzai