Why is there only one menu item with a label? Shouldn't they all have one for consistency?

😂 that's why we have BDD

Right.

Our style guides tend to dictate the braces on a new line for classes and methods but for control blocks we use one space after parentheses.

Passed 😁

Will need to look into that, sounds good. At present I have time machine running to an external drive. It quickly becomes full so I end up deleting old backups.

The deleting process can take forever sometimes so when I don't have time I disable time machine to stop the notifications. That's why my last backup was a month old. (Busy month 😂)

@orion-ix yeah I had time machine although s month old. It was good enough to get back the important files.

I was in a project folder running a custom Symfony console command. While debugging I had a print_r then an exit. For some strange reason when the script exited it threw me into the home directory.

The script creates files in the project folder so each run needs to flush it out first. Not cool running it after you realise you are in home :(

One of my pet hates. Absolutely hate this view on performance.

[1,2] for sure. It's not technically shorthand, just an upgrade in the syntax since let's be fair, it's not that much shorter than array(1,2) 😂

I would advice though not to mix in the same file since it can get messy and confusing for future maintainers.

I had the exact same issue. Had to investigate a bug after a major feature was release. Having no knowledgeable the feature or the system it gave me the chance to dive in deep.

The bug I found had been there since the systems conception, around 4 years. It only surfaces with the new feature. Nightmare few days with that.

Approx 1900 branches, 200 active PRs it's a big site! 😂

Inline comments are known to be an anti pattern (when misused). If you need to comment your code to explain what's going on then you should probably refactor. #SOLID

I am also with @dfox on that there is cases where they are required. Especially if there is a line of code that fixes a critical bug. The change might be seen from GIT log but an unknown maintainer might not crawl the file GIT history before updating.

In these edge cases the comment should point to external docs or changelog.

I usually find I get most or my work via my website and LinkedIn. LinkedIn for local people looking for a particular skill and the website is generally everything.

The key to being successful in freelance is word of mouth and marketing. You need to market yourself in the right area. Be specific about your skills. Just because you *can* use photoshop doesn't mean you should list it. Don't list too many skills, it can look desperate and spammy. Focus on the ones that matter most.

😩 not an ideal situation to be in. Let them learn the hard way when they try to upgrade the legacy system with no knowledge of what anything does 😂

Classes and methods should be documented to explain their requirements like input and return values. But commenting code inside a method is known as an anti pattern.

If the method is so big that you need to comment throughout what it does then this is usually a sign your method or class is doing too much. Time to refactor and separate out the logic into easier to manage chunks. #SOLID

Accurate 😂

This is the reason we call it code review. They should review and suggest. Not actually add the code!

Devs should only be coached and mentored through peer reviews. Being told why something is done a certain way encourages learning and strengthen the skills and abilities of the developer submitting the PR.

I only learned what this was the other day. Strangely feel normal now. For the record I do suffer from this! 😁

How do I get one of those stress balls? Looks awesome 😁

The perfect location 😁