Updates and recent posts about git..

Posts
Description

Activity

@adrian_schmidt started using tool Amazon SES , 1 day, 17 hours ago.

Activity

@adrian_schmidt started using tool Amazon S3 , 1 day, 17 hours ago.

Activity

@adrian_schmidt started using tool Amazon EC2 , 1 day, 17 hours ago.

Activity

@adrian_schmidt started using tool Amazon Cloudfront , 1 day, 17 hours ago.

Activity

@adrian_schmidt started using tool Amazon ALB , 1 day, 17 hours ago.

Story

@laura_garcia shared a post, 1 day, 18 hours ago

Software Developer, RELIANOID

𝗕𝗲𝘁𝘁 𝗕𝗿𝗮𝘀𝗶𝗹 𝟮𝟬𝟮𝟲

📍 São Paulo, Brazil 📅 May 5–8, 2026 𝗥𝗘𝗟𝗜𝗔𝗡𝗢𝗜𝗗 is heading to 𝗕𝗲𝘁𝘁 𝗕𝗿𝗮𝘀𝗶𝗹 𝟮𝟬𝟮𝟲 — 𝘵𝘩𝘦 𝘭𝘢𝘳𝘨𝘦𝘴𝘵 𝘌𝘥𝘛𝘦𝘤𝘩 𝘦𝘷𝘦𝘯𝘵 𝘪𝘯 𝘓𝘢𝘵𝘪𝘯 𝘈𝘮𝘦𝘳𝘪𝘤𝘢. 🚀 46,000+ professionals 💡 270+ companies 🌍 One shared goal: transforming education Let’s talk about secure, scalable, and high-performance digital learning. 👉 See you at Expo Cen..

Link

@koukibadr shared a link, 1 day, 18 hours ago

Mobile Developer, Nventive

LiveData vs StateFlow

LiveData and StateFlow both stream data reactively, but differ in two key ways:

Initialization — LiveData needs no initial value; StateFlow requires one.

Lifecycle — LiveData is lifecycle-aware by default; StateFlow is not, so you need to wrap it in repeatOnLifecycle to avoid memory leaks.

Story

@pramod_kumar_0820 shared a post, 1 day, 22 hours ago

Software Engineer, Teknospire

How To Crack Senior Java Interviews (6–10 YOE) In 4 Weeks

#system-... #Intervi... #spring ... #java #Microse...

A practical 4-week roadmap to crack Senior Java Developer interviews (6–10 YOE), covering Core Java, Spring Boot internals, Microservices, System Design, and real-world interview strategies.

Senior Java Interviews (6–10 YOE) In 4 Weeks

Activity

@smh started using tool TypeScript , 1 day, 23 hours ago.

Activity

@smh started using tool Terraform , 1 day, 23 hours ago.

At its core, Git records snapshots of state, not just file diffs. Every commit represents a complete, immutable view of the project at a point in time, identified by a cryptographic hash. This makes history reliable, auditable, and cheap to branch.

Git is distributed by design. Every clone contains the full repository history, which allows developers and automation systems to work offline, create branches freely, and synchronize changes without relying on a central server for every operation.

In modern cloud-native workflows, Git acts as the source of truth. Desired state is declared in Git, reviewed through pull requests, and promoted across environments by merging changes rather than applying ad-hoc commands. This is the foundation of GitOps.

Git does not deploy anything by itself. Its role is to capture intent, history, and collaboration, while other tools turn that intent into running systems.