Abandoning Modern Practices for FTP-based Chaos
Description
The image is a screenshot of a tweet from a user named 'terminally onλine engineer' (@tekbog). The tweet's text reads: 'We Abandoned Version Control and Saved Hundreds of Engineering Hours a Month. In the post below I will explain how you can directly deploy your code using FTP. No typescript, no cloud, no version control.' Below the text is a black-and-white, intense, and serious-looking headshot of a man, often associated with the 'Gigachad' or sigma male meme formats. The profile picture of the tweeter is a character from Dragon Ball Z, Vegeta, in a pink shirt that says 'BADMAN'. The humor is deeply satirical, targeting experienced developers who understand the absurdity of the proposal. It mocks the contrarian and often toxic 'hustle culture' mindset that sometimes appears in tech communities, where fundamental best practices like version control are questioned in the name of speed or simplicity. Deploying code via FTP is an outdated and error-prone method that modern CI/CD pipelines were designed to replace. The combination of the ridiculously bad advice with the hyper-masculine, serious photo creates a potent ironic statement about performative 'thought leadership' in the tech industry
Comments
12Comment deleted
This is the 'move fast and break things' strategy, except you skip the 'move fast' part and go straight to 'everything is broken and nobody knows whose FTP upload did it'
We swapped Git for FTP - now every deploy is a force-push to /var/www, rollback means dragging yesterday’s zip file back, and the incident review is our only commit history
Nothing says 'senior architect' quite like explaining to the board why the entire production codebase exists only on Dave's laptop after he rage-quit, but hey, at least we saved those precious seconds not typing 'git push'
Ah yes, the classic 'move fast and break things' taken to its logical extreme: move so fast you skip Git entirely and FTP directly to production. Nothing says 'saved hundreds of engineering hours' quite like spending those same hours frantically trying to remember which version of index.php you uploaded last Tuesday at 3 AM, or explaining to the CTO why there's no rollback strategy when the site goes down. It's the engineering equivalent of removing all the safety equipment from a factory floor and celebrating the 'efficiency gains' from not having to maintain fire extinguishers
Replaced Git with FTP: branching strategy is “prod,” code review is “last write wins,” audit trail is ls -ltr, and rollback is whatever final_final_backup.zip you can find
Hours saved on setup: 10. Hours untangling FTP timestamp conflicts in prod: eternity
Replacing Git with FTP turns change control into archaeology; the RPO is whoever still has yesterday's desktop.zip
We abandoned coding and saved everyone hundreds of hours every month. No code, no stress, no screaming. Comment deleted
Good luck 🍀 Comment deleted
where iknow this face from Comment deleted
https://en.wikipedia.org/wiki/David_Heinemeier_Hansson Comment deleted
But that is true Comment deleted