8 comments

1

We are working AGILE now, everyone must know everyone's code so picking a language is not important. Just learn 10% of any language and off you go.

1

This is how I choose the language for a project:

First, I choose Common Lisp.

EDIT: There is no excuse to use the gibbon abortion of PHP for anything ever. Especially not in 2017.

1

this is an underrated comment. The difference is not all of us are masochistic enough to desire that our eyes bleed continuously from parenthesis. PHP: What is love? Baby don't hurt me no more.

If PHP is an abortion (and it is), and you're a programmer, sometimes you just have to get the job done and become an abortion doctor. The clinic is open for business.

1

If PHP is an abortion (and it is), and you're a programmer, sometimes you just have to get the job done and become an abortion doctor.

I agree to a lot of what you've said, but there are python frameworks (for example) which make anything you'd do in PHP a breeze, or use something like Hunchentoot / CL-WHO for Lisp which not only makes it quick and easy but also a joy to program.

You're right though, sometimes you've got to hold your nose and jump into the cesspool (as I did a couple of months back writing a VB.net project).

1

VB.net jesus christ man. Don't come near me I don't want to catch anything.

0

It's not my fault, man, the rest of the team chose the language much to my horror.

Can you imagine the anguish it caused to a Lisp programmer like me? Every compile was like being licked by an old hobo.

Thank the gods it wasn't Java though.

1

Step 1. Determine what you're trying to solve

Step 2. Don't reinvent the wheel. Use what works and gets the job done. Nothing else matters.

Step 3. That was all the steps. There are no more steps.

Hammer->Nail

0

Is C++ dead then?