Dariusz

[Dariusz @darek1024]

@Socjalizator świetne fotki!

[Dariusz @darek1024]

@Kingzztons @JkmMikke @PiotrBezGranic musisz nagrać ☝️

[Dariusz @darek1024]

@Porzuc_ Potwierdzam. W zeszłym roku praktycznie od zera przygotowałem się z Runna do półmaratonu. Bardzo miło wspominam korzystanie

[Dariusz @darek1024]

@Ravcio55 @sniperlowcap Jak wgrales takie ladne mapy?

[Dariusz @darek1024]

@FinansowyUmysl Można dostać dostęp do tej apki?

[Dariusz @darek1024]

@ReadwiseReader Can you let Youtube video to expand horizontally, not only vertically please?

[Dariusz @darek1024]

@_onlyscott Sergio Ramos :)

[Dariusz @darek1024]

@ArturJanczak @nieantyfan Dlaczego nie 16 Pro?

[Dariusz @darek1024]

Around 90% of Claude Code is written with Claude Code

[Ben Dicken @BenjDicken]

1 of N reasons why sharding is a great way to scale a database?

Backup speed.

This is one of the fun little animations I worked on in my recent interactive sharding article. In case you missed it, link below.

[Dr Milan Milanović @milan_milanovic]

𝗚𝗶𝘁 𝗠𝗲𝗿𝗴𝗲 𝘃𝘀 𝗥𝗲𝗯𝗮𝘀𝗲

One of the most powerful Git features is branching. Yet, while working with it, we must integrate changes from one branch into another, and the way to do this can be different.

We have two ways to do it:

𝟭. 𝗠𝗲𝗿𝗴𝗲

When you merge Branch A into Branch B (with 𝚐𝚒𝚝 𝚖𝚎𝚛𝚐𝚎), Git creates a new merge commit. This commit has two parents, one from each branch, symbolizing the confluence of histories. It's a non-destructive operation that preserves the exact history of your project. Merges are particularly useful in collaborative environments where maintaining the integrity and chronological order of changes is essential. Yet, merge commits can clutter the history, making it harder to follow specific lines of development.

𝟮. 𝗥𝗲𝗯𝗮𝘀𝗲

When you rebase Branch A onto Branch B (with 𝚐𝚒𝚝 𝚛𝚎𝚋𝚊𝚜𝚎), you're essentially saying, "Let's pretend these changes from Branch A were made on top of the latest changes in Branch B." Rebase rewrites the project history by creating new commits for each commit in the original branch. This results in a much cleaner, straight-line history. Yet, it could be problematic if multiple people work on the same branch, as rebasing rewrites history, which can be challenging if others have pulled or pushed the original branch.

So, when to use them:

🔹 𝗨𝘀𝗲 𝗺𝗲𝗿𝗴𝗶𝗻𝗴 𝘁𝗼 𝗽𝗿𝗲𝘀𝗲𝗿𝘃𝗲 𝘁𝗵𝗲 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗲 𝗵𝗶𝘀𝘁𝗼𝗿𝘆, especially on shared branches or for collaborative work. It's ideal for feature branches to merge into a main or develop branch.

🔸 𝗨𝘀𝗲 𝗿𝗲𝗯𝗮𝘀𝗶𝗻𝗴 𝗳𝗼𝗿 𝗽𝗲𝗿𝘀𝗼𝗻𝗮𝗹 𝗯𝗿𝗮𝗻𝗰𝗵𝗲𝘀 or when you want a clean, linear history for easier tracking of changes. Remember to rebase locally and avoid pushing rebased branches to shared repositories. Also, be aware 𝗻𝗼𝘁 𝘁𝗼 𝗿𝗲𝗯𝗮𝘀𝗲 𝗽𝘂𝗯𝗹𝗶𝗰 𝗵𝗶𝘀𝘁𝗼𝗿𝘆. If your branch is shared with others, rebasing can rewrite history in a way that is disruptive and confusing to your collaborators.

👉 I 𝗽𝗿𝗲𝗳𝗲𝗿 𝘁𝗵𝗲 𝗿𝗲𝗯𝗮𝘀𝗲 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵, as we get a cleaner Git history, but to use it requires a higher level of Git understanding to manage safely.

#programming #coding

[Dariusz @darek1024]

@Marcinek135 @Dziennikarz_MK @FksStalMielec @RTS_Widzew_Lodz @gikiewicz33 Hotel Atena