Skip to content
loading...

re: Some thoughts on the labels we attach to ourselves VIEW POST

FULL DISCUSSION
 

I'm a seniorish PHP developer myself, and I'd have to say I generally agree.

Though I basically did a single Angular project and I now bill myself as an Angular developer with 7 years Experience. PHP in general ( though Laravel is an incredible framework, and it's still my favorite hands down ) , is kind of a poor language from an architectural standpoint. Blocking IO and the fact that old PHP projects turn into spaghetti because of it's loose typing means it's not a top pick for alot of companies.

So I take a bit of the middle ground here. The Labels are somewhat inaccurate and can often obscure greatness, but they aren't totally useless because they do provide a useful short hand to HR people who don't know anything about software engineering and who don't understand how transferable most of this stuff is for a competent developer. I'm up to like 6 languages at this point and I'm just collecting them like pokemon, but that can be hard to get across.

Though on the upside, re-branding yourself as any kind of developer is quite easy so long as you can prove you can build something in language x or framework y. Also 80% of our job is being able to learn, so it helps to avoid thinking of yourself as x type developer. Your just a developer. The language is fundamentally immaterial if your any good.

 

Yeah, legacy PHP can be a pain. We gained a lot with strict types. And the PHP project itself has gained huge traction lately. Also, I read a bit on the P++ initiative, and I salute it. State of PHP is a lot better. And when I say I worked with complex data models, that's not an exaggeration. We're talking thousands of objects handled gracefully and above all, fast.

That being said, I'm generally not looking to rebrand myself, but... I don't think that should be that difficult as it is.

 

Yeah that's really funny to, because I'm actually less interested in Strict Types , ( I prefer optional typing, because sometimes type errors are a huge pain in the dick and can create lots of unnecessary boiler plate ).

Untyped Laravel Code but using explicit imports is more than enough for fantastic idiomatic code. It's actually better because your controllers can be super thin and lightweight. You can build API's lightning quick because your not wrestling with compilers, preproccesors, and linters written by sadists.

Let data be data I say, you have to validate it anyways.

But the market for PHP just isn't there - so I doubt I'll ever go back unless someone offered me a butt-load of money to compensate me for lost future revenue for having the wrong technology on my resume.

Oh, I wouldn't go so far to say there's no market for PHP. As I said, it's making great strides. And I do think it's gonna be with us for a very long time.

code of conduct - report abuse