6 ms·
this is broken too!
by mattwad 1y ago
this is broken too!
- escapecharacter 1y agoThey must mean their local main branch.
- RonanSoleste 1y agoNo the remote one. No need for a local branch.
- mmastrac 1y agoGood thing we're using a shared Samba drive and editing files directly without locks!
- SparkyMcUnicorn 1y agoProject_v2_final3 is looking good, but remember to grab the new actionscript files out of Project_v2_final4 as well.
- hnuser123456 1y agoAlso the foo_bar method from v1 worked better so pull that back in
- rwmj 1y agoYou joke, but when I was doing my start-up we made good money on the side from monitoring websites to detect when the designers had pushed regressions to the live site. We would keep track of change requests that were filed and resolved, then scripts would monitor the sites to see if any earlier changes had been backed out. (Getting the designers to use version control was considered to be in the "too hard" bucket. This was back in the mid 2000s.)
- ZiiS 1y agoStill better than CVS then /s
- taude 1y agoSo glad we never bothered to migrate from Visual Source Safe
- vehemenz 1y agoMake sure everyone has caching disabled, for maximum effect
- tetha 1y agoWe have post-its with file names on a wall in the office. You take one down if you edit the file, and put it back up when you're done. Easy. Though I wish I was entirely kidding. ~12 years ago or so we did that if one of two parallel development teams had to modify a message of the network protocol to avoid incompatibilities and merge problems. Mind you, these were SVN merges. I can't even verbalize my feelings about SVN merges but by a mixture of laughing and groaning in pain, like if you stubbed your toe in a painful, but entirely funny way.
- spicybright 1y agoKeeping it when tech can't keep up is genuinely a good hack for any kind of engineering. Physical lock out tag out on industrial machines for instance. Passing paper notes/wooden blocks in air traffic control towers to see who's responsible for what even if computers go down.
- xorcist 1y agoWhat is this eternal meme about merges in svn being harder than in other tools? Git used literally the same merge algorithm, even if that has changed a bit since then, and merge conflicts are not something a tool can't just magically make disappear. If you want concurrent edits (the c in cvs), conflicts come in the same package. Various algortihms can supply their own dose of magic, but they're more similar than different (minus a few special cases such as rerere in git).
- tetha 1y agoMy interpretation within that company: You know this new idea of "If it's painful, do it more"? People in that company didn't do that in the SVN days or earlier, because merges were painful. Thus, merges filled a sprint if they had to be done. This made sense if you came from CSV or nothing, tbh. Git in turn made branches easier, causing merges to be more prevalent and developers overall learned to merge more, merge more often.
- xorcist 1y ago
- davey48016 1y agoThat's a single point of failure. If you email code changes around and use an email client that copies everything offline, then the history of your code base is distributed across all of your developers' laptops.
- jaredsohn 1y agoGood thing we just SSH into production and make the changes live.
- gloxkiqcza 1y agoVibe coding nonetheless #gofastandbreakthings
- redserk 1y agoSubtle Elixir/Erlang advocacy here.
- rwmj 1y agoYou're using Ansible?
- hdgvhicv 1y agoDo it manual you can screw up one server at a time Run ansible and you can screw it all up
- phendrenad2 1y agorsync is all you need ;)
- jaredsohn 1y agonah - ftp or run vi from ssh