I kinda hate to admit it but they were right. Data structures and algorithms are kinda the shit and you should try to learn and appreciate them. Not just so you’ll use them. But in that learning them helps you become a better problem solver.

There’s a self taught dev that my company works with for really bespoke applications. A senior dev that works with him and helps manage the development process told me that the dev in question doesn’t really know how to implement the finer details. Very telling indeed.

I hate CORS

Excuse me what the fuck? I deny your access to collect my data and you won't show me any content? Fine. Time to leave your shitty site then

Is it true, that DevRant uses the https://slimframework.com Slim PHP Framework?

Thank you PHP manual! I would never found it otherwise!

I am working on another developer's PHP code, and I found a new way that he done the redirect after the login with PHP!

Fuck you react native and your stupid memory leak on dev machine! You are even worse than chrome 🤦🏼‍♂️

Sick of fucking working with 'engineers' who cannot see that the piece of shit application that they have written is not 'done' until it has been tested. No it is not production fucking ready you fucking yes man.

FK_MySqlWhyTheFuckIs_TheMaxCharLengthOfForeginKeys_Only64YouCun

If you're going to add a fucking CAPTCHA to your already poorly-designed website, MAKE SURE IT FUCKING WORKS YOU FUCKING IDIOTS.

Laravel is the worst framework ever.

Everything has to be made convenient and easy. That sounds amazing, because developers want to save time, worry less about boilerplate code, right? No more constructors, no more dependency injection, fuck all the tedious OOP shit... RIGHT?

It does one thing well: Make PHP syntax uniform and concise through easily integrated libraries such as Collection and Carbon. But those are actually not really part of the framework... just commonly integrated and associated with Laravel.

The framework itself is completely derailed: You can define code in a callback in the routes file. You can define a controller in the routes file. You can define middleware as a parameter to the route, as a fluent method to the route, you can stack them up in a service provider. Validators can be made in controllers, Request objects, service providers, etc. You can send mail inline, through Mailable objects, through Notification objects, etc.

Everything is macroable, injectable, and definable in a million different places. Ultimate freedom!

Guess what happens when you give 50 developers of various seniority a swiss army knife?

One hammers in a screw with a nail file, the other clips the head from the screw using scissors, and you end up with an unworkable mess and blunt tools.

And don't get me started about Eloquent, the Active Record ORM. It's cute for the simple blog/article/author/comment queries, but starts choking when you want more selective and performant queries or more complex aggregates, and provides such an opaque apple-esque interface which lets people think everything is OK, when in reality it's forcing the SQL server to slowly commit suicide.

So I finally tried Laravel... And fuck this shit, I'm going back to PHP...