Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
Take advantage of Black Friday with 15% off sitewide with coupon code "BLACKFRIDAY" on Slashdot Deals (some exclusions apply)". ×

Comment Re:LESSON NUMBER #1 (Score 1) 118

Agile is the death of quality!

Not necessarily. In my hands, I guarantee you that Agile can deliver Quality.

However, I had worked in a Quality Control team before, and after, in a Quality Assurance one. So I know what must be done and why, so I know when some tests can be postponed, and what tests would be useless in a given moment.

The fallacy on the Agile movement is believing that all you need is coders. Worst, they think that TWO Quality ignorant developers together will compensate for the lack of formal testing. You can't give what you don't own - you need Quality Assurance and Control aware guys in your team.

Two pregnant women don't deliver a baby each six months - and you will need a father to raise the child after. But yet, it's common sense in Agile that you can lock up two women in a room and expect two childs a year - and nobody cares about the kids after they are born.

Comment Re:LESSON NUMBER #1 (Score 1) 118

Makes me wonder then why every developer I met so far (about 100) is fatally allergic to bug fixing. They rather fake their own death than fix bugs that they put into the code. Commonly, they just state "This is not a bug!" or "This was never requested!" effectively dismissing QA having any clue or say in the matter. QA is not the bad guys, QA is a mirror that developers can stand to look into....entirely self-inflicted!

You need new friends, i mean, developers.

You get what you promotes. If you promotes bad developers, you will get bad developments.

Yes, please, write bad code if that helps you learn, but then, please, fix it once you know better and don't give me all that BS. And stop discussing and triaging bug reports, go and fix the issues. Takes typically way less time than the discussion aimed at convincing everyone not to do anything.

And by all means, fire the fscking bastards that don't fix their mess. You get what you promotes.

Comment Re:Projects are much much more than code (Score 1) 118

In civil engineering the problems and needs are well understood, you also either build something or you don't.

Being the reason I don't think that Management is the key problem on I.T.

In IT the problems and needs are NOT well understood. Even when you do a ton of requirements gathering there will pop up edge cases or the legislative requirements change and you need to change your scope.

Yes. Somehow, some guys decided that it would be a good idea to start Projects without a well bounded requirements set in advance. And then the very same guys insisted in using management practices that works only on projects where that requirements set is well known, bounded and established.

You get what you design.

We are wrapping up a 4 year health records system implementation (successfully, not my credit though, I was just a SME on it) and we have the big brown paper sheets the original workflow and process needs were mapped out on, they are laughably out of date. A big part of the success is the platform we are using is custom but its a framework so some areas were able to be their own subprojects.

Good design.

Most of the big failed projects that I have seen the common complaint is the scope creep and changing scope made it impossible to actually deliver. Coders can only code what they are asked to, yes there may be bad code in there along with the good code but that code does not matter if the scope changed and its no longer valid.

Agreed. And the most successful projects I have seen are the ones that can be break in small enough parts where the developers can have a word on the design and implementation. Not necessarily the final word, as the parts should connects each other and what can be the best solution for a component, can kill the other.

Management has a very small role on this process (what's different from saying that Management has no role on the process).

Comment Re:Projects are much much more than code (Score 2) 118

You underestimate the importance of good coders. Or perhaps, overestimate the importance of managers.

Good developers can delivery a viable product besides bad management. But the best management of the World can't deliver a viable product without a minimum threshold of good code!

I agree and understand the problematic of big projects, I had my share of it too. But when the worst happens, and it eventually happens (more than once I saw a project being trashed by external causes, as a legislation that was changed without notice that fsck up our funding) it was always possible to salvage something from the mess, specially good and well written artifacts that were reused on other projects. Bad code is always trashed.

However, it is clear that the failure rate in large IT projects is higher than in projects, for example, from Civil Engineering. The Project Management Theory is essentially the same for all areas, so I have serious reservations to believe that this apparent crisis in IT is merely managerial.

Comment Re:This seems contradictory (Score 1) 210

Assange is offically not wanted by the US, and he already have the right to be in EU. Snowden needs an Asylum to protect him from being extradicted, and to be allowed to stay in EU in the first place.

Humm... Do you realize that Assange is the one in confinement inside the Ecuador's Embassy IN LONDON in order to avoid extradition, don't you?

Comment Re:This seems contradictory (Score 1) 210

Oh horsepoo.

Lisias. Nice to meet you. :-)

The EU were a willing party in the campaign to spy on citizens of the world. They are only a bit pissed when it turned out senior government figures were being spied on too.

Exact. They want to spy citizens of the world, they don't want the world spying THEIR citizens.

Being the reason I stated " *their* privacy concernings", not mine of yours. ;-)

Comment LESSON NUMBER #1 (Score 5, Insightful) 118

You will never write good code without writing bad code first.

And you will never stop writing bad code without being accountable for the results of writing bad code.

Experience is not how long you spend writing code. Is about how much time you spend fixing code, learning how to avoid having to do it again,

Comment Criticizers. (Score 1) 61

On the other hand, it would be a good idea to people stop harassing open source projects when serious and/or old bugs are discovered *and* fixed.

Nasty 7 years old bug discovered? Bad indeed.

Nasty 7 years old bug *FIXED*? Good, very very good.

Once you decide not to throw everything through the Windows, I mean, window every year ("fixing" old bugs with new bugs), you must expect that old flaws will one day be discovered. And fixed.

There're too many criticizers nowadays - but almost none of them got his hands dirty to know what they are criticizing.

Comment Re:This seems contradictory (Score 4, Interesting) 210

This seems entirely contradictory to their stance on Assange.
I wonder why.

It's a wild guess, but perhaps Snowden being a whistle blower that helped (indirectly) the EU in their privacy concernings, in contrast with Assange, that is a whistle blower that fsckd up every single Country in the World, can be a reason.

Comment Re:Welcome... (Score 1) 217

Are you sending your bank account number, your social security number, and your personal phone number in plaintext email messages ..?

You have that information? No? It's because I didn't sent to you.

But how I can prevent someone else to send you such information using non secure channels?

The only possible way is never give such information to anyone. But that would render you useless on society - try to get paid without an bank account, or try to get medical care without your social security number.

Once you give this information to anyone, you can't control it anymore.

All you can do is to prevent that yourself would be the leaking vector. But that's all.

Comment Re:Welcome... (Score 1) 217

My son's phone number, that is not Android and I don't want nobody out of the family to know. Just for starters.

They knew his phone number the moment one of your family or his friends added it to their android contact book.

If and only if they also adds the custom email I made to him to play on the Social Networks - what don't happens. The email account he's allowed to give away is another one.

Without a direct connection, the info is useless for them. Some social engineering can be used to infer that that phone number can be related to my son, as it's added to my sister's phonebook that is registered using an email account that was used to register an G+ account where it's said she is my syster. But what would be the value of such non-confirmable information for them? Too much hassle for such valueless information.

No problem is so formidable that you can't just walk away from it. -- C. Schulz