50,000? thems rookie numbers.
Been writing code for a good while. Will probably continue writing code for a while longer.
50,000? thems rookie numbers.
only way to be sure…
do it often. you may end up with 150 conflicts to have to wade through.
fond memories for BeOS
unless you inherit a large base written by someone who is bad at it where their approach seemed to be to write new bad rules in attempt to cover up previous bad rules and so on. we all know how supportive employers are at addressing technical debt. (site redesign cant come soon enough)
tarsnap makes use of S3. does a decent deduplication job as well
“algorithm” is a little too fine grained for what you describe. “software design patterns” is probably what you are looking for.
unfortunately, not all projects call out the patterns they employ.
nick named “meth damon”
they are just too expensive to maintain… would you like to rent a BMW?
just tell them there is a black man at the moment of theft, they will get on it lickety split!
need permisson for the bus too. “exact change only!!”
we all miss the blink element.
drive till you hit something. helluva strategy.
there was also a project to build it out in unreal engine.
firefox ‘offline mode’ not an option?
making them better would mean more work, stress and ill conceived requirements for the programmers. I’m more in favor of marketing thrashing about on their own.