@black-kite to answer your question, it depends. Squashing also contains all hashes and commit messages that were squashed, if done right. So to comply with this idiotic check, you would just ask the company to check the number of hashes in this squashed commit.

@black-kite monitoring the amount of commits a developer makes is roughly the same as counting code lines as a performance metric.
It's stupid and in no way an indication of what the developer truly did, his thought process, etc.
Like the age old joke:
An engineer comes to fix a machine, replaces a screw and bills high. The manager asks for a breakdown and gets the following:
Replacing the screw:5$
Knowing which screw to replace: 1000$

Just like they bought github and everyone thought it was the end of open source?

Working on Sundays 😅

@Noook we're not working on Fridays, so yea, you can say that

Your first project will forever be your worst. By definition. The most important thing is to learn from it - and seems like you did, a lot - and take it to the next level for next time.
That's how companies roll. Try to upsell the technical debt as much as you can. Maybe they'll allow you 5-10% of each sprint for it.

@Nihil75 technically, yes. But the unitests pinpointed the actual bug. It took me a long time to understand why I was getting so many dupes.

Should have pointed out that I knew how to solve the problem (by doing type comparison as well ===) but it took me a while to reach this line...

@Jumpshot44 just some agricultural data, not real time alerts

rubberduck debugging FTW, now with cats!

@robert-cox laravel is great, but when it comes down to performance the ORM slows things down DB-wise. I prefer usong raw SQL for the heavy stuff