American vision

Is front-end development a dumb thing to learn?

Answer @Quora: Is front-end development a dumb thing to learn? Something to consider if u r aspiring 2b a developer

Answer by Rahul Dogra:

One of the major demands of a front-end developer is staying on top of design and code trends to always present the most relevant, inviting and engaging visual experience and interaction for users and in no ways it is a dumb thing to learn.A front-end designer is responsible for combining the strictly visual work of designers with the behind-the-scenes structure created by back-end developers. With an eye for aesthetics and an understanding of the nuts and bolts that make websites work, he (or she!) is responsible for coding the look of a site. Ultimately, the front-end developer is responsible for creating, testing and implementing the workings of all the visual and interactive elements of a website.

Check this for some understanding

Source : Life of a Front-End Web Developer [Infographic]

Is front-end development a dumb thing to learn?

American vision

How many (programming) languages does a coder really know?

Answer on @Quora by @ravisRealm to How many (programming) languages does a coder really know?

Answer by Raviteja Chirala:

I would say not to worry about how many languages you need to learn rather how analytical you should be.

I can share a valuable lesson I have learned from one of my ex-managers in my first year of professional world. He has been working in the same company for like 20+ years and as a manager for 15 years almost. At some point we were evaluating some framework(product) and I was asked to compare some of the algorithms they had to what we have. I was a little hesitant earlier because I had never really written anything in C++ after my school.

After wasting couple of days with that, I walked to my boss and told him that may be I can't do it because this language is out of my scope. He gave his usual traditional smile and told me,

"Once you're an Engineer, you're an engineer. And if you're an engineer you should be able to write in whatever language is required for the specific task. It takes some time to understand the syntax and specifications but logic should not change. I am sure you can do. Just do it"

I don't know if you interpreted it correctly the way I did but that has changed the way I see and the way I work. Even though he manage a huge chunk of products and multiple teams he still writes code. He fixes issues in backend, front end, computation and what not. I have never complained again. I did Java, R and I am doing Python now. It's what is required for my team and what's best for our product. I am basically an Engineer who writes code no matter what language. So my advise is learn any language of your interest and be more analytical in what you do.

PS : Thank you for all the upvotes and feedback guys.

How many (programming) languages does a coder really know?

American vision

What kind of programming language do we need in the future?

Answer by Robert Love:

We need a successor to C++ that provides a modern, safe, powerful language without the complexity of C++ or the overhead of Java. This successor needs to treat concurrency and parallel programming as first-class features of the language. The language must be designed to write the system software of the 21st century. Finally, the language needs to have modern sensibilities around memory management.

Sounds a lot like Go.

What kind of programming language do we need in the future?

American vision

Unarmed Jason Bourne and 007 get into a street brawl, who would win?

Answer by Cindy Womack:

Bond has one potential advantage.

Bond fan that I am, I know the winner on paper (or in the BondVerse MI6's incredible data crunching battle simulation super computer) is Bourne. However Bourne doesn't have whats Really kept Bond alive all these years…Dumb Luck!

How often is it the inability of 20 trained soldiers to shoot straight, of a henchman looking left instead of right, of some piece of equipment failing the villain, a random civilian merging into the high speed car chase, of a completely loyal hench or lover suddenly betraying the villian, etc etc that saves Bond?

In this scenario Bond holds up a bit longer than the average counter agent Bourne fights (probably by sucessfully dodging many of Bourne's moves as opposed to overpowering Bourne and by not following a 'typical' series of moves in a given fighting style), but soon hes on the ropes. Bourne is about to deliver the killing move by way of fist, foot, head…paper napkin, whatever. Or hes about to cripple Bond in an attempt to get him to talk. When suddenly the wind picks up and either…

Sean Connery:
A passing Bread truck ,swerving to avoid something rolling into the street, jumps the curb and as Bourne is now,oddly, incapable of doing more than holding his arms in front of his face is hit by the truck.

Roger Moore:
A bag of flour flies out the same Bread truck; bursting open it covers and blinds Bourne.  A couple poorly executed moves and Bourne is thrown off a convenient bridge/overpass or comically locked in a dumpster.

Timothy Dalton:
Whatever it is that defeats Bourne it'll be singularly uninteresting.

Pierce Brosnan:
It'll be a Porsche Bread Truck with recognizable brand name flour that nearly hits them both. As a crowd starts to gather Bourne takes the truck, Bond steals another name brand luxury car and a chase ensues. Bond forces Bourne into crashing the truck into an internationally recognizable restaurant chain.

Daniel Craig:
Somehow they both windup atop the Bread truck so the fight can go on another 20 minutes as the truck goes thru heavy trafic. Bond hates it as he thinks he's winning but M orders Q to take Bourne out with a miniature drone. Bond winds up sitting stop the truck with the dead or unconcious Bourne next to him.

In all these scenarios the next thing to happen:

M: (via wrist communicator or cel phone) Bond, who is it? Is this the American rogue agent? (Ya know Felix was asked about Bourne earlier in the move and totally lied about him,Treadstone etc ;)

Bond: An American? Yes, Bourne and Bread. (straightens tie, music sting)

Unarmed Jason Bourne and 007 get into a street brawl, who would win?

American vision

How do Go, Scala and Julia compare with each other?

Answer by Eric Talevich:

Go is a systems programming language. Google created it to safely solve three specific problems that C++ was biting them with: concurrency, memory management and compilation time on large systems. It's concise and readable, like Scala and Julia, but a bit fussy and low-level, unlike Julia. You would use it to write safe, well-performing services that your main application might call to. It would certainly be possible to write scientific software in Go, much as you would with C or C++, but it doesn't have the same flexibility and interactivity as, say, Python or Julia, or even Scala. If you're trying to use Go for data analysis, the fussiness and lack of interactivity will disappoint you.

Julia is a scientific applications programming language, designed to be a good replacement for Matlab and Python+SciPy. It's very new, so I won't attempt to predict which specific features it will or won't pick up, but the underlying motivations should drive it to be a very good programming language for scientific software — not syntactically optimized for statistical operations on data arrays like R, but good to write a computationally intensive program that uses multiple CPUs and generates pretty graphics.

Scala is a general-purpose language that sits between the other two, capable of dealing with either end of the spectrum. Twitter uses it for services. Scientists use it for aligning protein structures. It's a good language, a few years older than the other two, and is built on the JVM, which has its own pros and cons. If you want your code to be something other programmers can use and/or build on, Scala is your best choice at the moment — it creates .jar files which can be used directly from plain Java, whereas Go doesn't seem to be capable of creating reusable shared object (.so) files yet.

How do Go, Scala and Julia compare with each other?

American vision

What can a person with an IQ of 160 do that a person with an IQ of 100 cannot? Are certain things fundamentally unlearnable/undoable like…

Answer by Peter Flom:

There are no absolute rules with regard to human abilities and outcomes. But there are some tendencies.

People with very high IQs (e.g. 160) will generally have an easier time with academics; they will understand more in less time than others. They will make connections that others miss. 

Let's take Isaac Asimov, for example.  When he was 5 or so, he was waiting for his big sister at school.  He had one of those composition books that had the multiplication table in the back.  So…… he taught himself to multiply. That is, he figured out what the table was for, without being told.

Or there was a Harvard philosopher.  His parents said they knew he was not a typical kid when at age 4, he came into the kitchen and said

"Mommy, is God really everywhere?"
"Yes sweetie"
"Well, do I squeeze some of him out of the kitchen when I come in and take up his space?"

Or one kid who, in preschool, had already learned to read. So, he taught himself to read upside down so he could help the teacher by reading to the other kids with the book facing them.

I've known a few people with IQs of 160 or so.  They are interesting.

What can a person with an IQ of 160 do that a person with an IQ of 100 cannot? Are certain things fundamentally unlearnable/undoable like…

American vision

Why do most programmers prefer Macs?

Answer by Markus Nigrin:

Everybody has a story and my Windows vs Mac story might give you an answer.
I was a die-hard Windows user & coder. It makes a lot of sense writing code on the OS you write software for and Windows always was my primary target. Used a friends Mac for some graphic stuff at times, always disliked it. When I wanted to write stuff for iOS I took the easy path and bought my first Mac, reluctantly so. Also the first time for me using OS X 10.5. Took a few months and I madly fell in love with it.
Think of the Windows registry, BIOS settings, msconfig, etc. Complete waste of time and with each new PC and Windows version it felt I was doing more of it. Enter the Mac and this amazing OS.
The productivity that machine offered was eye-opening for me. It booted fast. It didn't get slower over time. It woke from sleep in a second. Apps didn't bog it down. No virus scanners being all egocentric with the machine's resources. And a great screen, key when you write software.
Apple got me when I was weak, in the most convincing way possible. Now true, things are changing, Apple making some questionable choices, MS getting better but that's not what you asked.
This is how I learned to love the Mac and still do. They are powerful, beautiful and overall they just work, which is what I need.

Why do most programmers prefer Macs?