Patrik Ahlström

@MrPunyapal One way around that is to use computed columns. That way you can index that column and get away with filtering on the year alone. Like always it depends on the need.

Laravel performance tip: Be careful with `whereDate()` on large tables. It looks clean, but it can make your database apply a function to the column, which may stop the index from being used properly. For bigger tables, prefer a range query. Small change. Big difference at scale.

@patilvishi Select your gift from the basket. From the basket select your gift. I think the ”natural” flow is how you structure a sentence in you native language. For example in german the verb is the last word in the sentence. Your gift from the basket select.

Interviewer: Why does SQL start with SELECT instead of FROM? SELECT name FROM users; Wouldn't this be more natural? FROM users SELECT name; 99% of developers write SQL every day but never think about it...

@Akintola_steve I wrote a post on that for Laravel a few years back. tray2.se/posts/use-a-vi…

@Akintola_steve It depends, but I think of ORMs as a way to make the code more readable, and complex queries makes a mess regardless if you use ORM och plain SQL. In such cases I use views, and then I can keep the ORM simple and readable, and tuck the SQL into a migration

Raw dogging plain SQL queries directly inside your backend service vs using ORMs, what’s your take? Speaking strictly from a performance and speed perspective, which approach do you prefer and why? Do ORMs introduce unnecessary overhead, or does the maintainability, abstraction, and developer experience they provide outweigh the performance difference? I’m curious to hear how engineers approach this in real-world production systems.

@ImLunaHey It's a skill to de-technicalize complex things, and it takes a lot of patience to learn it.

you can really tell when someone's a jr dev when they have no idea how to talk to someone that's at a different skill level than they are.

@krunalbuilds Depends on the application, but I would likely do a hybrid. Step 1. Inactivate the user. Step 2. Delete the user after x days.

Senior Backend Interview Question: Two engineers delete a user from the database. Engineer A 👇 DELETE FROM users WHERE id = 1; Engineer B 👇 UPDATE users SET deleted_at = NOW() WHERE id = 1; Engineer A's user is gone forever. Engineer B's user is hidden but recoverable. A week later, a user emails saying they deleted their account by mistake. Engineer A is having a very bad day. Which one would you approve — and why?

@simonhamp @aarondfrancis One of my favorite comedies, love when they drive on the railroad track, and then orders flapjacks.

@aarondfrancis Groundhog Day was the one that kicked it all off for me

What's a good loop for someone just getting into loops

@marcelpociot I wish

Is anyone else going to Rock am Ring this weekend so we can turn it into Laravel am Ring? 🤘

@SumitM_X No. Sooner or later your db will be slow due to too much data in the tables.

Tech Lead tells you: "Never delete data, just add is_deleted = true for all tables." Will you agree?

@marcelpociot @asumikam @kotomin_m That is awesome. If you haven't seen Gojira yet, I highly recommend it.

@tray2_se @asumikam @kotomin_m Yeah, same! They did an "Evening with Machine Head" tour where they played an almost 3 hour set 🔥

Thanks for this awesome photo @asumikam and @kotomin_m 🥷🥷🥷

@javarevisited Nothing really, other that the formatting and the readability, and IN(1, 2, 3) would have been easier to read.

Interviewer: What’s the issue with this? SELECT * FROM orders WHERE id = 1 OR id = 2 OR id = 3;

@SumitM_X That is called a hacker's wet dream.

Tech Lead said : "password is base64 encoded.... its as safe as a turtle in its shell" Do you also feel its safe ?

@neerajjj6785 Json should almost never be used inside the database. The only reason I see valid for storing it there, is when you receive a big payload from an API and you process it with a schedule job, rather them at once.

Interviewer: If PostgreSQL supports JSON, why would anyone choose a NoSQL database?

@javarevisited Mute the CEO.

Interviewer: Your authentication service is down. Nobody can log in. CEO is messaging every 2 minutes. What do you do first?

@EOEboh Nope, binary data does not belong in the db, it belongs on the file system.

As a developer, have you ever asked: Why does every major app store images in S3 instead of a database?

@MrPunyapal I can not agree more.

Saying it again: Javascript is not for backend

@Umesh__digital If you have one key in your pocket, it's fast to get it, if you have 100 keys in your pocket, how long does take to get the correct key?

Interviewer: If cache is faster than DB, why not store everything in cache? 🤔

@christophrumpel The UX of many form inputs is really bad.

Every time I use number inputs, I wonder if I would be better off without a text one. The "Up/Down" buttons are super small, hard to click, increase way too fast and need extra space in the input. Am I the only one?

@ashoKumar89 Regular integers, faster and takes less space.

UUIDv4 vs UUIDv7 What would you pick for a new system?