I don’t do PHP. But I used other JetBrains tools for Go, Python and Java and they are very helpful. The AI Assistant is pretty good for explaining code. I am not in anyway paid by them. Good Luck
Here’s hoping you have Docker installed, because Laradock rules. (It’s not just for Laravel.)
If the project is a Laravel project, Laravel Herd just came out. If you’re on a Mac, there’s also Valet. If you prefer a VM, there’s Homestead - a PHP Vagrant config.
You’d probably get more feedback if you posted a proposed solution (or “correct answer”) to StackOverflow and let the community tell you how dumb you are in between generating exactly what you are looking for.
Real answer: consider passing Markdown through instead. You’re getting really close to one of my favorite memes. It’s a dark path, don’t tread down it.
“Master” is a strong word, but when I have to build applications it’s PHP in the back and JS up front. Specifically, Laravel implementations with whatever on top.
I’m extremely proficient with templating languages that eventually turn into HTML (nunjucks, antlers, blade, handlebars, webc, vue) and CSS (SCSS, LESS). A ton of my work winds up being on Static Site Generators and the unholy abomination that is at-scale Email development.
Hey, I’ve came over from Reddit and thought I’ll introduce myself as well. As every programmer, I’ve started way too many pet projects and almost all of them are starving. In terms of framework, I prefer Yii2 over Laravel every day. I feel like Laravel provides you a dozen different (seemingly equally good) ways of doing something. You could say it’s lacking clarity or guidance for the developer.
Hey, welcome! Classic haha, I have far too many pet projects as well 😅
And yeah agreed, it’s a bit dizzying to choose a Laravel “path”. Would probably be helpful to have a documentation page sort of like the Remix Stacks where they talk a little bit about which “path” to choose depending on app needs.
Docs is another topic I really don’t like about Laravel. Why don’t you have a simple API doc with available functions and their parameters instead of that blog-style documentation. And no, I don’t want to watch a video about how to use X, I want to know what functions I can call. Oh and don’t get me started on all their global “helper” functions.
Mainly because you’ve got to setup PHP to be debuggable in the first place.
And setting up PHP is already a hassle. When a dev has to set up php in about 5 separate ways just to figure out which one is actually debuggable, then PHP has a problem.
No Data Checking: It directly uses data from an API without checking if it’s safe or correct.
Dynamic Properties: Adding properties to an object on the fly can make the code hard to manage.
External Data Dependency: Relying on API data structure without checks can lead to issues if the API changes.
If you don’t know the data is safe (it’s not), it’s a lot better to use an associative array. Additionally, if it’s from a json, it’s quicker and easier to iterate over array. Don’t make it complicated for no reason.
php
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.