Become a fan of Slashdot on Facebook


Forgot your password?

Comment: Re:If I use an IDE, does it mean I'm a bad program (Score 1) 423

by serviscope_minor (#49749129) Attached to: Choosing the Right IDE

Your comments are as foolish as a carpenter saying he only ever uses hand tools.

Oh analogy time. Firstly, my comments are nothing like that. If you think so then your reading comprehension is so low then there's little chance of you ever understanding this post. But whatever, I'll use your analogy, because bits of it work (also carpentry is a hobby of mine as it happens---though I'm not especially good).

Your original claim is like saying that sticking anyone in front of power tools will make them a productive carpenter.

But professional carpenters in this day and age are using power tools for most of their work.

This is hilarious. Remember your claim that "anyone in front of an IDE is productive", translates to "anyone in front of power tools is productive". If you let someone completely incompetent into a good woodworking shop with actual proper power tools, you're more likely to end up with a pile of fingers on the floor and broken machines than anything coherent made out of wood.

Because tools alone are not sufficient to make someone productive.

That last line is really the crux. The fact that you appear to not understand it is quite frankly astonishing. I do hope you're not in charge of any hiring decisions. Because according to what you're espousing here, you can hire literally anyone, stick them in front of an IDE (or powerful woodworking tools---why not) and have a productive member of the work force.

Anyway your analogy still sucks, because all of the IDE related tools are available with equal or more power outside the IDE.

Comment: Re:If I use an IDE, does it mean I'm a bad program (Score 1) 423

by serviscope_minor (#49742435) Attached to: Choosing the Right IDE

You're obviously an amateur, or someone who works on very small projects.

And you obviously lack a basic understanding of logic. Let's say we accept your absurd premise that one needs an IDE to be productive.

That makes an IDE necessary but not sufficient to be productive. If you put a monkey in front of an IDE, you wouldn't have a productive programmer.

The fact that you seem to think an IDE makes even very bad people productive is a strong indication that you either don't work in programming at all or you only ever work with the bottom 20% so you don't know what a productive programmer actually looks like.

Comment: Re:If I use an IDE, does it mean I'm a bad program (Score 1) 423

by serviscope_minor (#49742033) Attached to: Choosing the Right IDE

Jesus Christ I thought you were *JOKING*.

Are you honestly so stupid you think any drooling moron placed in front of an IDE is productive???

I can demonstrate it by pointing to a few of the drooling morons I know who have somehow become employed as programmers, or you know the legions of idiots on stack exchange.

Comment: Re:Not Just Marvel (Score 1) 228

When was the last time you saw more than a tiny fraction of women showing interest or excelling in something like engineering or computer programming?

Out of interest who is the only person to have won two science Nobel prizes in different disciplines?

My university had something like 95% male engineers, 5% female. And the brightest were always guys.

Mine was about 85% guys and the smartest in my year was female. Not only got the top exam mark she was excellent at the practical side too.

Just because they might be rare doesn't mean truly astoundingly bright female scientists and engineers don't exist.

I mentioned this in another thread, but other shows like "The Flash" depicts every single fracking woman as a supersmart, unmatched computer or mechanical engineer, programmer, physics whiz, etc. What universe does this show even take place?

A truly realistic universe where a guy can run at 1000 miles per hour?

Comment: Re:Do most of the work? (Score 1) 423

by serviscope_minor (#49735689) Attached to: Choosing the Right IDE

You mean you do potentially mass commits before checking, or even before compiling or running unit tests because problems with compilation and unit tests can - and will - occur when refactoring/renaming of artifacts is done wrong?

Sure, why not? git suppupports quick branching. I can make a branch, do mass commits, do the testing then squash the commits before merging if I like.

How come financial advisors never seem to be as wealthy as they claim they'll make you?