DawnOfRiku,

Running it in a test environment and then not having users test (vendor upgrade, in-house internal-facing app, or integration), and then being ordered to put it in prod, then people start mentioning the things they should’ve been mentioning all along. Can’t blame them, as our timelines are short and every department is overworked and varying degrees of being understaffed.

mojo,

Over confidence and coffee are the only unit tests I need

ScrewdriverFactoryFactoryProvider,
@ScrewdriverFactoryFactoryProvider@hexbear.net avatar

Also, it still counts as pushing straight to prod if your PR reviewer gives it a once-over and stamps it with “LGTM”

DeathsEmbrace,

Let us be real honest, rarely your code isn’t completely broken.

Hazzia,

I still remember the one time I wrote code that worked the first try.

It was a single function of minimal complexity, but it’s literally the only time that’s happened with more than one line or conditional, so it’s special to me dammit.

noproblemmy,

The moment you need to break your code to make sure it was working.

Avg,

I once wrote a script from beginning to end that executed correctly the first time I ran, I spent the next 30 minutes troubleshooting.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • uselessserver093
  • Food
  • aaaaaaacccccccce
  • [email protected]
  • test
  • CafeMeta
  • testmag
  • MUD
  • RhythmGameZone
  • RSS
  • dabs
  • Socialism
  • KbinCafe
  • TheResearchGuardian
  • oklahoma
  • feritale
  • SuperSentai
  • KamenRider
  • All magazines