CS student suggests Dropbox over Git, triggering version control collective eye roll

Description

Screenshot of a dark-theme tweet UI. At top left is a blurred profile photo followed by the name “Shubhangi✨” in bold white text and the handle “@heyShubhi · 17h” in gray. The tweet body, in white sans-serif font, reads: “"Why are people using Git? It's too complicated. Dropbox can do the same kind of things." - A fellow CS student at university”. Below, standard Twitter interaction icons show 340 replies, 258 retweets, 3,499 likes, and a share symbol. The humor comes from a computer-science student conflating Git’s distributed version-control features (branching, merges, history) with basic file-sync tools like Dropbox, highlighting common beginner misconceptions and the steep learning curve of proper version control in professional software engineering

Common Tags

Git VersionControl DeveloperHumor RelatableDevExperience LearningCurve JuniorVsSenior

Comments

Anonymous ★ Top Pick “Dropbox can replace Git” - perfect, if your branching strategy is “new folder,” your merge algorithm is “overwrite whatever’s there,” and “git rebase --interactive” is renamed to “v2-final-FINAL-no-seriously.zip.”

Anonymous ★ Top Pick

“Dropbox can replace Git” - perfect, if your branching strategy is “new folder,” your merge algorithm is “overwrite whatever’s there,” and “git rebase --interactive” is renamed to “v2-final-FINAL-no-seriously.zip.”
Anonymous

Wait until they discover you can resolve merge conflicts by just keeping both versions and naming them final_final_v2_ACTUALLY_FINAL_USE_THIS_ONE.docx
Anonymous

Ah yes, Dropbox - the perfect tool for when you want to experience merge conflicts without any of the tools to resolve them, lose your entire commit history, and turn 'git blame' into a literal treasure hunt through 47 versions of 'final_FINAL_v2_actually_final.py'. Nothing says 'enterprise-ready collaborative development' quite like racing your teammates to see who can overwrite whose changes first
Anonymous

Dropbox branching strategy: folders named 'final_v2' and 'johns_final' - merge conflicts via folder roulette
Anonymous

Dropbox can replace Git - if your branching model is “Project copy (3)”, your merge strategy is last-writer-wins, and your rollback procedure is Slack archaeology
Anonymous

Using Dropbox as Git is like using S3 as a queue - fine until your branching strategy devolves to last‑writer‑wins and your audit log is the recycle bin
@paul_thunder 3y

Not hired - Not fired.
@beenotung 3y

Similar for micro-frontend, depends on team size Complex tool is only beneficial for complex use case
1. @dsmagikswsa 3y
  
  I think those microFE or microService is solving collaboration problem more than technical problem.
@ZgGPuo8dZef58K6hxxGVj3Z2 3y

She got me in the first part. But when she said “it can do the same things” I laughed
1. @pixelsex 3y
  
  my mouth did the "haha" thingie
  
  @ZgGPuo8dZef58K6hxxGVj3Z2 3y
  
  😂😂💀
@deerspangle 3y

A new challenger enters the ring: https://engineering.fb.com/2022/11/15/open-source/sapling-source-control-scalable/
@deerspangle 3y

(to clarify, I'm not sure I'm a fan of sapling. Seems odd)
@deerspangle 3y

It does a lot of different stuff, like the history of each commit is an interesting one. The different log view and the undo both seem like they could be slapped atop git, but each commit having its own history is weird
@deerspangle 3y

And the scalability ofc
@FunnyGuyU 3y

You simply mail project_source_final_final02.zip to yourself.