• 0 Posts
  • 129 Comments
Joined 10 months ago
cake
Cake day: September 11th, 2023

help-circle





  • But it’s genuinely what we were all doing not so long ago

    Jokes on you, my first job was editing files directly in production. It was for a webapp written in Classic ASP. To add a new feature, you made a copy of the current version of the page (eg index2_new.asp became index2_new_v2.asp) and developed your feature there by hitting the live page with your web browser.

    When you were ready to deploy, you modified all the other pages to link to your new page

    Good times!




  • It’s like rebrands.

    Most rebrands occur because the average marketing person is pretty average and “rebrand” looks good on your CV.

    A couple of million later, half way through, customers hate the new brand and the marketing people who started it have already left for greener pastures

    Redesigning a perfectly good design that everyone is used to allows you to put “designed Netflix user interface” on your CV, and since management has to spend a ton of money on it, suddenly your team is worth something


  • I disagree unless the tests are reasonably high level.

    Half the time the thing you’re testing is so poorly defined that the only way to tighten that definition is to iterate.

    In this sense, you’re wasting time writing tests until you’ve iterated enough to have something worth testing.

    At that point, a couple of regression tests offer the biggest bang for buck so you can sanity check things are still working when you move on to another function and forget all about this one