Having PHP as my most useful skill.

I know various other languages, but they're either too exotic for professional use, or my knowledge about them doesn't have the same depth as with PHP.

People joke about how awful PHP is, and it's not entirely true. The incongruous stuff such as confusing parameter ordering can be fixed with libraries. And PHP7 fixed a lot of the ugly stuff. A good dev can certainly write structured, readable, performant PHP code.

But there is a real hard limit. PHP is missing more complex type definitions present in other languages. A weak type system is like building stuff with popsicle sticks and bits of duct tape, it works fast and perfectly fine for small projects, but the lack of strictness is a problem when you have thousands of classes intertwined in all kinds of complex factory, service and repository patterns. And the simple type hints are still newish and fully optional, which means a lot of people don't use them.

So I regret getting stuck in this self reinforcing loop, where I learn more about a very imperfect language through employment, and keep rolling into jobs using that skill because it's what I'm most experienced with.

Trust Me Devs,
In INDIA we use this to WASH DISHES in the Kitchen...

Currently getting into Machine Learning and working on a joke-project to identify the main programming language of GitHub repositories based on commit messages. For half of the commits, the language is predicted correctly out of 53 possible languages. Which is not too bad given the fact that I have no clue what I'm doing...

Programming Languages are Like Cars:

Assembler: A formula I race car. Very fast but difficult to drive and maintain.

FORTRAN II: A Model T Ford. Once it was the king of the road.

FORTRAN IV: A Model A Ford.

FORTRAN 77: a six-cylinder Ford Fairlane with standard transmission and no seat belts.

COBOL: A delivery van. It's bulky and ugly but it does the work.

BASIC: A second-hand Rambler with a rebuilt engine and patched upholstery. Your dad bought it for you to learn to drive. You'll ditch it as soon as you can afford a new one.

PL/I: A Cadillac convertible with automatic transmission, a two-tone paint job, white-wall tires, chrome exhaust pipes, and fuzzy dice hanging in the windshield.

C++: A black Firebird, the all macho car. Comes with optional seatbelt (lint) and optional fuzz buster (escape to assembler).

ALGOL 60: An Austin Mini. Boy that's a small car.

ALGOL 68: An Aston Martin. An impressive car but not just anyone can drive it.

Pascal: A Volkswagon Beetle. It's small but sturdy. Was once popular with intellectual types.

liSP: An electric car. It's simple but slow. Seat belts are not available.

PROLOG/LUCID: Prototype concept cars.

FORTH: A go-cart.

LOGO: A kiddie's replica of a Rolls Royce. Comes with a real engine and a working horn.

APL: A double-decker bus. It takes rows and columns of passengers to the same place all at the same time but it drives only in reverse and is instrumented in Greek.
Ada: An army-green Mercedes-Benz staff car. Power steering, power brakes, and automatic transmission are standard. No other colors or options are available. If it's good enough for generals, it's good enough for you.

Java: All-terrain very slow vehicle.

"Sad violin"

If programming languages were countries, which country would each language represent?

Disclaimer: its just a joke

Java: USA -- optimistic, powerful, likes to gloss over inconveniences.

C++: UK -- strong and exacting, but not so good at actually finishing things and tends to get overtaken by Java.

Python: The Netherlands. "Hey no problem, let'sh do it guysh!"

Ruby: France. Powerful, stylish and convinced of its own correctness, but somewhat ignored by everyone else.

Assembly language: India. Massive, deep, vitally important but full of problems.

Cobol: Russia. Once very powerful and written with managers in mind; but has ended up losing out.

SQL and PL/SQL: Germany. A solid, reliable workhorse of a language.

Javascript: Italy. Massively influential and loved by everyone, but breaks down easily.

Scala: Hungary. Technically pure and correct, but suffers from an unworkable obsession with grammar that will limit its future success.

C: Norway. Tough and dynamic, but not very exciting.

PHP: Brazil. A lot of beauty springs from it and it flaunts itself a lot, but it's secretly very conservative.

LISP: Iceland. Incredibly clever and well-organised, but icy and remote.

Perl: China. Able to do apparently almost anything, but rather inscrutable.

Swift: Japan. One minute it's nowhere, the next it's everywhere and your mobile phone relies on it.

C#: Switzerland. Beautiful and well thought-out, but expect to pay a lot if you want to get seriously involved.

R: Liechtenstein. Probably really amazing, especially if you're into big numbers, but no-one knows what it actually does.

Awk: North Korea. Stubbornly resists change, and its users appear to be unnaturally fond of it for reasons we can only speculate on.

“PHP is evil” is not just a joke.

PHP is usually percieved as a language which is not so consistent and has some opinionated historical aspects but allows rapid development because it’s easy. They say PHP doesn’t focus on that “purist shit” such as concepts and “just gets things done”.

Hovewer, this is not true. PHP lures you in and lies to you promising saving time on development, but everything, and I mean EVERYTHING written in PHP is doomed to turn into a bloody mess sooner or later.

You have to be an AI to manage the growing PHP codebase and add features without breaking anything. With every feature it gets harder and harder. If you’re still a human managing a human team, you have to enforce guidelines. Automatic error preventon measures are made of code themselves so the cost of deploying them ona late stage can be ridiculous. And you never deploy them on early stage because you want to “save time”. Your people have to spend more and more time everyday checking on that guidelines. Your development process only becomes slower and slower. If you try to push things, your project will crumble to dust.

To make PHP at least decent, you have to figure out all this by yourself on an early stage. When you’re done, you spent a lot of time creating the buggy, ad-hoc, unspecified and unsupported alternative of what works out of the box in other languages. And you still code in PHP and still have all its disadvantages in your project’s DNA.

PHP is evil because it promises and never delivers. PHP is evil because it lies to you and it already fucked over so many of us.

If you want to code in PHP, do it under your pillow. Code your own silly projects.

If your project has the word “production” somewhere in its plans, PHP is not the way to go.

Amen.

How come it is so hard to find good developers. Have been doing interviews for a couple of weeks now (for a senior PHP developer role).

First round is me talking about the function and company, asking questions about candidates experience, wishes and we usually end in some tech conversations. Most of the resumes I got are pretty fucking good. I mean, experience with low-level languages, experience with the problems we need to solve here, contributions to open-source, experience in R and MathLab etc etc. On paper they look perfect.

For the second round I give them an assessment which they can do at home on their own machine in their own time. It's not a hard one, just some mathmatical problems they need to solve. A quick google GIVES the answer (no joke!!). But that's OK, I look at their code cleanliness, proper use of commenting so I can determine if they are solo-developers or fit good in a team and if they abstract repeated functions and make sure that they take their work seriously, you know the drill.

It pisses me off that I get BROKEN FUCKING CODE WHICH DOES NOT EVEN RUN and that I get code back which I look at and makes me vomit instantly, I mean, DO YOU EVEN TAKE YOUR PROFESSION SERIOUS? How dare you to ask for 50k the year, a lease-car, extra bonusses AND YOUR FUCKING CODE SPITS OUT COMPLETLY WRONG ANSWERS OR DOES NOT EVEN RUN WHAT THE FUCK DUDE GO BACK TO FROM WHICH EVER HOLE YOU CRAWLED OUT AND STOP WASTING OTHER PEOPLES TIME WITH YOUR FUCKING INCOMPENTENCE...

I'm so done with flutter.

I wanted to give it a little try by rewriting a small android project I wrote a few years back. It brings some nice concepts especially when it comes to UI related programming but that's all I can really compliment it for. It's nothing more than something to play with as it is right now.

Also I think this text will be hidden behind the read more. Did I successfully bait you with that cat?

The things I truly hate about it:

The ide integration makes me wanna use eclipse again. At least most nonsensical error messages disappear after saving the document on eclipse.
.
Wanna generate a new function? Yeah, let me just place it RIGHT INSIDE THIS FUCKING IMPORT STATEMENT

Over at Google: Let's just rename everything from java slightly different and put it in nonsensical context so that you have to learn all of it again. Also why don't we make it so that the code suggestions only suggest things you already imported, so that you have to look up every little piece shit feature.

When it comes to databases, I must say, I had more fun working with PHP and mysql than with sqFUCKlite. Throwing away the Room components for that? What a joke...

I already said what i think about the syntax here an devrant but I'm more than happy to repeat it here:
The syntax looks like someone looked at C#, Java and JavaScript and then decided to vomit the worst parts of it into a programming language. I can't really classify anything original about it. There are clear inspirations, but they are confusingly mashed together with the other languages making this one nuts of a language.

Android SDK documentation is a blessing in comparison to whatever the fuck flutter tries to do.

I don't think I'll want top touch that Google side project again within the next few years, if it hasn't been replaced with a new side project like billiard by then.

This happen to me once when I was a young kid walking home from school.

There were two other guys with me, older than me. They were talking to each other about programming languages. I have been programming from a very young age so I knew a lot about programming and I knew a few languages back then, but they were taking about Java, a language which I wasn't into yet back then, so I just listened for a while to what they had to say.

The first guy told the other, "You know I'm great at Java." The other guy responded "I can do anything in Java." Then I said as a joke "Oh, can you do hello world?". The guy said "Hello what? What do you mean?" The other guy said. "Is that a retro game?" I just laughed. Then I told them to go learn how to output text in Java.

A bit of current history about these guys:
The first now works in C# for a quiz test company, he never learned Java or languages other than C#. The second one owns and works at a scrapyard. They are both great guys, but they like to brag.

No wonder I'm having troubles finding a date

I was a foreign language student, but i didn't like the way my work-life was going (I had a lot of difficulties tryng to find a job).

So I decided to start programming... It appears i'm still studying "languages".

Is my life a joke?

I found this on internet and this is funny 😂 html

bruuuuuuuuuh I got an email asking for tech LatinX people to join for a talk on our problems facing x shit in tech.

As a Mexican American (I am more American than Mexican, but whatever) and your standard gun tootin Texan: fuck you, do not call me LatinX

I know both English and Spanish (and other languages that won't disclose here because fk u) well and believe that adding such buuuuuuuullshit to my beautiful Spanish is utter nonsense.

I sent it to the network admin and ask him to block them fuckers from ever sending emails my way ever again as spam.

LatinX....what a fucking joke

this is a repost organization post. each time you are going to post a classical joke, please find it from items below, and write as comment, the number of the repost. and people will give you ++'s to your comments as if you actually reposted the post. also, feel free to make additions to the list. syntax is:

"(n): [repost context]" for a new item (please do not mess with the order)

"-- [n]: [personal comment]" for simulating the repost.

here we go:

(0): the comic strip about rescuing princesses in different languages.

(1): in case of fire git commit, git push, leave the building.

(2): wanna hear a udp joke? i don't care if you get it.

(3): that joke about java devs wearing glasses because they can't c#.

--------------

An example repost:

-- 0: omg princess lol :)))

That feeling when you're applying for your first programming job.

And the knife stabs of nerves in your gut fearfully remind the coiled muscles in your sweaty brow of the singular possibility: what if I bullshit my way by the HR filter into this job and it turns out I was completely wrong, and I encounter a bug that my meager coding abilities really can't fix?

"Writing an interpreter in some community college you dropped out of ten years ago" doesn't mean you're a programmer.

"Figuring out where the bug was in a broken bat file that was pages long, for a language and framework you've never used, for a library nobody uses anymore", doesn't count as debugging.

"Writing a tweening library in an obscure tool" doesn't mean you're an expert. This is childs play.

What if they ask about big O? Do you admit that logarithms confuse the fuck out of you because you dropped out in 8th grade and got your GED later on due to being kicked out by your meth head dad?

What if being able to write a few measly cobbled together half-arsed estimate tools in python doesn't really mean you're qualified to do anything?

What if being able to look at code in languages you've never seen and grok it doesn't mean shit?

What if you've used more languages than you can remember?

What if you once lost a job offer casually given because the guy you built rapport with over months made a joke about browsers, and you joked about using internet explorer?

What if you got a job offer from a consultant friend one time and he asked you to write validation and testing code in javascript for amazon's cloud, and you completely screwed the pooch because you spent the entire time thinking you had to make it *work* and not just *look* correct, when all along he just wanted what amounted to *correct looking* code, and your gut had told you the same, but you ignored it, because the world can't possibly work like that, where people give anyone a chance or the benefit of the doubt, and any slip up or shortcoming means you were never really worthy to begin with.

What if you thought you could, but you'd been raised your entire life to *believe* you couldn't?

Me: "I want to learn a new language."
Other person: "I didn't C that coming".
Me: "LOL".